Problem correlating separate JMS MQs

Hi there - I am testing out a 10.1.2 BPEL process that correlates OK between Produce and Consume messages to the same test queue (IBM MQ) via the JMS Adapter.
We're deploying to BPEL 10.1.2 deployed into WebSphere 5.x using MQ 5.3.
This test uses a correlation set based on an Xpath query into a SOAP payload (client requirement is SOAP messages on Qs). Its working for our initial test as above.
As soon as I introduce separate queues for the Produce and Consume messages (i.e produce to one Queue, a background process returns a reply message to a second Queue, which I want to then consume), the process no longer correlates, even though I'm using the same correlation set and I know the correlation data will be in the messages. All we did was change the DestinationName(s) in the JMS PartnerLink WSDL files and redeploy.
Any ideas why this might be happening?
Thanks in advance.
Dennis

Similar Messages

Correlation for JMS Queue

Hi,
I have following scenario :
Queue1
Bpel1 -> Writes Schema A to Queue1
Bpel2 -> Writes Schema B to Queue1
Bpel3 -> Reads from Queue1
I need that Bpel3 should read only Schema A from Queue and not Schema B.
So how will i define the correlation between Bpel1 & Bpel 3.
I tried fetching the processId in Bpel 1 and add it to Invoke property jca.jms.JmsCorrelation_id, but was not able to set the same in Bpel3.
Any help/spec in setting up correlation for JMS Queues is highly apreciated.
Thanks !!

In standard JMS, an application can specify a correlation-id on per message basis using the javax.jms.Message API, and then specify a filter (a "selector") when creating a consumer via the javax.jms.Session API, but, in general, it is usually better to use a separate dedicated queue per business process (simplifies management, simplifies coding, improves perf, etc), or, if that's not an attractive option, to use a single MDB to dispatch messages from the same queue to different business processes. I don't know the specific steps to do the same in BPEL.
You might want to try posting to the BPEL forum at BPEL
Hope this helps,
Tom

Problem with transacted JMS connection factory and transaction timeouts

          We encountered an interesting problem using transacted JMS connection factories.
          An EJB starts a container managed transaction and tries to validate a credit card
          before creating some information to a database for the user, in case of success
          an SMS is sent to the user via the transacted JMS queue. If the credit card authentications
          duration is about the same as the transactions timeout (in this case the default
          30 seconds) sometimes the database inserts is committed but the JMS insert is
          rollbacked. How can this be?
          If the authorization duration is much longer than 30 seconds everything works
          fine (both database and JMS inserts rollbacked), the same is true if a rollback
          is insured by calling EJBContext.setRollbackOnly(). The problem thus occurs only
          if the duration is approximately the same as the transaction timeout, it appears
          that the database insert is not timeouted but the JMS insert is. How can this
          be if they are both participating in the same transaction.
          The JMSConnectionFactory used is a Connection factory with XA-enabled. The result
          is the same also with the default "javax.jms.QueueConnectionFactory" and if we
          configure our own factory with user transactions enabled.
          Any help appreciated!


