[jira] [Commented] (AMQCPP-377) Does not detect broken connection on Windows

[ https://issues.apache.org/jira/browse/AMQCPP-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13068180#comment-13068180 ] Pavel Jaoshvili commented on AMQCPP-377: On v3.4.0 problem still exists. May this

[jira] [Commented] (AMQCPP-377) Does not detect broken connection on Windows

[ https://issues.apache.org/jira/browse/AMQCPP-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13068194#comment-13068194 ] Pavel Jaoshvili commented on AMQCPP-377: string brokerURI =

[jira] [Issue Comment Edited] (AMQCPP-377) Does not detect broken connection on Windows

[ https://issues.apache.org/jira/browse/AMQCPP-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13068194#comment-13068194 ] Pavel Jaoshvili edited comment on AMQCPP-377 at 7/20/11 7:40 AM:

[jira] [Resolved] (AMQ-3406) Enable BrokerServiceAware support for DiscoveryAgent

[ https://issues.apache.org/jira/browse/AMQ-3406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-3406. Resolution: Fixed Fix Version/s: 5.6.0 Assignee: Dejan Bosanac Patch applied with

[jira] [Resolved] (AMQ-3407) Add ApplicationContextAware on XBeanBrokerService

[ https://issues.apache.org/jira/browse/AMQ-3407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-3407. Resolution: Won't Fix Assignee: Dejan Bosanac This is intentionally changed to remove runtime

Jenkins build is still unstable: ActiveMQ #701

See https://builds.apache.org/job/ActiveMQ/changes

Jenkins build is still unstable: ActiveMQ » ActiveMQ :: Core #701

See https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-core/changes

Jenkins build is still unstable: ActiveMQ » ActiveMQ :: Camel #701

See https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-camel/701/

Jenkins build is still unstable: ActiveMQ » ActiveMQ :: Spring #701

See https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-spring/701/

[jira] [Commented] (AMQNET-337) Creating ConnectionFactory fails if ActiveMQ assembly has long path

[ https://issues.apache.org/jira/browse/AMQNET-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13068239#comment-13068239 ] Simon Jackson commented on AMQNET-337: -- The path which is being tested is generated

[jira] [Created] (AMQ-3409) missing jar files

missing jar files - Key: AMQ-3409 URL: https://issues.apache.org/jira/browse/AMQ-3409 Project: ActiveMQ Issue Type: Bug Components: JMS client Affects Versions: 5.5.0 Environment: Windows

[jira] [Updated] (AMQNET-337) Creating ConnectionFactory fails if ActiveMQ assembly has long path

[ https://issues.apache.org/jira/browse/AMQNET-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jim Gomes updated AMQNET-337: - Affects Version/s: (was: 1.5.1) 1.5.0 Fix Version/s: 1.5.1 Yeah, that

[jira] [Assigned] (AMQ-3409) missing jar files

[ https://issues.apache.org/jira/browse/AMQ-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac reassigned AMQ-3409: -- Assignee: Dejan Bosanac missing jar files - Key: AMQ-3409

[jira] [Commented] (AMQCPP-377) Does not detect broken connection on Windows

[ https://issues.apache.org/jira/browse/AMQCPP-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13068338#comment-13068338 ] Timothy Bish commented on AMQCPP-377: - The InactivityMonitor looks at the

[jira] [Resolved] (AMQ-3409) missing jar files

[ https://issues.apache.org/jira/browse/AMQ-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-3409. Resolution: Fixed Just updated

[jira] [Commented] (AMQCPP-377) Does not detect broken connection on Windows

[ https://issues.apache.org/jira/browse/AMQCPP-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13068346#comment-13068346 ] Pavel Jaoshvili commented on AMQCPP-377: To reproduce the problem, you can run

[jira] [Commented] (AMQ-3402) Stomp over Websocket truncates the message body

[ https://issues.apache.org/jira/browse/AMQ-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13068348#comment-13068348 ] Manu Agarwal commented on AMQ-3402: --- Please find below a snippet from my cofig

[jira] [Reopened] (AMQ-3409) missing jar files

[ https://issues.apache.org/jira/browse/AMQ-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shaun Oneill reopened AMQ-3409: --- I cannot see a resolution. I need to find these 2 jar files which are not in the diowloaded library.

[jira] [Commented] (AMQ-3409) missing jar files

[ https://issues.apache.org/jira/browse/AMQ-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13068365#comment-13068365 ] Dejan Bosanac commented on AMQ-3409: You don't need them for 5.5.0 missing jar files

[jira] [Commented] (AMQ-3404) Purge command does not accept message selectors

[ https://issues.apache.org/jira/browse/AMQ-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13068432#comment-13068432 ] Allen Reese commented on AMQ-3404: -- The correct fix is to use a QueryViewMbean: //

[jira] [Updated] (AMQ-3404) Purge command does not accept message selectors

[ https://issues.apache.org/jira/browse/AMQ-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Reese updated AMQ-3404: - Comment: was deleted (was: I've dug into this further, and it seems like message selectors don't work

[jira] [Closed] (AMQ-3110) Same message redelivered again even though moved to a different queue using web console

[ https://issues.apache.org/jira/browse/AMQ-3110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-3110. - Resolution: Cannot Reproduce The test case provided sets redelivery on the client as unlimited so the fact

[jira] [Closed] (AMQ-3102) Can't find logging.properties file

[ https://issues.apache.org/jira/browse/AMQ-3102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish closed AMQ-3102. - Resolution: Cannot Reproduce Likely that the file isn't in the path given. Can't find logging.properties

[jira] [Resolved] (AMQ-2971) DestinationStatistics.getMessages() returns 0 after reset with messages still in queue

[ https://issues.apache.org/jira/browse/AMQ-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy Bish resolved AMQ-2971. --- Resolution: Fixed Fix Version/s: 5.6.0 Find in trunk. DestinationStatistics.getMessages()

[jira] [Created] (AMQ-3410) AbstractAmqCommand should allow the connection factory to be changed.

AbstractAmqCommand should allow the connection factory to be changed. - Key: AMQ-3410 URL: https://issues.apache.org/jira/browse/AMQ-3410 Project: ActiveMQ Issue Type:

[jira] [Updated] (AMQ-3404) Purge command does not accept message selectors

[ https://issues.apache.org/jira/browse/AMQ-3404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Reese updated AMQ-3404: - Attachment: PurgeCommand.patch Patch to fix this issue, with a test cases that fails before and passes

[jira] [Updated] (AMQ-3410) AbstractAmqCommand should allow the connection factory to be changed.

[ https://issues.apache.org/jira/browse/AMQ-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Reese updated AMQ-3410: - Patch Info: [Patch Available] AbstractAmqCommand should allow the connection factory to be changed.

[jira] [Updated] (AMQ-3410) AbstractAmqCommand should allow the connection factory to be changed.

[ https://issues.apache.org/jira/browse/AMQ-3410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Allen Reese updated AMQ-3410: - Attachment: AMQ-3410.patch This patch adds a --factory command line arg. It depends on the fixes to