quality@glassfish.java.net

Re: Deployment of our JEE5 app on GlassFish v 3.1 build 25

From: Hong Zhang <hong.hz.zhang_at_oracle.com>
Date: Tue, 26 Oct 2010 10:56:23 -0400

Hi, Wouter
   There were a few similar issues filed for this already, e.g:

https://glassfish.dev.java.net/issues/show_bug.cgi?id=13452

   Jerome has fixed it earlier this week and the fix will be in the next
build (b26). Please file an issue if you still see this problem with the
next promoted build.

  Thanks,

- Hong

On 10/26/2010 10:50 AM, Wouter van Reeven wrote:
> Hi all,
>
>
> I just downloaded and installed GlassFish v3.1 build 25. Next I created
> a JDBC ConnectionPool and Resource to our Oracle 11g database via the
> admin console and that went ok. Great!
>
> Next I tried to deploy our current JEE5 app (that runs fine on GFv2.1)
> on GFv3.1 and this failed. I didn't expect it to deploy fine so I'll try
> to tweak it further. However, loads of errors like this
>
> [#|2010-10-26T16:44:52.213+0200|SEVERE|glassfish3.1|javax.enterprise.system.tools.admin.org.glassfish.deployment.admin|_ThreadID=15;_ThreadName=Thread-1;|Exception while processing org/slf4j/impl/Log4jLoggerFactory.class inside slf4j-log4j12-1.5.6 of size 0
> java.lang.NullPointerException
> at com.sun.enterprise.v3.server.ReadableArchiveScannerAdapter.onSelectedEntries(ReadableArchiveScannerAdapter.java:107)
> at org.glassfish.hk2.classmodel.reflect.Parser.doJob(Parser.java:217)
> at org.glassfish.hk2.classmodel.reflect.Parser.access$100(Parser.java:59)
> at org.glassfish.hk2.classmodel.reflect.Parser$2.call(Parser.java:180)
> at org.glassfish.hk2.classmodel.reflect.Parser$2.call(Parser.java:169)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138) i
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
>
> were logged. Would this be an issue worth logging?
>
>
> Thanks, Wouter
>
>