LiveCycle JBoss/Tomcat Port Conflict on IBM System x and BladeCenter Servers

If you are trying to deploy LiveCycle with JBoss on IBM’s System x or BladeCenter servers (such as the x3650 M3), you might run into port conflict issues. JBoss Application Server uses Apache Tomcat as its J2EE Web Container implementation. By default, Tomcat listens for incoming HTTP connections on port 8080.

However, IBM System x and BladeCenter servers run the IBM ServeRAID Manager application that has a miniwinagent.exe (ServeRAID FlashCopy Agent) that also listens on port 8080. Since this is part of the system image, it will always be running and system administrators won’t allow this to be turned off. LiveCycle installations fail when they run against this.

The solution is to change the port Tomcat listens from 8080 to 8090, and continuing the install from where it failed (don’t start from scratch).

You can do this by editing the file server.xml in %JBOSS_HOME%\server\lc_turnkeyl\deploy\jboss-web.deployer\ with a reliable text editor. The line will look something like this:

<connector port="8080" address="${jboss.bind.address}"
maxThreads="250" maxHttpHeaderSize="8192"
emptySessionPath="true" protocol="org.apache.coyote.http11.Http11AprProtocol"
enableLookups="false" redirectPort="443" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true" />

Re-start JBoss after the change is made.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)
This entry was posted in Adobe LiveCycle ES2 (9.0.x), Adobe LiveCycle ES, Adobe LiveCycle 7.x, General Interest and tagged , . Bookmark the permalink.

Comments are closed.