You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Frank Cohen <fc...@pushtotest.com> on 2003/04/15 01:12:54 UTC

Axis 1.1 rc2 on Tomcat 4.0.3?

I didn't see a reply to this email I posted last week. Anyone know?  
-Frank

--

What is the final word on getting Axis 1.1 RC2 to run under Tomcat  
4.0.3?
After installing 1.1 RC2 and trying
http://myhost:92/axis/services/AdminService?wsdl I see in the Tomcat  
servlet
log that the Axis servlet threw:

java.lang.NoClassDefFoundError
         at java.lang.Class.forName0(Native Method)
         at java.lang.Class.forName(Class.java:217)
         at org.apache.axis.utils.ClassUtils$2.run(ClassUtils.java:179)
         at java.security.AccessController.doPrivileged(Native Method)
         at  
org.apache.axis.utils.ClassUtils.loadClass(ClassUtils.java:171)
         at org.apache.axis.utils.ClassUtils.forName(ClassUtils.java:112)
         at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getJavaClass(WSDDDepl 
oya
bleItem.java:389)
         at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.makeNewInstance(WSDDD 
epl
oyableItem.java:331)
         at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDe 
plo
yableItem.java:310)
         at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeplo 
yab
leItem.java:296)
         at
org.apache.axis.deployment.wsdd.WSDDDeployment.getHandler(WSDDDeployment 
.ja
va:455)
         at
org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDe 
plo
yableItem.java:312)
(more)

