date:20140610

Better release notes for ActiveMQ releases

2014-06-10 Thread Claus Ibsen

Hi

In the release notes for 5.10, there is only 2 items listened about
hardening X and Y
http://activemq.apache.org/activemq-5100-release.html

As its a long time since 5.9.0 was released, we know there is more to
it, than just hardening X and Y in this release.

So this is a plea from me, and other users of AMQ, can you guys please
start adding details to the release notes during development.

It gets harder to promote ActiveMQ when a new release comes out and
nobody knows what is included now.

Its just much easier to write the release notes, if developers had
added a tidbit to the docs during development, if the person though
that the change was noteworthy.

Now you can just look in the JIRAs would people say, but that is hard.
Also when people blog/tweet et all about a new ActiveMQ release, then
they need more details than just this.

I have noticed that when we do new Camel releases, then many news
sites and others write small articles about the new release, and use
the information from the release notes to say something about the
highlights.



-- 
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/

-

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

2014-06-10 Thread Jean-Baptiste Onofré


+1 (non binding)

I will fix the "Karaf/Equinox related" issue for the next release.

Regards
JB

On 06/05/2014 04:08 PM, 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/



--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

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

2014-06-10 Thread Jean-Baptiste Onofré


Hi,

I started to work on it, I will keep you posted later today.

Regards
JB

On 06/08/2014 12:35 AM, Krzysztof Sobkowiak wrote:

I think, one of the Karaf experts should look at this if this is really
an ActiveMQ issue. I'm not a Karaf expert but I feel this is rather an
issue of Karaf & Equinox and installation of ActiveMQ only triggers this
problem.

On 07.06.2014 20:30, artnaseef wrote:

Thank you for the clarification.  I have re-opened AMQ-4794 and removed the
"fixed-in" tag for 5.10.



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





--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

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

2014-06-10 Thread Claus Ibsen

Hi Arthur

Instead of adding a comment to each jira ticket about the commit. You
can get JIRA to link to it automatic when you click the source sub
tab.

But that requires AFAIR to tell JIRA to do that, and where the source
code is. Maybe INFRA can help with that.

On Wed, Jun 11, 2014 at 3:04 AM, artnaseef  wrote:
> +1 (non-binding)
>
> I was hoping to briefly review all of the jira entires, but only managed
> about 50 of them.  I will try to do more - as "life" permits.
>
>
>
> --
> View this message in context: 
> http://activemq.2283324.n4.nabble.com/VOTE-Apache-ActiveMQ-5-10-0-Release-Candidate-2-tp4681721p4681995.html
> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/

[jira] [Commented] (AMQ-4970) Deletion of a queue inaffective across broker restart

2014-06-10 Thread Arthur Naseef (JIRA)


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

Arthur Naseef commented on AMQ-4970:


Fix revision: 
https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=f7cbe9fa173f1f3cf91d016ed340f90a2bd61242

> Deletion of a queue inaffective across broker restart
> -
>
> Key: AMQ-4970
> URL: https://issues.apache.org/jira/browse/AMQ-4970
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 5.9.0
> Environment: mac osx/mavericks
>Reporter: Arthur Naseef
>Assignee: Arthur Naseef
> Fix For: 5.9.1, 5.10.0
>
> Attachments: AMQ4970Test.zip, AMQ4970Test.zip, AMQ4970Test.zip, 
> amq4970.patch
>
>
> Deleting a queue, it is revived from persistent store after a broker restart. 
>  The following steps reproduce the problem:
> * Create a queue (confirmed using the REST client I/F)
> * Shutdown the broker
> * Startup the broker
> * Confirm queue still exists via the hawtio ui (correct operation so far)
> * Delete the queue
> * Confirm queue removed via the hawtio ui
> * Shutdown the broker
> * Startup the broker
> * Confirm queue was not recreated via hawtio ui (failed: queue still exists)



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

[jira] [Commented] (AMQ-4857) WSServlet.doWebSocketConnect throws NPE if called with null protocol

2014-06-10 Thread Arthur Naseef (JIRA)


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

Arthur Naseef commented on AMQ-4857:


Fix revision: 
https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=692428eee5f7af1118881c1140ff45cd33e99d18

> WSServlet.doWebSocketConnect throws NPE if called with null protocol
> 
>
> Key: AMQ-4857
> URL: https://issues.apache.org/jira/browse/AMQ-4857
> Project: ActiveMQ
>  Issue Type: Bug
>Reporter: Kevin Earls
>Assignee: Kevin Earls
> Fix For: 5.9.1, 5.10.0
>
>
> I got the NPE shown below while working on a websocket demo.   
> WebSocketFactory.acceptWebSocket calls WSServlet.doWebSocketConnect with the 
> protocol hard coded to null.
> java.lang.NullPointerException
>   at 
> org.apache.activemq.transport.ws.WSServlet.doWebSocketConnect(WSServlet.java:54)
>   at 
> org.eclipse.jetty.websocket.WebSocketFactory.acceptWebSocket(WebSocketFactory.java:372)
>   at 
> org.eclipse.jetty.websocket.WebSocketServlet.service(WebSocketServlet.java:104)
>   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.doHandle(ServletHandler.java:445)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1044)
>   at 
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:372)
>   at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:978)
>   at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
>   at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
>   at org.eclipse.jetty.server.Server.handle(Server.java:367)
>   at 
> org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:486)
>   at 
> org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:926)
>   at 
> org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:988)
>   at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:640)
>   at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
>   at 
> org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
>   at 
> org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:628)
>   at 
> org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52)
>   at 
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
>   at 
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
>   at java.lang.Thread.run(Thread.java:744)



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

[jira] [Commented] (AMQ-4883) Fusesource release repo not needed

2014-06-10 Thread Arthur Naseef (JIRA)


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

Arthur Naseef commented on AMQ-4883:


Fix revision: 
https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=13ba3008d488161d0e18934614cf244cbc5ff722

