JMS connecting to remote Queue

Hi
I would like to know how to configure WLS to connect to remote JMS queue to retrieve messages.
Thanks.

Hi
Thanks for the reply.
I have checked the JNDI tree and i see the local JNDI (Local Queue, Local Conneciton Factory) with no red signs.
In additional i am checking with Jdeveloper if i can browse the Queue, but i don't see the remote queue.
So maybe i am missing something in the configuration.
My configurations are:
1.
JMS Module:
Foreign server (Initial Context Factory, JNDI connection Url, credentials, confirm credentials, JNDI properties (java.naming.security.principal=username))
Destinations: (Local JNDI queue name, Remote JNDI queue name)
Connection Factories: (Local JNDI factory name, Remote JNDI factory name, user, password, confirm password).
2.
Then restarted the JMS Module.
3.
Then connecting with Jdeveloper to the host of the managed server and browsing all available JMS destionations.
I see the folder of the JMS module, but under it there is no Queue.
So is there anything else that should be configured in order to connect to remote QUEUE.
Thanks

Similar Messages

Can' t consume JMS messages from remote queue

Hello.
We are using Tibco JMS Server as Foreign JMS server from WL server. And WebLoigic (8.1 SP 3) MDBs are receivers. Everything works fine until there is a restart of the Tibco server. Once the queues become unavailabe, we see in the WL log that the destination is unreachable. And also once the Tibco server comes back up, WL log says that the Foreign queues have been re-connected. But still, we don't see any messages being received by the MDB. The MDBs are configured to poll for messages evey 1 second. Still we don't see it happening after the foreign server restart.
But if we re-start the WL server, it begins to work just fine.
Any pointers?
Thanks

I do have the correct IP address of the syslog server set up. I do not want email logs so have not enabled that.
My setup is
remote lan > SA520-remote (192.168.160.1) > [ site to site IPSec VPN over WAN ] > SA520-local (192.168.150.1) > syslog server (192.168.150.25) & local lan
Firewall is set up to allow ANY IN & OUT to local lan on both routers.
I have also set up specific rules for UDP 514 Syslog traffic (no difference, currently disabled)
syslog server has -no- firewall at the moment.
Syslog server is receiving messages from the local router with no issues.
Log Severity is set to Information & Log Facility is set up to send to Syslog.
I have also setup a SNMP trap on the syslog server & pointed the remote router to it in hopes of diagnosing the issue.
Both routers have the latest firmware applied.
Using wireshark on the syslog server I see no traffic on UDP 514 (syslog) or UDP 162 (snmp)
I can use the WUI for the remote & ping the 160.1 with no problem. Both ping & TLS/TCP traffic show up in wireshark on the syslog server when I do so.
It looks to me like there is a problem routing the syslog messages out of the router & then back through the VPN.
Worst case I'll set up another syslog server on an old machine at the remote location & then cron the logs to the central syslog server but it really seems I shouldn't have to.

Cannot bind tibco's jms connection factory to wls jndi

we are using wls 6.1 sp2. I am trying to bind tibco's jms connection factory
and queue from a standalone client to weblogic's jndi tree so that apps on wls
can lookup these object in wls jndi locally. I have included the required classes
in the classpath for both the client and wls. I am able to bind the queue successfully
and am able to use it successfully too, but I am not able to bind the tib's queue
or topic connection factory. I am getting the following errors. I checked and
double checked the classpath and
Start server side stack trace:
java.rmi.UnmarshalException: error unmarshalling arguments; nested exception is:
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
InstantiationExcep
tion
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
InstantiationException
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:94)
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:123)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
; nested exception is:
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
com.tibco.tibjms.n
aming.TibjmsFederatedTopicConnectionFactory; InstantiationException
Start server side stack trace:
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
InstantiationException
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:94)
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:123)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
com.tibco.tibjms.naming.Ti
bjmsFederatedTopicConnectionFactory; InstantiationException
Start server side stack trace:
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
InstantiationException
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:94)
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:123)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
anybody any ideas.
I am also trying to bind the tib's jndi tree in wls jndi tree through a reference
object and am passing a composite name for lookup. I am getting a cannotproceedexception.
I wonder if the weblogic jndi can be federated.
anybody any ideas or pointers
thanks
Devaraju, Sushant

