Implementing JMS Brigde

Hi All,
 I am trying to implement JMS between two weblogic servers installed in different machines.
 I followed this steps using example server in both:
 1. The "Guest Disabled" check box must not be checked on that domain.
 2. The "Enable Generated Credential" check box must not be checked.
 3. In the exampleQueue Connection Factory "XA Connection Factory Enabled" must be checked.
 When Weblogic starts, follow is part of log:
 <7/10/2005 07:46:25 PM GMT-06:00> <Debug> <MessagingBridge> <BEA-200006> <Messaging bridge debugging STARTUP! Bridge Puente's source configurations are:
 AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
 Classpath=null
 ConnectionURL = t3://laboratorio:7001
 DestinationType = Queue
 DestinationJNDIName = weblogic.examples.jms.exampleQueue
 InitialContextFactory = weblogic.jndi.WLInitialContextFactory
 ConnectionFactoryJNDIName = weblogic.examples.jms.QueueConnectionFactory
 .>
 <7/10/2005 07:46:25 PM GMT-06:00> <Debug> <MessagingBridge> <BEA-200006> <Messaging bridge debugging STARTUP! Bridge Puente's target configurations are:
 AdapterJNDIName=eis.jms.WLSConnectionFactoryJNDIXA
 Classpath=null
 ConnectionURL = t3://172.16.1.44:7001
 DestinationType = Queue
 DestinationJNDIName = weblogic.examples.jms.exampleQueue
 InitialContextFactory = weblogic.jndi.WLInitialContextFactory
 ConnectionFactoryJNDIName = weblogic.jms.XAConnectionFactory
 .>
 <7/10/2005 07:46:32 PM GMT-06:00> <Debug> <MessagingBridge> <BEA-200006> <Messag
 ing bridge debugging RUNTIME! Bridge Puente Successfully got connection to the source destination.>
 <7/10/2005 07:46:32 PM GMT-06:00> <Debug> <MessagingBridge> <BEA-200006> <Messag
 ing bridge debugging RUNTIME! Bridge Puente Getting target connection.>
 <7/10/2005 07:46:35 PM GMT-06:00> <Warning> <Connector> <BEA-190032> << Weblogic
 Messaging Bridge Adapter (XA)_eis/jms/WLSConnectionFactoryJNDIXA > ResourceAllo
 cationException of javax.resource.ResourceException: Failed to start the connect
 ion on createManagedConnection.>
 Please any help will be appreciated.
 Thanks in advance...
 Jorge

Hi Jorge,
          Your target and destination que JNDI names are same. Weblogic does not support same name. Please refer to naming conventions for destinations.
          DestinationJNDIName = weblogic.examples.jms.exampleQueue
          ConnectionURL = t3://172.16.1.44:7001
          DestinationType = Queue
          DestinationJNDIName = weblogic.examples.jms.exampleQueue
          Thanks
          Akash

Similar Messages

Facing problem while implementing JMS in Weblogic 8.1

Hi all,
I am very new to JMS.
I am trying to implement JMS in Weblogic.
I have cofigured the server properly but while i am executing my receiver class i am getting the following error:
javax.naming.NameNotFoundException: Unable to resolve 'MyJMSQueue1' Resolved [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'MyJMSQueue1' Resolved ]; remaining name 'MyJMSQueue1'
Waiting for messages....
and my receiver program is as follows:
import java.util.Hashtable;
import javax.jms.JMSException;
import javax.jms.Message;
import javax.jms.MessageListener;
import javax.jms.Queue;
import javax.jms.QueueConnection;
import javax.jms.QueueConnectionFactory;
import javax.jms.QueueReceiver;
import javax.jms.QueueSession;
import javax.jms.TextMessage;
import javax.naming.Context;
import javax.naming.InitialContext;
public class SampleQueueReceiver implements MessageListener
private boolean done = false;
private Context ctx = null;
private QueueConnectionFactory connectionFactory = null;
private QueueConnection connection = null;
private QueueSession session = null;
private QueueReceiver receiver = null;
private Queue queue = null;
private Hashtable ht = null;
public void init()
try
ht = new Hashtable();
ht.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
ht.put(Context.PROVIDER_URL, "t3://localhost:7001");
ctx = new InitialContext(ht);
connectionFactory =(QueueConnectionFactory)ctx.lookup("weblogic.jms.ConnectionFactory");
connection = connectionFactory.createQueueConnection();
session = connection.createQueueSession(false,javax.jms.QueueSession.AUTO_ACKNOWLEDGE);
queue = (Queue) ctx.lookup("MyJMSQueue1");
receiver = session.createReceiver(queue);
receiver.setMessageListener(this);
connection.start();
catch ( Exception e )
System.out.println(e);
public void close() throws JMSException
try
receiver.close();
session.close();
connection.close();
catch ( Exception e )
System.out.println(e);
public void onMessage(Message message)
if ( message instanceof TextMessage )
try
TextMessage textMessage = (TextMessage) message;
String msg = textMessage.getText();
System.out.println("Received message: " + msg);
if ( msg.equals("exit") )
synchronized (this)
done = true;
this.notifyAll();
catch ( Exception e )
System.out.println(e);
public static void main(String[] args)
try
SampleQueueReceiver sqr = new SampleQueueReceiver();
sqr.init();
System.out.println("Waiting for messages....");
synchronized (sqr)
while ( !sqr.done )
try
sqr.wait();
catch ( InterruptedException ie )
sqr.close();
catch ( Exception e )
System.out.println(e);
I have already configured MyJMSQueue in the server.....
Someone please guide me...
Thanks in Advance........
Goutam

