[
https://issues.apache.org/jira/browse/AMQCPP-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13060319#comment-13060319
]
igor khaustov commented on AMQCPP-376:
--
Additional backtrace:
+Thread 13+ (Thread
Sending a message to a nonexistent queue suspends the current thread.
-
Key: AMQNET-334
URL: https://issues.apache.org/jira/browse/AMQNET-334
Project: ActiveMQ .Net
Issue
[
https://issues.apache.org/jira/browse/AMQNET-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sławomir Siudek updated AMQNET-334:
---
Fix Version/s: (was: 1.5.2)
Sending a message to a nonexistent queue suspends the
[
https://issues.apache.org/jira/browse/AMQNET-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sławomir Siudek updated AMQNET-334:
---
Description:
Code to reproduce:
class Program
{
static void Main()
[
https://issues.apache.org/jira/browse/AMQ-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Calvo updated AMQ-3353:
---
Attachment: DurableSubscriberWithNetworkDisconnectTest.java
(initial) JUnit case
Durable subscribers
[
https://issues.apache.org/jira/browse/AMQ-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13060410#comment-13060410
]
Gary Tully commented on AMQ-3353:
-
Andreas, thanks for the unit test. It has 32 tests in it
[
https://issues.apache.org/jira/browse/AMQ-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reassigned AMQ-3353:
---
Assignee: Gary Tully
Durable subscribers on durable topics don't receive messages after network
[
https://issues.apache.org/jira/browse/AMQ-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13060412#comment-13060412
]
Andreas Calvo commented on AMQ-3353:
Gary,
We set up a bunch of options, such as
[
https://issues.apache.org/jira/browse/AMQ-3372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Susan Javurek updated AMQ-3372:
---
Comment: was deleted
(was: Hi,
I will be out of the office until July 6th, 2011. If you need
[
https://issues.apache.org/jira/browse/AMQ-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Calvo updated AMQ-3353:
---
Attachment:
TEST-org.apache.activemq.usecases.DurableSubscriberWithNetworkDisconnectTest.xml
surefire
[
https://issues.apache.org/jira/browse/AMQ-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13060470#comment-13060470
]
Gary Tully commented on AMQ-3353:
-
the problem is the default value for
[
https://issues.apache.org/jira/browse/AMQ-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13060475#comment-13060475
]
Andreas Calvo commented on AMQ-3353:
We're concerned about the cyclic topology with a
[
https://issues.apache.org/jira/browse/AMQNET-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13060558#comment-13060558
]
Timothy Bish commented on AMQNET-334:
-
One issue here is that NMS.ActiveMQ doesn't
[
https://issues.apache.org/jira/browse/AMQCPP-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13060567#comment-13060567
]
Timothy Bish commented on AMQCPP-376:
-
Would probably need a complete back trace of
[
https://issues.apache.org/jira/browse/AMQ-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-3380.
---
Resolution: Fixed
Fix Version/s: 5.6.0
When tested against trunk the test passes. Fixes
[
https://issues.apache.org/jira/browse/AMQ-3342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-3342.
---
Resolution: Fixed
Fix Version/s: 5.6.0
Assignee: Timothy Bish
Created a test case to
[
https://issues.apache.org/jira/browse/AMQ-3157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13060755#comment-13060755
]
Timothy Bish commented on AMQ-3157:
---
Would be great if you could throw together a JUnit
[
https://issues.apache.org/jira/browse/AMQ-3032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish closed AMQ-3032.
-
Resolution: Incomplete
Fix Version/s: (was: 5.6.0)
Not entirely sure what the issue is trying
Hi Folks,
The Apache Board is expecting that the ActiveMQ project be compliant
with the following branding checklist by this next board report that's
due.
http://www.apache.org/foundation/marks/pmcs#checklist
I've gone through and fixed up most of the items that we were out of
compliance with.
[
https://issues.apache.org/jira/browse/AMQ-3074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-3074.
---
Resolution: Fixed
Fix Version/s: 5.6.0
Assignee: Timothy Bish
Don't see any harm in
Results of the Apache Apollo 1.0 Beta 4 vote:
Vote passes with 6 +1 binding and 1 +1 non binding votes.
The following binding votes were received:
Hiram Chirino
Jim Gomes
Gary Tully
Dejan Bosanac
Timothy Bish
Rob Davies
I'll start pushing out the release bundles and update the website.
Thanks, Hiram. Do we have a list of our project's brands and their proper
usage to use as a standard?
On Wed, Jul 6, 2011 at 12:07 PM, Hiram Chirino hi...@hiramchirino.comwrote:
Hi Folks,
The Apache Board is expecting that the ActiveMQ project be compliant
with the following branding
See
https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-spring/686/
See https://builds.apache.org/job/ActiveMQ/changes
See
https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-web-demo/686/
See
https://builds.apache.org/job/ActiveMQ/org.apache.activemq$activemq-core/changes
Well obviously the primary trade mark is 'ActiveMQ' and 'Apache
ActiveMQ'. But we may need do a similar exercise against the sub
projects like NMS, CMS, and Apollo. I'd be happy to be able to report
to the board that at least the top level project trademark is in
compliance.
Regards,
Hiram
[
https://issues.apache.org/jira/browse/AMQ-3034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13060894#comment-13060894
]
Timothy Bish commented on AMQ-3034:
---
Would be great if you could turn this into a JUnit
[
https://issues.apache.org/jira/browse/AMQ-3034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13060900#comment-13060900
]
Arthur Naseef commented on AMQ-3034:
This could be a case of using all of the broker's
[
https://issues.apache.org/jira/browse/AMQ-3012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQ-3012.
---
Resolution: Fixed
Fix Version/s: 5.6.0
Patch applied, thanks!
HttpTunnelServlet incorrectly
[
https://issues.apache.org/jira/browse/AMQ-3034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13060908#comment-13060908
]
Timothy Bish edited comment on AMQ-3034 at 7/6/11 11:11 PM:
[
https://issues.apache.org/jira/browse/AMQ-3034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13060908#comment-13060908
]
Timothy Bish commented on AMQ-3034:
---
Since the producer is submitting messages in batches
Hi,
We are using the activemq-5.4.0 with Journaling turned on. So far It has
been working fine without any issues.
All of the sudden, today, we started getting the
../apache-activemq-5.4.0/data/journal/archive/.log file not found
exception in our PRODUCTION environment.
We checked our
33 matches
Mail list logo