> Fusesource release repo not needed
> --
>
> Key: AMQ-4883
> URL: https://issues.apache.org/jira/browse/AMQ-4883
> Project: ActiveMQ
>  Issue Type: Task
>Affects Versions: 5.10.0
>Reporter: Daniel Kulp
>Assignee: Claus Ibsen
> Fix For: 5.10.0
>
>
> The proton dependencies are at central.  Thus, the fusesource release repo in 
> the top level pom is no longer needed and can slow down the build (as well as 
> cause extra required configuration if behind a firewall).
> {code}
> diff --git a/pom.xml b/pom.xml
> index eb05b07..ffd0bef 100755
> --- a/pom.xml
> +++ b/pom.xml
> @@ -1590,13 +1590,6 @@
>
>  
>
> -
> -
> -  com.fusesource.m2
> -  http://repo.fusesource.com/nexus/content/groups/public/
> -  true
> -  false
> -
>  
>  
>eclipse.m2
> {code}



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

[jira] [Commented] (AMQ-4892) MQTT clients disconnecting due to socket error do not publish the configured last will and testament message.

2014-06-10 Thread Arthur Naseef (JIRA)


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

Arthur Naseef commented on AMQ-4892:


Fix revision: 
https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=030c2cca31fa41dc938b7a6a5904c90bfce6dfac

Comment from the commit: "MQTT clients disconnecting due to socket error do not 
publish the configured last will and testament message."

> MQTT clients disconnecting due to socket error do not publish the configured 
> last will and testament message.
> -
>
> Key: AMQ-4892
> URL: https://issues.apache.org/jira/browse/AMQ-4892
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 5.9.0
>Reporter: Hiram Chirino
>Assignee: Hiram Chirino
> Fix For: 5.9.1, 5.10.0
>
>




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

[jira] [Commented] (AMQ-4893) UTF8Buffer should be a valid object for setObjectProperty

2014-06-10 Thread Arthur Naseef (JIRA)


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

Arthur Naseef commented on AMQ-4893:


Fix revision: 
https://git-wip-us.apache.org/repos/asf?p=activemq.git;a=commit;h=a6e306437efafc13cf2c2e9d681d5685fdfbcfce

> UTF8Buffer should be a valid object for setObjectProperty
> -
>
> Key: AMQ-4893
> URL: https://issues.apache.org/jira/browse/AMQ-4893
> Project: ActiveMQ
>  Issue Type: Bug
>  Components: JMS client
>Affects Versions: 5.8.0
>Reporter: Sam hendley
> Fix For: 5.9.1, 5.10.0
>
> Attachments: StringHeaderTest.java
>
>
> If we try to copy headers between messages using getProperties and 
> setObjectProperty with those values it now fails since the UTF8Buffer is not 
> in the whitelist of convertable types. I think it should be added as a 
> whitelisted type that gets handled like a string on setObjectProperty (and 
> probably setStringProperty). Otherwise this causes the application code to 
> have to special case String properties and couple to the hawtbuffer 
> implementation detail.



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

[jira] [Commented] (AMQ-5155) Heartbeat fails in STOMP over WebSockets

2014-06-10 Thread Timothy Bish (JIRA)


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

Timothy Bish commented on AMQ-5155:
---

Why not try and create a unit test and submit a patch that fixes it?

> Heartbeat fails in STOMP over WebSockets
> 
>
> Key: AMQ-5155
> URL: https://issues.apache.org/jira/browse/AMQ-5155
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.9.1, 5.10.0
>Reporter: Arjan van den Berg
>Priority: Minor
>
> From AMQ-4740:
> I receive the following error after establishing a connection and heartbeat 
> through stomp.js. This seems to occur after the 'PING' is sent.
> -- stomp.js output
> <<< CONNECTED
> heart-beat:1,1
> session:ID:localhost.localdomain-45596-1396530920609-2:2
> server:ActiveMQ/5.10-SNAPSHOT
> version:1.1
> send PING every 1ms 
> check PONG every 1ms 
> <<< PONG 
> >>> PING 
> did not receive server activity for the last 20005ms 
> Whoops! Lost connection to ws://172.16.99.73:61614/stomp
> - activemq console ---
> WARN | Transport Connection to: StompSocket_19548821 failed: 
> java.io.IOException
> Exception in thread "ActiveMQ InactivityMonitor Worker" 
> java.lang.NullPointerException
> at 
> org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:314)
> at 
> org.apache.activemq.transport.AbstractInactivityMonitor$4.run(AbstractInactivityMonitor.java:215)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> WARN | Transport Connection to: StompSocket_19548821 failed: 
> java.io.IOException
> Exception in thread "ActiveMQ InactivityMonitor Worker" 
> java.lang.NullPointerException
> at 
> org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:314)
> at 
> org.apache.activemq.transport.AbstractInactivityMonitor$4.run(AbstractInactivityMonitor.java:215)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> For me it looks as if the StompInactivityMonitor is delivering its events to 
> the wrong Transport, i.e. it needs a "narrow()" when setting it up.



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

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

2014-06-10 Thread artnaseef

+1 (non-binding)

I was hoping to briefly review all of the jira entires, but only managed
about 50 of them.  I will try to do more - as "life" permits.



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

[jira] [Commented] (AMQ-5155) Heartbeat fails in STOMP over WebSockets

2014-06-10 Thread Chad Kelly (JIRA)


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

Chad Kelly commented on AMQ-5155:
-

Someone please help resolve this ticket. The bug described above is still 
present in 5.9.1. I tried both cases, heartbeat set to 0,0 and 1,1. 
Slightly different buggy behaviors, but it still does not work. Please:
1) download 5.9.1
2) bin/activemq console xbean:examples/conf/activemq-demo.xml
3) open two browsers (firefox/chrome) to 
http://localhost:8161/demo/websocket/index.html
4) type a few messages over a 5 minute period

WARN | Transport Connection to: StompSocket_1998606381 failed: 
java.io.IOException
WARN | Transport Connection to: StompSocket_178709817 failed: 
java.io.IOException
Exception in thread "ActiveMQ InactivityMonitor Worker" 
java.lang.NullPointerException
at 
org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:314)
at 
org.apache.activemq.transport.AbstractInactivityMonitor$4.run(AbstractInactivityMonitor.java:215)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Exception in thread "ActiveMQ InactivityMonitor Worker" 
java.lang.NullPointerException
at 
org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:314)
at 
org.apache.activemq.transport.AbstractInactivityMonitor$4.run(AbstractInactivityMonitor.java:215)
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)


