Build failed in Jenkins: ActiveMQ » ActiveMQ :: Unit Tests #1455

[Apache Jenkins Server]

See 


Changes:

[tabish121] https://issues.apache.org/jira/browse/AMQ-5213

[tabish121] Convert to JUnit 4 test and add a timeout, also remove the tcp 
transport

--
[...truncated 2466 lines...]
[06:21:48] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
21.982 sec - in 
org.apache.activemq.usecases.ThreeBrokerVirtualTopicNetworkLevelDBTest
[06:21:49] Running 
org.apache.activemq.usecases.ThreeBrokerVirtualTopicNetworkTest
[06:22:14] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
24.578 sec - in org.apache.activemq.usecases.ThreeBrokerVirtualTopicNetworkTest
[06:22:14] Running org.apache.activemq.usecases.TopicDurableConnectStatsTest
[06:22:16] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
2.509 sec - in org.apache.activemq.usecases.TopicDurableConnectStatsTest
[06:22:17] Running org.apache.activemq.usecases.TopicProducerFlowControlTest
[06:23:09] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
51.755 sec - in org.apache.activemq.usecases.TopicProducerFlowControlTest
[06:23:09] Running org.apache.activemq.usecases.TopicRedeliverTest
[06:23:34] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
25.189 sec - in org.apache.activemq.usecases.TopicRedeliverTest
[06:23:35] Running org.apache.activemq.usecases.TopicReplicationTest
[06:23:41] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
5.974 sec - in org.apache.activemq.usecases.TopicReplicationTest
[06:23:41] Running 
org.apache.activemq.usecases.TopicSubscriptionSlowConsumerTest
[06:23:43] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.527 sec - in org.apache.activemq.usecases.TopicSubscriptionSlowConsumerTest
[06:23:44] Running 
org.apache.activemq.usecases.TopicSubscriptionZeroPrefetchTest
[06:23:46] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 2.22 
sec - in org.apache.activemq.usecases.TopicSubscriptionZeroPrefetchTest
[06:23:46] Running org.apache.activemq.usecases.TransactionRollbackOrderTest
[06:23:48] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
2.013 sec - in org.apache.activemq.usecases.TransactionRollbackOrderTest
[06:23:49] Running org.apache.activemq.usecases.TransactionTest
[06:23:50] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
1.009 sec - in org.apache.activemq.usecases.TransactionTest
[06:23:50] Running org.apache.activemq.usecases.TransientQueueRedeliverTest
[06:24:16] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
25.239 sec - in org.apache.activemq.usecases.TransientQueueRedeliverTest
[06:24:16] Running 
org.apache.activemq.usecases.TwoBrokerMessageNotSentToRemoteWhenNoConsumerTest
[06:24:28] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
11.574 sec - in 
org.apache.activemq.usecases.TwoBrokerMessageNotSentToRemoteWhenNoConsumerTest
[06:24:28] Running 
org.apache.activemq.usecases.TwoBrokerNetworkConnectorWildcardDynamicallyIncludedDestinationTest
[06:25:07] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
39.356 sec - in 
org.apache.activemq.usecases.TwoBrokerNetworkConnectorWildcardDynamicallyIncludedDestinationTest
[06:25:08] Running 
org.apache.activemq.usecases.TwoBrokerNetworkConnectorWildcardStaticallyIncludedDestinationTest
[06:30:08] Running org.apache.activemq.usecases.TwoBrokerNetworkLoadBalanceTest
[06:30:13] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
4.215 sec - in org.apache.activemq.usecases.TwoBrokerNetworkLoadBalanceTest
[06:30:13] Running 
org.apache.activemq.usecases.TwoBrokerQueueClientsReconnectTest
[06:31:07] Tests run: 11, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
54.465 sec - in org.apache.activemq.usecases.TwoBrokerQueueClientsReconnectTest
[06:31:08] Running org.apache.activemq.usecases.TwoBrokerQueueSendReceiveTest
[06:31:22] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
13.559 sec - in org.apache.activemq.usecases.TwoBrokerQueueSendReceiveTest
[06:31:22] Running org.apache.activemq.usecases.TwoBrokerTempQueueAdvisoryTest
[06:32:03] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
41.342 sec - in org.apache.activemq.usecases.TwoBrokerTempQueueAdvisoryTest
[06:32:04] Running 
org.apache.activemq.usecases.TwoBrokerTopicSendReceiveLotsOfMessagesUsingTcpTest
[06:32:13] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
9.338 sec - in 
org.apache.activemq.usecases.TwoBrokerTopicSendReceiveLotsOfMessagesUsingTcpTest
[06:32:14] Running org.apache.activemq.usecases.TwoBrokerTopicSendReceiveTest
[06:32:22] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
7.978 sec - in org.apache.activemq.usecases.TwoBrokerTopicSendReceiveTest
[06:32:22] Running 
org.apache.activemq.usecases.TwoBrokerTopicSendReceiveUsingJavaConfigurationTest
[06:32:29] Tests run: 1, Failures: 0, Erro

Build failed in Jenkins: ActiveMQ #1455

[Apache Jenkins Server]

See 

Changes:

[tabish121] https://issues.apache.org/jira/browse/AMQ-5213

[tabish121] https://issues.apache.org/jira/browse/AMQ-5214

[tabish121] Convert to JUnit 4 test and add a timeout, also remove the tcp 
transport

--
[...truncated 4741 lines...]
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 hudson.maven.Maven3Builder.call(Maven3Builder.java:134)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:69)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:328)
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.xmlpull.v1.XmlPullParserException: unexpected type 
(position:END_DOCUMENT null@3:1 in java.io.InputStreamReader@2ff661) 
at org.kxml2.io.KXmlParser.exception(Unknown Source)
at org.kxml2.io.KXmlParser.nextTag(Unknown Source)
at 
org.apache.felix.bundlerepository.impl.PullParser.parseRepository(PullParser.java:43)
at 
org.apache.felix.bundlerepository.impl.DataModelHelperImpl.repository(DataModelHelperImpl.java:147)
at 
org.apache.felix.bundlerepository.impl.DataModelHelperImpl.repository(DataModelHelperImpl.java:118)
at 
org.apache.felix.obrplugin.ObrUpdate.parseRepositoryXml(ObrUpdate.java:316)
... 34 more
[06:43:34] [INFO]   
  
[INFO] 
[INFO] Skipping ActiveMQ :: Web Demo
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: Web Console
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: Karaf Integration Tests
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: Integration Test :: Spring 3.1
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping ActiveMQ :: Assembly
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] ActiveMQ .. SUCCESS [32.831s]
[INFO] ActiveMQ :: Openwire Generator  SUCCESS [6.365s]
[INFO] ActiveMQ :: Client  SUCCESS [2:00.228s]
[INFO] ActiveMQ :: Openwire Legacy Support ... SUCCESS [3.468s]
[INFO] ActiveMQ :: JAAS .. SUCCESS [36.896s]
[INFO] ActiveMQ :: Broker  SUCCESS [1:26.950s]
[INFO] ActiveMQ :: KahaDB Store .. SUCCESS [1:48.450s]
[INFO] ActiveMQ :: STOMP Protocol  SUCCESS [24:15.167s]
[INFO] ActiveMQ :: MQTT Protocol . SUCCESS [15:21.491s]
[INFO] ActiveMQ :: JDBC Store  SUCCESS [3.448s]
[INFO] ActiveMQ :: LevelDB Store . SUCCESS [3:50.910s]
[INFO] ActiveMQ :: Generic JMS Pool .

[jira] [Created] (AMQ-5215) org.apache.activemq.thread.PooledTaskRunner.wakeup() doesn't handle errors

[Tapan Jaggi (JIRA)]

Tapan Jaggi created AMQ-5215:


 Summary: org.apache.activemq.thread.PooledTaskRunner.wakeup() 
