You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Pavel Jaoshvili (JIRA)" <ji...@apache.org> on 2011/07/15 08:18:59 UTC
[jira] [Created] (AMQCPP-377) Does not detect broken connection on
Windows
Does not detect broken connection on Windows
--------------------------------------------
Key: AMQCPP-377
URL: https://issues.apache.org/jira/browse/AMQCPP-377
Project: ActiveMQ C++ Client
Issue Type: Bug
Components: Openwire
Affects Versions: 3.3.0
Environment: Windows XP, Windows 7
Reporter: Pavel Jaoshvili
Assignee: Timothy Bish
Inactivity monitor does not detect broken connection.
transportInterrupted and transportResumed not called.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Issue Comment Edited] (AMQCPP-377) Does not detect broken
connection on Windows
Posted by "Pavel Jaoshvili (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068194#comment-13068194 ]
Pavel Jaoshvili edited comment on AMQCPP-377 at 7/20/11 7:40 AM:
-----------------------------------------------------------------
string brokerURI =
"failover:(tcp://"+servername+":61616"
"?wireFormat=openwire"
"&wireFormat.maxInactivityDuration=5000"
")";
Not working too
was (Author: jao):
string brokerURI =
"failover:(tcp://"+servername+":61616"
"?wireFormat=openwire"
"&wireFormat.maxInactivityDuratione=5000"
")";
Not working too
> Does not detect broken connection on Windows
> --------------------------------------------
>
> Key: AMQCPP-377
> URL: https://issues.apache.org/jira/browse/AMQCPP-377
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: Openwire
> Affects Versions: 3.3.0
> Environment: Windows XP, Windows 7
> Reporter: Pavel Jaoshvili
> Assignee: Timothy Bish
>
> Inactivity monitor does not detect broken connection.
> transportInterrupted and transportResumed not called.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQCPP-377) Does not detect broken connection
on Windows
Posted by "Pavel Jaoshvili (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068180#comment-13068180 ]
Pavel Jaoshvili commented on AMQCPP-377:
----------------------------------------
On v3.4.0 problem still exists.
May this be due to compilation warnings?
c:\Temp\amq\activemq-cpp-library\src\main\decaf/lang/Throwable.h(44) : warning C4275: non dll-interface class 'std::exception' used as base for dll-interface class 'decaf::lang::Throwable'
C:\Program Files\Microsoft Visual Studio 9.0\VC\include\exception(95) : see declaration of 'std::exception'
c:\Temp\amq\activemq-cpp-library\src\main\decaf/lang/Throwable.h(44) : see declaration of 'decaf::lang::Throwable'
What connection settings are responsible for the work of InactivityMonitor?
> Does not detect broken connection on Windows
> --------------------------------------------
>
> Key: AMQCPP-377
> URL: https://issues.apache.org/jira/browse/AMQCPP-377
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: Openwire
> Affects Versions: 3.3.0
> Environment: Windows XP, Windows 7
> Reporter: Pavel Jaoshvili
> Assignee: Timothy Bish
>
> Inactivity monitor does not detect broken connection.
> transportInterrupted and transportResumed not called.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQCPP-377) Does not detect broken connection
on Windows
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072334#comment-13072334 ]
Timothy Bish commented on AMQCPP-377:
-------------------------------------
I haven't had any time to work on it, my suggestion is still that you do some debugging of the InactivityMonitor class to see what is going on there that causes the connection drop to be missed. You can also take a look at trunk to see the recent patch to ActiveMQConnection and try that to see if that helps your close problem.
> Does not detect broken connection on Windows
> --------------------------------------------
>
> Key: AMQCPP-377
> URL: https://issues.apache.org/jira/browse/AMQCPP-377
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: Openwire
> Affects Versions: 3.3.0
> Environment: Windows XP, Windows 7
> Reporter: Pavel Jaoshvili
> Assignee: Timothy Bish
>
> Inactivity monitor does not detect broken connection.
> transportInterrupted and transportResumed not called.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQCPP-377) Does not detect broken connection
on Windows
Posted by "Pavel Jaoshvili (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065837#comment-13065837 ]
Pavel Jaoshvili commented on AMQCPP-377:
----------------------------------------
string brokerURI =
"failover:(tcp://"+servername+":61616"
"?wireFormat=openwire"
"&soKeepAlive=true"
"&jms.useCompression=true"
"&jms.prefetchPolicy.queuePrefetch=1"
")";
This problem occurs if the connection is dropped in the middle.
For example, node A is connected to the router B, which is connected to the server C. If lost connection between nodes B and C, then node A about anything without getting caught.
> Does not detect broken connection on Windows
> --------------------------------------------
>
> Key: AMQCPP-377
> URL: https://issues.apache.org/jira/browse/AMQCPP-377
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: Openwire
> Affects Versions: 3.3.0
> Environment: Windows XP, Windows 7
> Reporter: Pavel Jaoshvili
> Assignee: Timothy Bish
>
> Inactivity monitor does not detect broken connection.
> transportInterrupted and transportResumed not called.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQCPP-377) Does not detect broken connection
on Windows
Posted by "Pavel Jaoshvili (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068346#comment-13068346 ]
Pavel Jaoshvili commented on AMQCPP-377:
----------------------------------------
To reproduce the problem, you can run producer in the virtual machine. After disabling the network producer will not detect broken connection.
> Does not detect broken connection on Windows
> --------------------------------------------
>
> Key: AMQCPP-377
> URL: https://issues.apache.org/jira/browse/AMQCPP-377
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: Openwire
> Affects Versions: 3.3.0
> Environment: Windows XP, Windows 7
> Reporter: Pavel Jaoshvili
> Assignee: Timothy Bish
>
> Inactivity monitor does not detect broken connection.
> transportInterrupted and transportResumed not called.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQCPP-377) Does not detect broken connection
on Windows
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068338#comment-13068338 ]
Timothy Bish commented on AMQCPP-377:
-------------------------------------
The InactivityMonitor looks at the wireFormat.maxInactivityDuration. Since this isn't reproducible on my end you will need to step into the inactivity monitor code and see why the timers aren't firing off errors when the connection drops.
> Does not detect broken connection on Windows
> --------------------------------------------
>
> Key: AMQCPP-377
> URL: https://issues.apache.org/jira/browse/AMQCPP-377
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: Openwire
> Affects Versions: 3.3.0
> Environment: Windows XP, Windows 7
> Reporter: Pavel Jaoshvili
> Assignee: Timothy Bish
>
> Inactivity monitor does not detect broken connection.
> transportInterrupted and transportResumed not called.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQCPP-377) Does not detect broken connection
on Windows
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066002#comment-13066002 ]
Timothy Bish commented on AMQCPP-377:
-------------------------------------
You may want to try out v3.4.0 to see if any of the fixes in that release help you out. Also the uri options in your example aren't quite correct. See the configuration page for CMS for the correct options: http://activemq.apache.org/cms/configuring.html.
> Does not detect broken connection on Windows
> --------------------------------------------
>
> Key: AMQCPP-377
> URL: https://issues.apache.org/jira/browse/AMQCPP-377
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: Openwire
> Affects Versions: 3.3.0
> Environment: Windows XP, Windows 7
> Reporter: Pavel Jaoshvili
> Assignee: Timothy Bish
>
> Inactivity monitor does not detect broken connection.
> transportInterrupted and transportResumed not called.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (AMQCPP-377) Does not detect broken connection on
Windows
Posted by "Timothy Bish (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish closed AMQCPP-377.
-------------------------------
Resolution: Cannot Reproduce
Can't seem to find any cases where the inactivity is not detected and the connection restored.
> Does not detect broken connection on Windows
> --------------------------------------------
>
> Key: AMQCPP-377
> URL: https://issues.apache.org/jira/browse/AMQCPP-377
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: Openwire
> Affects Versions: 3.3.0
> Environment: Windows XP, Windows 7
> Reporter: Pavel Jaoshvili
> Assignee: Timothy Bish
>
> Inactivity monitor does not detect broken connection.
> transportInterrupted and transportResumed not called.
--
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-377) Does not detect broken connection
on Windows
Posted by "Pavel Jaoshvili (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13068194#comment-13068194 ]
Pavel Jaoshvili commented on AMQCPP-377:
----------------------------------------
string brokerURI =
"failover:(tcp://"+servername+":61616"
"?wireFormat=openwire"
"&wireFormat.maxInactivityDuratione=5000"
")";
Not working too
> Does not detect broken connection on Windows
> --------------------------------------------
>
> Key: AMQCPP-377
> URL: https://issues.apache.org/jira/browse/AMQCPP-377
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: Openwire
> Affects Versions: 3.3.0
> Environment: Windows XP, Windows 7
> Reporter: Pavel Jaoshvili
> Assignee: Timothy Bish
>
> Inactivity monitor does not detect broken connection.
> transportInterrupted and transportResumed not called.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQCPP-377) Does not detect broken connection
on Windows
Posted by "Pavel Jaoshvili (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072319#comment-13072319 ]
Pavel Jaoshvili commented on AMQCPP-377:
----------------------------------------
Any suggestions?
In addition. if connection is broken it's impossible to properly terminate the application. It hangs on session->close() or connection->close().
> Does not detect broken connection on Windows
> --------------------------------------------
>
> Key: AMQCPP-377
> URL: https://issues.apache.org/jira/browse/AMQCPP-377
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: Openwire
> Affects Versions: 3.3.0
> Environment: Windows XP, Windows 7
> Reporter: Pavel Jaoshvili
> Assignee: Timothy Bish
>
> Inactivity monitor does not detect broken connection.
> transportInterrupted and transportResumed not called.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQCPP-377) Does not detect broken connection
on Windows
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQCPP-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065829#comment-13065829 ]
Timothy Bish commented on AMQCPP-377:
-------------------------------------
Not really enough information to go on here. Under what circumstances is the problem occurring? What is your URI that you are using to connect?
> Does not detect broken connection on Windows
> --------------------------------------------
>
> Key: AMQCPP-377
> URL: https://issues.apache.org/jira/browse/AMQCPP-377
> Project: ActiveMQ C++ Client
> Issue Type: Bug
> Components: Openwire
> Affects Versions: 3.3.0
> Environment: Windows XP, Windows 7
> Reporter: Pavel Jaoshvili
> Assignee: Timothy Bish
>
> Inactivity monitor does not detect broken connection.
> transportInterrupted and transportResumed not called.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira