[jira] [Updated] (ARTEMIS-283) Protocol independent JMSMessageID from management interface

2015-10-27 Thread Petter Nordlander (JIRA) 

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

Petter Nordlander updated ARTEMIS-283:
--
Description: 
The Management interface (JMX) has a listMessagesAsJSON operation on JMS queues.

Listing JMS messages would not make sense if there is not a JMSMessageID to 
correlate with. This works only for messages produced with Artemis "Core JMS" 
protocol (i.e. HornetQ wire protocol). Messages produced with AMQP (proton) and 
OpenWire JMS clients does not contain the JMSMessageID property. 

This property is vital to make GUIs, management scripts and whatnot.


Example:

Three messages in the following order: Artemis JMS, OpenWire, AMQP
{code:javascript}
[
{
"JMSPriority":4,
"JMSMessageID":"ID:11d61bfc-7c8f-11e5-b67d-fbf95a4499b8",
"address":"jms.queue.a1",
"JMSExpiration":0,
"__AMQ_CID":"11d1d638-7c8f-11e5-b67d-fbf95a4499b8",
"JMSTimestamp":1445938962608,
"messageID":134336,
"JMSDeliveryMode":"PERSISTENT"
},
{
"address":"jms.queue.a1",
"JMSExpiration":0,
"JMSTimestamp":1445938969309,

"__HDR_MARSHALL_PROP":[0,0,0,1,0,6,118,101,110,100,111,114,9,0,3,97,109,113],
"messageID":134354,
"__HDR_GROUP_SEQUENCE":0,

"__HDR_PRODUCER_ID":[0,0,0,61,123,1,43,0,52,73,68,58,80,101,116,116,101,114,115,45,77,97,99,66,111,111,107,45,80,114,111,46,108,111,99,97,108,45,54,52,53,55,52,45,49,52,52,53,57,51,56,57,54,57,49,53,54,45,49,58,49,0,1,0,1],
"JMSDeliveryMode":"PERSISTENT",
"JMSPriority":4,
"__HDR_COMMAND_ID":6,
"__HDR_ARRIVAL":0,
"__HDR_REDELIVER_COUNTER":0,

"__HDR_MESSAGE_ID":[0,0,0,65,110,2,-82,2,123,0,52,73,68,58,80,101,116,116,101,114,115,45,77,97,99,66,111,111,107,45,80,114,111,46,108,111,99,97,108,45,54,52,53,55,52,45,49,52,52,53,57,51,56,57,54,57,49,53,54,45,49,58,49,0,1,0,1,0,1],
"__HDR_DROPPABLE":false,
"__HDR_BROKER_IN_TIME":1445938969310
},
{
"JMS_AMQP_NATIVE":false,
"JMSPriority":4,
"address":"jms.queue.a1",
"JMSExpiration":0,
"JMS_AMQP_MESSAGE_FORMAT":0,
"JMSTimestamp":1445939704838,
"messageID":134376,
"JMSDeliveryMode":"PERSISTENT"
}
]
{code}

Corresponding Message Ids would be (read from JMS interface).

Core: JMSMessageID: 783cf118-7c91-11e5-9a09-b3c5f39ba469:0:0:-1
OpenWire: JMSMessageID: 
ID:Petters-MacBook-Pro.local-64574-1445938969156-1:1:1:1:1
AMQP: JMSMessageID: 783d1829-7c91-11e5-9a09-b3c5f39ba469:0:0:-1

So. The idea is correct this and make a 1-1 relation between JMSMessageID 
listed from the management interface with the real JMSMessageID used by JMS 
clients. I.e. It should be possible to list message id:s and browse the 
corresponding messages using a JMS client with selector.


Use case: Management script, GUIs etc.


  was:
The Management interface (JMX) has a listMessagesAsJSON operation on JMS queues.

Listing JMS messages would not make sense if there is not a JMSMessageID to 
correlate with. This works only for messages produced with Artemis "Core JMS" 
protocol (i.e. HornetQ wire protocol). Messages produced with AMQP (proton) and 
OpenWire JMS clients does not contain the JMSMessageID property. 

This property is vital to make GUIs, management scripts and whatnot.


Example:

