From: Turner, George <george.turner_at_lmco.com>
Date: Fri, 28 Aug 2009 13:11:52 -0600

Please ignore this posting. The 404 was from an invalid entry in the web.xml where the servlet mapping had multiple paths and 1.1.0-ea deployed everything to both paths and 1.1.1-ea and later did not. (As it should not have) So we have corrected our invalid web.xml.

Thanks

From: Turner, George
Sent: Friday, August 28, 2009 12:40
To: users_at_jersey.dev.java.net
Subject: [Jersey] Version change induces strange errors

I have been trying to migrate from 1.1.0-ea to both 1.1.1-ea and now 1.1.2-ea with some interesting problems. When I change the jars from the server/lib to the new version and restart the server, I get the following errors on each JSON service deployment:

[#|2009-08-28T18:20:25.808+0000|SEVERE|sun-appserver2.1|javax.enterprise.system.container.web|_ThreadID=13;_ThreadName=pool-1-thread-3;_RequestID=1cf91f8b-0a49-4690-b4ad-85ce4c913ed2;|WEB0207: Error s
tarting web context StandardEngine[com.sun.appserv].StandardHost[server].StandardContext[/CommMgmtService/client] on virtual server server
LifecycleException: java.lang.NoSuchMethodError: com.sun.jersey.api.json.JSONConfiguration.natural()Lcom/sun/jersey/api/json/JSONConfiguration$NaturalBuilder;
        at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4927)
        at org.apache.catalina.core.StandardContext.start(StandardContext.java:5324)
        at com.sun.enterprise.web.WebModule.start(WebModule.java:353)
        at com.sun.enterprise.web.LifecycleStarter.doRun(LifecycleStarter.java:58)
        at com.sun.appserv.management.util.misc.RunnableBase.runSync(RunnableBase.java:304)
        at com.sun.appserv.management.util.misc.RunnableBase._submit(RunnableBase.java:176)
        at com.sun.appserv.management.util.misc.RunnableBase.submit(RunnableBase.java:192)
        at com.sun.enterprise.web.VirtualServer.startChildren(VirtualServer.java:1742)
        at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1247)
        at org.apache.catalina.core.StandardHost.start(StandardHost.java:971)
        at com.sun.enterprise.web.LifecycleStarter.doRun(LifecycleStarter.java:58)
        at com.sun.appserv.management.util.misc.RunnableBase.runSync(RunnableBase.java:304)
        at com.sun.appserv.management.util.misc.RunnableBase.run(RunnableBase.java:341)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        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:619)
|#]

I can then build against the new jars and then deploy without seeing this error. But then what I get on "some" but not all of the services is a HTTP 404 error without any exception stack trace in the server log. I have not been able to track down why the Jersey libraries are causing this.

Can anyone tell me what has changed significantly between 1.1.0-ea and later that I can examine to see why this is occurring.

Thanks

Gene

George (Gene) Turner
[cid:image001.png_at_01CA27E1.1ACF7990]
Senior Staff Software Engineer
Information Systems & Global Services
Work:(719) 277-5244 Cell:(719) 237-0490
george.turner_at_lmco.com<mailto:george.turner_at_lmco.com>