Looks like configuration prob.
Have you tried jms examples of weblogic ? you may need to re-configure your server setup, to create example server.

Implementing JMS-based EDN and JNDI-based EDN

I´m implementing a composite with two kinds of events JMS and JNDI and I saw in the configuration for JMS-base I must remove the EDN-DB JNDI sources to use EDN-JMS data sources. My doubt is, does my composite will work with that two kinds of events?
All the best,
Pierre

This is a functional desire that has come up on some of our projects too but is not directly supported by EDN. We have discussed the idea of EDN proxies (either as SOA Composites or as PL/SQL EDN subscribers). These proxies (presumably always active/deployed) would subscribe to EDN and provide a persistent buffer for the application. This is essentially implementing a persistence queue for each subscriber, but we wish to avoid statically configuring an AQ or JMS queue destination for each and every app subscription case and perhaps use some shared-but-keyed persistence design (e.g. database table).
Architecturally, this starts to hit on the ever evasive and controversial question of what is an "Event" versus what is a "Message". i.e. can you afford to sometimes miss the former but not the latter?
-Todd

Need suggestion on implementing JMS message error recovery

Hi,
Our application has a JMS topic where we publish application events. Now, there can be scenarios where the consumers cannot process the message due to some infrastructure issues and would error out. We need a way so that those messages can be reprocessed again later. we are thinking of the following design for JMS message error recovery
1. Use a persistent TOPIC (this would ensure guaranteed delivery)
2. Configure a error destination on JMS topic e.g a jms queue
3. Have an error handling MDB listening to the Error destination. An error handling MDB would dequeue the errored messages from error destination and persist it to a Data base "error" table..
4. Provide a mechanism to republish those messages to topic (e.g a scheduler or admin ui or a command line utility) .. The messages would deleted from database "error" table and published to topic again....
A. Are there any issues with the above design which we need to handle?
B. Are there any additional steps required in a Cluster environment with a distributed topic and distribute error destination? (our error mdb will have one-copy-per-application setting)
B. From a performance angle, Is it OK to use persistent TOPIC ? Or will it better to persist the message to the db table and then publish it as a non persistent message ... ? (But i guess the performance should be more or less the same in both of these approaches)
C. Are there any other recommended design patterns for error recovery of JMS messages
Please advise.
Regards,
Arif

Thanks Tom !
We may not be able to go with the approach of delaying/pausing redelivery of the messsage because
1. Pausing entire MDB approach: Our MDB application consumes messages generated by different producers and our MDB needs to continue processing the messages even if messages corresponding to one producer is erroring out
2. Redelivery delay : This would only delay the retry of an errored message. But there would still be a problem if the message fails during all retries (i.e redelivery limit count). We don't want to lose this message. In our case, It is possible that a particular message cannot be processed due to unavailability of a third party system for hours or may be a day.
Basically, i am looking on approaches for a robust and performant error recovery/retry framework for our application (refer details in my first post on this thread) while fully making use of all features provided by middleware (WLS). Please advise.
Regards,
Arif

Document for JMS Failover Implementation On WebLogic

Hi,
I am looking some good links and techniques to implement JMS failover using WebLogic 10.3.
FailOver* [As we do with our Databases (Concept of Clustring)]
System will consist of two app servers and each will have its own application deployments but if one failed for some reason the application messages should redirected to the other servere and vice versa.
Above efinition is very brief but if anyone can help provide some good documents and info how to implement it it will be appriciated.
Thanks :-)

