u reproduce the problem reliably in a minimal setup (just one or
>
> two
>
> clients, minimal time and message load)?
>
> Tim
>
> On Tue, Nov 2, 2021, 5:19 AM Guillaume Cripiau
> wrote:
>
>
> Hello,
>
> We need support. Many devices disconnect for no apparen
> Hello,
> >>
> >> We need support. Many devices disconnect for no apparent reason and
> >> cannot reconnect after several days. Could you help us solve this
> >> problem? Here is an example in the logs :
> >>
> >
us solve this
problem? Here is an example in the logs :
2021-11-02 10:30:44,413 | WARN | Transport Connection to:
tcp://62.83.10.35:1024 failed |
org.apache.activemq.broker.TransportConnection.Transport | Async
Exception Handler | localhost| |
java.io.IOException: Con
che.activemq.broker.TransportConnection.Transport | Async
> > Exception Handler | localhost| |
> > java.io.IOException: Connection reset
> > at
> >
> org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:46)[activemq-client-5.16.3.jar:5.
|
org.apache.activemq.broker.TransportConnection.Transport | Async
Exception Handler | localhost | |
java.io.IOException: Connection reset
at
org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport.java:46)[activemq-client-5.16.3.jar:5.16.3]
at
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
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
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
ublish. 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'd like to know, if the latest version needs different configuration, or
> be
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
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
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
> 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
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
compared to ActiveMQ 5.10.0).
>
> *[20150630 06:11:24.247 EDT (ActiveMQ NIO Worker 181214)
> org.apache.activemq.broker.TransportConnection#serviceTransportException
> 245
> WARN] - Transport Connection to: tcp://10.79.27.110:16327 failed:
> java.io.IOException: Connection reset by p
failed:
java.io.IOException: Connection reset by peer*
Is there a way to add other information in this error log, like client id,
connection id, destination name. This can help in identifying which client
connection had some problem.
--bansalp
--
View this message in context:
http://activemq
(standard out):
WARN: Transport Connect to tcp:// failed: java.net.SocketException:
Connection reset
I did try to "uncomment" the openwire protocl definition and append
"transport.useInactivityMonitor=false":
I still cannot get warning messages to disapper. Any input will be
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.
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
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
connect to the host server but when i tried sending a message (a xml
message/file) facing an exception. Error is coming when i do getOutputStream
from the HttpConnection object.
java.net.SocketException: Connection reset
at java.net.SocketInputStream.read(SocketInputStream.java:168)
at
have missed to add any more jar or did i have done
any mistake here?
Thanks.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Connection-reset-when-using-ActiveMQ-5-9-libraries-tp4675285p4675289.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
The dbcp connection pool may return a invalid connection when you require a
new connection to update the lease.
Enabling the idle check for the connection pool should help.
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Failed-to-update-lease-Oracle-connection-Reset
Mandar,
I am facing the same issue.
Did you have a solution for this?
Please post the solution if you had.
Thanks
Pramod
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Failed-to-update-lease-Oracle-connection-Reset-tp4662859p4668380.html
Sent from the ActiveMQ - User
tcp://10.10.0.112:61837 failed:
java.net.SocketException: Connection reset
--
View this message in context:
http://activemq.2283324.n4.nabble.com/Getting-Connection-Reset-While-consumer-receive-is-called-tp4667204.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
lease DB locking mechanism. I am facing strange
> issue in which AMQ after some random time once its up, crashes throwing
> below error.
>
> 2013-02-04 22:49:45,168 | WARN | , failed to update lease:
> java.sql.SQLRecoverableException: IO
Hi All,
We have configured AMQ in lease DB locking mechanism. I am facing strange
issue in which AMQ after some random time once its up, crashes throwing
below error.
2013-02-04 22:49:45,168 | WARN | , failed to update lease:
java.sql.SQLRecoverableException: IO Error: Connection reset
:26 PM, ruiluis wrote:
> you all were right.. the problem was originated by a router that for a
> reason
> that i am unaware of, simply decides to drop my tcps connections.
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Connection-re
inutes.. some third process
> removing the connections that is very strange because the server is a clean
> server running almost nothing..
>
>
>
> --
> View this message in context:
> http://activemq.2283324.n4.nabble.com/Connection-reset-tp4660818p4660921.html
> Sent fr
://activemq.2283324.n4.nabble.com/Connection-reset-tp4660818p4660921.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
ause the clients do not detect the connection
>> failure...
>>
>> 2012-12-18 11:27:21,401 | DEBUG | Transport Connection to:
>> tcp://127.0.0.1:1031 failed: java.net.SocketException: Connection reset |
>> org.apache.activemq.broker.TransportConnection.Transport | Act
the clients do not detect the connection
failure...
2012-12-18 11:27:21,401 | DEBUG | Transport Connection to:
tcp://127.0.0.1:1031 failed: java.net.SocketException: Connection reset |
org.apache.activemq.broker.TransportConnection.Transport | ActiveMQ
Transport: tcp:///127.0.0.1:1031@61613
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
Hi Dejan,
Dejan Bosanac wrote:
>
>
> it'd be great to make this work for Stomp. Any contribution is welcome.
> For
> starters, let's create a Jira issue to track this requirement.
>
>
I have created https://issues.apache.org/activemq/browse/AMQ-2646
Regards,
-
Michael Justin
SCJP, S
that the Stomp code handles the new header property in an unexpected
> way. If I find the time I'll have a look at the source code.
>
> Regards,
>
>
> -
> Michael Justin
> SCJP, SCJA
> betasoft - Software for Delphi™ and for the Java™ platform
> http://www.mikejus
View this message in context:
http://old.nabble.com/Delay-messages-with-Stomp%3A-connection-reset-tp27837862p27837862.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
appeared connecting from the server running php
5.1 to the amq server. So the above issue may only be an issue in php5.1.
Rob
--
View this message in context:
http://www.nabble.com/Connection-not-acknowledged---Connection-reset-tp19163862p19180884.html
Sent from the ActiveMQ - User mailing list
essages that are with the size below 42KB, with
> messages that are bigger than that broker resets the connection after 42KB
> written with fwrite() to tcp socket while sending message
>
> Is this connection reset normal behavior of the broker if its internal
> settings are that 42KB is the
; problems for messages that are with the size below 42KB, with messages that
> are bigger than that broker resets the connection after 42KB written with
> fwrite() to tcp socket while sending message
>
> Is this connection reset normal behavior of the broker if its internal
> setting
itten with
fwrite() to tcp socket while sending message
Is this connection reset normal behavior of the broker if its internal
settings are that 42KB is the message size it can accept?
I use persistent storage and I'm not sure that it should complain about the
message size at all? I tried to
40 matches
Mail list logo