Three messages in the following order: Artemis JMS, OpenWire, AMQP
{code:json}
[
{
"JMSPriority":4,
"JMSMessageID":"ID:11d61bfc-7c8f-11e5-b67d-fbf95a4499b8",
"address":"jms.queue.a1",
"JMSExpiration":0,
"__AMQ_CID":"11d1d638-7c8f-11e5-b67d-fbf95a4499b8",
"JMSTimestamp":1445938962608,
"messageID":134336,
"JMSDeliveryMode":"PERSISTENT"
},
{
"address":"jms.queue.a1",
"JMSExpiration":0,
"JMSTimestamp":1445938969309,

"__HDR_MARSHALL_PROP":[0,0,0,1,0,6,118,101,110,100,111,114,9,0,3,97,109,113],
"messageID":134354,
"__HDR_GROUP_SEQUENCE":0,

"__HDR_PRODUCER_ID":[0,0,0,61,123,1,43,0,52,73,68,58,80,101,116,116,101,114,115,45,77,97,99,66,111,111,107,45,80,114,111,46,108,111,99,97,108,45,54,52,53,55,52,45,49,52,52,53,57,51,56,57,54,57,49,53,54,45,49,58,49,0,1,0,1],
"JMSDeliveryMode":"PERSISTENT",
"JMSPriority":4,
"__HDR_COMMAND_ID":6,
"__HDR_ARRIVAL":0,
"__HDR_REDELIVER_COUNTER":0,

[jira] [Created] (ARTEMIS-283) Protocol independent JMSMessageID from management interface

2015-10-27 Thread Petter Nordlander (JIRA) 
Petter Nordlander created ARTEMIS-283:
-

 Summary: Protocol independent JMSMessageID from management 
interface
 Key: ARTEMIS-283
 URL: https://issues.apache.org/jira/browse/ARTEMIS-283
 Project: ActiveMQ Artemis
  Issue Type: Bug
  Components: Broker
Affects Versions: 1.1.0
Reporter: Petter Nordlander
Priority: Minor


The Management interface (JMX) has a listMessagesAsJSON operation on JMS queues.

Listing JMS messages would not make sense if there is not a JMSMessageID to 
correlate with. This works only for messages produced with Artemis "Core JMS" 
protocol (i.e. HornetQ wire protocol). Messages produced with AMQP (proton) and 
OpenWire JMS clients does not contain the JMSMessageID property. 

This property is vital to make GUIs, management scripts and whatnot.


Example:

Three messages in the following order: Artemis JMS, OpenWire, AMQP
{code:json}
[
{
"JMSPriority":4,
"JMSMessageID":"ID:11d61bfc-7c8f-11e5-b67d-fbf95a4499b8",
"address":"jms.queue.a1",
"JMSExpiration":0,
"__AMQ_CID":"11d1d638-7c8f-11e5-b67d-fbf95a4499b8",
"JMSTimestamp":1445938962608,
"messageID":134336,
"JMSDeliveryMode":"PERSISTENT"
},
{
"address":"jms.queue.a1",
"JMSExpiration":0,
"JMSTimestamp":1445938969309,

"__HDR_MARSHALL_PROP":[0,0,0,1,0,6,118,101,110,100,111,114,9,0,3,97,109,113],
"messageID":134354,
"__HDR_GROUP_SEQUENCE":0,

"__HDR_PRODUCER_ID":[0,0,0,61,123,1,43,0,52,73,68,58,80,101,116,116,101,114,115,45,77,97,99,66,111,111,107,45,80,114,111,46,108,111,99,97,108,45,54,52,53,55,52,45,49,52,52,53,57,51,56,57,54,57,49,53,54,45,49,58,49,0,1,0,1],
"JMSDeliveryMode":"PERSISTENT",
"JMSPriority":4,
"__HDR_COMMAND_ID":6,
"__HDR_ARRIVAL":0,
"__HDR_REDELIVER_COUNTER":0,

"__HDR_MESSAGE_ID":[0,0,0,65,110,2,-82,2,123,0,52,73,68,58,80,101,116,116,101,114,115,45,77,97,99,66,111,111,107,45,80,114,111,46,108,111,99,97,108,45,54,52,53,55,52,45,49,52,52,53,57,51,56,57,54,57,49,53,54,45,49,58,49,0,1,0,1,0,1],
"__HDR_DROPPABLE":false,
"__HDR_BROKER_IN_TIME":1445938969310
},
{
"JMS_AMQP_NATIVE":false,
"JMSPriority":4,
"address":"jms.queue.a1",
"JMSExpiration":0,
"JMS_AMQP_MESSAGE_FORMAT":0,
"JMSTimestamp":1445939704838,
"messageID":134376,
"JMSDeliveryMode":"PERSISTENT"
}
]
{code}

Corresponding Message Ids would be (read from JMS interface).

Core: JMSMessageID: 783cf118-7c91-11e5-9a09-b3c5f39ba469:0:0:-1
OpenWire: JMSMessageID: 
ID:Petters-MacBook-Pro.local-64574-1445938969156-1:1:1:1:1
AMQP: JMSMessageID: 783d1829-7c91-11e5-9a09-b3c5f39ba469:0:0:-1

So. The idea is correct this and make a 1-1 relation between JMSMessageID 
listed from the management interface with the real JMSMessageID used by JMS 
clients. I.e. It should be possible to list message id:s and browse the 
corresponding messages using a JMS client with selector.


Use case: Management script, GUIs etc.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (ARTEMIS-283) Protocol independent JMSMessageID from management interface

2015-10-27 Thread Petter Nordlander (JIRA) 

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

Petter Nordlander updated ARTEMIS-283:
--
Description: 
The Management interface (JMX) has a listMessagesAsJSON operation on JMS queues.

Listing JMS messages would not make sense if there is not a JMSMessageID to 
correlate with. This works only for messages produced with Artemis "Core JMS" 
protocol (i.e. HornetQ wire protocol). Messages produced with AMQP (proton) and 
OpenWire JMS clients does not contain the JMSMessageID property. 

This property is vital to make GUIs, management scripts and whatnot.


Example:

Three messages in the following order: Artemis JMS, OpenWire, AMQP
{code:javascript}
[
{
"JMSPriority":4,
"JMSMessageID":"ID:11d61bfc-7c8f-11e5-b67d-fbf95a4499b8",
"address":"jms.queue.a1",
"JMSExpiration":0,
"__AMQ_CID":"11d1d638-7c8f-11e5-b67d-fbf95a4499b8",
"JMSTimestamp":1445938962608,
"messageID":134336,
"JMSDeliveryMode":"PERSISTENT"
},
{
"address":"jms.queue.a1",
"JMSExpiration":0,
"JMSTimestamp":1445938969309,

"__HDR_MARSHALL_PROP":[0,0,0,1,0,6,118,101,110,100,111,114,9,0,3,97,109,113],
"messageID":134354,
"__HDR_GROUP_SEQUENCE":0,

"__HDR_PRODUCER_ID":[0,0,0,61,123,1,43,0,52,73,68,58,80,101,116,116,101,114,115,45,77,97,99,66,111,111,107,45,80,114,111,46,108,111,99,97,108,45,54,52,53,55,52,45,49,52,52,53,57,51,56,57,54,57,49,53,54,45,49,58,49,0,1,0,1],
"JMSDeliveryMode":"PERSISTENT",
"JMSPriority":4,
"__HDR_COMMAND_ID":6,
"__HDR_ARRIVAL":0,
"__HDR_REDELIVER_COUNTER":0,

"__HDR_MESSAGE_ID":[0,0,0,65,110,2,-82,2,123,0,52,73,68,58,80,101,116,116,101,114,115,45,77,97,99,66,111,111,107,45,80,114,111,46,108,111,99,97,108,45,54,52,53,55,52,45,49,52,52,53,57,51,56,57,54,57,49,53,54,45,49,58,49,0,1,0,1,0,1],
"__HDR_DROPPABLE":false,
"__HDR_BROKER_IN_TIME":1445938969310
},
{
"JMS_AMQP_NATIVE":false,
"JMSPriority":4,
"address":"jms.queue.a1",
"JMSExpiration":0,
"JMS_AMQP_MESSAGE_FORMAT":0,
"JMSTimestamp":1445939704838,
"messageID":134376,
"JMSDeliveryMode":"PERSISTENT"
}
]
{code}

Corresponding Message Ids would be (read from JMS interface).

Core: JMSMessageID: 783cf118-7c91-11e5-9a09-b3c5f39ba469:0:0:-1
OpenWire: JMSMessageID: 
ID:Petters-MacBook-Pro.local-64574-1445938969156-1:1:1:1:1
AMQP: JMSMessageID: 783d1829-7c91-11e5-9a09-b3c5f39ba469:0:0:-1

Problem is in QueueCtrlImpl which uses core-jms-client to convert messages from 
core to Jms Map. It consider all messages as core messages. Logic from each 
protocol/client should be used on respective message.

Map jmsMessage = 
ActiveMQMessage.coreMaptoJMSMap(coreMessage);


  was:
The Management interface (JMX) has a listMessagesAsJSON operation on JMS queues.

Listing JMS messages would not make sense if there is not a JMSMessageID to 
correlate with. This works only for messages produced with Artemis "Core JMS" 
protocol (i.e. HornetQ wire protocol). Messages produced with AMQP (proton) and 
OpenWire JMS clients does not contain the JMSMessageID property. 

This property is vital to make GUIs, management scripts and whatnot.


Example:

Three messages in the following order: Artemis JMS, OpenWire, AMQP
{code:javascript}
[
{
"JMSPriority":4,
"JMSMessageID":"ID:11d61bfc-7c8f-11e5-b67d-fbf95a4499b8",
"address":"jms.queue.a1",
"JMSExpiration":0,
"__AMQ_CID":"11d1d638-7c8f-11e5-b67d-fbf95a4499b8",
"JMSTimestamp":1445938962608,
"messageID":134336,
"JMSDeliveryMode":"PERSISTENT"
},
{
"address":"jms.queue.a1",
"JMSExpiration":0,
"JMSTimestamp":1445938969309,

"__HDR_MARSHALL_PROP":[0,0,0,1,0,6,118,101,110,100,111,114,9,0,3,97,109,113],
"messageID":134354,
"__HDR_GROUP_SEQUENCE":0,

"__HDR_PRODUCER_ID":[0,0,0,61,123,1,43,0,52,73,68,58,80,101,116,116,101,114,115,45,77,97,99,66,111,111,107,45,80,114,111,46,108,111,99,97,108,45,54,52,53,55,52,45,49,52,52,53,57,51,56,57,54,57,49,53,54,45,49,58,49,0,1,0,1],
"JMSDeliveryMode":"PERSISTENT",
"JMSPriority":4,
"__HDR_COMMAND_ID":6,
"__HDR_ARRIVAL":0,
"__HDR_REDELIVER_COUNTER":0,

[jira] [Resolved] (ARTEMIS-168) Pluggable ACL Hierarchies

2015-10-27 Thread Justin Bertram (JIRA) 

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

Justin Bertram resolved ARTEMIS-168.

Resolution: Fixed

> Pluggable ACL Hierarchies
> -
>
> Key: ARTEMIS-168
> URL: https://issues.apache.org/jira/browse/ARTEMIS-168
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: clebert suconic
>Assignee: Justin Bertram
>Priority: Critical
> Fix For: 1.3.0
>
>
> ActiveMQ5 has a way to plug the security-settings into LDAP | Files, or a 
> Pluggable ACL implementation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARTEMIS-283) Protocol independent JMSMessageID from management interface

2015-10-27 Thread Justin Bertram (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARTEMIS-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14976491#comment-14976491
 ] 

Justin Bertram commented on ARTEMIS-283:


Couple of questions:

# I don't quite understand why listing JMS messages would not make sense if 
there is not a JMSMessageID to correlate with. There are all kinds of different 
use-cases for listing messages. Can you clarify your specific use-case a bit 
more?
# I'm not sure it makes sense for a message produced with a non-JMS API to have 
a JMSMessageID.  The JMSMessageID is after all JMS-specific.

> Protocol independent JMSMessageID from management interface
> ---
>
> Key: ARTEMIS-283
> URL: https://issues.apache.org/jira/browse/ARTEMIS-283
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 1.1.0
>Reporter: Petter Nordlander
>Priority: Minor
>
> The Management interface (JMX) has a listMessagesAsJSON operation on JMS 
> queues.
> Listing JMS messages would not make sense if there is not a JMSMessageID to 
> correlate with. This works only for messages produced with Artemis "Core JMS" 
> protocol (i.e. HornetQ wire protocol). Messages produced with AMQP (proton) 
> and OpenWire JMS clients does not contain the JMSMessageID property. 
> This property is vital to make GUIs, management scripts and whatnot.
> Example:
> Three messages in the following order: Artemis JMS, OpenWire, AMQP
> {code:javascript}
> [
>   {
>   "JMSPriority":4,
>   "JMSMessageID":"ID:11d61bfc-7c8f-11e5-b67d-fbf95a4499b8",
>   "address":"jms.queue.a1",
>   "JMSExpiration":0,
>   "__AMQ_CID":"11d1d638-7c8f-11e5-b67d-fbf95a4499b8",
>   "JMSTimestamp":1445938962608,
>   "messageID":134336,
>   "JMSDeliveryMode":"PERSISTENT"
>   },
>   {
>   "address":"jms.queue.a1",
>   "JMSExpiration":0,
>   "JMSTimestamp":1445938969309,
>   
> "__HDR_MARSHALL_PROP":[0,0,0,1,0,6,118,101,110,100,111,114,9,0,3,97,109,113],
>   "messageID":134354,
>   "__HDR_GROUP_SEQUENCE":0,
>   
> "__HDR_PRODUCER_ID":[0,0,0,61,123,1,43,0,52,73,68,58,80,101,116,116,101,114,115,45,77,97,99,66,111,111,107,45,80,114,111,46,108,111,99,97,108,45,54,52,53,55,52,45,49,52,52,53,57,51,56,57,54,57,49,53,54,45,49,58,49,0,1,0,1],
>   "JMSDeliveryMode":"PERSISTENT",
>   "JMSPriority":4,
>   "__HDR_COMMAND_ID":6,
>   "__HDR_ARRIVAL":0,
>   "__HDR_REDELIVER_COUNTER":0,
>   
> "__HDR_MESSAGE_ID":[0,0,0,65,110,2,-82,2,123,0,52,73,68,58,80,101,116,116,101,114,115,45,77,97,99,66,111,111,107,45,80,114,111,46,108,111,99,97,108,45,54,52,53,55,52,45,49,52,52,53,57,51,56,57,54,57,49,53,54,45,49,58,49,0,1,0,1,0,1],
>   "__HDR_DROPPABLE":false,
>   "__HDR_BROKER_IN_TIME":1445938969310
>   },
>   {
>   "JMS_AMQP_NATIVE":false,
>   "JMSPriority":4,
>   "address":"jms.queue.a1",
>   "JMSExpiration":0,
>   "JMS_AMQP_MESSAGE_FORMAT":0,
>   "JMSTimestamp":1445939704838,
>   "messageID":134376,
>   "JMSDeliveryMode":"PERSISTENT"
>   }
> ]
> {code}
> Corresponding Message Ids would be (read from JMS interface).
> Core: JMSMessageID: 783cf118-7c91-11e5-9a09-b3c5f39ba469:0:0:-1
> OpenWire: JMSMessageID: 
> ID:Petters-MacBook-Pro.local-64574-1445938969156-1:1:1:1:1
> AMQP: JMSMessageID: 783d1829-7c91-11e5-9a09-b3c5f39ba469:0:0:-1
> Problem is in QueueCtrlImpl which uses core-jms-client to convert messages 
> from core to Jms Map. It consider all messages as core messages. Logic from 
> each protocol/client should be used on respective message.
> Map jmsMessage = 
> ActiveMQMessage.coreMaptoJMSMap(coreMessage);



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (AMQ-6022) Update Netty to version 4.0.32.Final

2015-10-27 Thread Timothy Bish (JIRA) 

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

Timothy Bish resolved AMQ-6022.
---
   Resolution: Fixed
Fix Version/s: (was: 5.12.2)
   5.13.0

> Update Netty to version 4.0.32.Final
> 
>
> Key: AMQ-6022
> URL: https://issues.apache.org/jira/browse/AMQ-6022
> Project: ActiveMQ
>  Issue Type: Sub-task
>  Components: Broker
>Reporter: Andrea Cosentino
>Priority: Minor
> Fix For: 5.13.0
>
>
> Netty-all 4.0.32.Final is out. We can use it :-)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARTEMIS-93) OSGI support

2015-10-27 Thread Justin Bertram (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARTEMIS-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14976699#comment-14976699
 ] 

Justin Bertram commented on ARTEMIS-93:
---

[~ch...@die-schneider.net], I think that would be great.

> OSGI support
> 
>
> Key: ARTEMIS-93
> URL: https://issues.apache.org/jira/browse/ARTEMIS-93
> Project: ActiveMQ Artemis
>  Issue Type: New Feature
>Affects Versions: 1.3.0
>Reporter: clebert suconic
>Priority: Critical
> Fix For: 1.3.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (ARTEMIS-284) Prevent thread interleaving on ClientConsumerImpl close methods

2015-10-27 Thread Martyn Taylor (JIRA) 
Martyn Taylor created ARTEMIS-284:
-

 Summary: Prevent thread interleaving on ClientConsumerImpl close 
methods
 Key: ARTEMIS-284
 URL: https://issues.apache.org/jira/browse/ARTEMIS-284
 Project: ActiveMQ Artemis
  Issue Type: Bug
  Components: Broker
Affects Versions: 1.1.0
Reporter: Martyn Taylor


There are situations where a consumer can be closed down from a number of 
places, for example:

* If a client topic is deleted from the server, the server issues a 
CloseConsumer packet, which will trigger the consumer to close.

* When an MDB is shutdown all Consumers assocated with the MDB are closed.

A problem arises when these things happen parrallel and multiple threads try to 
close down a consumer.  The consumer will eventually log warning messages and 
ultimately throw an error.

11:18:54,631 WARN  [org.apache.activemq.artemis.core.client] (Thread-16 
(ActiveMQ-client-global-threads-633087758)) AMQ212002: Timed out waiting for 
handler to complete processing

11:18:54,632 ERROR [org.apache.activemq.artemis.core.server] (Thread-11 
(ActiveMQ-remoting-threads-ActiveMQServerImpl::serverUUID=d370b51e-7678-11e5-b10e-af2a5d4a5196-148307791-514838245))
 AMQ224049: Cannot find consumer with id 0

Add some concurrency control around the Consumer.Close method should resolve 
this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMQ-6023) Update Snappy to version 1.1.2

