JMS Foreign destination issue
jing...@oracle.com
com.ibm.ws.exception.RuntimeWarning: javax.resource.NotSupportedException: CWSIV0754E: The destination CCQueue on bus CCServiceBus is foreign to the bus to which the message-driven bean is connected.
We followed the steps which are there in http://www.redbooks.ibm.com/redpapers/pdfs/redp4330.pdf (Chapter 15.5) and created Two buses and ME and destinations ect.,. The configuration of queue (Active specification) points to forien destionation websphere start up time getting this error.
The full error stack trace
[1/21/09 15:11:43:011 MST] 0000002c ActivationSpe E J2CA0155W: The lookup of the Authentication Alias MD_ASAuthAlias, assigned to the ActivationSpec jms/MessageDispatcher by application Ebilling#ejb-events-1.0-SNAPSHOT.jar#MessageDispatcher has failed.
[1/21/09 15:11:43:361 MST] 0000002c ActivationSpe W J2CA0149W: The contents of the Authentication Alias assigned to the ActivationSpec edx.queue.outbound used by MDB Ebilling#ejb-events-1.0-SNAPSHOT.jar#MessageDispatcher are not valid. The username and/or the Password were either null or blank. The AuthenticationAlias was: MD_ASAuthAlias, its UserName was: null, and its Password was: null
[1/21/09 15:11:44:125 MST] 0000002c ActivationSpe E J2CA0138E: The MessageEndpoint activation failed for ActivationSpec com.ibm.ws.sib.api.jmsra.impl.JmsJcaActivationSpecImpl and MDB Application Ebilling#ejb-events-1.0-SNAPSHOT.jar#MessageDispatcher, due to the following exception: javax.resource.NotSupportedException: CWSIV0754E: The destination CCQueue on bus CCServiceBus is foreign to the bus to which the message-driven bean is connected.
at com.ibm.ws.sib.ra.inbound.impl.SibRaStaticDestinationEndpointActivation.validateDestination(SibRaStaticDestinationEndpointActivation.java:430)
at com.ibm.ws.sib.ra.inbound.impl.SibRaStaticDestinationEndpointActivation.validateDestination(SibRaStaticDestinationEndpointActivation.java:471)
at com.ibm.ws.sib.ra.inbound.impl.SibRaStaticDestinationEndpointActivation.getRequiredMessagingEngines(SibRaStaticDestinationEndpointActivation.java:557)
at com.ibm.ws.sib.ra.inbound.impl.SibRaStaticDestinationEndpointActivation.isListenerRequired(SibRaStaticDestinationEndpointActivation.java:335)
at com.ibm.ws.sib.ra.inbound.impl.SibRaStaticDestinationEndpointActivation.(SibRaStaticDestinationEndpointActivation.java:222)
at com.ibm.ws.sib.ra.inbound.impl.SibRaResourceAdapterImpl.endpointActivation(SibRaResourceAdapterImpl.java:321)
at com.ibm.ejs.j2c.ActivationSpecWrapperImpl.activateEndpoint(ActivationSpecWrapperImpl.java:247)
at com.ibm.ejs.j2c.RAWrapperImpl.activateEndpoint(RAWrapperImpl.java:795)
at com.ibm.ejs.j2c.RALifeCycleManagerImpl.activateEndpoint(RALifeCycleManagerImpl.java:1480)
at com.ibm.ejs.container.MessageEndpointFactoryImpl.activateEndpoint(MessageEndpointFactoryImpl.java:257)
at com.ibm.ws.runtime.component.EJBContainerImpl.install(EJBContainerImpl.java:2955)
at com.ibm.ws.runtime.component.EJBContainerImpl.start(EJBContainerImpl.java:3634)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1295)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1129)
at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:567)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:814)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:948)
at com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run(ApplicationMgrImpl.java:2114)
at com.ibm.wsspi.runtime.component.WsComponentImpl$_AsynchInitializer.run(WsComponentImpl.java:340)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1498)
LEMI...@uk.ibm.com
Messages can only be sent to foreign destinations - or alias destinations which point to a foreign bus - they do not support the ability to receive messages. You should configure your activation specification to consume from a local queue or connect to the bus which contains the queue pointed to by the foreign queue.
Regards, Matt.
jing...@oracle.com
We are trying to send messages to foreign destination queue. Same active specification works fine if point to local queue.
We are migrating from Weblogic to Websphere. In weblogic we are consuming the messages from foreign queue using T3// protocol. Same thing we tried to consume from foreign destination we got this error and we read one article it says "application cannot consume messages from a destination in a foreign bus."
My work is to send the messages from Bus1 to foreign destination queue in Bus2 or consume messages from Bus1 in Bus2.
Please guide us how to achieve this issue.
Thank you,
Jing
error message consuming from foreign destination
_____________________________________________________________________________________
[1/20/09 12:36:43:486 MST] 00000059 SystemErr R javax.jms.InvalidDestinationException: CWSIA0086E: Failed to create a MessageConsumer for queue://eBillingQueue?busName=eBillingServiceBus
[1/20/09 12:36:43:490 MST] 00000059 SystemErr R at com.ibm.ws.sib.api.jms.impl.JmsMsgConsumerImpl.createCoreConsumer(JmsMsgConsumerImpl.java:1079)
[1/20/09 12:36:43:491 MST] 00000059 SystemErr R at com.ibm.ws.sib.api.jms.impl.JmsMsgConsumerImpl. (JmsMsgConsumerImpl.java:415)
[1/20/09 12:36:43:491 MST] 00000059 SystemErr R at com.ibm.ws.sib.api.jms.impl.JmsQueueReceiverImpl. (JmsQueueReceiverImpl.java:74)
[1/20/09 12:36:43:492 MST] 00000059 SystemErr R at com.ibm.ws.sib.api.jms.impl.JmsQueueSessionImpl.instantiateConsumer(JmsQueueSessionImpl.java:327)
[1/20/09 12:36:43:492 MST] 00000059 SystemErr R at com.ibm.ws.sib.api.jms.impl.JmsSessionImpl.createConsumer(JmsSessionImpl.java:1238)
[1/20/09 12:36:43:493 MST] 00000059 SystemErr R at com.ibm.ws.sib.api.jms.impl.JmsSessionImpl.createConsumer(JmsSessionImpl.java:1166)
[1/20/09 12:36:43:493 MST] 00000059 SystemErr R at com.ibm.ws.sib.api.jms.impl.JmsQueueSessionImpl.createReceiver(JmsQueueSessionImpl.java:192)
[1/20/09 12:36:43:493 MST] 00000059 SystemErr R at com.edocs.common.reporting.tasks.batchscheduler.BatchReportSchedulerTask.executeInternal(BatchReportSchedulerTask.java:100)
[1/20/09 12:36:43:494 MST] 00000059 SystemErr R at com.edocs.common.reporting.tasks.batchscheduler.BatchReportSchedulerTask.doProcessTask(BatchReportSchedulerTask.java:238)
[1/20/09 12:36:43:494 MST] 00000059 SystemErr R at com.edocs.pwc.tasks.CommonTask.processTask(CommonTask.java:166)
[1/20/09 12:36:43:494 MST] 00000059 SystemErr R at com.edocs.pwc.tasks.EJSRemoteStatefulBatchReportSchedulerTask_8ed80c92.processTask(Unknown Source)
[1/20/09 12:36:43:495 MST] 00000059 SystemErr R at com.edocs.pwc.tasks._EJSRemoteStatefulBatchReportSchedulerTask_8ed80c92_Tie.processTask(_EJSRemoteStatefulBatchReportSchedulerTask_8ed80c92_Tie.java:246)
[1/20/09 12:36:43:495 MST] 00000059 SystemErr R at com.edocs.pwc.tasks._EJSRemoteStatefulBatchReportSchedulerTask_8ed80c92_Tie._invoke(_EJSRemoteStatefulBatchReportSchedulerTask_8ed80c92_Tie.java:94)
[1/20/09 12:36:43:501 MST] 00000059 SystemErr R at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:613)
[1/20/09 12:36:43:501 MST] 00000059 SystemErr R at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:466)
[1/20/09 12:36:43:502 MST] 00000059 SystemErr R at com.ibm.rmi.iiop.ORB.process(ORB.java:503)
[1/20/09 12:36:43:502 MST] 00000059 SystemErr R at com.ibm.CORBA.iiop.ORB.process(ORB.java:1552)
[1/20/09 12:36:43:503 MST] 00000059 SystemErr R at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2673)
[1/20/09 12:36:43:503 MST] 00000059 SystemErr R at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2551)
[1/20/09 12:36:43:503 MST] 00000059 SystemErr R at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:62)
[1/20/09 12:36:43:504 MST] 00000059 SystemErr R at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:95)
[1/20/09 12:36:43:504 MST] 00000059 SystemErr R at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1498)
[1/20/09 12:36:43:504 MST] 00000059 SystemErr R Caused by: com.ibm.ws.sib.processor.exceptions.SIMPNotPossibleInCurrentConfigurationException: CWSIK0015E: The destination eBillingQueue was not found on messaging engine CC_node.server1-CCServiceBus.
at com.ibm.ws.sib.processor.impl.DestinationManager.checkDestinationHandlerExists(DestinationManager.java:3743)
at com.ibm.ws.sib.processor.impl.DestinationManager.getDestination(DestinationManager.java:956)
at com.ibm.ws.sib.processor.impl.DestinationManager.getDestination(DestinationManager.java:931)
at com.ibm.ws.sib.processor.impl.ConnectionImpl.internalCreateConsumerSession(ConnectionImpl.java:1302)
at com.ibm.ws.sib.processor.impl.ConnectionImpl.createConsumerSession(ConnectionImpl.java:4905)
at com.ibm.ws.sib.api.jms.impl.JmsMsgConsumerImpl.createCoreConsumer(JmsMsgConsumerImpl.java:1030)
at com.ibm.ws.sib.api.jms.impl.JmsMsgConsumerImpl. (JmsMsgConsumerImpl.java:415)
at com.ibm.ws.sib.api.jms.impl.JmsQueueReceiverImpl.(JmsQueueReceiverImpl.java:74)
at com.ibm.ws.sib.api.jms.impl.JmsQueueSessionImpl.instantiateConsumer(JmsQueueSessionImpl.java:327)
at com.ibm.ws.sib.api.jms.impl.JmsSessionImpl.createConsumer(JmsSessionImpl.java:1238)
at com.ibm.ws.sib.api.jms.impl.JmsSessionImpl.createConsumer(JmsSessionImpl.java:1166)
at com.ibm.ws.sib.api.jms.impl.JmsQueueSessionImpl.createReceiver(JmsQueueSessionImpl.java:192)
at com.edocs.common.reporting.tasks.batchscheduler.BatchReportSchedulerTask.executeInternal(BatchReportSchedulerTask.java:100)
at com.edocs.common.reporting.tasks.batchscheduler.BatchReportSchedulerTask.doProcessTask(BatchReportSchedulerTask.java:238)
at com.edocs.pwc.tasks.CommonTask.processTask(CommonTask.java:166)
at com.edocs.pwc.tasks.EJSRemoteStatefulBatchReportSchedulerTask_8ed80c92.processTask(Unknown Source)
at com.edocs.pwc.tasks._EJSRemoteStatefulBatchReportSchedulerTask_8ed80c92_Tie.processTask(_EJSRemoteStatefulBatchReportSchedulerTask_8ed80c92_Tie.java:246)
at com.edocs.pwc.tasks._EJSRemoteStatefulBatchReportSchedulerTask_8ed80c92_Tie._invoke(_EJSRemoteStatefulBatchReportSchedulerTask_8ed80c92_Tie.java:94)
at com.ibm.CORBA.iiop.ServerDelegate.dispatchInvokeHandler(ServerDelegate.java:613)
at com.ibm.CORBA.iiop.ServerDelegate.dispatch(ServerDelegate.java:466)
at com.ibm.rmi.iiop.ORB.process(ORB.java:503)
at com.ibm.CORBA.iiop.ORB.process(ORB.java:1552)
at com.ibm.rmi.iiop.Connection.respondTo(Connection.java:2673)
at com.ibm.rmi.iiop.Connection.doWork(Connection.java:2551)
at com.ibm.rmi.iiop.WorkUnitImpl.doWork(WorkUnitImpl.java:62)
at com.ibm.ejs.oa.pool.PooledThread.run(ThreadPool.java:95)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1498)
_____________________________________________________________________________________
LEMI...@uk.ibm.com
I am going to be out of the country for the best part of a month so I won't be able to provide a
large amount of help, but here are some thoughts.
The basic problem is that you are trying to consume messages from a remote bus. This is not supported
by the SIBus runtime hence the messages you are getting. There are a number of possible solutions
open to you.
For activation specifications:
If your buses are both part of the same cell then your activation specification will be able to connect
into either bus without the use of foreign destinations.
If your buses are in separate cells then it may be worth adjusting your configuration so they are not. Alternatively
you can link your cells together using a core group bridge and then your activation spec will be able to connect
directly to the SIBus running in the other cell. Also, there is now an APAR PK77768 which provides the
ability to set a provider endpoint on an activation specification. This is a back-port of WebSphere Application
Server version 7 functionality and can be requested from IBM service - NB this has yet to be listed on IBM's website.
Lastly you could put an application in the remote bus that forwards messages over to the other bus which would get around the problem.
For JMS MessageConsumers:
If you want to consume messages from a destination on a foreign bus using the default messaging provider you should
configure your default messaging provider connection factory so that it points directly to the foreign bus rather
than using a foreign destination on the local bus.
I hope this helps.
Cheers, Matt.