> Heartbeat fails in STOMP over WebSockets
> 
>
> Key: AMQ-5155
> URL: https://issues.apache.org/jira/browse/AMQ-5155
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.9.1, 5.10.0
>Reporter: Arjan van den Berg
>Priority: Minor
>
> From AMQ-4740:
> I receive the following error after establishing a connection and heartbeat 
> through stomp.js. This seems to occur after the 'PING' is sent.
> -- stomp.js output
> <<< CONNECTED
> heart-beat:1,1
> session:ID:localhost.localdomain-45596-1396530920609-2:2
> server:ActiveMQ/5.10-SNAPSHOT
> version:1.1
> send PING every 1ms 
> check PONG every 1ms 
> <<< PONG 
> >>> PING 
> did not receive server activity for the last 20005ms 
> Whoops! Lost connection to ws://172.16.99.73:61614/stomp
> - activemq console ---
> WARN | Transport Connection to: StompSocket_19548821 failed: 
> java.io.IOException
> Exception in thread "ActiveMQ InactivityMonitor Worker" 
> java.lang.NullPointerException
> at 
> org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:314)
> at 
> org.apache.activemq.transport.AbstractInactivityMonitor$4.run(AbstractInactivityMonitor.java:215)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> WARN | Transport Connection to: StompSocket_19548821 failed: 
> java.io.IOException
> Exception in thread "ActiveMQ InactivityMonitor Worker" 
> java.lang.NullPointerException
> at 
> org.apache.activemq.transport.AbstractInactivityMonitor.onException(AbstractInactivityMonitor.java:314)
> at 
> org.apache.activemq.transport.AbstractInactivityMonitor$4.run(AbstractInactivityMonitor.java:215)
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> For me it looks as if the StompInactivityMonitor is delivering its events to 
> the wrong Transport, i.e. it needs a "narrow()" when setting it up.



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

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

2014-06-10 Thread artnaseef

Thanks Dejan and Tim - I agree this jira entry should not hold up the
release.



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

[jira] [Commented] (AMQ-3883) activemq-jaas authorization doesn't work with Karaf JAAS LoginModule

2014-06-10 Thread Chris Schultz (JIRA)


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

Chris Schultz commented on AMQ-3883:


I have review the code for LDAP Authorisation (within Karaf/Fuse 6.1) and this 
also doesn't work due to using the {{map.getGroupClass()}} method.:

{code:title=SimpleCachedLDAPAuthorizationMap.java}