2015-10-27 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on AMQ-6023:
-

Github user asfgit closed the pull request at:

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


> Update Snappy to version 1.1.2
> --
>
> Key: AMQ-6023
> URL: https://issues.apache.org/jira/browse/AMQ-6023
> Project: ActiveMQ
>  Issue Type: Sub-task
>  Components: Broker
>Reporter: Andrea Cosentino
>Priority: Minor
> Fix For: 5.12.2
>
>
> We can upgrade Snappy to version 1.1.2
> Andrea



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMQ-6022) Update Netty to version 4.0.32.Final

2015-10-27 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on AMQ-6022:
--

Commit 4d73b089230e40c003d16dbf2f3171f1e8bf07f1 in activemq's branch 
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=4d73b08 ]

AMQ-5957 AMQ-6022 AMQ-6023

Update netty, snappy, jackson, and some maven plugins to latest patch
release.

This closes #154
This closes #155

> Update Netty to version 4.0.32.Final
> 
>
> Key: AMQ-6022
> URL: https://issues.apache.org/jira/browse/AMQ-6022
> Project: ActiveMQ
>  Issue Type: Sub-task
>  Components: Broker
>Reporter: Andrea Cosentino
>Priority: Minor
> Fix For: 5.12.2
>
>
> Netty-all 4.0.32.Final is out. We can use it :-)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMQ-6023) Update Snappy to version 1.1.2

