MQSeries as a Transactional Resource Manager with Weblogic Server

          I am trying to setup the example given in the BEA white paper:
          Using MQSeries as a Transactional Resource Manager with Weblogic Server.
          Version 1.
          October 25, 2001.
          I followed the instructions given in the documents, but when i run client program
          >java MQClient t3://localhost:7001 "MQSeries test"
          I received the following exception below. Does anyone how what is the reason for
          this exception(s) and how i can solve the problem? My MQSeries Server and Weblogic
          6.1 sp2 are installed on seperate NT machines. I installed the MQSeries classes
          for java and the MQSeries classes for Java Message Service on the weblogic
          server machine.
          sending: "MQSEries test"
          Exception in thread "main" java.rmi.ServerError: A error occurred the server; ne
          sted exception is:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          Start server side stack trace:
          java.rmi.ServerError: A error occurred the server; nested exception is:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          at java.lang.System.loadLibrary(System.java:820)
          at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          at java.security.AccessController.doPrivileged(Native Method)
          at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          149)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          a:80)
          at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          ctionManager.java:150)
          at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          a:666)
          at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          AQueueConnectionFactory.java:53)
          at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          a:267)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:22)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          ; nested exception is:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          Start server side stack trace:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          at java.lang.System.loadLibrary(System.java:820)
          at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          at java.security.AccessController.doPrivileged(Native Method)
          at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          149)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          a:80)
          at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          ctionManager.java:150)
          at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          a:666)
          at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          AQueueConnectionFactory.java:53)
          at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          a:267)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:22)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          Start server side stack trace:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          at java.lang.System.loadLibrary(System.java:820)
          at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          at java.security.AccessController.doPrivileged(Native Method)
          at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          149)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          a:80)
          at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          ctionManager.java:150)
          at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          a:666)
          at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          AQueueConnectionFactory.java:53)
          at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          a:267)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:22)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          <<no stack trace available>>
          --------------- nested within: ------------------
          weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
          [java.rmi.ServerError: A error occurred the server; nested exception is:
                  java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          Start server side stack trace:
          java.rmi.ServerError: A error occurred the server; nested exception is:
                  java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
                  at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
                  at java.lang.Runtime.loadLibrary0(Runtime.java:749)
                  at java.lang.System.loadLibrary(System.java:820)
                  at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
                  at java.security.AccessController.doPrivileged(Native Method)
                  at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
                  at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
                  at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
                  at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          149)
                  at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          tion(MQBindingsManagedConnectionFactoryJ11.java:139)
                  at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          ion(MQBindingsManagedConnectionFactoryJ11.java:157)
                  at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          a:80)
                  at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          ctionManager.java:150)
                  at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          a:666)
                  at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
                  at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
                  at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
                  at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
                  at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
                  at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
                  at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
                  at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
                  at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          AQueueConnectionFactory.java:53)
                  at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
                  at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
                  at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
                  at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
                  at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
                  at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          a:267)
                  at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:22)
                  at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                  at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          ; nested exception is:
                  java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          Start server side stack trace:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
                  at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
                  at java.lang.Runtime.loadLibrary0(Runtime.java:749)
                  at java.lang.System.loadLibrary(System.java:820)
                  at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
                  at java.security.AccessController.doPrivileged(Native Method)
                  at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
                  at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
                  at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
                  at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          149)
                  at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          tion(MQBindingsManagedConnectionFactoryJ11.java:139)
                  at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          ion(MQBindingsManagedConnectionFactoryJ11.java:157)
                  at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          a:80)
                  at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          ctionManager.java:150)
                  at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          a:666)
                  at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
                  at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
                  at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
                  at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
                  at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
                  at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
                  at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
                  at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
                  at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          AQueueConnectionFactory.java:53)
                  at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
                  at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
                  at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
                  at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
                  at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
                  at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          a:267)
                  at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:22)
                  at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                  at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
          at $Proxy1.bridgeWLS2MQS(Unknown Source)
          at MQClient.main(MQClient.java:54)

