This may be obvious but I have been pulling my hair out.

Have unpacked beta1 and have started the server.
Have built a simple 'hello' style ejb and deployed it.
Have build a client app which tries to instance the bean.

When trying to connect to the server using InitialContext:
    Properties p = new Properties();
    p.put("java.naming.factory.initial", 
"org.openejb.client.RemoteInitialContextFactory");
    p.put("java.naming.provider.url", "127.0.0.1:4201");
    p.put("java.naming.security.principal", user);
    p.put("java.naming.security.credentials", password);

It throws a: 
        javax.naming.AuthenticationException: Error while communicating with 
server: ; nested exception is:
        java.rmi.RemoteException: Cannot open object input stream to server: ; 
nested exception is:
        java.net.SocketException: Connection reset 
etc. at the getInitialContext line.

In the openejb/logs/openejb.log file I get:

2007-10-02 16:43:52,674 - ERROR - "null ��/0.0" FAIL "Unexpected error - For 
input string: "t""
java.lang.NumberFormatException: For input string: "t"
        at java.lang.NumberFormatException.forInputString(Unknown Source)
        at java.lang.Integer.parseInt(Unknown Source)
        at java.lang.Integer.parseInt(Unknown Source)
        at 
org.apache.openejb.client.ProtocolMetaData.init(ProtocolMetaData.java:56)
        at 
org.apache.openejb.client.ProtocolMetaData.readExternal(ProtocolMetaData.java:92)
        at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:103)
        at org.apache.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:84)
        at org.apache.openejb.server.ejbd.EjbServer.service(EjbServer.java:60)
        at 
org.apache.openejb.server.ServiceLogger.service(ServiceLogger.java:73)
        at 
org.apache.openejb.server.ServiceAccessController.service(ServiceAccessController.java:55)
        at org.apache.openejb.server.ServiceDaemon$1.run(ServiceDaemon.java:117)
        at java.lang.Thread.run(Unknown Source)

I am at a loss, I can telnet to 4202 and list the beans etc. 
It does not matter whether I deploy my bean or not, it is the connection to the 
port which is causing the issue, 
I have no Idea where the string "t" comes from.

Sorry if this is obvious.

Gus

-- 
Augustus Gingell BEng ACGI

Reply via email to