DefaultAuthorizationMap map = this.map.get();
if (group && !user) {
try {

members.add(DefaultAuthorizationMap.createGroupPrincipal(principalName, 
map.getGroupClass()));
} catch (Exception e) {
NamingException ne = new NamingException(
"Can't create a group " + principalName + " of 
class " + map.getGroupClass());
ne.initCause(e);
throw ne;
}
} else if (!group && user) {
members.add(new UserPrincipal(principalName));
}

{code}

> activemq-jaas authorization doesn't work with Karaf JAAS LoginModule
> 
>
> Key: AMQ-3883
> URL: https://issues.apache.org/jira/browse/AMQ-3883
> Project: ActiveMQ
>  Issue Type: Improvement
>Affects Versions: 5.6.0
>Reporter: Freeman Fang
>Assignee: Dejan Bosanac
> Fix For: 5.9.0
>
> Attachments: AMQ-3883.patch
>
>
> currently activemq-jaas can't work with karaf loginModule, the reason comes 
> from the compare between
> amq GroupPrincipal and karaf UserPrincipal/RolePrincipal doesn't work
> More details please see[1].
> We have a similar issue in Servicemix NMR[2] and the fix can honor the 
> compare between
> amq GroupPrincipal and karaf UserPrincipal/RolePrincipal yet not introduce 
> any dependency between activemq-jaas and karaf jaas.
> [1]http://karaf.922171.n3.nabble.com/Karaf-ActiveMQ-authorization-problem-td4024834.html
> [2]https://issues.apache.org/jira/browse/SMX4NMR-283



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

Build failed in Jenkins: ActiveMQ-Trunk-Deploy » ActiveMQ :: Assembly #960

2014-06-10 Thread Apache Jenkins Server

See 


--
[INFO] 
[INFO] 
[INFO] Building ActiveMQ :: Assembly 5.11-SNAPSHOT
[INFO] 
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ apache-activemq ---
[INFO] Deleting 

[INFO] 
[INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ apache-activemq ---
[INFO] 
[INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ 
apache-activemq ---
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ 
apache-activemq ---
[INFO] 
[INFO] --- maven-resources-plugin:2.5:copy-resources (copy-conf) @ 
apache-activemq ---
[debug] execute contextualize
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 17 resources
[INFO] Copying 19 resources
[INFO] 
[INFO] --- maven-compiler-plugin:2.5.1:testCompile (validate-config) @ 
apache-activemq ---
[INFO] Compiling 6 source files to 

[INFO] 
[INFO] --- maven-surefire-plugin:2.16:test (validate-config) @ apache-activemq 
---
[JENKINS] Recording test results[INFO] 
[INFO] --- maven-site-plugin:3.1:attach-descriptor (attach-descriptor) @ 
apache-activemq ---

[INFO] 
[INFO] --- maven-dependency-plugin:2.8:unpack-dependencies (unpack) @ 
apache-activemq ---
[INFO] Unpacking 
/home/jenkins/jenkins-slave/workspace/ActiveMQ-Trunk-Deploy/activemq-console/target/activemq-console-5.11-SNAPSHOT.jar
 to 

 with includes "" and excludes ""
[INFO] 
[INFO] --- maven-enforcer-plugin:1.0.1:enforce (default) @ apache-activemq ---
[INFO] 
[INFO] --- maven-bundle-plugin:2.3.7:cleanVersions (cleanVersions) @ 
apache-activemq ---
[WARNING] Failed to getClass for org.apache.maven.plugin.source.SourceJarMojo
[INFO] 
[INFO] --- maven-source-plugin:2.2.1:jar (attach-sources) @ apache-activemq ---
[INFO] 
[INFO] --- maven-javadoc-plugin:2.8.1:jar (attach-javadocs) @ apache-activemq 
---
[INFO] Not executing Javadoc as the project is not a Java classpath-capable 
package
[INFO] 
[INFO] --- maven-assembly-plugin:2.4:attached (unix-bin) @ apache-activemq ---
[INFO] Reading assembly descriptor: src/main/descriptors/unix-bin.xml
[WARNING] Cannot include project artifact: 
org.apache.activemq:apache-activemq:pom:5.11-SNAPSHOT; it doesn't have an 
associated file or directory.
[WARNING] Cannot include project artifact: 
org.apache.activemq:apache-activemq:pom:5.11-SNAPSHOT; it doesn't have an 
associated file or directory.
[WARNING] Cannot include project artifact: 
org.apache.activemq:apache-activemq:pom:5.11-SNAPSHOT; it doesn't have an 
associated file or directory.
[WARNING] Cannot include project artifact: 
org.apache.activemq:apache-activemq:pom:5.11-SNAPSHOT; it doesn't have an 
associated file or directory.
[WARNING] Cannot include project artifact: 
org.apache.activemq:apache-activemq:pom:5.11-SNAPSHOT; it doesn't have an 
associated file or directory.
[WARNING] The following patterns were never triggered in this artifact 
inclusion filter:
o  'org.apache.qpid:proton'

[WARNING] Cannot include project artifact: 
org.apache.activemq:apache-activemq:pom:5.11-SNAPSHOT; it doesn't have an 
associated file or directory.
[WARNING] Cannot include project artifact: 
org.apache.activemq:apache-activemq:pom:5.11-SNAPSHOT; it doesn't have an 
associated file or directory.
[INFO] Building tar: 

[INFO] 
[INFO] --- maven-assembly-plugin:2.4:attached (windows-bin) @ apache-activemq 
---
[INFO] Reading assembly descriptor: src/main/descriptors/windows-bin.xml
[WARNING] Cannot include project artifact: 
org.apache.activemq:apache-activemq:pom:5.11-SNAPSHOT; it doesn't have an 
associated file or directory.
[WARNING] Cannot include project artifact: 
org.apache.activemq:apache-activemq:pom:5.11-SNAPSHOT; it doesn't have an 
associated file or directory.
[WARNING] Cannot include project artifact: 
org.apache.activemq:apache-activemq:pom:5.11-SNAPSHOT; it doesn't have an 
associated file or directory.
[WARNING] Cannot include project artifact: 
org.apache.activemq:apache-activemq:pom:5.11-SNAPSHOT; it doesn't have an 
associated file or directory.
[WARNING] Cannot include project artifact: 
org.apache.activemq:apache-activemq:pom:5.11-SNAPSHOT; it doesn't have an 
associated file or directory.
[WARNING] The following patterns were never triggered in this art

Build failed in Jenkins: ActiveMQ-Trunk-Deploy #960

2014-06-10 Thread Apache Jenkins Server

See 

Changes:

[gtully] remove duplicate slf4j-log4j12 dep b/c it is in activemq-all from 
https://issues.apache.org/jira/browse/AMQ-3715

--
[...truncated 11959 lines...]
[JENKINS] Archiving 

 to 
org.apache.activemq/activemq-runtime-config/5.11-20140610.231122-7/activemq-runtime-config-5.11-20140610.231122-7-sources.jar
[JENKINS] Archiving 

 to 
org.apache.activemq/activemq-runtime-config/5.11-20140610.231122-7/activemq-runtime-config-5.11-20140610.231122-7-javadoc.jar
Sending artifact delta relative to ActiveMQ-Trunk-Deploy ? ActiveMQ :: Runtime 
Configuration #959
Archived 4 artifacts
Archive block size is 32768
Received 2 blocks and 6575065 bytes
Compression is 1.0%
Took 5 sec
[JENKINS] Archiving 
 
to 
org.apache.activemq/activemq-pool/5.11-SNAPSHOT/activemq-pool-5.11-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.activemq/activemq-pool/5.11-20140610.230807-7/activemq-pool-5.11-20140610.230807-7.jar
[JENKINS] Archiving 

 to 
org.apache.activemq/activemq-pool/5.11-20140610.230807-7/activemq-pool-5.11-20140610.230807-7-sources.jar
[JENKINS] Archiving 

 to 
org.apache.activemq/activemq-pool/5.11-20140610.230807-7/activemq-pool-5.11-20140610.230807-7-javadoc.jar
Sending artifact delta relative to ActiveMQ-Trunk-Deploy ? ActiveMQ :: Pool #959
Archived 4 artifacts
Archive block size is 32768
Received 0 blocks and 89670 bytes
Compression is 0.0%
Took 85 ms
[JENKINS] Archiving 
 
to 
org.apache.activemq/activemq-stomp/5.11-SNAPSHOT/activemq-stomp-5.11-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.activemq/activemq-stomp/5.11-20140610.230646-7/activemq-stomp-5.11-20140610.230646-7.jar
[JENKINS] Archiving 

 to 
org.apache.activemq/activemq-stomp/5.11-20140610.230646-7/activemq-stomp-5.11-20140610.230646-7-sources.jar
[JENKINS] Archiving 

 to 
org.apache.activemq/activemq-stomp/5.11-20140610.230646-7/activemq-stomp-5.11-20140610.230646-7-javadoc.jar
Sending artifact delta relative to ActiveMQ-Trunk-Deploy ? ActiveMQ :: STOMP 
Protocol #959
Archived 4 artifacts
Archive block size is 32768
Received 0 blocks and 398556 bytes
Compression is 0.0%
Took 0.18 sec
[JENKINS] Archiving 

 to 
org.apache.activemq/activemq-run/5.11-SNAPSHOT/activemq-run-5.11-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.activemq/activemq-run/5.11-20140610.231037-7/activemq-run-5.11-20140610.231037-7.jar
Sending artifact delta relative to ActiveMQ-Trunk-Deploy ? ActiveMQ :: Run Jar 
#959
Archived 2 artifacts
Archive block size is 32768
Received 0 blocks and 19027 bytes
Compression is 0.0%
Took 50 ms
[JENKINS] Archiving 
 
to 
org.apache.activemq/activemq-mqtt/5.11-SNAPSHOT/activemq-mqtt-5.11-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.activemq/activemq-mqtt/5.11-20140610.230655-7/activemq-mqtt-5.11-20140610.230655-7.jar
[JENKINS] Archiving 

 to 
org.apache.activemq/activemq-mqtt/5.11-20140610.230655-7/activemq-mqtt-5.11-20140610.230655-7-sources.jar
[JENKINS] Archiving 

 to 
org.apache.activemq/activemq-mqtt/5.11-20140610.230655-7/activemq-mqtt-5.11-20140610.230655-7-javadoc.jar
Sending artifact delta relative to ActiveMQ-Trunk-Deploy ? ActiveMQ :: MQTT 
Protocol #959
Archived 4 artifacts
Archive

[ANNOUNCE] Apache ActiveMQ 5.10.0

2014-06-10 Thread Dejan Bosanac

The Apache ActiveMQ team is proud to announce the release of Apache
ActiveMQ 5.10.0.

This release addresses over 200 issues and introduces many improvements
particularly in MQTT and AMQP support.

Full details and download link can be found in the release page:
http://activemq.apache.org/activemq-5100-release.html

The full list of resolved issues is at:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311210&version=12324950



A big thanks to everyone who contributed to this release.

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/

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

2014-06-10 Thread Dejan Bosanac

Hi Paul,

it’s a new feature request and there’s no work being done on it, so it’s
not something that should block the release. If you can create a patch for
this, it’d speed up the inclusion of it for the future. Contributions are
always more than welcomed.

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 Tue, Jun 10, 2014 at 3:09 PM, Paul Gale  wrote:

> I didn't really get an answer to my earlier post regarding AMQ-5174.
> Can that be included in ActiveMQ 5.10 too?
>
> Thanks,
> Paul
>
>
> On Tue, Jun 10, 2014 at 7:04 AM, Dejan Bosanac 
> wrote:
>
> > I reopened the issue and mark it for 5.11. I don’t think this issue is a
> > blocker for this release. Having said that, the vote was open for 5 days
> > with not -1s, so I’ll close it now and continue with the release.
> >
> > 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 Tue, Jun 10, 2014 at 2:46 AM, Timothy Bish 
> wrote:
> >
> > > On 06/09/2014 08:20 PM, artnaseef wrote:
> > >
> > >> Everyone voting "+1" -- what about the concern with AMQ-4277?
> > >>
> > >> Especially Claus who marked it as RESOLVED.
> > >>
> > >> Please help me to get this cleared up.
> > >>
> > >>
> > >>
> > >> --
> > >> View this message in context: http://activemq.2283324.n4.
> > >> nabble.com/VOTE-Apache-ActiveMQ-5-10-0-Release-
> > >> Candidate-2-tp4681721p4681924.html
> > >> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
> > >>
> > >>  If there's still a problem the right thing to do is reopen and work
> > > towards a unit test and a fix for the next release, v5.10.0 won't be
> the
> > > last ActiveMQ release ever.
> > >
> > >
> > > --
> > > 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/
> > >
> > >
> >
>

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

2014-06-10 Thread Paul Gale

I didn't really get an answer to my earlier post regarding AMQ-5174.
Can that be included in ActiveMQ 5.10 too?

Thanks,
Paul


On Tue, Jun 10, 2014 at 7:04 AM, Dejan Bosanac  wrote:

> I reopened the issue and mark it for 5.11. I don’t think this issue is a
> blocker for this release. Having said that, the vote was open for 5 days
> with not -1s, so I’ll close it now and continue with the release.
>
> 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 Tue, Jun 10, 2014 at 2:46 AM, Timothy Bish  wrote:
>
> > On 06/09/2014 08:20 PM, artnaseef wrote:
> >
> >> Everyone voting "+1" -- what about the concern with AMQ-4277?
> >>
> >> Especially Claus who marked it as RESOLVED.
> >>
> >> Please help me to get this cleared up.
> >>
> >>
> >>
> >> --
> >> View this message in context: http://activemq.2283324.n4.
> >> nabble.com/VOTE-Apache-ActiveMQ-5-10-0-Release-
> >> Candidate-2-tp4681721p4681924.html
> >> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
> >>
> >>  If there's still a problem the right thing to do is reopen and work
> > towards a unit test and a fix for the next release, v5.10.0 won't be the
> > last ActiveMQ release ever.
> >
> >
> > --
> > 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/
> >
> >
>

[RESULT][VOTE] Apache ActiveMQ 5.10.0

2014-06-10 Thread Dejan Bosanac

Vote passes with 8 +1 votes (Dejan, Tim, Claus, Hadrian, Gary, Hiram, Jim,
Christian) and no other votes.

I will proceed to publish the artifacts and complete the release.

Thanks to all who took the time to test the artifacts and vote.

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/

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

2014-06-10 Thread Dejan Bosanac

I reopened the issue and mark it for 5.11. I don’t think this issue is a
blocker for this release. Having said that, the vote was open for 5 days
with not -1s, so I’ll close it now and continue with the release.

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 Tue, Jun 10, 2014 at 2:46 AM, Timothy Bish  wrote:

> On 06/09/2014 08:20 PM, artnaseef wrote:
>
>> Everyone voting "+1" -- what about the concern with AMQ-4277?
>>
>> Especially Claus who marked it as RESOLVED.
>>
>> Please help me to get this cleared up.
>>
>>
>>
>> --
>> View this message in context: http://activemq.2283324.n4.
>> nabble.com/VOTE-Apache-ActiveMQ-5-10-0-Release-
>> Candidate-2-tp4681721p4681924.html
>> Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
>>
>>  If there's still a problem the right thing to do is reopen and work
> towards a unit test and a fix for the next release, v5.10.0 won't be the
> last ActiveMQ release ever.
>
>
> --
> 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/
>
>

[jira] [Updated] (AMQ-4277) activemq-web - REST GET 204

2014-06-10 Thread Dejan Bosanac (JIRA)


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

Dejan Bosanac updated AMQ-4277:
---

Fix Version/s: (was: 5.10.0)
   5.11.0

> activemq-web - REST GET 204
> ---
>
> Key: AMQ-4277
> URL: https://issues.apache.org/jira/browse/AMQ-4277
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.7.0
> Environment: windows 7 and windows xp
>Reporter: Helen Huang
>Assignee: Claus Ibsen
> Fix For: 5.11.0
>
> Attachments: AMQ4277TestPatch.txt, RestTest.java
>
>
> Using 5.7 REST API I can GET a message from a topic but if a new message is 
> POSTed to that same topic before the GET has been reissued (less than 20ms 
> behind the POST and using the same session as the previous GET) the GET will 
> timeout with a 204 and does not retrieve the message. This may be as designed 
> for topics (queues are not an option) but I am just looking for confirmation. 
> I assumed the first GET would have provided a topic subscription and the 
> broker would hold a topic message for which there is a subscriber for longer 
> than 20ms? This is not a stress test and is recreated with a simple producer 
> and a separate consumer usually within the first couple of message exchanges. 
> It has been noticed that when the topic message is POSTed without an 
> outstanding GET to receive it, the following exception is logged: 
> 2013-01-22 01:09:37,484 | DEBUG | Async client internal exception occurred 
> with no exception listener registered: java.lang.IllegalStateException: 
> DISPATCHED,initial | org.apache.activemq.ActiveMQConnection | ActiveMQ 
> Session Task-1 
> java.lang.IllegalStateException: DISPATCHED,initial 
> at 
> org.eclipse.jetty.server.AsyncContinuation.dispatch(AsyncContinuation.java:408)
>  
> at 
> org.eclipse.jetty.server.AsyncContinuation.resume(AsyncContinuation.java:815) 
> at 
> org.apache.activemq.web.MessageServlet$Listener.onMessageAvailable(MessageServlet.java:409)
>  
> at 
> org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:1343)
>  
> at 
> org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:131)
>  
> at 
> org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:202)
>  
> at 
> org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:129)
>  
> at 
> org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:47) 
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>  
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>  
> at java.lang.Thread.run(Thread.java:722) 
>   
> Are there any configuration modifications available to have the topic 
> messages retained for at least 1 second?



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

