NoInitialContextException in jms

i wrote a simple jms program for point to point Destination
i am able to run the program in j2ee 1.3
but i get problem with j2ee 1.4
here is my program
import javax.jms.*;
import javax.naming.*;
class test
     public static void main(String arg[])
          try {
               Context ctx = new InitialContext();
               QueueConnectionFactory  connectionFactory = (QueueConnectionFactory)ctx.lookup("QueueConnectionFactory");
               Queue myDest = (Queue) ctx.lookup("MyQueue");
               QueueConnection connection = connectionFactory.createQueueConnection();               
               QueueSession session = connection.createQueueSession(false, Session.AUTO_ACKNOWLEDGE);
               QueueSender producer = session.createSender(myDest);
               TextMessage message = session.createTextMessage();
               message.setText("Message");
               producer.send(message);          
               connection.close();
          } catch (NamingException e) {               
               e.printStackTrace();
          } catch (JMSException e) {               
               e.printStackTrace();
}& i got following error
javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file:  java.naming.factory.initial
     at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
     at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
     at javax.naming.InitialContext.getURLOrDefaultInitCtx(Unknown Source)
     at javax.naming.InitialContext.lookup(Unknown Source)
     at test.main(test.java:9)i have created QueueConnectionFactory in admin console
& even i tried as jms/QueueConnectionFactory but i am getting same error. what is the reason for this plz give me solutions
Thanks in advance

i need it urgently anybody could send me solution please.

