[
https://issues.apache.org/activemq/browse/AMQ-895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39019
]
Alf E. Helseth commented on AMQ-895:
------------------------------------
Thanks Manuel!
I now got rid of the wrapper, the <constructor-arg> stuff worked out just fine!
So to the ClassCastException, it really comes from the ActiveMQ program itself,
the moment I try to send a message into the queue on the JCAPS broker queue
that is defined to be inboundQueueName, and the bridge tries to fetch it into
AMQ.
The other way around messages (sendt to the outboundQueueName on AMQ) are
bridged correctly over to JCAPS.
The consumer/provider programs are using javax.jms.TextMessage as contents.
I have also tried to use the JMXConsole connected to AMQ for sending simple
test messages.
You says that the bridge should automatically convert incoming messages to
native AMQ - seems to me that that's where the error occurs ?
Br
Alf (with steep learning curve regarding ActiveMQ...)
> JMS to JMS Bridge never reconnects under remote broker restarts.
> ----------------------------------------------------------------
>
> Key: AMQ-895
> URL: https://issues.apache.org/activemq/browse/AMQ-895
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 4.0 RC2, 4.0.1
> Reporter: Manuel Teira
> Attachments: test_patch.diff
>
>
> I'm using ActiveMQ (4.0.1) JMS to JMS Bridge functionality to connect to a
> SunMQ JMS Broker (3.6 SP3 (Build 02-A)). I'm using two queues, an input and
> an output one, with the following configuration:
> <jmsBridgeConnectors>
> <jmsQueueConnector outboundQueueConnectionFactory="#REMOTE">
> <outboundQueueBridges>
> <outboundQueueBridge outboundQueueName="SUNRECV"/>
> </outboundQueueBridges>
> <inboundQueueBridges>
> <inboundQueueBridge inboundQueueName="SUNSEND"/>
> </inboundQueueBridges>
> </jmsQueueConnector>
> </jmsBridgeConnectors>
> The system works really well until the SunMQ broker needed to be restarted.
> This is what I found:
> 1.-ActiveMQ is not aware of the remote broker shutdown. I waited for a while,
> but no log on ActiveMQ indicates knowledge about the new situation.
> 2.-When I send a message to the output queue SUNRECV, ActiveMQ complains that
> the producer is closed:
> [ERROR][2006/08/25.09:47:12.039][ActiveMQ Session Task]failed to forward
> message: ActiveMQTextMessage {commandId = 5, responseRequired = false,
> messageId = ID:trabucco-43457-1156491843149-3:4:1:1:1, originalDestination =
> null, originalTransactionId = null, producerId =
> ID:trabucco-43457-1156491843149-3:4:1:1, destination = queue://SUNRECV,
> transactionId = null, expiration = 0, timestamp = 1156492032027, arrival = 0,
> correlationId = null, replyTo = null, persistent = false, type = null,
> priority = 0, groupID = null, groupSequence = 0, targetConsumerId = null,
> compressed = false, userID = null, content = null, marshalledProperties =
> null, dataStructure = null, redeliveryCounter = 0, size = 2, properties =
> null, readOnlyProperties = true, readOnlyBody = true, text = 1}([C4064]:
> Cannot perform operation, producer is closed.)
> After this, it is automatically queueing messages without sending them,
> showing the log:
> [DEBUG][2006/08/25.09:47:42.721][RMI TCP Connection(4)-10.95.89.20]No
> subscriptions registered, will not dispatch message at this time.
> Even if SunMQ is started again, ActiveMQ is not detecting the new situation,
> and continues queueing messages sent to SUNRECV.
> Please, make me know if more information is needed to understand the
> situation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
