| MHenke on Nov 17, 2008 at 7:51:39 AM (# 15) Almost similar, huh?
In terms of "my Tomcat log shows exceptions", maybe. :)
However, this kind of (runtime) exception (Caused by: java.lang.NoSuchMethodError: org.apache.naming.NamingContextBindingsEnumeration) is typically caused by a compiletime/runtime conflict.
Check your build process that your application is actually compiled against the same Java and server (Tomcat) version that it's runing at.
That specific exception seems JNDI related. It's also possible, that your Tomcat is loading an incompatible JNDI implementation (at runtime, vs. compiletime).
Just a shot in the dark, you can look for an implementation of "NamingContextBindingsEnumeration" in your Tomcat classpath, maybe in WEB-INF/lib (something like "Naming-[...].jar"). If there's such a thing, chances are that it's an incompatible (older) version.
khyati on Sep 17, 2009 at 1:05:16 AM (# 16)Hii
I have created a web service and while running the application getting simillar error.Can anybody help me out?its very urgent.
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.lang.reflect.InvocationTargetException
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}hostname:DSCP12371
java.lang.reflect.InvocationTargetException
at org.apache.axis.message.SOAPFaultBuilder.createFault(SOAPFaultBuilder
.java:222)
at org.apache.axis.message.SOAPFaultBuilder.endElement(SOAPFaultBuilder.
java:129)
at org.apache.axis.encoding.DeserializationContext.endElement(Deserializ
ationContext.java:1087)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source
)
at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknow
n Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContent
Dispatcher.dispatch(Unknown Source)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Un
known Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:375)
at org.apache.axis.encoding.DeserializationContext.parse(Deserialization
Context.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnders
tandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at localhost.axis.VCM_CRM_Integration_package_jws.VCM_CRM_Integration_pa
ckageSoapBindingStub.login(VCM_CRM_Integration_packageSoapBindingStub.java:101)
at IntegrationClientpack.main(IntegrationClientpack.java:37)
MHenke on Sep 17, 2009 at 5:36:43 AM (# 17)
This message has been edited.This is by no means similar, and it's far to less information.
Try to catch the InvocationTargetException (at the client, I'd guess) and trace the original cause of the error.
try {
whateverMayCauseThisShit();
}
catch(RuntimeException runtimeException) {
Throwable cause = runtimeException.getCause();
if(cause instanceof InvocationTargetException) {
Throwable targetException = ((InvocationTargetException)cause).getTargetException();
targetException.printStackTrace();
}
}
khyati on Sep 18, 2009 at 12:16:29 AM (# 18)hii,
I have tried getting the original cause of error, inside tomcat in logs its giving:
Sep 18, 2009 12:35:54 PM com.sun.xml.ws.server.sei.EndpointMethodHandler invoke
SEVERE: null
java.lang.NoClassDefFoundError
at com.vignette.as.client.javabean.OpsFactory.createRemote(OpsFactory.ja
va:226)
at com.vignette.as.client.javabean.OpsFactory.create(OpsFactory.java:96)
at com.vignette.as.client.javabean.Site.getLocalOps(Site.java:1018)
at com.vignette.as.client.javabean.Site.findByName(Site.java:438)
at Integration.impl.VCM_CRM_Integration.login(VCM_CRM_Integration.java:4
3)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sun.xml.ws.api.server.InstanceResolver$1.invoke(InstanceResolver.
java:246)
at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:146)
at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethod
Handler.java:257)
at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTub
e.java:93)
at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:24
3)
at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdap
ter.java:444)
at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244
)
at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAd
apter.java:135)
at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doGet(WSServl
etDelegate.java:129)
at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doPost(WSServ
letDelegate.java:160)
at com.sun.xml.ws.transport.http.servlet.WSServlet.doPost(WSServlet.java
:75)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:233)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:175)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
a:263)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ss(Http11Protocol.java:584)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:44
7)
at java.lang.Thread.run(Thread.java:595)
I have added all the jar files that are required for compilling this web service. if i use the method in stand alone program its working fine, but exposing it as a web service, its giving this error. please help me out with is.
MHenke on Sep 18, 2009 at 3:47:52 AM (# 19)>I have added all the jar files that are required for compilling this web service.
Great!
Nevertheless, you've been missing something for the runtime of the service. That's a major difference.
The java.lang.NoClassDefFoundError exception is pretty explicit here.
Double check the runtime environment of you service, that is, Tomcat. A good starting point to look for missing classes is the "OpsFactory"-thing. Maybe a version conflict (third party library)?
And take into account that the class loading mechanism of Tomcat is fundamentally different from a "stand alone" scenario.
Good luck...
khyati on Sep 22, 2009 at 2:56:26 AM (# 20)Hiii
thanks for your reply..
i have deployed the same web service on glassfish server,by netbeans IDE,its working fine.
Here com.vignette.as.client.javabean.OpsFactory is a java bean so can you tell please me does Tomcat supports EJB?if not,can i deploy WebService which is using EJB on Tomcat by adding ejb.jar in classpath. or how to deploy webservice which is using EJB on Tomcat.
And how to check the runtime environment of Tomcat.
How is class loading mechanism of tomcat different from Stand alone scenario.
MHenke on Sep 22, 2009 at 8:29:33 AM (# 21)>OpsFactory is a java bean so can you tell please me does Tomcat supports EJB?if not,can i deploy WebService which is using EJB on Tomcat by adding ejb.jar in classpath. or how to deploy webservice which is using EJB on Tomcat.
Nope, Tomcat dosn't support EJBs. It's a Servlet container and implements merely those parts of the J2EE specification that are required for Servlets/JSPs.
You can't run an app on Tomcat that needs full EJB/J2EE support.
>And how to check the runtime environment of Tomcat.
By checking the directories that are used by the Tomcat classloader.
>How is class loading mechanism of tomcat different from Stand alone scenario.
In terms of Tomcat using it's own classloader hierarchy, not the one of the JRE.
| 
Error during Tomcat Startup : java.lang.reflect.InvocationTargetException