Site Navigation

Mar 22, 2010

NullPointerException when Deploying EJB Client

Duke Waving
While testing the labs for one of our course a week or two back, I ran into the following error. A null pointer exception when an EJB 3 client is deployed. There are no errors in the source code.

Warning: Could not find file /export/home/student/sges-v3/glassfish/domains/domain1/generated/xml/EJB31/EJB31Client.jar to copy.
Copying 1 file to /export/home/student/solutions/mod02_sessions/EJB31/dist
Copying 4 files to /export/home/student/solutions/mod02_sessions/EJB31/dist/EJB31Client
Copying 1 file to /export/home/student/solutions/mod02_sessions/EJB31/dist/EJB31Client
at org.glassfish.appclient.client.acc.ACCLogger$
at Method)
at org.glassfish.appclient.client.acc.ACCLogger.reviseLogger(
at org.glassfish.appclient.client.acc.ACCLogger.init(
at org.glassfish.appclient.client.acc.ACCLogger.init(
at org.glassfish.appclient.client.AppClientFacade.createBuilder(
at org.glassfish.appclient.client.AppClientFacade.prepareACC(
at org.glassfish.appclient.client.acc.agent.AppClientContainerAgent.premain(
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
at java.lang.reflect.Method.invoke(
at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(
at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(
Java Result: 1

When you look on the app server, EJB31Client.jar is, in fact, in the wrong place. It turns out that this is a bug with GlassFish V3 and Java 6 update 18. To solve the problem, drop back to Java 6 update 17 or upgrade to GlassFish 3.0.1 when it becomes available.

For more information see the following links.
Post a Comment

Favorite Links Feed