doesn't handle errors
 Key: AMQ-5215
 URL: https://issues.apache.org/jira/browse/AMQ-5215
 Project: ActiveMQ
  Issue Type: Improvement
  Components: activemq-pool
Affects Versions: 5.x
 Environment: SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 3

Reporter: Tapan Jaggi
Priority: Critical
 Fix For: NEEDS_REVIEW


We were getting below error in logs only once, but once this error comes 
OnMessage was not getting called in my listener class. We found that in 
org.apache.activemq.thread.PooledTaskRunner.wakeup() , if some Error is thrown 
on line "executor.execute(runable)", like the one below, no further messages 
will be processed by the PooledTaskRunner.wakeup() since the flag queued will 
be set to true and 

if (queued || shutdown) {
return;
}

will make any future call to be returned without being processed.

14:26:04,676 ERROR [stderr] (ActiveMQ Session Task-14) Exception in thread 
"ActiveMQ Session Task-14" java.lang.OutOfMemoryError: unable to create new 
native thread
14:26:04,677 ERROR [stderr] (ActiveMQ Session Task-14)  at 
java.lang.Thread.start0(Native Method)
14:26:04,677 ERROR [stderr] (ActiveMQ Session Task-14)  at 
java.lang.Thread.start(Thread.java:691)
14:26:04,677 ERROR [stderr] (ActiveMQ Session Task-14)  at 
java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:943)
14:26:04,677 ERROR [stderr] (ActiveMQ Session Task-14)  at 
java.util.concurrent.ThreadPoolExecutor.processWorkerExit(ThreadPoolExecutor.java:992)
14:26:04,677 ERROR [stderr] (ActiveMQ Session Task-14)  at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
14:26:04,677 ERROR [stderr] (ActiveMQ Session Task-14)  at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
14:26:04,678 ERROR [stderr] (ActiveMQ Session Task-14)  at 
java.lang.Thread.run(Thread.java:722)

The issue can be reproduced by injecting java.lang.Error after line queued = 
true is executed.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (AMQ-5202) Default cursor exceeds allocated memory on broker restart

[Ben O'Day (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-5202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019575#comment-14019575
 ] 

Ben O'Day commented on AMQ-5202:


we were able to deal with this issue by setting a per queue memoryLimit as 
follows:


that said, if you have a sufficient number of queues where your  X 
 approaches the high water mark (70% of memUsage), then I 
suspect you'll run into the issue again...

> Default cursor exceeds allocated memory on broker restart
> -
>
> Key: AMQ-5202
> URL: https://issues.apache.org/jira/browse/AMQ-5202
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 5.9.0, 5.9.1
> Environment: Linux, OSX
>Reporter: Jakub Korab
>
> This seems to be related to solution that was implemented in AMQ-4495.
> Background:
> Publishing to queue:one at a high rate (loop, 10 producers), no consumers
> Publishing to queue:two at a low rate (2 msg/s), 1 consumer
> When using a fresh broker (no data directory) with LevelDB/KahaDB:
> Memory usage + cursor usage rise together on queue:one until they hit 69%; 
> this corresponds to disk usage of 90mb (69% of tempUsage - under 70% default 
> memory watermark for the cursor);
> queue:one keeps accepting messages.
> queue:two keeps accepting messages, and handing them off to the consumer
> This is reached when ~1 * 4kb messages are sent. All OK so far.
> Issue:
> Restart the broker.
> Memory usage + cursor usage rise together very slowly on queue:one until they 
> hit 70% (default policyEntry@cursorMemoryHighWaterMark)
> queue:one keeps accepting messages.
> queue:two keeps accepting messages, but _stops handing them off to the 
> consumer_
> It doesn't matter whether the number of messages in the store is under or 
> over the cursor watermark when the broker is restarted - the cursor usage 
> hits the limit and the messages stop flowing.
> Consuming some messages from queue:one at this point will free up space up on 
> the cursor, and messages start flowing through to the queue:two consumers. 
> The cursor will eventually hit the watermark again and the consumers will 
> again block, so it is not a self-healing issue.
> Deleting the queues does not change that situation, and neither consumers on 
> queue:one nor queue:two will receive messages. The cursor seems to keep a 
> handle on the old queue:one's reference.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Commented] (AMQ-5188) AMQ broker throws OutOfMemoryError even when global flow-control memoryUsage limit is imposed

[Ben O'Day (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-5188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019570#comment-14019570
 ] 

Ben O'Day commented on AMQ-5188:


we had a similar issue and were able to mitigate it by setting a per queue 
memory limit...that said, we have flow control disabled as well, so the 
scenario might be a bit different...

 

> AMQ broker throws OutOfMemoryError even when global flow-control memoryUsage 
> limit is imposed
> -
>
> Key: AMQ-5188
> URL: https://issues.apache.org/jira/browse/AMQ-5188
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 5.8.0
> Environment: AMQ 5.8.0 broker running on 64-bit Linux 
> AMQP Qpid (.26) JMS producers running on 64-bin Linux
>Reporter: Michael Samson
> Attachments: AMQ_heap1.png, AMQ_heap2.png, 
> QpidProducerAMQOutOfMemory.java, activemq-5.10.xml, activemq.xml, 
> qpid-producer.tar
>
>
> * 5.8.0 broker was configured with persistence=false and a global 
> 
> * 5.8.0 broker JVM memory was set to default of 1G
> * No active consumers
> * 10 Qpid (version .26) AMQP producers sent messages to 10 broker queues 
> until flow control was reached
> * Over time the AMQP connections/producers were closed and recreated and they 
> reattempted to send messages.  As this cycle continues, eventually ActiveMQ 
> threw OutOfMemoryErrors.
> I grabbed a heap dump and ActiveMQTextMessages consumed 874M of the heap.  
> Taking a closer look, it appears that each 
> org.apache.activemq.broker.region.Queue's messagesWaitingForSpace map grows 
> unbounded and causes the OutOfMemory.
> I will attach a sample maven program that reproduces the problem along with 
> my activemq configuration, heap screenshots, etc.
> Are their any workarounds to this issue?  It is a use case for our customers 
> if their queue consumers die for an extended period of time.
>  



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (AMQ-5211) ActiveMQDestination.createDestination() should prevent empty destination name

[Ben O'Day (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMQ-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ben O'Day updated AMQ-5211:
---

Attachment: AMQ-5211.patch

> ActiveMQDestination.createDestination() should prevent empty destination name
> -
>
> Key: AMQ-5211
> URL: https://issues.apache.org/jira/browse/AMQ-5211
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.9.0
>Reporter: Ben O'Day
>Priority: Minor
> Attachments: AMQ-5211.patch
>
>
> currently you can call ActiveMQDestination 
> createDestination("",ActiveMQDestination.QUEUE_TYPE) to create a queue with 
> no name.  
> while this doesn't seem to be an issue at first...if you are using mKahadb, 
> ActiveMQ will fail to restart after this queue/store directory are created.
> see this post: 
> http://activemq.2283324.n4.nabble.com/mkahadb-Failed-to-start-per-destination-persistence-adapter-for-destination-td4678754.html#a4679848
> the web console already prevents this, we should prevent this from other 
> entry points to this API (QueueView.moveMessagesTo() from JMX in my case)...



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Comment Edited] (AMQ-5211) ActiveMQDestination.createDestination() should prevent empty destination name

[Ben O'Day (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019562#comment-14019562
 ] 

Ben O'Day edited comment on AMQ-5211 at 6/6/14 4:32 AM:


patch to add validation with simple unit tests for empty queue/topic names and 
fixed a few typos


was (Author: boday):
patch to add validation with simple unit tests for empty queue/topic names...

