Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ecf-dev] Connection problems with the container for ActiveMQ 5.2

Furio Belgiorno ha scritto:
Hi,

Just some more details.
When the client fails to connect, the exception thrown is a ContainerConnectedException and the message is:

   connect failed to tcp://172.16.15.63:61616/exampleTopic

Then the execution hangs in ClientSOContainer.java, line 151, at the instruction

   setStateDisconnected(aConnection);

Regards,
Furio Belgiorno


Furio Belgiorno ha scritto:
Hi everybody,

I am trying to use the ECF container for ActiveMQ 5.2 (I have downloaded the head revision code from ecf1.osuosl.org CVS).

Our test consists of creating a server and some clients with 10 shared objects, and each client sends a random text message for each shared object at a random time interval between 10 and 20 seconds. (It is almost the same test we used for the ECF generic container, in which the time interval was 1-2 seconds, and that was very satisfactory in the LAN environment).

The main problem is that most clients fail to connect and hang, and we cannot connect more than 1-2 clients (20 clients was the default in our tests with the ECF generic container).

These events are traced by the server when a client fails to connect:

Received event: ContainerSharedObjectMessageSendingEvent[localContainerID=JMSID[tcp://172.16.15.63:61616/exampleTopic];targetContainerID=StringID[client1238590318859];sharedObjectID=StringID[textSo4];message=connection ok] Received event: ContainerSharedObjectMessageSendingEvent[localContainerID=JMSID[tcp://172.16.15.63:61616/exampleTopic];targetContainerID=StringID[client1238590318859];sharedObjectID=StringID[textSo1];message=connection ok] Received event: ContainerSharedObjectMessageSendingEvent[localContainerID=JMSID[tcp://172.16.15.63:61616/exampleTopic];targetContainerID=StringID[client1238590318859];sharedObjectID=StringID[textSo8];message=connection ok] Received event: ContainerSharedObjectMessageSendingEvent[localContainerID=JMSID[tcp://172.16.15.63:61616/exampleTopic];targetContainerID=StringID[client1238590318859];sharedObjectID=StringID[textSo6];message=connection ok] Received event: ContainerSharedObjectMessageSendingEvent[localContainerID=JMSID[tcp://172.16.15.63:61616/exampleTopic];targetContainerID=StringID[client1238590318859];sharedObjectID=StringID[textSo9];message=connection ok] Received event: ContainerSharedObjectMessageSendingEvent[localContainerID=JMSID[tcp://172.16.15.63:61616/exampleTopic];targetContainerID=StringID[client1238590318859];sharedObjectID=StringID[textSo2];message=connection ok] Received event: ContainerSharedObjectMessageSendingEvent[localContainerID=JMSID[tcp://172.16.15.63:61616/exampleTopic];targetContainerID=StringID[client1238590318859];sharedObjectID=StringID[textSo3];message=connection ok] Received event: ContainerSharedObjectMessageSendingEvent[localContainerID=JMSID[tcp://172.16.15.63:61616/exampleTopic];targetContainerID=StringID[client1238590318859];sharedObjectID=StringID[core];message=connection ok] Received event: ContainerSharedObjectMessageSendingEvent[localContainerID=JMSID[tcp://172.16.15.63:61616/exampleTopic];targetContainerID=StringID[client1238590318859];sharedObjectID=StringID[textSo5];message=connection ok] Received event: ContainerSharedObjectMessageSendingEvent[localContainerID=JMSID[tcp://172.16.15.63:61616/exampleTopic];targetContainerID=StringID[client1238590318859];sharedObjectID=StringID[textSo0];message=connection ok] Received event: ContainerSharedObjectMessageSendingEvent[localContainerID=JMSID[tcp://172.16.15.63:61616/exampleTopic];targetContainerID=StringID[client1238590318859];sharedObjectID=StringID[textSo7];message=connection ok] Received event: ContainerConnectedEvent[JMSID[tcp://172.16.15.63:61616/exampleTopic]]StringID[client1238590318859]; Received event: ContainerEjectedEvent[JMSID[tcp://172.16.15.63:61616/exampleTopic];StringID[client1238590318859];java.io.IOException: timeout waiting for response]

It seems that the container is connected and then ejected (look at the last two lines).

Any suggestion? Is this a problem with the current version in development?

Thanks for any tip,

Furio Belgiorno
_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev

_______________________________________________
ecf-dev mailing list
ecf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ecf-dev
Hi,

The bug has been solved. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=270942

Furio


Back to the top