2015-10-27 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on AMQ-6023:
--

Commit 4d73b089230e40c003d16dbf2f3171f1e8bf07f1 in activemq's branch 
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=4d73b08 ]

AMQ-5957 AMQ-6022 AMQ-6023

Update netty, snappy, jackson, and some maven plugins to latest patch
release.

This closes #154
This closes #155

> Update Snappy to version 1.1.2
> --
>
> Key: AMQ-6023
> URL: https://issues.apache.org/jira/browse/AMQ-6023
> Project: ActiveMQ
>  Issue Type: Sub-task
>  Components: Broker
>Reporter: Andrea Cosentino
>Priority: Minor
> Fix For: 5.12.2
>
>
> We can upgrade Snappy to version 1.1.2
> Andrea



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMQ-5957) Update outdated dependencies used by broker.

2015-10-27 Thread ASF subversion and git services (JIRA) 

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

ASF subversion and git services commented on AMQ-5957:
--

Commit 4d73b089230e40c003d16dbf2f3171f1e8bf07f1 in activemq's branch 
refs/heads/master from [~tabish121]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=4d73b08 ]

AMQ-5957 AMQ-6022 AMQ-6023

Update netty, snappy, jackson, and some maven plugins to latest patch
release.

This closes #154
This closes #155

> Update outdated dependencies used by broker.
> 
>
> Key: AMQ-5957
> URL: https://issues.apache.org/jira/browse/AMQ-5957
> Project: ActiveMQ
>  Issue Type: Task
>  Components: Broker
>Affects Versions: 5.12.0
>Reporter: Timothy Bish
>Priority: Minor
> Fix For: 5.13.0
>
>
> Several dependencies the broker requires are out of date and should be 
> updated.  



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMQ-6022) Update Netty to version 4.0.32.Final