[jira] [Reopened] (AMQ-4277) activemq-web - REST GET 204

2014-06-10 Thread Dejan Bosanac (JIRA)


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

Dejan Bosanac reopened AMQ-4277:



Let's examine this issue again

> activemq-web - REST GET 204
> ---
>
> Key: AMQ-4277
> URL: https://issues.apache.org/jira/browse/AMQ-4277
> Project: ActiveMQ
>  Issue Type: Bug
>Affects Versions: 5.7.0
> Environment: windows 7 and windows xp
>Reporter: Helen Huang
>Assignee: Claus Ibsen
> Fix For: 5.10.0
>
> Attachments: AMQ4277TestPatch.txt, RestTest.java
>
>
> Using 5.7 REST API I can GET a message from a topic but if a new message is 
> POSTed to that same topic before the GET has been reissued (less than 20ms 
> behind the POST and using the same session as the previous GET) the GET will 
> timeout with a 204 and does not retrieve the message. This may be as designed 
> for topics (queues are not an option) but I am just looking for confirmation. 
> I assumed the first GET would have provided a topic subscription and the 
> broker would hold a topic message for which there is a subscriber for longer 
> than 20ms? This is not a stress test and is recreated with a simple producer 
> and a separate consumer usually within the first couple of message exchanges. 
> It has been noticed that when the topic message is POSTed without an 
> outstanding GET to receive it, the following exception is logged: 
> 2013-01-22 01:09:37,484 | DEBUG | Async client internal exception occurred 
> with no exception listener registered: java.lang.IllegalStateException: 
> DISPATCHED,initial | org.apache.activemq.ActiveMQConnection | ActiveMQ 
> Session Task-1 
> java.lang.IllegalStateException: DISPATCHED,initial 
> at 
> org.eclipse.jetty.server.AsyncContinuation.dispatch(AsyncContinuation.java:408)
>  
> at 
> org.eclipse.jetty.server.AsyncContinuation.resume(AsyncContinuation.java:815) 
> at 
> org.apache.activemq.web.MessageServlet$Listener.onMessageAvailable(MessageServlet.java:409)
>  
> at 
> org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:1343)
>  
> at 
> org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:131)
>  
> at 
> org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:202)
>  
> at 
> org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:129)
>  
> at 
> org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:47) 
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
>  
> at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
>  
> at java.lang.Thread.run(Thread.java:722) 
>   
> Are there any configuration modifications available to have the topic 
> messages retained for at least 1 second?



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