Similar Messages

  • Error :- while accessing JMS topic messages in Design Studio

    Hi,
    Am getting this error while clicking update button in Design Studio to populate a dataobject using JMS Topic messages sent by oracle Bpel manager.
    IMessageSourceReceiver->messageReceive: javax.naming.NoInitialContextException: Cannot instantiate class: oracle.j2ee.rmi.RMIInitialContextFactory. Root exception is java.lang.ClassNotFoundException: oracle.j2ee.rmi.RMIInitialContextFactory
    Can you tell me where to find the class and how to use it to resolve the problem?
    P.S:-
    If you can provide any document how oracle BPEL process manager use JMS topic to send message to Oracle BAM and display in reports.
    Thanks in advance
    Cheers,
    Praveen G
    iSOFT R& D Pvt Ltd.
    [email protected]

    Hi,
    We are using BAM 10.1.3 against BPEL 10.1.2 and we cannot get it to work.
    We are also getting the error "javax.naming.NoInitialContextException: Cannot instantiate class: oracle.j2ee.rmi.RMIInitialContextFactory...." .
    Our startup paramters for Enterprise Source “Oracle (AS JMS and OJMS) looks like this:
    JMS*".;C:\OracleBAM\OC4J\j2ee\home\lib\jms.jar;C:\OracleBAM\OC4J\j2ee\home\lib\jndi.jar;C:\OracleBAM\OC4J\j2ee\home\oc4j.jar;C:\OracleBAM\OC4J\j2ee\home\oc4jclient.jar;C:\OracleBAM\OC4J\j2ee\home\lib\oc4j-internal.jar;C:\OracleBAM\OC4J\j2ee\home\lib\ejb.jar;C:\OracleBAM\OC4J\j2ee\home\lib\servlet.jar;C:\OracleBAM\OC4J\j2ee\home\lib\jta.jar;C:\OracleBAM\OC4J\j2ee\home\lib\jms.jar;C:\OracleBAM\OC4J\j2ee\home\lib\javax88.jar;C:\OracleBAM\OC4J\j2ee\home\lib\javax77.jar;C:\OracleBAM\OC4J\j2ee\home\lib\jmxri.jar;C:\OracleBAM\OC4J\j2ee\home\lib\jmx_remote_api.jar;C:\OracleBAM\OC4J\j2ee\home\lib\adminclient.jar;C:\OracleBAM\OC4J\j2ee\home\ojspc.jar;C:\OracleBAM\OC4J\j2ee\home\jazn.jar;C:\OracleBAM\OC4J\opmn\lib\optic.jar;C:\OracleBAM\OC4J\rdbms\jlib\aqapi.jar;"".;c:\TIBCO\JMS\clients\java\tibjms.jar;c:\TIBCO\JMS\clients\java\jms.jar;c:\TIBCO\JMS\clients\java\jndi.jar;c:\TIBCO\JMS\clients\java\jta-spec1_0_1.jar;c:\TIBCO\JMS\clients\java\jcert.jar;c:\TIBCO\JMS\clients\java\jnet.jar;c:\TIBCO\JMS\clients\java\jsse.jar;c:\TIBCO\JMS\clients\java\tibcrypt.jar;"".;C:\Program Files\IBM\WebSphere MQ\Java\lib\com.ibm.mq.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\com.ibm.mqjms.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\connector.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\jms.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\jndi.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\jta.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\providerutil.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\fscontext.jar;C:\Program Files\IBM\WebSphere MQ\Java\lib\ldap.jar;"".;C:\Program Files\SonicSoftware\SonicMQ\lib\sonic_Client.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\gnu-regexp-1.0.6.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\jaxp.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\xerces.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\tools.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\providerutil.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\fscontext.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\sslj.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\jsafe.jar;C:\Program Files\SonicSoftware\SonicMQ\lib\certj.jar;"".;C:\bea\weblogic700\server\lib\weblogic.jar;"".;C:\eGate\client\classes\stcjms.jar;C:\eGate\client\JRE\1.3\lib\ext\fscontext.jar;C:\eGate\client\JRE\1.3\lib\ext\providerutil.jar;C:\eGate\client\ThirdParty\sun\jms.jar;C:\eGate\client\ThirdParty\sun\jndi.jar;C:\eGate\client\ThirdParty\sun\jta.jar;"".;C:\JNDI-Directory_WebMethods\fscontext.jar;C:\JNDI-Directory_WebMethods\providerutil.jar;C:\JNDI-Directory_WebMethods\javax.jms.jar;C:\Program Files\webMethods6\Broker\lib\BrokerJMS60.jar;C:\Program Files\webMethods6\common\lib\client60.jar;C:\Program Files\webMethods6\Broker\lib\xerces.jar;"
    We are trying to get to our oc4j container on our BPEL server. We have the following settings on our created message sourcein BAM architect:
    Initial Context Factory: oracle.j2ee.rmi.RMIInitialContextFactory
    JNDI Service Provider URL: opmn:ormi://hostname:6003:OC4J_BPEL
    TopicConnectionFactory Name: java:comp/resource/ojms_ipl/TopicConnectionFactories/iplerror
    Topic Name: java:comp/resource/ojms_ipl/Topics/iplerror
    ojms_ipl refers to the datasource on our BPEL server that is defined in application.xml.
    Where is the class located?
    Best regards

  • ORABPEL-12141 JMS Adapter

    BPEL 10.1.2.0.2 Deployed on OAS on Linux OS.
    Trying to use a BPEL Process which is trying to Connect to JMS on Weblogic Server but getting error as below in the domain.log
    Added the weblogic.jar in the application.xml under integration/orabpel/system/appserver/oc4j/j2ee/home/config/application.xml
    Entry added : <library path="/home/bpel/weblogic/server/lib/weblogic.jar"/>
    XML file entry for JMS Adapter in BPEL :-
    <connector-factory location="eis/jms/topic/rdh/Notification" connector-name="Jms Adapter">
    <config-property name="connectionFactoryLocation" value="oracle.enterprise.crm.rdh.jms.connection.factory"/>
    <config-property name="factoryProperties" value="java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://MYMACHINE:7050"/>
    <config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
    <config-property name="isTopic" value="true"/>
    <config-property name="isTransacted" value="false"/>
    <config-property name="username" value=""/>
    <config-property name="password" value=""/>
    </connector-factory>
    Portion of Domain.log file :-
    <2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: JNDI Naming exception when looking up oracle.enterprise.crm.rdh.jms.connection.factory: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory
    <2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: Will now try to determine if the 'ConnectionFactoryLocation' oracle.enterprise.crm.rdh.jms.connection.factory is a loadable Java class. If so, the above exception can be ignored.
    <2007-08-17 03:25:29,148> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> Error while creating managed connection:
    <2007-08-17 03:25:29,150> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound>
    ORABPEL-12141
    ERRJMS_CONN_FAC_NOT_FOUND.
    Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor oracle.enterprise.crm.rdh.jms.connection.factory neither through JNDI nor instantiate it as a Java class
    Please examine the log file to determine the problem.
    at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:206)
    at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getTopicConnectionFactory(JMSConnectionFactoryFactory.java:109)
    at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:123)
    at oracle.tip.adapter.jms.JMS.JMSConnection.<init>(JMSConnection.java:107)
    at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:365)
    at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createDefaultConnection(JmsManagedConnectionFactory.java:356)
    at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:319)
    at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:101)
    at oracle.tip.adapter.jms.JmsDefaultConnectionManager.allocateConnection(JmsDefaultConnectionManager.java:76)
    at oracle.tip.adapter.jms.JmsConnectionFactory.getConnection(JmsConnectionFactory.java:94)
    at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:201)
    at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:158)
    at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:115)
    at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:113)
    at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
    at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:267)
    at java.lang.Thread.run(Thread.java:534)
    Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:652)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
    at javax.naming.InitialContext.init(InitialContext.java:219)
    at javax.naming.InitialContext.<init>(InitialContext.java:195)
    at oracle.tip.adapter.jms.JMS.JMSFactory.getInitialContext(JMSFactory.java:186)
    at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:133)
    ... 16 more
    Caused by: java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
    at com.evermind.naming.ContextClassLoader.findClass(ContextClassLoader.java:318)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
    at com.evermind.naming.ContextClassLoader.loadClass(ContextClassLoader.java:143)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:219)
    at com.evermind.server.ApplicationContextClassLoader.findClass(ApplicationContextClassLoader.java:19)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:219)
    at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:42)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:649)
    ... 21 more

    BPEL 10.1.2.0.2 Deployed on OAS on Linux OS.
    Trying to use a BPEL Process which is trying to Connect to JMS on Weblogic Server but getting error as below in the domain.log
    Added the weblogic.jar in the application.xml under integration/orabpel/system/appserver/oc4j/j2ee/home/config/application.xml
    Entry added : <library path="/home/bpel/weblogic/server/lib/weblogic.jar"/>
    XML file entry for JMS Adapter in BPEL :-
    <connector-factory location="eis/jms/topic/rdh/Notification" connector-name="Jms Adapter">
    <config-property name="connectionFactoryLocation" value="oracle.enterprise.crm.rdh.jms.connection.factory"/>
    <config-property name="factoryProperties" value="java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory;java.naming.provider.url=t3://MYMACHINE:7050"/>
    <config-property name="acknowledgeMode" value="AUTO_ACKNOWLEDGE"/>
    <config-property name="isTopic" value="true"/>
    <config-property name="isTransacted" value="false"/>
    <config-property name="username" value=""/>
    <config-property name="password" value=""/>
    </connector-factory>
    Portion of Domain.log file :-
    <2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: JNDI Naming exception when looking up oracle.enterprise.crm.rdh.jms.connection.factory: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory
    <2007-08-17 03:25:29,146> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> JMSConnectionFactoryFactory_getConnectionFactory: Will now try to determine if the 'ConnectionFactoryLocation' oracle.enterprise.crm.rdh.jms.connection.factory is a loadable Java class. If so, the above exception can be ignored.
    <2007-08-17 03:25:29,148> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound> Error while creating managed connection:
    <2007-08-17 03:25:29,150> <DEBUG> <CDH.collaxa.cube.activation> <JMSAdapter::Inbound>
    ORABPEL-12141
    ERRJMS_CONN_FAC_NOT_FOUND.
    Unable to instantiate connection factory. JMS adapter was unable to look up the connection factor oracle.enterprise.crm.rdh.jms.connection.factory neither through JNDI nor instantiate it as a Java class
    Please examine the log file to determine the problem.
    at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:206)
    at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getTopicConnectionFactory(JMSConnectionFactoryFactory.java:109)
    at oracle.tip.adapter.jms.JMS.JMSConnection.init(JMSConnection.java:123)
    at oracle.tip.adapter.jms.JMS.JMSConnection.<init>(JMSConnection.java:107)
    at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:365)
    at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createDefaultConnection(JmsManagedConnectionFactory.java:356)
    at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createConnection(JmsManagedConnectionFactory.java:319)
    at oracle.tip.adapter.jms.JmsManagedConnectionFactory.createManagedConnection(JmsManagedConnectionFactory.java:101)
    at oracle.tip.adapter.jms.JmsDefaultConnectionManager.allocateConnection(JmsDefaultConnectionManager.java:76)
    at oracle.tip.adapter.jms.JmsConnectionFactory.getConnection(JmsConnectionFactory.java:94)
    at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.createConsumer(JMSMessageConsumer.java:201)
    at oracle.tip.adapter.jms.JMS.JMSMessageConsumer.init(JMSMessageConsumer.java:158)
    at oracle.tip.adapter.jms.inbound.JmsConsumer.init(JmsConsumer.java:115)
    at oracle.tip.adapter.jms.JmsEndpoint.run(JmsEndpoint.java:113)
    at oracle.tip.adapter.fw.jca.work.WorkerJob.go(WorkerJob.java:51)
    at oracle.tip.adapter.fw.common.ThreadPool.run(ThreadPool.java:267)
    at java.lang.Thread.run(Thread.java:534)
    Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory]
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:652)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
    at javax.naming.InitialContext.init(InitialContext.java:219)
    at javax.naming.InitialContext.<init>(InitialContext.java:195)
    at oracle.tip.adapter.jms.JMS.JMSFactory.getInitialContext(JMSFactory.java:186)
    at oracle.tip.adapter.jms.JMS.JMSConnectionFactoryFactory.getConnectionFactory(JMSConnectionFactoryFactory.java:133)
    ... 16 more
    Caused by: java.lang.ClassNotFoundException: weblogic.jndi.WLInitialContextFactory
    at com.evermind.naming.ContextClassLoader.findClass(ContextClassLoader.java:318)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
    at com.evermind.naming.ContextClassLoader.loadClass(ContextClassLoader.java:143)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:219)
    at com.evermind.server.ApplicationContextClassLoader.findClass(ApplicationContextClassLoader.java:19)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:219)
    at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:42)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:649)
    ... 21 more

  • Jar files for jms websphere

    Hello Experts,
    We are trying to establish connection between PI and webshpere ,for that we are using JMS adapter.
    And in the channel we are getting the error as:
    Error connecting due to missing class: com.ibm.websphere.naming.WsnInitialContextFactory. Ensure that all resources required are present in the JMS provider library: com.sap.aii.adapter.lib.sda
    Can anyone please provide me the required jar files or the path from where i can download the .jar files required for this purpose.
    Regards
    Naveen

    Hi,
    Thanks for your reply ,i have installed 2 jar files:
    naming .jar and
    javax.j2ee.connector.jar.
    But still geting the error as :
    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://xyz, java.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory, java.naming.security.principal=xyz, java.naming.security.credentials=xyz}for profile: ConnectionProfile of channel: JMSSender_MESon node: xyz having object id: xyz: javax.naming.NoInitialContextException: Cannot instantiate class: com.ibm.websphere.naming.WsnInitialContextFactory<br> at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createInitialContext(JndiConnectorImpl.java:65)<br> ...
    Urgent help required..
    Thanks

  • Exception in thread "main" javax.naming.NoInitialContextException: Need to

    Hey,
    I am exploring the technique 'JMS'. I found an sample code on the Internet (https://www.redhat.gl/docs/manuals/jboss/jboss-eap-4.2/doc/Server_Configuration_Guide/JMS_Examples-A_Point_To_Point_Example.html).
    But unfortunately, by running the code on my local computer, I got an NoInitialContextException (Exception in thread "main" javax.naming.NoInitialContextException: Need to ...Application resource file: java.naming.factory.initial). After searching on the Internet, I discovered I need to configure some JNDI values. But, also after passing on the variables to the class by parameter (-Djava.naming.factory.initial=com.sun.enterprise.naming.SerialInitContextFactory), I still get the same error.
    What have I forgotten? Hope someone can help. Thanks!
    Tongue78.
    public void setupPTP()
    throws JMSException,
    NamingException
    InitialContext iniCtx = new InitialContext();
    Object tmp = iniCtx.lookup("ConnectionFactory"); // exception occurs here..
    QueueConnectionFactory qcf = (QueueConnectionFactory) tmp;
    conn = qcf.createQueueConnection();
    que = (Queue) iniCtx.lookup("queue/testQueue");
    session = conn.createQueueSession(false,
    QueueSession.AUTO_ACKNOWLEDGE);
    conn.start();
    ....

    Refer to the Sun App Server documentation.
    http://docs.sun.com/source/819-0079/dgacc.htmlIt lists down the steps you need to follow.

  • Error in JMS receiver adapter: "Error creating initial context with environment"

    Hello,
    I have some trouble with a JMS receiver adapter (access to JMS-provider with JNDI).
    The message in adapter monitoring is:
    A channel error occurred. Detailed error (if any) :
    com.sap.aii.adapter.jms.api.connector.ConnectorException: Fatal Error looking up connection factoryJMSQueueConnectionFactory, for profile: ConnectionProfile of channel: CC_JMS_RCV_XLIMI00001on node: 503473150 having object id: 5b424f2f79b6350ca636ab35d528cfdd:
    ConnectorException: Error creating initial context with environment: java.naming.provider.url=wcsefdev.example.com:9064; java.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory; for profile: ConnectionProfile of channel:
    CC_JMS_RCV_XLIMI00001on node: 503473150 having object id: 5b424f2f79b6350ca636ab35d528cfdd: javax.naming.NoInitialContextException:
    Cannot instantiate class: com.ibm.websphere.naming.WsnInitialContextFactory<br> at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createConnectionFactory
    (JndiConnectorImpl.java:152)<br> ....
    Message processing failed. Cause:
    com.sap.aii.adapter.jms.core.fsm.DFA$InvalidTransitionException: No transition found from state: ERROR, on event: process_commence for DFA: CC_JMS_RCV_XLIMI00001:5b424f2f79b6350ca636ab35d528cfdd
    The third party assured me that the specified JNDI parameters are right and everything is configured on their site, so it should work...
    Might there be a problem with the JMS drivers?
    Regards,
    Marcus

    Hi Marcus,
    Have a look at below thread
    Connecting to PI 7.11 JMS Queue from other PI 7.11 Server

  • Stand-Alone JMS SAF Client

    Im interested in using a WL Stand-Alone JMS SAF Client to send messages to a server-side JMS destination,
              regardless of the servers availability.
              This is for a J2SE Swing Application. There currently is no app server interaction.
              I found the doc http://e-docs.bea.com/wls/docs92/client/saf_client.html
              It describes almost everything except for what the actual client will look like.
              Im stuck after "Modify Your JMS Client Applications.." section.
              Questions:
              A) Suggestions for other docs?
              B) Is anyone using a Stand-Alone JMS SAF Client?
              C) Does anyone know of any code examples?
              The odd thing is that a search on the net for "JMS SAF Client" or variants of yields nothing other than the WL docs...
              Thanks!

    I could not make stand-alone jms saf client work. Followed the doc, created ClientSAF.xml, made the change for intial-context factory. Tried using with provider_url and without it.
              I am not using default queue and connection factory. The client code is working fine when I don't use saf, i.e. "weblogic.jndi.WLInitialContextFactory" and provider_url.
              Getting following error:
              javax.naming.NoInitialContextException: Cannot instantiate class: weblogic.jndi.WLInitialContextFactory [Root exception is java.lang.ClassCastException: weblogic.security.service.SubjectManagerImpl]
                   at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
                   at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
                   at javax.naming.InitialContext.init(Unknown Source)
                   at javax.naming.InitialContext.<init>(Unknown Source)
                   at weblogic.jms.safclient.agent.internal.ClientEnvironmentImpl.getContext(ClientEnvironmentImpl.java:76)
                   at weblogic.jms.forwarder.Forwarder.getInitialContext(Forwarder.java:334)
                   at weblogic.jms.forwarder.Forwarder.reconnect(Forwarder.java:210)
                   at weblogic.jms.forwarder.Forwarder.timerExpired(Forwarder.java:265)
                   at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:259)
                   at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
              Caused by: java.lang.ClassCastException: weblogic.security.service.SubjectManagerImpl
                   at weblogic.corba.client.ClientORBInitializer.initialize(ClientORBInitializer.java:106)
                   at weblogic.jndi.WLInitialContextFactory.<init>(WLInitialContextFactory.java:29)
                   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
                   at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
                   at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
                   at java.lang.reflect.Constructor.newInstance(Unknown Source)
                   at java.lang.Class.newInstance0(Unknown Source)
                   at java.lang.Class.newInstance(Unknown Source)
                   ... 12 more
              java.lang.ClassCastException: weblogic.security.service.SubjectManagerImpl
                   at weblogic.corba.client.ClientORBInitializer.initialize(ClientORBInitializer.java:106)
                   at weblogic.jndi.WLInitialContextFactory.<init>(WLInitialContextFactory.java:29)
                   at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)Stack level 1
                   at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
                   at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
                   at java.lang.reflect.Constructor.newInstance(Unknown Source)
                   at java.lang.Class.newInstance0(Unknown Source)
                   at java.lang.Class.newInstance(Unknown Source)
                   at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
                   at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
                   at javax.naming.InitialContext.init(Unknown Source)
                   at javax.naming.InitialContext.<init>(Unknown Source)
                   at weblogic.jms.safclient.agent.internal.ClientEnvironmentImpl.getContext(ClientEnvironmentImpl.java:76)
                   at weblogic.jms.forwarder.Forwarder.getInitialContext(Forwarder.java:334)
                   at weblogic.jms.forwarder.Forwarder.reconnect(Forwarder.java:210)
                   at weblogic.jms.forwarder.Forwarder.timerExpired(Forwarder.java:265)
                   at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:259)
                   at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
              disconnect stack trace finished
              QUEUE NAME: jmssysmodule-ois!oisQueue

  • 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.<br> at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createInitialContext(JndiConnectorImpl.java:65)<br> ...
    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<br> at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createInitialContext(JndiConnectorImpl.java:65)<br> ...

    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<br> at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createInitialContext(JndiConnectorImpl.java:65)<br> ...
    =====
    Thanks in Advance
    -Naveen

  • Error in JMS

    Hi
    I tried the following code to connect to a JMS server which is running on a remote machine..
    String strConnectionFactory="java:comp/env/jms/sample";
                   String strTopic="java:comp/env/jms/Computer";
                   Hashtable env = new Hashtable();
                   env.put(Context.INITIAL_CONTEXT_FACTORY,"com.sun.jndi.fscontext.RefFSContextFactory");
                   env.put (Context.PROVIDER_URL,"localhost");
                   Context ctx = new InitialContext(env);
                   //get the connection Factory
                   connectionFactory=(TopicConnectionFactory)ctx.lookup(strConnectionFactory);
    I am getting the following exception
    javax.naming.NoInitialContextException: Cannot instantiate class: com.sun.jndi.
    scontext.RefFSContextFactory [Root exception is java.lang.ClassNotFoundExceptio
    : com.sun.jndi.fscontext.RefFSContextFactory]
    Can anybody help me..
    thanks in advance
    hashin

    u said its remote m/c then wats the location of the provider
    looks like u dont have the fscontext.jar in your class path

  • Having problem to run JMS tutorial

    Hi,
    I have successfully compiled and add MyQueue to the queue. But when I try to run the sample program from the JMS tutorial my system would produced the exact error that I have posted bellow:
    =========================================
    F:\ttech\jeti\classes>java -Djms.properties=F:\j2sdkee1.3.1\config\jms_client.pr
    operties SimpleQueueSender MyQueue 3
    Queue name is MyQueue
    JNDI lookup failed: javax.naming.NoInitialContextException: Need to specify clas
    s name in environment or system property, or as an applet parameter, or in an ap
    plication resource file: java.naming.factory.initial
    ====================================
    If some body could please tell me what I am doing wrong here. I have installed all the jar files (like jms.jar, jndi.jar) and j2sdkee1.3.1 and jsdk1.3.1_01 and set up all the classpath accordingly.
    Thank you so much.
    Amir.

    This script should get rid of your troubles:
    Just to lay it all out, here is how to "run" the code.. the compiling is a breeze. So, this is only how to generically get things to run. Specific of *nix, but I'm sure windows users can pick-out the important parts.
    #!/bin/sh
    J2EE_HOME=/usr/local/j2sdkee1.4
    # this assumes your PATH already points to the following:
    # (the j2ee goodies listed below)
    # $J2EE_HOME/lib/j2ee.jar
    # $J2EE_HOME/lib/system/jmsra.jar
    # and of course... the standard java libs.
    #below the ~/code/w3track/jms1.0.2b/src/
    # is the directory where I manually compiled #The jms libraries in...
    # this could instead point to the jms.jar file in the lib directory.
    p=$PATH:$J2EE_HOME/lib/j2ee.jar:$J2EE_HOME/lib/system/jmsra.jar:~/code/w3track/jms1.0.2b/src/:.
    [ "$1" != "" ] && java -server -Djava.endorsed.dirs=$J2EE_HOME/lib/endorsed -classpath $p $1
    # first setup the queue,
    #I'll assume you have started a jms queue by
    #first starting #the j2ee -startRegistry and
    # j2eeadmin -addJmsDestination q1des queue
    #example of running:
    # ./<this_script> "SendToQueue q1des 5"
    #this will send 5 messages into the queue.
    #hope this helps some people out
    #there who are having issues getting the compiled
    #code to run. Good Luck!
    # Chris Danielson

  • NoInitialContextException when I try to lookup my ConnectionFactory

    Hello everyone,
    I'm now working on a small project using JMS, and I have installed the last version of JDK 6 Update 17 With J2EE.
    try{
         Context jndiContext = new InitialContext();
         connectionFactory = (ConnectionFactory)jndiContext.lookup("jms/ConnectionFactory");
         queue = (Queue)jndiContext.lookup("jms/queue");
    }catch(NamingException exc){
         System.err.println("Lookup Object failed");
         exc.printStackTrace();
         System.exit(1);
    ... ... ...When I tried to run the program above, I got a NoInitialContextException at the line : Context jndiContext = new InitialContext() . The full error message is:
    {color:#0000ff}
    javax.naming.NoInitialContextException: Cannot instantiate class: org.exolab.jms
    .jndi.InitialContextFactory [Root exception is java.lang.ClassNotFoundException:
    org.exolab.jms.jndi.InitialContextFactory]
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
    57)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288
    at javax.naming.InitialContext.init(InitialContext.java:223)
    at javax.naming.InitialContext.<init>(InitialContext.java:175)
    at SimpleMessageProducer.main(SimpleMessageProducer.java:49)
    Caused by: java.lang.ClassNotFoundException: org.exolab.jms.jndi.InitialContextF
    actory
    at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
    at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:316)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Class.java:247)
    at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.jav
    a:46)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
    54)
    ... 4 more{color}
    I have created a javax.jms.ConnectionFactory and a javax.jms.Queue in the Glassfish Admin Consle -> Resources -> JMS Resources -> Connection Factories / Destinations Resources, and I have also added the appserv-rt.jar and javaee.jar into CLASSPATH. But my program still doesn't work.
    I have tried to get my connection factory with the annotations @Resource, but it doesn't work either.
    Si I'm "lookup" someone who could debug this program for me,
    Greetings
    Edited by: WeepInSilence on Nov 8, 2009 8:57 AM
    Edited by: WeepInSilence on Nov 8, 2009 11:05 AM

    Hello esiuolyma,
    After reviewing your post, it sounds like the iPod is not recognized and that will not allow you to sync. I would recommend that you read these articles, they may be helpful in troubleshooting your issue.
    iPhone, iPad, or iPod not recognized in iTunes for Windows - Apple Support
    If you don't see your connected device in iTunes for Mac - Apple Support
    Thanks for using Apple Support Communities.
    Have a nice day,
    Mario

  • JMS sample code not working

    Hi,
    I am new to JMS and am trying to learn the technology. When I tried to run the JMS sample codes available at http://www.oracle.com/technology/sample_code/tech/java/jms/index.html, I got the following error:
    [java] javax.naming.NoInitialContextException: Cannot instantiate class: co
    m.evermind.server.rmi.RMIInitialContextFactory [Root exception is java.lang.Clas
    sNotFoundException: com.evermind.server.rmi.RMIInitialContextFactory]
    Please help me solve the problem. I find that, the downloaded code does not contain the class mentioned in the error message. Also, I do not see how the code is interacting with the OC4J server. It would be great if anyone could clarify.

    hi adith,
    the problem you are facing can be removed by adding oc4jclient.jar as libraray.
    But after that i am facing following error.
    Exception in thread "main" java.lang.NoClassDefFoundError: javax/management/j2ee/statistics/JMSEndpointStats
         at com.evermind.server.jms.EvermindSession.createProducer(EvermindSession.java:311)
         at warid.com.jms.JMSProducerConsumer.performMessagingOperations(JMSProducerConsumer.java:80)
         at warid.com.jms.JMSProducerConsumer.main(JMSProducerConsumer.java:42)
    Regards

  • How to use JMS with tomcat and Axis

    Hello
    I'm new in ii, so i'm still a little bit lost. I have been implementing web services with tomcat and Axis. However, these services are synchronous and I would like that some services were asynchronous.
    I've been reading about the topic and I've found that JMS is a good solution for it. I have already downloaded JMS in my computer but now I don't know what else to do. I've been trying to run the SimpleQueueSender.java example but I get the error:
    JNDI API lookup failed: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
    But I have attached all .jar from F:\Sun\MessageQueue\lib
    In addition to this, for my first webservices I used the Java2WSDL, WSDL2Java and AdminClient (axis tool) to create my web services bindings, stubs and skeletons and to deploy the web service on the server. Do I have to use them now with JMS? or now the deployment must be performed in a different way?
    Thank you in advanced,

    The error means that you have to specify the type and location of your jndi store. You could create a jndi.properties file and put two properties in it:
    java.naming.provider.url=file\\\:////var/jndi
    java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory
    for a file based jndi store. Then you have to make sure your jndi.properties file is in your CLASSPATH. Then you have to use something like imqadmin to create your jndi store and store in it your administrative objects like Queues and QueueConnectionFactories.

  • JMS Adapter question

    Hi,
    Is it possible to use a different jndi-factory other than teh default WL one: weblogic.jndi.WLInitialContextFactory?
    also if my jms accepts only client cert ssl authentication, is it possible to setup this in Oracle CEP? I am getting all kinds of errors
    when I try to do any of the above and the documentation seems to layout only default scenarios so not enough details. I am getting this error:
    org.springframework.beans.FatalBeanException: Error in context lifecycle initialization; nested exception is java.lang.Exception: Error initializing JMS connection: javax.naming.NoInitialContextException: The JNDI initial context factory "com.sun.jndi.fscontext.RefFSContextFactory" either cannot be loaded or it does not exist.
    I added all required jar files for this jndi-factory in runtime lib in Manifest.mf but it is not loading at all.
    Anybody tried something similar to this? any pointers?
    Thanks,
    Firas

    Hi Andy,
    I changed it to Debug and got the following stack:
    <Mar 10, 2010 2:53:46 PM EST> <Notice> <Deployment> <BEA-2045000> <The application bundle "mmxHelloWorldd" was deployed successfully to file:/E:/oracle/Middleware/user_projects/domains/ocep_domain/defaultserver/applications/mmxHelloWorldd/mmxHelloWorldd.jar with version 1268250825479>
    <Mar 10, 2010 2:53:50 PM EST> <Debug> <Adapters> <BEA-000000> <InboundJmsAdapter.beforeResume was called>
    <Mar 10, 2010 2:53:50 PM EST> <Debug> <Adapters> <BEA-000000> <JNDI lookup failed for QueueConnectionFactory from provider file://E:/Firas/mmx/jndi/bindings/
    java.lang.ClassCastException: javax.naming.Reference
         at com.bea.wlevs.adapters.jms.JmsAdapter.beforeResume(JmsAdapter.java:109)
         at com.bea.wlevs.adapters.jms.InboundJmsAdapter.beforeResume(InboundJmsAdapter.java:74)
         at com.bea.wlevs.adapters.jms.InboundJmsAdapter$$FastClassByCGLIB$$fc18e7ee.invoke(<generated>)
         at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
         at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:700)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
         at com.bea.wlevs.ede.spi.AbstractStageProxy.invoke(AbstractStageProxy.java:78)
         at com.bea.wlevs.eventstore.recplay.RecordPlayProxy.invoke(RecordPlayProxy.java:255)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at com.bea.wlevs.ede.spi.AbstractStageProxy.invoke(AbstractStageProxy.java:78)
         at com.bea.wlevs.monitor.internal.MonitoringProxy.invoke(MonitoringProxy.java:165)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:635)
         at com.bea.wlevs.adapters.jms.InboundJmsAdapter$$EnhancerByCGLIB$$b6867280.beforeResume(<generated>)
         at com.bea.wlevs.spring.ActivationBeanPostProcessor.preProcessBeforeContextResume(ActivationBeanPostProcessor.java:27)
         at com.bea.wlevs.spring.DeferredBeanPostProcessor.beforeResume(DeferredBeanPostProcessor.java:33)
         at com.bea.wlevs.spring.ApplicationContextLifecycle.onApplicationEvent(ApplicationContextLifecycle.java:114)
         at org.springframework.context.event.SimpleApplicationEventMulticaster$1.run(SimpleApplicationEventMulticaster.java:78)
         at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49)
         at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:76)
         at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:274)
         at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:736)
         at org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext.finishRefresh(AbstractOsgiBundleApplicationContext.java:235)
         at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:358)
         at org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
         at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:320)
         at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:136)
         at org.springframework.scheduling.commonj.DelegatingWork.run(DelegatingWork.java:61)
         at weblogic.work.commonj.CommonjWorkManagerImpl$WorkWithListener.run(CommonjWorkManagerImpl.java:196)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    <Mar 10, 2010 2:53:50 PM EST> <Error> <Deployment> <BEA-2045010> <The application context "mmxHelloWorldd" could not be started: org.springframework.beans.FatalBeanException: Error in context lifecycle initialization; nested exception is java.lang.Exception: JNDI lookup failed for QueueConnectionFactory from provider file://E:/Firas/mmx/jndi/bindings/
    org.springframework.beans.FatalBeanException: Error in context lifecycle initialization; nested exception is java.lang.Exception: JNDI lookup failed for QueueConnectionFactory from provider file://E:/Firas/mmx/jndi/bindings/
         at com.bea.wlevs.spring.ApplicationContextLifecycle.onApplicationEvent(ApplicationContextLifecycle.java:136)
         at org.springframework.context.event.SimpleApplicationEventMulticaster$1.run(SimpleApplicationEventMulticaster.java:78)
         at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49)
         at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:76)
         at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:274)
         at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:736)
         at org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext.finishRefresh(AbstractOsgiBundleApplicationContext.java:235)
         at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:358)
         at org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
         at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:320)
         at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:136)
         at org.springframework.scheduling.commonj.DelegatingWork.run(DelegatingWork.java:61)
         at weblogic.work.commonj.CommonjWorkManagerImpl$WorkWithListener.run(CommonjWorkManagerImpl.java:196)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused By: java.lang.Exception: JNDI lookup failed for QueueConnectionFactory from provider file://E:/Firas/mmx/jndi/bindings/
         at com.bea.wlevs.adapters.jms.JmsAdapter.beforeResume(JmsAdapter.java:120)
         at com.bea.wlevs.adapters.jms.InboundJmsAdapter.beforeResume(InboundJmsAdapter.java:74)
         at com.bea.wlevs.adapters.jms.InboundJmsAdapter$$FastClassByCGLIB$$fc18e7ee.invoke(<generated>)
         at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149)
         at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:700)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
         at com.bea.wlevs.ede.spi.AbstractStageProxy.invoke(AbstractStageProxy.java:78)
         at com.bea.wlevs.eventstore.recplay.RecordPlayProxy.invoke(RecordPlayProxy.java:255)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at com.bea.wlevs.ede.spi.AbstractStageProxy.invoke(AbstractStageProxy.java:78)
         at com.bea.wlevs.monitor.internal.MonitoringProxy.invoke(MonitoringProxy.java:165)
         at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
         at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:635)
         at com.bea.wlevs.adapters.jms.InboundJmsAdapter$$EnhancerByCGLIB$$b6867280.beforeResume(<generated>)
         at com.bea.wlevs.spring.ActivationBeanPostProcessor.preProcessBeforeContextResume(ActivationBeanPostProcessor.java:27)
         at com.bea.wlevs.spring.DeferredBeanPostProcessor.beforeResume(DeferredBeanPostProcessor.java:33)
         at com.bea.wlevs.spring.ApplicationContextLifecycle.onApplicationEvent(ApplicationContextLifecycle.java:114)
         at org.springframework.context.event.SimpleApplicationEventMulticaster$1.run(SimpleApplicationEventMulticaster.java:78)
         at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49)
         at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:76)
         at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:274)
         at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:736)
         at org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext.finishRefresh(AbstractOsgiBundleApplicationContext.java:235)
         at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:358)
         at org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
         at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:320)
         at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:136)
         at org.springframework.scheduling.commonj.DelegatingWork.run(DelegatingWork.java:61)
         at weblogic.work.commonj.CommonjWorkManagerImpl$WorkWithListener.run(CommonjWorkManagerImpl.java:196)
         at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    >
    <Mar 10, 2010 2:53:50 PM EST> <Notice> <Deployment> <BEA-2045001> <The application bundle "mmxHelloWorldd" was undeployed successfully>

  • JMS-MQSeries without J2EE

    Hi,
    I tried to compile the SimpleTopicPublisher and SimpleTopicSubscriber from the following link. I used the javax.jms.jar and the jms.jar from sun.
    http://java.sun.com/products/jms/tutorial/1_3_1-fcs/doc/client.html#1027256
    The code got compiled.
    I had a queue in MQSeries, its sample queue called postcard.
    When I tried running SimplePublisherTopic, the following exception was thrown:
    <code>
    D:\>java SimpleTopicPublisher postcard 1
    Topic name is postcard
    JNDI API lookup failed: javax.naming.NoInitialContextException: Need to specify
    class name in environment or system property, or as an applet parameter, or in a
    n application resource file: java.naming.factory.initial
    javax.naming.NoInitialContextException: Need to specify class name in environmen
    t or system property, or as an applet parameter, or in an application resource f
    ile: java.naming.factory.initial
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
    43)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246
    at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.jav
    a:283)
    at javax.naming.InitialContext.lookup(InitialContext.java:350)
    at SimpleTopicPublisher.main(SimpleTopicPublisher.java:60)
    </code>
    The program is J2EE server independent. The MQSeries for Win 2000 is used for JMS services.
    Please help me in understanding the following :
    1) How to get the JNDI server running and registering our topic there?
    2) There was no reference of 'Topic' in MQSeries. There are only 'Queue'. If this is the case, how to create topics in MQSeries.
    3) Who are providers? There are JNDI provider and IBMMQSeries provider. What is to be used? Can they both be used?
    4) MQSeries has a Java API. Is it a replacement/substitute for Sun JMS API? Which should we use to write a generic JMS code?
    Thanks in advance,
    Rajesh

    I could solve some of the exceptions based on Steve's suggestions. I am giving below on how I solved.
    "JNDI API lookup failed: javax.naming.NoInitialContextException: "
    The SimpleTopicPublisher has set env property for InitialContext and expects our System's properties to specify the provider URL. I have added the property this way in code:
              try {
                   // Identify service provider to use
                   Hashtable env = new Hashtable(11);
                   env.put(Context.INITIAL_CONTEXT_FACTORY,
                                 "com.sun.jndi.fscontext.RefFSContextFactory");
                   env.put(Context.PROVIDER_URL,
                                 "file:/C:/Program Files/IBM/MQSeries/Java/lib");
                   jndiContext = new InitialContext(env);
              } catch (NamingException e) {
                        System.out.println("Could not create JNDI API " +
                             "context: " + e.toString());
                        e.printStackTrace();
                        System.exit(1);
              }1) How to get the JNDI server running and registering our topic there?
    Unlike RMI Naming server/registry, JNDI is a standard API for naming services. Hence it is not designed as a server listening on a port. I understand the File System based name space. The bindings of key-value is maintained in .bindings file in the place you specify as a PROVIDER_URL. Both publisher and subscriber has to refer this name space. This is how you start registering and retrieving MQ objects.
    3) Who are providers? There are JNDI provider and IBMMQSeries provider. What is to be used? Can they both be used?
    Providers are vendors who have implemented javax.naming.Spi package. The default provider you get from Sun is one reference implementation. It is "com.sun.jndi.fscontext.RefFSContextFactory". There is no IBM MQSeries provider. The same "com.sun.jndi.fscontext.RefFSContextFactory" is only supplied with MQSeries also.
    I don't know the answers for questions 2 and 4. I shall post it as soon as I understand.
    Those of you who read this, if you find deviation from righteouness, please correct.
    Thanks/Regards,
    Rajesh

