Error getting initial context

Hi,
I've gotten the following exceptions reported to us by our production clients when trying to connect to our Weblogic 4.5.1 server (sp8).
CPClient with url: t3s://www.cpmarket.com:7002 Getting guest initial
context
[Root exception is java.io.IOException: Bootstrap unable to get a t3s
connection to
www.cpmarket.com/159.43.253.15]javax.naming.CommunicationException at
weblogic.jndi.toolkit.ExceptionTranslator.toNamingException(ExceptionTransla
tor.java:32) at
weblogic.jndi.WLInitialContextFactory.toNamingException(WLInitialContextFact
ory.java:513) at
weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
ory.java, Compiled Code) at
weblogic.jndi.Environment.getContext(Environment.java:128) at
weblogic.jndi.Environment.getInitialContext(Environment.java:111) at
com.xxxxxxx.CPClient.getGuestInitialContext(CPClient.jav
a:184) at
com.xxxxxxx.CPClient.<init>(CPClient.java:47)
Does anyone know where this could be coming from?
Thanks,
Gary Mui
[email protected]
[att1.html]

Hi Tim,
If you are running within a browser, you will not have access to anything
outside the sandbox which includes making RMI calls. Try signing the applet.
You can find more information on signing applets on the sun java website.
Regards
Arjuna
"Tim" <[email protected]> wrote in message
news:3c5ab818$[email protected]..
>
I get the following eror when I try to get the Initial Context in anapplet:
>
java.lang.ExceptionInInitializerError: java.security.Acc
ess denied (java.util.PropertyPermission * read,write)
atjava.security.AccessControlContext.checkPermission(AccessControlConte
xt.java:272)
atjava.security.AccessController.checkPermission(AccessController.java:
399)
Does anyone have any idea what would cause this? The code works finerunning
from an application. From what I understand there might be a problem withmy
policy file. However, it seems to look ok. Any ideas?

Similar Messages

Error creating initial context with environment

Hi,
Currently we are working on a scenarios, where we need to integrate XI and webmethods using JMS.
It was working fine. But recently they have restarted the webmethods server. After that we re getting an error message like,
In Adapter Monitoring:
Channel error occurred; detailed error description: com.sap.aii.adapter.jms.api.connector.ConnectorException: Error creating initial context with environment: {java.naming.provider.url=server:port, java.naming.factory.initial=com.sap.engine.services.jndi.InitialContextFactoryImpl, java.naming.security.principal=XYZ, java.naming.security.credentials=ABC}for profile: ConnectionProfile of channel: CC_RCV_JMS_INon node: 3010950 having object id: ABCXYZ: NamingException: Error getting the server-side naming service functionality during getInitialContext operation.
at com.sap.aii.adapter.jms.core.connector.JndiConnectorImpl.createInitialContext(JndiConnectorImpl.java:66)
In RWB
MP: Exception caught with cause com.sap.aii.af.ra.ms.api.RecoverableException: No transition found from state: STARTING, on event: process_commence for DFA: C_RCV_JMS_IN:e4413a5265a436459e271d5e0dd4859b
Can one please tell me what the problem is?
Thanks in advance.
Regards,
Prasad Babu.

Hi,
Check this link looks like same problem
Re: file to JMS(for MQ series)
Thanks
Vikranth

Getting initial context using a cluster address