Thanks alot guys for your help. We successfully implemented it at our servers here by creating distributed queues targetting all servers in a cluster.
One point which I think is worth mentioning and I want to share with all us here is that; when App Server [where MDB will post the message finally after retrieving from queue] if that goes down what will happen, what MDB will do with that message?.
We impleneted the DLQ (error destination) and deploy one more MDB_DLQ_SERVER2 (Let say App SERVER 1 is down) which gets triggered when any message comes to DLQ and post that message to some other App Server, Let say message has been read by MDB_SERVER1 on SERVER1 but offcourse actaull server is down so message should get Re-directed to its Error Destination after it expiration peiod or whatever the settings are. DLQ (Error Destination) which is also a distributed destinatrion again targetting all servers in cluster same as actaull Request or Reply queues BUT MDB_DLQ_SERVER2 which is deployed on Server2 is NOT able to read this message. It get triggered but can not access the message.
After debugging for almost a day we found out its because message has been transafed to DLQ but actaully its resides in a FILESTORE_SERVER1 and MDB_DLQ_SERVER2 is not able to access it.
To work with that we have to define MDB_DLQ_SERVER1 to cater the SERVER1 failure and MDB_DLQ_SERVER2 to cater SERVER2 failure.
Reason I am mentioning this because as I said DLQ is also a normal Distributed Queue but at the same time its NOT as Distributed as its says.
Hope you all understand what I just wrote above.
Now I need to implement exactly the same scenario using four seperate physicall machine containing my four servers. I tried this scenario by creating four machines where node manager for each server is running and listning but when I am trying to start the server it gives me Certificate Exception with bad user name and password. Anyway I have seen some posts here regarding this; So i think i'll be fine.
Thanks Again,
Sheeraz

Regarding step by step JMS implementation

HI
i am working on jms first time and i am using websphere 6.0 and jms 1.1.
i use this link to make a sample application ..
http://www-128.ibm.com/developerworks/websphere/library/techarticles/0407_yu/0407_yu.html
well here we will not use websphere MQ series to handle messages. we need to handle this all messanges manually.So Plz let me know about the process to implement jms 1.1 in WAS 6.0 without using webphere MQ series.I m using Embedded messaging insteead of websphere MQ Series.
so here when i run this applicaiton t gives this error:-
*** Starting the server ***
************ Start Display Current Environment ************
WebSphere Platform 5.1 [BASE 5.1.1 a0426.01] [JDK 1.4.2 cn1420-20040626] running with process name localhost\localhost\server1 and process id 2628
Host Operating System is Windows XP, version 5.1
Java version = J2RE 1.4.2 IBM Windows 32 build cn1420-20040626 (JIT enabled: jitc), Java Compiler = jitc, Java VM name = Classic VM
was.install.root = C:/Program Files/IBM/Rational/SDP/6.0/runtimes/base_v51
user.install.root = C:/Program Files/IBM/Rational/SDP/6.0/runtimes/base_v51
Java Home = C:\Program Files\IBM\Rational\SDP\6.0\runtimes\base_v51\java\jre
ws.ext.dirs = C:/Program Files/IBM/Rational/SDP/6.0/runtimes/base_v51/java/lib;C:/Program Files/IBM/Rational/SDP/6.0/runtimes/base_v51/classes;C:/Program Files/IBM/Rational/SDP/6.0/runtimes/base_v51/classes;C:/Program Files/IBM/Rational/SDP/6.0/runtimes/base_v51/lib;C:/Program Files/IBM/Rational/SDP/6.0/runtimes/base_v51/lib/ext;C:/Program Files/IBM/Rational/SDP/6.0/runtimes/base_v51/web/help;C:/Program Files/IBM/Rational/SDP/6.0/runtimes/base_v51/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime;C:/Program Files/IBM/SQLLIB/java/db2java.zip;C:/Program Files/IBM/Rational/SDP/6.0/rwd/eclipse/plugins/com.ibm.etools.webservice.consumption.soap_6.0.0/runtime/worf.jar
Classpath = C:/Program Files/IBM/Rational/SDP/6.0/runtimes/base_v51/properties;C:/Program Files/IBM/Rational/SDP/6.0/runtimes/base_v51/properties;C:/Program Files/IBM/Rational/SDP/6.0/runtimes/base_v51/lib/bootstrap.jar;C:/Program Files/IBM/Rational/SDP/6.0/runtimes/base_v51/lib/j2ee.jar;C:/Program Files/IBM/Rational/SDP/6.0/runtimes/base_v51/lib/lmproxy.jar;C:/Program Files/IBM/Rational/SDP/6.0/runtimes/base_v51/lib/urlprotocols.jar;C:/Program Files/IBM/Rational/SDP/6.0/rwd/eclipse/plugins/com.ibm.etools.websphere.tools.common_6.0.0/wteServers.jar;C:/Program Files/IBM/Rational/SDP/6.0/rwd/eclipse/plugins/com.ibm.etools.websphere.tools.common_6.0.0/wasToolsCommon.jar
Java Library path = C:\Program Files\IBM\Rational\SDP\6.0\runtimes\base_v51\bin;C:\Program Files\IBM\Rational\SDP\6.0\runtimes\base_v51\java/bin;C:\Program Files\IBM\Rational\SDP\6.0\runtimes\base_v51\java/jre/bin;C:\Program Files\IBM\Rational\SDP\6.0\eclipse\jre\bin;.;C:\Program Files\IBM\Rational\SDP\6.0\eclipse\jre\bin;C:\Program Files\IBM\WebSphere MQ\Java\lib;C:\Program Files\NCR\Teradata Client\DevKit\;C:\Program Files\NCR\Teradata Client\WinCLI-Runtime\;DevKit\;C:\Program Files\NCR\Teradata Client\Bin;C:\WINDOWS\system32\;C:\WINDOWS\system32\;C:\Program Files\NCR\Teradata Client\cliv2\;C:\Program Files\NCR\Common Files\Shared ICU Libraries for Teradata\lib;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\j2sdk1.4.1_06\bin;.;C:\PROGRA~1\IBM\SQLLIB\BIN;C:\PROGRA~1\IBM\SQLLIB\FUNCTION;C:\PROGRA~1\IBM\SQLLIB\SAMPLES\REPL;C:\Program Files\IBM\WebSphere MQ\bin;C:\Program Files\IBM\WebSphere MQ\Java\bin;C:\Program Files\IBM\WebSphere MQ\WEMPS\bin;C:\Program Files\IBM\Rational\SDP\6.0\runtimes\base_v51\bin;C:\Sun\AppServer\bin;C:\Program Files\SSH Communications Security\SSH Secure Shell
************* End Display Current Environment *************
[2/21/08 0:37:32:500 IST] 329af89b ManagerAdmin I TRAS0017I: The startup trace state is *=all=disabled.
[2/21/08 0:37:33:062 IST] 329af89b AdminInitiali A ADMN0015I: AdminService initialized
[2/21/08 0:37:33:531 IST] 329af89b ConfigInfoBui A NMSV0819I: No name server custom properties were found.
[2/21/08 0:37:33:688 IST] 329af89b Configuration A SECJ0215I: Successfully set JAAS login provider configuration class to com.ibm.ws.security.auth.login.Configuration.
[2/21/08 0:37:33:750 IST] 329af89b SecurityDM I SECJ0231I: The Security component's FFDC Diagnostic Module com.ibm.ws.security.core.SecurityDM registered successfully: true.
[2/21/08 0:37:33:922 IST] 329af89b SecurityCompo I SECJ0309I: Java 2 Security is disabled.
[2/21/08 0:37:33:922 IST] 329af89b SecurityCompo I SECJ0212I: WCCM JAAS configuration information successfully pushed to login provider class.
[2/21/08 0:37:33:938 IST] 329af89b SecurityCompo I SECJ0240I: Security service initialization completed successfully
[2/21/08 0:37:33:938 IST] 329af89b JMSRegistrati A MSGS0602I: WebSphere Embedded Messaging Client only has been installed
[2/21/08 0:37:36:188 IST] 329af89b JMSEmbeddedPr A MSGS0050I: Starting the Queue Manager
[2/21/08 0:37:41:672 IST] 329af89b JMSEmbeddedPr A MSGS0051I: Queue Manager open for business
[2/21/08 0:37:41:688 IST] 329af89b JMSEmbeddedPr A MSGS0052I: Starting the Broker
[2/21/08 0:37:42:156 IST] 5e48f89a BrokerDFEThre E MSGS0201E: Unable to start the Broker because WebSphere Embedded Messaging Server support not been installed
[2/21/08 0:40:42:172 IST] 329af89b BrokerManager E MSGS0252E: The Broker has terminated unexpectedly
[2/21/08 0:40:42:188 IST] 329af89b JMSService E MSGS0001E: Starting the JMS Server failed with exception: java.lang.Exception: MSGS0252E: **The Broker has terminated unexpectedly**
     at com.ibm.ws.messaging.BrokerManager.pingDFE(BrokerManager.java:344)
     at com.ibm.ws.messaging.BrokerManager.startFlows(BrokerManager.java:808)
     at com.ibm.ws.messaging.BrokerManager.startBroker(BrokerManager.java:251)
     at com.ibm.ws.messaging.JMSEmbeddedProviderImpl.start(JMSEmbeddedProviderImpl.java:194)
     at com.ibm.ws.messaging.JMSService.start(JMSService.java:288)
     at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
     at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
     at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:243)
     at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
     at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
     at java.lang.reflect.Method.invoke(Method.java:391)
     at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:189)
     at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:92)
