Yes, there was an issue logged under webbeans for this already:
https://glassfish.dev.java.net/issues/show_bug.cgi?id=9390
- Hong
Arun Gupta wrote:
> Deploying a simple Dynamic Web project using Eclipse on 62 is throwing
> the following exception:
>
> INFO: DOL Loading time108
> WARNING: Exception while dispatching an event
> java.lang.NullPointerException
> at
> org.glassfish.webbeans.WebBeansDeployer.event(WebBeansDeployer.java:125)
> at org.glassfish.kernel.event.EventsImpl.send(EventsImpl.java:88)
> at
> org.glassfish.internal.data.ApplicationInfo.load(ApplicationInfo.java:205)
>
> at
> com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:310)
>
> at
> com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:174)
>
> at
> org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:270)
>
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl$4.execute(CommandRunnerImpl.java:403)
>
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:418)
>
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:505)
>
> at
> com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:138)
>
> at
> com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:332)
> at
> com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:184)
> at
> com.sun.grizzly.tcp.http11.GrizzlyAdapter.service(GrizzlyAdapter.java:166)
>
> at
> com.sun.enterprise.v3.server.HK2Dispatcher.dispath(HK2Dispatcher.java:100)
>
> at
> com.sun.enterprise.v3.services.impl.ContainerMapper.service(ContainerMapper.java:215)
>
> at
> com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:752)
> at
> com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:660)
> at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:911)
> at
> com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:164)
>
> at
> com.sun.grizzly.DefaultProtocolChain.executeProtocolFilter(DefaultProtocolChain.java:135)
>
> at
> com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:102)
>
> at
> com.sun.grizzly.DefaultProtocolChain.execute(DefaultProtocolChain.java:88)
>
> at
> com.sun.grizzly.http.HttpProtocolChain.execute(HttpProtocolChain.java:76)
> at
> com.sun.grizzly.ProtocolChainContextTask.doCall(ProtocolChainContextTask.java:53)
>
> at
> com.sun.grizzly.SelectionKeyContextTask.call(SelectionKeyContextTask.java:57)
>
> at com.sun.grizzly.ContextTask.run(ContextTask.java:69)
> at
> com.sun.grizzly.util.FixedThreadPool$BasicWorker.dowork(FixedThreadPool.java:379)
>
> at
> com.sun.grizzly.util.FixedThreadPool$BasicWorker.run(FixedThreadPool.java:360)
>
> at java.lang.Thread.run(Thread.java:637)
>
> INFO: Loading application ee61 at /ee61
>
> No WebBeans are involved, the project gets deployed correctly and all
> the artifacts (JSP & Servlets) are rendered correctly.
>
> Is this a known issue before I start digging further ?
>
> -Arun
>