Author: kim.nel...@ca.com Message: We have attempted to create the configuration represented in Figure 5 of the document at:
http://publib.boulder.ibm.com/infocenter/wasinfo/fep/index.jsp?topic=/com.ibm.websphere.pmc.nd.multiplatform.doc/concepts/cjn_mdb_endpt_overview.html So, we have one cluster which contains the application server nodes and a second cluster which contains the message engine. The activation spec for each MDB on each application server node contains a target of the message engine on the second cluster. It is clear that our configuration is not complete, since we are published the subscription on one node but never receiving it on the others. I turned on WAS topic tracing and note that the publish entry is as follows: 8/30/10 16:03:57:627 CDT 00000037 JmsTopicPubli > publish(Message) [:] Entry 8/30/10 16:03:57:627 CDT 00000037 JmsTopicPubli 3 [:] message : JMSMessage class: jms_map JMSType: null JMSDeliveryMode: 2 JMSExpiration: 0 JMSPriority: 4 JMSMessageID: null JMSTimestamp: -1 JMSCorrelationID: null JMSDestination: null JMSReplyTo: null JMSRedelivered: false MessageFormat: 1.0 env: 2 Source: 31eaec17-c65896ff-261be8e5-db8c56b Command: flushaztype objecttype: PROVISIONING ROLE aztype: Ownership These nulls don't look very nice and I am hoping that they might yield a clue about what is wrong with our configuration. I would really appreciate some help on this subject. Thanks very much To respond to this post, please click the following link: <http://www.ibm.com/developerworks/forums/thread.jspa?messageID=14526735> ____________________________________ Unsubscribe via the "binocular" icon on the web