The point is that over TCPIP the MQ XA connection factory is not available.
          The MQ shared memory/JNI driver is required to access it, which limits
          access to those processes that are on the same box as the MQ q manager.
          This is an MQ series limitation.
          Douglas WF Acheson wrote:
          > Hello,
          >
          > If memory server me correct, default connection to MQ Series is through
          > JNI calls and shared memory. You have to change the protocol to TCPIP when
          > connection to the queue manager on another box (do not know much about XA
          > with MQ Series); that is when you connect to MQ Series vi JMS on another
          > box you must do something like the following:
          >
          > qcf = new MQQueueConnectionFactory() ;
          > qcf.setHostName(hostName) ;
          > qcf.setPort(port) ;
          > qcf.setTransportType(JMSC.MQJMS_TP_CLIENT_MQ_TCPIP) ;
          > qcf.setQueueManager(qManagerName) ;
          >
          > Then when you create you queues, sesions etc. you are point at the correct Q
          > manager.
          >
          > Hope this helps ...
          >
          > Douglas WF Acheson
          >
          > "Raja Mukherjee" <[email protected]> wrote in message
          > news:[email protected]...
          > > On a closer look at the original post (sorry for missing that, it was
          > early
          > > in the morning), you would not be able to use XA if your QM and WLS are in
          > > different boxes. Check on this newsgroup, there are several posts on this
          > > subject. The whitepaper, if I recall correctly, installs both MQ and WLS
          > on
          > > the sames box. This is a MQSeries limitation not WLS.
          > >
          > > .raja
          > >
          > >
          > > "ibrahim Nehme" <[email protected]> wrote in message
          > > news:[email protected]...
          > > >
          > > > I am trying to setup the example given in the BEA white paper:
          > > > Using MQSeries as a Transactional Resource Manager with Weblogic Server.
          > > > Version 1.
          > > > October 25, 2001.
          > > > I followed the instructions given in the documents, but when i run
          > client
          > > program
          > > >
          > > > >java MQClient t3://localhost:7001 "MQSeries test"
          > > > I received the following exception below. Does anyone how what is the
          > > reason for
          > > >
          > > > this exception(s) and how i can solve the problem? My MQSeries Server
          > and
          > > Weblogic
          > > > 6.1 sp2 are installed on seperate NT machines. I installed the MQSeries
          > > classes
          > > > for java and the MQSeries classes for Java Message Service on the
          > weblogic
          > > > server machine.
          > > > ---------------------------------------
          > > > sending: "MQSEries test"
          > > > Exception in thread "main" java.rmi.ServerError: A error occurred the
          > > server; ne
          > > > sted exception is:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >
          > > > Start server side stack trace:
          > > > java.rmi.ServerError: A error occurred the server; nested exception is:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          > > > at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          > > > at java.lang.System.loadLibrary(System.java:820)
          > > > at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          > > > at java.security.AccessController.doPrivileged(Native Method)
          > > > at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          > > > at
          > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          > > > at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          > > > at
          > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          > > > 149)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          > > > at
          > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          > > > a:80)
          > > > at
          > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          > > > ctionManager.java:150)
          > > > at
          > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          > > > a:666)
          > > > at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          > > > at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          > > > at
          > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          > > > at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          > > > at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          > > > )
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          > > > AQueueConnectionFactory.java:53)
          > > > at
          > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          > > > at
          > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          > > > at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          > > > at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          > > > a:267)
          > > > at
          > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          > > > java:22)
          > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > > End server side stack trace
          > > > ; nested exception is:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >
          > > > Start server side stack trace:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          > > > at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          > > > at java.lang.System.loadLibrary(System.java:820)
          > > > at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          > > > at java.security.AccessController.doPrivileged(Native Method)
          > > > at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          > > > at
          > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          > > > at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          > > > at
          > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          > > > 149)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          > > > at
          > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          > > > a:80)
          > > > at
          > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          > > > ctionManager.java:150)
          > > > at
          > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          > > > a:666)
          > > > at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          > > > at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          > > > at
          > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          > > > at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          > > > at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          > > > )
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          > > > AQueueConnectionFactory.java:53)
          > > > at
          > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          > > > at
          > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          > > > at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          > > > at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          > > > a:267)
          > > > at
          > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          > > > java:22)
          > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > > End server side stack trace
          > > >
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >
          > > > Start server side stack trace:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          > > > at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          > > > at java.lang.System.loadLibrary(System.java:820)
          > > > at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          > > > at java.security.AccessController.doPrivileged(Native Method)
          > > > at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          > > > at
          > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          > > > at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          > > > at
          > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          > > > 149)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          > > > at
          > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          > > > a:80)
          > > > at
          > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          > > > ctionManager.java:150)
          > > > at
          > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          > > > a:666)
          > > > at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          > > > at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          > > > at
          > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          > > > at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          > > > at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          > > > )
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          > > > AQueueConnectionFactory.java:53)
          > > > at
          > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          > > > at
          > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          > > > at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          > > > at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          > > > a:267)
          > > > at
          > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          > > > java:22)
          > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > > End server side stack trace
          > > >
          > > > <<no stack trace available>>
          > > > --------------- nested within: ------------------
          > > > weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
          > > > [java.rmi.ServerError: A error occurred the server; nested exception is:
          > > >         java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >
          > > > Start server side stack trace:
          > > > java.rmi.ServerError: A error occurred the server; nested exception is:
          > > >         java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >         at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          > > >         at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          > > >         at java.lang.System.loadLibrary(System.java:820)
          > > >         at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          > > >         at java.security.AccessController.doPrivileged(Native Method)
          > > >         at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          > > >         at
          > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          > > >         at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          > > >         at
          > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          > > > 149)
          > > >         at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          > > >         at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          > > >         at
          > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          > > > a:80)
          > > >         at
          > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          > > > ctionManager.java:150)
          > > >         at
          > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          > > > a:666)
          > > >         at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          > > >         at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          > > >         at
          > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          > > >         at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          > > >         at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          > > >         at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          > > >         at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          > > >         at
          > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          > > > )
          > > >         at
          > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          > > > AQueueConnectionFactory.java:53)
          > > >         at
          > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          > > >         at
          > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          > > >         at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          > > >         at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          > > >         at
          > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          > > >         at
          > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          > > > a:267)
          > > >         at
          > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          > > > java:22)
          > > >         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > >         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > > End server side stack trace
          > > > ; nested exception is:
          > > >         java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >
          > > > Start server side stack trace:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >         at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          > > >         at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          > > >         at java.lang.System.loadLibrary(System.java:820)
          > > >         at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          > > >         at java.security.AccessController.doPrivileged(Native Method)
          > > >         at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          > > >         at
          > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          > > >         at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          > > >         at
          > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          > > > 149)
          > > >         at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          > > >         at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          > > >         at
          > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          > > > a:80)
          > > >         at
          > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          > > > ctionManager.java:150)
          > > >         at
          > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          > > > a:666)
          > > >         at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          > > >         at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          > > >         at
          > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          > > >         at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          > > >         at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          > > >         at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          > > >         at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          > > >         at
          > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          > > > )
          > > >         at
          > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          > > > AQueueConnectionFactory.java:53)
          > > >         at
          > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          > > >         at
          > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          > > >         at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          > > >         at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          > > >         at
          > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          > > >         at
          > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          > > > a:267)
          > > >         at
          > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          > > > java:22)
          > > >         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > >         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > > End server side stack trace
          > > > ]
          > > > at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
          > > > at $Proxy1.bridgeWLS2MQS(Unknown Source)
          > > > at MQClient.main(MQClient.java:54)
          > >
          > >

