CFMX 7.0.2: Preventing 'Unable to register Flex Assembler Service in RMI registry' error

Related Categories: ColdFusion

I've come across this error in two places with ColdFusion MX 7.0.2:

• a customer's JBoss deployment (unsupported)
• my own Server configuration

The error (recorded in CFMX's server.log) means the embedded Flex 2 Assembler service in CFMX 7.0.2 can not bind to TCP port 1099. This port is hard coded in the source code and cannot be modified. The solution is to discover what is bound to port 1099 and either stop it or reconfigure it to use another port (e.g. 11099), then restart/redeploy ColdFusion.

Use networking tools to verify which process is bound to port 1099:

For my CFMX Server configuration on my Windows 2003 Server, this turned out to be the File Replication service bound to port 1099. Stopping that service and restarting CFMX did the trick. JBoss binds the JNP/RMI service to TCP port 1099 by default. This bind happens prior to it deploying CFMX:

The solution is to modify the configuration (in either jboss-service.xml or naming-service.xml in the JBoss config folder) to use a different port and restart JBoss.

I wrote technote 400051 for supported CFMX configurations and 400048 for the JBoss configuration. Both are currently being reviewed, however since JBoss is an unsupported configuration, I do not know whether that technote will get published.

Comments (3) | Print | Send | del.icio.us | Digg It! | Linking Blogs

Comments (Comment Moderation is enabled. Your comment will not appear until approved.)

[Add Comment] [Subscribe to Comments]

Hi Sarge -- Regarding the RMI registry -- is there a way to prevent it from starting for a particular JRun instance? I'm running multiple CF instances -- only one of which is using Flex Integration. The RMI Registry appears to run under the first CF/Jrun instance started when the RMI Registry is not running. This causes problems when the instance running the RMI Registry is stopped. I'd prefer to have have the RMI Registry running ONLY under the CF instance with Flex Integration enabled. Any thoughts?

# Posted By Bernie Dolan | 11/30/06 2:40 PM

Hi Sarge - I'm getting a similar, but different, error in the CF Admin (CF 7.02) on top of Tomcat 5.5 when I try to Enable Flex Data Management support:

Error attempting to update settings:
Unable to register Flex Assembler Service in RMI registry: java.rmi.ServerException: RemoteException occurred in server thread; nested exception is: java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is: java.net.MalformedURLException: no protocol: Files/Apache.

any ideas?

# Posted By Aaron Longnion | 2/1/07 9:55 AM

Thank you Sarge - this made my life so much easier!

# Posted By anon | 2/8/07 10:47 AM

[Add Comment]