Seems there is a bug in the tibco jms software.
thanks
Devaraju, Sushant
"sushant" <[email protected]> wrote:
>
we are using wls 6.1 sp2. I am trying to bind tibco's jms connection
factory
and queue from a standalone client to weblogic's jndi tree so that apps
on wls
can lookup these object in wls jndi locally. I have included the required
classes
in the classpath for both the client and wls. I am able to bind the queue
successfully
and am able to use it successfully too, but I am not able to bind the
tib's queue
or topic connection factory. I am getting the following errors. I checked
and
double checked the classpath and
Start server side stack trace:
java.rmi.UnmarshalException: error unmarshalling arguments; nested exception
is:
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
InstantiationExcep
tion
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
InstantiationException
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:94)
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:123)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
; nested exception is:
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
com.tibco.tibjms.n
aming.TibjmsFederatedTopicConnectionFactory; InstantiationException
Start server side stack trace:
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
InstantiationException
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:94)
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:123)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
com.tibco.tibjms.naming.Ti
bjmsFederatedTopicConnectionFactory; InstantiationException
Start server side stack trace:
java.io.InvalidClassException: com.tibco.tibjms.naming.TibjmsFederatedTopicConnectionFactory;
InstantiationException
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:94)
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:123)
at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown
Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
End server side stack trace
<<no stack trace available>>
anybody any ideas.
I am also trying to bind the tib's jndi tree in wls jndi tree through
a reference
object and am passing a composite name for lookup. I am getting a cannotproceedexception.
I wonder if the weblogic jndi can be federated.
anybody any ideas or pointers
thanks
Devaraju, Sushant

JMS adapter fails to open IBM WebSphere MQ Manager V6 Remote Queue

Hello,
We are trying to connect to a Remote Queue with the SAP PI 7.0 SP9 JMS adapter to IBM WebSphere MQ V6 on Linux SLES9 x86_64.
We did deployed the JMS-adapter with the V6 native libaries on SAP PI.
In the Communication Channel we use the Adapter Type = JMS, Sender, Transport Protocol = WebSphereMQ(non-JMS).
The MQ Queue Manager is on the same server as SAP PI so we use localhost, Server Port, Queue Manager Name, Channel Name and JMS Queue Name
The <sid>adm user is a member of the mqm group.
When I check the RWB I see this fault message:
Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2008: failed to open MQ Queue at ...
and also
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2045
When we lookup the reason 2045 we get this explaination on MQ:
MQRC_OPTION_NOT_VALID_FOR_TYPE
We also have a type = Receiver Communication Channel on the same MQ Queue Manager that one is working fine.
Please advise!
Best regards,
Mike Laanen

Mike,
check whether the Queues are created and activated if it done. then check whether you have authorization for those queues.
Regards
Sreeram.G.Reddy

MDB connecting to Remote Distributed Queue

