activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Tully (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQ-2201) DemandForwardingBridge shutdown due to java.io.IOException: Unknown data type
Date Wed, 08 Apr 2009 19:13:35 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-2201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=51111#action_51111
] 

Gary Tully commented on AMQ-2201:
---------------------------------

Just a thought, but I wonder if this is chatter on the multicast address you use. what do
you use as the group on the discovery multicast address.
Ensure that it is something unique: discoveryUri="multicast://default?group=MyUniqueInMyDomainProjectName"

> DemandForwardingBridge shutdown due to java.io.IOException: Unknown data type
> -----------------------------------------------------------------------------
>
>                 Key: AMQ-2201
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2201
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Connector
>    Affects Versions: 5.2.0
>         Environment: Solaris 10 java 1.6
>            Reporter: ying
>             Fix For: 5.3.0
>
>
> I have a network of 4 brokers and I sporadically see the following error:
> 2009-04-06 15:48:29,849 [0.0.0.237:61616] WARN  DemandForwardingBridge         -
>  Network connection between vm://host04#0 and ssl://host02/10.0.0.237:61616 shut
> down due to a remote error: java.io.IOException: Unknown data type: 49
> 2009-04-06 15:48:29,853 [NetworkBridge  ] INFO  DemandForwardingBridge         -
>  host04 bridge to host02 stopped
> 2009-04-06 15:48:35,073 [erService[host04]] INFO  DiscoveryNetworkConnector      -
>  Establishing network connection from vm://host04 to ssl://host02:61616
> 2009-04-06 15:48:35,109 [ker=vm://host04#8] INFO  DemandForwardingBridge         -
>  Network connection between vm://host04#8 and ssl://host02/10.0.0.237:61616(host02
> ) has been established.
> This is really hard to reproduce for some reason. But the consequence will affect temporary
queue:
> consumer of temporary queue on broker2
> producer of temporary queue on broker4
> due to this error, producer side will get 
> javax.jms.InvalidDestinationException: Cannot publish to a deleted Destination: temp-queue://queuename
> I checked to make sure all client and brokers are using trunk 761597 revision. I am not
sure what cause this "Unknown data type" error.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message