Clustered JMS Sender channel only connecting to one server

[former_member247401]

Hi experts,

We are using WebMethods as a JMS Broker and are connecting SAP PO 7.4 SP11 to it to retrieve messges.

As there are multiple users of the message, we are using a Topic with a specific Subscriber so that the messages stay there until everyone has picked them up.

All of the above is working fine.

However on the JMS Broker (WebMethods) the messages are separated to two servers. It's a clustered setup and round robin is used to split the messages evenly between the server.

We noticed PO is only connected to one of the two servers!

I've looked on SAP Help, and at the documentation of the JARs we use to connect but nothing is working. When we write the same code in Java applications using the same drivers they are easily connecting to both servers where the topic runs, but not PO ...

We are connecting via "Access JMS Provider via JNDI"

With JNDI Initial Context Factory: com.webmethods.jms.naming.WmJmsNamingCtxFactory

JNDI Server address: wmjmsnaming://host1@host2:port

Selecting is done via the JMS Message Selector based on properties (this is working fine)

Durable subscribtion is assured by setting the parameter: JMS.Remove.SubscriptionID = false

Any idea how we can force PO to connect to both servers?

Kr,

Frederik-Jan.

[Former Member]

hey,

We are facing the same problem,

In our case we have JMS sender that connect to 3 clusterd oracle weblogic JMS servers,

however we are successfuly connecting to 2 out of those 3 (every time it connects to different ones).

There is a direct coorelation between the number of the total java nodes in the PI application (We have 2 servers with 1 java instance on each) and the number of connections(consumers) in the weblogic server, when wev'e increased the number to total of 3, the channel was connected to all of the JMS servers.

The problem is that we cannot stay with 3 nodes due to memory usage on server...

We tried to find to increase the number of JMS max threads and some other params in the JAVA system properties but with no luck.

Did you (or anyone who comes accros this thred) ever find a solution or a workaround to that issue?

thank you,

Jonathan Bendayan