Hi,
I am trying to deploy a MDB in weblogic 10.0 and this will listen to a Distributed Queue in another weblogic version10 server.
my MDB code looks like
@MessageDriven(mappedName = "jms/DMSQueue", activationConfig = {
 @ActivationConfigProperty(propertyName = "initial-context-factory ", propertyValue = "weblogic.jndi.WLInitialContextFactory"),
 @ActivationConfigProperty(propertyName = "connectionFactoryJndiName", propertyValue = "jms/cf"),
 @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
 @ActivationConfigProperty(propertyName="destination", propertyValue="jms/DMSQueue"),
 @ActivationConfigProperty(propertyName = "destinationJndiName", propertyValue = "jms/DMSQueue"),
 @ActivationConfigProperty(propertyName = "providerAdapterJNDI", propertyValue = "java:/RemoteJMSProvider"),
 @ActivationConfigProperty(propertyName = "provider-url", propertyValue = "t3://10.54.115.171:80")
public class TestMdb implements MessageListener {
 public void onMessage(Message message) {
 System.out.println("Received Message: " + message);
if the I configure the bean for a local Queue it works properly.
But if I provide the url of the remote Queue, it does not get connected.
my ejb-jar.xml
contains only
<enterprise-beans>
<message-driven>
<ejb-name>ejbsms</ejb-name>
<ejb-class>hmil.TestMdb</ejb-class>
</message-driven>
</enterprise-beans>
I guess we need to provide the security credentials of the remote server and may be missing some thing else.
Please guide me on what changes required in annotations to get it working
I prefer to use container independent propertyName
Edited by: user13583038 on Jan 3, 2011 4:08 AM

You can try posting JMS related questions to the JMS newsgroup.

WLS 7.0.4 - JMS connection Factory for RMI queues - server affinity issues help pls

We are using WLS 7.0.4 - One of JMS connection factory setting in admin
console we selected "Server Affinity" options.
We see this messages appear in Weblogic log file,
####<Apr 24, 2006 1:56:53 AM EDT> <Error> <Cluster>
<liberatenode4.dc2.adelphia.com> <node4_svr> <ExecuteThrea
d: '4' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <>
<000123> <Conflict start: You tried to bi
nd an object under the name sbetrmi2 in the JNDI tree. The object you have
bound from liberatenode2.dc2.adelp
hia.com is non clusterable and you have tried to bind more than once from
two or more servers. Such objects ca
n only deployed from one server.>
and then,
####<Apr 24, 2006 1:58:12 AM EDT> <Error> <Cluster>
<liberatenode5.dc2.adelphia.com> <node5_svr> <ExecuteThrea
d: '7' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <>
<000125> <Conflict Resolved: sbetrmi2 for
the object from liberatenode5.dc2.adelphia.com under the bind name sbetrmi2
in the JNDI tree.>
Should we use 'load balancing option' instead of 'server affinity' ?
Any thuoghts?
Thanks in adv.
Vijay

Test Reply
 <Vijay Kumar> wrote in message news:[email protected]..
 > WLS 7.0.4 - JMS Connection Factory - Server Affinity - issues in log
 > file
 >
 > We are using WLS 7.0.4 - One of JMS connection factory setting in admin
 > console we selected "Server Affinity" options.
 >
 > We see this messages appear in Weblogic log file,
 > ####<Apr 24, 2006 1:56:53 AM EDT> <Error> <Cluster>
 > <liberatenode4.dc2.adelphia.com> <node4_svr> <ExecuteThrea
 > d: '4' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <>
 > <000123> <Conflict start: You tried to bi
 > nd an object under the name sbetrmi2 in the JNDI tree. The object you have
 > bound from liberatenode2.dc2.adelp
 > hia.com is non clusterable and you have tried to bind more than once from
 > two or more servers. Such objects ca
 > n only deployed from one server.>
 >
 > and then,
 > ####<Apr 24, 2006 1:58:12 AM EDT> <Error> <Cluster>
 > <liberatenode5.dc2.adelphia.com> <node5_svr> <ExecuteThrea
 > d: '7' for queue: '__weblogic_admin_rmi_queue'> <kernel identity> <>
 > <000125> <Conflict Resolved: sbetrmi2 for
 > the object from liberatenode5.dc2.adelphia.com under the bind name
 > sbetrmi2 in the JNDI tree.>
 >
 >
 > Should we use 'load balancing option' instead of 'server affinity' ?
 >
 > Any thuoghts?
 >
 > Thanks in adv.
 > Vijay

Problem in sending JMS message on remote OC4J

I have two OC4J standalone (10.1.3.0.0 build 041119.0001.2385)
The containers work on Windows2000 in different machines connected by the LAN.
The First container has deployed application from example http://www.oracle.com/technology/tech/java/oc4j/1013/howtos/how-to-jca-intro/doc/how-to-jca-intro.html
The second container has j2ee application (Servlet) that sending JMS messages in the queue of the first container.
Code Servlet in second OC4J:
package mypackage2;
import javax.servlet. *;
import javax.servlet.http. *;
import java.io. PrintWriter;
import java.io. IOException;
import javax.jms. *;
import javax.naming. *;
import java.util. *;
public class Servlet1 extends HttpServlet
private static final String CONTENT_TYPE = "text/html;charset=windows-1251";
public void init (ServletConfig config) throws ServletException
super.init (config);
String QUEUE_NAME = "OracleASjms/MyQueue1";
String QUEUE_CONNECTION_FACTORY = "OracleASjms/MyQCF";
public void doGet (HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException
response.setContentType (CONTENT_TYPE);
PrintWriter out = response.getWriter ();
out.println (" < html > ");
out.println (" < head > < title > Servlet1 < /title > < /head > ");
out.println (" < body > ");
try
Hashtable env = new Hashtable ();
env.put (Context. INITIAL_CONTEXT_FACTORY, "oracle.j2ee.rmi.RMIInitialContextFactory");
env.put (Context. SECURITY_PRINCIPAL, "admin");
env.put (Context. SECURITY_CREDENTIALS, "admin");
env.put (Context. PROVIDER_URL, "ormi://host_OC4J_1:23791/jcamdb");
env.put ("dedicated.rmicontext", "true");
InitialContext ic = new InitialContext (env);
QueueConnectionFactory connectionFactory = (QueueConnectionFactory)ic.lookup (QUEUE_CONNECTION_FACTORY);
QueueConnection connection = connectionFactory.createQueueConnection ();
connection.start ();
QueueSession queueSession =
connection.createQueueSession (false, Session.AUTO_ACKNOWLEDGE);
Queue queue = (Queue) ic.lookup (QUEUE_NAME);
ic.close ();
System.out.println (" Queue: " + queue);
QueueSender sender = queueSession.createSender (queue);
System.out.println (" creating Message: " + queue);
Message message = queueSession.createMessage ();
System.out.println (" Message created ");
message.setJMSType ("theMessage");
message.setLongProperty ("time", System.currentTimeMillis ());
message.setStringProperty ("id", "11111");
message.setStringProperty ("oamount", "55555");
message.setStringProperty ("message", "77777");
message.setStringProperty ("RECIPIENT", "MDB");
System.out.println (" Sending message... ");
sender.send (message);
System.out.println (" Message sent ");
sender.close ();
queueSession.close ();
connection.close ();
catch (Exception e)
System.out.println (" ** TEST FAILED ** Exception: " + e);
out.println (e.toString ());
e.printStackTrace ();
out.println (" The servlet has received a GET. This is the reply. < /html > ");
out.close ();
Error: This code send message in The First container, and should send in the second OC4J !!!!
Please answer :
As configure (what code it is necessary to write) servlet (any J2EE the application in OC4J) to use a path to OC4J JMS (remote OC4J JMS) through the Resource Adapter (using OracleASjms.rar). ???

I have two OC4J standalone (10.1.3.0.0 build 041119.0001.2385)
The containers work on Windows2000 in different machines connected by the LAN.
The First container has deployed application from example http://www.oracle.com/technology/tech/java/oc4j/1013/howtos/how-to-jca-intro/doc/how-to-jca-intro.html
The second container has j2ee application (Servlet) that sending JMS messages in the queue of the first container.
Code Servlet in second OC4J:
package mypackage2;
import javax.servlet. *;
import javax.servlet.http. *;
import java.io. PrintWriter;
import java.io. IOException;
import javax.jms. *;
import javax.naming. *;
import java.util. *;
public class Servlet1 extends HttpServlet
private static final String CONTENT_TYPE = "text/html;charset=windows-1251";
public void init (ServletConfig config) throws ServletException
super.init (config);
String QUEUE_NAME = "OracleASjms/MyQueue1";
String QUEUE_CONNECTION_FACTORY = "OracleASjms/MyQCF";
public void doGet (HttpServletRequest request, HttpServletResponse response)
throws ServletException, IOException
response.setContentType (CONTENT_TYPE);
PrintWriter out = response.getWriter ();
out.println (" < html > ");
out.println (" < head > < title > Servlet1 < /title > < /head > ");
out.println (" < body > ");
try
Hashtable env = new Hashtable ();
env.put (Context. INITIAL_CONTEXT_FACTORY, "oracle.j2ee.rmi.RMIInitialContextFactory");
env.put (Context. SECURITY_PRINCIPAL, "admin");
env.put (Context. SECURITY_CREDENTIALS, "admin");
env.put (Context. PROVIDER_URL, "ormi://host_OC4J_1:23791/jcamdb");
env.put ("dedicated.rmicontext", "true");
InitialContext ic = new InitialContext (env);
QueueConnectionFactory connectionFactory = (QueueConnectionFactory)ic.lookup (QUEUE_CONNECTION_FACTORY);
QueueConnection connection = connectionFactory.createQueueConnection ();
connection.start ();
QueueSession queueSession =
connection.createQueueSession (false, Session.AUTO_ACKNOWLEDGE);
Queue queue = (Queue) ic.lookup (QUEUE_NAME);
ic.close ();
System.out.println (" Queue: " + queue);
QueueSender sender = queueSession.createSender (queue);
System.out.println (" creating Message: " + queue);
Message message = queueSession.createMessage ();
System.out.println (" Message created ");
message.setJMSType ("theMessage");
message.setLongProperty ("time", System.currentTimeMillis ());
message.setStringProperty ("id", "11111");
message.setStringProperty ("oamount", "55555");
message.setStringProperty ("message", "77777");
message.setStringProperty ("RECIPIENT", "MDB");
System.out.println (" Sending message... ");
sender.send (message);
System.out.println (" Message sent ");
sender.close ();
queueSession.close ();
connection.close ();
catch (Exception e)
System.out.println (" ** TEST FAILED ** Exception: " + e);
out.println (e.toString ());
e.printStackTrace ();
out.println (" The servlet has received a GET. This is the reply. < /html > ");
out.close ();
Error: This code send message in The First container, and should send in the second OC4J !!!!
Please answer :
As configure (what code it is necessary to write) servlet (any J2EE the application in OC4J) to use a path to OC4J JMS (remote OC4J JMS) through the Resource Adapter (using OracleASjms.rar). ???

Remote queue in XI server for IBM MQSeries

Dear All,
my scenario is IBM MQSeries -> message via sender JMS adapter -> XI -> receiver RFC adapter -> R/3.
now for IBM MQSeries to send a message to XI via a transmission queue in MQSeries - it needs a remote queue name and queue manager name in XI server.
So now where can i find these information regarding remote queue name and queue manager name in XI server. I currently do not know whether in XI server, currently is there any remote queue or not? So how to find this information. If we do not have remote queue manager in XI currently, then how to install a remote queue name and queue manager in XI server.
It is slightly urgent. So i request you all to please reply quickly.
Thanks and Regards,
Rajeev Gupta

Dear Sebastin,
Thanks for your inputs.
I have to connect to MQSeries 5.2.1 to XI server.
am getting the below error in Communicatin Channel Monitoring for my sender JMS adapter:
Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for '<IP_ADRESS>:<MQ_QUEUE_MANAGER>'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:546)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1137)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:799)
com.ibm.mq.MQException: Message catalog not found
at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:171)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:228)
i have written '<IP_ADRESS>:<MQ_QUEUE_MANAGER>' just to hide the data - i am getting <IP_ADRESS> as IP Adress i gave in JMS adapter and <MQ_QUEUE_MANAGER> as Queue Manager i gave in JMS adapter.
i am using the correct IP and 1414 port of MQSeries server. I have used a MQQueueManager defined in MQSeries. i have deployed JMS adapter properly in XI server.
So can anybody suggest what could be the possible reason of this error and how to rectify it. It is slightly urgent.
One more question - should the queue manager in MQSeries server be a local or remote queue manager..........i was not able to create a remote queue manager in MQSeries 5.2.1 as by default it is creating a local queue manager.......
Thanks and Regards,
Rajeev Gupta