2015-10-27 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on AMQ-6022:
-

Github user asfgit closed the pull request at:

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


> Update Netty to version 4.0.32.Final
> 
>
> Key: AMQ-6022
> URL: https://issues.apache.org/jira/browse/AMQ-6022
> Project: ActiveMQ
>  Issue Type: Sub-task
>  Components: Broker
>Reporter: Andrea Cosentino
>Priority: Minor
> Fix For: 5.12.2
>
>
> Netty-all 4.0.32.Final is out. We can use it :-)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARTEMIS-93) OSGI support

2015-10-27 Thread Christian Schneider (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARTEMIS-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14976672#comment-14976672
 ] 

Christian Schneider commented on ARTEMIS-93:


Are you interested that I help with the OSGi enabling?

> OSGI support
> 
>
> Key: ARTEMIS-93
> URL: https://issues.apache.org/jira/browse/ARTEMIS-93
> Project: ActiveMQ Artemis
>  Issue Type: New Feature
>Affects Versions: 1.3.0
>Reporter: clebert suconic
>Priority: Critical
> Fix For: 1.3.0
>
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (AMQ-6022) Update Netty to version 4.0.32.Final

2015-10-27 Thread Andrea Cosentino (JIRA) 

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

Andrea Cosentino edited comment on AMQ-6022 at 10/27/15 4:37 PM:
-

