[
https://issues.apache.org/jira/browse/AMQ-6677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Nedzvetsky updated AMQ-6677:
-----------------------------------
Description:
I reproduced this issue with NIO setup.
Steps to reproduce:
1. copy wrapper.conf to bin/win64 and activemq.xml to conf directory(attached)
2. start Activemq in the console mode
3. install nodejs
4. unpack files from the archive deadlock.zip to some directory
5. execute npm.exe install stomp
6. execute nodejs suppliers.js and wait about 10 seconds
7. execute nodejs consumers.js and wait about 20 seconds
8. open activemq console and type ctrl-break or kill -3 <actiemq-pid>
stop Activemq and reproduce steps 6 - 8 again if deadlock message doesn't exist.
was:
I reproduced this issue with NIO setup.
Steps to reproduce:
1. replace wrapper.conf and activemq.xml files(attached)
2. start Activemq in the console mode
3. install nodejs
4. unpack files from the archive deadlock.zip to some directory
5. execute npm.exe install stomp
6. execute nodejs suppliers.js and wait about 10 seconds
7. execute nodejs consumers.js and 20 seconds
8. open activemq console and type ctrl-break or kill -3 <actiemq-pid>
stop Activemq and reproduce steps 6 - 8 again if deadlock message doesn't exist.
> NIO setup produces deadlock on add new subscriber
> --------------------------------------------------
>
> Key: AMQ-6677
> URL: https://issues.apache.org/jira/browse/AMQ-6677
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.14.5
> Environment: Windows 7 x64
> Reporter: Eugene Nedzvetsky
> Attachments: activemq.xml, deadlock.txt, deadlock.zip,
> full-stack.txt, wrapper.conf
>
>
> I reproduced this issue with NIO setup.
> Steps to reproduce:
> 1. copy wrapper.conf to bin/win64 and activemq.xml to conf directory(attached)
> 2. start Activemq in the console mode
> 3. install nodejs
> 4. unpack files from the archive deadlock.zip to some directory
> 5. execute npm.exe install stomp
> 6. execute nodejs suppliers.js and wait about 10 seconds
> 7. execute nodejs consumers.js and wait about 20 seconds
> 8. open activemq console and type ctrl-break or kill -3 <actiemq-pid>
> stop Activemq and reproduce steps 6 - 8 again if deadlock message doesn't
> exist.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