I am having trouble getting initial context using a cluster address. My cluster
has two WL 8.1 servers at localhost:8001 and localhost:9001. I set the hashtable
to get the initial context as follows:
env.put(InitialContext.PROVIDER_URL, "t3://localhost:8001,t3://localhost:9001");
This gives me the following exception:
Could not create JNDI InitialContext: javax.naming.ConfigurationException
[Root exception is java.net.MalformedURLException: port expected: t3://cammnbhati:8001,t3://cammnbhati:9001]
Any idea whey this is not working? If I set only one of the addresses then there
is no error. For example, the following works just fine:
env.put(InitialContext.PROVIDER_URL, "t3://localhost:8001");
Thanks.

try t3://localhost:8001,localhost:9001 as url
hth
sree
"Naresh Bhatia" <[email protected]> wrote in message
news:4009cfdf$[email protected]..
>
I am having trouble getting initial context using a cluster address. Mycluster
has two WL 8.1 servers at localhost:8001 and localhost:9001. I set thehashtable
to get the initial context as follows:
env.put(InitialContext.PROVIDER_URL,"t3://localhost:8001,t3://localhost:9001");
>
This gives me the following exception:
Could not create JNDI InitialContext:javax.naming.ConfigurationException
[Root exception is java.net.MalformedURLException: port expected:
t3://cammnbhati:8001,t3://cammnbhati:9001
Any idea whey this is not working? If I set only one of the addresses thenthere
is no error. For example, the following works just fine:
env.put(InitialContext.PROVIDER_URL, "t3://localhost:8001");
Thanks.

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

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

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

Getting Initial context

Here is some debug output from a simple test I run against a WL6.1
Server. Notice the 35 secs. it takes to get Initial Context.
-- Initializing bean access.
-- Succeeded getting naming context.
-- Execution time: 35047 ms.
-- Succeeded looking up jndi name.
-- Execution time: 453 ms.
-- Succeeded casting Home interface.
-- Execution time: 94 ms.
Second time I run the test from the same machine I get this.
-- Initializing bean access.
-- Succeeded getting naming context.
-- Execution time: 1907 ms.
-- Succeeded looking up jndi name.
-- Execution time: 312 ms.
-- Succeeded casting Home interface.
-- Execution time: 31 ms.
The pattern is consistent. First attempt to get the Initial Context
from any of my client boxes will take about 30 secs more than any
consecutive attempts.
Here is the code for getting the Context:
long startTime = 0;
if (logging) {
     log("Initializing bean access.");
     startTime = System.currentTimeMillis();
try {
     //get naming context
     Context ctx = getInitialContext();
     if (logging) {
          long endTime = System.currentTimeMillis();
          log("Succeeded getting naming context.");
          log("Execution time: " + (endTime - startTime) + " ms.");
          startTime =endTime;
     //look up jndi name
     Object ref = ctx.lookup("DynamicPool");
     if (logging) {
          long endTime = System.currentTimeMillis();
          log("Succeeded looking up jndi name.");
          log("Execution time: " + (endTime - startTime) + " ms.");
          startTime =endTime;
     //cast to Home interface
     dynamicPoolHome = (DynamicPoolHome) PortableRemoteObject.narrow(ref,
DynamicPoolHome.class);
     if (logging) {
          long endTime = System.currentTimeMillis();
          log("Succeeded casting Home interface.");
          log("Execution time: " + (endTime - startTime) + " ms.");
catch(Exception e) {
     if (logging) {
          log("Failed initializing bean access.");
     e.printStackTrace();
Am I missing something here ?
Regards,
Klaus

My first guess would be a DNS problem.
Also, creating an InitialContext loads a fair amount of classes. If you're
loading them over the network, that could also account for the slow-down.
-- Rob
Klaus Preisler wrote:
Here is some debug output from a simple test I run against a WL6.1
Server. Notice the 35 secs. it takes to get Initial Context.
-- Initializing bean access.
-- Succeeded getting naming context.
-- Execution time: 35047 ms.
-- Succeeded looking up jndi name.
-- Execution time: 453 ms.
-- Succeeded casting Home interface.
-- Execution time: 94 ms.
Second time I run the test from the same machine I get this.
-- Initializing bean access.
-- Succeeded getting naming context.
-- Execution time: 1907 ms.
-- Succeeded looking up jndi name.
-- Execution time: 312 ms.
-- Succeeded casting Home interface.
-- Execution time: 31 ms.
The pattern is consistent. First attempt to get the Initial Context
from any of my client boxes will take about 30 secs more than any
consecutive attempts.
Here is the code for getting the Context:
long startTime = 0;
if (logging) {
log("Initializing bean access.");
startTime = System.currentTimeMillis();
try {
//get naming context
Context ctx = getInitialContext();
if (logging) {
long endTime = System.currentTimeMillis();
log("Succeeded getting naming context.");
log("Execution time: " + (endTime - startTime) + " ms.");
startTime =endTime;
//look up jndi name
Object ref = ctx.lookup("DynamicPool");
if (logging) {
long endTime = System.currentTimeMillis();
log("Succeeded looking up jndi name.");
log("Execution time: " + (endTime - startTime) + " ms.");
startTime =endTime;
//cast to Home interface
dynamicPoolHome = (DynamicPoolHome) PortableRemoteObject.narrow(ref,
DynamicPoolHome.class);
if (logging) {
long endTime = System.currentTimeMillis();
log("Succeeded casting Home interface.");
log("Execution time: " + (endTime - startTime) + " ms.");
catch(Exception e) {
if (logging) {
log("Failed initializing bean access.");
e.printStackTrace();
Am I missing something here ?
Regards,
Klaus

Error in getting Initial Context

Hello,
I am facing the following exception while trying to get the Initial Context. Following
is the snippet of code that I use for getting the Context -
Properties p = new Properties();
p.put(Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");p.
put(Context.PROVIDER_URL, url);
if (user != null) {
p.put(Context.SECURITY_PRINCIPAL, user);
if (password == null)
password = "";
p.put(Context.SECURITY_CREDENTIALS, password);
return new InitialContext(p);
The following is the exception that I encounter -
javax.naming.AuthenticationException. Root exception is java.lang.SecurityException:
attempting to add an object which is not an instance of java.security.Principal
to a Subject's Principal Set
Am i missing anything. Thanks for your time.
See the attached file for the details of the exception
Thanks,
Ashutosh
[trace.txt]

Hi Tim,
If you are running within a browser, you will not have access to anything
outside the sandbox which includes making RMI calls. Try signing the applet.
You can find more information on signing applets on the sun java website.
Regards
Arjuna
"Tim" <[email protected]> wrote in message
news:3c5ab818$[email protected]..
>
I get the following eror when I try to get the Initial Context in anapplet:
>
java.lang.ExceptionInInitializerError: java.security.Acc
ess denied (java.util.PropertyPermission * read,write)
atjava.security.AccessControlContext.checkPermission(AccessControlConte
xt.java:272)
atjava.security.AccessController.checkPermission(AccessController.java:
399)
Does anyone have any idea what would cause this? The code works finerunning
from an application. From what I understand there might be a problem withmy
policy file. However, it seems to look ok. Any ideas?

How to get Initial context of Local Interface in weblogic 8.1

I have developed a local entity bean but i wouldnt able to initial context of that bean
CAN ANYBODY HELP ME
bean deployment descriptor
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>

<ejb-jar>
<enterprise-beans>
<entity>
<ejb-name>CabinBean</ejb-name>
<home>my.CabinRemoteHome</home>
<remote>my.CabinRemote</remote>
<ejb-class>my.CabinBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.Integer</prim-key-class>
<reentrant>True</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>CabinBean</abstract-schema-name>
<cmp-field>
<field-name>bedCount</field-name>
</cmp-field>
<cmp-field>
<field-name>deckLevel</field-name>
</cmp-field>
<cmp-field>
<field-name>id</field-name>
</cmp-field>
<cmp-field>
<field-name>name</field-name>
</cmp-field>
<cmp-field>
<field-name>shipId</field-name>
</cmp-field>
<primkey-field>id</primkey-field>
<security-identity>
<use-caller-identity/>
</security-identity>
</entity>
<entity>
<ejb-name>CabinLocal</ejb-name>
<local-home>my.CabinLocalHome</local-home>
<local>my.CabinLocalLocal</local>
<ejb-class>my.CabinLocal</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.Integer</prim-key-class>
<reentrant>True</reentrant>
<cmp-version>2.x</cmp-version>
<abstract-schema-name>CabinLocal</abstract-schema-name>
<cmp-field>
<field-name>bedCount</field-name>
</cmp-field>
<cmp-field>
<field-name>deckLevel</field-name>
</cmp-field>
<cmp-field>
<field-name>id</field-name>
</cmp-field>
<cmp-field>
<field-name>name</field-name>
</cmp-field>
<cmp-field>
<field-name>shipId</field-name>
</cmp-field>
<primkey-field>id</primkey-field>
<ejb-local-ref>
<ejb-ref-name>LocalCabin</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<local-home>CabinLocalHome</local-home>
<local>CabinLocal</local>
<ejb-link>LocalCabin</ejb-link>
</ejb-local-ref>
<security-identity>
<use-caller-identity/>
</security-identity>
</entity>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>CabinLocal</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>CabinBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
<ejb-client-jar>EjbClient</ejb-client-jar>
</ejb-jar>
************************************** Client Code****************
package com;
import my.CabinBean;
import my.CabinRemoteHome;
import my.CabinRemote;
import javax.naming.InitialContext;
import javax.naming.Context;
import javax.naming.NamingException;
import java.rmi.RemoteException;
import java.util.Properties;
import javax.rmi.PortableRemoteObject;
import weblogic.jndi.Environment;
public class Test
    public static void main(String args[])
        try{
             Context context = getInitialContext();
                      Object cab = context.lookup("CabinLocalHome");
            ///**********-- Exception is thrown at this point -******************
            System.out.println("============ done====");
            Context ct = getInitialContext();
            Object ref = ct.lookup("CabinHomeRemote");
            CabinRemoteHome home = (CabinRemoteHome)PortableRemoteObject.narrow(ref,CabinRemoteHome.class);
            //CabinRemote cab = home.create(new Integer(1));
            //cab.setName("Master Suite");
            //cab.setDeckLevel(new Integer(1));
            //cab.setShipId(new Integer(1));
            //cab.setBedCount(new Integer(1));
            Integer pk = new Integer(1);
            CabinRemote cab1 = home.findByPrimaryKey(pk);
            System.out.println("--->>>>>>>> "+cab1.getName());
            System.out.println("--->>>>>>>> "+cab1.getShipId());
            System.out.println("--->>>>>>>>"+cab1.getBedCount());
            System.out.println("--->>>>>>>>"+cab1.getDeckLevel());
            System.out.println("---");
      }catch(java.rmi.RemoteException e){e.printStackTrace();}
       catch(javax.naming.NamingException e){e.printStackTrace();}
       //catch(javax.ejb.CreateException e){e.printStackTrace();}
       catch(javax.ejb.FinderException e){e.printStackTrace();}
    public static Context getInitialContext() throws javax.naming.NamingException
       Properties p = new Properties();
       p.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFactory");
       p.put(Context.PROVIDER_URL,"t3://localhost:7001");
       return new javax.naming.InitialContext(p);
} ************************************** Error ***********************
javax.naming.LinkException: [Root exception is javax.naming.LinkException: [Root exception is javax.naming.NameNotFoundException: remaining name: /app/ejb/myejb.jar#CabinLocal/local-home]; Link Remaining Name: 'null']; Link Remaining Name: 'java:app/ejb/myejb.jar#CabinLocal/local-home'
     at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:284)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:244)
     at weblogic.jndi.internal.ServerNamingNode_813_WLStub.lookup(Unknown Source)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:369)
     at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:357)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at com.Test.main(Test.java:27)
Caused by: javax.naming.LinkException: [Root exception is javax.naming.NameNotFoundException: remaining name: /app/ejb/myejb.jar#CabinLocal/local-home]; Link Remaining Name: 'null'
     at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:98)
     at weblogic.jndi.internal.ServerNamingNode.resolveObject(ServerNamingNode.java:292)
     at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:771)
     at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:191)
     at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
     at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)
Caused by: javax.naming.NameNotFoundException: remaining name: /app/ejb/myejb.jar#CabinLocal/local-home
     at weblogic.j2eeclient.SimpleContext.resolve(SimpleContext.java:35)
     at weblogic.j2eeclient.SimpleContext.resolve(SimpleContext.java:39)
     at weblogic.j2eeclient.SimpleContext.lookup(SimpleContext.java:57)
     at weblogic.j2eeclient.SimpleContext.lookup(SimpleContext.java:62)
     at weblogic.jndi.factories.java.ReadOnlyContextWrapper.lookup(ReadOnlyContextWrapper.java:45)
     at weblogic.jndi.internal.AbstractURLContext.lookup(AbstractURLContext.java:130)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:96)

Hi,
from what I gather, u have two jars
1. EJBClient - this will have remote and home interfaces and will be used by the client
2. myEJB - this iwll have all the classes - remote & home interfaces, the bean class and all the other classes required by the bean.
Now, the question is, who is acting as the client of your EJB ? There are 3 possibilities
1. A servlet
2. Another EJB
3. a simple java program.
In the first 2 cases, you can go for Local Interfaces (more so in the second case than the first). The reason being that the the client and server will be in the same JVM. Thus, in the first case, if the Web container and the ejb container are in the same app server, EJBs can be local.
However, in the third case, it is unlikey that you will have the client runnng and the same jvm as the server, because the server is using the jvm provided by weblogic.
Thus, you cannot use local interfaces in this 3rd case. I have a feeling that this is what you are doing. If so, change the local interfaces to remote.
See if this helps. Else, I will mail you some sample code. But I am afraid, sample code wont be of much help bcoz this seems to be a design problem.
regards

Error con Initial Context

I was running the example that this in the tutorial but I am having problems.
The code is:
public static void main(String[] args) {
          String name = "autoexec.bat";
          Hashtable env = new Hashtable();
          env.put(Context.INITIAL_CONTEXT_FACTORY,
               "com.sun.jndi.ldap.LdapCtxFactory");
          try {
               // Create the initial context
               Context ctx = new InitialContext(env);
               // Look up an object
               Object obj = ctx.lookup(name);
               // Print it
               System.out.println(name + " is bound to: " + obj);
          } catch (NamingException e) {
               System.err.println("Problem looking up " + name + ": " + e);
And the error is:
Problem looking up autoexec.bat: javax.naming.CommunicationException: localhost:389 [Root exception is java.net.ConnectException: Connection refused: connect]

you are trying to connect to an LDAP directory server, but obviously there is no such server running on your machine.
If you want to work with LdapCtxFactory, you need an LDAP server, e.g. openldap, which is included in most LINUX distributions (see also www.openldap.org).

'Type code out of range' error when getting initial Context

I am running WLS 6.1 SP3 for J2EE 1.2 on Solaris. I try to create a JNDI Context
with the standard example code:
ht.put( Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory"
ht.put( Context.PROVIDER_URL, "t3://3.7.193.101:7001" );
ctx = new InitialContext( ht );
When I compile and run this code on the same machine where I am hosting WLS 6.1,
I get the error messages below. The PROGRAM ERROR output is from the command
line I used to run the program; the SERVER ERROR output is in the WLS console
window.
The funny thing is, when I compile and run the same code on a different machine
(A Windows laptop) it works fine !
So ... some kind of network setup problem ?!? I dunno ... can anybody help ?
Thanks in advance for your effort !!
PROGRAM ERROR
java.io.StreamCorruptedException: Type code out of range, is 0
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Exception.java:42)
at java.io.IOException.<init>(IOException.java:47)
at java.io.ObjectStreamException.<init>(ObjectStreamException.java:29)
at java.io.StreamCorruptedException.<init>(StreamCorruptedException.java:30)
at java.io.ObjectInputStream.peekCode(Compiled Code)
at java.io.ObjectInputStream.SkipToEndOfBlockData(Compiled Code)
at java.io.ObjectInputStream.inputClassDescriptor(Compiled Code)
at java.io.ObjectInputStream.readObject(Compiled Code)
at java.io.ObjectInputStream.readObject(Compiled Code)
at java.io.ObjectInputStream.inputObject(Compiled Code)
at java.io.ObjectInputStream.readObject(Compiled Code)
at java.io.ObjectInputStream.readObject(Compiled Code)
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:107)
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:115)
at weblogic.rjvm.ConnectionManager.readPeerInfo(ConnectionManager.java:685)
at weblogic.rjvm.ConnectionManagerClient.handleIdentifyResponse(ConnectionManagerClient.java:140)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:626)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(Compiled Code)
at weblogic.socket.JavaSocketMuxer.processSockets2(Compiled Code)
at weblogic.socket.JavaSocketMuxer.processSockets(Compiled Code)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(Compiled Code)
--------------- nested within: ------------------
weblogic.utils.AssertionError: ***** ASSERTION FAILED ***** - with nested exception:
[java.io.StreamCorruptedException: Type code out of range, is 0]
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Error.<init>(Error.java:50)
at weblogic.utils.NestedError.<init>(NestedError.java:24)
at weblogic.utils.AssertionError.<init>(AssertionError.java:56)
at weblogic.rjvm.ConnectionManager.readPeerInfo(ConnectionManager.java:687)
at weblogic.rjvm.ConnectionManagerClient.handleIdentifyResponse(ConnectionManagerClient.java:140)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:626)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(Compiled Code)
at weblogic.socket.JavaSocketMuxer.processSockets2(Compiled Code)
at weblogic.socket.JavaSocketMuxer.processSockets(Compiled Code)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(Compiled Code)
Exception in EJATestJMSSender main block ! was :javax.naming.CommunicationException
[Root exception is java.net.ConnectException: No server found at T3://3.7.193.101:7001]:
javax.naming.CommunicationException. Root exception is java.net.ConnectException:
No server found at T3://3.7.193.101:7001
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Exception.java:42)
at java.io.IOException.<init>(IOException.java:47)
at java.net.SocketException.<init>(SocketException.java:36)
SERVER ERROR
<Sep 6, 2002 12:27:48 PM CDT> <Error> <Posix Performance Pack> <Uncaught Throwable
in processSockets
java.util.EmptyStackException
at weblogic.utils.collections.Stack.pop(Stack.java:72)
at weblogic.rjvm.InboundMsgAbbrev.getAbbrev(InboundMsgAbbrev.java:85)
at weblogic.rjvm.MsgAbbrevInputStream.readImmutable(MsgAbbrevInputStream.java:172)
at weblogic.rjvm.MsgAbbrevInputStream.readClassDescriptor(MsgAbbrevInputStream.java:186)
at weblogic.common.internal.ChunkedObjectInputStream$NestedObjectInputStream.readClassDescriptor(ChunkedObjectInputStream.java:290)
at java.io.ObjectInputStream.inputClassDescriptor(ObjectInputStream.java:906)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:366)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
at java.io.ObjectInputStream.inputObject(ObjectInputStream.java:1186)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:386)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:236)
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:107)
at weblogic.common.internal.ChunkedObjectInputStream.readObject(ChunkedObjectInputStream.java:115)
at weblogic.rjvm.ConnectionManager.readPeerInfo(ConnectionManager.java:685)
at weblogic.rjvm.ConnectionManagerServer.handleIdentifyRequest(ConnectionManagerServer.java:255)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:619)
at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
at weblogic.socket.PosixSocketMuxer.deliverGoodNews(PosixSocketMuxer.java:449)
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)

I get this error when i run Visual Cafe with Netscape Navigator. All the classes are in CLASSPATH. Can someone point out the reason.

Getting Initial Context from standalone client

I have not been able to set up the InitialContext for a stand-alone client, sending and receiving a topic.
I have already looked at and tried all the previous relevant threads, but no success.
Any help is greatly appreciated.
Many thanks in advance.

I have not been able to set up the InitialContext for a stand-alone client, sending and receiving a topic.
I have already looked at and tried all the previous relevant threads, but no success.
Any help is greatly appreciated.
Many thanks in advance.

Initial Context prbm

hi everybody,
i am new to this forum. any body help me to solve the problem
i am trying to communicate statelessbean with console client thro' weblogic 8.1 server. but i got an error during initial context object creation time. that error is
Exception in thread "main" java.lang.NoClassDefFoundError: javax/security/auth/callback/CallbackHandler
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:131)
at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
at javax.naming.InitialContext.init(Unknown Source)
at javax.naming.InitialContext.<init>(Unknown Source)
at com.anand.StateLess.HelloTestClient.getContextInfo(HelloTestClient.java:61)
at com.anand.StateLess.HelloTestClient.main(HelloTestClient.java:104)
kindly give me a solution
thanx in advance
bye
regards
muruganandam

This is what I get when I started the agents, I am using weblogic8.1 . Are we missing any other jars in the classpath.
Exception in thread "main" java.lang.NoClassDefFoundError: javax/security/auth/callback/CallbackHandler
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:131)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:665)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
at javax.naming.InitialContext.init(InitialContext.java:222)
at javax.naming.InitialContext.<init>(InitialContext.java:198)
at javax.naming.directory.InitialDirContext.<init>(InitialDirContext.java:83)
at com.yantra.interop.util.YIFMessageBrowser.getInitialDirContext(YIFMessageBrowser.java:212)
at com.yantra.interop.util.YIFMessageBrowser.init(YIFMessageBrowser.java:156)
at com.yantra.interop.util.YIFMessageBrowser.<init>(YIFMessageBrowser.java:85)
at com.yantra.ycp.agent.server.YCPAgentTrigger.queueHasMessages(YCPAgentTrigger.java:101)
at com.yantra.ycp.agent.server.YCPAgentTrigger.hasTrigger(YCPAgentTrigger.java:113)
at com.yantra.ycp.agent.server.YCPAgentTrigger.sendMessage(YCPAgentTrigger.java:74)
at com.yantra.ycp.agent.server.YCPAgentTrigger.main(YCPAgentTrigger.java:53)