[jira] [Created] (AMQ-5220) Advisory messages are still empty when received with a Stomp subscription

2014-06-10 Thread Vladislav Krakhalev (JIRA)

Vladislav Krakhalev created AMQ-5220:


 Summary: Advisory messages are still empty when received with a 
Stomp subscription
 Key: AMQ-5220
 URL: https://issues.apache.org/jira/browse/AMQ-5220
 Project: ActiveMQ
  Issue Type: Bug
  Components: Transport
Affects Versions: 5.x
 Environment: ActiveMQ 5.9.1, Sun Java 1.7.0_51, Ubuntu Linux
Reporter: Vladislav Krakhalev


The subject of this task similiar as AMQ-2098. Bug still exists, and it can be 
reproduced according to steps below.

This simple script written in PHP uses standard Stomp client
{code}
$stomp   = new \Stomp('tcp://localhost:61613', 'admin', 'admin');
$stomp->subscribe('/topic/stats');

$stomp->begin($transaction = microtime(true));
$status = $stomp->send('/queue/ActiveMQ.Statistics.Destination.testqueue', '', 
Array('reply-to' => '/topic/stats', 'persistent' => 'true'));

$message = $stomp->readFrame();
$stomp->ack($message->headers['message-id']);
$stomp->commit($transaction);
{code}
And in $message we'll have empty body paramter. It's because ActiveMQ returned 
message without body that's show in a captured packets between ActiveMQ and PHP 
communication below
{code}
T 127.0.0.1:53988 -> 127.0.0.1:61613 [AP]
CONNECT
login:admin
passcode:admin

T 127.0.0.1:53988 -> 127.0.0.1:61613 [AP]
.

T 127.0.0.1:61613 -> 127.0.0.1:53988 [AP]
CONNECTED
heart-beat:0,0
session:ID:amneziac-59996-1402320672417-5:8
server:ActiveMQ/5.9.1
version:1.0
.

T 127.0.0.1:53988 -> 127.0.0.1:61613 [AP]
SUBSCRIBE
ack:client
destination:/topic/stats
activemq.prefetchSize:1

T 127.0.0.1:53988 -> 127.0.0.1:61613 [AP]
.

T 127.0.0.1:53988 -> 127.0.0.1:61613 [AP]
BEGIN
transaction:1402321825.9952

T 127.0.0.1:53988 -> 127.0.0.1:61613 [AP]
.

T 127.0.0.1:53988 -> 127.0.0.1:61613 [AP]
SEND
reply-to:/topic/stats
persistent:true
destination:/queue/ActiveMQ.Statistics.Destination.testqueue