Thank you for upgrade the dependencies.

If you think this kind of PRs are not useful, just tell me.


was (Author: ancosen):
Thank you for upgrade the dependencies.

If you think these kind of PRs are not useful, just tell me.

> Update Netty to version 4.0.32.Final
> 
>
> Key: AMQ-6022
> URL: https://issues.apache.org/jira/browse/AMQ-6022
> Project: ActiveMQ
>  Issue Type: Sub-task
>  Components: Broker
>Reporter: Andrea Cosentino
>Priority: Minor
> Fix For: 5.13.0
>
>
> Netty-all 4.0.32.Final is out. We can use it :-)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (AMQ-6023) Update Snappy to version 1.1.2

2015-10-27 Thread Timothy Bish (JIRA) 

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

Timothy Bish resolved AMQ-6023.
---
   Resolution: Fixed
Fix Version/s: (was: 5.12.2)
   5.13.0

> Update Snappy to version 1.1.2
> --
>
> Key: AMQ-6023
> URL: https://issues.apache.org/jira/browse/AMQ-6023
> Project: ActiveMQ
>  Issue Type: Sub-task
>  Components: Broker
>Reporter: Andrea Cosentino
>Priority: Minor
> Fix For: 5.13.0
>
>
> We can upgrade Snappy to version 1.1.2
> Andrea



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (AMQ-6022) Update Netty to version 4.0.32.Final

