?
If neither the client nor the broker initiated the disconnect, perhaps
there's a network hickup causing the same.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/activemq-client-does-not-close-properly-connections-to-the-broker-tp4681005p4681006.html
Sent from the ActiveMQ
InternalManagedConnectionPool.removeIdleConnections() line: 483
IdleRemover$IdleRemoverRunnable.run() line: 171
Thread.run() line: 744
Now It is time to look for candidates...
--
View this message in context:
http://activemq.2283324.n4.nabble.com/activemq-client-does-not-close-properly-connections-to-the-broker
concerns about it, that's why I'm
investigating. My next step will be to check the IdleRemover to see what
It's doing :-)
--
View this message in context:
http://activemq.2283324.n4.nabble.com/activemq-client-does-not-close-properly-connections-to-the-broker-tp4681005p4681131.html
Sent from
-not-close-properly-connections-to-the-broker-tp4681005p4681082.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
You should test against the trunk code as the code you are using is not
the latest and my not have all current fixes.
--
Tim Bish
Sr Software Engineer | RedHat Inc
high enough.
In order to raise a bug with the community that is likely to get attention,
it would be helpful to have a minimal use-case showing the problem with only
ActiveMQ code.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/activemq-client-does-not-close-properly
:
http://activemq.2283324.n4.nabble.com/activemq-client-does-not-close-properly-connections-to-the-broker-tp4681005p4681114.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
you think?
Thanks a lot for your help.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/activemq-client-does-not-close-properly-connections-to-the-broker-tp4681005p4681123.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
, but on the
method start() or on a similar place the invocation to /started.set(true); /
is missing.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/activemq-client-does-not-close-properly-connections-to-the-broker-tp4681005p4681084.html
Sent from the ActiveMQ - User
-60024 | Transport
Connection to: tcp://172.16.151.77:54043 failed: java.net.SocketException:
Connection reset
Should I raise a bug with this?
Thanks.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/activemq-client-does-not-close-properly-connections-to-the-broker
Hi
Thanks for your answer, I will do It next week and tell you about my
findings.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/activemq-client-does-not-close-properly-connections-to-the-broker-tp4681005p4681007.html
Sent from the ActiveMQ - User mailing list archive
that It is what It is happening on my scenario, although I'm
using Java 7.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/activemq-client-does-not-close-properly-connections-to-the-broker-tp4681005.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
11 matches
Mail list logo