> ActiveMQDestination.createDestination() should prevent empty destination name
> -
>
> Key: AMQ-5211
> URL: https://issues.apache.org/jira/browse/AMQ-5211
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.9.0
>Reporter: Ben O'Day
>Priority: Minor
> Attachments: AMQ-5211.patch
>
>
> currently you can call ActiveMQDestination 
> createDestination("",ActiveMQDestination.QUEUE_TYPE) to create a queue with 
> no name.  
> while this doesn't seem to be an issue at first...if you are using mKahadb, 
> ActiveMQ will fail to restart after this queue/store directory are created.
> see this post: 
> http://activemq.2283324.n4.nabble.com/mkahadb-Failed-to-start-per-destination-persistence-adapter-for-destination-td4678754.html#a4679848
> the web console already prevents this, we should prevent this from other 
> entry points to this API (QueueView.moveMessagesTo() from JMX in my case)...



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (AMQ-5211) ActiveMQDestination.createDestination() should prevent empty destination name

[Ben O'Day (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMQ-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ben O'Day updated AMQ-5211:
---

Attachment: (was: AMQ-5211.patch)

> ActiveMQDestination.createDestination() should prevent empty destination name
> -
>
> Key: AMQ-5211
> URL: https://issues.apache.org/jira/browse/AMQ-5211
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.9.0
>Reporter: Ben O'Day
>Priority: Minor
>
> currently you can call ActiveMQDestination 
> createDestination("",ActiveMQDestination.QUEUE_TYPE) to create a queue with 
> no name.  
> while this doesn't seem to be an issue at first...if you are using mKahadb, 
> ActiveMQ will fail to restart after this queue/store directory are created.
> see this post: 
> http://activemq.2283324.n4.nabble.com/mkahadb-Failed-to-start-per-destination-persistence-adapter-for-destination-td4678754.html#a4679848
> the web console already prevents this, we should prevent this from other 
> entry points to this API (QueueView.moveMessagesTo() from JMX in my case)...



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (AMQ-5211) ActiveMQDestination.createDestination() should prevent empty destination name

[Ben O'Day (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMQ-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ben O'Day updated AMQ-5211:
---

Attachment: AMQ-5211.patch

patch to add validation with simple unit tests for empty queue/topic names...

> ActiveMQDestination.createDestination() should prevent empty destination name
> -
>
> Key: AMQ-5211
> URL: https://issues.apache.org/jira/browse/AMQ-5211
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.9.0
>Reporter: Ben O'Day
>Priority: Minor
> Attachments: AMQ-5211.patch
>
>
> currently you can call ActiveMQDestination 
> createDestination("",ActiveMQDestination.QUEUE_TYPE) to create a queue with 
> no name.  
> while this doesn't seem to be an issue at first...if you are using mKahadb, 
> ActiveMQ will fail to restart after this queue/store directory are created.
> see this post: 
> http://activemq.2283324.n4.nabble.com/mkahadb-Failed-to-start-per-destination-persistence-adapter-for-destination-td4678754.html#a4679848
> the web console already prevents this, we should prevent this from other 
> entry points to this API (QueueView.moveMessagesTo() from JMX in my case)...



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (AMQ-5211) ActiveMQDestination.createDestination() should prevent empty destination name

[Ben O'Day (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMQ-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ben O'Day updated AMQ-5211:
---

Attachment: (was: AMQ-5211.patch)

> ActiveMQDestination.createDestination() should prevent empty destination name
> -
>
> Key: AMQ-5211
> URL: https://issues.apache.org/jira/browse/AMQ-5211
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.9.0
>Reporter: Ben O'Day
>Priority: Minor
>
> currently you can call ActiveMQDestination 
> createDestination("",ActiveMQDestination.QUEUE_TYPE) to create a queue with 
> no name.  
> while this doesn't seem to be an issue at first...if you are using mKahadb, 
> ActiveMQ will fail to restart after this queue/store directory are created.
> see this post: 
> http://activemq.2283324.n4.nabble.com/mkahadb-Failed-to-start-per-destination-persistence-adapter-for-destination-td4678754.html#a4679848
> the web console already prevents this, we should prevent this from other 
> entry points to this API (QueueView.moveMessagesTo() from JMX in my case)...



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: [VOTE] Apache ActiveMQ 5.10.0 - Release Candidate 2

[Krzysztof Sobkowiak]

AMQ-5167 works now -- Karaf with Felix. With Equinox (AMQ-4794) does not work 
and adding the missing import doesn't help too,   


On 05.06.2014 23:54, artnaseef wrote:
> Did I misread the earlier statement that "it works", or did something change?
>
>
>
> --
> View this message in context: 
> http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-10-0-Release-Candidate-2-tp4681721p4681747.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.


-- 
Krzysztof Sobkowiak

JEE & OSS Architect | Technical Architect @ Capgemini
Capgemini  | Software Solutions Center
 | Wroclaw
e-mail: krzys.sobkow...@gmail.com  |
Twitter: @KSobkowiak
Calendar: goo.gl/yvsebC

Re: [VOTE] Apache ActiveMQ 5.10.0 - Release Candidate 2

[artnaseef]

Did I misread the earlier statement that "it works", or did something change?



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-10-0-Release-Candidate-2-tp4681721p4681747.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: [VOTE] Apache ActiveMQ 5.10.0 - Release Candidate 2

[Krzysztof Sobkowiak]

The problem still exists (tested with Karaf 2.3.4, Camel 2.13.1 and
ActiveMQ 5.10.0)



On 05.06.2014 23:00, artnaseef wrote:
> Great - any concerns with changing the resolution on
> https://issues.apache.org/jira/browse/AMQ-4794 to "FIXED"?
>
>
>
> --
> View this message in context: 
> http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-10-0-Release-Candidate-2-tp4681721p4681742.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.


-- 
Krzysztof Sobkowiak

JEE & OSS Architect | Technical Architect @ Capgemini
Capgemini  | Software Solutions Center
 | Wroclaw
e-mail: krzys.sobkow...@gmail.com  |
Twitter: @KSobkowiak
Calendar: goo.gl/yvsebC

[jira] [Commented] (AMQ-5211) ActiveMQDestination.createDestination() should prevent empty destination name

[Ben O'Day (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019278#comment-14019278
 ] 

Ben O'Day commented on AMQ-5211:


agreed Tim, I'll add a unit test to the patch...

> ActiveMQDestination.createDestination() should prevent empty destination name
> -
>
> Key: AMQ-5211
> URL: https://issues.apache.org/jira/browse/AMQ-5211
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.9.0
>Reporter: Ben O'Day
>Priority: Minor
> Attachments: AMQ-5211.patch
>
>
> currently you can call ActiveMQDestination 
> createDestination("",ActiveMQDestination.QUEUE_TYPE) to create a queue with 
> no name.  
> while this doesn't seem to be an issue at first...if you are using mKahadb, 
> ActiveMQ will fail to restart after this queue/store directory are created.
> see this post: 
> http://activemq.2283324.n4.nabble.com/mkahadb-Failed-to-start-per-destination-persistence-adapter-for-destination-td4678754.html#a4679848
> the web console already prevents this, we should prevent this from other 
> entry points to this API (QueueView.moveMessagesTo() from JMX in my case)...



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: [VOTE] Apache ActiveMQ 5.10.0 - Release Candidate 2

[artnaseef]

Great - any concerns with changing the resolution on
https://issues.apache.org/jira/browse/AMQ-4794 to "FIXED"?



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-10-0-Release-Candidate-2-tp4681721p4681742.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: RAM or Core for AMQ

[Gary Tully]

 can you elaborate on what sort of test your are running - message
size, persistent or non persistent, destination type, num
producer/consumer pairs, protocol etc. AMQ is not great at using
multiple cores so mostly gets cpu bound on 2/3 cores. So RAM/CPU is
the answer up to a point

On 31 May 2014 23:02, surfnerd  wrote:
> We are trying ActiveMQ and it's tough to scale beyond 17000 msgs / second.
> What affects more for AMQ performance RAM or Core ?
>
> Can anyone please share insights about AMQ performance at scale ?
>
> Thank you
>
>
>
> --
> View this message in context: 
> http://activemq.2283324.n4.nabble.com/RAM-or-Core-for-AMQ-tp4681541.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.



-- 
http://redhat.com
http://blog.garytully.com

[jira] [Commented] (AMQ-5211) ActiveMQDestination.createDestination() should prevent empty destination name

[Timothy Bish (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-5211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019250#comment-14019250
 ] 

Timothy Bish commented on AMQ-5211:
---

This seems sensible enough.  Empty destination names don't make much sense.  
Would be good if there were some unit tests to protect the change. 

> ActiveMQDestination.createDestination() should prevent empty destination name
> -
>
> Key: AMQ-5211
> URL: https://issues.apache.org/jira/browse/AMQ-5211
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.9.0
>Reporter: Ben O'Day
>Priority: Minor
> Attachments: AMQ-5211.patch
>
>
> currently you can call ActiveMQDestination 
> createDestination("",ActiveMQDestination.QUEUE_TYPE) to create a queue with 
> no name.  
> while this doesn't seem to be an issue at first...if you are using mKahadb, 
> ActiveMQ will fail to restart after this queue/store directory are created.
> see this post: 
> http://activemq.2283324.n4.nabble.com/mkahadb-Failed-to-start-per-destination-persistence-adapter-for-destination-td4678754.html#a4679848
> the web console already prevents this, we should prevent this from other 
> entry points to this API (QueueView.moveMessagesTo() from JMX in my case)...



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Resolved] (AMQ-5214) Security errors for sync commands are only logged at debug levels

[Timothy Bish (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMQ-5214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Bish resolved AMQ-5214.
---

Resolution: Fixed

Fixed on trunk.

> Security errors for sync commands are only logged at debug levels
> -
>
> Key: AMQ-5214
> URL: https://issues.apache.org/jira/browse/AMQ-5214
> Project: ActiveMQ
>  Issue Type: Improvement
>  Components: Broker, Transport
>Affects Versions: 5.9.0, 5.9.1, 5.10.0
>Reporter: Timothy Bish
>Assignee: Timothy Bish
>Priority: Trivial
> Fix For: 5.11.0
>
>
> For any operation that sends a sync commands (response required) there is no 
> warning logs indicating a security exception was triggered.  In the async 
> case we log in detail.  We should add a log at warn level for security errors 
> sent back as responses.  



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (AMQ-5214) Security errors for sync commands are only logged at debug levels

[Timothy Bish (JIRA)]

Timothy Bish created AMQ-5214:
-

 Summary: Security errors for sync commands are only logged at 
debug levels
 Key: AMQ-5214
 URL: https://issues.apache.org/jira/browse/AMQ-5214
 Project: ActiveMQ
  Issue Type: Improvement
  Components: Broker, Transport
Affects Versions: 5.9.1, 5.9.0, 5.10.0
Reporter: Timothy Bish
Assignee: Timothy Bish
Priority: Trivial
 Fix For: 5.11.0


For any operation that sends a sync commands (response required) there is no 
warning logs indicating a security exception was triggered.  In the async case 
we log in detail.  We should add a log at warn level for security errors sent 
back as responses.  



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: [VOTE] Apache ActiveMQ 5.10.0 - Release Candidate 2

[Krzysztof Sobkowiak]

The web console installs now with no problem on Karaf.

Best regards
Krzysztof

On 05.06.2014 16:08, Dejan Bosanac wrote:
> Hi folks,
>
> I've just cut a second release candidate for the 5.10.0 release. This
> release has
> 232 bug fixes and improvements.
>
> Could you review the artifacts and vote?
>
> The list of resolved issues is here:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMQ%20AND%20fixVersion%20%3D%205.10.0%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC
>
>
> You can get binary distributions here:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1007/org/apache/activemq/apache-activemq/5.10.0/
>
> Source archives are here:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1007/org/apache/activemq/activemq-parent/5.10.0/
>
> Maven2 repository is at:
> https://repository.apache.org/content/repositories/orgapacheactivemq-1007/
>
> Source tag:
> https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=58dd93e42e7405768fd89154ff94b45ac71f151f
>
>
> Please vote to approve this release
>
> [ ] +1 Release the binary as Apache ActiveMQ 5.10.0
> [ ] -1 Veto the release (provide specific comments)
>
> Here's my +1
>
> Regards
> --
> Dejan Bosanac
> --
> Red Hat, Inc.
> FuseSource is now part of Red Hat
> dbosa...@redhat.com
> Twitter: @dejanb
> Blog: http://sensatic.net
> ActiveMQ in Action: http://www.manning.com/snyder/
>


-- 
Krzysztof Sobkowiak

JEE & OSS Architect | Technical Architect @ Capgemini
Capgemini  | Software Solutions Center
 | Wroclaw
e-mail: krzys.sobkow...@gmail.com  |
Twitter: @KSobkowiak
Calendar: goo.gl/yvsebC

[jira] [Resolved] (AMQ-5213) Allow for changing logger levels via JMX

[Timothy Bish (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMQ-5213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Timothy Bish resolved AMQ-5213.
---

Resolution: Fixed

Feature added on trunk. 

> Allow for changing logger levels via JMX
> 
>
> Key: AMQ-5213
> URL: https://issues.apache.org/jira/browse/AMQ-5213
> Project: ActiveMQ
>  Issue Type: New Feature
>  Components: Broker, JMX
>Affects Versions: 5.9.0, 5.9.1, 5.10.0
>Reporter: Timothy Bish
>Assignee: Timothy Bish
>Priority: Minor
> Fix For: 5.11.0
>
>
> Create a new MBean that is loaded if the Broker is running with Log4J as 
> which would allow for changing the level of loggers via JMX to enable debug 
> without needing access to the log4j.properties.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (AMQ-5213) Allow for changing logger levels via JMX

[Timothy Bish (JIRA)]

Timothy Bish created AMQ-5213:
-

 Summary: Allow for changing logger levels via JMX
 Key: AMQ-5213
 URL: https://issues.apache.org/jira/browse/AMQ-5213
 Project: ActiveMQ
  Issue Type: New Feature
  Components: Broker, JMX
Affects Versions: 5.9.1, 5.9.0, 5.10.0
Reporter: Timothy Bish
Assignee: Timothy Bish
Priority: Minor
 Fix For: 5.11.0


Create a new MBean that is loaded if the Broker is running with Log4J as which 
would allow for changing the level of loggers via JMX to enable debug without 
needing access to the log4j.properties.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Build failed in Jenkins: ActiveMQ Protocol Buffer #15

[Apache Jenkins Server]

See 

--
[...truncated 828 lines...]
1K downloaded
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-sink-api/1.0-alpha-9/doxia-sink-api-1.0-alpha-9.pom
1K downloaded
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia/1.0-alpha-9/doxia-1.0-alpha-9.pom
8K downloaded
Downloading: 
http://repo1.maven.org/maven2/net/java/dev/javacc/javacc/4.0/javacc-4.0.jar
267K downloaded
Downloading: 
http://repo1.maven.org/maven2/edu/ucla/cs/compilers/jtb/1.3.2/jtb-1.3.2.jar
329K downloaded
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/reporting/maven-reporting-impl/2.0.4/maven-reporting-impl-2.0.4.jar
13K downloaded
Downloading: 
http://repo1.maven.org/maven2/commons-validator/commons-validator/1.2.0/commons-validator-1.2.0.jar
88K downloaded
Downloading: 
http://repo1.maven.org/maven2/commons-beanutils/commons-beanutils/1.7.0/commons-beanutils-1.7.0.jar
184K downloaded
Downloading: 
http://repo1.maven.org/maven2/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar
37K downloaded
Downloading: 
http://repo1.maven.org/maven2/commons-digester/commons-digester/1.6/commons-digester-1.6.jar
164K downloaded
Downloading: 
http://repo1.maven.org/maven2/xml-apis/xml-apis/1.0.b2/xml-apis-1.0.b2.jar
106K downloaded
Downloading: http://repo1.maven.org/maven2/oro/oro/2.0.7/oro-2.0.7.jar
63K downloaded
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-core/1.0-alpha-7/doxia-core-1.0-alpha-7.jar
225K downloaded
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-site-renderer/1.0-alpha-7/doxia-site-renderer-1.0-alpha-7.jar
12K downloaded
Downloading: 
http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-i18n/1.0-beta-6/plexus-i18n-1.0-beta-6.jar
11K downloaded
Downloading: 
http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-velocity/1.1.2/plexus-velocity-1.1.2.jar
7K downloaded
Downloading: 
http://repo1.maven.org/maven2/commons-logging/commons-logging-api/1.0.4/commons-logging-api-1.0.4.jar
25K downloaded
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-decoration-model/1.0-alpha-7/doxia-decoration-model-1.0-alpha-7.jar
37K downloaded
[INFO] [javacc:javacc {execution: javacc}]
Java Compiler Compiler Version 4.0 (Parser Generator)
(type "javacc" with no arguments for help)
Reading from file 

 . . .
File "TokenMgrError.java" does not exist.  Will create one.
File "ParseException.java" does not exist.  Will create one.
File "Token.java" does not exist.  Will create one.
File "SimpleCharStream.java" does not exist.  Will create one.
Parser generated successfully.
[INFO] Processed 1 grammar
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-site-renderer/1.0-alpha-10/doxia-site-renderer-1.0-alpha-10.pom
4K downloaded
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-sitetools/1.0-alpha-10/doxia-sitetools-1.0-alpha-10.pom
7K downloaded
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-core/1.0-alpha-10/doxia-core-1.0-alpha-10.pom
2K downloaded
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-decoration-model/1.0-alpha-10/doxia-decoration-model-1.0-alpha-10.pom
2K downloaded
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-module-apt/1.0-alpha-10/doxia-module-apt-1.0-alpha-10.pom
2K downloaded
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-modules/1.0-alpha-10/doxia-modules-1.0-alpha-10.pom
2K downloaded
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-module-fml/1.0-alpha-10/doxia-module-fml-1.0-alpha-10.pom
2K downloaded
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-module-xdoc/1.0-alpha-10/doxia-module-xdoc-1.0-alpha-10.pom
2K downloaded
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/doxia/doxia-module-xhtml/1.0-alpha-10/doxia-module-xhtml-1.0-alpha-10.pom
1K downloaded
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/maven-plugin-descriptor/2.0.6/maven-plugin-descriptor-2.0.6.pom
1K downloaded
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/plugin-tools/maven-plugin-tools-api/2.5/maven-plugin-tools-api-2.5.pom
4K downloaded
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/plugin-tools/maven-plugin-tools/2.5/maven-plugin-tools-2.5.pom
9K downloaded
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/reporting/maven-reporting-impl/2.0.4.1/maven-reporting-impl-2.0.4.1.pom
2K downloaded
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/plugin-tools/maven-plugin-tools-java/2.5/maven-plugin-tools-java-2.5.pom
2K downloaded
Downloading: http://repo1.maven.org/maven2/ant/ant/1.5.1/ant-1.5.1.pom
140b downloaded
Downloading: 

Re: [VOTE] Apache ActiveMQ 5.10.0 - Release Candidate 2

[artnaseef]

Can someone familiar with AMQ-4269 put a quick comment there as to why it was
marked "invalid"?  Was it a case of the original post didn't expose a bug,
but rather just known "undesirable, but correct" operation?

https://issues.apache.org/jira/browse/AMQ-4269


AMQ-4794 is marked "won't fix -- due to HawtIO console".  Does it make sense
to revive that one or mark it "won't fix" for another reason?


That's as far as I've reviews of the bug list so far; I'll do more later.



--
View this message in context: 
http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-10-0-Release-Candidate-2-tp4681721p4681725.html
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

[jira] [Commented] (AMQ-5167) ActiveMQ web-cosole fails to start in Karaf - missing import

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-5167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14018842#comment-14018842
 ] 

ASF GitHub Bot commented on AMQ-5167:
-

Github user sobkowiak closed the pull request at:

https://github.com/apache/activemq/pull/27


> ActiveMQ web-cosole fails to start in Karaf - missing import 
> -
>
> Key: AMQ-5167
> URL: https://issues.apache.org/jira/browse/AMQ-5167
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: OSGi/Karaf
>Affects Versions: 5.9.1
>Reporter: Ioan Eugen Stan
> Fix For: 5.10.0
>
>
> Steps to reprodouce: 
> 1. start Karaf 2.3.5 or 3.0.1. 
> 2. install activemq feature : 
> feature:repo-add activemq 5.9.1 
> feature:install activemq-broker 
> Stack trace: 
> ~~~
> aused by: org.springframework.beans.factory.BeanCreationException: Error 
> creating bean with name 
> 'org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter':
>  Instantiation of bean failed; nested exception is 
> org.springframework.beans.BeanInstantiationException: Could not instantiate 
> bean class 
> [org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter]:
>  Constructor threw exception; nested exception is 
> java.lang.NoClassDefFoundError: javax/xml/stream/XMLStreamException
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1037)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:983)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:487)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:289)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.DispatcherServlet.createDefaultStrategy(DispatcherServlet.java:810)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.DispatcherServlet.getDefaultStrategies(DispatcherServlet.java:779)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.DispatcherServlet.initHandlerAdapters(DispatcherServlet.java:587)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.DispatcherServlet.initStrategies(DispatcherServlet.java:444)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.DispatcherServlet.onRefresh(DispatcherServlet.java:432)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.FrameworkServlet.onApplicationEvent(FrameworkServlet.java:772)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.FrameworkServlet$ContextRefreshListener.onApplicationEvent(FrameworkServlet.java:1083)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.FrameworkServlet$ContextRefreshListener.onApplicationEvent(FrameworkServlet.java:1080)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.context.event.GenericApplicationListenerAdapter.onApplicationEvent(GenericApplicationListenerAdapter.java:51)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.context.event.SourceFilteringListener.onApplicationEventInternal(SourceFilteringListener.java:96)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.context.event.SourceFilteringListener.onApplicationEvent(SourceFilteringListener.java:68)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:96)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:334)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:948)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.context.s

