Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
2 replies Latest Post - ‏2013-05-23T07:58:55Z by manjunathn
WS7D_Sreekanth_Sreedharan
1 Post
ACCEPTED ANSWER

Pinned topic Connecting to JMS queues in WAS8.0 Server

‏2013-01-29T11:18:49Z |
I have configured JMS ques in WAS 8.0 using the default messaging service, but when I try to connect to the queues, I am getting the following exception. Any idea on this?

==========================================
QCF =jms/TestQCF
QueueName =jms/SQueue
App Server =Websphere
ProviderUrl =corbaloc::mngnet173865d:2811
inititalCF =com.ibm.websphere.naming.WsnInitialContextFactory
InitialContext = {com.ibm.websphere.naming.hostname.normalizer=com.ibm.ws.naming.util.DefaultHostnameNormalizer, java.naming.factory.initial=com.ibm.websphere.naming.WsnInitialContextFactory, com.ibm.websphere.naming.name.syntax=jndi, com.ibm.websphere.naming.namespace.connection=lazy, com.ibm.ws.naming.ldap.ldapinitctxfactory=com.sun.jndi.ldap.LdapCtxFactory, com.ibm.websphere.naming.jndicache.cacheobject=populated, com.ibm.websphere.naming.namespaceroot=defaultroot, com.ibm.ws.naming.wsn.factory.initial=com.ibm.ws.naming.util.WsnInitCtxFactory, com.ibm.websphere.naming.jndicache.maxcachelife=0, com.ibm.websphere.naming.jndicache.maxentrylife=0, com.ibm.ws.naming.wsn.localonly=false, com.ibm.websphere.naming.jndicache.cachename=providerURL, java.naming.provider.url=corbaloc::mngnet173865d:2811, java.naming.factory.url.pkgs=com.ibm.ws.naming}
JSAS1480I: Security is not enabled because the ConfigURL property file is not set.
Exception occurred : javax.naming.NamingException: Error getting WsnNameService properties Root exception is org.omg.CORBA.TRANSIENT: initial and forwarded IOR inaccessible vmcid: IBM minor code: E07 completed: No
javax.naming.NamingException: Error getting WsnNameService properties Root exception is org.omg.CORBA.TRANSIENT: initial and forwarded IOR inaccessible vmcid: IBM minor code: E07 completed: No
at com.ibm.ws.naming.util.WsnInitCtxFactory.mergeWsnNSProperties(WsnInitCtxFactory.java:1550)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootContextFromServer(WsnInitCtxFactory.java:1040)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getRootJndiContext(WsnInitCtxFactory.java:960)
at com.ibm.ws.naming.util.WsnInitCtxFactory.getInitialContextInternal(WsnInitCtxFactory.java:612)
at com.ibm.ws.naming.util.WsnInitCtx.getContext(WsnInitCtx.java:128)
at com.ibm.ws.naming.util.WsnInitCtx.getContextIfNull(WsnInitCtx.java:765)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:164)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:179)
at javax.naming.InitialContext.lookup(InitialContext.java:431)
at JMS.JMSBrowser.browse(JMSBrowser.java:162)
at JMS.JMSBrowser.main(JMSBrowser.java:72)
Caused by: org.omg.CORBA.TRANSIENT: initial and forwarded IOR inaccessible vmcid: IBM minor code: E07 completed: No
at com.ibm.rmi.corba.ClientDelegate.createRequest(ClientDelegate.java:1274)
at com.ibm.CORBA.iiop.ClientDelegate.createRequest(ClientDelegate.java:1342)
at com.ibm.rmi.corba.ClientDelegate.createRequest(ClientDelegate.java:1162)
at com.ibm.CORBA.iiop.ClientDelegate.createRequest(ClientDelegate.java:1308)
at com.ibm.rmi.corba.ClientDelegate.request(ClientDelegate.java:1884)
at com.ibm.CORBA.iiop.ClientDelegate.request(ClientDelegate.java:1264)
at org.omg.CORBA.portable.ObjectImpl._request(ObjectImpl.java:458)
at com.ibm.WsnBootstrap._WsnNameServiceStub.getProperties(_WsnNameServiceStub.java:38)
at com.ibm.ws.naming.util.WsnInitCtxFactory.mergeWsnNSProperties(WsnInitCtxFactory.java:1547)
... 10 more
Caused by: java.net.ConnectException: connect: Address is invalid on local machine, or port is not valid on remote machine
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:383)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:245)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:232)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:377)
at java.net.Socket.connect(Socket.java:539)
at com.ibm.ws.orbimpl.transport.WSTCPTransportConnection.createSocket(WSTCPTransportConnection.java:295)
at com.ibm.CORBA.transport.TransportConnectionBase.connect(TransportConnectionBase.java:354)
at com.ibm.ws.orbimpl.transport.WSTransport.getConnection(WSTransport.java:436)
at com.ibm.CORBA.transport.TransportBase.getConnection(TransportBase.java:187)
at com.ibm.rmi.iiop.TransportManager.get(TransportManager.java:89)
at com.ibm.rmi.iiop.GIOPImpl.getConnection(GIOPImpl.java:130)
at com.ibm.rmi.iiop.GIOPImpl.locate(GIOPImpl.java:219)
at com.ibm.rmi.corba.ClientDelegate.locate(ClientDelegate.java:1981)
at com.ibm.rmi.corba.ClientDelegate._createRequest(ClientDelegate.java:2006)
at com.ibm.rmi.corba.ClientDelegate.createRequest(ClientDelegate.java:1184)
at com.ibm.rmi.corba.ClientDelegate.createRequest(ClientDelegate.java:1270)
... 18 more
MSG ====>
  • indira
    indira
    1 Post
    ACCEPTED ANSWER

    Re: Connecting to JMS queues in WAS8.0 Server

    ‏2013-04-18T03:43:01Z  in response to WS7D_Sreekanth_Sreedharan

    Hi,

    After reading the blog  http://mresetar.blogspot.in/2012/06/was-8-has-ssl-turned-on-for-rmi-by.html ,  I am able to resolve the same issue as posted  above by changing the transport layer setting of  CSIv2 inbound /outbound communications to SSL-supported from  SSL-required (which was by default set in WAS 8.0).

    The steps to resolve the issue are :

    In Application Server Admin Console,                     
    1) Go to Global Security                                 
    2) Under Authentication panel -> Expand RMI/IIOP security
    3) Click on  CSIv2 inbound communications ->             
    CSIv2 Transport Layer  ->                                
    .                                                        
    set Transport :  SSL-supported                           
    .                                                        
    4) Similarly, for  CSIv2 outbound communications ->      
    CSIv2 Transport Layer  ->                                
    set Transport :  SSL-supported                           
    .                                                        
    5) Restart the Server.                             

    You should be able to send the messages after restarting the server.

     

    Thanks & Regards,

    Indira,

    WebSphere BPTE Team, ISL.

    • manjunathn
      manjunathn
      1 Post
      ACCEPTED ANSWER

      Re: Connecting to JMS queues in WAS8.0 Server

      ‏2013-05-23T07:58:55Z  in response to indira

      hi indira,

       

      it was a very useful post.

       

      Thanks & regards

      manju