T 127.0.0.1:53988 -> 127.0.0.1:61613 [AP]
.

T 127.0.0.1:61613 -> 127.0.0.1:53988 [AP]
MESSAGE
message-id:ID:amneziac-59996-1402320672417-2:1:0:0:8
type:Advisory
destination:/topic/stats
timestamp:1402321826311
expires:0
priority:4
.

T 127.0.0.1:53988 -> 127.0.0.1:61613 [AP]
ACK
message-id:ID:amneziac-59996-1402320672417-2:1:0:0:8

T 127.0.0.1:53988 -> 127.0.0.1:61613 [AP]
.

T 127.0.0.1:53988 -> 127.0.0.1:61613 [AP]
COMMIT
transaction:1402321825.9952

T 127.0.0.1:53988 -> 127.0.0.1:61613 [AFP]
.
DISCONNECT
{code}



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

Build failed in Jenkins: ActiveMQ #1458

2014-06-10 Thread Apache Jenkins Server

See 

Changes:

[gtully] test case that shows something is wrong with start logic on pooled 
connection factory, the vm test variant was getting serialized on the broker vm 
transport server

[tabish121] Convert the JUnit 4 test so that the ignore is honoered.

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

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

--
[...truncated 3211 lines...]
at java.util.concurrent.FutureTask.get(FutureTask.java:83)
at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:300)
... 37 more
Caused by: java.lang.RuntimeException: The forked VM terminated without saying 
properly goodbye. VM crash or System.exit called ?
Command was/bin/sh -c cd 
 && 
/home/jenkins/tools/java/jdk1.6.0_45-32/jre/bin/java -Xmx512m -jar 

 

 

at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:485)
at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.fork(ForkStarter.java:352)
at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter.access$300(ForkStarter.java:85)
at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter$2.call(ForkStarter.java:288)
at 
org.apache.maven.plugin.surefire.booterclient.ForkStarter$2.call(ForkStarter.java:283)
... 5 more
[ERROR] 
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :activemq-unit-tests
[JENKINS] Archiving 
 to 
org.apache.activemq/activemq-unit-tests/5.11-SNAPSHOT/activemq-unit-tests-5.11-SNAPSHOT.pom
Sending artifact delta relative to ActiveMQ ? ActiveMQ :: Unit Tests #1439
Archived 1 artifacts
Archive block size is 32768
Received 0 blocks and 60502 bytes
Compression is 0.0%
Took 0.39 sec
[JENKINS] Archiving 
 to 
org.apache.activemq/activemq-openwire-legacy/5.11-SNAPSHOT/activemq-openwire-legacy-5.11-SNAPSHOT.pom
[JENKINS] Archiving 

 to 
org.apache.activemq/activemq-openwire-legacy/5.11-SNAPSHOT/activemq-openwire-legacy-5.11-SNAPSHOT.jar
No artifacts from ActiveMQ ? ActiveMQ :: Openwire Legacy Support #1457 to 
compare, so performing full copy of artifacts
[JENKINS] Archiving 
 to 
org.apache.activemq/activemq-web-console/5.11-SNAPSHOT/activemq-web-console-5.11-SNAPSHOT.pom
Sending artifact delta relative to ActiveMQ ? ActiveMQ :: Web Console #1439
Archived 1 artifacts
Archive block size is 32768
Received 0 blocks and 10330 bytes
Compression is 0.0%
Took 2.8 sec
[JENKINS] Archiving 
 to 
org.apache.activemq/activemq-web-demo/5.11-SNAPSHOT/activemq-web-demo-5.11-SNAPSHOT.pom
Sending artifact delta relative to ActiveMQ ? ActiveMQ :: Web Demo #1439
Archived 1 artifacts
Archive block size is 32768
Received 0 blocks and 8321 bytes
Compression is 0.0%
Took 0.32 sec
[JENKINS] Archiving 
 to 
org.apache.activemq/activemq-osgi/5.11-SNAPSHOT/activemq-osgi-5.11-SNAPSHOT.pom
Sending artifact delta relative to ActiveMQ ? ActiveMQ :: OSGi bundle #1439
Archived 1 artifacts
Archive block size is 32768
Received 0 blocks and 19690 bytes
Compression is 0.0%
Took 2.6 sec
[JENKINS] Archiving 

 to 
org.apache.activemq.tooling/activemq-maven-plugin/5.11-SNAPSHOT/activemq-maven-plugin-5.11-SNAPSHOT.pom
Sending artifact delta relative to ActiveMQ ? ActiveMQ :: StartUp/Stop Plugin 
#1439
Archived 1 artifacts
Archive block size is 32768
Received 0 blocks and 3037 bytes
Compression is 0.0%
Took 0.2 sec
[JENKINS] Archiving 
 
to 
org.apache.activemq/activemq-openwire-generator/5.11-SNAPSHOT/activemq-openwire-generator-5.11-SNAPSHOT.pom
[JENKINS] Arch

Jenkins build is back to stable : ActiveMQ » ActiveMQ :: Runtime Configuration #1458

2014-06-10 Thread Apache Jenkins Server

See

Jenkins build is back to stable : ActiveMQ » ActiveMQ :: AMQP #1458

2014-06-10 Thread Apache Jenkins Server

See

Jenkins build became unstable: ActiveMQ » ActiveMQ :: RA #1458

2014-06-10 Thread Apache Jenkins Server

See

Jenkins build is back to stable : ActiveMQ » ActiveMQ :: LevelDB Store #1458

2014-06-10 Thread Apache Jenkins Server

See

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

2014-06-10 Thread Apache Jenkins Server

See 


Changes:

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