[GitHub] activemq pull request: AMQ-5167 ActiveMQ web-cosole fails to start...

[sobkowiak]

Github user sobkowiak closed the pull request at:

https://github.com/apache/activemq/pull/27


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (AMQ-5030) Upgrade Camel to latest 2.12.x patch

[Paul Gale (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14018830#comment-14018830
 ] 

Paul Gale commented on AMQ-5030:


Is there any reason why Camel cannot be upgraded to 2.13.1 instead of 2.12x?

> Upgrade Camel to latest 2.12.x patch
> 
>
> Key: AMQ-5030
> URL: https://issues.apache.org/jira/browse/AMQ-5030
> Project: ActiveMQ
>  Issue Type: Task
>  Components: activemq-camel
>Reporter: Claus Ibsen
>Assignee: Hadrian Zbarcea
>Priority: Blocker
> Fix For: 5.10.0
>
>
> We need to upgrade to latest Camel 2.12.3 release to pickup some very 
> important fixes.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[VOTE] Apache ActiveMQ 5.10.0 - Release Candidate 2

[Dejan Bosanac]

Hi folks,

I've just cut a second release candidate for the 5.10.0 release. This
release has
232 bug fixes and improvements.

Could you review the artifacts and vote?

The list of resolved issues is here:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20AMQ%20AND%20fixVersion%20%3D%205.10.0%20AND%20status%20%3D%20Resolved%20ORDER%20BY%20priority%20DESC


You can get binary distributions here:
https://repository.apache.org/content/repositories/orgapacheactivemq-1007/org/apache/activemq/apache-activemq/5.10.0/

Source archives are here:
https://repository.apache.org/content/repositories/orgapacheactivemq-1007/org/apache/activemq/activemq-parent/5.10.0/

Maven2 repository is at:
https://repository.apache.org/content/repositories/orgapacheactivemq-1007/

Source tag:
https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=58dd93e42e7405768fd89154ff94b45ac71f151f


Please vote to approve this release

[ ] +1 Release the binary as Apache ActiveMQ 5.10.0
[ ] -1 Veto the release (provide specific comments)

Here's my +1

Regards
--
Dejan Bosanac
--
Red Hat, Inc.
FuseSource is now part of Red Hat
dbosa...@redhat.com
Twitter: @dejanb
Blog: http://sensatic.net
ActiveMQ in Action: http://www.manning.com/snyder/

[jira] [Updated] (AMQ-5125) Broker and clients hang

[Tomas Klubal (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMQ-5125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tomas Klubal updated AMQ-5125:
--

Attachment: broker-threads-blocked.tdump

Same issue happening to us not every time but quite often on very small load 
and even with just one rollback. The all threads are BLOCKED. The version is  
5.9.0.

> Broker and clients hang
> ---
>
> Key: AMQ-5125
> URL: https://issues.apache.org/jira/browse/AMQ-5125
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.9.0, 5.10.0
> Environment: Windows 7, Linux
> JAVA_HOME=C:\Program Files\Java\jdk1.7.0_07
> ActiveMQ 5.9.0 with LevelDB storage adapter enabled
>Reporter: Albert Barmettler
>Priority: Blocker
> Attachments: Broker-threaddump-1396544622970.tdump, 
> Clients-threaddump-1396544622970.tdump, VM.PNG, activemq.xml, 
> broker-threads-blocked.tdump, src.zip
>
>
> JMS clients start to hang after a while in calls such as 
> session.createObjectMessage(). Both the broker and the hanging clients can't 
> be easily shut down when this happens - only forcefully applied kill's do the 
> job.
> I'm using queues and transactional sessions. All clients (producers and 
> consumers) are in the same Java VM. There is only one JMS connection between 
> the application and the broker. Each client has its own session, but they all 
> share the same connection.
> Normally, the data directory of the LevelDb contains only a few log files. 
> But in my case, the number of log files is steadily increasing.
> Furthermore, I was able to track down the issue to following circumstance: 
> The problem only occurs, when consumers do a rollback instead of a commit 
> when they receive the message. The rollback / redelivery works as expected - 
> the same message is received again after a previous rollback.
> As far as I can tell, the problem does not occur with KahaDb.
> I'll attach a test program that provokes the error. It sets up a few hundred 
> queues, consumers and producers. The consumers just receive the message and 
> commit the session, but they also do "random" rollbacks. It can be observed 
> immediately that the number of files starts increasing in the data directory. 
> After a few minutes, the clients hang - sometimes sooner, sometimes later. 
> I'll also attach the config file for the broker.
> I am aware, that heavy rollbacking should not happen in normal operation. But 
> from a long term stability perspective, this is a blocker for us.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Created] (AMQ-5212) Deadlock with duplicate detection and dlq processing in kahadb

[Gary Tully (JIRA)]

Gary Tully created AMQ-5212:
---

 Summary: Deadlock with duplicate detection and dlq processing in 
kahadb
 Key: AMQ-5212
 URL: https://issues.apache.org/jira/browse/AMQ-5212
 Project: ActiveMQ
  Issue Type: Bug
  Components: Broker, Message Store
Affects Versions: 5.9.1, 5.9.0
Reporter: Gary Tully
Assignee: Gary Tully
 Fix For: 5.10.0


Contention between access to the destination map from store duplicate 
processing and dlq destination creation from the cursor. But could be between 
any destination creation/deletion.
>From the test case: {code}Found one Java-level deadlock:
=
"ActiveMQ Transport: tcp://27.0.0.1:60895@60852":
  waiting for ownable synchronizer 7df695ea8, (a 
java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync),
  which is held by "ActiveMQ Transport: tcp://27.0.0.1:60894@60852"
"ActiveMQ Transport: tcp://27.0.0.1:60894@60852":
  waiting for ownable synchronizer 7df605fd8, (a 
java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync),
  which is held by "ConcurrentQueueStoreAndDispatch"
"ConcurrentQueueStoreAndDispatch":
  waiting for ownable synchronizer 7df695ea8, (a 
java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync),
  which is held by "ActiveMQ Transport: tcp://27.0.0.1:60894@60852"

Java stack information for the threads listed above:
===
"ActiveMQ Transport: tcp://27.0.0.1:60895@60852":
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  <7df695ea8> (a 
java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:811)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:842)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1178)
at 
java.util.concurrent.locks.ReentrantReadWriteLock$WriteLock.lock(ReentrantReadWriteLock.java:890)
at 
org.apache.activemq.broker.region.AbstractRegion.addDestination(AbstractRegion.java:129)
at 
org.apache.activemq.broker.region.RegionBroker.addDestination(RegionBroker.java:334)
at 
org.apache.activemq.broker.BrokerFilter.addDestination(BrokerFilter.java:172)
at 
org.apache.activemq.advisory.AdvisoryBroker.addDestination(AdvisoryBroker.java:184)
at 
org.apache.activemq.broker.BrokerFilter.addDestination(BrokerFilter.java:172)
at 
org.apache.activemq.broker.BrokerFilter.addDestination(BrokerFilter.java:172)
at 
org.apache.activemq.broker.MutableBrokerFilter.addDestination(MutableBrokerFilter.java:177)
at 
org.apache.activemq.broker.region.RegionBroker.addProducer(RegionBroker.java:384)
at 
org.apache.activemq.broker.BrokerFilter.addProducer(BrokerFilter.java:107)
at 
org.apache.activemq.advisory.AdvisoryBroker.addProducer(AdvisoryBroker.java:172)
at 
org.apache.activemq.broker.CompositeDestinationBroker.addProducer(CompositeDestinationBroker.java:56)
at 
org.apache.activemq.broker.BrokerFilter.addProducer(BrokerFilter.java:107)
at 
org.apache.activemq.broker.MutableBrokerFilter.addProducer(MutableBrokerFilter.java:112)
at 
org.apache.activemq.broker.TransportConnection.processAddProducer(TransportConnection.java:565)
at org.apache.activemq.command.ProducerInfo.visit(ProducerInfo.java:108)
at 
org.apache.activemq.broker.TransportConnection.service(TransportConnection.java:294)
at 
org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:148)
at 
org.apache.activemq.transport.MutexTransport.onCommand(MutexTransport.java:50)
at 
org.apache.activemq.transport.WireFormatNegotiator.onCommand(WireFormatNegotiator.java:113)
at 
org.apache.activemq.transport.AbstractInactivityMonitor.onCommand(AbstractInactivityMonitor.java:270)
at 
org.apache.activemq.transport.TransportSupport.doConsume(TransportSupport.java:83)
at 
org.apache.activemq.transport.tcp.TcpTransport.doRun(TcpTransport.java:214)
at 
org.apache.activemq.transport.tcp.TcpTransport.run(TcpTransport.java:196)
at java.lang.Thread.run(Thread.java:695)
"ActiveMQ Transport: tcp://27.0.0.1:60894@60852":
at sun.misc.Unsafe.park(Native Method)
- parking to wait for  <7df605fd8> (a 
java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:156)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:811)
at 
java.util.concurrent.locks.AbstractQueuedSynch