Tomas Granö wrote:
          > We encountered an interesting problem using transacted JMS connection factories.
          > An EJB starts a container managed transaction and tries to validate a credit card
          > before creating some information to a database for the user, in case of success
          > an SMS is sent to the user via the transacted JMS queue. If the credit card authentications
          > duration is about the same as the transactions timeout (in this case the default
          > 30 seconds) sometimes the database inserts is committed but the JMS insert is
          > rollbacked. How can this be?
          It should not be.
          >
          > If the authorization duration is much longer than 30 seconds everything works
          > fine (both database and JMS inserts rollbacked), the same is true if a rollback
          > is insured by calling EJBContext.setRollbackOnly(). The problem thus occurs only
          > if the duration is approximately the same as the transaction timeout, it appears
          > that the database insert is not timeouted but the JMS insert is. How can this
          > be if they are both participating in the same transaction.
          >
          > The JMSConnectionFactory used is a Connection factory with XA-enabled. The result
          > is the same also with the default "javax.jms.QueueConnectionFactory" and if we
          > configure our own factory with user transactions enabled.
          >
          > Any help appreciated!
          Make sure that your session is not "transacted". In other words,
          the first parameter to createSession() must be false. There is an
          unfortunate name re-use here. If a session is "transacted", it
          maintains an independent "inner transaction" independent of the
          outer transaction. From the above description, it seems unlikely
          that your application has this wrong, as you say that
          "setRollbackOnly" works - but please check anyway.
          Make sure that you are using a true XA capable driver and database
          (XA "emulation" may not suffice)
          Beyond the above, I do not see what can be going wrong. You
          may want to try posting to the transactions and jdbc newsgroups. Note
          that JMS is appears to be exhibiting the correct behavior, but the
          JDBC operation is not. The JDBC operation appears to have
          its timeout independent of the transaction monitor's timeout.
          Tom

When to create a separate JMS Server

Gurus
Please provide/point to guidelines on when to create a separate JMS server within the Weblogic server 11g, the Pros and Cons of doing the same.
From Oracle JMS Guide for Weblogic , the main value add I am able to see is the separate Persistent store and a separate logical container for JMS resources related to my project. These will be important value additions since we will be using a shared environment where artifacts from multiple projects will be deployed.
I researched online , but could not get more inputs. Appreciate any pointers.
regards
Basu

There is a JMS Server and Persistent Store section in the JMS configuration best practices book.
http://docs.oracle.com/cd/E17904_01/web.1111/e13738/best_practice.htm#CACGFHDJ
Hope this is helpful to you.

