Re: Continously java.net.SocketException: Connection reset

2020-04-29 Thread AntonR
You might have some luck trying the "keepAlive" option detailed here: http://activemq.apache.org/tcp-transport-reference if the connection is getting terminated by the haproxy for some reason. Br, Anton -- Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Continously java.net.SocketException: Connection reset

2020-04-24 Thread Tim Bain
You're right, I re-read the log and you did provide the broker logs. Sorry for the confusion. I assume the client logs show something similar for the root cause (even though it'll be a different stack trace)? Unfortunately I don't have any experience configuring or troubleshooting HAProxy. I reco

Re: Continously java.net.SocketException: Connection reset

2020-04-23 Thread JJ
No. The connection established using localhost is working as expected. The question is how to configure HAProxy properly? I just used the old configuration working with Activemq 5.15.3 The broker log is the one I have already posted, isn't it? Is there another specific log?If yes I do not know how

Re: Continously java.net.SocketException: Connection reset

2020-04-23 Thread Tim Bain
I hadn't understood that the connection was initially successful and data passes correctly at first, so thank you for clarifying that. Do you see the same behavior if you connect directly to the broker without going through the HAProxy? Might this be introduced by the loan balancer, possibly due t

Re: Continously java.net.SocketException: Connection reset

2020-04-21 Thread JJ
Sorry but iI do not understand what you mean. The clients regularly estabilish the connection, subscribe and publish. But after some seconds they are disconnected and I found a lot af Connection reset server/broker side. I use the same configuration fo years, but with an older Activemq version. I'

Re: Continously java.net.SocketException: Connection reset

2020-04-21 Thread Tim Bain
What URI (without the HAProxy IP, of course) are you using in your MQTT client? It's OK/expected that the underlying protocol be TCP at the network level, but the client needs to be specifying mqtt:// in the URI to tell the client library to use MQTT over TCP instead of OpenWire over TCP. It also n

Re: Continously java.net.SocketException: Connection reset

2020-04-21 Thread JJ
I forgot to write that Activemq is behind HAProxy as pfsense plugin. The client MQTT connects to the the public pfsense WAN->nat to VIP -> VIP is HAProxy frontend -> backend with one server. HAproxy frontend is set as tcp. ActiveMQ listen on: -- Sent from: htt

Re: Continously java.net.SocketException: Connection reset

2020-04-20 Thread Tim Bain
> Simple MQTT connection produce continously errors, and after few seconds > client disconnection. > > activemq.xml is the default one. > > Any help/hint? > > java.net.SocketException: Connection reset > at java.base/java.net > .SocketInputStream.read(Socke

Continously java.net.SocketException: Connection reset

2020-04-20 Thread JJ
Simple MQTT connection produce continously errors, and after few seconds client disconnection. activemq.xml is the default one. Any help/hint? java.net.SocketException: Connection reset at java.base/java.net.SocketInputStream.read(SocketInputStream.java:186)[:] at java.base

Re: Transport failed: java.net.SocketException: Connection reset

2014-03-24 Thread manikandan0110
we are also facing the same kind of issue. how did you resolve the issue -- View this message in context: http://activemq.2283324.n4.nabble.com/Transport-failed-java-net-SocketException-Connection-reset-tp4676162p4679459.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Transport failed: java.net.SocketException: Connection reset

2014-01-13 Thread Torsten Mielke
tmielke.blogspot.com On 09 Jan 2014, at 16:35 pm, asantos wrote: > hi guys, > > Our clients activemq stopped connecting to server apparently after this > error, Would anyone have any idea what is happening? > > | DEBUG | Transport failed: java.net.SocketException

Transport failed: java.net.SocketException: Connection reset

2014-01-10 Thread asantos
hi guys, Our clients activemq stopped connecting to server apparently after this error, Would anyone have any idea what is happening? | DEBUG | Transport failed: java.net.SocketException: Connection reset | org.apache.activemq.broker.TransportConnection.Transport | InactivityMonitor Async Task

Re: Getting 'java.net.SocketException' in ActiveMQ logs frequently

2013-04-23 Thread Howard W. Smith, Jr.
> > > At 2013-04-23 15:26:21,Prashant wrote: > >We are frequently getting 'java.net.SocketException' in ActiveMQ logs. > Aftr > >that the number of consumer becomes 0 and message becomes pending. > >java.net.SocketException: Connection reset | > >org.

Re:Getting 'java.net.SocketException' in ActiveMQ logs frequently

2013-04-23 Thread SuoNayi
Seems this is a real FAQ but never gets answered. http://stackoverflow.com/questions/62929/java-net-socketexception-connection-reset At 2013-04-23 15:26:21,Prashant wrote: >We are frequently getting 'java.net.SocketException' in ActiveMQ logs. Aftr >that the number of consum

Getting 'java.net.SocketException' in ActiveMQ logs frequently

2013-04-23 Thread Prashant
We are frequently getting 'java.net.SocketException' in ActiveMQ logs. Aftr that the number of consumer becomes 0 and message becomes pending. java.net.SocketException: Connection reset | org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ Transport: tcp:///10.51.19.88:

Re: after tomcat 7/java 7 upgrade: failed to process packet: java.net.SocketException: Socket closed

2012-08-13 Thread john bush
gt; org.apache.activemq.transport.discovery.multicast.MulticastDiscoveryAgent >> - >> failed to process packet: java.net.SocketException: Socket closed >> >> Any ideas, totally stuck here. It went away for a day and now back. Very >> strange. >> >

Re: after tomcat 7/java 7 upgrade: failed to process packet: java.net.SocketException: Socket closed

2012-08-13 Thread Torsten Mielke
13:24:19,198 ERROR > MulticastDiscoveryAgent-advertise:tcp://localhost:61616:Thread-14 > org.apache.activemq.transport.discovery.multicast.MulticastDiscoveryAgent - > failed to process packet: java.net.SocketException: Socket closed > > Any ideas, totally stuck here. It went away for a

after tomcat 7/java 7 upgrade: failed to process packet: java.net.SocketException: Socket closed

2012-08-09 Thread john bush
:61616:Thread-14 org.apache.activemq.transport.discovery.multicast.MulticastDiscoveryAgent - failed to process packet: java.net.SocketException: Socket closed Any ideas, totally stuck here. It went away for a day and now back. Very strange. -- View this message in context: http://activemq

Re: Get exception in broker networks java.net.SocketException: Broken pipe

2011-07-21 Thread mahens
I have the similar problem getting exception in activemq.log as Transport failed: java.net.SocketException: Broken pipe | org.apache.activemq.broker.TransportConnection.Transport | InactivityMonitor Async Task: java.util.concurrent.ThreadPoolExecutor$Worker@77517751 java.net.SocketException

Re: Get exception in broker networks java.net.SocketException: Broken pipe

2011-06-25 Thread jessezbj
I was using DurableSubscriber and I already set static://(tcp://brokerb:61616?wireFormat.maxInactivityDuration=0) for broker network connection, and it can send for a while but finally get broken. What is the reason? -- View this message in context: http://activemq.2283324.n4.nabble.com/Get-excep

Get exception in broker networks java.net.SocketException: Broken pipe

2011-06-25 Thread jessezbj
java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) at java.net.SocketOutputStream.write(SocketOutputStream.java:136) at

