Upgrade from 0.8.1 to 0.9.0

173 views
Skip to first unread message

Dhananjay Bagi

unread,
Oct 21, 2013, 5:09:55 PM10/21/13
to jets3t...@googlegroups.com
Hello,

I have changed my maven dependency version in pom.xml from 0.8.1 to 0.9.0. Since then I've been getting the below IllegalStateException
upon calling the checkBucketStatus method of RestS3Service.

org.jets3t.service.ServiceException: Request Error: java.lang.IllegalStateException: Invalid class name: org.jets3t.service.utils.RestUtils$ConnManagerFactory
at org.jets3t.service.impl.rest.httpclient.RestStorageService.performRequest(RestStorageService.java:574)
at org.jets3t.service.impl.rest.httpclient.RestStorageService.performRequest(RestStorageService.java:281)
at org.jets3t.service.impl.rest.httpclient.RestStorageService.performRestHead(RestStorageService.java:942)
at org.jets3t.service.impl.rest.httpclient.RestStorageService.checkBucketStatus(RestStorageService.java:1332)
at com.fuelquest.mothra.common.util.AmazonS3FileUtils.uploadFileToAmazonS3(AmazonS3FileUtils.java:324)
at com.fuelquest.fqng.esb.dcs.bean.DeliveryProcessingBean.onMessageExchange(DeliveryProcessingBean.java:243)
at org.apache.servicemix.bean.BeanEndpoint.onProviderExchange(BeanEndpoint.java:254)
at org.apache.servicemix.bean.BeanEndpoint.process(BeanEndpoint.java:241)
at org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:630)
at org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:587)
at org.apache.servicemix.common.AsyncBaseLifeCycle.onMessageExchange(AsyncBaseLifeCycle.java:544)
at org.apache.servicemix.common.SyncLifeCycleWrapper.onMessageExchange(SyncLifeCycleWrapper.java:62)
at org.apache.servicemix.jbi.messaging.DeliveryChannelImpl.processInBound(DeliveryChannelImpl.java:631)
at org.apache.servicemix.jbi.nmr.flow.AbstractFlow.doRouting(AbstractFlow.java:185)
at org.apache.servicemix.jbi.nmr.flow.seda.SedaFlow.doRouting(SedaFlow.java:168)
at org.apache.servicemix.jbi.nmr.flow.seda.SedaQueue$1.run(SedaQueue.java:134)
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)
Caused by: java.lang.IllegalStateException: Invalid class name: org.jets3t.service.utils.RestUtils$ConnManagerFactory
at org.apache.http.impl.client.AbstractHttpClient.createClientConnectionManager(AbstractHttpClient.java:319)
at org.apache.http.impl.client.AbstractHttpClient.getConnectionManager(AbstractHttpClient.java:467)
at org.apache.http.impl.client.AbstractHttpClient.createHttpContext(AbstractHttpClient.java:285)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:868)
at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:822)
at org.jets3t.service.impl.rest.httpclient.RestStorageService.performRequest(RestStorageService.java:334)

Could you please help me with this?

Thanks,
Dhananjay. 


James Murty

unread,
Oct 21, 2013, 5:57:01 PM10/21/13
to jets3t...@googlegroups.com
Hi,

Your stack trace looks pretty similar this one [1] from StackOverflow,
which was apparently caused by having some JetS3t jar files missing
from the classpath.

That's a pretty opaque error message if that is really the problem,
but hopefully it's something this simple and easy to fix.

Hope this helps,
James

[1]: http://stackoverflow.com/questions/10144188/jets3t-connects-without-exception-but-invalid-class-name-when-i-try-to-do-a

---
jamesmurty.com
> --
> You received this message because you are subscribed to the Google Groups
> "JetS3t Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jets3t-users...@googlegroups.com.
> To post to this group, send email to jets3t...@googlegroups.com.
> Visit this group at http://groups.google.com/group/jets3t-users.
> For more options, visit https://groups.google.com/groups/opt_out.

Dhananjay Bagi

unread,
Oct 22, 2013, 9:58:35 AM10/22/13
to jets3t...@googlegroups.com
Thank you!
Reply all
Reply to author
Forward
0 new messages