Similar Messages

ClassCircularityError in JAAS Authorization with Weblogic Server 10.3

We are implementing JAAS authorization in which roles and policies are stored in a custom JAAS policy file and users are stored in the embedded LDAP server provided by Weblogic. We are facing problem is authorizing users using the custom policy created.
We have implemented the JAAS authentication service with weblogic server 10g R3 and user's information stored in embedded LDAP server provided WLS. Given below are the details of implementation for JAAS Authorization:
Following are the custom classes created:
1. Custom Principal Class
public class Principal implements java.security.Principal, java.io.Serializable {
private String name;
public Principal() {
name = "";
public Principal(String newName) {
name = newName;
public boolean equals(Object o) {
if (o == null)
return false;
if (this == o)
return true;
if (o instanceof Principal) {
if (((Principal) o).getName().equals(name))
return true;
else
return false;
else
return false;
public int hashCode() {
return name.hashCode();
public String toString() {
return name;
public String getName() {
return name;
2. Custom Permission Class
public class ActionPermission extends Permission {
     public ActionPermission(String name) {
          super(name);
     @Override
     public boolean equals(Object obj) {
          if ((obj instanceof ActionPermission)
                    && ((ActionPermission) obj).getName().equals(this.getName())) {
               return true;
          } else {
               return false;
     @Override
     public String getActions() {
          return "";
     @Override
     public int hashCode() {
          return this.getName().hashCode();
     @Override
     public boolean implies(Permission permission) {
          if (!(permission instanceof ActionPermission)) {
               return false;
          String thisName = this.getName();
          String permName = permission.getName();
          if (this.getName().equals("*")) {
               return true;
          if (thisName.endsWith("*")
                    && permName.startsWith(thisName.substring(0, thisName
                              .lastIndexOf("*")))) {
               return true;
          if (thisName.equals(permName)) {
               return true;
          return false;
Following are the configuration changes:
1. Added custom policy to weblogic.policy.
grant Principal com.scotia.security.authorization.Principal "test" <User defined in the embedded LDAP server of WLS>{
permission com.scotia.security.authorization.permission.ActionPermission "viewScreen";
2. Set the java security manager in startWeblogic.cmd file.
%JAVA_HOME%\bin\java %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -Dweblogic.Name=%SERVER_NAME% -Djava.security.manager -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy %PROXY_SETTINGS% %SERVER_CLASS%
3. Set Realm "Security Model" to "Custom Roles and Policies".
Right now we are facing the given below exception:
java.lang.ClassCircularityError: com/scotia/security/authorization/THORPrincipal
     at java.lang.Class.forName0(Native Method)
     at java.lang.Class.forName(Class.java:247)
     at sun.security.provider.PolicyFile.addPermissions(PolicyFile.java:1381)
     at sun.security.provider.PolicyFile.getPermissions(PolicyFile.java:1268)
     at sun.security.provider.PolicyFile.getPermissions(PolicyFile.java:1231)
     at sun.security.provider.PolicyFile.getPermissions(PolicyFile.java:1167)
     at sun.security.provider.PolicyFile.implies(PolicyFile.java:1122)
     at weblogic.security.service.WLSPolicy.implies(Unknown Source)
     at java.security.ProtectionDomain.implies(ProtectionDomain.java:213)
     at java.security.AccessControlContext.checkPermission(AccessControlContext.java:301)
     at java.security.AccessController.checkPermission(AccessController.java:546)
     at java.lang.SecurityManager.checkPermission(SecurityManager.java:532)
     at java.lang.SecurityManager.checkRead(SecurityManager.java:871)
     at java.io.File.exists(File.java:731)
     at weblogic.utils.classloaders.DirectoryClassFinder.getSource(DirectoryClassFinder.java:36)
Please help if anyone has some clue regarding this exception. We tried checking the jdk version used by eclipse and weblogic and found it to be same.

1. Custom Principal Class
public class Principal implements java.security.Principal, java.io.Serializable {Rename it. You are asking for trouble naming a class after an interface it implements.
java.lang.ClassCircularityError: com/scotia/security/authorization/THORPrincipalWhat's that class? You haven't shown us.

Error while deploying application with WebLogic server

Hi,
I use Jdeveloper 11g and created and ADF application which i want to deploy with WebLogic Server.But i have an error which is :
"There was a failure when processing annotations for application C:\...\xxx.war. Please make sure that the annotations are valid. The error is oracle.adf.library.webapp.ResourceServlet "
Plz help me.
Thx

I am receiving same message for simple servlet. Running JDev11g build 5166 and embedded WLS 10.3. Servlet used to deploy to embedded WLS and ran fine. Recently running newly created servlets produces error message as in this thread.
Investigation turned up the fact that the class file for the servlet was not deployed to the context-root (o.j2ee\drs) on the server. Copying the class file from the mywork project folder to the context-root folder (o.j2ee\drs) permitted the servlet to run.
Don't know if this is the cause of what you are experiencing but it may assist in your investigation! I have not figured out why the class file for servlets does not deploy to server despite the fact that the log file shows war and ear files were deployed. As it turns out, the war file does not have the class file in it so something is wrong before the war file is created.
Cheers!

How to know report server name in oracle forms and reports with weblogic server 10.3.5

Hello Experts, I am new in oracle forms and reports.I have installed Oracle forms 11g with weblogic server 10.3.5 at windows 7.Forms and reports are working well.But I want to call a report from an oracle form button press trigger. For This I need to know the my report server name which i dont know.Please tell me how can I know my report server name.

I want to call a report from an oracle form button press trigger. For This I need to know the my report server name
You can find the name of the standalone reports server in $ORACLE_INSTANCE/config/ReportsServerComponent.
Or you can use Fusion Middleware Control Console, normally at http://<machine name>:7001/em

Enabling SSO with Weblogic Server

Hi,
Can someone please forward some documention on enabling SSO with Weblogic server for different applications using the admin console.
Is enabling SSO only possible programmatically??
Is there an external server amongst the Weblogic Platform that maintains this SSO information??
Regards,
Mukta

Pradeep,
Here are some questions for you.
1. what version of Weblogic App Server you are using?
2. Is it a weblogic Portal or a Java application deployed
on a Weblogic App Server?
3. You have mentioned that the users are stored in a table. Is it a database table ?
Anyway see the following link as a starting point?
http://e-docs.bea.com/wls/docs81/jconnector/security.html#1216783
If the customer has lot of other web applications that they want to integrate you can look at third party authentication solutions (Ex: Siteminder). But if it is a few or limited applications then custom solution would be more appropriate from the cost perspective.
Hope this can be a starting point.
-Regards
-Venkat Malempati

WLS :: Will Vista web client work with Weblogic Server 8.1.6 over SSL?

Hello,
I have installed 51-2 bit SSL cert on weblogic 7 and found that the secure site doesn't work on Vista web client.
Weblogic gives error in handshaking and says algorithm is not supported.
Vista web client uses some algorithms which were not supported by weblogic 7.
So would like to know if would Vista web client work with Weblogic Server 8.1.6 over SSL?
Any information in this regard would be helpful.
Thanks in Advance.

can you use the following debug flags in the weblogic server as java_options and paste the complete ssl handshake exception here.
-Dweblogic.StdoutDebugEnabled=true
-Dssl.debug=true
thanks,
sandeep

Jsf with weblogic server 6.1

Hi, Any help would be appreciated. I am trying to use jsf with weblogic server 6.1 and wlintegration 2.1 I tried to deploy the samples provided with jwsdp-1.2 When I start the guess number sample I get the following error message:
Duke's number: 3
<25-Jun-03 16:03:40 BST> <Error> <HTTP> <[WebAppServletConte
xt(57758238,examplesWebApp,/examplesWebApp)] Root cause of S
ervletException
javax.servlet.jsp.JspException: Cannot find FacesContext
at javax.faces.webapp.UIComponentTag.doStartTag(UICo
mponentTag.java:269)
at jsp_servlet._jsf_45_guessnumber._faces.__greeting
._jspService(__greeting.java:123)
at weblogic.servlet.jsp.JspBase.service(JspBase.java
:27), etc.
I updated the web.xml file, created the faces directory under my examplesWebApp active domain with the jsp files, it finds the UserNumberBean class but it still crashes with the above.
One problem I was having while deploying it that Weblogic Server did not allow me to copy jsf-api.jar, jstl.jar,etc under web-inf/lib.
So I added all required jar files under bea root/config/samples/lib and updated startWeblogic.cmd
Please help with how to deploy correctly the samples:
Botond

Thanks bill.
I checked my weblogic server 6.1,it limited to j2ee1.2 features only.So I changed it supporting j2ee1.3 features.Now my JSF example is working normally.
But I found a new question soon.
I writed some letter in Chinese in jsp page .And I got some errors in weblogic.
<2003-10-14 01:47:57> <Error> <HTTP> <101019> <[ServletContext(id=6480502,name=jaction,conte
xt-path=/jaction)] Servlet failed with IOException
java.io.IOException: javax.servlet.jsp.JspException: The taglib validator rejected the page: "org.xm
l.sax.SAXParseException: An invalid XML character (Unicode: 0xb8) was found in the CDATA section., "
at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:124)
at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java:258)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:356)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:214)
at weblogic.servlet.jsp.JspStub.checkForReload(JspStub.java:149)
at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:538)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:364)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:312)
at com.sun.faces.context.ExternalContextImpl.dispatchMessage(ExternalContextImpl.java:298)
at com.sun.faces.lifecycle.ViewHandlerImpl.renderView(ViewHandlerImpl.java:53)
at com.sun.faces.lifecycle.RenderResponsePhase.execute(RenderResponsePhase.java:89)
at com.sun.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:185)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:169)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1075)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:418)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletC
ontext.java:5517)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:685)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:31
56)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2506)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
I donnot know what is the matter.And how to correct?
thanks again.
Yanger

(266758030) Q SYNCH-12 Does Workshop work with WebLogic Server 6.1?

(266758030) Q<SYNCH-12> Does Workshop work with WebLogic Server 6.1? (asked by Noel
Fuentes)
A<SYNCH-12> (by Adam Fitzgerald): No, Web Services in WebLogic Server 6.1 are different
from those available in WebLogic Server 7.0. WebLogic Workshop is a WLS 7.0 tool.

Rick,
You may want to look at the Alteon and F5 configuration we have on edocs.
Take a look at the following URLs for a possible solution
http://edocs.bea.com/wls/docs61/cluster/alteon.html#591902
http://edocs.bea.com/wls/docs61/cluster/bigip.html#591902
Chuck Nelson
DRE
BEA Technical Support

BEA Workshop for WebLogic Platform9.2 can use with weblogic server 9.1?

Wanted to know whether BEA Workshop for WebLogic Platform9.2 can be used with weblogic server 9.1?. If it cannot be used then which ide we need to use to build the j2ee application to deploy on to weblogic server 9.1

try http://edelivery.oracle.com
accept the licenses and in the next screens
"Select a Product Pack" select Oracle BEA
and your platform (i.e. Windows)
then select the media pack you want
i.e. "BEA WebLogic Media Pack for Linux x86"
and voila!
"WebLogic Platform 10.2 for Microsoft Windows (32-bit)"
(in the Platform includes WebLogic Server, Workshop for WebLogic, WebLogic Portal and WebLogic Integration)
./ydes

How to associate an XA Resource Manager with a Corba Native Client?

Hello,
how is a Corba Native (C++) Client associated with an XA Resource Manager? I can't find it in the documentation.
I believe I understand how it works in a Tuxedo native client: buildclient needs "-r <rmname>" and tpinit() needs to include the group name (ubbconfig group with TMS_ORA and OPENINFO).
buildobjclient does not seem have anything like the "-r" option, and the bootstrap object does not seem to have any way to specify a group.
We have a Corba client that updates the database, enqueues into /Q and invokes a transactional Corba service. All three need to be in the same transaction. I am stuck on how to get an XA DB connection.
Thanks...
Roger
PS: The proper solution is to make the client's functionality a service and have the client invoke the service. But that causes other complications.

I got part of the answer from a different thread.
Native clients do not need a TMS_* to start a transaction. On commit/rollback they consult the Global Transaction Table (GTT) to find a TMS_* that is involved in the transaction and delegate the commit/rollback to one of those TMS_*.
For remote clients (using IIOP) the ISH handles the request from the remote client and deals with transaction management.
Roger

Unable to use JProfiler with SUN Access Manager (in Weblogic Server)

Whe I was trying to profiling with JProfiler , I am getting the following exception during the Weblogic startup:
<Dec 12, 2005 6:30:49 PM IST> <Warning> <HTTP> <BEA-101247> <Application: '/opt/SUNWam', Module: 'amcommon': Public ID references the old version of the Servlet DTD. You must change the public ID in web.xml file to "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN".>
Dec 12, 2005 6:30:54 PM com.sun.xml.rpc.server.http.JAXRPCContextListener contextInitialized
INFO: JAXRPCSERVLET12: JAX-RPC context listener initializing
<Dec 12, 2005 6:30:56 PM IST> <Warning> <Net> <BEA-000905> <Could not open connection with host: ctsblrsun14.gmacfs.com and port: 8001.>
<Dec 12, 2005 6:30:56 PM IST> <Warning> <Net> <BEA-000905> <Could not open connection with host: ctsblrsun14.gmacfs.com and port: 8001.>
<Dec 12, 2005 6:30:56 PM IST> <Warning> <Net> <BEA-000905> <Could not open connection with host: ctsblrsun14.gmacfs.com and port: 8001.>
<Dec 12, 2005 6:30:56 PM IST> <Warning> <Net> <BEA-000905> <Could not open connection with host: ctsblrsun14.gmacfs.com and port: 8001.>
<Dec 12, 2005 6:30:57 PM IST> <Error> <HTTP> <BEA-101216> <Servlet: "LoginLogoutMapping" failed to preload on startup in Web application: "amserver".
javax.servlet.ServletException
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:919)
at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:883)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:822)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3335)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3292)
at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3278)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3261)
at weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:5951)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:862)
at weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2127)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2168)
at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2115)
at weblogic.management.deploy.slave.SlaveDeployer$Application.setActivation(SlaveDeployer.java:3082)
at weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllApplications(SlaveDeployer.java:1751)
at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:359)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
at weblogic.Server.main(Server.java:32)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.jprofiler.agent.Agent$_E.run(Unknown Source)
at java.lang.Thread.run(Thread.java:534)
Caused by: java.lang.NullPointerException
at com.sun.identity.authentication.UI.LoginLogoutMapping.init(LoginLogoutMapping.java:71)
at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1028)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:904)
... 25 more
>