MDB Listening to remote queue

 Hi,
 Could any of you please let me know what needs to be done to configure my MDB
 to listen to a remote queue in a different domain (also using wls 7.0).
 I tried adding the <provider-url> element in the weblogic-ejb-jar.xml but looks
 like that didnt work.
 Thanks,
 -Sri


Posting the actual error helps. This error usually occurs due
 to a naming conflict. Make sure that:
 All local and remote:
 WL servers are named differently
 WL JMS servers are named differently
 WL JMS stores are named differently
 Tom, BEA
 P.S. For future reference, a google search of
 this newsgroup often quickly leads to answers. In this
 case search for "Connection not found" or "invocableFind".
 Sri wrote:
 > Tom, I did. But I still get this error...
 >
 > [exec] <Jun 10, 2003 9:27:57 AM EDT> <Error> <EJB> <010020> <EJB-20 - Messa
 > geDriven - Couldn't start the JMS connection: weblogic.jms.common.JMSException:
 > Connection not found
 > [exec] weblogic.jms.common.JMSException: Connection not found
 > [exec] at weblogic.jms.dispatcher.InvocableManager.invocableFind(Invoca
 > bleManager.java:134)
 > [exec] at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Req
 > uest.java:592)
 > [exec] at weblogic.jms.dispatcher.DispatcherImpl.dispatchSync(Dispatche
 > rImpl.java:275)
 > [exec] at weblogic.jms.client.JMSConnection.start(JMSConnection.java:54
 > 7)
 > [exec] at weblogic.ejb20.internal.JMSConnectionPoller.startJMSConnectio
 > n(JMSConnectionPoller.java:1228)
 > [exec] at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.startCo
 > nnection(MessageDrivenBeanPoolInfoImpl.java:150)
 > [exec] at weblogic.ejb20.deployer.MessageDrivenBeanPoolInfoImpl.start(M
 > essageDrivenBeanPoolInfoImpl.java:223)
 > [exec] at weblogic.ejb20.deployer.EJBDeployer.deployMessageDrivenBeans(
 > EJBDeployer.java:1560)
 > [exec] at weblogic.ejb20.deployer.EJBDeployer.start(EJBDeployer.java:14
 > 06)
 > [exec] at weblogic.ejb20.deployer.EJBModule.start(EJBModule.java:391)
 > [exec] at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationC
 > ontainer.java:1039)
 > [exec] at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicati
 > onContainer.java:1025)
 > [exec] at weblogic.management.deploy.slave.SlaveDeployer.setActivationS
 > tateForAllApplications(SlaveDeployer.java:617)
 > [exec] at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDe
 > ployer.java:376)
 > [exec] at weblogic.management.deploy.DeploymentManagerServerLifeCycleIm
 > pl.resume(DeploymentManagerServerLifeCycleImpl.java:235)
 > [exec] at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleLi
 > st.java:65)
 > [exec] at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:832)
 > [exec] at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:300)
 > [exec] at weblogic.Server.main(Server.java:32)
 > [exec] >
 >
 > Tom Barnes <[email protected]> wrote:
 >
 >>Check your server logs for Warning and/or error messages.
 >>
 >>Make sure that you specified a correct:
 >>
 >>provider-url
 >>
 >>destination-jndi-name
 >>
 >>connection-factory-jndi-name (needed if you disabled the default
 >>connection factories in the remote domain)
 >>
 >>Sri wrote:
 >>
 >>>Hi,
 >>>
 >>>Could any of you please let me know what needs to be done to configure
 >>
 >>my MDB
 >>
 >>>to listen to a remote queue in a different domain (also using wls 7.0).
 >>
 >>>I tried adding the <provider-url> element in the weblogic-ejb-jar.xml
 >>
 >>but looks
 >>
 >>>like that didnt work.
 >>>
 >>>Thanks,
 >>>-Sri
 >>
 >

