[jira] [Updated] (AMQ-3353) Durable subscribers on durable topics don't receive messages after network disconnect
[
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
Use Case updated to stable ActiveMQ 5.6.
Notice how the timeout parameter in the failover transport protocol has changed
and now is using -1 instead of 0
Durable subscribers on durable topics don't receive messages after network
disconnect
-
Key: AMQ-3353
URL: https://issues.apache.org/jira/browse/AMQ-3353
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.3.1, 5.5.0
Environment: Windows Linux
JDK 1.6
Reporter: Syed Faraz Ali
Assignee: Gary Tully
Fix For: 5.6.0
Attachments: DurableSubscriberWithNetworkDisconnectTest.java,
DurableSubscriberWithNetworkDisconnectTest.java,
TEST-org.apache.activemq.usecases.DurableSubscriberWithNetworkDisconnectTest.xml,
test-results.ods
I've set up a durable topic with the default (persistent) delivery mode on
one machine that is publishing a simple text message every 5 seconds. I
created a durable subscriber that consumes messages published to the above
topic on another machine. I am using broker to broker communication between
the two machines.
I start up the two programs on either machine and see the messages coming
through to the subscriber. If I then pull the network cable to disconnect the
network between the two machines, wait for a minute and then plug it back in,
my subscriber doesn't receive the messages any more. I can see from the
output that the publisher is still publishing them (Temporary topics,
non-durable queues all continue to sync up in our production environment, it
is only the durable topics that don't work after network reconnect)
If I were to tweak a setting on the publisher's broker (that was introduced
only in 5.5.0), suppressDuplicateTopicSubscriptions=false, then the topics
work correctly after network reconnect. But this may have other unintended
consequences and I was hoping to get a better idea of:
- is this a known issue ? if so, then are there any specific challenges that
have caused it not to be fixed?
- are other people out there using durable topics and subscribers without a
failover option that have run into this problem? What have they done to work
around?
Here is how my subscriber and publisher are set up:
Topic Publisher (Machine 1)
publisherConnection = connFactory.createConnection();
publisherConnection.setClientID( ProducerCliID );
publisherConnection.start();
session = publisherConnection.createSession( true, -1 );
Destination producerTopic = session.createTopic( TEST_TOPIC_NAME );
producer = session.createProducer( (Topic)producerTopic );
// On a timer, keep sending this out every 5 seconds
String text = HELLO + count++;
TextMessage msg = session.createTextMessage( text );
System.out.println( Sending TextMessage = + msg.getText()
);
producer.send( msg );
session.commit();
Subscriber ( Machine 2):
Connection clientConnection = connFactory.createConnection();
clientConnection.setClientID(cliID);
clientConnection.start();
Session session = clientConnection.createSession( false,
Session.AUTO_ACKNOWLEDGE );
Destination topic = session.createTopic( topicName );
MessageConsumer subscriber = session.createDurableSubscriber(
(Topic)topic, subName );
TestMessageListener msgListener = new TestMessageListener( 1000 );
subscriber.setMessageListener( msgListener );
.
.
// TestMessageListener's onMessage method simply outputs the message:
public void onMessage(Message message)
{
if ( message instanceof TextMessage )
{
System.out.println( Message received = +
((TextMessage)message) );
}
}
I can provide the jars for you to run the program if need be.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQ-3353) Durable subscribers on durable topics don't receive messages after network disconnect
[
https://issues.apache.org/jira/browse/AMQ-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13288572#comment-13288572
]
Timothy Bish commented on AMQ-3353:
---
Tried you new test case against the latest trunk SNAPSHOT and it passes.
There's been a couple recent fixes since 5.6.0 for issues that could affect
durable consumers so you may want to try out a 5.7-SNAPSHOT.
Durable subscribers on durable topics don't receive messages after network
disconnect
-
Key: AMQ-3353
URL: https://issues.apache.org/jira/browse/AMQ-3353
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.3.1, 5.5.0
Environment: Windows Linux
JDK 1.6
Reporter: Syed Faraz Ali
Assignee: Gary Tully
Fix For: 5.6.0
Attachments: DurableSubscriberWithNetworkDisconnectTest.java,
DurableSubscriberWithNetworkDisconnectTest.java,
TEST-org.apache.activemq.usecases.DurableSubscriberWithNetworkDisconnectTest.xml,
test-results.ods
I've set up a durable topic with the default (persistent) delivery mode on
one machine that is publishing a simple text message every 5 seconds. I
created a durable subscriber that consumes messages published to the above
topic on another machine. I am using broker to broker communication between
the two machines.
I start up the two programs on either machine and see the messages coming
through to the subscriber. If I then pull the network cable to disconnect the
network between the two machines, wait for a minute and then plug it back in,
my subscriber doesn't receive the messages any more. I can see from the
output that the publisher is still publishing them (Temporary topics,
non-durable queues all continue to sync up in our production environment, it
is only the durable topics that don't work after network reconnect)
If I were to tweak a setting on the publisher's broker (that was introduced
only in 5.5.0), suppressDuplicateTopicSubscriptions=false, then the topics
work correctly after network reconnect. But this may have other unintended
consequences and I was hoping to get a better idea of:
- is this a known issue ? if so, then are there any specific challenges that
have caused it not to be fixed?
- are other people out there using durable topics and subscribers without a
failover option that have run into this problem? What have they done to work
around?
Here is how my subscriber and publisher are set up:
Topic Publisher (Machine 1)
publisherConnection = connFactory.createConnection();
publisherConnection.setClientID( ProducerCliID );
publisherConnection.start();
session = publisherConnection.createSession( true, -1 );
Destination producerTopic = session.createTopic( TEST_TOPIC_NAME );
producer = session.createProducer( (Topic)producerTopic );
// On a timer, keep sending this out every 5 seconds
String text = HELLO + count++;
TextMessage msg = session.createTextMessage( text );
System.out.println( Sending TextMessage = + msg.getText()
);
producer.send( msg );
session.commit();
Subscriber ( Machine 2):
Connection clientConnection = connFactory.createConnection();
clientConnection.setClientID(cliID);
clientConnection.start();
Session session = clientConnection.createSession( false,
Session.AUTO_ACKNOWLEDGE );
Destination topic = session.createTopic( topicName );
MessageConsumer subscriber = session.createDurableSubscriber(
(Topic)topic, subName );
TestMessageListener msgListener = new TestMessageListener( 1000 );
subscriber.setMessageListener( msgListener );
.
.
// TestMessageListener's onMessage method simply outputs the message:
public void onMessage(Message message)
{
if ( message instanceof TextMessage )
{
System.out.println( Message received = +
((TextMessage)message) );
}
}
I can provide the jars for you to run the program if need be.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQCPP-407) Application crashes after stopping message broker
[ https://issues.apache.org/jira/browse/AMQCPP-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13288908#comment-13288908 ] Helen Huang commented on AMQCPP-407: We have not been able to catch the issue on any development system. We are wondering if you have enough information by looking at the call stacks I have attached before on 5/22 and 5/31. Thanks! Application crashes after stopping message broker - Key: AMQCPP-407 URL: https://issues.apache.org/jira/browse/AMQCPP-407 Project: ActiveMQ C++ Client Issue Type: Bug Components: CMS Impl Affects Versions: 3.4.1 Environment: Windows xp service pack 3, ActiveMQ broker 5.3.1, apr 1.4.2, apr-util 1.3.9, apr iconv 1.2.1 Reporter: Helen Huang Assignee: Timothy Bish Priority: Blocker Fix For: 3.4.1 Attachments: AttemptedFix1.7z Stopping the message broker would crash our application. The following is the call stack of the fault thread. Thread 0 - System ID 672 Entry point msvcr80!endthreadex+61 Create time 5/24/2012 1:53:56 PM Time spent in user mode 0 Days 0:0:0.46 Time spent in kernel mode 0 Days 0:0:0.78 Function Arg 1 Arg 2 Arg 3 Source kernel32!InterlockedDecrement+9 00242110 msvcrt!cexit+f 77c1 0001 ntdll!LdrInitializeThunk+24 77c1f2a1 77c1 ntdll!RtlDestroyEnvironment+178 0eec256d 0001 kernel32!IsValidLocale+8eb 0003 77e8f3b0 kernel32!ExitProcess+14 0003 0ec21a04 0003 msvcr80!amsg_exit+5e 0003 0001 msvcr80!exit+d 1795efe0 user32!MessageBoxIndirectA+23a 0001 7c91005d 13946b5e user32!MessageBoxIndirectA+254 13946b5e 00e30850 ntdll!RtlFreeHeap+130 0468001b 0202 1795f110 activemq_cppu!activemq::core::ActiveMQConnection::onException+fd 1795fe24 7f427d47 1795fe18 activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 7f427d33 1795fe18 activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 7f427cef 1795fe18 activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 1795f60c 0ef4a264 activemq_cppu!activemq::transport::inactivity::InactivityMonitor::onException+33 1795fe24 7f427cd7 1795fe18 activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 7f427c83 1795fe18 activemq_cppu!activemq::transport::IOTransport::fire+4b 1795fe24 0ec48ed7 1795fe18 activemq_cppu!activemq::transport::IOTransport::run+15e 7f427107 7c809c65 12519500 activemq_cppu!decaf::lang::ThreadProperties::runCallback+82 7c936d80 04682060 0ec229bb activemq_cppu!`anonymous namespace'::threadWorker+20 04682060 0ec229bb 12519500 ntdll!RtlRemoveVectoredExceptionHandler+2a2 04682060 7c80b729 1252f168 msvcr80!endthreadex+c7 0ec229e1 1252f168 KERNEL32!INTERLOCKEDDECREMENT+9WARNING - DebugDiag was not able to locate debug symbols for kernel32.dll, so the information below may be incomplete. In ScotAppU__PID__1168__Date__05_24_2012__Time_02_18_41PM__916__Second_Chance_Exception_C005.dmp the assembly instruction at kernel32!InterlockedDecrement+9 in C:\WINDOWS\system32\kernel32.dll from Microsoft Corporation has caused an access violation exception (0xC005) when trying to write to memory location 0x014718e4 on thread 0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQCPP-407) Application crashes after stopping message broker
[
https://issues.apache.org/jira/browse/AMQCPP-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13288921#comment-13288921
]
Timothy Bish commented on AMQCPP-407:
-
From the call stack given the thread that initiates the onException callback
is that of the IOTransport:
{code}
activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 7f427c83
1795fe18
activemq_cppu!activemq::transport::IOTransport::fire+4b 1795fe24 0ec48ed7
1795fe18
activemq_cppu!activemq::transport::IOTransport::run+15e 7f427107 7c809c65
12519500
{code}
It happens to pass through the InactivityMonitor but is not initiated there.
I'm not able to reproduce this so I can't really say why its happening. From
code inspection it appears as though it should be waiting for the transport
close().
Application crashes after stopping message broker
-
Key: AMQCPP-407
URL: https://issues.apache.org/jira/browse/AMQCPP-407
Project: ActiveMQ C++ Client
Issue Type: Bug
Components: CMS Impl
Affects Versions: 3.4.1
Environment: Windows xp service pack 3, ActiveMQ broker 5.3.1, apr
1.4.2, apr-util 1.3.9, apr iconv 1.2.1
Reporter: Helen Huang
Assignee: Timothy Bish
Priority: Blocker
Fix For: 3.4.1
Attachments: AttemptedFix1.7z
Stopping the message broker would crash our application. The following is the
call stack of the fault thread.
Thread 0 - System ID 672
Entry point msvcr80!endthreadex+61
Create time 5/24/2012 1:53:56 PM
Time spent in user mode 0 Days 0:0:0.46
Time spent in kernel mode 0 Days 0:0:0.78
Function Arg 1 Arg 2 Arg 3 Source
kernel32!InterlockedDecrement+9 00242110
msvcrt!cexit+f 77c1 0001
ntdll!LdrInitializeThunk+24 77c1f2a1 77c1
ntdll!RtlDestroyEnvironment+178 0eec256d 0001
kernel32!IsValidLocale+8eb 0003 77e8f3b0
kernel32!ExitProcess+14 0003 0ec21a04 0003
msvcr80!amsg_exit+5e 0003 0001
msvcr80!exit+d 1795efe0
user32!MessageBoxIndirectA+23a 0001 7c91005d 13946b5e
user32!MessageBoxIndirectA+254 13946b5e 00e30850
ntdll!RtlFreeHeap+130 0468001b 0202 1795f110
activemq_cppu!activemq::core::ActiveMQConnection::onException+fd 1795fe24
7f427d47 1795fe18
activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24
7f427d33 1795fe18
activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24
7f427cef 1795fe18
activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24
1795f60c 0ef4a264
activemq_cppu!activemq::transport::inactivity::InactivityMonitor::onException+33
1795fe24 7f427cd7 1795fe18
activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24
7f427c83 1795fe18
activemq_cppu!activemq::transport::IOTransport::fire+4b 1795fe24
0ec48ed7 1795fe18
activemq_cppu!activemq::transport::IOTransport::run+15e 7f427107
7c809c65 12519500
activemq_cppu!decaf::lang::ThreadProperties::runCallback+82 7c936d80
04682060 0ec229bb
activemq_cppu!`anonymous namespace'::threadWorker+20 04682060
0ec229bb 12519500
ntdll!RtlRemoveVectoredExceptionHandler+2a2 04682060 7c80b729
1252f168
msvcr80!endthreadex+c7 0ec229e1 1252f168
KERNEL32!INTERLOCKEDDECREMENT+9WARNING - DebugDiag was not able to locate
debug symbols for kernel32.dll, so the information below may be incomplete.
In
ScotAppU__PID__1168__Date__05_24_2012__Time_02_18_41PM__916__Second_Chance_Exception_C005.dmp
the assembly instruction at kernel32!InterlockedDecrement+9 in
C:\WINDOWS\system32\kernel32.dll from Microsoft Corporation has caused an
access violation exception (0xC005) when trying to write to memory
location 0x014718e4 on thread 0
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQCPP-407) Application crashes after stopping message broker
[ https://issues.apache.org/jira/browse/AMQCPP-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13288924#comment-13288924 ] Helen Huang commented on AMQCPP-407: Do you think turning off InacitvityMonitor would help? Also what is the impact if we turn it off? Application crashes after stopping message broker - Key: AMQCPP-407 URL: https://issues.apache.org/jira/browse/AMQCPP-407 Project: ActiveMQ C++ Client Issue Type: Bug Components: CMS Impl Affects Versions: 3.4.1 Environment: Windows xp service pack 3, ActiveMQ broker 5.3.1, apr 1.4.2, apr-util 1.3.9, apr iconv 1.2.1 Reporter: Helen Huang Assignee: Timothy Bish Priority: Blocker Fix For: 3.4.1 Attachments: AttemptedFix1.7z Stopping the message broker would crash our application. The following is the call stack of the fault thread. Thread 0 - System ID 672 Entry point msvcr80!endthreadex+61 Create time 5/24/2012 1:53:56 PM Time spent in user mode 0 Days 0:0:0.46 Time spent in kernel mode 0 Days 0:0:0.78 Function Arg 1 Arg 2 Arg 3 Source kernel32!InterlockedDecrement+9 00242110 msvcrt!cexit+f 77c1 0001 ntdll!LdrInitializeThunk+24 77c1f2a1 77c1 ntdll!RtlDestroyEnvironment+178 0eec256d 0001 kernel32!IsValidLocale+8eb 0003 77e8f3b0 kernel32!ExitProcess+14 0003 0ec21a04 0003 msvcr80!amsg_exit+5e 0003 0001 msvcr80!exit+d 1795efe0 user32!MessageBoxIndirectA+23a 0001 7c91005d 13946b5e user32!MessageBoxIndirectA+254 13946b5e 00e30850 ntdll!RtlFreeHeap+130 0468001b 0202 1795f110 activemq_cppu!activemq::core::ActiveMQConnection::onException+fd 1795fe24 7f427d47 1795fe18 activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 7f427d33 1795fe18 activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 7f427cef 1795fe18 activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 1795f60c 0ef4a264 activemq_cppu!activemq::transport::inactivity::InactivityMonitor::onException+33 1795fe24 7f427cd7 1795fe18 activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 7f427c83 1795fe18 activemq_cppu!activemq::transport::IOTransport::fire+4b 1795fe24 0ec48ed7 1795fe18 activemq_cppu!activemq::transport::IOTransport::run+15e 7f427107 7c809c65 12519500 activemq_cppu!decaf::lang::ThreadProperties::runCallback+82 7c936d80 04682060 0ec229bb activemq_cppu!`anonymous namespace'::threadWorker+20 04682060 0ec229bb 12519500 ntdll!RtlRemoveVectoredExceptionHandler+2a2 04682060 7c80b729 1252f168 msvcr80!endthreadex+c7 0ec229e1 1252f168 KERNEL32!INTERLOCKEDDECREMENT+9WARNING - DebugDiag was not able to locate debug symbols for kernel32.dll, so the information below may be incomplete. In ScotAppU__PID__1168__Date__05_24_2012__Time_02_18_41PM__916__Second_Chance_Exception_C005.dmp the assembly instruction at kernel32!InterlockedDecrement+9 in C:\WINDOWS\system32\kernel32.dll from Microsoft Corporation has caused an access violation exception (0xC005) when trying to write to memory location 0x014718e4 on thread 0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (AMQCPP-407) Application crashes after stopping message broker
[ https://issues.apache.org/jira/browse/AMQCPP-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13288924#comment-13288924 ] Helen Huang edited comment on AMQCPP-407 at 6/4/12 9:42 PM: Do you think turning off InacitvityMonitor would help? Also what would be the impact if we turn it off? was (Author: hhuang): Do you think turning off InacitvityMonitor would help? Also what is the impact if we turn it off? Application crashes after stopping message broker - Key: AMQCPP-407 URL: https://issues.apache.org/jira/browse/AMQCPP-407 Project: ActiveMQ C++ Client Issue Type: Bug Components: CMS Impl Affects Versions: 3.4.1 Environment: Windows xp service pack 3, ActiveMQ broker 5.3.1, apr 1.4.2, apr-util 1.3.9, apr iconv 1.2.1 Reporter: Helen Huang Assignee: Timothy Bish Priority: Blocker Fix For: 3.4.1 Attachments: AttemptedFix1.7z Stopping the message broker would crash our application. The following is the call stack of the fault thread. Thread 0 - System ID 672 Entry point msvcr80!endthreadex+61 Create time 5/24/2012 1:53:56 PM Time spent in user mode 0 Days 0:0:0.46 Time spent in kernel mode 0 Days 0:0:0.78 Function Arg 1 Arg 2 Arg 3 Source kernel32!InterlockedDecrement+9 00242110 msvcrt!cexit+f 77c1 0001 ntdll!LdrInitializeThunk+24 77c1f2a1 77c1 ntdll!RtlDestroyEnvironment+178 0eec256d 0001 kernel32!IsValidLocale+8eb 0003 77e8f3b0 kernel32!ExitProcess+14 0003 0ec21a04 0003 msvcr80!amsg_exit+5e 0003 0001 msvcr80!exit+d 1795efe0 user32!MessageBoxIndirectA+23a 0001 7c91005d 13946b5e user32!MessageBoxIndirectA+254 13946b5e 00e30850 ntdll!RtlFreeHeap+130 0468001b 0202 1795f110 activemq_cppu!activemq::core::ActiveMQConnection::onException+fd 1795fe24 7f427d47 1795fe18 activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 7f427d33 1795fe18 activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 7f427cef 1795fe18 activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 1795f60c 0ef4a264 activemq_cppu!activemq::transport::inactivity::InactivityMonitor::onException+33 1795fe24 7f427cd7 1795fe18 activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 7f427c83 1795fe18 activemq_cppu!activemq::transport::IOTransport::fire+4b 1795fe24 0ec48ed7 1795fe18 activemq_cppu!activemq::transport::IOTransport::run+15e 7f427107 7c809c65 12519500 activemq_cppu!decaf::lang::ThreadProperties::runCallback+82 7c936d80 04682060 0ec229bb activemq_cppu!`anonymous namespace'::threadWorker+20 04682060 0ec229bb 12519500 ntdll!RtlRemoveVectoredExceptionHandler+2a2 04682060 7c80b729 1252f168 msvcr80!endthreadex+c7 0ec229e1 1252f168 KERNEL32!INTERLOCKEDDECREMENT+9WARNING - DebugDiag was not able to locate debug symbols for kernel32.dll, so the information below may be incomplete. In ScotAppU__PID__1168__Date__05_24_2012__Time_02_18_41PM__916__Second_Chance_Exception_C005.dmp the assembly instruction at kernel32!InterlockedDecrement+9 in C:\WINDOWS\system32\kernel32.dll from Microsoft Corporation has caused an access violation exception (0xC005) when trying to write to memory location 0x014718e4 on thread 0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQCPP-407) Application crashes after stopping message broker
[ https://issues.apache.org/jira/browse/AMQCPP-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13288935#comment-13288935 ] Timothy Bish commented on AMQCPP-407: - I don't see how it would help in this case. Turning it off means that your client might not detect when connections to the broker are dropped and hang waiting for new messages to arrive. Application crashes after stopping message broker - Key: AMQCPP-407 URL: https://issues.apache.org/jira/browse/AMQCPP-407 Project: ActiveMQ C++ Client Issue Type: Bug Components: CMS Impl Affects Versions: 3.4.1 Environment: Windows xp service pack 3, ActiveMQ broker 5.3.1, apr 1.4.2, apr-util 1.3.9, apr iconv 1.2.1 Reporter: Helen Huang Assignee: Timothy Bish Priority: Blocker Fix For: 3.4.1 Attachments: AttemptedFix1.7z Stopping the message broker would crash our application. The following is the call stack of the fault thread. Thread 0 - System ID 672 Entry point msvcr80!endthreadex+61 Create time 5/24/2012 1:53:56 PM Time spent in user mode 0 Days 0:0:0.46 Time spent in kernel mode 0 Days 0:0:0.78 Function Arg 1 Arg 2 Arg 3 Source kernel32!InterlockedDecrement+9 00242110 msvcrt!cexit+f 77c1 0001 ntdll!LdrInitializeThunk+24 77c1f2a1 77c1 ntdll!RtlDestroyEnvironment+178 0eec256d 0001 kernel32!IsValidLocale+8eb 0003 77e8f3b0 kernel32!ExitProcess+14 0003 0ec21a04 0003 msvcr80!amsg_exit+5e 0003 0001 msvcr80!exit+d 1795efe0 user32!MessageBoxIndirectA+23a 0001 7c91005d 13946b5e user32!MessageBoxIndirectA+254 13946b5e 00e30850 ntdll!RtlFreeHeap+130 0468001b 0202 1795f110 activemq_cppu!activemq::core::ActiveMQConnection::onException+fd 1795fe24 7f427d47 1795fe18 activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 7f427d33 1795fe18 activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 7f427cef 1795fe18 activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 1795f60c 0ef4a264 activemq_cppu!activemq::transport::inactivity::InactivityMonitor::onException+33 1795fe24 7f427cd7 1795fe18 activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 7f427c83 1795fe18 activemq_cppu!activemq::transport::IOTransport::fire+4b 1795fe24 0ec48ed7 1795fe18 activemq_cppu!activemq::transport::IOTransport::run+15e 7f427107 7c809c65 12519500 activemq_cppu!decaf::lang::ThreadProperties::runCallback+82 7c936d80 04682060 0ec229bb activemq_cppu!`anonymous namespace'::threadWorker+20 04682060 0ec229bb 12519500 ntdll!RtlRemoveVectoredExceptionHandler+2a2 04682060 7c80b729 1252f168 msvcr80!endthreadex+c7 0ec229e1 1252f168 KERNEL32!INTERLOCKEDDECREMENT+9WARNING - DebugDiag was not able to locate debug symbols for kernel32.dll, so the information below may be incomplete. In ScotAppU__PID__1168__Date__05_24_2012__Time_02_18_41PM__916__Second_Chance_Exception_C005.dmp the assembly instruction at kernel32!InterlockedDecrement+9 in C:\WINDOWS\system32\kernel32.dll from Microsoft Corporation has caused an access violation exception (0xC005) when trying to write to memory location 0x014718e4 on thread 0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQCPP-407) Application crashes after stopping message broker
[ https://issues.apache.org/jira/browse/AMQCPP-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13288939#comment-13288939 ] Helen Huang commented on AMQCPP-407: Thanks for the feedback. That was what I worried about also. Application crashes after stopping message broker - Key: AMQCPP-407 URL: https://issues.apache.org/jira/browse/AMQCPP-407 Project: ActiveMQ C++ Client Issue Type: Bug Components: CMS Impl Affects Versions: 3.4.1 Environment: Windows xp service pack 3, ActiveMQ broker 5.3.1, apr 1.4.2, apr-util 1.3.9, apr iconv 1.2.1 Reporter: Helen Huang Assignee: Timothy Bish Priority: Blocker Fix For: 3.4.1 Attachments: AttemptedFix1.7z Stopping the message broker would crash our application. The following is the call stack of the fault thread. Thread 0 - System ID 672 Entry point msvcr80!endthreadex+61 Create time 5/24/2012 1:53:56 PM Time spent in user mode 0 Days 0:0:0.46 Time spent in kernel mode 0 Days 0:0:0.78 Function Arg 1 Arg 2 Arg 3 Source kernel32!InterlockedDecrement+9 00242110 msvcrt!cexit+f 77c1 0001 ntdll!LdrInitializeThunk+24 77c1f2a1 77c1 ntdll!RtlDestroyEnvironment+178 0eec256d 0001 kernel32!IsValidLocale+8eb 0003 77e8f3b0 kernel32!ExitProcess+14 0003 0ec21a04 0003 msvcr80!amsg_exit+5e 0003 0001 msvcr80!exit+d 1795efe0 user32!MessageBoxIndirectA+23a 0001 7c91005d 13946b5e user32!MessageBoxIndirectA+254 13946b5e 00e30850 ntdll!RtlFreeHeap+130 0468001b 0202 1795f110 activemq_cppu!activemq::core::ActiveMQConnection::onException+fd 1795fe24 7f427d47 1795fe18 activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 7f427d33 1795fe18 activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 7f427cef 1795fe18 activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 1795f60c 0ef4a264 activemq_cppu!activemq::transport::inactivity::InactivityMonitor::onException+33 1795fe24 7f427cd7 1795fe18 activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 7f427c83 1795fe18 activemq_cppu!activemq::transport::IOTransport::fire+4b 1795fe24 0ec48ed7 1795fe18 activemq_cppu!activemq::transport::IOTransport::run+15e 7f427107 7c809c65 12519500 activemq_cppu!decaf::lang::ThreadProperties::runCallback+82 7c936d80 04682060 0ec229bb activemq_cppu!`anonymous namespace'::threadWorker+20 04682060 0ec229bb 12519500 ntdll!RtlRemoveVectoredExceptionHandler+2a2 04682060 7c80b729 1252f168 msvcr80!endthreadex+c7 0ec229e1 1252f168 KERNEL32!INTERLOCKEDDECREMENT+9WARNING - DebugDiag was not able to locate debug symbols for kernel32.dll, so the information below may be incomplete. In ScotAppU__PID__1168__Date__05_24_2012__Time_02_18_41PM__916__Second_Chance_Exception_C005.dmp the assembly instruction at kernel32!InterlockedDecrement+9 in C:\WINDOWS\system32\kernel32.dll from Microsoft Corporation has caused an access violation exception (0xC005) when trying to write to memory location 0x014718e4 on thread 0 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQCPP-407) Application crashes after stopping message broker
[ https://issues.apache.org/jira/browse/AMQCPP-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13288945#comment-13288945 ] Helen Huang commented on AMQCPP-407: By the way did you look at this following stack (you probably did, but I just want to make sure) This thread shows a connection can be destroyed by CmsTemplate. Is there any way to prevent IOTransport from calling onException, when a connection is being destroyed? activemq-cppud.dll!activemq::core::ActiveMQConnection::~ActiveMQConnection() Line 242 C++ activemq-cppud.dll!activemq::core::ActiveMQConnection::`vbase destructor'() + 0xf bytes C++ activemq-cppud.dll!activemq::core::ActiveMQConnection::`vector deleting destructor'() + 0x4d bytes C++ activemq-cppud.dll!activemq::cmsutil::ResourceLifecycleManager::destroy() Line 135 + 0x20 bytes C++ activemq-cppud.dll!activemq::cmsutil::CmsAccessor::destroy() Line 131 C++ activemq-cppud.dll!activemq::cmsutil::CmsDestinationAccessor::destroy() Line 58 C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::destroy() Line 211 + 0xb bytes C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::ProducerExecutor::doInCms(cms::Session * session=0x01231668) Line 527 + 0x1a bytes C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::execute(activemq::cmsutil::SessionCallback * action=0x0012fb80) Line 446 C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::execute(activemq::cmsutil::ProducerCallback * action=0x0012fc08) Line 465 C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::send(activemq::cmsutil::MessageCreator * messageCreator=0x01210698) Line 546 C++ BrokerMonitor.exe!main(int argc=1, char * * argv=0x00b78fb8) Line 76 + 0x1f bytes C++ BrokerMonitor.exe!__tmainCRTStartup() Line 597 + 0x19 bytes C BrokerMonitor.exe!mainCRTStartup() Line 414 C Application crashes after stopping message broker - Key: AMQCPP-407 URL: https://issues.apache.org/jira/browse/AMQCPP-407 Project: ActiveMQ C++ Client Issue Type: Bug Components: CMS Impl Affects Versions: 3.4.1 Environment: Windows xp service pack 3, ActiveMQ broker 5.3.1, apr 1.4.2, apr-util 1.3.9, apr iconv 1.2.1 Reporter: Helen Huang Assignee: Timothy Bish Priority: Blocker Fix For: 3.4.1 Attachments: AttemptedFix1.7z Stopping the message broker would crash our application. The following is the call stack of the fault thread. Thread 0 - System ID 672 Entry point msvcr80!endthreadex+61 Create time 5/24/2012 1:53:56 PM Time spent in user mode 0 Days 0:0:0.46 Time spent in kernel mode 0 Days 0:0:0.78 Function Arg 1 Arg 2 Arg 3 Source kernel32!InterlockedDecrement+9 00242110 msvcrt!cexit+f 77c1 0001 ntdll!LdrInitializeThunk+24 77c1f2a1 77c1 ntdll!RtlDestroyEnvironment+178 0eec256d 0001 kernel32!IsValidLocale+8eb 0003 77e8f3b0 kernel32!ExitProcess+14 0003 0ec21a04 0003 msvcr80!amsg_exit+5e 0003 0001 msvcr80!exit+d 1795efe0 user32!MessageBoxIndirectA+23a 0001 7c91005d 13946b5e user32!MessageBoxIndirectA+254 13946b5e 00e30850 ntdll!RtlFreeHeap+130 0468001b 0202 1795f110 activemq_cppu!activemq::core::ActiveMQConnection::onException+fd 1795fe24 7f427d47 1795fe18 activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 7f427d33 1795fe18 activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 7f427cef 1795fe18 activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 1795f60c 0ef4a264 activemq_cppu!activemq::transport::inactivity::InactivityMonitor::onException+33 1795fe24 7f427cd7 1795fe18 activemq_cppu!activemq::transport::TransportFilter::fire+44 1795fe24 7f427c83 1795fe18 activemq_cppu!activemq::transport::IOTransport::fire+4b 1795fe24 0ec48ed7 1795fe18 activemq_cppu!activemq::transport::IOTransport::run+15e 7f427107 7c809c65 12519500 activemq_cppu!decaf::lang::ThreadProperties::runCallback+82 7c936d80 04682060 0ec229bb activemq_cppu!`anonymous namespace'::threadWorker+20 04682060 0ec229bb 12519500 ntdll!RtlRemoveVectoredExceptionHandler+2a2 04682060 7c80b729 1252f168 msvcr80!endthreadex+c7 0ec229e1 1252f168 KERNEL32!INTERLOCKEDDECREMENT+9WARNING - DebugDiag was not able to locate debug symbols for kernel32.dll, so the information below
[jira] [Comment Edited] (AMQCPP-407) Application crashes after stopping message broker
[ https://issues.apache.org/jira/browse/AMQCPP-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13288945#comment-13288945 ] Helen Huang edited comment on AMQCPP-407 at 6/4/12 10:06 PM: - By the way did you look at this following stack (you probably did, but just in case) This thread shows a connection can be destroyed by CmsTemplate. Is there any way to prevent IOTransport from calling onException, when a connection is being destroyed? activemq-cppud.dll!activemq::core::ActiveMQConnection::~ActiveMQConnection() Line 242 C++ activemq-cppud.dll!activemq::core::ActiveMQConnection::`vbase destructor'() + 0xf bytes C++ activemq-cppud.dll!activemq::core::ActiveMQConnection::`vector deleting destructor'() + 0x4d bytes C++ activemq-cppud.dll!activemq::cmsutil::ResourceLifecycleManager::destroy() Line 135 + 0x20 bytes C++ activemq-cppud.dll!activemq::cmsutil::CmsAccessor::destroy() Line 131 C++ activemq-cppud.dll!activemq::cmsutil::CmsDestinationAccessor::destroy() Line 58 C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::destroy() Line 211 + 0xb bytes C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::ProducerExecutor::doInCms(cms::Session * session=0x01231668) Line 527 + 0x1a bytes C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::execute(activemq::cmsutil::SessionCallback * action=0x0012fb80) Line 446 C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::execute(activemq::cmsutil::ProducerCallback * action=0x0012fc08) Line 465 C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::send(activemq::cmsutil::MessageCreator * messageCreator=0x01210698) Line 546 C++ BrokerMonitor.exe!main(int argc=1, char * * argv=0x00b78fb8) Line 76 + 0x1f bytes C++ BrokerMonitor.exe!__tmainCRTStartup() Line 597 + 0x19 bytes C BrokerMonitor.exe!mainCRTStartup() Line 414 C was (Author: hhuang): By the way did you look at this following stack (you probably did, but I just want to make sure) This thread shows a connection can be destroyed by CmsTemplate. Is there any way to prevent IOTransport from calling onException, when a connection is being destroyed? activemq-cppud.dll!activemq::core::ActiveMQConnection::~ActiveMQConnection() Line 242 C++ activemq-cppud.dll!activemq::core::ActiveMQConnection::`vbase destructor'() + 0xf bytes C++ activemq-cppud.dll!activemq::core::ActiveMQConnection::`vector deleting destructor'() + 0x4d bytes C++ activemq-cppud.dll!activemq::cmsutil::ResourceLifecycleManager::destroy() Line 135 + 0x20 bytes C++ activemq-cppud.dll!activemq::cmsutil::CmsAccessor::destroy() Line 131 C++ activemq-cppud.dll!activemq::cmsutil::CmsDestinationAccessor::destroy() Line 58 C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::destroy() Line 211 + 0xb bytes C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::ProducerExecutor::doInCms(cms::Session * session=0x01231668) Line 527 + 0x1a bytes C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::execute(activemq::cmsutil::SessionCallback * action=0x0012fb80) Line 446 C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::execute(activemq::cmsutil::ProducerCallback * action=0x0012fc08) Line 465 C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::send(activemq::cmsutil::MessageCreator * messageCreator=0x01210698) Line 546 C++ BrokerMonitor.exe!main(int argc=1, char * * argv=0x00b78fb8) Line 76 + 0x1f bytes C++ BrokerMonitor.exe!__tmainCRTStartup() Line 597 + 0x19 bytes C BrokerMonitor.exe!mainCRTStartup() Line 414 C Application crashes after stopping message broker - Key: AMQCPP-407 URL: https://issues.apache.org/jira/browse/AMQCPP-407 Project: ActiveMQ C++ Client Issue Type: Bug Components: CMS Impl Affects Versions: 3.4.1 Environment: Windows xp service pack 3, ActiveMQ broker 5.3.1, apr 1.4.2, apr-util 1.3.9, apr iconv 1.2.1 Reporter: Helen Huang Assignee: Timothy Bish Priority: Blocker Fix For: 3.4.1 Attachments: AttemptedFix1.7z Stopping the message broker would crash our application. The following is the call stack of the fault thread. Thread 0 - System ID 672 Entry point msvcr80!endthreadex+61 Create time 5/24/2012 1:53:56 PM Time spent in user mode 0 Days 0:0:0.46 Time spent in kernel mode 0 Days 0:0:0.78 Function Arg 1 Arg 2 Arg 3 Source kernel32!InterlockedDecrement+9 00242110 msvcrt!cexit+f 77c1 0001 ntdll!LdrInitializeThunk+24 77c1f2a1 77c1 ntdll!RtlDestroyEnvironment+178 0eec256d 0001 kernel32!IsValidLocale+8eb 0003 77e8f3b0 kernel32!ExitProcess+14 0003 0ec21a04
[jira] [Comment Edited] (AMQCPP-407) Application crashes after stopping message broker
[ https://issues.apache.org/jira/browse/AMQCPP-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13288945#comment-13288945 ] Helen Huang edited comment on AMQCPP-407 at 6/4/12 10:08 PM: - By the way did you look at this following stack (you probably did, but just in case) This thread shows a connection can be destroyed by CmsTemplate. Is there any way to prevent IOTransport/TransportFilter from calling fire(), when a connection is being destroyed? activemq-cppud.dll!activemq::core::ActiveMQConnection::~ActiveMQConnection() Line 242 C++ activemq-cppud.dll!activemq::core::ActiveMQConnection::`vbase destructor'() + 0xf bytes C++ activemq-cppud.dll!activemq::core::ActiveMQConnection::`vector deleting destructor'() + 0x4d bytes C++ activemq-cppud.dll!activemq::cmsutil::ResourceLifecycleManager::destroy() Line 135 + 0x20 bytes C++ activemq-cppud.dll!activemq::cmsutil::CmsAccessor::destroy() Line 131 C++ activemq-cppud.dll!activemq::cmsutil::CmsDestinationAccessor::destroy() Line 58 C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::destroy() Line 211 + 0xb bytes C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::ProducerExecutor::doInCms(cms::Session * session=0x01231668) Line 527 + 0x1a bytes C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::execute(activemq::cmsutil::SessionCallback * action=0x0012fb80) Line 446 C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::execute(activemq::cmsutil::ProducerCallback * action=0x0012fc08) Line 465 C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::send(activemq::cmsutil::MessageCreator * messageCreator=0x01210698) Line 546 C++ BrokerMonitor.exe!main(int argc=1, char * * argv=0x00b78fb8) Line 76 + 0x1f bytes C++ BrokerMonitor.exe!__tmainCRTStartup() Line 597 + 0x19 bytes C BrokerMonitor.exe!mainCRTStartup() Line 414 C was (Author: hhuang): By the way did you look at this following stack (you probably did, but just in case) This thread shows a connection can be destroyed by CmsTemplate. Is there any way to prevent IOTransport from calling onException, when a connection is being destroyed? activemq-cppud.dll!activemq::core::ActiveMQConnection::~ActiveMQConnection() Line 242 C++ activemq-cppud.dll!activemq::core::ActiveMQConnection::`vbase destructor'() + 0xf bytes C++ activemq-cppud.dll!activemq::core::ActiveMQConnection::`vector deleting destructor'() + 0x4d bytes C++ activemq-cppud.dll!activemq::cmsutil::ResourceLifecycleManager::destroy() Line 135 + 0x20 bytes C++ activemq-cppud.dll!activemq::cmsutil::CmsAccessor::destroy() Line 131 C++ activemq-cppud.dll!activemq::cmsutil::CmsDestinationAccessor::destroy() Line 58 C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::destroy() Line 211 + 0xb bytes C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::ProducerExecutor::doInCms(cms::Session * session=0x01231668) Line 527 + 0x1a bytes C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::execute(activemq::cmsutil::SessionCallback * action=0x0012fb80) Line 446 C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::execute(activemq::cmsutil::ProducerCallback * action=0x0012fc08) Line 465 C++ activemq-cppud.dll!activemq::cmsutil::CmsTemplate::send(activemq::cmsutil::MessageCreator * messageCreator=0x01210698) Line 546 C++ BrokerMonitor.exe!main(int argc=1, char * * argv=0x00b78fb8) Line 76 + 0x1f bytes C++ BrokerMonitor.exe!__tmainCRTStartup() Line 597 + 0x19 bytes C BrokerMonitor.exe!mainCRTStartup() Line 414 C Application crashes after stopping message broker - Key: AMQCPP-407 URL: https://issues.apache.org/jira/browse/AMQCPP-407 Project: ActiveMQ C++ Client Issue Type: Bug Components: CMS Impl Affects Versions: 3.4.1 Environment: Windows xp service pack 3, ActiveMQ broker 5.3.1, apr 1.4.2, apr-util 1.3.9, apr iconv 1.2.1 Reporter: Helen Huang Assignee: Timothy Bish Priority: Blocker Fix For: 3.4.1 Attachments: AttemptedFix1.7z Stopping the message broker would crash our application. The following is the call stack of the fault thread. Thread 0 - System ID 672 Entry point msvcr80!endthreadex+61 Create time 5/24/2012 1:53:56 PM Time spent in user mode 0 Days 0:0:0.46 Time spent in kernel mode 0 Days 0:0:0.78 Function Arg 1 Arg 2 Arg 3 Source kernel32!InterlockedDecrement+9 00242110 msvcrt!cexit+f 77c1 0001 ntdll!LdrInitializeThunk+24 77c1f2a1 77c1 ntdll!RtlDestroyEnvironment+178 0eec256d 0001 kernel32!IsValidLocale+8eb 0003 77e8f3b0 kernel32!ExitProcess+14 0003 0ec21a04
[jira] [Commented] (AMQ-498) Secure the server from simple DoS attacks
[ https://issues.apache.org/jira/browse/AMQ-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13288999#comment-13288999 ] Matthew Good commented on AMQ-498: -- Fyi, this change broke us. In the future you should try to make changes that are backwards compatible. If they are not, they should be explicitly mentioned in the release notes. In this case, how many people really need it? It could have been that if the maxFrameSize is not explicitly set, then frame size checking would be disabled - as before. I will say, it is a great feature for those who have publicly exposed brokers. Thanks! Secure the server from simple DoS attacks - Key: AMQ-498 URL: https://issues.apache.org/jira/browse/AMQ-498 Project: ActiveMQ Issue Type: Improvement Components: Broker Environment: An untrusted network. DoS attack attempts are common. Reporter: Hiram Chirino Assignee: Hiram Chirino Fix For: 5.6.0 Originating from http://forums.logicblaze.com/posts/list/205.page Simply start the 4.0 server (I used the stock config) in another window telnet to localhost 61616 you will receieve: ActiveMQ^[[?1;2c type asdfasdf The connection will close by itself. All future TCP connections, either from telnet or from real JMS clients, will hang. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQNET-249) Is API Receive having ordering problem?
[ https://issues.apache.org/jira/browse/AMQNET-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13289158#comment-13289158 ] Tamilmaran commented on AMQNET-249: --- How did you fix it? I'm facing the same issue.I have used only NMS DLL. I am not supposed to use NMS.ActiveMQ DLL. In this case, How to get rid of this issue? Is API Receive having ordering problem? --- Key: AMQNET-249 URL: https://issues.apache.org/jira/browse/AMQNET-249 Project: ActiveMQ .Net Issue Type: Bug Components: NMS Affects Versions: 1.1.0 Environment: ActiveMQ is running on Linunx Ubuntu, VB.NET + Apache.NMS is running on WinXP Reporter: jim yu Assignee: Jim Gomes Fix For: 1.2.0 Original Estimate: 1h Remaining Estimate: 1h Hi, All, If try the following steps, the API receive won't work normally.. 1. have 2 programs, one is sender for sending message to actuvemq, another is receiver for receiving message from activemq. 2. Start a connection from the sender to activemq first. 3. Start a connection from the receiver to qctivemq and call consumer.Receive (API Receive) to wait for retrieving data form activemq. 4. Call request.send (API Send) to send a message to activemq in sender. 5. The data will be drop by activemq but Receiver will never get data from activemq. However, API Receive will work normally if start the receiver first and then start the sender. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