This is an SSL handshake problem of Websphere - has nothing to do with AM.
Websphere�s JDK does not trust the Signer / Cert of AM�s deployment container.
Either configure a truststore (or use an existing webshpere truststore) where you import the Cert of the Signing CA of your AM DC�s cert.
Other option - import the mentioned cert in cacert file of IBM JDK - but be aware that this might get lost when applying an Websphere fixpack/refreshpack.
BTW what have you configured for server.port,server.host and server.protocol in your AMConfig.properties?
If you have not changed that settings agent will use the port/protocol specified to communicate with AM.
-Bernhard

Kodo with Weblogic Server?

Hi,
I am intending to port my current operations from a direct kodo -> mssql
connection to a kodo->weblogic->mssql methology.
From what i found out, web logic support a type 4 jdbc driver.
I wish to find out if its possible for kodo to directly utilise this
methodology, without any changes to existing structure. And possibly the
security improvements over this new arrangement.
I wish to do some homework on this before i get the web logic software.
Pls advice.

Hi,
I made further read up and i wish to clarify some information.
I noted that to use Weblogic as the middle tier, a startup class is
required on Weblogic server so that Weblogic knows when it should start
taking note of a new connection....
I took the sample startup class from
http://docs.solarmetric.com/j2ee_tutorial_jca_installation.html#j2ee_tutorial_generic
1) The code seems to suggest that a kodo.properties will be found on the
weblogic server. Is this right? I am assuming that the compiled class file
will not have any memory of what is loaded from the kodo.properties file
during runtime.
2) Will my client java application be automatically getting connections
pooled from the weblogic server? That is, all connection pooling
activities will be handled by weblogic and on kodo side, no additional
code is required to perform connection pooling management.
For example, my current code below will not require any changes to make
use of weblogic's connection pool.
PPersistenceManager pm = JDOFactory.getPersistencemanager(props);
Transaction trans = pm.currentTransaction();
trans.begin();
Query query = pm.newQuery(.....);
trans.commit();
Pls advice
tan
Stephen Kim wrote:
Yes. Kodo can work with both WebLogic and SQLServer. Kodo can use
datasources defined in WebLogic or directly address SQLServer.
Tan wrote:
Hi,
I am intending to port my current operations from a direct kodo -> mssql
connection to a kodo->weblogic->mssql methology.
From what i found out, web logic support a type 4 jdbc driver.
I wish to find out if its possible for kodo to directly utilise this
methodology, without any changes to existing structure. And possibly the
security improvements over this new arrangement.
I wish to do some homework on this before i get the web logic software.
Pls advice.
Steve Kim
[email protected]
SolarMetric Inc.
http://www.solarmetric.com