Maybe you are looking for

  • Is it possible to upgrade the CPU or GPU of a Toshiba Notebook?

    Many customers would like to upgrade/replace the CPU (Central Processing Unit) and/or GPU (Graphics Processing Unit) in their mobile systems to gain performance. Toshiba does not support or recommend performing modifications on their mobile systems s

  • Error when running unit tests

    Hi, I'm getting the error 'Marker id <num> not found' about 9 times out of 10 when I try to run unit tests in Flash Builder 4.5 Premium. This is happening on a new (2 weeks old) spark + mx project, with the unit test classes created in Flash Builder

  • Problem starting MemoryAnalyzer in linux

    I am trying to run under Linux, and I have been unable to get it to work.  When I try to run the script (or just run the java command directly), it runs for a second, then exits with no output to stdout or stderr. Commands I've tried: java -Xms512m -

  • Unable to launch InDesign CC

    I have just installed Creative Cloud on my MacBook Pro laptop, which is running Mavericks Version 10.9.2. When I try to launch ID, I get "Error: Unable to launch Adobe InDesign as you do not have sufficient permissions to access the preferences folde

  • UI5 load view from another view

    Hi all, I'm trying to load a view from an external project. The idea being that a view can be used by multiple projects to cater for reuse e.g a view that has different view modes, user role privileges etc. however I can't seem to find a way to find