[2/21/08 0:40:42:266 IST] 329af89b ContainerImpl E WSVR0501E: Error creating component null [class com.ibm.ws.messaging.JMSService]
com.ibm.ws.exception.RuntimeWarning: MSGS0001E: Starting the JMS Server failed with exception: java.lang.Exception: MSGS0252E: The Broker has terminated unexpectedly
     at com.ibm.ws.messaging.JMSService.start(JMSService.java:295)
     at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
     at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
     at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:243)
     at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
     at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
     at java.lang.reflect.Method.invoke(Method.java:391)
     at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:189)
     at com.ibm.etools.websphere.tools.runner.api.ServerRunnerV5$1.run(ServerRunnerV5.java:92)
[2/21/08 0:40:43:016 IST] 329af89b ResourceMgrIm I WSVR0049I: Binding QCF as QCF
[2/21/08 0:40:43:141 IST] 329af89b ResourceMgrIm I WSVR0049I: Binding PointToPointQ as Q
[2/21/08 0:40:43:438 IST] 329af89b CacheServiceI I DYNA0048I: WebSphere Dynamic Cache initialized successfully.
[2/21/08 0:40:44:969 IST] 329af89b JMXSoapAdapte A ADMC0013I: SOAP connector available at port 8880
[2/21/08 0:40:44:984 IST] 329af89b SecurityCompo I SECJ0243I: Security service started successfully
[2/21/08 0:40:44:984 IST] 329af89b SecurityCompo I SECJ0210I: Security enabled false
[2/21/08 0:40:45:391 IST] 329af89b ApplicationMg A WSVR0200I: Starting application: IBMUTC
[2/21/08 0:40:45:453 IST] 329af89b WebContainer A SRVE0161I: IBM WebSphere Application Server - Web Container. Copyright IBM Corp. 1998-2002
[2/21/08 0:40:45:469 IST] 329af89b WebContainer A SRVE0162I: Servlet Specification Level: 2.3
[2/21/08 0:40:45:469 IST] 329af89b WebContainer A SRVE0163I: Supported JSP Specification Level: 1.2
[2/21/08 0:40:45:594 IST] 329af89b WebContainer A SRVE0169I: Loading Web Module: Universal Test Client.
[2/21/08 0:40:45:781 IST] 329af89b WebGroup I SRVE0180I: [Universal Test Client] [UTC] [Servlet.LOG]: JSP 1.2 Processor: init
[2/21/08 0:40:45:844 IST] 329af89b WebGroup I SRVE0180I: [Universal Test Client] [UTC] [Servlet.LOG]: SimpleFileServlet: init
[2/21/08 0:40:45:891 IST] 329af89b ApplicationMg A WSVR0221I: Application started: IBMUTC
[2/21/08 0:40:45:906 IST] 329af89b HttpTransport A SRVE0171I: Transport http is listening on port 9,080.
[2/21/08 0:40:48:000 IST] 329af89b HttpTransport A SRVE0171I: Transport https is listening on port 9,443.
[2/21/08 0:40:48:125 IST] 329af89b RMIConnectorC A ADMC0026I: RMI Connector available at port 2809
[2/21/08 0:40:48:172 IST] 329af89b WsServer A WSVR0002I: Server server1 open for e-business, problems occurred during startup

