Community
Participate
Working Groups
When trying to run the BottomUp Web Service tutorial from : http://www.eclipse.org/webtools/jst/components/ws/tutorials/BottomUpWebService.h tml I get the following error: IWAB0489E Error when deploying Web service to Axis runtime axis-admin failed with {http://schemas.xmlsoap.org/soap/envelope/}Server.userException java.lang.NullPointerException The error shows up in step 12 after clicking the Finish button it churns for a while then gives me the error: I also notice that the ERR LOG window shows the message (does this represent a problem ?): Skipping builder com.ibm.etools.j2ee.LibCopyBuilder for project converter. Either the builder is missing from the install, or it belongs to a project nature that is missing or disabled. An exception stack trace could not be found. I am running with: Tomcat v5.0 (instead of version 4.1 mentioned in the tutorial) eclipse-SDK-3.1M5a-win32.zip emf-sdo-xsd-SDK-I200502171619.zip GEF-SDK-I20050215.zip JEM-runtime-1.0.2.zip wtp-1.0M3.zip I modified the log4j.properties file (changed version shown below) to try and get additional debug information. With these changes it generated an axis.log file which contained the following stack excerpt for the NullPointerException: AxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException faultSubcode: faultString: java.lang.NullPointerException faultActor: faultNode: faultDetail: {http://xml.apache.org/axis/}stackTrace: java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:396) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.setProperty(SAXParserI mpl.java:395) at org.apache.axis.encoding.DeserializationContextImpl.parse(DeserializationCon textImpl.java:246) at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:538) at org.apache.axis.Message.getSOAPEnvelope(Message.java:376) at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:675 ) at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:128) at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java: 71) at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:150) at org.apache.axis.SimpleChain.invoke(SimpleChain.java:120) at org.apache.axis.client.AxisClient.invoke(AxisClient.java:180) at org.apache.axis.client.Call.invokeEngine(Call.java:2564) at org.apache.axis.client.Call.invoke(Call.java:2553) at org.apache.axis.client.Call.invoke(Call.java:1672) at org.apache.axis.client.AdminClient.process(AdminClient.java:355) at org.apache.axis.client.AdminClient.process(AdminClient.java:334) at org.apache.axis.client.AdminClient.process(AdminClient.java:341) at org.apache.axis.client.AdminClient.process(AdminClient.java:292) at org.apache.axis.tools.ant.axis.AdminClientTask.execute(AdminClientTask.java: 308) at org.eclipse.jst.ws.internal.axis.consumption.core.command.AxisDeployCommand. executeAntTask(AxisDeployCommand.java:102) at org.eclipse.jst.ws.internal.axis.consumption.core.command.AxisDeployCommand. execute(AxisDeployCommand.java:72) There was lots more in the log file. I would have provided the whole file if I could figure out how to attach it to the bug report. If you need the rest of the file I can provide it through email.
Created attachment 18980 [details] Modified log4j.properties file to get additional debug data about the problem.
Created attachment 18981 [details] axis.log file produced when this problem occured. This is the log file produced when the problem was recreated after changing the log4j.properties file (see other attachment for these changes). The end of this file conatins the java stack which shows the NullPointerException reported by this bug report. I tried to put the full log file but got an error that it was too big to be attached so I trimmed off most of the front of the file which did not look that interesting anyway (at least to my untrained eye) and gave you just the end of the file which contains the faulting stacks.
I'm getting the same error. From the stack trace it appears that axis is using the internal Xerces impl, I wonder if that has anythin to do with it.
Kathy, would you please have a look? Thanks - CB.
*** Bug 90524 has been marked as a duplicate of this bug. ***
What JDK are you using? From the stack trace, this problem look almost identical to the problem we found when using JDK 1.5 to create bottom-up Web service using Axis 1.1. You can take a look at defect 92603: https://bugs.eclipse.org/bugs/show_bug.cgi?id=92603
When I was trying to use this tutorial I had both JDK1.4 and JDK1.5 downloaded to my system. I think I had originally seen the error with JDK1.5 active but tried to back up to JDK1.4.2_07 to see if I could run with that but got the same error. I have since found that my attempt to back up missed removing a copy of the JDK1.5 java compiler which somehow found its way to C:\WINNT\system32. I have since removed this file. Now when I try the tutorial with JDK1.5 I get the Null Pointer Exception. When I try the tutorial with JDK1.4.2_07 I get the message "IWAB0514E Unable to get URL for project {0}" in step 12 after clicking on the finish button. This message seems to come out almost immediately (I do not see it trying to build anything) so I do not think that I am getting as far as when running with JDK1.5. I am willing to try again but I do not know what to set up so it can find the URL.
Since the original problem is caused by Axis 1.1 not able to support JDK 1.5, I'm marking this defect as a duplicate of 92603 (that's the defect we are tracking to as an enhancement and pointed to by the News and Noteworthy document). We have seen intermitten problem with "Unable to get project URL". It seems like server tooling was not able to give us the project URL in some cases but we were not able to reproduce the problem consistently in order to have this investigated. Are you able to gett this error consistently with the M4 driver? If so, please open a seperate defect with the your configuration information (JDK, Tomcat, project setup etc.) and exact steps on how to re- create the problem. Thanks! *** This bug has been marked as a duplicate of 92603 ***
Changed Version field given new release numbering.
I got this problem (NPE on Axis deployment) with M5 and all possible combinations of tomcat 4.1, 5.0, 5.5 with java 1.5, java 1.4 So the assumption at comment 8 that Java 1.5 is to blame seems not to be correct
(In reply to comment #10) > I got this problem (NPE on Axis deployment) with M5 and all possible > combinations of tomcat 4.1, 5.0, 5.5 with java 1.5, java 1.4 > > So the assumption at comment 8 that Java 1.5 is to blame seems not to be correct I got this bug as well with Eclipse 3.1, WTP1 RC1 and all the newest releases of GEF, EMF and JEM Marc
I was able to run the Creating Bottom-up Web services tutorial using 0628i WTP build on eclipse RC4 with jakarta-tomcat-5.0.28 and j2sdk1.4.2_07. I haven't tested it since then. - Joan.
We had been successful running the bottom-up Web service tutorial using JDK 1.4.2 with Tomcat 4.0, 4.1 and 5.0 using the various WTP drivers. I just tried JDK 1.4.2_06 with Tomcat 5.0.28 on Windows 2000 using Eclipse 3.1 with WTP RC1 and the was able to run the scenario successfully. Like I said earlier, the only time we get problem with deploying to Axis in bottom-up Web service tutorial is with JDK 1.5. If you need to use JDK 1.5, you will need to wait for defect 98340 (support Axis 1.2 instead of Axis 1.1). If you need to use JDK 1.5 because you want to run on Tomcat 5.5 , another optoin is to run with the compatibility JARs for Tomcat 5.5. Then you can stay with JDK 1.4.2. If you still have problem, please re-open the defect (or open another bug if you are cannot reopen because you are not the originator) with exact steps to reproduce the problem including the exact configuration you are using. We will take a look at that to see why it is causing you problem.
As we are trying to close down WTP 1.5, please get the latest WTP 1.5 driver to verify the bug and reopen if the problem had not been fixed. If this defect is not verified/reopened by end of day 06/16, I'll attempt to verify the defect by reproducing the problem as described in the defect. However, since you know your scenario best, it would be more appropriate if you verify the fix.
I guess you can close this problem because in the roughly 12 months since the problem was reported, the BottomUpWebService tutorial has disappeared from the web and my workspaces and projects that had been used to create the problem seem to have disappeared with it. I am not yet a user of WTP 1.5 but will be some day so we will just have to hope it is corrected there. In general I am more than happy to help verify fixes but it is very rare that a year after reporting a problem I will still have the necessary environment to reproduce the problem.
Closing defect ... FYI. The Web services tutorial for WTP 1.0 is at: http://www.eclipse.org/webtools/community/communityresources.html#ws Follow the link in those tutorials to the tutorials for using the Web services wizard with WTP 1.5.
I meet the problem with eclipse 3.4 It makes me can not develop web service on eclipse, so annoying.