I followed the Axis installation instructions
(http://docs.pushtotest.com/axisdocs/install.html) and put copies of the
Axis jar files into the Tomcat common/lib. I also put xercesImpl.jar and
xmlParserAPIs.jar into common/lib.

> From a Google search I found:
http://www.sce.carleton.ca/~weima/AxisInstallation.html#_edn1. This
basically says "Don't use Tomcat 4.0.3."

What is the final word on this?

-Frank

---

http://www.sce.carleton.ca/~weima/AxisInstallation.html#_edn1


AXIS installation guide
Motivation   2
ISSUES   2
ClassNotFoundException  2
Cause  2
Solution/work around  3
Reference   4



Motivation
The installation guide provided by Apache does not solve all problems  
with
AXIS installation. The document explains some "hidden issues" of  
servlet and
axis and provides some workarounds to solve the issues.

ISSUES
ClassNotFoundException
Cause[1]
Some versions (4.0.2, 4.0.3) of Tomcat don't load classes whose fully
qualified names began with any of the following:
             java.
             javax.net.
             javax.security.cert.
             javax.naming.
             javax.xml.
             org.xml.sax.
             org.w3c.dom.
and additionally, they don't load jar files that contain any of the
following classes
             com.sun.jndi.ldap.LdapCtxFactory
             com.sun.net.ssl.internal.ssl.Provider
             javax.security.auth.Subject
             javax.servlet.Servlet


             Some other versions (4.0.4-b1, 4.0.4-b2) of Tomcat don't  
load
classes whose fully qualified names start with any of the following:
             java.
             javax.naming.
             javax.naming.directory
             javax.xml.parsers
             org.xml.sax.
             org.xml.sax.ext
org.xml.sax.helpers
             org.w3c.dom.
and additionally, they don't load jar files that contains
             javax.servlet.Servlet

Notice that javax.xml package is not forbidden for version 4.0.4-b1 and
4.0.4-b2 the many of the ClassNotFoundException is avoid.
Solution/work around
             By the time the document is written, the latest stable  
version
of Tomcat is version 4.0.3. The version does NOT work with axis, so use
4.0.4.-b2 instead.





Reference




[1] Nathan D.Bowen nbowen+axis-users@andtonic.com, response to the  
subject:
"Axis trouble with Tomcat 4.0.2 and 4.0.3" on April 9th 2002




--
Frank Cohen, Founder, PushToTest, http://www.PushToTest.com, phone: 408  
374 7426
Come to PushToTest for free open-source test automation solutions that  
test and monitor
Web-enabled applications, especially Web Services for scalability and  
reliability.


Re: Axis 1.1 rc2 on Tomcat 4.0.3?

Posted by Brian Ewins <Br...@btinternet.com>.
I've had axis working on 4.0.3 in the past, but its a pain in the ass. 
I'd recommend you move up to 4.1.*.

What I did involved moving all of the jars associated with axis (axis 
itself, saaj, jaxrpc, wsdl4j etc) into common/lib. Then I removed log4j 
everywhere. IIRC there was also a clash of commons-logging jars that was 
awkward to fix.

This was enough to get Axis running within my app but I was using an 
axis /client/ within my code, not an axis /server/. You look like you're 
  going to be in a world of pain because axis loaded in 'common/lib' 
won't see classes from your webapp classloader, which I guess you're 
trying to work with there.

You don't mention if you ran happyaxis or not? It could be that 
something a whole lot simpler is wrong.

-Baz

Frank Cohen wrote:
> I didn't see a reply to this email I posted last week. Anyone know?  -Frank
> 
> -- 
> 
> What is the final word on getting Axis 1.1 RC2 to run under Tomcat  4.0.3?
> After installing 1.1 RC2 and trying
> http://myhost:92/axis/services/AdminService?wsdl I see in the Tomcat  
> servlet
> log that the Axis servlet threw:
> 
> java.lang.NoClassDefFoundError
>         at java.lang.Class.forName0(Native Method)
>         at java.lang.Class.forName(Class.java:217)
>         at org.apache.axis.utils.ClassUtils$2.run(ClassUtils.java:179)
>         at java.security.AccessController.doPrivileged(Native Method)
>         at  org.apache.axis.utils.ClassUtils.loadClass(ClassUtils.java:171)
>         at org.apache.axis.utils.ClassUtils.forName(ClassUtils.java:112)
>         at
> org.apache.axis.deployment.wsdd.WSDDDeployableItem.getJavaClass(WSDDDepl 
> oya
> bleItem.java:389)
>         at
> org.apache.axis.deployment.wsdd.WSDDDeployableItem.makeNewInstance(WSDDD 
> epl
> oyableItem.java:331)
>         at
> org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDe 
> plo
> yableItem.java:310)
>         at
> org.apache.axis.deployment.wsdd.WSDDDeployableItem.getInstance(WSDDDeplo 
> yab
> leItem.java:296)
>         at
> org.apache.axis.deployment.wsdd.WSDDDeployment.getHandler(WSDDDeployment 
> .ja
> va:455)
>         at
> org.apache.axis.deployment.wsdd.WSDDDeployableItem.getNewInstance(WSDDDe 
> plo
> yableItem.java:312)
> (more)
> 
> I followed the Axis installation instructions
> (http://docs.pushtotest.com/axisdocs/install.html) and put copies of the
> Axis jar files into the Tomcat common/lib. I also put xercesImpl.jar and
> xmlParserAPIs.jar into common/lib.
> 
>> From a Google search I found:
> 
> http://www.sce.carleton.ca/~weima/AxisInstallation.html#_edn1. This
> basically says "Don't use Tomcat 4.0.3."
> 
> What is the final word on this?
> 
> -Frank
> 
> ---
> 
> http://www.sce.carleton.ca/~weima/AxisInstallation.html#_edn1
> 
> 
> AXIS installation guide
> Motivation   2
> ISSUES   2
> ClassNotFoundException  2
> Cause  2
> Solution/work around  3
> Reference   4
> 
> 
> 
> Motivation
> The installation guide provided by Apache does not solve all problems  with
> AXIS installation. The document explains some "hidden issues" of  
> servlet and
> axis and provides some workarounds to solve the issues.
> 
> ISSUES
> ClassNotFoundException
> Cause[1]
> Some versions (4.0.2, 4.0.3) of Tomcat don't load classes whose fully
> qualified names began with any of the following:
>             java.
>             javax.net.
>             javax.security.cert.
>             javax.naming.
>             javax.xml.
>             org.xml.sax.
>             org.w3c.dom.
> and additionally, they don't load jar files that contain any of the
> following classes
>             com.sun.jndi.ldap.LdapCtxFactory
>             com.sun.net.ssl.internal.ssl.Provider
>             javax.security.auth.Subject
>             javax.servlet.Servlet
> 
> 
>             Some other versions (4.0.4-b1, 4.0.4-b2) of Tomcat don't  load
> classes whose fully qualified names start with any of the following:
>             java.
>             javax.naming.
>             javax.naming.directory
>             javax.xml.parsers
>             org.xml.sax.
>             org.xml.sax.ext
> org.xml.sax.helpers
>             org.w3c.dom.
> and additionally, they don't load jar files that contains
>             javax.servlet.Servlet
> 
> Notice that javax.xml package is not forbidden for version 4.0.4-b1 and
> 4.0.4-b2 the many of the ClassNotFoundException is avoid.
> Solution/work around
>             By the time the document is written, the latest stable  version
> of Tomcat is version 4.0.3. The version does NOT work with axis, so use
> 4.0.4.-b2 instead.
> 
> 
> 
> 
> 
> Reference
> 
> 
> 
> 
> [1] Nathan D.Bowen nbowen+axis-users@andtonic.com, response to the  
> subject:
> "Axis trouble with Tomcat 4.0.2 and 4.0.3" on April 9th 2002
> 
> 
> 
> 
> -- 
> Frank Cohen, Founder, PushToTest, http://www.PushToTest.com, phone: 408  
> 374 7426
> Come to PushToTest for free open-source test automation solutions that  
> test and monitor
> Web-enabled applications, especially Web Services for scalability and  
> reliability.
> 
>