Foreign JMS vs. Remote MDB

Hi,
          I have a JMS scenario that I'm hoping to get some input on. The system architecture is as follows:
          One WebLogic 8.1 SP5 domain with a JMS server
          One WebLogic 9.2 MP1 domain with no JMS server
          We'd like to consume a JMS message that's sitting on a queue in the 8.1 domain by code running on the 9.2 domain.
          Without configuring a JMS server in the 9.2 domain (which we'd like to avoid), the two obvious options are:
          1. An MDB running on the 9.2 server that connects to a queue on the 8.1 server
          2. An MDB running on the 9.2 server that connects to a foreign JMS server locally which in turn is linked to the 8.1's JMS server
          Does anyone have any suggestions, experience from this or a similar scenario?
          The main areas that I'd be interested in are:
          - Inter domain compatability
          - Any problems with Transactions, XA
          Many thanks,
          Eoin

Hi,
          I think your approach is fine - inter-version compatibility is supported for both JMS and XA. You'll need to ensure that all 9.1 and 8.1 WL domain names are unique, ditto for all 8.1 WL server names, 8.1 WL store names, plus 8.1 JMS server names (even across different domains).
          "1" and "2" are essentially the same in that "Foreign JMS" is simply a mapping from the local JNDI naming service to a remote JMS service . "2" tends to be preferable as it can simplify administration once configured. For more information, see the "Integrating Remote JMS Providers" FAQ linked off of this page: "http://edocs.bea.com/wls/docs92/messaging.html".
          FYI There are advantages in using 9.x and later JMS - not only does it have a broader set of features, but it also has more sophisticated message management (use the console to pause/resume dests, view individual messages, etc), and significantly higher performance. Also, 9.x MDBs do a better job of connecting to remote 9.x distributed destinations than 8.1 MDBs - as they automatically ensure that all component destinations get serviced.
          Tom

Maximum JMS Connections

 Hi,
 I would like to know what is the maximum JMS connections weblogic server can
 handle anytime. And where do we set this parameter? we have a group of Message
 Listeners listening to a Queue on weblogic by opening JMS connections at the same
 time. So I was wondering how many JMS clients can Weblogic handle?? And also does
 it impact the performance of weblgic server.
 Thanx,
 Sankas


 Thanks for the information guys. It was very helful.
 -Sankas
 Tom Barnes <[email protected]> wrote:
 >Each remote JVM to the WL server multiplexes network calls over a single
 >socket
 >connection, and each remote JVM may have many JMSConnections into the
 >WL server. A
 >single server can support thousands of remote JVMs, and tens of thousands
 >of
 >JMSConnections -- even with the default thread-pool sizes. Clustering
 >and
 >distributed destinations can help one scale higher. Of course, performance
 >and
 >scalability are highly application and hardware dependent, and the best
 >thing to do
 >is create a benchmark that emulates your particular apps characteristics
 >and see
 >how it scales...
 >
 >Tom, BEA
 >
 >Sankas wrote:
 >
 >> Shean,
 >> I did not have anything in mind. But if you see the weblogic console
 >there
 >> is a default parameter "JMS Thread Pool Size = 15" under the Server
 >section in
 >> the services/JMS Tab .
 >> I thought this was the JMSConnections count in the server.
 >> Well I think it would be good to know how far can we go
 >> with the JMS connections thing.
 >>
 >> Thanx,
 >> Sankas
 >>
 >> "Shean-Guang Chang" <[email protected]> wrote:
 >> > It will depend on the memory resource you used for the JVM (both
 >WLS
 >> >server
 >> >and client). There is no design limit for this. Do you have a number
 >> >in
 >> >mind?
 >> >"Sankas" <[email protected]> wrote in message
 >> >news:[email protected]...
 >> >>
 >> >> Hi,
 >> >> I would like to know what is the maximum JMS connections weblogic
 >> >server can
 >> >> handle anytime. And where do we set this parameter? we have a group
 >> >of
 >> >Message
 >> >> Listeners listening to a Queue on weblogic by opening JMS connections
 >> >at
 >> >the same
 >> >> time. So I was wondering how many JMS clients can Weblogic handle??
 >> >And
 >> >also does
 >> >> it impact the performance of weblgic server.
 >> >>
 >> >> Thanx,
 >> >> Sankas
 >> >
 >> >
 >

Reliable JMS connection?! Fantasy?

Good day!
Is there a standart (classical ) way to organize reliable, with confirmation of delivery to queue application?
On JBoss4 i tried to solve this problem and recognize, was my message delivered to remote queue or not, but I found that there is no way (i tried analise all sorts of exceptions while connection) to be 100% sure, that my message put in remote queue. It happened that no exceptions were generated while i switched on and off net cables, but message was not put in queue.

Hi russiandroopy,
If you send a DeliveryMode.PERSISTENT message to a JMS queue and the call succeeds you are guaranteed (as per the JMS specification) that the message has been stored reliably on the JMS server. The method returning successfully may be considered your "confirmation of delivery".
However the following two caveats apply:
1. From the JMS Javadocs speaking about a DeliveryMode of PERSISTENT :
This mode instructs the JMS provider to log the message to stable storage as part of the client's send operation. Only a hard media failure should cause a PERSISTENT message to be lost.
2. There could be the case where the JMS provider has received the message, performed all requirements in terms of persistence and is in the process of returning out of the send operation when the server crashes. In this case the client will not receive its "confirmation of delivery" (i.e. the clients send method call may terminate with a JMSException) though the message has been persisted.
Hope this helps,
Tom Jenkinson

JMS connection from SAP PI to Oracle AQ via JNDI...

Hi,
I am currently working on a project that requires connections between PI and Oracle AQ. It was advised that we shoule use PI JMS adpater with JNDI driver. However, it seems that not many people have tried this approach.
Has anyone had similar solutions in production ? How repliable it is ?
Your help is very much appreciated
Tim

Hi Tim,
We implemented a similar scenario and now itu2019s still working.
You have to configure a JNDI connection, but not directly with the Oracle AQ. The Oracle AQ are just queues, and you need a JMS provider in order to establish the connection with these queues. The solution we implemented was:
1. Configure one OC4J server as JMS provider for the Oracle AQ queues.
2. Configure JMS communication channels in SAP PI to establish the connection with the OC4J server.
Maybe you can use a different and newer JMS provider, as BEA Weblogic or SAP WAS (I donu2019t know if itu2019s possible).
We implement the scenario in SAP PI 7.0, and with this version we had a problem: When the communication between JMS adapter and the queues was broken (the DDBB fell down for example), the channel failed, itu2019s normal. But when the DDBB was already running the channel stayed in an error state, and we had to restart the channel manually. The response of SAP to this issue was that the channel behavior was correct because the connection failed.
But this problem occurred rarely, maybe once a month. The solution is very reliable, we exchange a lot of message with this solution, and support messages of any size with an excellent performance.
Best Regards,
Roberto

Not able to connect to a queue under a foreign server.

Not able to connect to a queue under a foreign server.
I'm using WebLogic Server Version: 10.3.3.0. The foreign server is running, and can be pinged from this local server. Also the port where queue resides on foreign server, can be accessed through the my local server.
OS used is AIX 6.0 on both servers.
Tried restarting the local server but nothing helps. Same error continues.
HAS ANYBODY FACED THIS PROBLEM? WHAT IS THE CAUSE AND SOLUTION FOR THIS?
It throws following errors:
<Jun 25, 2012 12:14:15 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
javax.naming.NoInitialContextException: Failed to create InitialContext using factory specified in hashtable [Root exception is java.lang.ClassCastException: Expected RemoteException, RuntimeException, or Error but received: 'java.io.IOException: RJVM has already been shutdown']
 at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:247)
 at javax.naming.InitialContext.initializeDefaultInitCtx(InitialContext.java:318)
 at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:348)
 at javax.naming.InitialContext.internalInit(InitialContext.java:286)
 at javax.naming.InitialContext.<init>(InitialContext.java:211)
 at weblogic.deployment.jms.ForeignOpaqueReference.getReferent(ForeignOpaqueReference.java:179)
 at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)
 at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:377)
 at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:856)
 at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:209)
 at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
 at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
 at javax.naming.InitialContext.lookup(InitialContext.java:436)
 at weblogic.jms.common.CDS$2.run(CDS.java:503)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
 at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
 at weblogic.jms.common.CDS.lookupDestination(CDS.java:497)
 at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:276)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1455)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1252)
 at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
 at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
 at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
 at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:531)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:157)
 at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
 at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
 at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
 at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
 at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
 at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.ClassCastException: Expected RemoteException, RuntimeException, or Error but received: 'java.io.IOException: RJVM has already been shutdown'
 at weblogic.common.internal.BootServicesStub.getMsg(BootServicesStub.java:34)
 at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
 at weblogic.security.acl.internal.RemoteAuthenticate.authenticate(RemoteAuthenticate.java:90)
 at weblogic.jndi.WLInitialContextFactoryDelegate.authenticateRemotely(WLInitialContextFactoryDelegate.java:746)
 at weblogic.jndi.WLInitialContextFactoryDelegate.pushSubject(WLInitialContextFactoryDelegate.java:678)
 at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:469)
 at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:376)
 at weblogic.jndi.Environment.getContext(Environment.java:315)
 at weblogic.jndi.Environment.getContext(Environment.java:285)
 at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
 at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:239)
 ... 46 more