Initial Context is slow within Java Web Start

All,
I have a Swing-based client app that makes EJB calls on a Weblogic 6.1sp2
server. It works great as a standalone app run from the command line. The
problem is when I deploy it using Java Web Start. The 'new
InitialContext(props)' call takes from 5-20 seconds. This is on a single
user development machine with the server and client running on the same
machine.
When I run it from the command line the initial context only takes 1-2
seconds to create. This is using the exact same .jar file used in the Web
Start case.
The Web Start environment is somewhat different than command line clients.
I think it is similar to the applet sandbox environment (security,etc).
Other than this, the client/server interaction speed is good (they should
be since they are on the same machine!). Any ideas?
System particulars:
Weblogic 6.1sp2. Native IO.
Host=127.0.0.1 (Reverse DNS Lookup disabled in server).
Java 1.3.1
Java Web Start 1.0.1
Windows NT 4.0sp5

I have some more details. If I signed the .jar file and give it all
permissions, then the performance is fine (~1s to get initial context).
Does anyone know which permissions are needed to connect quickliy? I would
like to only give the application those permissions it really needs.
Thanks.
Mike Houston <[email protected]> wrote in
news:[email protected]:
All,
I have a Swing-based client app that makes EJB calls on a Weblogic
6.1sp2 server. It works great as a standalone app run from the command
line. The problem is when I deploy it using Java Web Start. The 'new
InitialContext(props)' call takes from 5-20 seconds. This is on a
single user development machine with the server and client running on
the same machine.
When I run it from the command line the initial context only takes 1-2
seconds to create. This is using the exact same .jar file used in the
Web Start case.
The Web Start environment is somewhat different than command line
clients. I think it is similar to the applet sandbox environment
(security,etc).
Other than this, the client/server interaction speed is good (they
should be since they are on the same machine!). Any ideas?
System particulars:
Weblogic 6.1sp2. Native IO.
Host=127.0.0.1 (Reverse DNS Lookup disabled in server).
Java 1.3.1
Java Web Start 1.0.1
Windows NT 4.0sp5

