users@jersey.java.net

Error while Resin server startup

From: Bhimraju K <bhimraju.k_at_tavant.com>
Date: Tue, 10 Nov 2009 13:40:26 -0800

Hi,

I am using jersey with spring and configured a JAXBContextResolver. I
started getting the following error on start up of the Resin server.

 

[12:42:12.817] {resin-15} Initiating Jersey application, version
'Jersey: 1.1.2-ea 08/25/2009 04:39 PM'

[12:42:12.848] {resin-15}
com.sun.jersey.spi.service.ServiceConfigurationError:
jersey-server-components: A dependent class,
org/jvnet/mimepull/MIMEParsingException, of the class
com.sun.jersey.multipart.impl.MultiPartReader implementing the provider
class java.lang.Object is not found. The provider implementation is
ignored.

[12:42:12.848] {resin-15} at
com.sun.jersey.spi.service.ServiceFinder.fail(ServiceFinder.java:388)

[12:42:12.848] {resin-15} at
com.sun.jersey.spi.service.ServiceFinder.access$200(ServiceFinder.java:1
44)

[12:42:12.848] {resin-15} at
com.sun.jersey.spi.service.ServiceFinder$LazyClassIterator.next(ServiceF
inder.java:595)

[12:42:12.848] {resin-15} at
com.sun.jersey.spi.service.ServiceFinder$LazyClassIterator.next(ServiceF
inder.java:571)

[12:42:12.848] {resin-15} at
com.sun.jersey.spi.service.ServiceFinder.toClassArray(ServiceFinder.java
:374)

[12:42:12.848] {resin-15} at
com.sun.jersey.server.impl.application.WebApplicationImpl.initiate(WebAp
plicationImpl.java:437)

[12:42:12.848] {resin-15} at
com.sun.jersey.spi.spring.container.servlet.SpringServlet.initiate(Sprin
gServlet.java:97)

[12:42:12.848] {resin-15} at
com.sun.jersey.spi.container.servlet.ServletContainer$InternalWebCompone
nt.initiate(ServletContainer.java:242)

[12:42:12.848] {resin-15} at
com.sun.jersey.spi.container.servlet.WebComponent.load(WebComponent.java
:466)

[12:42:12.848] {resin-15} at
com.sun.jersey.spi.container.servlet.WebComponent.init(WebComponent.java
:182)

[12:42:12.848] {resin-15} at
com.sun.jersey.spi.container.servlet.ServletContainer.init(ServletContai
ner.java:281)

[12:42:12.848] {resin-15} at
com.sun.jersey.spi.container.servlet.ServletContainer.init(ServletContai
ner.java:442)

[12:42:12.848] {resin-15} at
javax.servlet.GenericServlet.init(GenericServlet.java:70)

[12:42:12.848] {resin-15} at
com.caucho.server.dispatch.ServletConfigImpl.createServletImpl(ServletCo
nfigImpl.java:833)

[12:42:12.848] {resin-15} at
com.caucho.server.dispatch.ServletConfigImpl.createServlet(ServletConfig
Impl.java:735)

[12:42:12.848] {resin-15} at
com.caucho.server.dispatch.ServletManager.init(ServletManager.java:159)

[12:42:12.848] {resin-15} at
com.caucho.server.webapp.WebApp.start(WebApp.java:1874)

[12:42:12.848] {resin-15} at
com.caucho.server.deploy.DeployController.startImpl(DeployController.jav
a:667)

[12:42:12.848] {resin-15} at
com.caucho.server.deploy.DeployController.restartImpl(DeployController.j
ava:630)

[12:42:12.848] {resin-15} at
com.caucho.server.deploy.StartAutoRedeployAutoStrategy.alarm(StartAutoRe
deployAutoStrategy.java:177)

[12:42:12.848] {resin-15} at
com.caucho.server.deploy.DeployController.handleAlarm(DeployController.j
ava:789)

[12:42:12.848] {resin-15} at
com.caucho.util.Alarm.handleAlarm(Alarm.java:375)

[12:42:12.848] {resin-15} at
com.caucho.util.Alarm.run(Alarm.java:345)

[12:42:12.848] {resin-15} at
com.caucho.util.ThreadPool$Item.runTasks(ThreadPool.java:743)

[12:42:12.848] {resin-15} at
com.caucho.util.ThreadPool$Item.run(ThreadPool.java:662)

[12:42:12.848] {resin-15} at java.lang.Thread.run(Unknown Source)

 

Please let me know what's going wrong. I tried googling about this
problem but couldn't get anything.

 

Regards,

Bhimraju K

 


Check us out on Facebook, visit www.facebook.com/TavantTechnologies

Any comments or statements made in this email are not necessarily those of Tavant Technologies.
The information transmitted is intended only for the person or entity to which it is addressed and may
contain confidential and/or privileged material. If you have received this in error, please contact the
sender and delete the material from any computer. All e-mails sent from or to Tavant Technologies
may be subject to our monitoring procedures.