Seam Faces, Persistence, Servlet, Catch produce NullPointerException

[mischu]

Hello together

I'm on the setup for a new project for a Glassfish 3.0.1 ( Community ) and work on the dependencies. Seam Faces and Seam Persistence works proberly. But i will also use the atch module and have add it ... it have still worked well.
But when i try to add further the Servlet module to bring Catch to work i get a NullPointerException.

There is no way for me to consider the problem.

Any suggestions?

Thanks for help

Here are my seam dependencies

    <properties>
        <org.richfaces.bom.version>4.0.0.20110209-M6</org.richfaces.bom.version>
        <seam.bom.version>3.0.0.b09</seam.bom.version>
    </properties>

    <dependencyManagement>
        <dependencies>
            <dependency>
                <groupId>org.jboss.seam</groupId>
                <artifactId>seam-bom</artifactId>
                <version>${seam.bom.version}</version>
                <scope>import</scope>
                <type>pom</type>
            </dependency>
        </dependencies>
    </dependencyManagement>

    <dependencies>
        <!--seam faces-->
        <dependency>
            <groupId>org.jboss.seam.faces</groupId>
            <artifactId>seam-faces</artifactId>
        </dependency>
        <!-- without this a ClassNotFoundException occurr -->
        <dependency> 
            <groupId>joda-time</groupId>
            <artifactId>joda-time</artifactId>
            <version>1.6</version>
        </dependency>
        <!-- without this a ClassNotFoundException occurr -->
        <dependency>
            <groupId>org.jboss.logging</groupId>
            <artifactId>jboss-logging-logmanager</artifactId>
            <version>2.2.0.CR2</version>
        </dependency>

        <!--seam catch-->
        <dependency>
            <groupId>org.jboss.seam.catch</groupId>
            <artifactId>seam-catch</artifactId>
        </dependency>

        <!--seam servlet-->
        <dependency>
            <groupId>org.jboss.seam.servlet</groupId>
            <artifactId>seam-servlet</artifactId>
        </dependency>
        <dependency>
            <groupId>org.jboss.logging</groupId>
            <artifactId>jboss-logging</artifactId>
            <version>3.0.0.Beta4</version>
        </dependency>

        <!--seam persistence-->
        <dependency>
            <groupId>org.jboss.seam.persistence</groupId>
            <artifactId>seam-persistence</artifactId>
        </dependency>

        <!--Hibernate-->
        <dependency>
            <groupId>org.hibernate</groupId>
            <artifactId>hibernate-annotations</artifactId>
            <version>3.5.6-Final</version>
        </dependency>
        <dependency>
            <groupId>org.hibernate</groupId>
            <artifactId>hibernate-validator</artifactId>
            <version>4.1.0.Final</version>
        </dependency>
        <dependency>
            <groupId>org.hibernate</groupId>
            <artifactId>hibernate-search</artifactId>
        </dependency>
    </dependencies>

And here the complete Stacktrace:

[#|2011-02-18T15:21:39.794+0100|SEVERE|glassfish3.0.1|javax.enterprise.system.core.com.sun.enterprise.v3.server|_ThreadID=23;_ThreadName=Thread-1;|Exception while deploying the app
java.lang.NullPointerException
 at com.sun.enterprise.deployment.OrderingDescriptor$Node.access$300(OrderingDescriptor.java:429)
 at com.sun.enterprise.deployment.OrderingDescriptor.sort(OrderingDescriptor.java:164)
 at com.sun.enterprise.deployment.archivist.WebArchivist.readStandardFragments(WebArchivist.java:389)
 at com.sun.enterprise.deployment.archivist.WebArchivist.postAnnotationProcess(WebArchivist.java:301)
 at com.sun.enterprise.deployment.archivist.WebArchivist.postAnnotationProcess(WebArchivist.java:81)
 at com.sun.enterprise.deployment.archivist.Archivist.readRestDeploymentDescriptors(Archivist.java:397)
 at com.sun.enterprise.deployment.archivist.Archivist.openWith(Archivist.java:259)
 at com.sun.enterprise.deployment.archivist.ApplicationFactory.openWith(ApplicationFactory.java:222)
 at org.glassfish.javaee.core.deployment.DolProvider.load(DolProvider.java:152)
 at org.glassfish.javaee.core.deployment.DolProvider.load(DolProvider.java:79)
 at com.sun.enterprise.v3.server.ApplicationLifecycle.loadDeployer(ApplicationLifecycle.java:612)
 at com.sun.enterprise.v3.server.ApplicationLifecycle.setupContainerInfos(ApplicationLifecycle.java:554)
 at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:262)
 at com.sun.enterprise.v3.server.ApplicationLifecycle.deploy(ApplicationLifecycle.java:183)
 at org.glassfish.deployment.admin.DeployCommand.execute(DeployCommand.java:272)
 at com.sun.enterprise.v3.admin.CommandRunnerImpl$1.execute(CommandRunnerImpl.java:305)
 at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:320)
 at com.sun.enterprise.v3.admin.CommandRunnerImpl.doCommand(CommandRunnerImpl.java:1176)
 at com.sun.enterprise.v3.admin.CommandRunnerImpl.access$900(CommandRunnerImpl.java:83)
 at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1235)
 at com.sun.enterprise.v3.admin.CommandRunnerImpl$ExecutionContext.execute(CommandRunnerImpl.java:1224)
 at com.sun.enterprise.v3.admin.AdminAdapter.doCommand(AdminAdapter.java:365)
 at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:204)
 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:245)
 at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:791)
 at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:693)
 at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:954)
 at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:170)
 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.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:330)
 at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:309)
 at java.lang.Thread.run(Thread.java:619)