Initial context lookup error??

hi, i keep having a problem with the initial context lookup .
my bean is RoomManagerBean and its JNDI is IRMS/hotel/RoomManagerBean.
this is the code:
Object obj = context.lookup("IRMS/hotel/RoomManagerBean");
however, the result is always NULL. when i try to edit the path to:
Object obj = context.lookup("java:comp/env/IRMS/hotel/RoomManagerBean");
, i will get the error: object not bound to name: java:comp/env/IRMS/hotel/RoomManagerBean
is it becasue my path name is wrong? or the JNDI name? pls help me with this, highly appreciated :)

ok here's my web.xml:
<?xml version="1.0" encoding="UTF-8"?>
<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
     version="2.4">
<session-config>
<session-timeout>
30
</session-timeout>
</session-config>
<welcome-file-list>
     <welcome-file>
index.jsp
</welcome-file>
</welcome-file-list>
<ejb-local-ref>
<ejb-ref-name>IRMS/hotel/RoomManager</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>IRMS.hotel.RoomManagerLocalHome</local-home>
<local>IRMS.hotel.RoomManagerLocal</local>
<ejb-link>IRMS-EJBModule.jar#RoomManager</ejb-link>
</ejb-local-ref>
</web-app>
as u can see, the ejb ref is there. however, when i try to run the file, it gives me the error: Unresolved: <ejb-link>. what does it mean and how to solve it? because i checked the JNDI name for room manager, it's IRMS/hotel/RoomManager. and under the ejb-jar.xml, here is a portion of it in relation to the roommanager:
<session>
<display-name>RoomManagerSB</display-name>
<ejb-name>RoomManager</ejb-name>
<local-home>IRMS.hotel.RoomManagerLocalHome</local-home>
<local>IRMS.hotel.RoomManagerLocal</local>
<ejb-class>IRMS.hotel.RoomManagerEJB</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Bean</transaction-type>
<ejb-local-ref>
<ejb-ref-name>ejb/Room</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<local-home>IRMS.hotel.RoomLocalHome</local-home>
<local>IRMS.hotel.RoomLocal</local>
<ejb-link>Room</ejb-link>
</ejb-local-ref>
<ejb-local-ref>
<ejb-ref-name>IRMS/hotel/Room</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<local-home>IRMS.hotel.RoomLocalHome</local-home>
<local>IRMS.hotel.RoomLocal</local>
<ejb-link>Room</ejb-link>
</ejb-local-ref>
<ejb-local-ref>
<ejb-ref-name>IRMS/hotel/Room</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<local-home>IRMS.hotel.RoomLocalHome</local-home>
<local>IRMS.hotel.RoomLocal</local>
<ejb-link>Room</ejb-link>
</ejb-local-ref>
<ejb-local-ref>
<ejb-ref-name>IRMS/hotel/RoomManager</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>IRMS.hotel.RoomManagerLocalHome</local-home>
<local>IRMS.hotel.RoomManagerLocal</local>
<ejb-link>RoomManager</ejb-link>
</ejb-local-ref>
</session>
can u solve this? thanks