2015-10-27 Thread Andrea Cosentino (JIRA) 

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

Andrea Cosentino commented on AMQ-6022:
---

Thank you for upgrade the dependencies.

If you think these kind of PRs are not useful, just tell me.

> Update Netty to version 4.0.32.Final
> 
>
> Key: AMQ-6022
> URL: https://issues.apache.org/jira/browse/AMQ-6022
> Project: ActiveMQ
>  Issue Type: Sub-task
>  Components: Broker
>Reporter: Andrea Cosentino
>Priority: Minor
> Fix For: 5.13.0
>
>
> Netty-all 4.0.32.Final is out. We can use it :-)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (ARTEMIS-261) Allow certificate based JAAS security

2015-10-27 Thread Justin Bertram (JIRA) 

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

Justin Bertram reassigned ARTEMIS-261:
--

Assignee: Justin Bertram

> Allow certificate based JAAS security
> -
>
> Key: ARTEMIS-261
> URL: https://issues.apache.org/jira/browse/ARTEMIS-261
> Project: ActiveMQ Artemis
>  Issue Type: Improvement
>  Components: Broker
>Affects Versions: 1.1.1
>Reporter: Stephen Lewis
>Assignee: Justin Bertram
>
> ARTEMIS-74 imported ActiveMQ 5 JAAS. However, this doesn't allow certificate 
> based authentication.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (ARTEMIS-168) Pluggable ACL Hierarchies

2015-10-27 Thread Justin Bertram (JIRA) 

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

Justin Bertram reassigned ARTEMIS-168:
--

Assignee: Justin Bertram

> Pluggable ACL Hierarchies
> -
>
> Key: ARTEMIS-168
> URL: https://issues.apache.org/jira/browse/ARTEMIS-168
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: clebert suconic
>Assignee: Justin Bertram
>Priority: Critical
> Fix For: 1.3.0
>
>
> ActiveMQ5 has a way to plug the security-settings into LDAP | Files, or a 
> Pluggable ACL implementation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARTEMIS-281) JGroups channel Broadcast Endpoint reference counting broken

2015-10-27 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARTEMIS-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14976437#comment-14976437
 ] 

ASF subversion and git services commented on ARTEMIS-281:
-

Commit 290cb65b1733092344fe08b1c10e91a1a20daa30 in activemq-artemis's branch 
refs/heads/master from [~andytaylor]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=290cb65 ]

ARTEMIS-281 - fix reference counting for jgroups channels

https://issues.apache.org/jira/browse/ARTEMIS-281


> JGroups channel Broadcast Endpoint reference counting broken
> 
>
> Key: ARTEMIS-281
> URL: https://issues.apache.org/jira/browse/ARTEMIS-281
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: Andy Taylor
>Assignee: Andy Taylor
>
> this is because JGroupsChannelBroadcastEndpoint does not do anything when 
> closed so if a new channel is created with the same channel name the old one 
> is returned which may be closed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARTEMIS-282) Server lock file creation throws exception

2015-10-27 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARTEMIS-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14976440#comment-14976440
 ] 

ASF subversion and git services commented on ARTEMIS-282:
-

Commit dd402f4f9171d92594ed7b1f2f0bbd2ad8d5bbeb in activemq-artemis's branch 
refs/heads/master from [~andytaylor]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=dd402f4 ]

ARTEMIS-282 - remove unneeded check on file lock creation

https://issues.apache.org/jira/browse/ARTEMIS-282


> Server lock file creation throws exception
> --
>
> Key: ARTEMIS-282
> URL: https://issues.apache.org/jira/browse/ARTEMIS-282
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 1.1.0
>Reporter: Andy Taylor
>Assignee: Andy Taylor
>
> This is because there is a check to see if createNewFile which throws an 
> exception on false, this can be removed as another servermay have created it 
> which is fine



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARTEMIS-168) Pluggable ACL Hierarchies

2015-10-27 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARTEMIS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14976402#comment-14976402
 ] 

ASF GitHub Bot commented on ARTEMIS-168:


GitHub user jbertram opened a pull request:

https://github.com/apache/activemq-artemis/pull/220

ARTEMIS-168 - pluggable authorization

Please provide feedback on the requested changes.  The new documentation 
and JavaDoc should explain just about everything (along with the changes 
themselves).

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-168

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/activemq-artemis/pull/220.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #220


commit 6cada7bcb2e4572924704ef8f9fb0bc61d64a5cf
Author: jbertram 
Date:   2015-10-27T02:12:36Z

Fix incorrect ID on WARN message

commit 73eaea4857e5804f79c5bd8d9f0917ec0cbb2367
Author: jbertram 
Date:   2015-10-09T13:29:41Z