|#]

[#|2011-02-18T15:21:42.601+0100|INFO|glassfish3.0.1|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=21;_ThreadName=Thread-1;|Updating configuration from org.apache.felix.fileinstall-autodeploy-bundles.cfg|#]

[#|2011-02-18T15:21:42.608+0100|INFO|glassfish3.0.1|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=21;_ThreadName=Thread-1;|Installed C:\java\glassfish\v3\glassfish\modules\autostart\org.apache.felix.fileinstall-autodeploy-bundles.cfg|#]

[#|2011-02-18T15:21:42.610+0100|INFO|glassfish3.0.1|javax.enterprise.system.std.com.sun.enterprise.v3.services.impl|_ThreadID=24;_ThreadName=Thread-1;|{felix.fileinstall.poll (ms) = 5000, felix.fileinstall.dir = C:\java\glassfish\v3\glassfish\domains\domain1\autodeploy\bundles, felix.fileinstall.debug = 1, felix.fileinstall.bundles.new.start = true, felix.fileinstall.tmpdir = C:\Users\Machnix\AppData\Local\Temp\fileinstall-5934476343123332764, felix.fileinstall.filter = null}|#]

[#|2011-02-18T15:22:26.418+0100|INFO|glassfish3.0.1|javax.enterprise.system.tools.admin.com.sun.enterprise.v3.admin|_ThreadID=25;_ThreadName=Thread-1;|Server shutdown initiated|#]

[#|2011-02-18T15:22:28.309+0100|SEVERE|glassfish3.0.1|com.sun.grizzly.config.GrizzlyServiceListener|_ThreadID=23;_ThreadName=Thread-1;|service exception
java.lang.RuntimeException: ClientAbortException: java.nio.channels.ClosedChannelException
 at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:236)
 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:245)
 at com.sun.grizzly.http.ProcessorTask.invokeAdapter(ProcessorTask.java:791)
 at com.sun.grizzly.http.ProcessorTask.doProcess(ProcessorTask.java:693)
 at com.sun.grizzly.http.ProcessorTask.process(ProcessorTask.java:954)
 at com.sun.grizzly.http.DefaultProtocolFilter.execute(DefaultProtocolFilter.java:170)
 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.AbstractThreadPool$Worker.doWork(AbstractThreadPool.java:330)
 at com.sun.grizzly.util.AbstractThreadPool$Worker.run(AbstractThreadPool.java:309)
 at java.lang.Thread.run(Thread.java:619)
Caused by: ClientAbortException: java.nio.channels.ClosedChannelException
 at com.sun.grizzly.tcp.http11.GrizzlyOutputBuffer.doFlush(GrizzlyOutputBuffer.java:436)
 at com.sun.grizzly.tcp.http11.GrizzlyOutputBuffer.flush(GrizzlyOutputBuffer.java:402)
 at com.sun.grizzly.tcp.http11.GrizzlyOutputStream.flush(GrizzlyOutputStream.java:138)
 at com.sun.enterprise.v3.admin.AdminAdapter.service(AdminAdapter.java:233)
 ... 17 more
Caused by: java.nio.channels.ClosedChannelException
 at sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:126)
 at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:324)
 at com.sun.grizzly.util.OutputWriter.flushChannel(OutputWriter.java:106)
 at com.sun.grizzly.util.OutputWriter.flushChannel(OutputWriter.java:74)
 at com.sun.grizzly.http.SocketChannelOutputBuffer.flushChannel(SocketChannelOutputBuffer.java:321)
 at com.sun.grizzly.http.SocketChannelOutputBuffer.flushBuffer(SocketChannelOutputBuffer.java:392)
 at com.sun.grizzly.http.SocketChannelOutputBuffer.flush(SocketChannelOutputBuffer.java:370)
 at com.sun.grizzly.http.ProcessorTask.action(ProcessorTask.java:1174)
 at com.sun.grizzly.tcp.Response.action(Response.java:266)
 at com.sun.grizzly.tcp.http11.GrizzlyOutputBuffer.doFlush(GrizzlyOutputBuffer.java:431)
 ... 20 more
|#]

[lightguard]

I've noticed this problem with Servlet as well, however, I don't know the cause :(

[swd847]

Based on the stack trace I would say it is a problems with servlets web-fragment.xml.

You could try removing web-fragment.xml and moving the contents into web.xml.

[mimik789]

Removing / commenting this in web-fragment.xml of seam-servlet(-impl) and repackaging jar fixed this exception for me on GF 3.1 b43 (web)

   <ordering>
      <after>
         <name>WeldServlet</name>
      </after>
      <before>
         <others/>
      </before>
   </ordering>

But I'm facing another issue regarding performance of deployment - adding seam-servlet slowed down deployment by 5 times (without ~ 20sec vs ~115sec when inc.).
I suppose that is not expected behaviour?

[swd847]

What version of weld and seam solder are you using?

[mimik789]

Newest as in Seam3 Beta2 release,
but I tweaked modules a bit (these wich uses type-safe loggers/messagebundles for use with slf4j-api:1.6.1) - I had to do that because of nasty exceptions I got when tried - the 'offical way' - ie. adding '-Djboss.i18n.generate-proxies=true' to GF JVM opts.

vers:
Solder 3.0.0.Beta4
Servlet 3.0.0.Beta2

here I roughly described those logging tweaks:
http://seamframework.org/Community/DeploymentExceptionWithSeamFaces300Beta1#comment149540

[swd847]

Which version of weld are you using?

There were significant portable extension performance improvements between the version of weld included in jboss 6 final and weld 1.1 final.

Stuart

[mimik789]

actually this version:
http://java.net/jira/secure/attachment/44919/weld-osgi-bundle.jar

because I pretty sure that 'current' from GF 3.1 b43 doesn't containg fix for:
https://issues.jboss.org/browse/WELD-846

(btw, I run these tests and ony first passing for me - see my comment:
http://java.net/jira/secure/ViewProfile.jspa?name=mimik789)

[swd847]

Would you be able to run a profiler on the startup and see what is causing the bottleneck?

[mimik789]

That would be the best solution.
Unfortunately currently I've lack of required knowledge to do that (once tried YourKit Java Profiler) but I know there is eclipse TPTP project - should (can) I use it to figure out these strange deployment slowdowns, on gf 3.1?

[swd847]

Yourkit is probably the easiest, as it requires no setup.

If you get the trial version, tell it to attach to gf and then start CPU profiling in sampling mode. Once startup is complete capture a snapshot, and either look at where the hot spots are or send the snapshot to me.

I have never managed to get TPTP to work, your milage may vary.

[swd847]

I created WELD-859 for this issue.

[mimik789]

I have good news for those of you who like to deploy seam3 modules on GF3.

1. seam-servlet module performance issues on webapp deployment/load/startup were gone for me on GF 3.1 b_43 (web)!, when using build from source recently fixed weld-core ie.


2. seam3 modules under glassfish 3.1 b_43 (with fixed weld-core, see below) should be working now (if you fix logging problems, with type-safe loggers that needs concreate classes for annotated interfaces (see my: previous comment #comment149562; and also remove ordering part from seam-servlet's web-fragments.xml see: #comment149556)

Seam3 Beta2 release modules that I deployed with success (webapp at least can start and display simple JSF page) on GF3 (haven't tested it thoroughly). These marked with * needs to be fixed for logging issues:

• seam-solder: 3.0.0.Beta4*


• seam-catch3.0.0.Beta2


• seam-config-xml:3.0.0.Beta3


• seam-faces:3.0.0.Beta3


• seam-international:3.0.0.Beta2*


• seam-persistence:3.0.0.Beta4


• seam-security:3.0.0.Beta2


• seam-servlet:3.0.0.Beta2*

fixing weld-core for GF3.1_b43:

git clone git://github.com/stuartwdouglas/core.git weld-core.git_stuartwdouglas.fork
mvn clean package -Pbundles

and then replace GF 3.1_b43's: 
   glassfish\glassfish\modules\weld-osgi-bundle.jar 
with built:
   weld-core.git_stuartwdouglas.fork\bundles\osgi\target\weld-osgi-bundle-1.1.0-SNAPSHOT.jar

[mimik789]

small error in my prv post:
you need to switch to WELD-859 branch after cloning ie.

git clone git://github.com/stuartwdouglas/core.git weld-core.git_stuartwdouglas.fork
git checkout WELD-859
mvn clean package -Pbundles

or you can use my build of weld-osgi-bundle.jar which is here:
http://java.net/jira/secure/attachment/45052/weld-osgi-bundle.jar

[mischu]

With the fixed Wel-Core it works for me ... thanks a lot