Why can't I get an initial context in websphere!?!

I am using WebSphere App Dev v.4.0, and I have written a client application which should call methods from an EJB. But I don't seem to be able to get an initial context no matter what I do. Here is a snippet of the app code and the exception it throws: I will be most grateful if someone could help me out. Thanks Ben.
THE CODE...
try {
    System.out.println("about to retrieve initial context.");
    java.util.Properties p = new java.util.Properties();
    p.put(Context.PROVIDER_URL, "iiop://localhost:901");
    p.put(Context.INITIAL_CONTEXT_FACTORY, "com.ibm.websphere.naming.WsnInitialContextFactory");
    InitialContext initContext = new InitialContext(p);
    System.out.println("initial context has been created.");
}catch (Exception e) {
    e.printStackTrace();
THE EXCEPTION...
about to retrieve initial context.
javax.naming.NoInitialContextException: Cannot instantiate class: com.ibm.websphere.naming.WsnInitialContextFactory. Root exception is java.lang.ClassNotFoundException: com.ibm.websphere.naming.WsnInitialContextFactory
at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
at java.lang.ClassLoader.loadClass(ClassLoader.java:325)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:380)
at java.lang.ClassLoader.loadClass(ClassLoader.java:257)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:212)
at com.sun.naming.internal.VersionHelper12.loadClass(VersionHelper12.java:46)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:656)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:199)
at BeanClient.main(BeanClient.java:18)