Hi,
First you receive the functional Spec or technical spec from the onsite.
If it is a Technical spec it is easy for the developer to write code.
But in the case of a Functional spec , take the help of a Fun guy and prepare the tech spec first then start coding.
After preparing the tech spec, it has to be reviewed along with your PL, Testing person.
then clarify the doubt's/logic if any and start the coding.
Once the coding is over, then it has to be tested/checked by a Senior of your team and if any mistakes are there he will tell you and you will correct them, it is called Code walk through.
Then You prepare a Unit testing Doc (UTD) for that with some test cases.
After that give that object to testing people, they will test it based on their rules and conditions and once it is over, they will send it to quality and the object is delivered to client from quality.
reward if useful
regards,
ANJI

PI unable to connect via JMS adapter to Weblogic

Hello All,
We have implemented JMS adapter on PI 7.11 for the first time in our landscape which connects to Weblogic server. When i test my scenario i get this Error on JMS Communication Channel. Could some one help me out .. where things are going wrong?
Am using Transport protocol as : Access JMS Provider with JNDI
CASE 1 :
284272 A channel error occurred. The detailed error (if any) : com.sap.aii.adapter.jms.api.connector.ConnectorException: Error creating initial context with
environment: {java.naming.provider.url=t3s://usdatlpc64m----
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory}for profile: ConnectionProfile of channel: JMS_RCV_IA_WorkOrderStatuson node: 28427250 having object id: 035dd91446303f17bf0e7ad9a4dbd564: RuntimeException: Exception occurred while reading the license file. at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createInitialContext(JndiConnectorImpl.java:65) ...
CASE2:
A channel error occurred. The detailed error (if any) : com.sap.aii.adapter.jms.api.connector.ConnectorException: Error creating initial context with environment: {java.naming.provider.url=----
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory}for profile: ConnectionProfile of channel: JMS_RCV_IA_WorkOrderStatuson node: 28427251 having object id: 035dd91446303f17bf0e7ad9a4dbd564: javax.naming.NamingException: String index out of range: -1 at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createInitialContext(JndiConnectorImpl.java:65) ...

