T3s protocol

Hi,
I'm running an applet from which i'm connecting to servlet in weblogic 6.0(SSL
is enabled). We are trying to connect using t3s protocol but it is giving us error
that resource is not found...Can some body give me some info regarding t3s protocol
or any ideas regarding the above problem?
Thanks in advance...
-Madhu

Madhu
U need to connect to the T3s Server .If u are using the demo certificates
then ur request should be
t3s://weblogic.bea.com
and in ur hosts file if windows map the url with the IP
Sachin
"Madhu" <[email protected]> wrote in message
news:3be7efd6$[email protected]..
>
Hi,
I'm running an applet from which i'm connecting to servlet in weblogic6.0(SSL
is enabled). We are trying to connect using t3s protocol but it is givingus error
that resource is not found...Can some body give me some info regarding t3sprotocol
or any ideas regarding the above problem?
Thanks in advance...
-Madhu

Similar Messages

  • 2-way SSL using t3s protocol

    Goodmorning,
    I'm trying to get a 2-way SSL connection between two WLS 10.3 in production mode.
    WLS #1 contains the client application and WLS #2 contains the server application.
    I've got a standalone Microsoft CA.
    I've configured WLSs with custom identity and trust JKS Stores.
    In trust store I stored the CA certificate.
    In identity store I created a selfsigned cert with RSA alg and this cert was signed from my CA.
    In identity store I also stored the CA's Certificate.
    I've enabled SSL with custom identity and trust store,
    None host verification,
    Export Key Lifespan 500,
    Two Way Client Cert Behavior: Client cert requested and enforced,
    SSL Rejection Logging Enabled checked,
    Inbound and Outbound Certificate Validation: Builtin SSL Validation Only
    I configured both WLS as explained (except identity certs that are custom for each server).
    I can invoke WLS #2 Webservices from WLS #1 via https.
    So I tried to invoke an EJB deployed on WLS #2 via t3s, but it didn't work.
    During handshake process, the first step is ok; in fact WLS #1 trusts WLS #2 certs.
    The second step goes wrong; here follows some logs.
    WLS #1
    <2-mar-2011 11.14.13 CET> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: CertificateRequest>
    <2-mar-2011 11.14.13 CET> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
    <2-mar-2011 11.14.13 CET> <Debug> <SecuritySSL> <BEA-000000> <8374786 SSL3/TLS MAC>
    <2-mar-2011 11.14.13 CET> <Debug> <SecuritySSL> <BEA-000000> <8374786 received HANDSHAKE>
    <2-mar-2011 11.14.13 CET> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: ServerHelloDone>
    <2-mar-2011 11.14.13 CET> <Debug> <SecuritySSL> <BEA-000000> *<No suitable identity certificate chain has been found.>*
    <2-mar-2011 11.14.13 CET> <Debug> <SecuritySSL> <BEA-000000> <write HANDSHAKE, offset = 0, length = 7>
    <2-mar-2011 11.14.13 CET> <Debug> <SecuritySSL> <BEA-000000> <write HANDSHAKE, offset = 0, length = 134>
    <2-mar-2011 11.14.13 CET> <Debug> <SecuritySSL> <BEA-000000> <write CHANGE_CIPHER_SPEC, offset = 0, length = 1>
    <2-mar-2011 11.14.13 CET> <Debug> <SecuritySSL> <BEA-000000> <Using JCE Cipher: SunJCE version 1.6 for algorithm RC4>
    <2-mar-2011 11.14.13 CET> <Debug> <SecuritySSL> <BEA-000000> <Ignoring not supported JCE Mac: SunJCE version 1.6 for algorithm HMACSHA1>
    <2-mar-2011 11.14.13 CET> <Debug> <SecuritySSL> <BEA-000000> <Will use default Mac for algorithm HMACSHA1>
    <2-mar-2011 11.14.13 CET> <Debug> <SecuritySSL> <BEA-000000> <Ignoring not supported JCE Mac: SunJCE version 1.6 for algorithm HmacMD5>
    <2-mar-2011 11.14.13 CET> <Debug> <SecuritySSL> <BEA-000000> <Will use default Mac for algorithm HmacMD5>
    <2-mar-2011 11.14.13 CET> <Debug> <SecuritySSL> <BEA-000000> <Ignoring not supported JCE Mac: SunJCE version 1.6 for algorithm HmacSHA1>
    <2-mar-2011 11.14.13 CET> <Debug> <SecuritySSL> <BEA-000000> <Will use default Mac for algorithm HmacSHA1>
    <2-mar-2011 11.14.13 CET> <Debug> <SecuritySSL> <BEA-000000> <write HANDSHAKE, offset = 0, length = 16>
    <2-mar-2011 11.14.13 CET> <Debug> <SecuritySSL> <BEA-000000> <isMuxerActivated: false>
    <2-mar-2011 11.14.13 CET> <Debug> <SecuritySSL> <BEA-000000> <8374786 SSL3/TLS MAC>
    <2-mar-2011 11.14.13 CET> <Debug> <SecuritySSL> <BEA-000000> <8374786 received ALERT>
    <2-mar-2011 11.14.13 CET> <Debug> <SecuritySSL> <BEA-000000> <NEW ALERT with Severity: FATAL, Type: 40
    WLS #2
    <2-mar-2011 11.14.12 CET> <Debug> <SecuritySSL> <BEA-000000> <HANDSHAKEMESSAGE: Certificate>
    <2-mar-2011 11.14.12 CET> <Debug> <SecuritySSL> <BEA-000000> <validationCallback: validateErr = 0>
    <2-mar-2011 11.14.12 CET> <Debug> <SecuritySSL> <BEA-000000> *<Required peer certificates not supplied by peer>*
    <2-mar-2011 11.14.12 CET> <Debug> <SecuritySSL> <BEA-000000> <weblogic user specified trustmanager validation status 4>
    <2-mar-2011 11.14.12 CET> <Warning> <Security> <BEA-090508> <Certificate chain received from xpr-selex-fel01 - 192.168.60.48 was incomplete.>
    <2-mar-2011 11.14.12 CET> <Debug> <SecuritySSL> <BEA-000000> <Validation error = 4>
    <2-mar-2011 11.14.12 CET> <Debug> <SecuritySSL> <BEA-000000> <Certificate chain is incomplete>
    <2-mar-2011 11.14.12 CET> <Debug> <SecuritySSL> <BEA-000000> <User defined JSSE trustmanagers not allowed to override>
    <2-mar-2011 11.14.12 CET> <Debug> <SecuritySSL> <BEA-000000> <SSLTrustValidator returns: 68>
    <2-mar-2011 11.14.12 CET> <Debug> <SecuritySSL> <BEA-000000> <Trust failure (68): CERT_CHAIN_INCOMPLETE>
    <2-mar-2011 11.14.12 CET> <Debug> <SecuritySSL> <BEA-000000> <NEW ALERT with Severity: FATAL, Type: 40
    One useful info: if I deploy both EJB application and client application all on the same WLS and alient application invokes the EJB via t3s, all works fine.
    Is there anything missing/wrong in the configuration?
    Thanks.

    Is this a typo?
    In identity store I created a selfsigned cert with RSA alg and this cert was signed from my CA.It can't be both self-signed and signed by a CA.
    In identity store I also stored the CA's Certificate.The identity store should not have a CA certificate in it. Either put the CA in your trust store, or chain your CA and your identity into a single cert within your identity store.
    During the handshake, the server (#2) will send a list of of its trusted CA certs to the client. The client has to look in its identity store for certs which are signed by one of the CAs sent by the server.
    If your client has multiple identity certs ( with the clientAuth key usage ) in its identity store, then there has to be some way to choose which cert to select. Does t3s use the SSL configuration's alias in the client as http does? You can test this by only using a client identity store with a single identity cert which is signed by one of the CA certificates presented by your server.

  • Weblogic Messaging Bridge - T3S Enabling Process

    Dear All,
    I need your help to resolve an issue in Weblogic Messaging Bridge - T3S enabling process.
    I'm doing a POC to forward messages between 2 different domains (from wl 10.3.2 to wl 10.0) using Messaging Bridge with T3S Protocol.
    I enabled SSL Port, Custom Identity and Custom Trust in those domains.
    In my laptop (single JVM), WL Messaging Bridge in 10.3.2 is able to forward messages between domains using T3S.
    My Testing Scenario:
    A Sample web application use the https/t3s protocol to put message(s) in the source jms queue                    
    Weblogic Messaging Bridge use the t3s protocol to get message(s) from source jms queue & forward the message(s) to the destination jms queue                    
    But, When I tried the same POC in sepearate boxes (WL 10.3.2 in one box, WL 10.0 in another box). I got the below exceptiion.
    Any one please throw some lights here to resolve the issue.
    ####<Oct 12, 2011 4:11:49 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1318416109085> <BEA-000000> <Exception:
    javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3s://172.16.2.25:4936: Destination unreachable; nested exception is:
         javax.net.ssl.SSLKeyException: [Security:090477]Certificate chain received from 172.16.2.25 - 172.16.2.25 was not trusted causing SSL handshake failure.; No available router to destination]
         at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
         at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:367)
         at weblogic.jndi.Environment.getContext(Environment.java:315)
         at weblogic.jndi.Environment.getContext(Environment.java:285)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
         at javax.naming.InitialContext.init(InitialContext.java:223)
         at javax.naming.InitialContext.<init>(InitialContext.java:197)
         at weblogic.jms.adapter.JMSBaseConnection.getInitialContext(JMSBaseConnection.java:2253)
         at weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:261)
         at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:247)
         at weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:190)
         at weblogic.connector.security.layer.AdapterLayer.createManagedConnection(AdapterLayer.java:802)
         at weblogic.connector.outbound.ConnectionFactory.createResource(ConnectionFactory.java:91)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1180)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:395)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:332)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:315)
         at weblogic.connector.outbound.ConnectionPool.reserveResource(ConnectionPool.java:596)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:309)
         at weblogic.connector.outbound.ConnectionManagerImpl.getConnectionInfo(ConnectionManagerImpl.java:352)
         at weblogic.connector.outbound.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:307)
         at weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:115)
         at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseConnectionFactory.java:123)
         at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:860)
         at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1051)
         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.net.ConnectException: t3s://172.16.2.25:4936: Destination unreachable; nested exception is:
         javax.net.ssl.SSLKeyException: [Security:090477]Certificate chain received from 172.16.2.25 - 172.16.2.25 was not trusted causing SSL handshake failure.; No available router to destination
         at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)
         at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
         at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:352)
         at weblogic.jndi.Environment.getContext(Environment.java:315)
         at weblogic.jndi.Environment.getContext(Environment.java:285)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
         at javax.naming.InitialContext.init(InitialContext.java:223)
         at javax.naming.InitialContext.<init>(InitialContext.java:197)
         at weblogic.jms.adapter.JMSBaseConnection.getInitialContext(JMSBaseConnection.java:2253)
         at weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:261)
         at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:247)
         at weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:190)
         at weblogic.connector.security.layer.AdapterLayer.createManagedConnection(AdapterLayer.java:802)
         at weblogic.connector.outbound.ConnectionFactory.createResource(ConnectionFactory.java:91)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1180)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:395)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:332)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:315)
         at weblogic.connector.outbound.ConnectionPool.reserveResource(ConnectionPool.java:596)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:309)
         at weblogic.connector.outbound.ConnectionManagerImpl.getConnectionInfo(ConnectionManagerImpl.java:352)
         at weblogic.connector.outbound.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:307)
         at weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:115)
         at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseConnectionFactory.java:123)
         at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:860)
         at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1051)
         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.rmi.ConnectException: Destination unreachable; nested exception is:
         javax.net.ssl.SSLKeyException: [Security:090477]Certificate chain received from 172.16.2.25 - 172.16.2.25 was not trusted causing SSL handshake failure.; No available router to destination
         at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:464)
         at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:315)
         at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:251)
         at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:194)
         at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
         at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
         at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
         at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:352)
         at weblogic.jndi.Environment.getContext(Environment.java:315)
         at weblogic.jndi.Environment.getContext(Environment.java:285)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
         at javax.naming.InitialContext.init(InitialContext.java:223)
         at javax.naming.InitialContext.<init>(InitialContext.java:197)
         at weblogic.jms.adapter.JMSBaseConnection.getInitialContext(JMSBaseConnection.java:2253)
         at weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:261)
         at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:247)
         at weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:190)
         at weblogic.connector.security.layer.AdapterLayer.createManagedConnection(AdapterLayer.java:802)
         at weblogic.connector.outbound.ConnectionFactory.createResource(ConnectionFactory.java:91)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1180)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:395)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:332)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:315)
         at weblogic.connector.outbound.ConnectionPool.reserveResource(ConnectionPool.java:596)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:309)
         at weblogic.connector.outbound.ConnectionManagerImpl.getConnectionInfo(ConnectionManagerImpl.java:352)
         at weblogic.connector.outbound.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:307)
         at weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:115)
         at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseConnectionFactory.java:123)
         at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:860)
         at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1051)
         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)
    >
    ####<Oct 12, 2011 4:11:49 PM IST> <Warning> <Connector> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416109086> <BEA-190032> << eis/jms/WLSConnectionFactoryJNDINoTX > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory, url = t3s://172.16.2.25:4936, user name = null) ">
    ####<Oct 12, 2011 4:11:49 PM IST> <Info> <MessagingBridge> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416109089> <BEA-200043> <Bridge "Bridge-0" failed to connect to the target destination and will try again in 45 seconds. This could be a temporary condition unless the messages repeat several times. (java.lang.Exception: javax.resource.ResourceException: ConnectionFactory: failed to get initial context (InitialContextFactory =weblogic.jndi.WLInitialContextFactory, url = t3s://172.16.2.25:4936, user name = null)
         at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1665)
         at weblogic.jms.adapter.JMSBaseConnection.throwResourceException(JMSBaseConnection.java:1645)
         at weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:460)
         at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:247)
         at weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:190)
         at weblogic.connector.security.layer.AdapterLayer.createManagedConnection(AdapterLayer.java:802)
         at weblogic.connector.outbound.ConnectionFactory.createResource(ConnectionFactory.java:91)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1180)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:395)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:332)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:315)
         at weblogic.connector.outbound.ConnectionPool.reserveResource(ConnectionPool.java:596)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:309)
         at weblogic.connector.outbound.ConnectionManagerImpl.getConnectionInfo(ConnectionManagerImpl.java:352)
         at weblogic.connector.outbound.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:307)
         at weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:115)
         at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseConnectionFactory.java:123)
         at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:860)
         at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1051)
         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)
    -------------- Linked Exception ------------
    javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3s://172.16.2.25:4936: Destination unreachable; nested exception is:
         javax.net.ssl.SSLKeyException: [Security:090477]Certificate chain received from 172.16.2.25 - 172.16.2.25 was not trusted causing SSL handshake failure.; No available router to destination]
         at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
         at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:367)
         at weblogic.jndi.Environment.getContext(Environment.java:315)
         at weblogic.jndi.Environment.getContext(Environment.java:285)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
         at javax.naming.InitialContext.init(InitialContext.java:223)
         at javax.naming.InitialContext.<init>(InitialContext.java:197)
         at weblogic.jms.adapter.JMSBaseConnection.getInitialContext(JMSBaseConnection.java:2253)
         at weblogic.jms.adapter.JMSBaseConnection.startInternal(JMSBaseConnection.java:261)
         at weblogic.jms.adapter.JMSBaseConnection.start(JMSBaseConnection.java:247)
         at weblogic.jms.adapter.JMSManagedConnectionFactory.createManagedConnection(JMSManagedConnectionFactory.java:190)
         at weblogic.connector.security.layer.AdapterLayer.createManagedConnection(AdapterLayer.java:802)
         at weblogic.connector.outbound.ConnectionFactory.createResource(ConnectionFactory.java:91)
         at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1180)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:395)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:332)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:315)
         at weblogic.connector.outbound.ConnectionPool.reserveResource(ConnectionPool.java:596)
         at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:309)
         at weblogic.connector.outbound.ConnectionManagerImpl.getConnectionInfo(ConnectionManagerImpl.java:352)
         at weblogic.connector.outbound.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:307)
         at weblogic.connector.outbound.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:115)
         at weblogic.jms.adapter.JMSBaseConnectionFactory.getTargetConnection(JMSBaseConnectionFactory.java:123)
         at weblogic.jms.bridge.internal.MessagingBridge.getConnections(MessagingBridge.java:860)
         at weblogic.jms.bridge.internal.MessagingBridge.run(MessagingBridge.java:1051)
         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.net.ConnectException: t3s://172.16.2.25:4936: Destination unreachable; nested exception is:
         javax.net.ssl.SSLKeyException: [Security:090477]Certificate chain received from 172.16.2.25 - 172.16.2.25 was not trusted causing SSL handshake failure.; No available router to destination
         at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:216)
         at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:170)
         at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
         at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:352)
         ... 28 more
    Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
         javax.net.ssl.SSLKeyException: [Security:090477]Certificate chain received from 172.16.2.25 - 172.16.2.25 was not trusted causing SSL handshake failure.; No available router to destination
         at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:464)
         at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:315)
         at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:251)
         at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:194)
         at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:238)
         at weblogic.rjvm.RJVMFinder.findOrCreateInternal(RJVMFinder.java:200)
         ... 31 more
    )>
    ####<Oct 12, 2011 4:11:49 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416109479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
    ####<Oct 12, 2011 4:11:50 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416110055> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
    ####<Oct 12, 2011 4:11:50 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416110479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
    ####<Oct 12, 2011 4:11:51 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416111055> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
    ####<Oct 12, 2011 4:11:51 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416111479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
    ####<Oct 12, 2011 4:11:52 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416112055> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
    ####<Oct 12, 2011 4:11:52 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416112479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
    ####<Oct 12, 2011 4:11:53 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416113055> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
    ####<Oct 12, 2011 4:11:53 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416113479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
    ####<Oct 12, 2011 4:11:54 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416114055> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
    ####<Oct 12, 2011 4:11:54 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416114479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
    ####<Oct 12, 2011 4:11:55 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416115051> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
    ####<Oct 12, 2011 4:11:55 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416115479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
    ####<Oct 12, 2011 4:11:56 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416116055> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
    ####<Oct 12, 2011 4:11:56 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416116479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
    ####<Oct 12, 2011 4:11:57 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416117055> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
    ####<Oct 12, 2011 4:11:57 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416117479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
    ####<Oct 12, 2011 4:11:58 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416118055> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
    ####<Oct 12, 2011 4:11:58 PM IST> <Debug> <MessagingBridgeRuntimeVerbose> <GLLNX01> <AdminServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1318416118479> <BEA-000000> <Bridge Bridge-0 doTrigger(): state = 2 stopped = false>
    Thanks in advance.

    Think this can help you on the way - http://blog.eisele.net/2010/06/weblogic-server-ssl-httpst3s-and-java.html

  • Weblogic 9.1 X.509 UserName Mapper and T3S

    Why doesn't our custom User Name mapper class fire when using the T3S protocol? It works when we use HTTPS however when we use T3S it will not fire. We have tested this on both UNIX and WINDOWS platforms. Also, we do have a BEA strong encryption license.
    Our server is configure such that on SSL Client Certificates are Requested and Enforced. We have looked at the ssl debug on both an HTTPS and T3S connection and both look good.
    Any help is appreciated.
    Thanks,
    Rob

    Weblogic 9.x supports only JDK 1.5 ? Now, Iam trying to perform same build using Weblogic 8.1 SP5 and Iam not able to find javax.jms.ConnectionFactory in weblogic.jar, where as in Weblogic 9.x 'weblogic.jar' javax.jms.ConnectionFactory' is found.
    code snippet:
    String url = "t3://" + hostName + ":" + hostPort;
    Environment environment = new Environment();
    environment.setProviderUrl( url );
    environment.setInitialContextFactory( weblogic.jndi.WLInitialContextFactory );
    Context context = environment.getInitialContext();
    ConnectionFactory factory = (ConnectionFactory)context.lookup( "..." );
    Connection theConnection = factory.createConnection();
    Iam using SUN JDK 1.4.2.11 ( even did try Weblogic JDK). I have weblogic.jar and JDK/tools.jar included in my classpath.
    What other jar files we need to included in my classpath to make this code to work in weblogic 8.1SP5 ?

  • Weblogic.socket.MaxMessageSizeExceededException from T3S in SSLFIlter

    We are seeing stack traces that complain about 10MB message sizes on the
    T3S protocol stream. These stack traces go to standard out and are not
    recorded in the Weblogics Server all.log and they are not time stamped.
    Is this a bug in the native code of the socket muxer perhaps ?
    We are running WL 6.1 sp1 with Oracle 8i using the thin Oracle 8.1.7
    driver all running in a Sun 1.3.1_02 JVM on Red Hat Linux release 6.2
    (Zoot). We do send a lot of JMS messages between the client and the
    server over T3S, most of these messages are pretty small ( <100 bytes ).
    Any ideas or help or patches appreciated, thanks.
    weblogic.socket.MaxMessageSizeExceededException: [Incoming message of
    size 10000022 bytes exceeds the configured maximum of 10000000 bytes for
    T3S protocol]
    at
    weblogic.socket.SSLFilter.incrementBufferOffset(SSLFilter.java:160)
    at
    weblogic.socket.PosixSocketMuxer.readBytesProblem(PosixSocketMuxer.java:528)
    at
    weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:446)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:378)
    at
    weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Tim Farrell Laurel Networks, Inc

    Do contact customer support.
    Meanwhile tune up your "MaxT3MessageSize" setting on your server
    to 2000000000 (the max value) - which should defer the problem
    by a factor of 200. Or give https a shot instead (this is of course slower).
    Timothy Farrell wrote:
    We are seeing stack traces that complain about 10MB message sizes on the
    T3S protocol stream. These stack traces go to standard out and are not
    recorded in the Weblogics Server all.log and they are not time stamped.
    Is this a bug in the native code of the socket muxer perhaps ?
    We are running WL 6.1 sp1 with Oracle 8i using the thin Oracle 8.1.7
    driver all running in a Sun 1.3.1_02 JVM on Red Hat Linux release 6.2
    (Zoot). We do send a lot of JMS messages between the client and the
    server over T3S, most of these messages are pretty small ( <100 bytes ).
    Any ideas or help or patches appreciated, thanks.
    weblogic.socket.MaxMessageSizeExceededException: [Incoming message of
    size 10000022 bytes exceeds the configured maximum of 10000000 bytes for
    T3S protocol]
    at
    weblogic.socket.SSLFilter.incrementBufferOffset(SSLFilter.java:160)
    at
    weblogic.socket.PosixSocketMuxer.readBytesProblem(PosixSocketMuxer.java:528)
    at
    weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:446)
    at
    weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:378)
    at
    weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Tim Farrell Laurel Networks, Inc

  • WebLogic 8 WebSphere 6.0.1 - T3S - NoClassDefFound

    Hi,
    Im using WebSphere 6.0.1 as a client and WebLogic 8.1 as my server. I want to connect to weblogic with t3s-protocol.
    As a standalone, not running on websphere, the connection works fine. But if I include my client to a WebSphere Portlet, I get the following error:
    [13.12.07 16:00:07:510 CET] 00000072 ServletWrappe E SRVE0068E: Die Methode service() für das Servlet StaticContentPortlet konnte nicht aufgerufen werden. Ausgelöste Ausnahme: java.lang.NoClassDefFoundError: weblogic/jndi/WLInitialContextFactoryDelegate
         at weblogic.jndi.Environment.getContext(Environment.java:166)
         at weblogic.jndi.Environment.getInitialContext(Environment.java:145)
         at com.test.t3s.TwoWaySSL.init(Unknown Source)
         at com.test.portlet.StaticContentPortlet.doView(Unknown Source)
         at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:235)
         at javax.portlet.GenericPortlet.render(GenericPortlet.java:163)
         at com.ibm.wps.pe.pc.std.cmpf.impl.PortletFilterChainImpl.render(PortletFilterChainImpl.java:144)
         at com.ibm.wps.pe.pc.std.invoker.impl.PortletServlet.dispatch(PortletServlet.java:130)
         at com.ibm.wps.pe.pc.std.invoker.impl.PortletServlet.doGet(PortletServlet.java:69)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
         at com.ibm.wps.pe.pc.std.cache.CacheablePortlet.service(CacheablePortlet.java:393)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1572)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java(Compiled Code))
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.include(WebAppRequestDispatcher.java:670)
         at com.ibm.wps.pe.pc.std.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:204)
         at com.ibm.wps.pe.pc.std.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:168)
         at com.ibm.wps.pe.pc.std.invoker.impl.PortletInvokerImpl.render(PortletInvokerImpl.java:97)
         at com.ibm.wps.pe.pc.std.PortletContainerImpl.renderPortlet(PortletContainerImpl.java:110)
         at com.ibm.wps.pe.pc.PortletContainerImpl.doRenderPortlet(PortletContainerImpl.java:587)
         at com.ibm.wps.pe.ext.render.AbstractRenderManager.performService(AbstractRenderManager.java:247)
         at com.ibm.wps.pe.pc.PortletContainerImpl.renderPortlet(PortletContainerImpl.java:115)
         at com.ibm.wps.engine.tags.PortletRenderTag.doStartTag(PortletRenderTag.java:161)
         at com.ibm._jsp._Control._jspx_meth_portal$1skin_portletRender_0(_Control.java:953)
         at com.ibm._jsp._Control._jspx_meth_portal$1logic_if_4(_Control.java:985)
         at com.ibm._jsp._Control._jspService(_Control.java:582)
    Has somebody an idea, why it runs as a standalone version and why it is not running on WebSphere as a portlet?
    Thanks sebbay

    Sebastian Bayerlein <> writes:
    You should use IIOP in this instance. Trying to use the full WL client
    is only going to lead to this sort of problem. Support have an
    interoperability document for setting this kind of thing up, you
    should probably ask for it.
    andy
    Hi,
    Im using WebSphere 6.0.1 as a client and WebLogic 8.1 as my server. I want to connect to weblogic with t3s-protocol.
    As a standalone, not running on websphere, the connection works fine. But if I include my client to a WebSphere Portlet, I get the following error:
    [13.12.07 16:00:07:510 CET] 00000072 ServletWrappe E SRVE0068E: Die Methode service() für das Servlet StaticContentPortlet konnte nicht aufgerufen werden. Ausgelöste Ausnahme: java.lang.NoClassDefFoundError: weblogic/jndi/WLInitialContextFactoryDelegate
         at weblogic.jndi.Environment.getContext(Environment.java:166)
         at weblogic.jndi.Environment.getInitialContext(Environment.java:145)
         at com.test.t3s.TwoWaySSL.init(Unknown Source)
         at com.test.portlet.StaticContentPortlet.doView(Unknown Source)
         at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:235)
         at javax.portlet.GenericPortlet.render(GenericPortlet.java:163)
         at com.ibm.wps.pe.pc.std.cmpf.impl.PortletFilterChainImpl.render(PortletFilterChainImpl.java:144)
         at com.ibm.wps.pe.pc.std.invoker.impl.PortletServlet.dispatch(PortletServlet.java:130)
         at com.ibm.wps.pe.pc.std.invoker.impl.PortletServlet.doGet(PortletServlet.java:69)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:743)
         at com.ibm.wps.pe.pc.std.cache.CacheablePortlet.service(CacheablePortlet.java:393)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:856)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.service(ServletWrapper.java:1572)
         at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java(Compiled Code))
         at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.include(WebAppRequestDispatcher.java:670)
         at com.ibm.wps.pe.pc.std.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:204)
         at com.ibm.wps.pe.pc.std.invoker.impl.PortletInvokerImpl.invoke(PortletInvokerImpl.java:168)
         at com.ibm.wps.pe.pc.std.invoker.impl.PortletInvokerImpl.render(PortletInvokerImpl.java:97)
         at com.ibm.wps.pe.pc.std.PortletContainerImpl.renderPortlet(PortletContainerImpl.java:110)
         at com.ibm.wps.pe.pc.PortletContainerImpl.doRenderPortlet(PortletContainerImpl.java:587)
         at com.ibm.wps.pe.ext.render.AbstractRenderManager.performService(AbstractRenderManager.java:247)
         at com.ibm.wps.pe.pc.PortletContainerImpl.renderPortlet(PortletContainerImpl.java:115)
         at com.ibm.wps.engine.tags.PortletRenderTag.doStartTag(PortletRenderTag.java:161)
         at com.ibm._jsp._Control._jspx_meth_portal$1skin_portletRender_0(_Control.java:953)
         at com.ibm._jsp._Control._jspx_meth_portal$1logic_if_4(_Control.java:985)
         at com.ibm._jsp._Control._jspService(_Control.java:582)
    Has somebody an idea, why it runs as a standalone version and why it is not running on WebSphere as a portlet?
    Thanks sebbay

  • Best practice for OSB to OSB communication

    Cross posting this message:
    I am currently in a project where we have two OSB that have to communicate. The OSBs are located in different security zones ("internal" and "secure"). All communication on a network level must be initiated from the secure zone to the internal zone. The message flow should be initated from the internal zone to the secure zone. Ideally we should establish a tcp connection from the secure zone to the internal zone, and then use SOAP over HTTP on this pre-established connection. Is this at all possible?
    Our best approach now, is to establish a jms-queue in the internal zone and let both OSBs connect to this. All communication between the zone is then done over JMS. This is an approach that would work, but is it the only solution?
    Can the t3/t3s protocol be used to achieve our goal? I.e. To have synchronous commincation over a pre-established connection (that is established the in opposite direction of the communication)?
    Is there any other approach that might work?
    What is considered best practice for sending messages from a OSB to another OSB in a more secure zone?
    Edited by: hilmersen on 11.jun.2009 00:59

    Hi,
    In my experience in a live project, we have used secured communication (https) between internal service bus and DMZ/external service bus.
    We also used two way SSL with customers.
    The ports were also secured by firewall in between them.
    If you wish more details, please email [email protected]
    Ganapathi.V.Subramanian[VG]
    Sydney, Australia
    Edited by: Ganapathi.V.Subramanian[VG] on Aug 28, 2009 10:50 AM

  • BEA-141151 The admin server could not be reached at ...

    I have been at this for 3 days now... I created a new ManagedServer, but I'm not able to make it connect to the Admin server.
    The Admin server is running and listening on port 5306. I can connect to the Admin Console (web).
    I can also connect to the Admin server via WLST, using this command: connect('operator','operator01','t3://localhost:5306')
    However, when I try to run the managed server from a script, it does not see the Admin server. This is the command I run:
    java -Dweblogic.Name=ManSer1 -Dweblogic.management.server=t3://localhost:5306 -Dweblogic.RootDirectory=<path to my domain> weblogic.Server
    This is the error I get:
    <BEA-141151> <The admin server could not be reached at http://localhost:5306.>
    I believe it's trying to connect using "http", because I've never actually connected in the past. Here is a website explaining this: http://download.oracle.com/docs/cd/E17904_01/web.1111/e13749/weblogicserver.htm#i1031832
    Note: Regardless of which protocol you specify, the initial download of a Managed Server's configuration is over HTTP or HTTPS. After the RMI subsystem initializes, the server instance can use the T3 or T3S protocol.
    I'm not sure what else to try... Firewalls are not in play, since this is traffic moving around on the local machine. I'm running on SunOS. Weblogic is version 9.2 MP3.
    Appreciate any help.

    Is the NodeManager , AdminServer running ?The NodeManager is not running. Is it required?
    Also, I haven't closed the command prompt.
    I noticed the issue when I tried to deploy my project. Connected to Localhost/7001 but in the deploy project window, I dont see any soa_server instance
    running. Also, in the console the soa_server status is shutdown.

  • Webstart  unable to find the Bea licence file

    Hi All,
    We are using an web application with weblogic server and webstart. We are currently trying to convert the application from T3 to T3s protocol. For this we require the license.bea file to be set in the client side class path.
    When i place this license.bea in the download directory of the webstart (where all signed the jar's and .jnlp file is downloaded) and launch the .jnlp file,it works.But when the .jnlp file is called throug the application it fails to locate the license file. error message:
    <<Missing license file for: WebLogic Platform 8.1>>
    The .jnlp file is as below :
    <?xml version="1.0" encoding="UTF-8"?>
    <jnlp codebase="http://dbnexus.int.risk.db.com:80/webstart/" href="launch.jnlp" spec="1.0+">
    <information>
    <vendor>GRT</vendor>
    <homepage href="index.html"/>
    <description kind="short">Client for dbNexus reference data management system</description>
    <description kind="one-line">dbNexus client</description>
    <description kind="tooltip">dbNexus client</description>
    <title>dbNexus Client ( INT )</title>
    </information>
    <security>
    <all-permissions/>
    </security>
    <property name="bea.home" value=".\"/>
    <property name="weblogic.security.SSL.ignoreHostnameVerification" value="true"/>
    <property name="weblogic.security.SSL.trustedCAKeyStore" value=".\DAPTrust.jks"/>
    <property name="weblogic.security.SSL.trustedCAKeyStorePassPhrase" value="trustpassword"/>
    <resources>
    <j2se initial-heap-size="512M" max-heap-size="1024M" version="1.4+"/>
    <jar download="eager" href="dbnApplet.jar"/>
    <jar download="eager" href="xmlParserAPIs.jar"/>
    <jar download="eager" href="xercesImpl.jar"/>
    <jar download="eager" href="log4j-1.2.3.jar"/>
    <jar download="eager" href="utils.jar"/>
    <jar download="eager" href="weblogic.jar"/>
    <jar download="eager" href="dbnexus-ejb-compiled.jar"/>
    <jar download="eager" href="wlcipher.jar"/>
    </resources>
    <application-desc main-class="dbnexus.client.applet.appletwrapper.MainFrame">
    <argument>http://dbnexus.int.risk.db.com:80/webstart//dbnexus.properties</argument>
    </application-desc>
    </jnlp>
    In the above code i have specified the Bea.home as .\ so that it picks up the license from the same directory. We do not want to place the file at other place and hard code the path in the code as the path might differ in different systems where the application will be downloaded.
    Is there any way by which we can achive the above. Is it possible to place the .bea file inside any jar and access it from the same. Please advice.
    Thaks in advance....
    Regards,
    Ravi

    The problem is,the appliaction is not able to find
    the license file from within the .Jar.
    is set the property as :
    Dbea.home="c:/Documents and Settings/All
    Users/Application
    Data/JavaCache/http/Ddbnexus.int.risk.db.com/P80/DMweb
    start/" and it works
    But if i giv the path of the jar file it does not :
    -Dbea.home="c:/Documents and Settings/All
    Users/Application
    Data/JavaCache/http/Ddbnexus.int.risk.db.com/P80/DMweb
    start/RMwlcipher.jar!/license.bea"
    How can i make the licence file insidethe .jar file
    readable by the application ?
    Or is there any way by which i can download the .bea
    file to the webstart catch(I.e the download
    directory). I am able to download the .jar using
    <resources>
    <jar href="wlcipher.jar" download="eager"/>
    </resources>
    Please advice.........
    Ravi
    The problem is,the appliaction is not able to find
    the license file from within the .Jar.
    That is because there is no such "file" on the client machine.
    c:/Documents and Settings/.../DMwebstart/RMwlcipher.jar!/license.bea"
    is not a path at all. (notice the "!" between the jar and the file in it.)
    After you call getResource you have a valid url to the file, but URL.getPath() will not return a "path" that can be used by the file system.
    You have to open a URLConnection to that URL and read the stream that is the file contents, and store it as a file somewhere on the filesystem.
    (Instead of getResource(), you can just use getResourceAsStream())
    /Andy

  • OSB Federation and establishing connections

    I am currently in a project where we have two OSB that have to communicate. The OSBs are located in different security zones ("internal" and "secure"). All communication on a network level must be initiated from the secure zone to the internal zone. The message flow should be initated from the internal zone to the secure zone. Ideally we should establish a tcp connection from the secure zone to the internal zone, and then use SOAP over HTTP on this pre-established connection. Is this at all possible?
    Our best approach now, is to establish a jms-queue in the internal zone and let both OSBs connect to this. All communication between the zone is then done over JMS. This is an approach that would work, but is it the only solution?
    Can the t3/t3s protocol be used to achieve our goal? I.e. To have synchronous commincation over a pre-established connection (that is established the in opposite direction of the communication)?
    Is there any other approach that might work?
    Christian Hilmersen

    Check the javadoc for ALSBConfigurationMBean
    This has sample code as well.
    regards,
    ~Krithika

  • Secure communication for JMS

    How to enable secure transfer of JMS Messages possibly using SSL ?
    a. JMS messages from client to Queue/Topic
    b. Queue/Topic to MDB
    One options seems to be using t3s instead of t3 ? Is this correct ?
    If we use EJB3 resource injections for initializing JMS connection factories and Destinations, then how can we configure the app to use t3s protocol instead of t3.
    Thanks
    -Siva

    In SM59 open up a RFC destination and go to Logon & Security. There you can enable Trusted relashionship and activate status of secure protocol.
    And yes you have to do it manually for the desired RFC's

  • WLST connects rarely

    Guys,
    I am seeing this weired issue in my environment. I want to connect to Admin server to do any configuration. But It use to connects all the time. But right now it rarely connects to admin server.
    Admin Server Host is the same where the wlst is running. Same physical box.
    Dont know whats going on: Again the server is running all the time and connection can be made once in 30-40 times.
    javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3s://mydomain:7001: Destination unreachable; nested exception is:
    java.io.IOException: Stream closed.; No available router to destination]
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:365)
    at weblogic.jndi.Environment.getContext(Environment.java:315)
    at weblogic.jndi.Environment.getContext(Environment.java:285)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
    at javax.naming.InitialContext.init(InitialContext.java:223)
    at javax.naming.InitialContext.<init>(InitialContext.java:197)
    at weblogic.management.scripting.WLSTHelper.populateInitialContext(WLSTHelper.java:512)
    at weblogic.management.scripting.WLSTHelper.initDeprecatedConnection(WLSTHelper.java:565)
    at weblogic.management.scripting.WLSTHelper.initConnections(WLSTHelper.java:305)
    at weblogic.management.scripting.WLSTHelper.connect(WLSTHelper.java:203)
    at weblogic.management.scripting.WLScriptContext.connect(WLScriptContext.java:60)
    at weblogic.management.scripting.utils.WLSTUtil.initializeOnlineWLST(WLSTUtil.java:125)
    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:597)
    at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160)
    at org.python.core.PyMethod.__call__(PyMethod.java:96)
    at org.python.core.PyObject.__call__(PyObject.java:248)
    at org.python.core.PyObject.invoke(PyObject.java:2016)
    at org.python.pycode._pyx4.connect$1(<iostream>:16)
    at org.python.pycode._pyx4.call_function(<iostream>)
    at org.python.core.PyTableCode.call(PyTableCode.java:208)
    at org.python.core.PyTableCode.call(PyTableCode.java:404)
    at org.python.core.PyTableCode.call(PyTableCode.java:287)
    at org.python.core.PyFunction.__call__(PyFunction.java:179)
    at org.python.pycode._pyx16.connectIfNecessary$7(/usr/local/admintools/jmsscripts/PDjmsselectorRMTCAQueue.py:254)
    at org.python.pycode._pyx16.call_function(/usr/local/admintools/jmsscripts/PDjmsselectorRMTCAQueue.py)
    at org.python.core.PyTableCode.call(PyTableCode.java:208)
    at org.python.core.PyTableCode.call(PyTableCode.java:267)
    at org.python.core.PyFunction.__call__(PyFunction.java:172)
    at org.python.pycode._pyx16.f$0(/usr/local/admintools/jmsscripts/PDjmsselectorRMTCAQueue.py:299)
    at org.python.pycode._pyx16.call_function(/usr/local/admintools/jmsscripts/PDjmsselectorRMTCAQueue.py)
    at org.python.core.PyTableCode.call(PyTableCode.java:208)
    at org.python.core.PyCode.call(PyCode.java:14)
    at org.python.core.Py.runCode(Py.java:1135)
    at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:167)
    at weblogic.management.scripting.WLST.main(WLST.java:129)
    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:597)
    at weblogi

    I think I solved the issue. We are using t3s protocol to connect. somehting might have been changes in network that we started seeing the delays. I have increased the default size of SSL Login timeout in weblogic from 25000 ms to 65000 ms I have tried several times and got successfull which was not possible before. So looks like something in tcp has changed which blow up my connection.

  • Oracle Service Bus, calling ejb on ormi protocol

    Hi.
    I'm trying to call an EJB on a Oracle Application server on the ormi protocol, but when i try to call it, I get this error:
    <con:fault xmlns:con="http://www.bea.com/wli/sb/context">
    <con:errorCode>BEA-380000</con:errorCode>
    <con:reason>
    General runtime error: Error accessing the JNDI context for the EJB call: java.net.UnknownHostException: Unknown protocol: 'ORMI'
    </con:reason>
    <con:location>
    <con:node>PipelinePairNode1</con:node>
    <con:pipeline>PipelinePairNode1_request</con:pipeline>
    <con:stage>stage1</con:stage>
    <con:path>request-pipeline</con:path>
    </con:location>
    </con:fault>
    I have my business service referencing a local jndi provider which in turn points to the remote server, on the ormi protocol.
    Could I be missing some libraries?

    I have my business service referencing a local jndi provider which in turn points to the remote server, on the ormi protocol.
    Could I be missing some libraries?EJB transport doesn't support ORMI. Protocols supported by JNDI Provider resource are documented. Click help on you JNDI provider page.
    supported protocols : http, https,t3, t3s, iiop,iiops.
    Only BPEL transport supports ORMI (http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/bpelpmtransport/transport.html)
    cheers
    Manoj
    Edited by: mneelapu on Jun 8, 2009 2:39 PM

  • Using t3s with applets

    Hi -
    We have a few applets accessing EJB's on WebLogic 5.1 (SP 6) which utilize
    "t3" as the protocol and don't have any problem getting Contexts and issuing
    requests. However, once we switch to t3s, we get an error indicating that
    the server can't be found at t3s://myserver:443. This is not a firewall
    problem (we've tested it with no firewall in place), nor does it appear to
    be a certificate problem (WL server is running in 128-bit mode with a valid
    cert, etc.) Does anyone have any experience running applets and WL,
    particularly over t3s? I've included a stack trace below. Thanks in
    advance -
    Andy
    [email protected]
    =========================
    javax.naming.CommunicationException. Root exception is
    java.net.ConnectException: No server found at T3S://myserver:443
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:161)
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:200)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
    textFactoryDelegate.java:195)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
    textFactoryDelegate.java:148)
    at
    weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
    ory.java:123)
    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)
    [applet call stack goes here]
    at sun.applet.AppletPanel.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)

    FYI, I believe we have a legitimate fix, but we're still waiting for an
    official stance from WL. The "fix" we've implemented includes the previously
    mentioned workaround, plus the layering of SP8 weblogic.security package on
    top of SP6.
    Andy
    "Andrew King" <[email protected]> wrote in message
    news:[email protected]...
    Hi -
    It appears there's a bug with WL's RSA classes in SP6 (RSAKey, RSApkcs1),
    128-bit vesion. We've hacked a couple of fixes which appear to work, butI'm
    wondering if anyone else can confirm this. Thanks -
    Andy
    "Andrew King" <[email protected]> wrote in message
    news:[email protected]...
    Hi -
    We have a few applets accessing EJB's on WebLogic 5.1 (SP 6) which
    utilize
    "t3" as the protocol and don't have any problem getting Contexts andissuing
    requests. However, once we switch to t3s, we get an error indicating
    that
    the server can't be found at t3s://myserver:443. This is not a firewall
    problem (we've tested it with no firewall in place), nor does it appearto
    be a certificate problem (WL server is running in 128-bit mode with avalid
    cert, etc.) Does anyone have any experience running applets and WL,
    particularly over t3s? I've included a stack trace below. Thanks in
    advance -
    Andy
    [email protected]
    =========================
    javax.naming.CommunicationException. Root exception is
    java.net.ConnectException: No server found at T3S://myserver:443
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:161)
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:200)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
    textFactoryDelegate.java:195)
    at
    weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
    textFactoryDelegate.java:148)
    at
    weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
    ory.java:123)
    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)
    [applet call stack goes here]
    at sun.applet.AppletPanel.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)

  • Can not connect to ther admin server with t3s in the WLST

    Hi,
    Our server face a strange problem.
    We want to add SSL to our server, and I have set the SSL linsten port enabled, an we can access the admin console with https protocol and SSL listen port.
    Then I want to manage the server with
    ##start WLST with DemoTrust enable
    java -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.security.TrustKeyStore=DemoTrust weblogic.WLST
    ##connect
    If I use
    connect('system','testAdmin','t3://xxxx:10001')
    ##this can connect successful.
    If I use
    connect('system','testAdmin','t3s://xxxx:10002')
    It will cause an error
    WLSTException: Error occured while performing connect : Error getting the initial context. There is no server running at t3s://xxxx:10002 Use dumpStack() to view the full stacktrace
    I both enabled plain and SSL listen port and I can access the admin console with http and https without problem. But why I just can not use t3s to connect the server in the WLST? Is there any setting related this? Please advise, thanks.
    Here is the dumpStack()
    javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3s://xxxx:10002: Destination unreachable; nested exception is:
            java.io.IOException: Stream closed.; No available router to destination]
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:365)
    at weblogic.jndi.Environment.getContext(Environment.java:315)
    at weblogic.jndi.Environment.getContext(Environment.java:285)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
    at javax.naming.InitialContext.init(InitialContext.java:223)
    at javax.naming.InitialContext.<init>(InitialContext.java:197)
    at weblogic.management.scripting.WLSTHelper.populateInitialContext(WLSTHelper.java:512)
    at weblogic.management.scripting.WLSTHelper.initDeprecatedConnection(WLSTHelper.java:565)
    at weblogic.management.scripting.WLSTHelper.initConnections(WLSTHelper.java:305)
    at weblogic.management.scripting.WLSTHelper.connect(WLSTHelper.java:203)
    at weblogic.management.scripting.WLScriptContext.connect(WLScriptContext.java:60)
    at weblogic.management.scripting.utils.WLSTUtil.initializeOnlineWLST(WLSTUtil.java:125)
    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:597)
    at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160)
    at org.python.core.PyMethod.__call__(PyMethod.java:96)
    at org.python.core.PyObject.__call__(PyObject.java:248)
    at org.python.core.PyObject.invoke(PyObject.java:2016)
    at org.python.pycode._pyx4.connect$1(<iostream>:16)
    at org.python.pycode._pyx4.call_function(<iostream>)
    at org.python.core.PyTableCode.call(PyTableCode.java:208)
    at org.python.core.PyTableCode.call(PyTableCode.java:404)
    at org.python.core.PyTableCode.call(PyTableCode.java:287)
    at org.python.core.PyFunction.__call__(PyFunction.java:179)
    at org.python.pycode._pyx15.f$0(<console>:1)
    at org.python.pycode._pyx15.call_function(<console>)
    at org.python.core.PyTableCode.call(PyTableCode.java:208)
    at org.python.core.PyCode.call(PyCode.java:14)
    at org.python.core.Py.runCode(Py.java:1135)
    at org.python.core.Py.exec(Py.java:1157)
    at org.python.util.PythonInterpreter.exec(PythonInterpreter.java:148)
    at org.python.util.InteractiveInterpreter.runcode(InteractiveInterpreter.java:89)
    at org.python.util.InteractiveInterpreter.runsource(InteractiveInterpreter.java:70)
    at org.python.util.InteractiveInterpreter.runsource(InteractiveInterpreter.java:44)
    at weblogic.management.scripting.WLST.main(WLST.java:178)
    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:597)
    at weblogic.WLST.main(WLST.java:29)
    Caused by: java.net.ConnectException: t3s://xxxx:10002: Destination unreachable; nested exception is:
    java.io.IOException: Stream closed.; No available router to destination
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:203)
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
    at weblogic.jndi.WLInitialContextFactoryDelegate$1.run(WLInitialContextFactoryDelegate.java:344)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:339)
    ... 43 more
    Caused by: java.rmi.ConnectException: Destination unreachable; nested exception is:
    java.io.IOException: Stream closed.; No available router to destination
    at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:464)
    at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:315)
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:251)
    at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:194)
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:225)
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:188)
    ... 48 more
    Edited by: Kaos on Feb 25, 2010 12:06 AM

    Jai/Faisal,
    One strange thing i observe, i tried connecting to admin server through WLST, it works for first time and again it gave me the error next (Connecting alternatively).
    the error message which i am getting:
    This Exception occurred at Thu Jun 10 08:19:39 CDT 2010.
    javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3s://mo8xdwls0018.bankofamerica.com:8933: Destination unreachable; nested exception is:
            java.io.IOException: Stream closed.; No available router to destination]
    at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
    at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:365)
    at weblogic.jndi.Environment.getContext(Environment.java:315)
    at weblogic.jndi.Environment.getContext(Environment.java:285)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
    at javax.naming.InitialContext.init(InitialContext.java:223)
    at javax.naming.InitialContext.<init>(InitialContext.java:197)
    at weblogic.management.scripting.WLSTHelper.populateInitialContext(WLSTHelper.java:512)
    at weblogic.management.scripting.WLSTHelper.initDeprecatedConnection(WLSTHelper.java:565)
    at weblogic.management.scripting.WLSTHelper.initConnections(WLSTHelper.java:305)
    at weblogic.management.scripting.WLSTHelper.connect(WLSTHelper.java:203)
    at weblogic.management.scripting.WLScriptContext.connect(WLScriptContext.java:60)
    at weblogic.management.scripting.utils.WLSTUtil.initializeOnlineWLST(WLSTUtil.java:125)
    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:597)
    at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160)
    at org.python.core.PyMethod.__call__(PyMethod.java:96)
    we are connecting to t3s://mo8xdwls0018.bankofamerica.com:8933.
    Any help would be appreciated.
    -Vishal Iyer

Maybe you are looking for