Hi Ben,
As the gurus told in the earlier replies, it is the problem with Class loading.
Make Sure that following jar files are in CLASSPATH. (Assuming C:\Websphere is your websphere installation directory)
J2EE.jar - C:/Websphere/AppServer/lib/J2ee.jar
Websphere.jar - C:/Websphere/AppServer/lib/websphere.jar
Ibmorb.jar - C:/Websphere/AppServer/java/jre/lib/ext/ibmorb.jar
Once you have all these in your CLASSPATH, try running your client application. If you are using Sun JDK you will encounter an error message in the runtime which says like "Service Unavaible.. XXXX Service not found".
When you encounter this problem make sure that your service named XXXX is running and you are calling it appropriately. To find whether a service with name XXXX is running type
>>>>dumpnamespace
at the command prompt. If your service name is listed by dumpnamespace.. your service is running. So there is something wrong with the client code. Proceed to the next step.
In this tep you can use IBM JDK to fix the error. But that might not be the most suitable solution.
Here is how you can run Websphere EJB client programs without IBM JDK.
http://www7b.software.ibm.com/wsdd/downloads/pluggableclient.html
Follow this link and download the Websphere Pluggable application client and follow the instructions given in Readme to install the pluggable application client.
Once you finish installing the pluggable application client, you should be able to run with no problems.
For dwildcat92
I was also under the impression that we SHOULD use IBM JDK to make the client run. But our integration process demanded that the clients be called from Apache Tomcat. Thats how I was forced to find this link
http://www7b.software.ibm.com/wsdd/downloads/pluggableclient.html
Thanks for making me learn guys,
Ravi.