[jira] [Commented] (AMQ-5167) ActiveMQ web-cosole fails to start in Karaf - missing import

[Dejan Bosanac (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-5167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14018633#comment-14018633
 ] 

Dejan Bosanac commented on AMQ-5167:


I don't have any plans to do it. If someone wants to do it, he can apply the 
patch to that branch before the release.

> ActiveMQ web-cosole fails to start in Karaf - missing import 
> -
>
> Key: AMQ-5167
> URL: https://issues.apache.org/jira/browse/AMQ-5167
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: OSGi/Karaf
>Affects Versions: 5.9.1
>Reporter: Ioan Eugen Stan
> Fix For: 5.10.0
>
>
> Steps to reprodouce: 
> 1. start Karaf 2.3.5 or 3.0.1. 
> 2. install activemq feature : 
> feature:repo-add activemq 5.9.1 
> feature:install activemq-broker 
> Stack trace: 
> ~~~
> aused by: org.springframework.beans.factory.BeanCreationException: Error 
> creating bean with name 
> 'org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter':
>  Instantiation of bean failed; nested exception is 
> org.springframework.beans.BeanInstantiationException: Could not instantiate 
> bean class 
> [org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter]:
>  Constructor threw exception; nested exception is 
> java.lang.NoClassDefFoundError: javax/xml/stream/XMLStreamException
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1037)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:983)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:487)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:289)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.DispatcherServlet.createDefaultStrategy(DispatcherServlet.java:810)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.DispatcherServlet.getDefaultStrategies(DispatcherServlet.java:779)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.DispatcherServlet.initHandlerAdapters(DispatcherServlet.java:587)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.DispatcherServlet.initStrategies(DispatcherServlet.java:444)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.DispatcherServlet.onRefresh(DispatcherServlet.java:432)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.FrameworkServlet.onApplicationEvent(FrameworkServlet.java:772)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.FrameworkServlet$ContextRefreshListener.onApplicationEvent(FrameworkServlet.java:1083)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.FrameworkServlet$ContextRefreshListener.onApplicationEvent(FrameworkServlet.java:1080)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.context.event.GenericApplicationListenerAdapter.onApplicationEvent(GenericApplicationListenerAdapter.java:51)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.context.event.SourceFilteringListener.onApplicationEventInternal(SourceFilteringListener.java:96)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.context.event.SourceFilteringListener.onApplicationEvent(SourceFilteringListener.java:68)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:96)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:334)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:948)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springf

