Rookie tuning Error (iii)--jboss and JDK version number incompatibility cause WebService call error

Source: Internet
Author: User
Tags soap jboss

Environment:

jdk1.6

Jboss 5.1.0.GA


Description of the problem:

The EJB publication Webserivce has been successful and has been able to access the WSDL file successfully;
Using the Axis1 sample/client class Dynamicinvoker test, the program error.


Error message:


Client

Exception in thread "main" Axisfault FaultCode: {http://schemas.xmlsoap.org/soap/envelope/}server.userexception FaultSubcode:faultString:org.xml.sax.SAXParseException:Premature end of file. FaultActor:faultNode:faultDetail: {http://xml.apache.org/axis/}stacktrace:org.xml.sax.saxparseexception: Premature end of file.at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException ( Unknown source) at Com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError (Unknown source) at Com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError (Unknown Source) at Com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError (Unknown Source) at Com.sun.org.apache.xerces.internal.impl.xmldocumentscannerimpl$prologdriver.next (Unknown Source) at Com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next (Unknown Source) at Com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next (Unknown Source) at Com.sun.org.apache.xerces.internal.Impl. Xmldocumentfragmentscannerimpl.scandocument (Unknown Source) at Com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse (Unknown Source) at Com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse (Unknown Source) at Com.sun.org.apache.xerces.internal.parsers.XMLParser.parse (Unknown Source) at Com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse (Unknown Source) at Com.sun.org.apache.xerces.internal.jaxp.saxparserimpl$jaxpsaxparser.parse (Unknown Source) at Javax.xml.parsers.SAXParser.parse (Unknown Source)

Server (Jboss) side error message:

ERROR [SOAPFAULTHELPERJAXWS] SOAP request Exceptionjava.lang.UnsupportedOperationException:setProperty must be Overridden by all subclasses of Soapmessageat Javax.xml.soap.SOAPMessage.setProperty (Unknown Source) at Org.jboss.ws.core.soap.soapmessageimpl.<init> (soapmessageimpl.java:87) at Org.jboss.ws.core.soap.MessageFactoryImpl.createMessage (messagefactoryimpl.java:215) at Org.jboss.ws.core.soap.MessageFactoryImpl.createMessage (messagefactoryimpl.java:193) at Org.jboss.wsf.stack.jbws.RequestHandlerImpl.processRequest (requesthandlerimpl.java:455) at Org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleRequest (requesthandlerimpl.java:295) at Org.jboss.wsf.stack.jbws.RequestHandlerImpl.doPost (requesthandlerimpl.java:205) at Org.jboss.wsf.stack.jbws.RequestHandlerImpl.handleHttpRequest (requesthandlerimpl.java:131) at Org.jboss.wsf.common.servlet.AbstractEndpointServlet.service (abstractendpointservlet.java:85) at Javax.servlet.http.HttpServlet.service (httpservlet.java:717) at Org.apache.catalina. Core. Applicationfilterchain.internaldofilter (applicationfilterchain.java:290) at Org.apache.catalina.core.ApplicationFilterChain.doFilter (applicationfilterchain.java:206) at Org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter (replyheaderfilter.java:96) at Org.apache.catalina.core.ApplicationFilterChain.internalDoFilter (applicationfilterchain.java:235) at Org.apache.catalina.core.ApplicationFilterChain.doFilter (applicationfilterchain.java:206) at Org.apache.catalina.core.StandardWrapperValve.invoke (standardwrappervalve.java:235) at Org.apache.catalina.core.StandardContextValve.invoke (standardcontextvalve.java:191) at Org.jboss.web.tomcat.security.SecurityAssociationValve.invoke (securityassociationvalve.java:190) at Org.jboss.web.tomcat.security.JaccContextValve.invoke (jacccontextvalve.java:92) at Org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process (Securitycontextestablishmentvalve.java : 126) at Org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke (securityCONTEXTESTABLISHMENTVALVE.JAVA:70) at Org.apache.catalina.core.StandardHostValve.invoke (Standardhostvalve.java : 127) at Org.apache.catalina.valves.ErrorReportValve.invoke (errorreportvalve.java:102) at Org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke (cachedconnectionvalve.java:158) at Org.apache.catalina.core.StandardEngineValve.invoke (standardenginevalve.java:109) at Org.apache.catalina.connector.CoyoteAdapter.service (coyoteadapter.java:330) at Org.apache.coyote.http11.Http11Processor.process (http11processor.java:829) at Org.apache.coyote.http11.http11protocol$http11connectionhandler.process (http11protocol.java:598) at Org.apache.tomcat.util.net.jioendpoint$worker.run (jioendpoint.java:447) at Java.lang.Thread.run (Unknown Source)


How to resolve:

Download Jboss-5.1.0.ga-jdk6. A few jar packages that start with JBoss under jboss_home\lib\endorsed are copied to the java_home\lib\endorsed and jre_home\lib\endorsed folders, respectively. There may not be a endorsed folder in the two Lib folders (I don't have one anyway). Then create a new one yourself.

Jar packages to replicate:

Jbossws-native-jaxrpc.jar
Jbossws-native-jaxws.jar
Jbossws-native-jaxws-ext.jar
Jbossws-native-saaj.jar


Note: Starting JBoss from eclipse requires that these packages be placed under the JRE. Starting JBoss from outside requires placing the above jar package under the JDK.


Started only to notice the client's error, so based on the wrong information on the Internet to search for solutions, but found the information is strange, say anything. Later Marjorie a word to remind me. When he asked me what was wrong with the JBoss report, I remembered what was going on with JBoss.

Later, he sent me a blog that was similar to the wrong one, and I did it the way I did, just to find a little bit of a problem (from the outside to start JBoss or an error). Later to participate in a Netizen's blog to overcome this problem. This article is a very specific explanation of the cause of this error, interested friends can see.




Rookie tuning Error (iii)--jboss and JDK version number incompatibility cause WebService call error

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.