Hiram Chirino created ACTIVEMQ6-99:
--
Summary: Support installing as a windows service
Key: ACTIVEMQ6-99
URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-99
Project: Apache ActiveMQ 6
Hiram Chirino created ACTIVEMQ6-98:
--
Summary: Make the the distro readonly and support creating mutable
broker instances dirs.
Key: ACTIVEMQ6-98
URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-98
[
https://issues.apache.org/jira/browse/AMQ-5652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino resolved AMQ-5652.
Resolution: Fixed
IdGenerator not optimal in port restricted enviroments.
[
https://issues.apache.org/jira/browse/AMQ-5652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14353269#comment-14353269
]
Hiram Chirino commented on AMQ-5652:
In some containerized environments, the IdGenerator
Hiram Chirino created AMQ-5652:
--
Summary: IdGenerator not optimal in port restricted enviroments.
Key: AMQ-5652
URL: https://issues.apache.org/jira/browse/AMQ-5652
Project: ActiveMQ
Issue Type:
[
https://issues.apache.org/jira/browse/AMQ-5458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14224801#comment-14224801
]
Hiram Chirino edited comment on AMQ-5458 at 11/26/14 3:58 PM:
--
Hiram Chirino created AMQ-5458:
--
Summary: MBean to help testing replicated levelDB
Key: AMQ-5458
URL: https://issues.apache.org/jira/browse/AMQ-5458
Project: ActiveMQ
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/AMQ-5458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino reassigned AMQ-5458:
--
Assignee: Hiram Chirino
MBean to help testing replicated levelDB
[
https://issues.apache.org/jira/browse/AMQ-5458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated AMQ-5458:
---
Fix Version/s: 5.11.0
MBean to help testing replicated levelDB
[
https://issues.apache.org/jira/browse/AMQ-5458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14224801#comment-14224801
]
Hiram Chirino commented on AMQ-5458:
Implemented. New mbean will be registered with the
Hiram Chirino created AMQ-5123:
--
Summary: Optionaly support encrypted passwords in ActiveMQ
users.properties file.
Key: AMQ-5123
URL: https://issues.apache.org/jira/browse/AMQ-5123
Project: ActiveMQ
Hiram Chirino created AMQ-5124:
--
Summary: Exception logged on startup: jolokia-agent: Cannot start
discovery multicast handler
Key: AMQ-5124
URL: https://issues.apache.org/jira/browse/AMQ-5124
Project:
[
https://issues.apache.org/jira/browse/AMQ-5123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated AMQ-5123:
---
Summary: Optionally support encrypted passwords in ActiveMQ
users.properties file. (was: Optionaly
[
https://issues.apache.org/jira/browse/AMQ-5123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino resolved AMQ-5123.
Resolution: Fixed
Implemented.
Optionally support encrypted passwords in ActiveMQ users.properties
[
https://issues.apache.org/jira/browse/AMQ-5123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13949621#comment-13949621
]
Hiram Chirino commented on AMQ-5123:
The PropertiesLoginModule now uses the
[
https://issues.apache.org/jira/browse/AMQ-5115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13943205#comment-13943205
]
Hiram Chirino commented on AMQ-5115:
This could potential lead to data loss as writes to
Hiram Chirino created AMQ-5115:
--
Summary: LevelDB sync=true is not being honored.
Key: AMQ-5115
URL: https://issues.apache.org/jira/browse/AMQ-5115
Project: ActiveMQ
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQ-5116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino resolved AMQ-5116.
Resolution: Fixed
Fix Version/s: 5.10.0
Assignee: Hiram Chirino
batchStatment is
[
https://issues.apache.org/jira/browse/AMQ-5074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino resolved AMQ-5074.
Resolution: Fixed
Assignee: Hiram Chirino
Patch applied.. Many thanks!
MQTT paths with empty
Hiram Chirino created AMQ-5072:
--
Summary: Support configuring a different directory for the KahaDB
index files.
Key: AMQ-5072
URL: https://issues.apache.org/jira/browse/AMQ-5072
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-5072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino resolved AMQ-5072.
Resolution: Fixed
kahaDB element now supports the indexDirectory attribute. If not set it falls
[
https://issues.apache.org/jira/browse/AMQ-5054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino resolved AMQ-5054.
Resolution: Fixed
Implemented.
Display the number of active transactions and age of oldest
Hiram Chirino created AMQ-5050:
--
Summary: Populate a 'Host' header in the WireFormatInfo of the
Openwire protocol to let multi-tenant proxies route connections
Key: AMQ-5050
URL:
[
https://issues.apache.org/jira/browse/AMQ-5051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino reassigned AMQ-5051:
--
Assignee: Hiram Chirino
MQTTInactivityMonitor throws a NullPointerException
Hiram Chirino created AMQ-5043:
--
Summary: Improve MQTT spec compatibility
Key: AMQ-5043
URL: https://issues.apache.org/jira/browse/AMQ-5043
Project: ActiveMQ
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQ-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13898445#comment-13898445
]
Hiram Chirino commented on AMQ-5043:
Eclipse has setup a MQTT testing suite and we are
[
https://issues.apache.org/jira/browse/AMQ-5002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13889732#comment-13889732
]
Hiram Chirino commented on AMQ-5002:
To get it working when the timestamp is set, we
[
https://issues.apache.org/jira/browse/AMQ-5002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino resolved AMQ-5002.
Resolution: Fixed
Fix committed.
AMQP: If a proton client only sets the ttl, and not the message
Hiram Chirino created AMQ-5002:
--
Summary: AMQP: If a proton client only sets the ttl, and not the
message timestamp, ActiveMQ does not handle the expiration correctly
Key: AMQ-5002
URL:
Hiram Chirino created AMQ-4990:
--
Summary: Add support for the changes in MQTT 3.1.1
Key: AMQ-4990
URL: https://issues.apache.org/jira/browse/AMQ-4990
Project: ActiveMQ
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/AMQ-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino resolved AMQ-4837.
Resolution: Fixed
Fix Version/s: 5.10.0
Marking issue as resolved since the fix was confirmed
[
https://issues.apache.org/jira/browse/AMQ-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino resolved AMQ-4917.
Resolution: Fixed
Thanks for checking the fix. Resolving as fixed.
LevelDB store can fail when
Hiram Chirino created AMQ-4922:
--
Summary: BrokerService.addConnector(URI bindAddress) binds the
port before starting the broker.
Key: AMQ-4922
URL: https://issues.apache.org/jira/browse/AMQ-4922
[
https://issues.apache.org/jira/browse/AMQ-4922?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13840289#comment-13840289
]
Hiram Chirino commented on AMQ-4922:
I've got fix started at:
Hiram Chirino created AMQ-4923:
--
Summary: Replicated LevelDB: Loss of broker Quorum fails to fully
stop the master
Key: AMQ-4923
URL: https://issues.apache.org/jira/browse/AMQ-4923
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-4923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino resolved AMQ-4923.
Resolution: Fixed
Fix Version/s: 5.10.0
Fixed.
Replicated LevelDB: Loss of broker Quorum
[
https://issues.apache.org/jira/browse/AMQ-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated AMQ-4882:
---
Summary: LevelDB can get to a corrupt state when using XA transactions
(was: LevelDB can get to a
[
https://issues.apache.org/jira/browse/AMQ-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated AMQ-4882:
---
Comment: was deleted
(was: I’m experiencing the same error using the latest 5.10-SNAPSHOT build and
[
https://issues.apache.org/jira/browse/AMQ-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated AMQ-4837:
---
Summary: LevelDB corrupted when in a replication cluster (was: LevelDB
corrupted in AMQ cluster)
Hiram Chirino created AMQ-4917:
--
Summary: LevelDB store can fail when using durable subs
Key: AMQ-4917
URL: https://issues.apache.org/jira/browse/AMQ-4917
Project: ActiveMQ
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQ-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13839034#comment-13839034
]
Hiram Chirino commented on AMQ-4837:
Tenzin, since your issue seems different I opened a
[
https://issues.apache.org/jira/browse/AMQ-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated AMQ-4917:
---
Description:
Tenzin giatso original reported this issue
Hi,
the broker stopped 3 times this night
[
https://issues.apache.org/jira/browse/AMQ-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated AMQ-4917:
---
Description:
Tenzin giatso original reported this issue in AMQ-4837 :
The broker stopped 3 times
[
https://issues.apache.org/jira/browse/AMQ-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13837814#comment-13837814
]
Hiram Chirino commented on AMQ-4837:
Hi Remo,
FYI: seems like AMQ-4882 talks about a
[
https://issues.apache.org/jira/browse/AMQ-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13837825#comment-13837825
]
Hiram Chirino commented on AMQ-4882:
Could you attach the sources to the test client?
[
https://issues.apache.org/jira/browse/AMQ-4882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13837831#comment-13837831
]
Hiram Chirino commented on AMQ-4882:
From the logs it seems the client is using XA
[
https://issues.apache.org/jira/browse/AMQ-4684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13837834#comment-13837834
]
Hiram Chirino commented on AMQ-4684:
Could you give use the full list of .nfs files
[
https://issues.apache.org/jira/browse/AMQ-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13837814#comment-13837814
]
Hiram Chirino edited comment on AMQ-4837 at 12/3/13 4:06 PM:
-
Hi
[
https://issues.apache.org/jira/browse/AMQ-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13837905#comment-13837905
]
Hiram Chirino commented on AMQ-4837:
Tenzin, how big are the messages and are you using
[
https://issues.apache.org/jira/browse/AMQ-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13831593#comment-13831593
]
Hiram Chirino commented on AMQ-4837:
Hi Tenzin,
Yeah if your setup is non-replicated,
[
https://issues.apache.org/jira/browse/AMQ-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13826530#comment-13826530
]
Hiram Chirino commented on AMQ-4837:
Ok.. so right now it just seems like the master is
[
https://issues.apache.org/jira/browse/AMQ-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13825318#comment-13825318
]
Hiram Chirino commented on AMQ-4837:
Tenzin,
Does it also happen with the following
[
https://issues.apache.org/jira/browse/AMQ-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13825318#comment-13825318
]
Hiram Chirino edited comment on AMQ-4837 at 11/18/13 1:46 PM:
--
[
https://issues.apache.org/jira/browse/AMQ-4895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13825360#comment-13825360
]
Hiram Chirino commented on AMQ-4895:
Is the ActiveMQManagedConnection.destroy() getting
Hiram Chirino created AMQ-4896:
--
Summary: MQTT does not properly restore durable subs with the Paho
client.
Key: AMQ-4896
URL: https://issues.apache.org/jira/browse/AMQ-4896
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-4896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino resolved AMQ-4896.
Resolution: Fixed
MQTT does not properly restore durable subs with the Paho client.
Hiram Chirino created AMQ-4892:
--
Summary: 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-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13814892#comment-13814892
]
Hiram Chirino edited comment on AMQ-4837 at 11/6/13 1:49 PM:
-
[
https://issues.apache.org/jira/browse/AMQ-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13814892#comment-13814892
]
Hiram Chirino commented on AMQ-4837:
Weird. I can't reproduce anymore with the latest
[
https://issues.apache.org/jira/browse/AMQ-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13811515#comment-13811515
]
Hiram Chirino commented on AMQ-4837:
Hi Guillaume,
Ok. I think I got it this time.
[
https://issues.apache.org/jira/browse/AMQ-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13810429#comment-13810429
]
Hiram Chirino commented on AMQ-4837:
unit test for this issue can be found at:
[
https://issues.apache.org/jira/browse/AMQ-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13810453#comment-13810453
]
Hiram Chirino commented on AMQ-4837:
Hi Guillaume,
I think I've fixed this issue now.
[
https://issues.apache.org/jira/browse/AMQ-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13810473#comment-13810473
]
Hiram Chirino commented on AMQ-4837:
Ah.. hold off.. I'm still seeing the issue. Need
[
https://issues.apache.org/jira/browse/AMQ-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino reassigned AMQ-4837:
--
Assignee: Hiram Chirino
Looking into it...
LevelDB corrupted in AMQ cluster
[
https://issues.apache.org/jira/browse/AMQ-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809313#comment-13809313
]
Hiram Chirino commented on AMQ-4837:
I failed to reproduce using the procedure outlined.
[
https://issues.apache.org/jira/browse/AMQ-3621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809331#comment-13809331
]
Hiram Chirino commented on AMQ-3621:
5.9 was just released so, its probably going to be
[
https://issues.apache.org/jira/browse/AMQ-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809333#comment-13809333
]
Hiram Chirino commented on AMQ-4354:
We could also just make the stats more consistent
[
https://issues.apache.org/jira/browse/AMQ-4354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809334#comment-13809334
]
Hiram Chirino commented on AMQ-4354:
Persisting the stats could have significant
Hiram Chirino created AMQ-4840:
--
Summary: Invalid STOMP frame sent on websocket connections with
heartbeats.
Key: AMQ-4840
URL: https://issues.apache.org/jira/browse/AMQ-4840
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-4840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated AMQ-4840:
---
Description: a KEEPALIVE frame was being sent by ActiveMQ to stomp
websocket clients that enabled
[
https://issues.apache.org/jira/browse/AMQ-4837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809446#comment-13809446
]
Hiram Chirino commented on AMQ-4837:
Ok. thx. I was able to reproduce.. looking into the
[
https://issues.apache.org/jira/browse/AMQ-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808422#comment-13808422
]
Hiram Chirino commented on AMQ-4833:
Its weird as the artifact is deployed in maven
[
https://issues.apache.org/jira/browse/AMQ-4833?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13808443#comment-13808443
]
Hiram Chirino commented on AMQ-4833:
On my local machine installing in karaf 2.3.3 work
Hiram Chirino created AMQ-4806:
--
Summary: './bin/activemq console' should 'exec' java so that way
scripts calling it can get the pid for the broker's java process.
Key: AMQ-4806
URL:
[
https://issues.apache.org/jira/browse/AMQ-4806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino resolved AMQ-4806.
Resolution: Fixed
'./bin/activemq console' should 'exec' java so that way scripts calling it
can
[
https://issues.apache.org/jira/browse/AMQ-4788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated AMQ-4788:
---
Summary: Add support for allowing the broker to partition client client
load across a broker cluster
Hiram Chirino created AMQ-4788:
--
Summary: Add support for allowing the broker to partition client
client load across a broker cluster using a partitioning configuraiton
Key: AMQ-4788
URL:
[
https://issues.apache.org/jira/browse/AMQ-4310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino reassigned AMQ-4310:
--
Assignee: Hiram Chirino
Add composite persistence adapter to support multiple storages for
[
https://issues.apache.org/jira/browse/AMQ-4310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino resolved AMQ-4310.
Resolution: Fixed
Fix Version/s: (was: Unscheduled)
5.9.0
Add
Hiram Chirino created AMQ-4744:
--
Summary: Support using LevelDB as a nested store in mKahaDB
Key: AMQ-4744
URL: https://issues.apache.org/jira/browse/AMQ-4744
Project: ActiveMQ
Issue Type: Bug
[
https://issues.apache.org/jira/browse/AMQ-4310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13779907#comment-13779907
]
Hiram Chirino commented on AMQ-4310:
mKahaDB has now been generalized to support
[
https://issues.apache.org/jira/browse/AMQ-4744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13779911#comment-13779911
]
Hiram Chirino commented on AMQ-4744:
This is now mostly working. A couple of failing
[
https://issues.apache.org/jira/browse/AMQ-4310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13779910#comment-13779910
]
Hiram Chirino commented on AMQ-4310:
Issue AMQ-4744 will track adding support for nested
[
https://issues.apache.org/jira/browse/AMQ-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13770812#comment-13770812
]
Hiram Chirino commented on AMQ-4718:
documented on the wiki.
Extra
[
https://issues.apache.org/jira/browse/AMQ-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13770812#comment-13770812
]
Hiram Chirino edited comment on AMQ-4718 at 9/18/13 2:27 PM:
-
[
https://issues.apache.org/jira/browse/AMQ-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino resolved AMQ-4723.
Resolution: Fixed
Fix Version/s: 5.9.0
HTTP Discovery agent should only poll for broker
[
https://issues.apache.org/jira/browse/AMQ-4718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino resolved AMQ-4718.
Resolution: Fixed
Extra options added to a failover/discovery URL that don't map to failover
Hiram Chirino created AMQ-4723:
--
Summary: HTTP Discovery agent should only poll for broker URLs
while attempting to connect a transport.
Key: AMQ-4723
URL: https://issues.apache.org/jira/browse/AMQ-4723
[
https://issues.apache.org/jira/browse/AMQ-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino reassigned AMQ-4717:
--
Assignee: Hiram Chirino
populateJMSXUserID is not setting the JMSXUserID property on the
[
https://issues.apache.org/jira/browse/AMQ-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated AMQ-4717:
---
Summary: populateJMSXUserID is not setting the JMSXUserID property on the
JMS message in JMX (was:
[
https://issues.apache.org/jira/browse/AMQ-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino resolved AMQ-4717.
Resolution: Fixed
Fix Version/s: 5.9.0
populateJMSXUserID is not setting the JMSXUserID
[
https://issues.apache.org/jira/browse/AMQ-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13763100#comment-13763100
]
Hiram Chirino commented on AMQ-4717:
The JMSXUserID was being set in the message but
[
https://issues.apache.org/jira/browse/AMQ-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated AMQ-4717:
---
Issue Type: Bug (was: New Feature)
populateJMSXUserID is not setting the JMSXUserID property on
[
https://issues.apache.org/jira/browse/AMQ-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated AMQ-4717:
---
Issue Type: New Feature (was: Bug)
populateJMSXUserID is not setting the JMSXUserID property on
Hiram Chirino created AMQ-4718:
--
Summary: Extra options added to a failover/discovery URL that
don't map to failover configuration settings, should get passed to the nested
URLs.
Key: AMQ-4718
URL:
[
https://issues.apache.org/jira/browse/AMQ-4672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino resolved AMQ-4672.
Resolution: Fixed
Fixed.
[JMS Client] Set the SNI field on SSL connections
[
https://issues.apache.org/jira/browse/AMQ-3692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino resolved AMQ-3692.
Resolution: Won't Fix
Assignee: Hiram Chirino
Bundle state and service state are 2 different
[
https://issues.apache.org/jira/browse/AMQ-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino resolved AMQ-4205.
Resolution: Won't Fix
Closing as wont fix. Please re-open if can describe a use case were changing
[
https://issues.apache.org/jira/browse/AMQ-4292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13752538#comment-13752538
]
Hiram Chirino commented on AMQ-4292:
Hi Kevin,
I just tried to stick in the
Hiram Chirino created AMQ-4672:
--
Summary: [JMS Client] Set the SNI field on SSL connections
Key: AMQ-4672
URL: https://issues.apache.org/jira/browse/AMQ-4672
Project: ActiveMQ
Issue Type: Bug
1 - 100 of 541 matches
Mail list logo