BIBeans internationalization issue with weblogic server 8.1 sp2

We use oralce bibeans 9.0.4 to develop OLAP web application in Chinsese Simplified environment. When deploy the web application on the embedded OC4J server, everything goes well. All the labels (Line items and image button labels etc. ) of the crosstab is displayed in chinese. but it always display English labels when delploy it on weblogic server V8.1 sp2.
currently on my web page java.util.Locale.getDefault() return zh_CN
I have done two things:
first, add exportCharacterEncoding init param for UIXServlet
<init-param>
<param-name>exportCharacterEncoding</param-name>
<param-value>GBK</param-value>
</init-param>
second,Set locale for the BIThinSession instance in jsp file.
oracle.dss.addins.jspTags.BIThinSession bisession = (oracle.dss.addins.jspTags.BIThinSession) pageContext.findAttribute("SalesBIThinSession");
bisession.setLocale(Locale.getDefault());
Is this a bug that bibeans can not locate resource bundles correctly base on the user's specified environment? Is there an invisible environment variable base on which the bibean tags judge to select a resource file and result in this phenomenon?

The intersting point here is that the application works using an Oracle stack but does not work using an IBM stack. I will contact our development engineers for more information and will post another response when I have a reply.
Business Intelligence Beans Product Management Team
Oracle Corporation