Hi ,
Were you able to resolve the issue?
We are facing similar issue when trying to integrate (SOAP over JMS) with WebSphere 7.x server to read JMS messages. We are using SAP PI 7.1 version and after providing the JNDI connection factory as "com.ibm.websphere.naming.WsnInitialContextFactory".....the error returned is :
======
Channel error occurred. Detailed error (if any) : com.sap.aii.adapter.jms.api.connector.ConnectorException: Error creating initial context with environment: {java.naming.provider.url=iiop://10.60.5.115:2809, java.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory, java.naming.security.principal=admin, java.naming.security.credentials=admin}for profile: ConnectionProfile of channel: JMSSender_MESon node: 8649950 having object id: a8c808c859f33b40a41d0ced2088fb18: javax.naming.NoInitialContextException: Cannot instantiate class: com.ibm.websphere.naming.WsnInitialContextFactory at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createInitialContext(JndiConnectorImpl.java:65) ...
=====
Thanks in Advance
-Naveen

Best way to implement a shared Blocking Queue?

What's the best way to implement a shared Blocking Queue that multiple JVMs can enqueue objects in and multiple JVM's can dequeue from simultaneously?
Also, I see references on the web to com.tangosol.coherence.component.util.queue.ConcurrentQueue but I don't see it in the current API docs...
Thanks

Hi snidely_whiplash,
snidely_whiplash wrote:
What's the best way to implement a shared Blocking Queue that multiple JVMs can enqueue objects in and multiple JVM's can dequeue from simultaneously?
Also, I see references on the web to com.tangosol.coherence.component.util.queue.ConcurrentQueue but I don't see it in the current API docs...
ThanksThat class is an internal class, AFAIK.
As for implementing a queue, you might want to look at Ashish Srivastava's ezMQ component for some ideas:
http://ezsaid.blogspot.com/2009/01/implementing-jms-queue-on-top-of-oracle.html
Best regards,
Robert

Messages could not persist in jms Topic

Hi,
I implement JMS Topic in a SOA project in a cluster (two nodes) environment.
The problem is,
1. The jms topic service executes twice (because of 2 nodes in my cluster) and the message is also replicates but shows as a single message.
To overcome the above issue, I use "singleton" property in composite as well as EM console.
Then above problem has been resolved but creates below issue.
2. The issue is, in my case 2 servers in my cluster, if first server comes first to running state and jms Topic produces messages to first server.. then messages
persists pretty good.
But if first server comes first to running state and jms Topic produces messages on to 2nd server then messages are deleted immediately when they produced.
and vice-versa for 2nd server comes first to running state.
Friends, please help me on this.
Regards,
Venkat
Edited by: Pasagad on Mar 20, 2013 6:11 AM

What type of topic have you created ? Try not to create a distributed topic instead create topics for each managed server with same local jndi name.
see this blog: http://soa-street.blogspot.com/2010/08/subscribing-to-distributed-topic-within.html

Can JMS topics and queues be clustered in a WLS 7.0 Cluster?

We are installing a weblogic 7.0 cluster with 1 admin server and 2 managed
 node servers. Two nodes have been clustered. We are at the point where we
 need to configure JMS. Has any one implemented JMS in WLS 7 clustered
 environment? What are the things to watch out when clustering JMS? Can JMS
 topics and queues be clustered?
 TIA for any helpful hints and comments.
 Regards


"Karim Ali" <[email protected]> wrote:
 >> Has any one implemented JMS in WLS 7 clustered
 >> environment?
 I'm currently working on a project with WLS 7 here at work, involving
 the implementation of BEA's JMS Cluster. So far, I really haven't had
 many hiccups.
 "Karim Ali" <[email protected]> wrote:
 >> What are the things to watch out when clustering JMS?
 At least in WLS 7, the biggest thing that stands out is the lack of
 automatic failover. Also, Message Paging -- make sure you configure
 paging high/low thresholds. Or, if you don't wish for it to occur but
 can't stop the server (very common these days with SLAs), set that
 byte/message high threshold to a very large number (correct me if I'm
 wrong, but I believe BEA recommends 2^63 -1).
 "Karim Ali" <[email protected]> wrote:
 >> Can JMS topics and queues be clustered?
 Well, since Topics and Queues are extensions of the
 javax.jms.Destination interface, the answer is: Yes!
 (SIDE NOTE: most people usually refer to them as a [JMS] "destination"
 -- it avoids a lot of conceptual baggage and plus, less typing!)
 You'll probably want to see this section of BEA's e-docs:
 http://edocs.bea.com/wls/docs70/adminguide/jms.html#config_distributed_destinations
 later,
 Brian J. Mitchell
 BEA Systems Administrator
 TRX
 Atlanta, GA
 email: [email protected]
 office: 404-327-7238
 mobile: 678-283-6530

TransactionRolledbackLocalException in JMS Embedded Messaging...

We"re using two Message Driven Beans (say MDB1 and MDB2) and two EJBs (say EJB1 and EJB2) in a module in our project to implement JMS Embedded messaging on WAS5.1 (using WSAD5.1.2 environment)
The MDB2"s onMessage() listens to a queue written by EJB1 and MDB1"s onMessage() also listens to a queue written by EJB1.
Flow:-
EJB1 starts first and writes a queue to the MDB2, which asynchronously invokes the EJB2 and this EJB2, after calls to a few utility classes invokes EJB1. Then, EJB1, with the Vector input from EJB2 writes a queue to be captured by MDB1.
The first flow of EJB1 --> MDB2 works fine, but the second part (EJB1 --> MDB1) is failing and the MDB2 is also getting shut down because of this. The cause of this is a javax.ejb.TransactionRolledbackLocalException: ; nested exception is: com.ibm.ws.exception.WsEJBException
Can someone who"s already faced such a challege kindly help?
This is the stack trace:- (for sake of clarity, MSSPriceChangeAlertMDB in the below trace is the MDB2)
[8/9/05 19:55:11:951 EDT] 234d1b6e RegisteredRes E WTRN0063E: An illegal attempt to commit a one phase capable resource with existing two phase capable resources has occurred.
[8/9/05 19:55:14:467 EDT] 2a50db6e JMSExceptionL E WMSG0018E: Error on JMSConnection for MDB MSSPriceChangeAlertMDB , JMSDestination jms/MarketDataQueue : javax.jms.JMSException: MQJMS1016: an internal error has occurred. Please contact your system administrator. Detail: {0}
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:540)
at com.ibm.mq.jms.MQQueueAgentThread.run(MQQueueAgentThread.java:1583)
at java.lang.Thread.run(Thread.java:568)
---- Begin backtrace for Nested Throwables
java.lang.NullPointerException
at com.ibm.mq.jms.MQQueueAgentThread.processMessage(MQQueueAgentThread.java:368)
at com.ibm.mq.jms.MQQueueAgentThread.run(MQQueueAgentThread.java:1557)
at java.lang.Thread.run(Thread.java:568)
[8/9/05 19:55:14:576 EDT] 2a50db6e JMSExceptionL E WMSG0057E: Error on JMSConnection for MDB MSSPriceChangeAlertMDB , JMSDestination jms/MarketDataQueue , JMS Linked Exception : java.lang.NullPointerException
at com.ibm.mq.jms.MQQueueAgentThread.processMessage(MQQueueAgentThread.java:368)
at com.ibm.mq.jms.MQQueueAgentThread.run(MQQueueAgentThread.java:1557)
at java.lang.Thread.run(Thread.java:568)
[8/9/05 19:55:14:654 EDT] 2a50db6e MDBListenerIm I WMSG0043I: MDB Listener MarketDataAlertListener stopped for JMSDestination jms/MarketDataQueue
[8/9/05 19:55:14:982 EDT] 234d1b6e ServerSession W WMSG0031E: Exception processing JMS Message for MDB MSSPriceChangeAlertMDB, JMSDestination jms/MarketDataQueue : javax.ejb.TransactionRolledbackLocalException: ; nested exception is: com.ibm.ws.exception.WsEJBException
com.ibm.ws.exception.WsEJBException
at com.ibm.ejs.container.LocalExceptionMappingStrategy.mapException(LocalExceptionMappingStrategy.java:159)
at com.ibm.ejs.container.LocalExceptionMappingStrategy.mapCSITransactionRolledBackException(LocalExceptionMappingStrategy.java:293)
at com.ibm.ejs.container.EJSContainer.postInvoke(EJSContainer.java:3128)
at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:102)
at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:127)
at com.ibm.ejs.jms.listener.ServerSession.run(ServerSession.java:372)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:672)
javax.ejb.TransactionRolledbackLocalException: ; nested exception is: com.ibm.ws.exception.WsEJBException
at com.ibm.ejs.container.LocalExceptionMappingStrategy.mapCSIException(LocalExceptionMappingStrategy.java:96)
at com.ibm.ejs.container.LocalExceptionMappingStrategy.mapException(LocalExceptionMappingStrategy.java:165)
at com.ibm.ejs.container.LocalExceptionMappingStrategy.mapCSITransactionRolledBackException(LocalExceptionMappingStrategy.java:293)
at com.ibm.ejs.container.EJSContainer.postInvoke(EJSContainer.java:3128)
at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:102)
at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:127)
at com.ibm.ejs.jms.listener.ServerSession.run(ServerSession.java:372)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:672)
Thanks a ton in advance!

