You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Justin Pitts (JIRA)" <ji...@apache.org> on 2008/10/30 02:13:52 UTC
[jira] Created: (AMQ-1990) Failing network connectors randomly log
SEVERE message : Could not accept connection : java.lang.Object cannot be
cast to org.apache.activemq.command.Command
Failing network connectors randomly log SEVERE message : Could not accept connection : java.lang.Object cannot be cast to org.apache.activemq.command.Command
-------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: AMQ-1990
URL: https://issues.apache.org/activemq/browse/AMQ-1990
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 5.1.0
Environment: Linux, Windows XP, Mac OSX 10.5.1
Reporter: Justin Pitts
I have an application which embeds the broker service. A common deployment scenario is a sometimes-connected network of these applications. Unfortunately, I don't have many situations where I can use discovery, so the network connectors are static configurations. Randomly, when these network connections are unable to connect, I see the following exception trace:
30 Sep 2008 18:36:18 ERROR [ActiveMQ Transport Initiator: vm://instance-2#2] (TransportConnector.java:234) - Could not accept connection : java.lang.Object cannot be cast to org.apache.activemq.command.Command
These errors seem like they might be the result of a race condition during start or stop of a network connector. I will attach a sample application which demonstrates the problem. You may have to run the application a couple times to provoke it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-1990) Failing network connectors randomly log
SEVERE message : Could not accept connection : java.lang.Object cannot be
cast to org.apache.activemq.command.Command
Posted by "Justin Pitts (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Justin Pitts updated AMQ-1990:
------------------------------
Attachment: CouldNotAcceptConnection.java
This application demonstrates the issue. Run the application, and observe the SEVERE level log message "Unable to accept connection"
> Failing network connectors randomly log SEVERE message : Could not accept connection : java.lang.Object cannot be cast to org.apache.activemq.command.Command
> -------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-1990
> URL: https://issues.apache.org/activemq/browse/AMQ-1990
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.1.0
> Environment: Linux, Windows XP, Mac OSX 10.5.1
> Reporter: Justin Pitts
> Attachments: CouldNotAcceptConnection.java
>
>
> I have an application which embeds the broker service. A common deployment scenario is a sometimes-connected network of these applications. Unfortunately, I don't have many situations where I can use discovery, so the network connectors are static configurations. Randomly, when these network connections are unable to connect, I see the following exception trace:
> 30 Sep 2008 18:36:18 ERROR [ActiveMQ Transport Initiator: vm://instance-2#2] (TransportConnector.java:234) - Could not accept connection : java.lang.Object cannot be cast to org.apache.activemq.command.Command
> These errors seem like they might be the result of a race condition during start or stop of a network connector. I will attach a sample application which demonstrates the problem. You may have to run the application a couple times to provoke it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1990) Failing network connectors randomly
log SEVERE message : Could not accept connection : java.lang.Object cannot
be cast to org.apache.activemq.command.Command
Posted by "Gary Tully (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47023#action_47023 ]
Gary Tully commented on AMQ-1990:
---------------------------------
Justin,
I put this test in a loop and ran 20 times against trunk but did not see the error message. Have you verified with trunk or a 5.3-SNAPSHOT?
thanks
> Failing network connectors randomly log SEVERE message : Could not accept connection : java.lang.Object cannot be cast to org.apache.activemq.command.Command
> -------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-1990
> URL: https://issues.apache.org/activemq/browse/AMQ-1990
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.1.0
> Environment: Linux, Windows XP, Mac OSX 10.5.1
> Reporter: Justin Pitts
> Attachments: CouldNotAcceptConnection.java
>
>
> I have an application which embeds the broker service. A common deployment scenario is a sometimes-connected network of these applications. Unfortunately, I don't have many situations where I can use discovery, so the network connectors are static configurations. Randomly, when these network connections are unable to connect, I see the following exception trace:
> 30 Sep 2008 18:36:18 ERROR [ActiveMQ Transport Initiator: vm://instance-2#2] (TransportConnector.java:234) - Could not accept connection : java.lang.Object cannot be cast to org.apache.activemq.command.Command
> These errors seem like they might be the result of a race condition during start or stop of a network connector. I will attach a sample application which demonstrates the problem. You may have to run the application a couple times to provoke it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1990) Failing network connectors randomly
log SEVERE message : Could not accept connection : java.lang.Object cannot
be cast to org.apache.activemq.command.Command
Posted by "Benoit Xhenseval (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51379#action_51379 ]
Benoit Xhenseval commented on AMQ-1990:
---------------------------------------
We have this issue with 5.2 and 5.3-snapshot (18 April).
The same application seems to be running ok under XP, OpenSolaris but throws those exceptions at a rate of 1 every minute or so under Ubuntu Server 8.10.
HTH
Benoit.
> Failing network connectors randomly log SEVERE message : Could not accept connection : java.lang.Object cannot be cast to org.apache.activemq.command.Command
> -------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-1990
> URL: https://issues.apache.org/activemq/browse/AMQ-1990
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.1.0
> Environment: Linux, Windows XP, Mac OSX 10.5.1
> Reporter: Justin Pitts
> Attachments: CouldNotAcceptConnection.java
>
>
> I have an application which embeds the broker service. A common deployment scenario is a sometimes-connected network of these applications. Unfortunately, I don't have many situations where I can use discovery, so the network connectors are static configurations. Randomly, when these network connections are unable to connect, I see the following exception trace:
> 30 Sep 2008 18:36:18 ERROR [ActiveMQ Transport Initiator: vm://instance-2#2] (TransportConnector.java:234) - Could not accept connection : java.lang.Object cannot be cast to org.apache.activemq.command.Command
> These errors seem like they might be the result of a race condition during start or stop of a network connector. I will attach a sample application which demonstrates the problem. You may have to run the application a couple times to provoke it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1990) Failing network connectors randomly
log SEVERE message : Could not accept connection : java.lang.Object cannot
be cast to org.apache.activemq.command.Command
Posted by "Justin Pitts (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=47032#action_47032 ]
Justin Pitts commented on AMQ-1990:
-----------------------------------
I have not verified in anything but 5.1. Our product is currently shipping with 5.1. Should I not expect this issue to be addressed in 5.1?
> Failing network connectors randomly log SEVERE message : Could not accept connection : java.lang.Object cannot be cast to org.apache.activemq.command.Command
> -------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-1990
> URL: https://issues.apache.org/activemq/browse/AMQ-1990
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.1.0
> Environment: Linux, Windows XP, Mac OSX 10.5.1
> Reporter: Justin Pitts
> Attachments: CouldNotAcceptConnection.java
>
>
> I have an application which embeds the broker service. A common deployment scenario is a sometimes-connected network of these applications. Unfortunately, I don't have many situations where I can use discovery, so the network connectors are static configurations. Randomly, when these network connections are unable to connect, I see the following exception trace:
> 30 Sep 2008 18:36:18 ERROR [ActiveMQ Transport Initiator: vm://instance-2#2] (TransportConnector.java:234) - Could not accept connection : java.lang.Object cannot be cast to org.apache.activemq.command.Command
> These errors seem like they might be the result of a race condition during start or stop of a network connector. I will attach a sample application which demonstrates the problem. You may have to run the application a couple times to provoke it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-1990) Failing network connectors randomly log
SEVERE message : Could not accept connection : java.lang.Object cannot be
cast to org.apache.activemq.command.Command
Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1990?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bruce Snyder updated AMQ-1990:
------------------------------
Fix Version/s: 5.5.0
(was: 5.4.1)
> Failing network connectors randomly log SEVERE message : Could not accept connection : java.lang.Object cannot be cast to org.apache.activemq.command.Command
> -------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-1990
> URL: https://issues.apache.org/activemq/browse/AMQ-1990
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.1.0
> Environment: Linux, Windows XP, Mac OSX 10.5.1
> Reporter: Justin Pitts
> Fix For: 5.5.0
>
> Attachments: CouldNotAcceptConnection.java
>
>
> I have an application which embeds the broker service. A common deployment scenario is a sometimes-connected network of these applications. Unfortunately, I don't have many situations where I can use discovery, so the network connectors are static configurations. Randomly, when these network connections are unable to connect, I see the following exception trace:
> 30 Sep 2008 18:36:18 ERROR [ActiveMQ Transport Initiator: vm://instance-2#2] (TransportConnector.java:234) - Could not accept connection : java.lang.Object cannot be cast to org.apache.activemq.command.Command
> These errors seem like they might be the result of a race condition during start or stop of a network connector. I will attach a sample application which demonstrates the problem. You may have to run the application a couple times to provoke it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.