--
[...truncated 815 lines...]
[06:32:49] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.19 
sec - in org.apache.activemq.bugs.AMQ5136Test
[06:32:50] Running org.apache.activemq.bugs.AMQ5212Test
[06:33:10] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
20.212 sec - in org.apache.activemq.bugs.AMQ5212Test
[06:33:11] Running org.apache.activemq.bugs.ActiveMQSlowConsumerManualTest
[06:33:22] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
11.307 sec - in org.apache.activemq.bugs.ActiveMQSlowConsumerManualTest
[06:33:23] Running org.apache.activemq.bugs.ConnectionPerMessageTest
[06:33:30] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
7.412 sec - in org.apache.activemq.bugs.ConnectionPerMessageTest
[06:33:30] Running org.apache.activemq.bugs.CraigsBugTest
[06:33:34] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
4.001 sec - in org.apache.activemq.bugs.CraigsBugTest
[06:33:35] Running org.apache.activemq.bugs.DoubleExpireTest
[06:34:36] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
61.055 sec - in org.apache.activemq.bugs.DoubleExpireTest
[06:34:37] Running org.apache.activemq.bugs.DurableConsumerTest
[06:38:40] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
243.558 sec - in org.apache.activemq.bugs.DurableConsumerTest
[06:38:41] Running org.apache.activemq.bugs.JMSDurableTopicNoLocalTest
[06:38:48] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
7.091 sec - in org.apache.activemq.bugs.JMSDurableTopicNoLocalTest
[06:38:48] Running org.apache.activemq.bugs.JmsDurableTopicSlowReceiveTest
[06:40:42] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
113.406 sec - in org.apache.activemq.bugs.JmsDurableTopicSlowReceiveTest
[06:40:42] Running org.apache.activemq.bugs.JmsTimeoutTest
[06:40:58] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
16.34 sec - in org.apache.activemq.bugs.JmsTimeoutTest
[06:40:59] Running org.apache.activemq.bugs.MemoryUsageBlockResumeTest
[06:41:05] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
5.804 sec - in org.apache.activemq.bugs.MemoryUsageBlockResumeTest
[06:41:05] Running org.apache.activemq.bugs.MemoryUsageBrokerTest
[06:42:45] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
100.212 sec - in org.apache.activemq.bugs.MemoryUsageBrokerTest
[06:42:46] Running org.apache.activemq.bugs.MemoryUsageCleanupTest
[06:46:20] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
214.375 sec - in org.apache.activemq.bugs.MemoryUsageCleanupTest
[06:46:21] Running org.apache.activemq.bugs.MessageExpirationReaperTest
[06:46:31] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
9.658 sec - in org.apache.activemq.bugs.MessageExpirationReaperTest
[06:46:31] Running org.apache.activemq.bugs.MissingDataFileTest
[06:52:26] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
354.389 sec - in org.apache.activemq.bugs.MissingDataFileTest
[06:52:27] Running 
org.apache.activemq.bugs.OptimizeAcknowledgeWithExpiredMsgsTest
[06:52:30] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
3.491 sec - in org.apache.activemq.bugs.OptimizeAcknowledgeWithExpiredMsgsTest
[06:52:30] Running org.apache.activemq.bugs.QueueWorkerPrefetchTest
[06:52:32] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.17 
sec - in org.apache.activemq.bugs.QueueWorkerPrefetchTest
[06:52:32] Running org.apache.activemq.bugs.RedeliveryPluginHeaderTest
[06:52:40] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
8.068 sec - in org.apache.activemq.bugs.RedeliveryPluginHeaderTest
[06:52:41] Running org.apache.activemq.bugs.SlowConsumerTest
[06:54:36] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
115.537 sec <<< FAILURE! - in org.apache.activemq.bugs.SlowConsumerTest
[06:54:36] testRemoveSubscriber(org.apache.activemq.bugs.SlowConsumerTest)  
Time elapsed: 115.375 sec  <<< FAILURE!
[06:54:36] junit.framework.AssertionFailedError: expected:<1> but was:<2217>
[06:54:36]  at junit.framework.Assert.fail(Assert.java:57)
[06:54:36]  at junit.framework.Assert.failNotEquals(Assert.java:329)
[06:54:36]  at junit.framework.Assert.assertEquals(Assert.java:78)
[06:54:36]  at junit.framework.Assert.assertEquals(Assert.java:234)
[06:54:36]  at junit.framework.Assert.assertEquals(Assert.java:241)
[06:54:36]  at junit.framework.TestCase.assertEquals(TestCase.java:409)
[06:54:36]  at 
org.apache.activemq.bugs.SlowConsumerTest.testRemoveSubscriber(SlowConsumerTest.java:124)
[06:54:36] 
[06:54:44] Running 
org.apache.activemq.bugs.SparseAckReplayAfterStoreCleanupLevelDBStoreTest
[06:55:00] Tests run: 2, Failures: 0, Errors

Jenkins build became unstable: ActiveMQ » ActiveMQ :: MQTT Protocol #1458

2014-06-10 Thread Apache Jenkins Server

See

Better release notes for ActiveMQ releases

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

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

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

[jira] [Commented] (AMQ-4970) Deletion of a queue inaffective across broker restart

[jira] [Commented] (AMQ-4857) WSServlet.doWebSocketConnect throws NPE if called with null protocol

[jira] [Commented] (AMQ-4883) Fusesource release repo not needed

[jira] [Commented] (AMQ-4892) MQTT clients disconnecting due to socket error do not publish the configured last will and testament message.

[jira] [Commented] (AMQ-4893) UTF8Buffer should be a valid object for setObjectProperty

[jira] [Commented] (AMQ-5155) Heartbeat fails in STOMP over WebSockets

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

[jira] [Commented] (AMQ-5155) Heartbeat fails in STOMP over WebSockets

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

[jira] [Commented] (AMQ-3883) activemq-jaas authorization doesn't work with Karaf JAAS LoginModule

Build failed in Jenkins: ActiveMQ-Trunk-Deploy » ActiveMQ :: Assembly #960

Build failed in Jenkins: ActiveMQ-Trunk-Deploy #960

[ANNOUNCE] Apache ActiveMQ 5.10.0

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

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

[RESULT][VOTE] Apache ActiveMQ 5.10.0

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

[jira] [Updated] (AMQ-4277) activemq-web - REST GET 204

[jira] [Reopened] (AMQ-4277) activemq-web - REST GET 204

[jira] [Created] (AMQ-5220) Advisory messages are still empty when received with a Stomp subscription

Build failed in Jenkins: ActiveMQ #1458

Jenkins build is back to stable : ActiveMQ » ActiveMQ :: Runtime Configuration #1458

Jenkins build is back to stable : ActiveMQ » ActiveMQ :: AMQP #1458

Jenkins build became unstable: ActiveMQ » ActiveMQ :: RA #1458

Jenkins build is back to stable : ActiveMQ » ActiveMQ :: LevelDB Store #1458

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

Jenkins build became unstable: ActiveMQ » ActiveMQ :: MQTT Protocol #1458

31 matches

Site Navigation

Mail list logo

Footer information