ARTEMIS-168 - pluggable authorization




> Pluggable ACL Hierarchies
> -
>
> Key: ARTEMIS-168
> URL: https://issues.apache.org/jira/browse/ARTEMIS-168
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: clebert suconic
>Priority: Critical
> Fix For: 1.3.0
>
>
> ActiveMQ5 has a way to plug the security-settings into LDAP | Files, or a 
> Pluggable ACL implementation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARTEMIS-282) Server lock file creation throws exception

2015-10-27 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARTEMIS-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14976436#comment-14976436
 ] 

ASF GitHub Bot commented on ARTEMIS-282:


Github user clebertsuconic commented on the pull request:

https://github.com/apache/activemq-artemis/pull/219#issuecomment-151505200
  
...merging


> Server lock file creation throws exception
> --
>
> Key: ARTEMIS-282
> URL: https://issues.apache.org/jira/browse/ARTEMIS-282
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 1.1.0
>Reporter: Andy Taylor
>Assignee: Andy Taylor
>
> This is because there is a check to see if createNewFile which throws an 
> exception on false, this can be removed as another servermay have created it 
> which is fine



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARTEMIS-282) Server lock file creation throws exception

2015-10-27 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARTEMIS-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14976439#comment-14976439
 ] 

ASF subversion and git services commented on ARTEMIS-282:
-

Commit dd402f4f9171d92594ed7b1f2f0bbd2ad8d5bbeb in activemq-artemis's branch 
refs/heads/master from [~andytaylor]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=dd402f4 ]

ARTEMIS-282 - remove unneeded check on file lock creation

https://issues.apache.org/jira/browse/ARTEMIS-282


> Server lock file creation throws exception
> --
>
> Key: ARTEMIS-282
> URL: https://issues.apache.org/jira/browse/ARTEMIS-282
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>  Components: Broker
>Affects Versions: 1.1.0
>Reporter: Andy Taylor
>Assignee: Andy Taylor
>
> This is because there is a check to see if createNewFile which throws an 
> exception on false, this can be removed as another servermay have created it 
> which is fine



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARTEMIS-281) JGroups channel Broadcast Endpoint reference counting broken

2015-10-27 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARTEMIS-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14976438#comment-14976438
 ] 

ASF subversion and git services commented on ARTEMIS-281:
-

Commit 290cb65b1733092344fe08b1c10e91a1a20daa30 in activemq-artemis's branch 
refs/heads/master from [~andytaylor]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=290cb65 ]

ARTEMIS-281 - fix reference counting for jgroups channels

https://issues.apache.org/jira/browse/ARTEMIS-281


> JGroups channel Broadcast Endpoint reference counting broken
> 
>
> Key: ARTEMIS-281
> URL: https://issues.apache.org/jira/browse/ARTEMIS-281
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: Andy Taylor
>Assignee: Andy Taylor
>
> this is because JGroupsChannelBroadcastEndpoint does not do anything when 
> closed so if a new channel is created with the same channel name the old one 
> is returned which may be closed



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARTEMIS-168) Pluggable ACL Hierarchies

2015-10-27 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARTEMIS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14976452#comment-14976452
 ] 

ASF GitHub Bot commented on ARTEMIS-168:


Github user asfgit closed the pull request at:

https://github.com/apache/activemq-artemis/pull/220


> Pluggable ACL Hierarchies
> -
>
> Key: ARTEMIS-168
> URL: https://issues.apache.org/jira/browse/ARTEMIS-168
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: clebert suconic
>Assignee: Justin Bertram
>Priority: Critical
> Fix For: 1.3.0
>
>
> ActiveMQ5 has a way to plug the security-settings into LDAP | Files, or a 
> Pluggable ACL implementation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (ARTEMIS-168) Pluggable ACL Hierarchies

2015-10-27 Thread ASF subversion and git services (JIRA) 

[ 
https://issues.apache.org/jira/browse/ARTEMIS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=14976449#comment-14976449
 ] 

ASF subversion and git services commented on ARTEMIS-168:
-

Commit fe4dafedcb5daab883694f2eaaedf3ae3dad29b8 in activemq-artemis's branch 
refs/heads/master from [~jbertram]
[ https://git-wip-us.apache.org/repos/asf?p=activemq-artemis.git;h=fe4dafe ]

ARTEMIS-168 - pluggable authorization


> Pluggable ACL Hierarchies
> -
>
> Key: ARTEMIS-168
> URL: https://issues.apache.org/jira/browse/ARTEMIS-168
> Project: ActiveMQ Artemis
>  Issue Type: Bug
>Reporter: clebert suconic
>Assignee: Justin Bertram
>Priority: Critical
> Fix For: 1.3.0
>
>
> ActiveMQ5 has a way to plug the security-settings into LDAP | Files, or a 
> Pluggable ACL implementation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)