[jira] [Commented] (AMQ-5167) ActiveMQ web-cosole fails to start in Karaf - missing import

[Krzysztof Sobkowiak (JIRA)]

[ 
https://issues.apache.org/jira/browse/AMQ-5167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14018627#comment-14018627
 ] 

Krzysztof Sobkowiak commented on AMQ-5167:
--

Will you not release the 5.9.x line anymore? 

> ActiveMQ web-cosole fails to start in Karaf - missing import 
> -
>
> Key: AMQ-5167
> URL: https://issues.apache.org/jira/browse/AMQ-5167
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: OSGi/Karaf
>Affects Versions: 5.9.1
>Reporter: Ioan Eugen Stan
> Fix For: 5.10.0
>
>
> Steps to reprodouce: 
> 1. start Karaf 2.3.5 or 3.0.1. 
> 2. install activemq feature : 
> feature:repo-add activemq 5.9.1 
> feature:install activemq-broker 
> Stack trace: 
> ~~~
> aused by: org.springframework.beans.factory.BeanCreationException: Error 
> creating bean with name 
> 'org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter':
>  Instantiation of bean failed; nested exception is 
> org.springframework.beans.BeanInstantiationException: Could not instantiate 
> bean class 
> [org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter]:
>  Constructor threw exception; nested exception is 
> java.lang.NoClassDefFoundError: javax/xml/stream/XMLStreamException
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1037)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:983)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:487)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:289)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.DispatcherServlet.createDefaultStrategy(DispatcherServlet.java:810)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.DispatcherServlet.getDefaultStrategies(DispatcherServlet.java:779)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.DispatcherServlet.initHandlerAdapters(DispatcherServlet.java:587)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.DispatcherServlet.initStrategies(DispatcherServlet.java:444)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.DispatcherServlet.onRefresh(DispatcherServlet.java:432)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.FrameworkServlet.onApplicationEvent(FrameworkServlet.java:772)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.FrameworkServlet$ContextRefreshListener.onApplicationEvent(FrameworkServlet.java:1083)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.FrameworkServlet$ContextRefreshListener.onApplicationEvent(FrameworkServlet.java:1080)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.context.event.GenericApplicationListenerAdapter.onApplicationEvent(GenericApplicationListenerAdapter.java:51)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.context.event.SourceFilteringListener.onApplicationEventInternal(SourceFilteringListener.java:96)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.context.event.SourceFilteringListener.onApplicationEvent(SourceFilteringListener.java:68)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:96)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:334)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:948)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.context.support.AbstractApplicationContext.refresh(A

[jira] [Resolved] (AMQ-5167) ActiveMQ web-cosole fails to start in Karaf - missing import

[Dejan Bosanac (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMQ-5167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dejan Bosanac resolved AMQ-5167.


   Resolution: Fixed
Fix Version/s: 5.10.0

Patch applied to trunk. Thanks!

> ActiveMQ web-cosole fails to start in Karaf - missing import 
> -
>
> Key: AMQ-5167
> URL: https://issues.apache.org/jira/browse/AMQ-5167
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: OSGi/Karaf
>Affects Versions: 5.9.1
>Reporter: Ioan Eugen Stan
> Fix For: 5.10.0
>
>
> Steps to reprodouce: 
> 1. start Karaf 2.3.5 or 3.0.1. 
> 2. install activemq feature : 
> feature:repo-add activemq 5.9.1 
> feature:install activemq-broker 
> Stack trace: 
> ~~~
> aused by: org.springframework.beans.factory.BeanCreationException: Error 
> creating bean with name 
> 'org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter':
>  Instantiation of bean failed; nested exception is 
> org.springframework.beans.BeanInstantiationException: Could not instantiate 
> bean class 
> [org.springframework.web.servlet.mvc.annotation.AnnotationMethodHandlerAdapter]:
>  Constructor threw exception; nested exception is 
> java.lang.NoClassDefFoundError: javax/xml/stream/XMLStreamException
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1037)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:983)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:487)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:289)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.DispatcherServlet.createDefaultStrategy(DispatcherServlet.java:810)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.DispatcherServlet.getDefaultStrategies(DispatcherServlet.java:779)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.DispatcherServlet.initHandlerAdapters(DispatcherServlet.java:587)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.DispatcherServlet.initStrategies(DispatcherServlet.java:444)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.DispatcherServlet.onRefresh(DispatcherServlet.java:432)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.FrameworkServlet.onApplicationEvent(FrameworkServlet.java:772)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.FrameworkServlet$ContextRefreshListener.onApplicationEvent(FrameworkServlet.java:1083)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.web.servlet.FrameworkServlet$ContextRefreshListener.onApplicationEvent(FrameworkServlet.java:1080)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.context.event.GenericApplicationListenerAdapter.onApplicationEvent(GenericApplicationListenerAdapter.java:51)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.context.event.SourceFilteringListener.onApplicationEventInternal(SourceFilteringListener.java:96)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.context.event.SourceFilteringListener.onApplicationEvent(SourceFilteringListener.java:68)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:96)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:334)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:948)[145:org.apache.activemq.activemq-web-console:5.9.1]
>   at 
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.jav

