[jira] [Created] (AMQ-4660) OutOfMemoryError in Web Console
Jan Wedel created AMQ-4660:
--
Summary: OutOfMemoryError in Web Console
Key: AMQ-4660
URL: https://issues.apache.org/jira/browse/AMQ-4660
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.8.0
Environment: Linux h1666427 2.6.32-042stab078.27 #1 SMP Mon Jul 1
20:48:07 MSK 2013 i686 athlon i386 GNU/Linux
Reporter: Jan Wedel
I have multiple queues (about 20), most of them are empty. One queue has 60
messages. When click on the queue in the web console to view the messages, I
get an error displayed after a few minutes:
{quote}
Error!
Exception occurred while processing this request, check the log for more
information!
{quote}
When I check the log, I get this huge stacktrace:
{quote}
2013-07-30 08:44:26,380 | WARN | /admin/browse.jsp |
org.eclipse.jetty.servlet.ServletHandler | qtp10279131-55
javax.servlet.jsp.JspException: java.lang.OutOfMemoryError: Java heap space
at
org.apache.jsp.tag.web.jms.persistent_tag.doTag(org.apache.jsp.tag.web.jms.persistent_tag:80)
at
org.apache.jsp.browse_jsp._jspx_meth_jms_persistent_0(org.apache.jsp.browse_jsp:222)
at org.apache.jsp.browse_jsp.access$2(org.apache.jsp.browse_jsp:210)
at
org.apache.jsp.browse_jsp$browse_jspHelper.invoke0(org.apache.jsp.browse_jsp:401)
at
org.apache.jsp.browse_jsp$browse_jspHelper.invoke(org.apache.jsp.browse_jsp:450)
at
org.apache.jsp.tag.web.jms.forEachMessage_tag.doTag(org.apache.jsp.tag.web.jms.forEachMessage_tag:89)
at
org.apache.jsp.browse_jsp._jspx_meth_jms_forEachMessage_0(org.apache.jsp.browse_jsp:170)
at org.apache.jsp.browse_jsp._jspService(org.apache.jsp.browse_jsp:100)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:109)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:389)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:486)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:380)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:652)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1329)
at
org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:83)
at
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1300)
at org.apache.activemq.web.SessionFilter.doFilter(SessionFilter.java:45)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1300)
at
org.apache.activemq.web.filter.ApplicationContextFilter.doFilter(ApplicationContextFilter.java:102)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1300)
at
com.opensymphony.sitemesh.webapp.SiteMeshFilter.obtainContent(SiteMeshFilter.java:129)
at
com.opensymphony.sitemesh.webapp.SiteMeshFilter.doFilter(SiteMeshFilter.java:77)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1300)
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:445)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:534)
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227)
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1038)
at
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:374)
at
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:189)
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:972)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
at
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:154)
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:534)
at
org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:154)
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
at org.eclipse.jetty.server.Server.handle(Server.java:363)
at
org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:483)
at
org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:920)
at
[jira] [Assigned] (AMQ-4656) Pending Queue Counter is incorrect when using durable topics
[
https://issues.apache.org/jira/browse/AMQ-4656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dejan Bosanac reassigned AMQ-4656:
--
Assignee: Dejan Bosanac
Pending Queue Counter is incorrect when using durable topics
Key: AMQ-4656
URL: https://issues.apache.org/jira/browse/AMQ-4656
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.8.0
Reporter: Timothy Bish
Assignee: Dejan Bosanac
Fix For: 5.9.0
Attachments: AMQ4656Test.java
When using a durable topics the Pending Queue Counter provides an incorrect
value for pending messages.
Steps to recreate
Set up the durable subscriber
{noformat}
ant consumer -Durl=tcp://localhost:61616 -Dtopic=true -Dsubject=MYSUB
-Ddurable=true -Dmax=2
{noformat}
Stop the subscriber
Send 20 persistent messages
{noformat}
ant producer -Ddurable=true -Durl=tcp://localhost:61616 -Dtopic=true
-Dsubject=MYSUB -Dmax=20
{noformat}
Consume 2 messages
{noformat}
ant consumer -Durl=tcp://localhost:61616 -Dtopic=true -Dsubject=MYSUB
-Ddurable=true -Dmax=2
{noformat}
View the counter stats.
The result is the following:
{noformat}
Pending Queue Size = 38
Dispatched Queue Size = 0
Dispatched Counter = 20
Enqueue Counter = 20
Dequeue Counter = 2
{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQNET-441) unable to create a connection using stomp
[
https://issues.apache.org/jira/browse/AMQNET-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13723674#comment-13723674
]
Timothy Bish commented on AMQNET-441:
-
{code}
Uri connecturi = new Uri(stomp:tcp://localhost:61613);
{code}
unable to create a connection using stomp
-
Key: AMQNET-441
URL: https://issues.apache.org/jira/browse/AMQNET-441
Project: ActiveMQ .Net
Issue Type: Bug
Components: ActiveMQ
Affects Versions: 1.6.0
Environment: ActiveMQ 5.8.0 and NMS API 1.6.0.3061
Reporter: Tamilmaran
Assignee: Jim Gomes
Fix For: 1.6.0
used the following code to connect with stomp but i am getting the error like
Error creating transport.
{code}
Uri connecturi = new Uri(activemq:stomp://localhost:61613);
IConnectionFactory factory = new NMSConnectionFactory(connecturi);
using (IConnection connection = factory.CreateConnection())
{code}
if i used code as below i am getting the error as No IConnectionFactory
implementation found for connection URI: stomp://localhost:61613/
{code}
Uri connecturi = new Uri(stomp://localhost:61613);
IConnectionFactory factory = new NMSConnectionFactory(connecturi);
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (AMQNET-441) unable to create a connection using stomp
[
https://issues.apache.org/jira/browse/AMQNET-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQNET-441.
---
Resolution: Not A Problem
If using the Stomp library then you use a URI of stomp:tcp..
unable to create a connection using stomp
-
Key: AMQNET-441
URL: https://issues.apache.org/jira/browse/AMQNET-441
Project: ActiveMQ .Net
Issue Type: Bug
Components: ActiveMQ
Affects Versions: 1.6.0
Environment: ActiveMQ 5.8.0 and NMS API 1.6.0.3061
Reporter: Tamilmaran
Assignee: Jim Gomes
used the following code to connect with stomp but i am getting the error like
Error creating transport.
{code}
Uri connecturi = new Uri(activemq:stomp://localhost:61613);
IConnectionFactory factory = new NMSConnectionFactory(connecturi);
using (IConnection connection = factory.CreateConnection())
{code}
if i used code as below i am getting the error as No IConnectionFactory
implementation found for connection URI: stomp://localhost:61613/
{code}
Uri connecturi = new Uri(stomp://localhost:61613);
IConnectionFactory factory = new NMSConnectionFactory(connecturi);
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQNET-441) unable to create a connection using stomp
[
https://issues.apache.org/jira/browse/AMQNET-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish updated AMQNET-441:
Fix Version/s: (was: 1.6.0)
unable to create a connection using stomp
-
Key: AMQNET-441
URL: https://issues.apache.org/jira/browse/AMQNET-441
Project: ActiveMQ .Net
Issue Type: Bug
Components: ActiveMQ
Affects Versions: 1.6.0
Environment: ActiveMQ 5.8.0 and NMS API 1.6.0.3061
Reporter: Tamilmaran
Assignee: Jim Gomes
used the following code to connect with stomp but i am getting the error like
Error creating transport.
{code}
Uri connecturi = new Uri(activemq:stomp://localhost:61613);
IConnectionFactory factory = new NMSConnectionFactory(connecturi);
using (IConnection connection = factory.CreateConnection())
{code}
if i used code as below i am getting the error as No IConnectionFactory
implementation found for connection URI: stomp://localhost:61613/
{code}
Uri connecturi = new Uri(stomp://localhost:61613);
IConnectionFactory factory = new NMSConnectionFactory(connecturi);
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-4660) OutOfMemoryError in Web Console
[
https://issues.apache.org/jira/browse/AMQ-4660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13723693#comment-13723693
]
Jan Wedel commented on AMQ-4660:
Hmm, the question is: Why does it happen with 60 messages? In issue AMQ-4595,
the had 1 messages. Right now, after some messages have been consumed,
there are 28 left, and these messages are displayed instantly.
However, I've checked the body size and each message contains about 20kB of XML
(don't ask my why, its not my code). But does browsing actually needs to
acquire the body for displaying a list of message ids?
And even if its been done, this would be 60*20b=1,4MB which should be fine when
running AMQ with 1GB of heap, shouldn't it?
Also, they were talking about the auditDeph, which is set to 2000 by default.
So this appears not to be the same issue at least from my outsider's point of
view.
Unfortunately, this is a live-system. I will try to deploy the dev version on
one of our development servers.
OutOfMemoryError in Web Console
---
Key: AMQ-4660
URL: https://issues.apache.org/jira/browse/AMQ-4660
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.8.0
Environment: Linux h1666427 2.6.32-042stab078.27 #1 SMP Mon Jul 1
20:48:07 MSK 2013 i686 athlon i386 GNU/Linux
Reporter: Jan Wedel
I have multiple queues (about 20), most of them are empty. One queue has 60
messages. When click on the queue in the web console to view the messages, I
get an error displayed after a few minutes:
{quote}
Error!
Exception occurred while processing this request, check the log for more
information!
{quote}
When I check the log, I get this huge stacktrace:
{quote}
2013-07-30 08:44:26,380 | WARN | /admin/browse.jsp |
org.eclipse.jetty.servlet.ServletHandler | qtp10279131-55
javax.servlet.jsp.JspException: java.lang.OutOfMemoryError: Java heap space
at
org.apache.jsp.tag.web.jms.persistent_tag.doTag(org.apache.jsp.tag.web.jms.persistent_tag:80)
at
org.apache.jsp.browse_jsp._jspx_meth_jms_persistent_0(org.apache.jsp.browse_jsp:222)
at org.apache.jsp.browse_jsp.access$2(org.apache.jsp.browse_jsp:210)
at
org.apache.jsp.browse_jsp$browse_jspHelper.invoke0(org.apache.jsp.browse_jsp:401)
at
org.apache.jsp.browse_jsp$browse_jspHelper.invoke(org.apache.jsp.browse_jsp:450)
at
org.apache.jsp.tag.web.jms.forEachMessage_tag.doTag(org.apache.jsp.tag.web.jms.forEachMessage_tag:89)
at
org.apache.jsp.browse_jsp._jspx_meth_jms_forEachMessage_0(org.apache.jsp.browse_jsp:170)
at
org.apache.jsp.browse_jsp._jspService(org.apache.jsp.browse_jsp:100)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:109)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:389)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:486)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:380)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:806)
at
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:652)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1329)
at
org.springframework.web.filter.RequestContextFilter.doFilterInternal(RequestContextFilter.java:83)
at
org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:76)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1300)
at
org.apache.activemq.web.SessionFilter.doFilter(SessionFilter.java:45)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1300)
at
org.apache.activemq.web.filter.ApplicationContextFilter.doFilter(ApplicationContextFilter.java:102)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1300)
at
com.opensymphony.sitemesh.webapp.SiteMeshFilter.obtainContent(SiteMeshFilter.java:129)
at
com.opensymphony.sitemesh.webapp.SiteMeshFilter.doFilter(SiteMeshFilter.java:77)
at
org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1300)
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:445)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:534)
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:227)
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1038)
[jira] [Commented] (AMQNET-441) unable to create a connection using stomp
[
https://issues.apache.org/jira/browse/AMQNET-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13723698#comment-13723698
]
Tamilmaran commented on AMQNET-441:
---
We tried that also already but it is not working..
unable to create a connection using stomp
-
Key: AMQNET-441
URL: https://issues.apache.org/jira/browse/AMQNET-441
Project: ActiveMQ .Net
Issue Type: Bug
Components: ActiveMQ
Affects Versions: 1.6.0
Environment: ActiveMQ 5.8.0 and NMS API 1.6.0.3061
Reporter: Tamilmaran
Assignee: Jim Gomes
used the following code to connect with stomp but i am getting the error like
Error creating transport.
{code}
Uri connecturi = new Uri(activemq:stomp://localhost:61613);
IConnectionFactory factory = new NMSConnectionFactory(connecturi);
using (IConnection connection = factory.CreateConnection())
{code}
if i used code as below i am getting the error as No IConnectionFactory
implementation found for connection URI: stomp://localhost:61613/
{code}
Uri connecturi = new Uri(stomp://localhost:61613);
IConnectionFactory factory = new NMSConnectionFactory(connecturi);
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQNET-441) unable to create a connection using stomp
[
https://issues.apache.org/jira/browse/AMQNET-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13723700#comment-13723700
]
Tamilmaran commented on AMQNET-441:
---
we are getting the following error
No IConnectionFactory implementation found for connection URI:
stomp:tcp://127.0.0.1:61613
unable to create a connection using stomp
-
Key: AMQNET-441
URL: https://issues.apache.org/jira/browse/AMQNET-441
Project: ActiveMQ .Net
Issue Type: Bug
Components: ActiveMQ
Affects Versions: 1.6.0
Environment: ActiveMQ 5.8.0 and NMS API 1.6.0.3061
Reporter: Tamilmaran
Assignee: Jim Gomes
used the following code to connect with stomp but i am getting the error like
Error creating transport.
{code}
Uri connecturi = new Uri(activemq:stomp://localhost:61613);
IConnectionFactory factory = new NMSConnectionFactory(connecturi);
using (IConnection connection = factory.CreateConnection())
{code}
if i used code as below i am getting the error as No IConnectionFactory
implementation found for connection URI: stomp://localhost:61613/
{code}
Uri connecturi = new Uri(stomp://localhost:61613);
IConnectionFactory factory = new NMSConnectionFactory(connecturi);
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (AMQNET-441) unable to create a connection using stomp
[
https://issues.apache.org/jira/browse/AMQNET-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamilmaran reopened AMQNET-441:
---
we are tried as you said like
{code}
Uri connecturi = new Uri(stomp:tcp://127.0.0.1:61613);
{code}
but we are getting the error like below
No IConnectionFactory implementation found for connection URI:
stomp:tcp://127.0.0.1:61613
unable to create a connection using stomp
-
Key: AMQNET-441
URL: https://issues.apache.org/jira/browse/AMQNET-441
Project: ActiveMQ .Net
Issue Type: Bug
Components: ActiveMQ
Affects Versions: 1.6.0
Environment: ActiveMQ 5.8.0 and NMS API 1.6.0.3061
Reporter: Tamilmaran
Assignee: Jim Gomes
used the following code to connect with stomp but i am getting the error like
Error creating transport.
{code}
Uri connecturi = new Uri(activemq:stomp://localhost:61613);
IConnectionFactory factory = new NMSConnectionFactory(connecturi);
using (IConnection connection = factory.CreateConnection())
{code}
if i used code as below i am getting the error as No IConnectionFactory
implementation found for connection URI: stomp://localhost:61613/
{code}
Uri connecturi = new Uri(stomp://localhost:61613);
IConnectionFactory factory = new NMSConnectionFactory(connecturi);
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Subscriber connections not Released by ActiveMQ
Please use the users-list for these kinds of questions. dev-list is for discussing development on activemq. Your best bet is to create a test that shows this error somehow and attach it to a JIRA. On Tue, Jul 30, 2013 at 2:26 AM, Raghunath ragunath.ch...@sigma-systems.com wrote: ActiveMQ Version 5.8 We have a Failover setup where producer consumer connect to ActiveMQ. We have noticed that when the subscriber is stopped, the subscriber connections are not Released by AMQ. The issue is intermittent but when it happens the problem stays until we do the following: • When we stop ActiveMQ, the connections to subscribers are Released. • Workaround is to Restart ActiveMQ and then delete the Subscribers. This is the configuration used in activemq: transportConnector name=openwire uri=tcp:// 0.0.0.0:61616?wireFormat.maxInactivityDuration=-1amp;wireFormat.cacheSize=2048amp;wireFormat.socketBufferSize=131072 discoveryUri=multicast://default/ /transportConnectors -- View this message in context: http://activemq.2283324.n4.nabble.com/Subscriber-connections-not-Released-by-ActiveMQ-tp4669854.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com. -- *Christian Posta* http://www.christianposta.com/blog twitter: @christianposta
[jira] [Commented] (AMQNET-441) unable to create a connection using stomp
[
https://issues.apache.org/jira/browse/AMQNET-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13723840#comment-13723840
]
Timothy Bish commented on AMQNET-441:
-
The latest version of the NMS Stomp client is v1.5.3, if you have something
that's 1.6.0 then you have the wrong thing.
http://activemq.apache.org/nms/apachenmsstomp-v153.html
unable to create a connection using stomp
-
Key: AMQNET-441
URL: https://issues.apache.org/jira/browse/AMQNET-441
Project: ActiveMQ .Net
Issue Type: Bug
Components: ActiveMQ
Affects Versions: 1.6.0
Environment: ActiveMQ 5.8.0 and NMS API 1.6.0.3061
Reporter: Tamilmaran
Assignee: Jim Gomes
used the following code to connect with stomp but i am getting the error like
Error creating transport.
{code}
Uri connecturi = new Uri(activemq:stomp://localhost:61613);
IConnectionFactory factory = new NMSConnectionFactory(connecturi);
using (IConnection connection = factory.CreateConnection())
{code}
if i used code as below i am getting the error as No IConnectionFactory
implementation found for connection URI: stomp://localhost:61613/
{code}
Uri connecturi = new Uri(stomp://localhost:61613);
IConnectionFactory factory = new NMSConnectionFactory(connecturi);
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (AMQ-4661) Using ActiveMQ 5.8.0 with grails 2.x: Error SLF4J: Class path contains multiple SLF4J bindings
Alex Freller created AMQ-4661:
-
Summary: Using ActiveMQ 5.8.0 with grails 2.x: Error SLF4J: Class
path contains multiple SLF4J bindings
Key: AMQ-4661
URL: https://issues.apache.org/jira/browse/AMQ-4661
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.8.0
Environment: OSX 10.8 / JDK 1.6.0_51, ActiveMQ 5.8.0, grails 2.2.1
Reporter: Alex Freller
Priority: Minor
Starting up the grails (2.2.1) application, I get the following errors:
| Error SLF4J: Class path contains multiple SLF4J bindings.
| Error SLF4J: Found binding in
[jar:file:/Users/userName/.grails/ivy-cache/org.grails/grails-plugin-log4j/jars/grails-plugin-log4j-2.2.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
| Error SLF4J: Found binding in
[jar:file:/Users/userName/.grails/ivy-cache/org.apache.activemq/activemq-all/jars/activemq-all-5.8.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
BuildConfig:
compile('org.apache.activemq:activemq-all:5.8.0') {
excludes spring-context
}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AMQ-4643) JDBCPersistence DB stopped during message send with JDBCIOExceptionHandler configured; IOException/SQLException is sent back (sometimes) to the client before the transport
[
https://issues.apache.org/jira/browse/AMQ-4643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-4643.
-
Resolution: Fixed
Fix Version/s: 5.9.0
Assignee: Gary Tully
fix in http://svn.apache.org/viewvc?view=revisionrevision=r1508602
thanks for the test.
The ft/JDBCRestart* tests had workarounds for the non deterministic behaviour
that are now removed.
JDBCPersistence DB stopped during message send with JDBCIOExceptionHandler
configured; IOException/SQLException is sent back (sometimes) to the client
before the transport connector is shutdown
-
Key: AMQ-4643
URL: https://issues.apache.org/jira/browse/AMQ-4643
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.8.0
Environment: - tested on trunk
Reporter: Pat Fox
Assignee: Gary Tully
Fix For: 5.9.0
Attachments: AMQ4643Test.java
This related to AMQ-4636 JIRA for gtully's second point in comment
https://issues.apache.org/jira/browse/AMQ-4636?focusedCommentId=13712196page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13712196
Scenario:
- Producer sending persistent message (no transaction)
- JDBCIOExceptionHandler is configured
- the underlying DB is shutdown during message send
Result:
One of two outcomes can happen:
1) the broker sends the an IOException/SQLException wrapped in a JMSException
(below) back to the client and then shuts down the transport connectors.
2) the broker shuts down the transport connector when the
IOException/SQLException is encountered.
Expected behavior:
As the JDBCIOHandler is configured which is handling the SQL exception, it
would be good if the transport connectors were shutdown and no
IOException/SQLException is reported to producer.
{code}
2013-07-19 15:22:05,436 [main ] - ERROR
pDBDuringProducerSendTopicTest - unexpected exception caught
javax.jms.JMSException: Database apos;target/derbydb_15apos; not found.
at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54)
at
org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1391)
at
org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1319)
at org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1809)
at
org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:289)
at
org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:224)
at
org.apache.activemq.ActiveMQMessageProducerSupport.send(ActiveMQMessageProducerSupport.java:241)
at
org.apache.activemq.store.jdbc.StopDBDuringProducerSendTopicTest.sendMessage(StopDBDuringProducerSendTopicTest.java:150)
at
org.apache.activemq.store.jdbc.StopDBDuringProducerSendTopicTest.testProducerWithDBShutdown(StopDBDuringProducerSendTopicTest.java:127)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at junit.framework.TestCase.runTest(TestCase.java:176)
at junit.framework.TestCase.runBare(TestCase.java:141)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
at
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
[jira] [Commented] (AMQ-4643) JDBCPersistence DB stopped during message send with JDBCIOExceptionHandler configured; IOException/SQLException is sent back (sometimes) to the client before the transpor
[
https://issues.apache.org/jira/browse/AMQ-4643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13724363#comment-13724363
]
Gary Tully commented on AMQ-4643:
-
the fix was to introduce a SuppressReplyException that an IOExceptionHandler
can use it to mask the current exception, it will be trapped by the transport
so that a reply will not be propagated, the client will see a socket.close in
place.
To get immediate notification of store failure on a client, the
DefaultIOExceptionHandler needs to be configured to ingnoreAllErrors{code}
broker ...
ioExceptionHandler
defaultIOExceptionHandler ignoreAllErrors=true /
/ioExceptionHandler
...{code}
JDBCPersistence DB stopped during message send with JDBCIOExceptionHandler
configured; IOException/SQLException is sent back (sometimes) to the client
before the transport connector is shutdown
-
Key: AMQ-4643
URL: https://issues.apache.org/jira/browse/AMQ-4643
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.8.0
Environment: - tested on trunk
Reporter: Pat Fox
Assignee: Gary Tully
Fix For: 5.9.0
Attachments: AMQ4643Test.java
This related to AMQ-4636 JIRA for gtully's second point in comment
https://issues.apache.org/jira/browse/AMQ-4636?focusedCommentId=13712196page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13712196
Scenario:
- Producer sending persistent message (no transaction)
- JDBCIOExceptionHandler is configured
- the underlying DB is shutdown during message send
Result:
One of two outcomes can happen:
1) the broker sends the an IOException/SQLException wrapped in a JMSException
(below) back to the client and then shuts down the transport connectors.
2) the broker shuts down the transport connector when the
IOException/SQLException is encountered.
Expected behavior:
As the JDBCIOHandler is configured which is handling the SQL exception, it
would be good if the transport connectors were shutdown and no
IOException/SQLException is reported to producer.
{code}
2013-07-19 15:22:05,436 [main ] - ERROR
pDBDuringProducerSendTopicTest - unexpected exception caught
javax.jms.JMSException: Database apos;target/derbydb_15apos; not found.
at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:54)
at
org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1391)
at
org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1319)
at org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1809)
at
org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:289)
at
org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:224)
at
org.apache.activemq.ActiveMQMessageProducerSupport.send(ActiveMQMessageProducerSupport.java:241)
at
org.apache.activemq.store.jdbc.StopDBDuringProducerSendTopicTest.sendMessage(StopDBDuringProducerSendTopicTest.java:150)
at
org.apache.activemq.store.jdbc.StopDBDuringProducerSendTopicTest.testProducerWithDBShutdown(StopDBDuringProducerSendTopicTest.java:127)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at junit.framework.TestCase.runTest(TestCase.java:176)
at junit.framework.TestCase.runBare(TestCase.java:141)
at junit.framework.TestResult$1.protect(TestResult.java:122)
at junit.framework.TestResult.runProtected(TestResult.java:142)
at junit.framework.TestResult.run(TestResult.java:125)
at junit.framework.TestCase.run(TestCase.java:129)
at junit.framework.TestSuite.runTest(TestSuite.java:255)
at junit.framework.TestSuite.run(TestSuite.java:250)
at
org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
at
org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
[jira] [Resolved] (AMQ-4636) JDBCPersistence DB stopped during message send; JMSException is sent back to client rather than shutting down connection
[
https://issues.apache.org/jira/browse/AMQ-4636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-4636.
-
Resolution: Fixed
Fix Version/s: 5.9.0
This is fixed as a byproduct of https://issues.apache.org/jira/browse/AMQ-4643
The TransactionContext.close now correctly delegates to the IOExceptionHandler
which handles the transaction commit/rollback failure cases
JDBCPersistence DB stopped during message send; JMSException is sent back to
client rather than shutting down connection
Key: AMQ-4636
URL: https://issues.apache.org/jira/browse/AMQ-4636
Project: ActiveMQ
Issue Type: Bug
Affects Versions: 5.8.0
Environment: tested on trunk.
Reporter: Pat Fox
Assignee: Gary Tully
Fix For: 5.9.0
Attachments: AMQ4636Test.java
Broker is configured to use JDBCIOExceptionHandler.
When the JDBCPersistence DB is stopped during a message send the broker
returns the following javax.jms.JMSException back to the client rather than
closing the connection.
This results in the client having to deal with the exception instead of the
failover transport having to deal with a connection loss and redeliver the
message. Failover transport and transport connection loss seems to be the
approach used when other SQL exceptions are thrown.
{code}
Exception received on client side:
javax.jms.JMSException: ORA-01089: immediate shutdown in progress - no
operation
s are permitted
at
org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSuppo
rt.java:54)
at
org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnect
ion.java:1391)
at
org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnect
ion.java:1319)
at org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1798)
at
org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProdu
cer.java:289)
at
org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProdu
cer.java:224)
at
org.apache.activemq.ActiveMQMessageProducerSupport.send(ActiveMQMessa
geProducerSupport.java:241)
at com.acme.MyPublisher.doIt(MyPublisher.java:50)
at com.acme.MyPublisher.main(MyPublisher.java:26)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
at java.lang.Thread.run(Thread.java:662)
Caused by: java.io.IOException: ORA-01089: immediate shutdown in progress -
no o
perations are permitted
at
org.apache.activemq.util.IOExceptionSupport.create(IOExceptionSupport
.java:45)
at
org.apache.activemq.store.jdbc.TransactionContext.close(TransactionCo
ntext.java:141)
at
org.apache.activemq.store.jdbc.JDBCMessageStore.addMessage(JDBCMessag
eStore.java:129)
at
org.apache.activemq.store.memory.MemoryTransactionStore.addMessage(Me
moryTransactionStore.java:327)
at
org.apache.activemq.store.memory.MemoryTransactionStore$2.asyncAddTop
icMessage(MemoryTransactionStore.java:190)
at
org.apache.activemq.broker.region.Topic.doMessageSend(Topic.java:471)
at org.apache.activemq.broker.region.Topic.send(Topic.java:435)
at
org.apache.activemq.broker.region.AbstractRegion.send(AbstractRegion.
java:406)
at
org.apache.activemq.broker.region.RegionBroker.send(RegionBroker.java
:392)
at
org.apache.activemq.broker.jmx.ManagedRegionBroker.send(ManagedRegion
Broker.java:282)
at org.apache.activemq.broker.BrokerFilter.send(BrokerFilter.java:129)
at
org.apache.activemq.broker.CompositeDestinationBroker.send(CompositeD
estinationBroker.java:96)
at
org.apache.activemq.broker.TransactionBroker.send(TransactionBroker.j
ava:317)
at
org.apache.activemq.broker.MutableBrokerFilter.send(MutableBrokerFilt
er.java:135)
at
org.apache.activemq.broker.TransportConnection.processMessage(Transpo
rtConnection.java:499)
at
org.apache.activemq.command.ActiveMQMessage.visit(ActiveMQMessage.jav
a:749)
at
org.apache.activemq.broker.TransportConnection.service(TransportConne
ction.java:329)
at
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportC
onnection.java:184)
at
org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport
.java:50)
at
Build failed in Jenkins: ActiveMQ » ActiveMQ :: STOMP Protocol #1346
See https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-stomp/1346/ -- [01:05:51] Jul 31, 2013 1:05:51 AM org.apache.maven.cli.event.ExecutionEventLogger projectStarted INFO: Jul 31, 2013 1:05:51 AM org.apache.maven.cli.event.ExecutionEventLogger projectStarted INFO: Jul 31, 2013 1:05:51 AM org.apache.maven.cli.event.ExecutionEventLogger projectStarted INFO: Building ActiveMQ :: STOMP Protocol 5.9-SNAPSHOT Jul 31, 2013 1:05:51 AM org.apache.maven.cli.event.ExecutionEventLogger projectStarted INFO: Jul 31, 2013 1:05:51 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Jul 31, 2013 1:05:51 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-clean-plugin:2.5:clean (default-clean) @ activemq-stomp --- Jul 31, 2013 1:05:52 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Jul 31, 2013 1:05:52 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-enforcer-plugin:1.0.1:enforce (default) @ activemq-stomp --- Jul 31, 2013 1:05:52 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Jul 31, 2013 1:05:52 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-consolets-plugin:1.30:install (default) @ activemq-stomp --- Jul 31, 2013 1:05:52 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Jul 31, 2013 1:05:52 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ activemq-stomp --- Jul 31, 2013 1:05:52 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Jul 31, 2013 1:05:52 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-remote-resources-plugin:1.3:process (default) @ activemq-stomp --- Jul 31, 2013 1:05:52 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Jul 31, 2013 1:05:52 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-resources-plugin:2.5:resources (default-resources) @ activemq-stomp --- [01:05:52] [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 14 resources [INFO] skip non existing resourceDirectory https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-stomp/ws/src/main/filtered-resources [INFO] Copying 3 resources Jul 31, 2013 1:05:52 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Jul 31, 2013 1:05:52 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-compiler-plugin:2.5.1:compile (default-compile) @ activemq-stomp --- [INFO] Compiling 24 source files to https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-stomp/ws/target/classes Jul 31, 2013 1:05:52 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Jul 31, 2013 1:05:52 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-resources-plugin:2.5:testResources (default-testResources) @ activemq-stomp --- [01:05:52] [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 6 resources [INFO] Copying 3 resources Jul 31, 2013 1:05:52 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Jul 31, 2013 1:05:52 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-compiler-plugin:2.5.1:testCompile (default-testCompile) @ activemq-stomp --- [INFO] Compiling 30 source files to https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-stomp/ws/target/test-classes Jul 31, 2013 1:05:53 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: Jul 31, 2013 1:05:53 AM org.apache.maven.cli.event.ExecutionEventLogger mojoStarted INFO: --- maven-surefire-plugin:2.10:test (default-test) @ activemq-stomp --- [INFO] Surefire report directory: https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-stomp/ws/target/surefire-reports [01:05:53] [01:05:53] --- [01:05:53] T E S T S [01:05:53] --- [01:05:53] [01:05:53] --- [01:05:53] T E S T S [01:05:53] --- [01:05:53] Running org.apache.activemq.transport.stomp.ConnectTest [01:06:28] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 35.605 sec [01:06:29] Running org.apache.activemq.transport.stomp.Stomp11NIOSSLTest [01:08:28] Tests run: 27, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 119.03 sec [01:08:28] Running org.apache.activemq.transport.stomp.Stomp11NIOTest [01:10:25] Tests run:
Build failed in Jenkins: ActiveMQ #1346
See https://builds.apache.org/job/ActiveMQ/1346/changes Changes: [gtully] https://issues.apache.org/jira/browse/AMQ-4643 - ensure handled ioexceptions are not propagated back to client when broker or transports are shutdown. additional tests existing tests refactored to reflect new determinism. IOException handler now throws SuppressReplyException which is trapped by the transport connector. If store exception need to be processes by the client, for immediate response rather than failover reconnect, then the ioexception handler should be configured to ignoreAllErrors -- [...truncated 7726 lines...] INFO: Jul 31, 2013 2:12:39 AM org.apache.maven.cli.event.ExecutionEventLogger projectSkipped INFO: Skipping ActiveMQ :: Assembly Jul 31, 2013 2:12:39 AM org.apache.maven.cli.event.ExecutionEventLogger projectSkipped INFO: This project has been banned from the build due to previous failures. Jul 31, 2013 2:12:39 AM org.apache.maven.cli.event.ExecutionEventLogger projectSkipped INFO: Jul 31, 2013 2:12:39 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Jul 31, 2013 2:12:39 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Reactor Summary: Jul 31, 2013 2:12:39 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: Jul 31, 2013 2:12:39 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: ActiveMQ .. SUCCESS [20.289s] Jul 31, 2013 2:12:39 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: ActiveMQ :: Openwire Generator SUCCESS [4.223s] Jul 31, 2013 2:12:39 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: ActiveMQ :: Client SUCCESS [1:53.288s] Jul 31, 2013 2:12:39 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: ActiveMQ :: Openwire Legacy Support ... SUCCESS [2.822s] Jul 31, 2013 2:12:39 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: ActiveMQ :: JAAS .. SUCCESS [38.736s] Jul 31, 2013 2:12:39 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: ActiveMQ :: Broker SUCCESS [57.285s] Jul 31, 2013 2:12:39 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: ActiveMQ :: KahaDB Store .. SUCCESS [4:40.929s] Jul 31, 2013 2:12:39 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: ActiveMQ :: STOMP Protocol FAILURE [46:57.648s] Jul 31, 2013 2:12:39 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: ActiveMQ :: MQTT Protocol . SUCCESS [7:57.288s] Jul 31, 2013 2:12:39 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: ActiveMQ :: JDBC Store SUCCESS [3.257s] Jul 31, 2013 2:12:39 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: ActiveMQ :: LevelDB Store . SUCCESS [6:49.344s] Jul 31, 2013 2:12:39 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: ActiveMQ :: RA SUCCESS [2:36.341s] Jul 31, 2013 2:12:39 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: ActiveMQ :: Pool .. SUCCESS [1:49.819s] Jul 31, 2013 2:12:39 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: ActiveMQ :: Spring SKIPPED Jul 31, 2013 2:12:39 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: ActiveMQ :: AMQP .. SKIPPED Jul 31, 2013 2:12:39 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: ActiveMQ :: Console ... SUCCESS [4.465s] Jul 31, 2013 2:12:39 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: ActiveMQ :: Unit Tests SKIPPED Jul 31, 2013 2:12:39 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: ActiveMQ :: Camel . SKIPPED Jul 31, 2013 2:12:39 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: ActiveMQ :: HTTP Protocol Support . SKIPPED Jul 31, 2013 2:12:39 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: ActiveMQ :: All JAR bundle SKIPPED Jul 31, 2013 2:12:39 AM org.apache.maven.cli.event.ExecutionEventLogger logReactorSummary INFO: ActiveMQ :: File Server