Enterprise Manager For WebLogic Server 10.3

Hi,
I have a weblogic server version 10.3.
I want to access the Enterprise Manager for the same.I believe standalone version of weblogic server 10.3 doesnt come with
Enterprise Manager.
I believe we can have EM if we download Application Development Runtime.
I tried doing the same ,but I am unable to launch the Enterprise Manager Website.
My server is running on on port 7001 ,hence I tried accessing the Enterprise Manager
using the below url i.e http://localhost:7001/em,but i was not able to access.
Could somebody help me on how I can access the enterprise Manager.
Regards
Harish

Actually, with FMW 11g (WLS version 10.3.1 NOT 10.3), there is now an application called Fusion Middleware Control that is part of the Enterprise Manager family. This typically binds to http://host:port/em on the AdminServer. This is for the FMW components in a single domain, plus any other web tier components like Oracle HTTP Server or Web Cache.
http://download.oracle.com/docs/cd/E12839_01/integration.1111/e10223/17_em.htm
Check the docs for installation instructions of this component.

JNDIMapper Problem (Foreign JMS Providers with WebLogic Server does not close connection )

          Hello All,
          We tried to use wlsmqseries.zip classes (specially JNDI Mapper) for integrating
          WebLogic Server with MQ so that we can incorporate XA transactions. We use LDAP
          context factory to bind MQ.
          We found a number of LDAP connections are getting opened by JNDIMapper, but it's
          not getting closed.
          Can some one give some clue to this ?
          Also any suggestion to serve the current purpose is welcome.
          Thanks, Sudarson


          Hello All,
          We tried to use wlsmqseries.zip classes (specially JNDI Mapper) for integrating
          WebLogic Server with MQ so that we can incorporate XA transactions. We use LDAP
          context factory to bind MQ.
          We found a number of LDAP connections are getting opened by JNDIMapper, but it's
          not getting closed.
          Can some one give some clue to this ?
          Also any suggestion to serve the current purpose is welcome.
          Thanks, Sudarson

MQSeries as a Transactional Resource Manager with Weblogic Server

Similar Messages

Maybe you are looking for