Messaging SocketServer stops to accept new connections on Solaris

[#1]

We have migrated our application from LCDS2.6 to LCDS3.1 on Tomcat 5.5 running on Solaris 10.

Since we have done this our SocketServer (used by rtmp & nio-channel) stops accepting new connections after X time (sometimes some hours, some time some minutes). Connected clients keep getting messages on port 2037, but any new connection on this port fails. (also a telnet is no longer possible)

Does any one has seen this problem?

Any help is welcome !

This is the situation:

We have 1 message destination in our messaging-config

<destination id="marketdataStream">

<properties>

<server><message-time-to-live>12000</message-time-to-live>

<durable>false</durable>

<allow-subtopics>true</allow-subtopics></server>

</properties>

<channels>

<channel ref="serverRtmp"/>

<channel ref="serverNio"/>

<channel ref="serverHttp"/>

</channels>

</destination>

The SocketServer configured in flex-config

<servers>

<server id="nioserver" class="flex.messaging.socketserver.SocketServer">

<properties>

<http>

<cross-domain-path>crossdomain.xml</cross-domain-path>

</http>

</properties>

</server>

</servers>

the 2 channels use the same socketserver. (serverRtmp & serverNio)

<channel-definition id="serverNio" class="mx.messaging.channels.AMFChannel">

<endpoint url="http://localhost:2037/nio" class="flex.messaging.endpoints.NIOAMFEndpoint"/>

<server ref="nioserver"/>

<properties>

<polling-enabled>true</polling-enabled>

<polling-interval-millis>0</polling-interval-millis>

<wait-interval-millis>-1</wait-interval-millis>

</properties>

</channel-definition>

<channel-definition id="serverRtmp" class="mx.messaging.channels.RTMPChannel">

<endpoint uri="rtmp://localhost:2037/rtmp" class="flex.messaging.endpoints.RTMPEndpoint"/>

<server ref="nioserver"/>

<properties>

<block-rtmpt-polling-clients>true</block-rtmpt-polling-clients>

</properties>

</channel-definition>

</channels>

[tomj]

My guess is there is a Solaris socket configuration that needs to be adjusted upwards to allow more connections per port.  I do not know if there is such a configuration setting, nor what it might be, as my Solaris expertise stops with Solaris 7.

Also check to make sure you have correctly configured your license as the developer edition will restrict the number of IP addresses that are able to connect.

[#3]

Hi,

Thanks for your quick response.

I think the license is ok since this is in our log-file: Flex12/08/2010

08:13:10.299 Starting Adobe LiveCycle Data Services: 3.1.0.273931

Enterprise License

I have also thought about some Solaris configuration. But why didn't we

had this problem with lcds 2.6?

I will look some further in that direction.

Best regards,

tomj <forums@adobe.com>

08/12/2010 15:59

Please respond to

clearspace-270237165-570794-2-3326115@mail.forums.adobe.com

Subject

LiveCycle Data Services ES Messaging SocketServer stops to accept new

connections on Solaris

My guess is there is a Solaris socket configuration that needs to be

adjusted upwards to allow more connections per port.  I do not know if

there is such a configuration setting, nor what it might be, as my Solaris

expertise stops with Solaris 7.

Also check to make sure you have correctly configured your license as the

developer edition will restrict the number of IP addresses that are able

to connect.

[#4]

Could you try to figure out whether this is related to the number of connections? If so, we can be more certain that it's an OS level connection limit. Also, when the server stops accepting new connections, could you get a JVM thread-dump to see if there's a deadlock or something?