Provide configurable default for unqualified stomp reply-to header destination
string
-
Key: AMQ-3496
URL: https://issues.apache.org/jira/browse/AMQ-3496
Project:
[
https://issues.apache.org/jira/browse/AMQ-3496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully resolved AMQ-3496.
-
Resolution: Fixed
resolved in http://svn.apache.org/viewvc?rev=1170474view=rev
reuse of
[
https://issues.apache.org/jira/browse/AMQNET-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Parkin updated AMQNET-342:
-
Attachment: consumercreator.cs
I can now reproduce the problem every time with the attached code
STOMP subscription receipt can be out of order with message dispatch, resulting
in consumer/client error
Key: AMQ-3497
URL:
Add support for setting ActiveMQ destination options in Camel endpoint uris
---
Key: AMQ-3498
URL: https://issues.apache.org/jira/browse/AMQ-3498
Project: ActiveMQ
[
https://issues.apache.org/jira/browse/AMQ-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13104485#comment-13104485
]
Claus Ibsen commented on AMQ-3498:
--
Sending
[
https://issues.apache.org/jira/browse/AMQ-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13104490#comment-13104490
]
Claus Ibsen commented on AMQ-3498:
--
Updated wiki documentation, with an example
[
https://issues.apache.org/jira/browse/AMQ-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved AMQ-3498.
--
Resolution: Fixed
Add support for setting ActiveMQ destination options in Camel endpoint uris
Raise Logging level to warn for Transport failure exceptions
Key: AMQ-3499
URL: https://issues.apache.org/jira/browse/AMQ-3499
Project: ActiveMQ
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/AMQ-3498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully updated AMQ-3498:
Component/s: activemq-camel
Add support for setting ActiveMQ destination options in Camel endpoint uris
[
https://issues.apache.org/jira/browse/AMQ-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13104531#comment-13104531
]
ravi bhatt commented on AMQ-3451:
-
I am having similar issue where tomcat does not shut down
[
https://issues.apache.org/jira/browse/AMQ-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13104532#comment-13104532
]
ravi bhatt commented on AMQ-3451:
-
and BTW i have tested this on tomcat 5, 6 and 7 with
[
https://issues.apache.org/jira/browse/AMQ-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13104532#comment-13104532
]
ravi bhatt edited comment on AMQ-3451 at 9/14/11 2:41 PM:
--
and BTW
[
https://issues.apache.org/jira/browse/AMQ-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13104584#comment-13104584
]
john richartz commented on AMQ-3490:
I agree, the first stack trace does look odd.
[
https://issues.apache.org/jira/browse/AMQ-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13104587#comment-13104587
]
john richartz commented on AMQ-3490:
The version of 5.6 was retrieved from
[
https://issues.apache.org/jira/browse/AMQ-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13104660#comment-13104660
]
Gary Tully commented on AMQ-3490:
-
hmm. thanks for the detail. I need to try and reproduce.
[
https://issues.apache.org/jira/browse/AMQ-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reopened AMQ-3481:
-
The inactivity monitor is still a problem with disconnects. Wonder should there
be an inactivity monitor on
[
https://issues.apache.org/jira/browse/AMQ-3490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13104712#comment-13104712
]
john richartz commented on AMQ-3490:
I don't have a test case that directly exposes this
The problem is only reproducible with the
wireFormat.maxInactivityDuration=0parameter. If this parameter is
removed, then the thread is cleaned up
correctly. Knowing that, I think the fix should be pretty straightforward.
In the meantime, as a work-around, I would suggest not adding that
hi Jim,
thank for your help .. i will remove that parameter and try it again.
best regards
Shine
The problem is only reproducible with the
wireFormat.maxInactivityDuration=0parameter. If this parameter is
removed, then the thread is cleaned up
correctly. Knowing that, I think the fix
[
https://issues.apache.org/jira/browse/AMQ-2846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-2846.
-
Resolution: Duplicate
Fix Version/s: 5.6.0
Duplicate of AMQ-3498. Fixed
Apache Camel Activemq
[
https://issues.apache.org/jira/browse/AMQ-3492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-3492.
---
Resolution: Fixed
patch applied, thanks!
enhance maven-activemq-perf-plugin to send specific message
[
https://issues.apache.org/jira/browse/AMQ-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-3485.
-
Resolution: Not A Problem
Working as designed. The second consumer would not receive the message as the
[
https://issues.apache.org/jira/browse/AMQ-3465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13105051#comment-13105051
]
William Youmans commented on AMQ-3465:
--
I am experiencing similar issue as described in
See
https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-spring/757/
See
https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-core/changes
See https://builds.apache.org/job/ActiveMQ/757/changes
See https://builds.apache.org/job/ActiveMQ-Trunk-Deploy/377/changes
28 matches
Mail list logo
