Since I've been using the servicemix-web WAR that is built from the
examples, it seems to be working better. The strange thing is that my
servicemix-http binding and cxf binding were being bound to their defined
ports in the xbean.xml, rather than be rewritten to the jbi/ url like the
docs mentioned. So I was just using that as I fixed some various services
issues arising from being in the tomcat container in my own code. After a
few redeployments with little fixes to my servicemix-bean components,
servicemix decided to start rewriting my servicemix-http urls for whatever
reason to the correct jbi/ urls, but that URL, while it now exists, fails
when I hit it with the exception (version 3.3):
HTTP Status 500 -
------------------------------
*type* Exception report
*message*
*description* *The server encountered an internal error () that prevented it
from fulfilling this request.*
*exception*
javax.servlet.ServletException: Servlet.init() for servlet
HttpManagedServlet threw exception
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
java.lang.Thread.run(Thread.java:619)
*root cause*
java.lang.IllegalStateException: ServerManager is not managed
org.apache.servicemix.http.jetty.JettyContextManager.getMainProcessor(JettyContextManager.java:489)
org.apache.servicemix.http.HttpComponent.getMainProcessor(HttpComponent.java:364)
org.apache.servicemix.http.HttpManagedServlet.init(HttpManagedServlet.java:78)
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845)
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
java.lang.Thread.run(Thread.java:619)
*note* *The full stack trace of the root cause is available in the Apache
Tomcat/6.0.18 logs.*
I'm really confused as to why the deployment was wrong in the first place,
why it changed but why it changed to the correct URL but then fails
everytime....
Any help would be appreciated... I figured the servicemix-web would be a
little more transparent with my services, but it's seeming not be so :(
Ryan