[jira] [Updated] (AMQ-5193) Java Files Started Appearing in activemq-all jar starting in 5.9.0

[Dejan Bosanac (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMQ-5193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dejan Bosanac updated AMQ-5193:
---

Fix Version/s: (was: 5.11.0)
   5.10.0

> Java Files Started Appearing in activemq-all jar starting in 5.9.0
> --
>
> Key: AMQ-5193
> URL: https://issues.apache.org/jira/browse/AMQ-5193
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.9.0, 5.9.1
>Reporter: Johnny Clark
> Fix For: 5.10.0
>
>
> activemq-all-5.8.0.jar and older versions do not contain any .java files, 
> only .class files as I would expect.  Strating in version 
> activemq-all-5.9.0.jar .java and .class files are included in the JAR. 
> Was this intentional?  I'm having a problem related to the fact that Maven 
> is attempting to compile the.java files within the jar.  I'm sure I can work 
> around the issue in the short term, however I wanted to make sure that you 
> were aware of it.  It seems odd to me that the .java files are included in 
> the .jar file, normally they would only appear in the sources jar (example: 
> activemq-all-5.9.0-sources.jar). 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

[jira] [Updated] (AMQ-5209) Add additional properties to advisory for consumed, delivered and discarded

[Dejan Bosanac (JIRA)]

 [ 
https://issues.apache.org/jira/browse/AMQ-5209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dejan Bosanac updated AMQ-5209:
---

Fix Version/s: (was: 5.11.0)
   5.10.0

> Add additional properties to advisory for consumed, delivered and discarded
> ---
>
> Key: AMQ-5209
> URL: https://issues.apache.org/jira/browse/AMQ-5209
> Project: ActiveMQ
>  Issue Type: Improvement
>  Components: Broker
>Affects Versions: 5.9.0, 5.9.1
>Reporter: Timothy Bish
>Priority: Minor
> Fix For: 5.10.0
>
>
> Add information as message properties to the advisory events for Message ID 
> and Destination so that clients can read information using standard JMS API 
> calls.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Re: [VOTE] Apache ActiveMQ 5.10.0

[Dejan Bosanac]

Hi Paul,

it’s a mistake in the release notes, it got all the issues that has fix
version 5.10.

Regards
--
Dejan Bosanac
--
Red Hat, Inc.
FuseSource is now part of Red Hat
dbosa...@redhat.com
Twitter: @dejanb
Blog: http://sensatic.net
ActiveMQ in Action: http://www.manning.com/snyder/


On Wed, Jun 4, 2014 at 8:17 PM, Paul Gale  wrote:

> Hi Dejan,
>
> The release notes for 5.10 that you posted earlier state that the bug
> AMQ-5174 has been fixed. When I checked Jira, however, it's still marked as
> open and unresolved. I was hopeful that it was fixed as it was a bug that I
> reported.
>
> Is this an oversight or has the Jira ticket not been updated to reflect the
> actual fix?
>
> Thanks,
> Paul
>
>
> On Wed, Jun 4, 2014 at 12:12 PM, Krzysztof Sobkowiak <
> krzys.sobkow...@gmail.com> wrote:
>
> > Hi
> >
> > I tried to install the web console on Karaf 2.3.x and it fails with
> > following error
> >
> > Caused by: java.lang.ClassNotFoundException:
> > javax.xml.transform.dom.DOMSource not found by
> > org.apache.activemq.activemq-web-console [138]
> > at
> >
> >
> org.apache.felix.framework.BundleWiringImpl.findClassOrResourceByDelegation(BundleWiringImpl.java:1460)[org.apache.felix.framework-4.0.3.jar:]
> > at
> >
> >
> org.apache.felix.framework.BundleWiringImpl.access$400(BundleWiringImpl.java:72)[org.apache.felix.framework-4.0.3.jar:]
> > at
> >
> >
> org.apache.felix.framework.BundleWiringImpl$BundleClassLoader.loadClass(BundleWiringImpl.java:1843)
> >
> > I have attached a new pull request for trunk in AMQ-5167
> > 
> >
> > Best regards
> > Krzysztof
> >
> > On 04.06.2014 15:10, Dejan Bosanac wrote:
> > > Hi folks,
> > >
> > > I've just cut a release candidate for the long-awaited 5.10.0 release.
> > This
> > > release has
> > > 229 bug fixes and improvements.
> > >
> > > Could you review the artifacts and vote?
> > >
> > > The list of resolved issues is here:
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12324950&styleName=&projectId=12311210
> > >
> > > You can get binary distributions here:
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheactivemq-1003/org/apache/activemq/apache-activemq/5.10.0/
> > >
> > > Source archives are here:
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheactivemq-1003/org/apache/activemq/activemq-parent/5.10.0/
> > >
> > > Maven2 repository is at:
> > >
> >
> https://repository.apache.org/content/repositories/orgapacheactivemq-1003/
> > >
> > > Source tag:
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=5bc741f227e7f3e17862db5d3543b445dc746869
> > >
> > >
> > > Please vote to approve this release
> > >
> > > [ ] +1 Release the binary as Apache ActiveMQ 5.10.0
> > > [ ] -1 Veto the release (provide specific comments)
> > >
> > > Here's my +1
> > >
> > > Regards
> > > --
> > > Dejan Bosanac
> > > --
> > > Red Hat, Inc.
> > > dbosa...@redhat.com
> > > Twitter: @dejanb
> > > Blog: http://sensatic.net
> > > ActiveMQ in Action: http://www.manning.com/snyder/
> > >
> >
> >
> > --
> > Krzysztof Sobkowiak
> >
> > JEE & OSS Architect | Technical Architect @ Capgemini
> > Capgemini  | Software Solutions Center
> >  | Wroclaw
> > e-mail: krzys.sobkow...@gmail.com  |
> > Twitter: @KSobkowiak
> > Calendar: goo.gl/yvsebC
> >
>

Re: [VOTE] Apache ActiveMQ 5.10.0

[Dejan Bosanac]

Thanks guys, cancelling this vote and will build the new RC.

Regards
--
Dejan Bosanac
--
Red Hat, Inc.
FuseSource is now part of Red Hat
dbosa...@redhat.com
Twitter: @dejanb
Blog: http://sensatic.net
ActiveMQ in Action: http://www.manning.com/snyder/


On Wed, Jun 4, 2014 at 9:25 PM, Timothy Bish  wrote:

> On 06/04/2014 09:10 AM, Dejan Bosanac wrote:
>
>> Hi folks,
>>
>> I've just cut a release candidate for the long-awaited 5.10.0 release.
>> This
>> release has
>> 229 bug fixes and improvements.
>>
>> Could you review the artifacts and vote?
>>
>> The list of resolved issues is here:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
>> version=12324950&styleName=&projectId=12311210
>>
>> You can get binary distributions here:
>> https://repository.apache.org/content/repositories/
>> orgapacheactivemq-1003/org/apache/activemq/apache-activemq/5.10.0/
>>
>> Source archives are here:
>> https://repository.apache.org/content/repositories/
>> orgapacheactivemq-1003/org/apache/activemq/activemq-parent/5.10.0/
>>
>> Maven2 repository is at:
>> https://repository.apache.org/content/repositories/
>> orgapacheactivemq-1003/
>>
>> Source tag:
>> https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=
>> 5bc741f227e7f3e17862db5d3543b445dc746869
>>
>>
>> Please vote to approve this release
>>
>> [ ] +1 Release the binary as Apache ActiveMQ 5.10.0
>> [ ] -1 Veto the release (provide specific comments)
>>
>> Here's my +1
>>
>> Regards
>> --
>> Dejan Bosanac
>> --
>> Red Hat, Inc.
>> dbosa...@redhat.com
>> Twitter: @dejanb
>> Blog: http://sensatic.net
>> ActiveMQ in Action: http://www.manning.com/snyder/
>>
>>
> -1
>
> Looks like these should all really get into a 5.10.0 release first.
>
> Missing imports in pom.
> https://issues.apache.org/jira/browse/AMQ-5167
>
> Source files included in the activemq-all jar.
> https://issues.apache.org/jira/browse/AMQ-5193
>
> This one could also go in if redoing the release:
> https://issues.apache.org/jira/browse/AMQ-5209
>
> --
> Tim Bish
> Sr Software Engineer | RedHat Inc.
> tim.b...@redhat.com | www.fusesource.com | www.redhat.com
> skype: tabish121 | twitter: @tabish121
> blog: http://timbish.blogspot.com/
>
>