Workbench ES2 Hangs When Deployed with LiveCycle Data Services 3.0

There is a port conflict when LiveCycle Workbench ES2 is installed on the same machine instance as LiveCycle Data Services 3.0. As a result, if you try to start Workbench ES2 on a machine where LCDS is already running, it will hang. The Workbench log (at C:\Users\<your_login_name>\Workbench ES2\.metadata\.log in Windows 7) will report this:
!MESSAGE The communication port 2038 is unavailabe, trying again using port 2048.

To fix this, you have to break open the lcds.war file using WinRAR, WinZIP or some other tool and change the RTMP port. The port is set in \WEB-INF\flex\services-config.xml. Look for a channel definition called my-rtmp (<channel-definition id=”my-rtmp”) and change the port number for the endpoint URL (<endpoint url=”rtmp://{server.name}:2038″) from 2038 to some other port such as 2058. Insert this file back into lcds.war, deploy it to the appserver and re-start the appserver.

You should now be able to start Workbench ES2 without it hanging.

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 ES and tagged . Bookmark the permalink.

Comments are closed.