Help-Problem in calling JMS inside an EJB having transaction attribute Required New

 Hi,
 Version wl 5.1 service pack 8
 OS - unix
 I am using a Container managed bean say Bean1(transaction attribute Required)
 which in one of its method is trying to call another EJB say Bean2 which has the
 transaction attribute set to "RequiredNew".Inside the method in Bean2 i have my
 JMS funtions coded to persist to database.JMS uses Queue connection factory and
 is an non transaction JMS session.The JMS server is running in a separate weblogic
 server and not in the server where EJB is deployed.I use the url of the JMS server
 and get the context of that server and connect my JMS.
 The problem that i am facing is
 I do the transaction in bean1 and the i make the call to bean2 to do the JMS work
 and i can see the JMS doing the insert in the table and everthing works fine.But
 after few seconds i can see the exception/message seen on the console of the weblogic
 server where my JMS server is running as below
 Tue Sep 04 15:57:09 CDT 2001: <TX> Transaction (TxC (30486015, xid = 99963563
 2756_5, timeout = 30, txState = Marked Rollback, root = 829817264280676325S10.51
 .110.237:[7001,7001,7002,7002,7001,-1]/326) rolled back after 30 sec.
 After this happen i dont see any roll back in either bean1 or bean2 or the JMS
 insert is rolled back.
 I don't know why this exception is thrown and no effects on the rollback and it
 works the way i wanted.But the only thing that keeps bothering me is the rollback
 and why does this happen.
 Thanks
 Krish.


The exception your seeing is troubling - if the tran is rolled
 back than whatever work is associated should also roll back. I suggest
 instrumenting your code to see if the tran rolling back is the same tran
 that is being used for the transactional application work that appears to succeed.
 Also, try forcing a rollback, you may see that the EJB work truly rolls back
 while the JMS work does not.
 I'm not really familiar with 5.1, but I know there is a fundamental limitation to one
 phase commits, this means that the JDBC connection pool used by JMS as well
 as that used by the EJB must be one and the same - I'm not exactly sure how
 it works, but I'm pretty sure multiple servers can share the same connection pool.
 This post seems unrelated to clustering, if you need further help, I
 suggest posting in the ejb or transaction newsgroups.
 Krish wrote:
 > Hi,
 >
 > Version wl 5.1 service pack 8
 > OS - unix
 >
 > I am using a Container managed bean say Bean1(transaction attribute Required)
 > which in one of its method is trying to call another EJB say Bean2 which has the
 > transaction attribute set to "RequiredNew".Inside the method in Bean2 i have my
 > JMS funtions coded to persist to database.JMS uses Queue connection factory and
 > is an non transaction JMS session.The JMS server is running in a separate weblogic
 > server and not in the server where EJB is deployed.I use the url of the JMS server
 > and get the context of that server and connect my JMS.
 >
 > The problem that i am facing is
 >
 > I do the transaction in bean1 and the i make the call to bean2 to do the JMS work
 > and i can see the JMS doing the insert in the table and everthing works fine.But
 > after few seconds i can see the exception/message seen on the console of the weblogic
 > server where my JMS server is running as below
 >
 > Tue Sep 04 15:57:09 CDT 2001: <TX> Transaction (TxC (30486015, xid = 99963563
 > 2756_5, timeout = 30, txState = Marked Rollback, root = 829817264280676325S10.51
 > 110.237:[7001,7001,7002,7002,7001,-1]/326) rolled back after 30 sec.
 >
 >
 > After this happen i dont see any roll back in either bean1 or bean2 or the JMS
 > insert is rolled back.
 >
 > I don't know why this exception is thrown and no effects on the rollback and it
 > works the way i wanted.But the only thing that keeps bothering me is the rollback
 > and why does this happen.
 >
 > Thanks
 >
 > Krish.

Acrobat 9 Pro - Serial Number Problem - 3 Separate Licenses

I own 3 separate licenses of Acrobat 9 Pro and have owned several licenses going clear back to Acrobat 6. We have used them on the office computers and home or laptop just as the license authorizes.
Recently we had a problem of employees getting confused as to which license or Serial Number of 9 Pro was installed on which machine and apparently the number of authorized installs was exceeded.   The solution to that was to go around and try to determine which SN was installed on which computer.
With all prior versions, this was an easy task. You simply clicked on the Help tab and selected the About option and it gave you a screen that showed the SN of the license installed on that computer.   That way you could keep straight which was installed on which, and you could that way monitor employees so that the authorized number of installs were not exceeded and that deactivation had been done properly. We had a new computer we needed to install 9 Pro on but we needed to know the SN on the old machine in order to make sure we had the deactivation done properly.
I was taken by surprise to discover that this method of determining the installed SN would not work on 9 Pro. The "About" screen showed no SN. It showed patent information and credits, but no SN. I checked this on all three licenses and it was the same on each one.
I called Tech Support and got into the support problem from Hell over what should be a simple issue. I went through 4 separate techies and 5 different calls. After spending most of the day dealing with this issue, and a substantial loss of revenue. I was given completely wrong information by 3 of the techies (called lies in my culture) and the 4th one claimed there was no possible way to determine the SN of the license running on any individual computer under 9 Pro.
I then called the sales department for volume licensing and was told that if I bought 3 licenses under the volume license program, I could have one serial number and get rid of the 3 SN problem. I was told that I could get a refund on my 3 separate licenses and this would fix my problem. I stated 3 times that I would buy the volume licenses only if I was guaranteed a refund for the 3 separate licenses. Each time I was assured that would occur. After the new sale for the volume licenses was completed, I was transferred to another department for the refunds and the refund request was refused!!!!   It took the rest of that day and part of the next to get a response back from the sales person that sold me the volume licenses and get that transaction cancelled. They still charged my credit card and then it took several more days to get that reversed. On top of all of that, Adobe keeps attempting to close my support incident claiming it is resolved when it most certainly is not.
I have been computing for over 20 years and I would have to say this was the worst tech support treatment I have ever experienced. I am simply amazed and disgusted. As a user of Acrobat over many years, I am so mad that if 10 users wanted to file a class action suit against Adobe, I might do it for nothing.
Can anyone tell me if there is any way to determine the SN of the license of 9 Pro that is running on a computer? If not, how else can you keep straight which install is on which computer and which needs to be deactivated when you replace the computer or try to move it to another?
This would seem to me to be a huge problem and I am extremely surprised that Adobe seems to simply be ignoring it and that the tech support people are telling fibs.
Any information would be most appreciated.

Sorry that you got such a hassle. Try this. I don't have Acrobat 9 per se, but I have the TCS2 and found the following.
Run Regedit (all the serious warning apply here. Look but don't touch).
Under HKEY_LOCAL_MACHNINE->SOFTWARE->Adobe->Repair->Adobe Acrobat->9.0->IOD Look under the entry under SERIAL.
Maybe it works maybe it doesn't. But it might help.
Message was edited by: MichaelKazlow

Problem in creating JMS business service in OSB

Hi all
I am creating a JMS business service in osb:request /response is TEXT
It write to "*QueueSend*"-which is my URI endpoint
I have a MDB which read from "*QueueSend*" and write to "*QueueReceive*"
i have given the *"Response Endpoint*" in jms business service to point to "*QueueReceive*"
When i send the msg, it write to QueueSend and mdb writes it to QueueReceive but JMS business service doesn't read from QueueReceive,it just wait a long .......
What is the problem??
Thanks
Rohan

Hi Rohan,
Are you able to see consumers on "QueueReceive"?
If no, then your BS is not listening on this queue. Check the end-point again. Check server logs to know if any error occured while BS tried to connect with Queue. Restart your server which has this queue and then the OSB, and try again.
Regards,
Anuj

Problem in configuring JMS adapter

Hello,
My purpose is to send xml data from MQSeries to BW using XI. MQSereies is installed in XI server. For thah I am trying to configure JMS adpter for MQSeries in XI. I have successfully deployed the necessary external drivers using SDM. I have configured the sender channel with the following parameters.
Adapter type: JMS
Transport Protocol :WEBsphereMQ(non-JMS)
Message protocol :JMS1.x
Queue connection factory java class:com.ibm.mq.jms.MQQueueConnectionFactory
Queue Java Class: com.ibm.mq.jms.MQQueue
IP address: IP address of XI system.
Port: 1414
Queue manager name : MQ-manager-name_XI-system-name
Channel Name : reciever-channel-name_XI-system-name
JMS queue: postcard
Charecter set ID:
Transport/networkprotocol: TCP/IP
JMS-Compliant : WebsphereMQ(non-JMS)
But when I check it in adapter monitor JMS is shown as red.
When I go to Visual Administrator
"cluster->server->services->monitoring->runtime->monitor tree->services->Connector Service" is white instead of green.
Can any one tell what could be the problem.
Regards,
Amith

Hi Vijaya,
In VA there is only option to stop or start JMS XI adapter.
I dont know where to activate JMS adapter in VA. It is already started in VA.
Regards,
Amith

Problem with Sender JMS J2EE adapter...

I have configured the sender JMS J2EE adpater. I am getting this error at Adapter monitoring:
Sender channel. Details: Last Exception during send at Fri May 25 09:44:18 CEST 2007: Error converting Message: 'java.lang.Exception: ERROR consistency check in recordset structure validation (line no. 1: missing structure(s) in last recordset'.
I am using recordset structure as Header,1,Item,99999. and also i am ignoring the recordsetName...i tried confiuring the File adapter using same parameters as in JMS adapter it is not giving any error at Adapter Monitoring.
Also i configured File adapter by putting in their the parameters of J2EE JMS adapter in Module tab, it too worked...
so What is exactly this error, if anyone can please tell me...

Hi,
Check some links for FCC
Introduction to simple(File-XI-File)scenario and complete walk through for starters(Part1)
Introduction to simple (File-XI-File)scenario and complete walk through for starters(Part2)
File Receiver with Content Conversion
Content Conversion (Pattern/Random content in input file)
NAB the TAB (File Adapter)
Introduction to simple(File-XI-File)scenario and complete walk through for starters(Part1)
Introduction to simple (File-XI-File)scenario and complete walk through for starters(Part2)
How to send a flat file with various field lengths and variable substructures to XI 3.0
Content Conversion (Pattern/Random content in input file)
NAB the TAB (File Adapter)
File Content Conversion for Unequal Number of Columns
Content Conversion ( The Key Field Problem )
The specified item was not found.
File Receiver with Content Conversion
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/content.htm
Regards,
Phani

Problem in Sender JMS J2EE adapter....

Hello All.
I have configured the sender JMS J2EE adpater. I am getting this error at Adapter monitoring:
Sender channel. Details: Last Exception during send at Fri May 25 09:44:18 CEST 2007: Error converting Message: 'java.lang.Exception: ERROR consistency check in recordset structure validation (line no. 1: missing structure(s) in last recordset'.
I am using recordset structure as Header,1,Item,99999. and also i am ignoring the recordsetName...i tried confiuring the File adapter using same parameters as in JMS adapter it is not giving any error at Adapter Monitoring.
Also i configured File adapter by putting in their the parameters of J2EE JMS adapter in Module tab, it too worked...
so What is exactly this error, if anyone can please tell me...
Thnsk in Advace

> I think you have to figure out first, which codepage you really have, not just try. Maybe you ask someone or you check with a hex editor.
Hi Stefan,
Finally we solved the problem.
As you said above to figure the the codepage, we asked to our MQ team for the same and found that they are using ISO-8859-1. In XI we were also trying with multiple conbinations (ISO-8859-1, UTF-8 and many more), but didn't get any success.
Finally MQ team changed their encoding to UTF-8 and in XI we used ISO-8859-1 and we get the success in picking the data with spl char. Even though in XI the spl char comes in destorted order but at the receiver end they are in proper shape.
Thanks a lot for your help.
Regards,
Sarvesh

Problem with Starting JMS e JAXR

When I execute J2ee -verbose
Starting JMS via Resource Adapter
Deploying jmsra.rar in D:\j2sdkee1.4\lib\system_apps\jmsra.rar
org.w3c.dom.DOMException: DOM003 Namespace error
JAXR:Installing JAXR RA
Deploying jaxr-ra.rar in D:\j2sdkee1.4\lib\system_apps\jaxr-ra.rar
org.w3c.dom.DOMException: DOM003 Namespace error

Well, same occurrence of described problem and no solution-
thx

Correlation for JMS Messages possible? JMSCorrID in JMSHeader not accepted

Is Correlation for communication over JMS messages possible?
If I define the JMSHeader field "JMSCorrelationID" in a correlation set ("as usual") then I get
compiler errors:
Error ORABPEL-10036: invalid correlation set
BPEL seems not to accept JMSHeader fields for correlation but only fields from the actual payload msg.
Is this true?
Is there soemwhere a guide on how to correlate JMS messages?
Thank you
Michael

you can use the "Message Selector" on the JMS adapter to filter to achieve that;
here is extract from oracle help document
Message Selector
Specify filtering logic that enables you to receive messages that match a certain criteria. Enter an expression between 1 and 255 characters in length. Use SQL92 syntax in this field. The JMS server uses this criteria to filter messages received by this consumer. The message selector works with variables defined in standard JMS headers and user-defined properties. You cannot use variables or elements that are in the payload of the message.
For example, you can enter logic such as: JMSPriority > 3. Based on this, messages with a priority greater than 3 are consumed; all other messages are rejected. JMSType = 'car' AND color = 'blue' AND weight > 2500 Country in ('UK', 'US', 'France')
it's got some limitations but works fine for our requirements so far...

OWB 11.2.0.1 SAP LOCATION: Problem with separate FTP Server connection

Hello,
hope somebody can help me. We are working on a BI Project by our Customer with a Exadata Machine.
The Goal of this project is to have the DWH on the Oracle Exadata machine.
At the Moment we have the Development System on a separate Server with OWB 11.1. and are to get stuck because we can't work with OWB 11.2 with the problem we have.
Separate for the coming Migration we set up for testing a machine with OWB 11.2.0.1 (Exadata is productiv system, so not available for testing)
The SAP System of the customer is on a separate physical Machine as the FTP Server.
The new possibility from the OWB 11.2 SAP Location allowed choose between different transport type, also for a separate FTP Server.
We took FTP as Transport Type and we input the FTP IP Adress, User etc.
The Inputs are all correct, we have also check if its possible to connect the FTP server via fillezilla, via cmd -- all works fine
But OWB 11.2 show us by test the connection this Error:
ENV0032: Location SAP_TEST is invalid. Check that you provided the PASSWORD or+
valid values for at least one of the set of mandatory parameters+
HOST_LOGIN_HOST+
I know that seems as if some is not ok with the password or the other parameters.
But all inputs are correct and the password doesn't contains any special character.
Also the connection to the SAP system works fine with OWB 11.2 but not with the FTP System.
Have somebody experience with this error or on a project by customer with separate SAP and FTP System?
Thanking you in anticipation

Hello,
hope somebody can help me. We are working on a BI Project by our Customer with a Exadata Machine.
The Goal of this project is to have the DWH on the Oracle Exadata machine.
At the Moment we have the Development System on a separate Server with OWB 11.1. and are to get stuck because we can't work with OWB 11.2 with the problem we have.
Separate for the coming Migration we set up for testing a machine with OWB 11.2.0.1 (Exadata is productiv system, so not available for testing)
The SAP System of the customer is on a separate physical Machine as the FTP Server.
The new possibility from the OWB 11.2 SAP Location allowed choose between different transport type, also for a separate FTP Server.
We took FTP as Transport Type and we input the FTP IP Adress, User etc.
The Inputs are all correct, we have also check if its possible to connect the FTP server via fillezilla, via cmd -- all works fine
But OWB 11.2 show us by test the connection this Error:
ENV0032: Location SAP_TEST is invalid. Check that you provided the PASSWORD or+
valid values for at least one of the set of mandatory parameters+
HOST_LOGIN_HOST+
I know that seems as if some is not ok with the password or the other parameters.
But all inputs are correct and the password doesn't contains any special character.
Also the connection to the SAP system works fine with OWB 11.2 but not with the FTP System.
Have somebody experience with this error or on a project by customer with separate SAP and FTP System?
Thanking you in anticipation

Problem Connecting to JMS queue with C sharp client

Hi there,
I am trying to connect to a JMS queue using a C# client but i have a problem trying to connect. The problem comes in when i run the C# script a dialog box appears requesting a T3TransportFactory.cs which i do not have on the client. and when i close it i get an exception on
IContext context = ContextFactory.CreateContext(paramMap);
Exception - Failed to connect using URL <t3://10.103.130.18:7001>
StackTrace - at WebLogic.Messaging.Physical.T3TransportFactory.CreateT3Transport(IDictionary`2 paramMap) in c:\weblogic\dev\src1032\modules\weblogic-jms-dotnetclient\jmsimpl\src\WebLogic\Messaging\Physical\T3TransportFactory.cs:line 226
at WebLogic.Messaging.Physical.ContextPhysical.CreateContext(IDictionary`2 paramMap) in c:\weblogic\dev\src1032\modules\weblogic-jms-dotnetclient\jmsimpl\src\WebLogic\Messaging\Physical\ContextPhysical.cs:line 83
at WebLogic.Messaging.Context.CreateContext(IDictionary`2 paramMap) in c:\weblogic\dev\src1032\modules\weblogic-jms-dotnetclient\jmsimpl\src\WebLogic\Messaging\Context.cs:line 56
The stacktrace indicates that it is looking for a T3TransportFactory.cs file in that particular path on the client (This is my speculation) but this directory path does not exist on the client machine with the c# code.
I got a WebLogic.Messaging.dll referenced in my c# project and the ip/port numbers are correct (we know this cause we tried a java client that connected successfully)
Can anyone assist me on this issue?

The issue might be the dll file you are referring to. Did you use the dll from the weblogic installation folder (BEA_HOME/modules/com.bea.weblogic.jms.dotnetclient_1.X.X.X).
Refer - http://docs.oracle.com/cd/E15051_01/wls/docs103/jms_dotnet/install.html#wp1075258
Hope this helps.
Thanks,
Patrick

Problems using distributed JMS topic

          I'm having problems using a distributed topic. I'm running WebLogic 8.1 (SP1)
          with two managed servers in a cluster. I created a new distributed topic using
          the console, and used auto deploy to target the distributed topic to the cluster
          and create members on both servers. I deployed three message-driven EJBs (listening
          on the distributed topic) to both servers.
          After initial deployment, the topic works as expected - I post a message to the
          distributed topic, and it is received by all six EJBs. When I re-start the system
          (both managed servers and the admin server), however, the results are different.
          When I post a message to the distributed topic, it is only received by the three
          EJBs on the first server (the log shows that all EJBs have deployed successfully).
          Under Deployments/EJB Modules/Monitoring, the EJBs on the second server show "JMSConnection
          Alive" as false, while the others are true.
          Under Monitoring/"Monitor all Active JMS Destinations..." for the member topics,
          there are three consumers listed when there should be six.
          If remove and re-create the member topics, or the distributed topic, exceptions
          appear in the log saying that one or both of the member topics are "suspended".
          Is there additional configuration that needs to be done for this scenario? Are
          there any known problems related to distributed topics?
          Thanks,
          Richard


Hi Richard,
          There are no 8.1SP1 problems that I know of.
          Check your logs for Warnings and Errors - distributed topics
          members often log an explanatory message
          when they fail to contact their fellow members.
          Also make sure that you have configured so that
          the following are true:
          All WL servers are named differently.
          All JMS servers are named differently.
          All JMS stores are named differently.
          All distributed topic members within a distributed topic are named
          differently.
          Also make sure that your cluster is coming up
          properly in the first place. If you have
          trouble doing so, you can post
          to the clustering newsgroups for info.
          Tom
          Richard Killen wrote:
          > I'm having problems using a distributed topic. I'm running WebLogic 8.1 (SP1)
          > with two managed servers in a cluster. I created a new distributed topic using
          > the console, and used auto deploy to target the distributed topic to the cluster
          > and create members on both servers. I deployed three message-driven EJBs (listening
          > on the distributed topic) to both servers.
          >
          > After initial deployment, the topic works as expected - I post a message to the
          > distributed topic, and it is received by all six EJBs. When I re-start the system
          > (both managed servers and the admin server), however, the results are different.
          > When I post a message to the distributed topic, it is only received by the three
          > EJBs on the first server (the log shows that all EJBs have deployed successfully).
          >
          > Under Deployments/EJB Modules/Monitoring, the EJBs on the second server show "JMSConnection
          > Alive" as false, while the others are true.
          >
          > Under Monitoring/"Monitor all Active JMS Destinations..." for the member topics,
          > there are three consumers listed when there should be six.
          >
          > If remove and re-create the member topics, or the distributed topic, exceptions
          > appear in the log saying that one or both of the member topics are "suspended".
          >
          > Is there additional configuration that needs to be done for this scenario? Are
          > there any known problems related to distributed topics?
          >
          > Thanks,
          > Richard
          >

Problem correlating separate JMS MQs

Similar Messages

Maybe you are looking for