hi
I am using two MDb nad about 5 Ejb's..thw transaction attribute for the MDB are set to Required..and for the EjB it is set to Not Supported.Moreover i am using a CLi datasource...but i am getting this error:::::
ServerSession W WMSG0031E: Exception processing JMS Message for MDB AggregatedMT598PosnSwiftReader, JMSDestination jms/accounting/ACCT.MT598_535.CORR.OUT.QUEUE : javax.ejb.TransactionRolledbackLocalException: ; nested exception is: com.ibm.ws.exception.WsEJBException
com.ibm.ws.exception.WsEJBException
 at com.ibm.ejs.container.LocalExceptionMappingStrategy.mapException(LocalExceptionMappingStrategy.java:159)
 at com.ibm.ejs.container.LocalExceptionMappingStrategy.mapCSITransactionRolledBackException(LocalExceptionMappingStrategy.java:293)
 at com.ibm.ejs.container.EJSContainer.postInvoke(EJSContainer.java:3159)
 at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:102)
 at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:127)
 at com.ibm.ejs.jms.listener.ServerSession.run(ServerSession.java:375)
 at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:936)
javax.ejb.TransactionRolledbackLocalException: ; nested exception is: com.ibm.ws.exception.WsEJBException
 at com.ibm.ejs.container.LocalExceptionMappingStrategy.mapCSIException(LocalExceptionMappingStrategy.java:96)
 at com.ibm.ejs.container.LocalExceptionMappingStrategy.mapException(LocalExceptionMappingStrategy.java:165)
 at com.ibm.ejs.container.LocalExceptionMappingStrategy.mapCSITransactionRolledBackException(LocalExceptionMappingStrategy.java:293)
 at com.ibm.ejs.container.EJSContainer.postInvoke(EJSContainer.java:3159)
 at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:102)
 at com.ibm.ejs.container.MDBWrapper.onMessage(MDBWrapper.java:127)
 at com.ibm.ejs.jms.listener.ServerSession.run(ServerSession.java:375)
 at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:936)