our program reconnect repeatly due to java.net.SocketException: Connection reset

2011-06-22 Thread hunan
we use activemq 5.3.0 , our client program reconnect repeatly due to " java.net.SocketException: Connection reset" on that computer , but normal on other computers , the concrete logs is: [DEBUG] 2011-06-17 21:11:39,343 [] org.apache.activemq.transport.ResponseCor relator

Weird java.net.SocketException

2008-09-27 Thread Bryan.Shaw
consume message less than 1K byte, but the client can't consume a 60k byte message. I turned on the debug logging in the log4j.properties on the broker side, I saw exceptions thrown when client try to consume the message.The exception is java.net.SocketException: Software caused connection

Re: ActiveMQConnection:1653 - Async exception with no exception listener: java.net.SocketException: socket closed

2008-04-09 Thread Hatta
m the team about this matter. >> >> >> >> This log can be really disturbing when the solution goes to >> >> production. >> >> >> >> Regards >> >> Hatta >> >> >> >> >> >>

Re: ActiveMQConnection:1653 - Async exception with no exception listener: java.net.SocketException: socket closed

2008-04-09 Thread Dhruba Bandopadhyay
>> > >> Dil wrote: > >>> > >>> Did somebody see this Warning exception while using active MQ 5 when > >>> sending asynchronous messages? > >>> > >>> this is exception i am getting on producer class after some ti

Re: ActiveMQConnection:1653 - Async exception with no exception listener: java.net.SocketException: socket closed

2008-04-08 Thread Hatta
ception while using active MQ 5 when >>> sending asynchronous messages? >>> >>> this is exception i am getting on producer class after some time of >>> its >>> running. >>> >>> the url for broker is : >&g

Re: ActiveMQConnection:1653 - Async exception with no exception listener: java.net.SocketException: socket closed

2008-04-08 Thread Rob Davies
some time of its running. the url for broker is : tcp://localhost:61616?trace=true&wireFormat.maxInactivityDuration=-1 10:44:44,427 WARN ActiveMQConnection:1653 - Async exception with no exception listener: java.net.SocketException: socket closed java.net.SocketException: socket cl

Re: ActiveMQConnection:1653 - Async exception with no exception listener: java.net.SocketException: socket closed

2008-04-08 Thread Hatta
tion=-1 > > 10:44:44,427 WARN ActiveMQConnection:1653 - Async exception with no > exception listener: java.net.SocketException: socket closed > java.net.SocketException: socket closed > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.

ActiveMQConnection:1653 - Async exception with no exception listener: java.net.SocketException: socket closed

2008-03-27 Thread Dil
WARN ActiveMQConnection:1653 - Async exception with no exception listener: java.net.SocketException: socket closed java.net.SocketException: socket closed at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(Unknown Source)

Re: ActiveMQ Transport Server: tcp://localhost:61616] class [TransportConnector] Could not accept connection from /127.0.0.1:53085: java.net.SocketException: Socket closed

2008-03-25 Thread ttmdev
iveMQ with broker URL = > vm:broker:(tcp://localhost:61616)?brokerName=MessageTransport > > > getting sometime this error: > > [2008-03-25 11:58:17] : [DEBUG] thread [ActiveMQ Transport: > tcp:///127.0.0.1:54901] class [Transport] Transport failed: &g

ActiveMQ Transport Server: tcp://localhost:61616] class [TransportConnector] Could not accept connection from /127.0.0.1:53085: java.net.SocketException: Socket closed

2008-03-25 Thread Fuddi
: java.net.SocketException: Connection reset java.net.SocketException: Connection reset at java.net.SocketInputStream.read(SocketInputStream.java:168) at org.apache.activemq.transport.tcp.TcpBufferedInputStream.fill(TcpBufferedInputStream.java:49) at

java.net.SocketException!

2007-10-16 Thread goldi
Hallo everybody, everbody I'm using ActiveMQ in JBoss and within ServiveMix-ESB, as you can see in the picture. Today I got the following Excptions on the ESB-side (I just replaced IP with host): Could not accept connection from /host: java.net.SocketException: Socket c