>
<Jun 25, 2012 12:14:15 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
Can not get destination information. The destination JNDI name is NOTIFY_QUEUE, the provider URL is null>
<Jun 25, 2012 12:14:45 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
 at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
 at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
 at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
 at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
 at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
 Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:15:03 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
 at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
 at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
 at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
 at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
 at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
 Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:15:25 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
 at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
 at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
 at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
 at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
 at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
 Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:15:35 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
 at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
 at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
 at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
 at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
 at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
 Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:15:43 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
 at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
 at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
 at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
 at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
 at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
 Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:20:53 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
 at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
 at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
 at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
 at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
 at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
 Truncated. see log file for complete stacktrace
>
<Jun 25, 2012 12:24:16 AM GMT+06:00> <Error> <Common> <BEA-000621> <Expected RemoteException, RuntimeException, or Error
java.io.IOException: RJVM has already been shutdown
java.io.IOException: RJVM has already been shutdown
 at weblogic.rjvm.RJVMImpl.addPendingResponse(RJVMImpl.java:511)
 at weblogic.rjvm.RJVMImpl.send(RJVMImpl.java:898)
 at weblogic.rjvm.MsgAbbrevOutputStream.flushAndSend(MsgAbbrevOutputStream.java:394)
 at weblogic.rjvm.MsgAbbrevOutputStream.sendRecv(MsgAbbrevOutputStream.java:424)
 at weblogic.common.internal.BootServicesStub.authenticate(BootServicesStub.java:54)
 Truncated. see log file for complete stacktrace