PLz help..its kind of urgent

JMS .jar files

Hi All,
We are working on XI interfaces implementation. As part of our project, we have to implement JMS to receive messages from an external server.
What are the .jar files that need to be deployed in XI to enable JMS communication?
Where can we find these .jar files? and Is there any documentation explaining a sample JMS communication scenario in XI?
Thank you,
Regards,
Balaji.M

Hi Balaji -
As far as JMS providers are concerned, WebSphereMQ, Sonic MQ, and SAP JMS are well supported by SAP. Outside of these, the current official stance is that the JMS provider must be compatible with the JMS 1.02b or 1.1 specification.
Part of the problem is that there are a large number of 3rd party JMS providers out there from different vendors (with different versions) and it is unreasonable/unmanagable to maintain support for all of them, especially if providers deviate or do not comply to the specifications. Even so I know of customers who have successfully implemented JMS integration with other major JMS providers like Tibco and BEA. But I know of another case, for example, where SSL connectivity was required for Tibco integration and it was not supportable (at that time at least).
Depending on the JMS provider being used, you may run into varying degrees of issues during integration and, unfortunately, varying degrees of support SAP can provide. So if you have the option, stick with the well supported JMS providers I listed initially. If the JMS provider in your landscape is not one of these, I'd recommend creating a SAP customer message to find out whether your particular JMS provider can be supported before going forward with it in your interface design.
BTW, the guide <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3867a582-0401-0010-6cbf-9644e49f1a10">How to Install and Configure External Drivers for JDBC & JMS</a> gives you the specifics on how to deploy the JMS drivers.
Regards,
Jin

Best way to implement a docking container

Hi everyone,
I need to create a docking container that behaves the same way the draggable panel system works in Flex Builder (Eclipse):
- Dock other containers to the edges
- Automatically layout other containers when the dragged container is docked into/out of an edge
Is there a custom control that would enable me to do this? If not, what's the best approach to create one?
Thanks,
Amir

Hi snidely_whiplash,
snidely_whiplash wrote:
What's the best way to implement a shared Blocking Queue that multiple JVMs can enqueue objects in and multiple JVM's can dequeue from simultaneously?
Also, I see references on the web to com.tangosol.coherence.component.util.queue.ConcurrentQueue but I don't see it in the current API docs...
ThanksThat class is an internal class, AFAIK.
As for implementing a queue, you might want to look at Ashish Srivastava's ezMQ component for some ideas:
http://ezsaid.blogspot.com/2009/01/implementing-jms-queue-on-top-of-oracle.html
Best regards,
Robert

JMS custom headers in Oracle SOA suite 11g

Hi,
Can any body expalin me how to implement JMS custom headers in Oracle SOA suite.Please help
Thanks,
Kumar

Kumar,
It is jca.jms.JMSProperty which is used to set and get custom JMS headers. So if you want to set two custom JMS headers say Test1 and Test2 then add them as a property in your invoke action as below -
<invoke name="InvokeTest"
inputVariable="InvokeTest_Produce_Message_InputVariable"
partnerLink="test" portType="ns2:Produce_Message_ptt"
operation="Produce_Message" bpelx:invokeAsDetail="no">
<bpelx:inputProperty name="jca.jms.JMSProperty.Test1" variable="testA"/>
<bpelx:inputProperty name="jca.jms.JMSProperty.Test2" expression="'foo'"/>
</invoke>
Here we have assigned value of variable testA into custom JMS header Test1 and expression "foo" into custom JMS header Test2.
Regards,
Anuj

JMS Version in Weblogic 6.1

Hi all,
Can any body tell me which version of JMS API is included with Weblogic
Server 6.1 Windows2000/NT download ?
Thanks in advance
Bhavin Raichura

HI
Weblogic 6.1 implements JMS specification 1.0.2
regards
Sasikanth
"Weblogic" <[email protected]> wrote:
Hi all,
Can any body tell me which version of JMS API is included with Weblogic
Server 6.1 Windows2000/NT download ?
Thanks in advance
Bhavin Raichura

Implementing JMS Brigde

Similar Messages

Maybe you are looking for