Hi,
I am having trouble with messages not being delivered after a reconnect.
I am using ActiveMQ 5.7. My clients are connecting using the failover
transport and ssl. - moodycl
I have posted this same problem here before but this time I think it is a
little different.
A few years back we
I think I have found the problem. In ClassLoadingAwareObjectInputStream.java
the load() method makes a call to Class.forName().
For the primitive types (int, boolean, etc.) this would result in a call
similar to:
Class.forName(int, false, loader); //Where loader is the
Applet2ClassLoader
So far I have not been able to reproduce this outside of the applet.
I have setup small test applications on the same machine as the client, but
they never seem to fail.
I can run them both at the same time and the applet will fail to reconnect
completely while the test app operates just fine.
I
I am having a problem loading classes when my applet reconnects to the
backup server after a network failure. My messages are taking a very long
time to be processed and I think that it is because the
ClassLoadingAwareObjectInputStream is still trying to connect to the
original server that served
Update:
Some more testing has shown that this may be a problem related to connecting
to the broker from inside the applet. It appears that the connection fails
to setup properly when failing over to the server that did not originally
serve up the applet. This only happens when the network cable
Currently the two brokers are not connected. They are completely separate.
The destinations are all created on demand when the clients subscribe.
Here is what my client URI looks like.