Edited by: 942523 on Jun 24, 2012 11:38 PM

Thanks René van Wijk for the reply.
I have a foreign server created in my local server, where i have already given the provider URL. This foreign server has the one queue and one queue connection factory under it to which I'm referring to.
Under JNDI tree i noticed this, for the queue(NOTIFY_QUEUE) i'm trying to read from one of the EJB:
This page displays details about this bound object.
Failed to create InitialContext using factory specified in hashtable
Also,etc/hosts has already these IP entries. Even after hardcoding the provider URL its throwing following:
<Jun 25, 2012 3:01:31 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
javax.naming.CommunicationException [Root exception is weblogic.rjvm.PeerGoneException: ; nested exception is:
 java.io.EOFException]
 at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:74)
 at weblogic.jndi.internal.WLContextImpl.translateException(WLContextImpl.java:452)
 at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:408)
 at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393)
 at javax.naming.InitialContext.lookup(InitialContext.java:436)
 at weblogic.jms.common.CDS$2.run(CDS.java:503)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
 at weblogic.jms.common.CrossDomainSecurityManager.runAs(CrossDomainSecurityManager.java:130)
 at weblogic.jms.common.CDS.lookupDestination(CDS.java:497)
 at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:276)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1455)
 at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1252)
 at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1320)
 at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
 at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
 at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:531)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:165)
 at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:157)
 at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
 at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
 at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:43)
 at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
 at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
 at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
 at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
 at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
 at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
 at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
 at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: weblogic.rjvm.PeerGoneException: ; nested exception is:
 java.io.EOFException
 at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
 at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
 at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
 at weblogic.jndi.internal.ServerNamingNode_1033_WLStub.lookup(Unknown Source)
 at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:405)
 ... 36 more
Caused by: java.io.EOFException
 at weblogic.rjvm.t3.MuxableSocketT3.endOfStream(MuxableSocketT3.java:338)
 at weblogic.socket.SocketMuxer.deliverExceptionAndCleanup(SocketMuxer.java:768)
 at weblogic.socket.SocketMuxer.deliverEndOfStream(SocketMuxer.java:702)
 at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:890)
 at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:840)
 at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:130)
 at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
 at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
 at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
 at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
>
<Jun 25, 2012 3:01:31 AM GMT+06:00> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: NotificationQueueAnonymousWaiter is unable to connect to the JMS destination: NOTIFY_QUEUE. The Error was:
Can not get destination information. The destination JNDI name is NOTIFY_QUEUE, the provider URL is t3://10.52.50.51:7002>
Let me know if any other thing i'm missing or it can be something else like network or some other issue.

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

JMS connecting to remote Queue

Similar Messages

Maybe you are looking for