Error in ArjunaMs Provider: Could not set up Initial Context

Hi,
I am trying to run the chatdemo example that comes with arjunams using http as the protocol and for that I have changed the file "chatdemo.properties" to this:
java.naming.factory.initial=com.arjuna.ams.client.naming.AMSInitialContextFactory
java.naming.provider.url=ams://server?web#http://localhost:8090/WebConnect/WebConnect
I have already tried running the tomcat server in port 8080 now I am trying it in 8090 and I have WebConnect.war deployed in webapps folder. When I run the chatdemo I get the following error:
Caught exception getting properties from file
javax.naming.CommunicationException: Cannot set up Initial Context : Timeout whe
n communicating with the server (ams.timeout=3000 [milliseconds]). [Root excepti
on is [TIMEOUT_EXCEPTION]com.arjuna.ams.internal.client.common.TransportExceptio
n: Timeout when communicating with the server (ams.timeout=3000 [milliseconds]).
at com.arjuna.ams.internal.client.core.AbstractInitialContext.<init>(Abs
tractInitialContext.java:171)
at com.arjuna.ams.internal.client.transport.server.InitialContext.<init>
(InitialContext.java:72)
at com.arjuna.ams.internal.client.transport.server.web.naming.InitialCon
text.<init>(InitialContext.java:40)
at com.arjuna.ams.internal.client.transport.server.web.naming.InitialCon
textFactory.getInitialContext(InitialContextFactory.java:41)
at com.arjuna.ams.client.naming.AMSInitialContextFactory.getInitialConte
xt(AMSInitialContextFactory.java:360)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
62)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.arjuna.ams.demos.chat.core.JMSChatInterface.<init>(JMSChatInterfa
ce.java:240)
at com.arjuna.ams.demos.chat.ui.text.TextClient.test(TextClient.java:163
at com.arjuna.ams.demos.chat.ui.text.TextClient.main(TextClient.java:67)
Caused by: [TIMEOUT_EXCEPTION]com.arjuna.ams.internal.client.common.TransportExc
eption: Timeout when communicating with the server (ams.timeout=3000 [millisecon
ds]).
at com.arjuna.ams.internal.client.common.MessageCarrierBuffer.get(Messag
eCarrierBuffer.java:67)
at com.arjuna.ams.internal.client.common.RPCMapper.sendRPC(RPCMapper.jav
a:102)
at com.arjuna.ams.internal.client.transport.server.TransportManager.init
(TransportManager.java:139)
at com.arjuna.ams.internal.client.transport.server.InitialContext.create
TransportLayer(InitialContext.java:102)
at com.arjuna.ams.internal.client.core.AbstractInitialContext.createComm
Chain(AbstractInitialContext.java:999)
at com.arjuna.ams.internal.client.core.AbstractInitialContext.<init>(Abs
tractInitialContext.java:165)
What can be the error? Please I need help urgently!!!
Thanks in advance!

Hi RESIDENT2,
First of all, please let me apologise for the delay in response time to your message! Unfortunately it seems as though we missed this one.
Can I suggest to you that the best place to get help with ArjunaMS is from:
http://www.arjuna.com/forum/
As far as your problem is concerned it appears as though you have performed the correct procedures to setup ArjunaMS, if your problem still exists can I ask you to post a complete description of the system as it stands.
NOTE: To check the WebConnect servlet is running you should be able to connect to http://localhost:8090/WebConnect, which should display a welcome page for the servlet. If this welcome screen cannot be seen then the servlet failed to deploy.
Once again, sorry for the delayed response!
Cheers,
Tom
Arjuna Technologies Limited

Error getting initial context

Similar Messages

Maybe you are looking for