Re: JNDI Access Problem
David, Thanks for the response. I'll try to debug it - I'm assuming there's no log statements, and you would like me to run it in a debugger? Another thought that I had, is it possible to look at the JNDI tree, to verify that my ejb is deployed properly? And also, I don't have a geronimo-application.xml deployed with my ear. Could that have anything to do with it? (I couldn't find any examples that met what we do in this app). Thanks, Rick On Jan 4, 2007, at 8:03 PM, Carragher Jr, Richard wrote: Hi, I'm trying to deploy a non-j2ee application client connecting to a stateless session bean in Geronimo 1.1. This seems simple, and it has worked without changes on WebSphere, Jboss, and WebLogic, so I'm pretty sure that I m setting something up in Geronimo incorrectly. In open-ejb-jar.xml, I have the following snippet: session ejb-nameController/ejb-name jndi-nameawc/jndi-name local-jndi-nameControllerLocal/local-jndi-name gernaming:resource-ref gernaming:ref-namejdbc/datasourceUri/ gernaming:ref-name gernaming:resource-linkjdbc/ transactionwareDataSource/gernaming:resource-link /gernaming:resource-ref /session My client has the following properties setup: java.naming.factory.initial=org.openejb.client.RemoteInitialContextFac tory java.naming.provider.url=localhost:4201 java.naming.security.principal=system java.naming.security.credentials=manager And the client lookup code is pretty straightforward: InitialContext jndiContext = new InitialContext(env); Object ref = jndiContext.lookup(awc); ControllerRemoteHome home = (ControllerRemoteHome) PortableRemoteObject.narrow(ref, ControllerRemoteHome.class); Here's the exception I get in geronimo.out: 19:46:54,233 ERROR [JndiRequestHandler] JNDI request error java.lang.IllegalArgumentException at java.net.URI.create(URI.java:859) at org.openejb.ContainerIndex.getContainerIndex (ContainerIndex.java:207) at org.openejb.ContainerIndex$$FastClassByCGLIB$ $6674ccb6.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java (Inlined Compiled Code)) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke (FastMethodInvoker.java(Compiled Code)) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke (GBeanOperation.java(Inlined Compiled Code)) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke (GBeanInstance.java(Compiled Code)) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke (RawInvoker.java(Inlined Compiled Code)) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke (RawOperationInvoker.java(Compiled Code)) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept (ProxyMethodInterceptor.java(Compiled Code)) at org.openejb.ContainerIndex$$EnhancerByCGLIB$ $2edf4a7f.getContainerIndex(generated) at org.openejb.server.ejbd.JndiRequestHandler.doLookup (JndiRequestHandler.java:178) at org.openejb.server.ejbd.JndiRequestHandler.processRequest (JndiRequestHandler.java:115) at org.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java: 154) at org.openejb.server.ejbd.EjbServer.service(EjbServer.java: 87) at org.openejb.server.ejbd.EjbServer$$FastClassByCGLIB$ $d379d2ff.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java (Inlined Compiled Code)) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke (FastMethodInvoker.java(Compiled Code)) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke (GBeanOperation.java(Inlined Compiled Code)) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke (GBeanInstance.java(Compiled Code)) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke (RawInvoker.java(Inlined Compiled Code)) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke (RawOperationInvoker.java(Compiled Code)) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept (ProxyMethodInterceptor.java(Compiled Code)) at org.activeio.xnet.ServerService$$EnhancerByCGLIB$ $eb95fe48.service(generated) at org.activeio.xnet.ServicePool$2.run(ServicePool.java:67) at org.activeio.xnet.ServicePool$3.run(ServicePool.java:90) at org.apache.geronimo.pool.ThreadPool$1.run (ThreadPool.java:172) at org.apache.geronimo.pool.ThreadPool $ContextClassLoaderRunnable.run(ThreadPool.java:289) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor $Worker.run(Unknown Source) at java.lang.Thread.run(Thread.java:568) Caused by: java.net.URISyntaxException: Illegal character in path at index 1: /awc at java.net.URI$Parser.fail(URI.java:2764) at
Re: JNDI Access Problem
On Jan 5, 2007, at 9:04 AM, Carragher Jr, Richard wrote: David, Thanks for the response. I'll try to debug it - I'm assuming there's no log statements, and you would like me to run it in a debugger? Either that or add some logging statements and recompile. I suspect the debugger might be simpler. Another thought that I had, is it possible to look at the JNDI tree, to verify that my ejb is deployed properly? I don't know of any tools that would let you look. And also, I don't have a geronimo-application.xml deployed with my ear. Could that have anything to do with it? (I couldn't find any examples that met what we do in this app). I can't think of a way this could cause the problem you are seeing, but my imagination might be limited. thanks david jencks Thanks, Rick On Jan 4, 2007, at 8:03 PM, Carragher Jr, Richard wrote: Hi, I'm trying to deploy a non-j2ee application client connecting to a stateless session bean in Geronimo 1.1. This seems simple, and it has worked without changes on WebSphere, Jboss, and WebLogic, so I'm pretty sure that I m setting something up in Geronimo incorrectly. In open-ejb-jar.xml, I have the following snippet: session ejb-nameController/ejb-name jndi-nameawc/jndi-name local-jndi-nameControllerLocal/local-jndi-name gernaming:resource-ref gernaming:ref-namejdbc/datasourceUri/ gernaming:ref-name gernaming:resource-linkjdbc/ transactionwareDataSource/gernaming:resource-link /gernaming:resource-ref /session My client has the following properties setup: java.naming.factory.initial=org.openejb.client.RemoteInitialContextFa c tory java.naming.provider.url=localhost:4201 java.naming.security.principal=system java.naming.security.credentials=manager And the client lookup code is pretty straightforward: InitialContext jndiContext = new InitialContext(env); Object ref = jndiContext.lookup(awc); ControllerRemoteHome home = (ControllerRemoteHome) PortableRemoteObject.narrow(ref, ControllerRemoteHome.class); Here's the exception I get in geronimo.out: 19:46:54,233 ERROR [JndiRequestHandler] JNDI request error java.lang.IllegalArgumentException at java.net.URI.create(URI.java:859) at org.openejb.ContainerIndex.getContainerIndex (ContainerIndex.java:207) at org.openejb.ContainerIndex$$FastClassByCGLIB$ $6674ccb6.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java (Inlined Compiled Code)) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke (FastMethodInvoker.java(Compiled Code)) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke (GBeanOperation.java(Inlined Compiled Code)) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke (GBeanInstance.java(Compiled Code)) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke (RawInvoker.java(Inlined Compiled Code)) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke (RawOperationInvoker.java(Compiled Code)) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept (ProxyMethodInterceptor.java(Compiled Code)) at org.openejb.ContainerIndex$$EnhancerByCGLIB$ $2edf4a7f.getContainerIndex(generated) at org.openejb.server.ejbd.JndiRequestHandler.doLookup (JndiRequestHandler.java:178) at org.openejb.server.ejbd.JndiRequestHandler.processRequest (JndiRequestHandler.java:115) at org.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java: 154) at org.openejb.server.ejbd.EjbServer.service(EjbServer.java: 87) at org.openejb.server.ejbd.EjbServer$$FastClassByCGLIB$ $d379d2ff.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java (Inlined Compiled Code)) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke (FastMethodInvoker.java(Compiled Code)) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke (GBeanOperation.java(Inlined Compiled Code)) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke (GBeanInstance.java(Compiled Code)) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke (RawInvoker.java(Inlined Compiled Code)) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke (RawOperationInvoker.java(Compiled Code)) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept (ProxyMethodInterceptor.java(Compiled Code)) at org.activeio.xnet.ServerService$$EnhancerByCGLIB$ $eb95fe48.service(generated) at org.activeio.xnet.ServicePool$2.run(ServicePool.java:67) at org.activeio.xnet.ServicePool$3.run(ServicePool.java:90) at org.apache.geronimo.pool.ThreadPool$1.run (ThreadPool.java:172) at org.apache.geronimo.pool.ThreadPool $ContextClassLoaderRunnable.run(ThreadPool.java:289) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor $Worker.run(Unknown Source) at
Re: JNDI Access Problem
On Jan 5, 2007, at 9:52 AM, David Jencks wrote: On Jan 5, 2007, at 9:04 AM, Carragher Jr, Richard wrote: David, Thanks for the response. I'll try to debug it - I'm assuming there's no log statements, and you would like me to run it in a debugger? Either that or add some logging statements and recompile. I suspect the debugger might be simpler. Another thought that I had, is it possible to look at the JNDI tree, to verify that my ejb is deployed properly? I don't know of any tools that would let you look. FYI, there was just a jira opened (and a patch supplied) to provide this capability in 2.0 -- https://issues.apache.org/jira/browse/ GERONIMO-2689 I doubt it would work on a 1.1 base... --kevan
Re: JNDI Access Problem
On Jan 5, 2007, at 10:00 AM, Kevan Miller wrote: On Jan 5, 2007, at 9:52 AM, David Jencks wrote: On Jan 5, 2007, at 9:04 AM, Carragher Jr, Richard wrote: David, Thanks for the response. I'll try to debug it - I'm assuming there's no log statements, and you would like me to run it in a debugger? Either that or add some logging statements and recompile. I suspect the debugger might be simpler. Another thought that I had, is it possible to look at the JNDI tree, to verify that my ejb is deployed properly? I don't know of any tools that would let you look. FYI, there was just a jira opened (and a patch supplied) to provide this capability in 2.0 -- https://issues.apache.org/jira/browse/ GERONIMO-2689 I doubt it would work on a 1.1 base... Also Richard is using the proprietary openejb remote jndi implementation which is not shown in the proposed jndi viewer. Maybe it should be. thanks david jencks --kevan
RE: JNDI Access Problem
Ok, user error. I was looking up the jndi name from a property file, and the property file had the name in quotes (). That explains that problem. However, now I'm getting this one: 10:30:23,843 ERROR [JndiRequestHandler] Failed to write to JNDIResponse java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113) at java.net.SocketOutputStream.write(SocketOutputStream.java:157) at java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStrea m.java:1733) at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(Object OutputStream.java:1642) at java.io.ObjectOutputStream.writeNonProxyDesc(ObjectOutputStream.java:120 0) at java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java:1131) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1 332) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1083) at java.io.ObjectOutputStream.writeFatalException(ObjectOutputStream.java:1 449) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:312) at org.openejb.client.EJBMetaDataImpl.writeExternal(EJBMetaDataImpl.java:18 5) at org.openejb.client.JNDIResponse.writeExternal(JNDIResponse.java:203) at org.openejb.server.ejbd.JndiRequestHandler.processRequest(JndiRequestHan dler.java:131) at org.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:154) at org.openejb.server.ejbd.EjbServer.service(EjbServer.java:87) at org.openejb.server.ejbd.EjbServer$$FastClassByCGLIB$$d379d2ff.invoke(ge nerated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java(Inlined Compiled Code)) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInv oker.java(Compiled Code)) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.j ava(Inlined Compiled Code)) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.jav a(Compiled Code)) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java(Inli ned Compiled Code)) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperation Invoker.java(Compiled Code)) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyM ethodInterceptor.java(Compiled Code)) at org.activeio.xnet.ServerService$$EnhancerByCGLIB$$bffe4aa3.service(gene rated) at org.activeio.xnet.ServicePool$2.run(ServicePool.java:67) at org.activeio.xnet.ServicePool$3.run(ServicePool.java:90) at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:172) at org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run(Threa dPool.java:289) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Thread.java:568) 10:30:23,846 ERROR [EjbDaemon] 0:0:0:0:0:0:0:1 JNDI_REQUEST OEJP/2.0 FAIL Broken pipe Any thoughts? Thanks, Rick Carragher Senior Architect Store and Multi-Channel SAP AG 311 Sinclair Rd. Bristol, PA. 19007 T +1(215)785-4321x425 mailto:[EMAIL PROTECTED] www.sap.com -Original Message- From: David Jencks [mailto:[EMAIL PROTECTED] Sent: Friday, January 05, 2007 9:52 AM To: user@geronimo.apache.org Subject: Re: JNDI Access Problem On Jan 5, 2007, at 9:04 AM, Carragher Jr, Richard wrote: David, Thanks for the response. I'll try to debug it - I'm assuming there's no log statements, and you would like me to run it in a debugger? Either that or add some logging statements and recompile. I suspect the debugger might be simpler. Another thought that I had, is it possible to look at the JNDI tree, to verify that my ejb is deployed properly? I don't know of any tools that would let you look. And also, I don't have a geronimo-application.xml deployed with my ear. Could that have anything to do with it? (I couldn't find any examples that met what we do in this app). I can't think of a way this could cause the problem you are seeing, but my imagination might be limited. thanks david jencks Thanks, Rick On Jan 4, 2007, at 8:03 PM, Carragher Jr, Richard wrote: Hi, I'm trying to deploy a non-j2ee application client connecting to a stateless session bean in Geronimo 1.1. This seems simple, and it has worked without changes on WebSphere, Jboss, and WebLogic, so I'm pretty sure that I m setting something up in Geronimo incorrectly. In open-ejb-jar.xml, I have the following snippet: session ejb-nameController/ejb-name jndi-nameawc/jndi-name local-jndi-nameControllerLocal/local-jndi-name gernaming:resource-ref gernaming:ref-namejdbc/datasourceUri/ gernaming:ref-name gernaming:resource-linkjdbc
Re: JNDI Access Problem
On Jan 5, 2007, at 10:35 AM, Carragher Jr, Richard wrote: Ok, user error. I was looking up the jndi name from a property file, and the property file had the name in quotes (). That explains that problem. However, now I'm getting this one: Unfortunately I have no idea about this one, maybe an openejb person can figure it out. One thing that looks different from what I remember seeing is it looks like you might be using tcp v6 addresses. At one point I had problems getting geronimo to start on a linux machine with some v6 support enabled: I solved the problem by using a different machine. david jencks 10:30:23,843 ERROR [JndiRequestHandler] Failed to write to JNDIResponse java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113) at java.net.SocketOutputStream.write(SocketOutputStream.java:157) at java.io.ObjectOutputStream$BlockDataOutputStream.drain (ObjectOutputStrea m.java:1733) at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode (Object OutputStream.java:1642) at java.io.ObjectOutputStream.writeNonProxyDesc (ObjectOutputStream.java:120 0) at java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java: 1131) at java.io.ObjectOutputStream.writeOrdinaryObject (ObjectOutputStream.java:1 332) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1083) at java.io.ObjectOutputStream.writeFatalException (ObjectOutputStream.java:1 449) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:312) at org.openejb.client.EJBMetaDataImpl.writeExternal (EJBMetaDataImpl.java:18 5) at org.openejb.client.JNDIResponse.writeExternal(JNDIResponse.java:203) at org.openejb.server.ejbd.JndiRequestHandler.processRequest (JndiRequestHan dler.java:131) at org.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:154) at org.openejb.server.ejbd.EjbServer.service(EjbServer.java:87) at org.openejb.server.ejbd.EjbServer$$FastClassByCGLIB$$d379d2ff.invoke (ge nerated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java(Inlined Compiled Code)) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke (FastMethodInv oker.java(Compiled Code)) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke (GBeanOperation.j ava(Inlined Compiled Code)) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke (GBeanInstance.jav a(Compiled Code)) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java (Inli ned Compiled Code)) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke (RawOperation Invoker.java(Compiled Code)) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept (ProxyM ethodInterceptor.java(Compiled Code)) at org.activeio.xnet.ServerService$$EnhancerByCGLIB$$bffe4aa3.service (gene rated) at org.activeio.xnet.ServicePool$2.run(ServicePool.java:67) at org.activeio.xnet.ServicePool$3.run(ServicePool.java:90) at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:172) at org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run (Threa dPool.java:289) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Thread.java:568) 10:30:23,846 ERROR [EjbDaemon] 0:0:0:0:0:0:0:1 JNDI_REQUEST OEJP/2.0 FAIL Broken pipe Any thoughts? Thanks, Rick Carragher Senior Architect Store and Multi-Channel SAP AG 311 Sinclair Rd. Bristol, PA. 19007 T +1(215)785-4321x425 mailto:[EMAIL PROTECTED] www.sap.com -Original Message- From: David Jencks [mailto:[EMAIL PROTECTED] Sent: Friday, January 05, 2007 9:52 AM To: user@geronimo.apache.org Subject: Re: JNDI Access Problem On Jan 5, 2007, at 9:04 AM, Carragher Jr, Richard wrote: David, Thanks for the response. I'll try to debug it - I'm assuming there's no log statements, and you would like me to run it in a debugger? Either that or add some logging statements and recompile. I suspect the debugger might be simpler. Another thought that I had, is it possible to look at the JNDI tree, to verify that my ejb is deployed properly? I don't know of any tools that would let you look. And also, I don't have a geronimo-application.xml deployed with my ear. Could that have anything to do with it? (I couldn't find any examples that met what we do in this app). I can't think of a way this could cause the problem you are seeing, but my imagination might be limited. thanks david jencks Thanks, Rick On Jan 4, 2007, at 8:03 PM, Carragher Jr, Richard wrote: Hi, I'm trying to deploy a non-j2ee application client connecting to a stateless session bean in Geronimo 1.1. This seems simple, and it has worked without changes
RE: JNDI Access Problem
Well, I disabled ipv6, and I get the same error, except the last line changes to: 11:24:40,457 ERROR [EjbDaemon] 127.0.0.1 JNDI_REQUEST OEJP/2.0 FAIL Broken pipe Thanks, Rick Carragher -Original Message- From: David Jencks [mailto:[EMAIL PROTECTED] Sent: Friday, January 05, 2007 10:52 AM To: user@geronimo.apache.org Subject: Re: JNDI Access Problem On Jan 5, 2007, at 10:35 AM, Carragher Jr, Richard wrote: Ok, user error. I was looking up the jndi name from a property file, and the property file had the name in quotes (). That explains that problem. However, now I'm getting this one: Unfortunately I have no idea about this one, maybe an openejb person can figure it out. One thing that looks different from what I remember seeing is it looks like you might be using tcp v6 addresses. At one point I had problems getting geronimo to start on a linux machine with some v6 support enabled: I solved the problem by using a different machine. david jencks 10:30:23,843 ERROR [JndiRequestHandler] Failed to write to JNDIResponse java.net.SocketException: Broken pipe at java.net.SocketOutputStream.socketWrite0(Native Method) at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113) at java.net.SocketOutputStream.write(SocketOutputStream.java:157) at java.io.ObjectOutputStream$BlockDataOutputStream.drain (ObjectOutputStrea m.java:1733) at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode (Object OutputStream.java:1642) at java.io.ObjectOutputStream.writeNonProxyDesc (ObjectOutputStream.java:120 0) at java.io.ObjectOutputStream.writeClassDesc(ObjectOutputStream.java: 1131) at java.io.ObjectOutputStream.writeOrdinaryObject (ObjectOutputStream.java:1 332) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1083) at java.io.ObjectOutputStream.writeFatalException (ObjectOutputStream.java:1 449) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:312) at org.openejb.client.EJBMetaDataImpl.writeExternal (EJBMetaDataImpl.java:18 5) at org.openejb.client.JNDIResponse.writeExternal(JNDIResponse.java:203) at org.openejb.server.ejbd.JndiRequestHandler.processRequest (JndiRequestHan dler.java:131) at org.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:154) at org.openejb.server.ejbd.EjbServer.service(EjbServer.java:87) at org.openejb.server.ejbd.EjbServer$$FastClassByCGLIB$$d379d2ff.invoke (ge nerated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java(Inlined Compiled Code)) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke (FastMethodInv oker.java(Compiled Code)) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke (GBeanOperation.j ava(Inlined Compiled Code)) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke (GBeanInstance.jav a(Compiled Code)) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java (Inli ned Compiled Code)) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke (RawOperation Invoker.java(Compiled Code)) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept (ProxyM ethodInterceptor.java(Compiled Code)) at org.activeio.xnet.ServerService$$EnhancerByCGLIB$$bffe4aa3.service (gene rated) at org.activeio.xnet.ServicePool$2.run(ServicePool.java:67) at org.activeio.xnet.ServicePool$3.run(ServicePool.java:90) at org.apache.geronimo.pool.ThreadPool$1.run(ThreadPool.java:172) at org.apache.geronimo.pool.ThreadPool$ContextClassLoaderRunnable.run (Threa dPool.java:289) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Thread.java:568) 10:30:23,846 ERROR [EjbDaemon] 0:0:0:0:0:0:0:1 JNDI_REQUEST OEJP/2.0 FAIL Broken pipe Any thoughts? Thanks, Rick Carragher -Original Message- From: David Jencks [mailto:[EMAIL PROTECTED] Sent: Friday, January 05, 2007 9:52 AM To: user@geronimo.apache.org Subject: Re: JNDI Access Problem On Jan 5, 2007, at 9:04 AM, Carragher Jr, Richard wrote: David, Thanks for the response. I'll try to debug it - I'm assuming there's no log statements, and you would like me to run it in a debugger? Either that or add some logging statements and recompile. I suspect the debugger might be simpler. Another thought that I had, is it possible to look at the JNDI tree, to verify that my ejb is deployed properly? I don't know of any tools that would let you look. And also, I don't have a geronimo-application.xml deployed with my ear. Could that have anything to do with it? (I couldn't find any examples that met what we do in this app). I can't think of a way this could cause the problem you are seeing, but my imagination might be limited. thanks
Re: JNDI Access Problem
On Jan 5, 2007, at 11:17 AM, Carragher Jr, Richard wrote: Well, I disabled ipv6, and I get the same error, except the last line changes to: 11:24:40,457 ERROR [EjbDaemon] 127.0.0.1 JNDI_REQUEST OEJP/2.0 FAIL Broken pipe What level of JRE(s) are you running? Possible that you can you post a simple test case? If you raise a jira and attach a test case, somebody will have a look... --kevan
RE: JNDI Access Problem
I'm on Linux (Suse 9.2), and I've tried the IBM 1.4.2 and 1.5.0 JVMs. Both give the same error. I can raise a Jira, but I'm not sure what you mean about posting a test case? Rick -Original Message- From: Kevan Miller [mailto:[EMAIL PROTECTED] Sent: Friday, January 05, 2007 11:46 AM To: user@geronimo.apache.org Subject: Re: JNDI Access Problem On Jan 5, 2007, at 11:17 AM, Carragher Jr, Richard wrote: Well, I disabled ipv6, and I get the same error, except the last line changes to: 11:24:40,457 ERROR [EjbDaemon] 127.0.0.1 JNDI_REQUEST OEJP/2.0 FAIL Broken pipe What level of JRE(s) are you running? Possible that you can you post a simple test case? If you raise a jira and attach a test case, somebody will have a look... --kevan
Re: JNDI Access Problem
On Jan 5, 2007, at 12:17 PM, Carragher Jr, Richard wrote: I'm on Linux (Suse 9.2), and I've tried the IBM 1.4.2 and 1.5.0 JVMs. Both give the same error. I can raise a Jira, but I'm not sure what you mean about posting a test case? Whatever is necessary to recreate your problem. E.g. deployment plans, java code, archives (jars/wars/ears), and instructions for recreating the problem you are seeing... The simpler it is to recreate, the better... --kevan
Re: JNDI Access Problem
On Jan 4, 2007, at 8:03 PM, Carragher Jr, Richard wrote: Hi, I'm trying to deploy a non-j2ee application client connecting to a stateless session bean in Geronimo 1.1. This seems simple, and it has worked without changes on WebSphere, Jboss, and WebLogic, so I'm pretty sure that I’m setting something up in Geronimo incorrectly. In open-ejb-jar.xml, I have the following snippet: session ejb-nameController/ejb-name jndi-nameawc/jndi-name local-jndi-nameControllerLocal/local-jndi-name gernaming:resource-ref gernaming:ref-namejdbc/datasourceUri/ gernaming:ref-name gernaming:resource-linkjdbc/ transactionwareDataSource/gernaming:resource-link /gernaming:resource-ref /session My client has the following properties setup: java.naming.factory.initial=org.openejb.client.RemoteInitialContextFac tory java.naming.provider.url=localhost:4201 java.naming.security.principal=system java.naming.security.credentials=manager And the client lookup code is pretty straightforward: InitialContext jndiContext = new InitialContext(env); Object ref = jndiContext.lookup(awc); ControllerRemoteHome home = (ControllerRemoteHome) PortableRemoteObject.narrow(ref, ControllerRemoteHome.class); Here's the exception I get in geronimo.out: 19:46:54,233 ERROR [JndiRequestHandler] JNDI request error java.lang.IllegalArgumentException at java.net.URI.create(URI.java:859) at org.openejb.ContainerIndex.getContainerIndex (ContainerIndex.java:207) at org.openejb.ContainerIndex$$FastClassByCGLIB$ $6674ccb6.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java (Inlined Compiled Code)) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke (FastMethodInvoker.java(Compiled Code)) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke (GBeanOperation.java(Inlined Compiled Code)) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke (GBeanInstance.java(Compiled Code)) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke (RawInvoker.java(Inlined Compiled Code)) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke (RawOperationInvoker.java(Compiled Code)) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept (ProxyMethodInterceptor.java(Compiled Code)) at org.openejb.ContainerIndex$$EnhancerByCGLIB$ $2edf4a7f.getContainerIndex(generated) at org.openejb.server.ejbd.JndiRequestHandler.doLookup (JndiRequestHandler.java:178) at org.openejb.server.ejbd.JndiRequestHandler.processRequest (JndiRequestHandler.java:115) at org.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java: 154) at org.openejb.server.ejbd.EjbServer.service(EjbServer.java: 87) at org.openejb.server.ejbd.EjbServer$$FastClassByCGLIB$ $d379d2ff.invoke(generated) at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java (Inlined Compiled Code)) at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke (FastMethodInvoker.java(Compiled Code)) at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke (GBeanOperation.java(Inlined Compiled Code)) at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke (GBeanInstance.java(Compiled Code)) at org.apache.geronimo.gbean.runtime.RawInvoker.invoke (RawInvoker.java(Inlined Compiled Code)) at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke (RawOperationInvoker.java(Compiled Code)) at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept (ProxyMethodInterceptor.java(Compiled Code)) at org.activeio.xnet.ServerService$$EnhancerByCGLIB$ $eb95fe48.service(generated) at org.activeio.xnet.ServicePool$2.run(ServicePool.java:67) at org.activeio.xnet.ServicePool$3.run(ServicePool.java:90) at org.apache.geronimo.pool.ThreadPool$1.run (ThreadPool.java:172) at org.apache.geronimo.pool.ThreadPool $ContextClassLoaderRunnable.run(ThreadPool.java:289) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor $Worker.run(Unknown Source) at java.lang.Thread.run(Thread.java:568) Caused by: java.net.URISyntaxException: Illegal character in path at index 1: /awc at java.net.URI$Parser.fail(URI.java:2764) at java.net.URI$Parser.checkChars(URI.java(Inlined Compiled Code)) at java.net.URI$Parser.parseHierarchical(URI.java(Compiled Code)) at java.net.URI$Parser.parse(URI.java(Compiled Code)) at java.net.URI.init(URI.java:595) at java.net.URI.create(URI.java:857) ... 29 more I've tried all variations of the jndi name in my client, but none seem to work. Any thoughts or ideas? I dont see anything wrong with your setup. The lookup should have succeeded in line 175 of JndiRequestHandler. Is there any chance you could debug the
