Art,
Looking at ActiveMQConnection, In the close method, I see
>
> ServiceSupport.dispose(this.transport);
>
Yes, now I can see it into the finally block, so the connection handle the
passed transaction close() call.
> This in turn calls
>
> service.stop();
>
> Which ult
Are there transactions part of the problem, or is that just a typo?
Looking at ActiveMQConnection, In the close method, I see
ServiceSupport.dispose(this.transport);
This in turn calls
service.stop();
Which ultimately closes the transport.
--
View this message in co
Thanks. By the way - stopping the transport should also close it. I will check
the code later.
Sent from my iPhone
> On Mar 16, 2014, at 2:16 PM, "carlo cancellieri [via ActiveMQ]"
> wrote:
>
> Art,
> Response is inline.
>
> > Hmm, what you describe sounds disturbing and counter to my exp
Art,
Response is inline.
> Hmm, what you describe sounds disturbing and counter to my experience.
>
> Opening a jira entry is the first step to getting any bug addressed.
> Attaching a self-contained junit that can reproduce the problem certainly
> helps a lot.
I'll ask to my society if I can all
Hmm, what you describe sounds disturbing and counter to my experience.
Opening a jira entry is the first step to getting any bug addressed.
Attaching a self-contained junit that can reproduce the problem certainly
helps a lot.
One question comes to mind - is a connection pool part of the setup?
Errata corridge:
Sorry, substitute 'Transaction' with 'Transport' in the previous mail.
Il 16/mar/2014 21:20 "carlo cancellieri"
ha scritto:
> Art,
> thanks for your prompt response. Finally I have found a workaround but I
> had to implement a wrapper of the ActiveMQConnectionFactory to handle
>
Art,
thanks for your prompt response. Finally I have found a workaround but I
had to implement a wrapper of the ActiveMQConnectionFactory to handle
Transport by my self.
Looking at the
org.apache.activemq.ActiveMQConnectionFactory.createActiveMQConnection(String,
String)
in the 5.10-SNAPSHOT and p
Ah, I was reading your message from my mailbox and didn't have the full
history.
Take a look at all the non-daemon threads, they are what keep a JVM from
terminating:
Thread [DestroyJavaVM] (Running)
Thread [pool-3-thread-1] (Running)
Thread [ActiveMQ Transport: tcp://CIO174/168.202.25.104:643
Hi art,
probably my first message (with thread stack dumped using eclipse remote
debug) is missing, I repeat the post here:
Hi all,
I'm having some problem during the Tomcat shutdown.
I'm using ActiveMQ-5.8 and my brokerURL are:
brokerURL=peer\://geoserver/tomcat1?soTimeout\=3000&transport.soTi
Try grabbing a thread dump with jstack, or the like, to see what threads are
still active.
Sent from my iPhone
> On Mar 15, 2014, at 7:35 PM, "carlo cancellieri [via ActiveMQ]"
> wrote:
>
> More:
>
> At tomcat shutdown I get: (note that all the brokers, connections and
> Transport are aut
More:
At tomcat shutdown I get: (note that all the brokers, connections and
Transport are automatically created by the PooledConnectionFactory with the
passed URL so they should be ideally closed with a close() on the
PooledConnectionFactory, right?)
SEVERE: The web application [/geoserver] creat
11 matches
Mail list logo
