Hi again:
I looked futher into this issue.
It is strange that, something seems to be wrong with my camel route bundles.
Initially, I was not able to replicate this issue on a different system.
Then, I used my camel routes bundle that was built 2 weeks ago. And, now I
see plenty of connections. I
Hi:
I just tried netstat, and I see majority of the connections as "TIME_WAIT".
And, there are a lot of connections.
Thank you for the pointers. I will dig further and post back later.
Regards,
Cooshal.
--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html
This sounds to me like a misbehaving connection pool. Maybe jax-jms has a
bug?
I'd try to get a count of open and recently-closed sockets on the client
host (e.g. via netstat) to try to confirm that. If you see tens of
thousands, you'll want to try to dig into why they're being closed and
re-opene
Hi again:
has anyone encountered and resolved similar issue ?
My activemq configuration has the default stuffs. Should I configure
something there as well?
After I update my pax-jms configuration by adding pool=transx, I get
following log events:
INFO Updating configuration from org.ops4j.conn
Hi JB:
Thank you for your reply.
how do I start an embedded server in the bundle? I do not recall doing
anything like that. Following lines are in my jms config file:
name=db-consumer
jms.url=tcp://localhost:61616
jms.username=
jms.password=
type=activemq
osgi.jndi.service.name=jms/consumer
;
>name=db-consumer
>jms.url=tcp://localhost:61616
>jms.username=
>jms.password=
>type=activemq
>osgi.jndi.service.name=jms/consumer
>
>Time and again, with high frequency of data, I am getting the following
>error:
>
>Uncategorized exception occurred during JMS processing;
JMS processing; nested exception is
javax.jms.JMSException: Could not connect to broker URL:
tcp://localhost:61616. Reason: java.net.BindException: Address already in
use: connect
Do I need to configure something specific in the broker or in the
configuration to resolve this issue?
Regards
be greatly appreciated.
>
> Stacktrace: org.springframework.jms.UncategorizedJmsException:
> Uncategorized exception occurred during JMS processing; nested exception is
> javax.jms.JMSException: Error while attempting to add new Connection to the
> pool; nested exception is javax.jms.JMSExcepti
: org.springframework.jms.UncategorizedJmsException:
Uncategorized exception occurred during JMS processing; nested exception is
javax.jms.JMSException: Error while attempting to add new Connection to the
pool; nested exception is javax.jms.JMSException: Could not connect to
broker URL: tcp://localhost:61616. Reason
ave tried to create the
broker with
the Spring configuration and problematically with the same
result. Any
insight would be greatly appreciated.
Thanks in advance.
TQ
--
View this message in context:
http://old.nabble.com/Could-not-connect-to-broker-URL%3A-tcp-remote-connection-failure-tp27184
I can provide the code for the client, but it seems unnecessary
>>>>> since it
>>>>> does work within the same machine.
>>>>>
>>>>> I have spent a few days trying to resolve this problem and gone
>>>>> through the
>>>>&
connect without issue. I can
provide
the code if desired.
I do not know what I am missing here. I have tried to create the
broker with
the Spring configuration and problematically with the same
result. Any
insight would be greatly appreciated.
Thanks in advance.
TQ
--
View this message in co
/p27184667/netstat.txt netstat.txt
>>>
>>> I also know that a connection is possible because I have written a
>>> simple
>>> echo server and echo client that can connect without issue. I can
>>> provide
>>> the code if desired.
>>>
>>
de
>> the code if desired.
>>
>> I do not know what I am missing here. I have tried to create the
>> broker with
>> the Spring configuration and problematically with the same result. Any
>> insight would be greatly appreciated.
>>
>> Thanks in advan
.
TQ
--
View this message in context:
http://old.nabble.com/Could-not-connect-to-broker-URL%3A-tcp-remote-connection-failure-tp27184667p27184667.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Rob Davies
http://twitter.com/rajdavies
I work here: http://fusesource.com
My
ied to create the broker with
the Spring configuration and problematically with the same result. Any
insight would be greatly appreciated.
Thanks in advance.
TQ
--
View this message in context:
http://old.nabble.com/Could-not-connect-to-broker-URL%3A-tcp-remote-connection-failure-tp27184667p271
t; to "ping" then?
>>>> Note that if I execute the sender from same windows machine as of
>>>> receiver/broker, then it is working fine.
>>>>
>>>> Exception in thread "main"
>>>> org.springframework.jms.UncategorizedJmsException: Uncategoriz
cured during JMS processing; nested exception is
>>> javax.jms.JMSException: Could not connect to br
>>> oker URL: tcp://150.123.186.61:61616. Reason:
>>> java.net.SocketTimeoutException: connect timed out;
JMS processing; nested exception is
>> javax.jms.JMSException: Could not connect to br
>> oker URL: tcp://150.123.186.61:61616. Reason:
>> java.net.SocketTimeoutException: connect timed out; ne
>> sted exception is java.net.SocketT
ed during JMS processing; nested exception is
> javax.jms.JMSException: Could not connect to br
> oker URL: tcp://150.123.186.61:61616. Reason:
> java.net.SocketTimeoutException: connect timed out; ne
> sted exception is java.net.SocketTimeoutException: connect timed
: connect timed out; ne
sted exception is java.net.SocketTimeoutException: connect timed out
Caused by: javax.jms.JMSException: Could not connect to broker URL:
tcp://150.123.186.61:61616. Reas
on: java.net.SocketTimeoutException: connect timed out
at
org.apache.activemq.util.JMSExceptionSupport.creat
been
>> working in the past, so we are not sure what is going on now.
>>
>> Could not connect to broker URL: tcp://eagle4c:61616?
>> socket.tcpNoDelay=true.
>> Reason: java.net.ConnectException: A remote host refused an attempted
>> connect operation
>>
Thanks Rob. We have confirmed that the broker is running and there is no
firewall issue. Sometimes we can fix the problem by recycling the JVM, but
eventually we end up with the same error message again:
Could not connect to broker URL: tcp://eagle4c:61616?
> socket.tcpNoDelay=true.
>
URL: tcp://eagle4c:61616?
socket.tcpNoDelay=true.
Reason: java.net.ConnectException: A remote host refused an attempted
connect operation
Thanks,
Bijou
--
View this message in context:
http://www.nabble.com/Could-not-connect-to-broker-URL%3A-tp15519981s2354p15519981.html
Sent from the ActiveMQ
Hello,
We are getting the following error message. Could this be a permissions
issue? The broker is on a Unix box, in a WebSphere environment. It has been
working in the past, so we are not sure what is going on now.
Could not connect to broker URL: tcp://eagle4c:61616?socket.tcpNoDelay=true
25 matches
Mail list logo
