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 Michael Woinoski <mi...@pineneedleconsulting.com> on 2003/06/26 18:55:01 UTC
Problem installing Axis 1.1 on Tomcat 5
I'm having a problem migrating Axis from Tomcat 4 to Tomcat 5 (the version
bundled with JWSDP 1.2). I tried the same Axis installation process that worked
with Tomcat 4 (copy /axis/webapps/axis to Tomcat's webapps and copy dom.jar,
sax.jar and xercesImpl.jar to axis WEB-INF/lib) but the axis app is listed as
"stopped" in the Tomcat app list. I can't find any error messages in the log
files, and if I add a <Logger> to the Tomcat webapps/axis.xml, the axis log file
is created and contains happy startup messages. I then tried deploying axis as a
war file in Tomcat's webapps but get the same result.
The only clue is that when I try to display the properties of the /axis webapp
using Tomcat's gui admin tool, it displays this error:
Error retrieving attribute debug
What debug attribute is causing the problem? This error occurs even though the
<Context> in axis.xml has a debug attribute.
Any help would be much appreciated,
Thanks,
Mike
--
Mike Woinoski Pine Needle Consulting
mailto:michaelw@pineneedleconsulting.com
Re: Problem installing Axis 1.1 on Tomcat 5
Posted by Michael Woinoski <mi...@pineneedleconsulting.com>.
Steve (and Matias),
You just won the white-hat award! Thank you! The problem was the jwsdp libs, not
Tomcat 5, because Axis 1.1 ran fine on an unbundled Tomcat (although Tomcat did
give an "Error retrieving attribute debug" when I used the Tomcat admin tool to
tinker with the /axis context settings.)
The real culprit was log4j-1.2.8.jar, which I moved to JWSDP_HOME/commons/lib as
Matias suggested. My JWSDP_HOME/webapps/axis/WEB-INF/lib currently contains only
axis.jar, commons-discovery.jar, and wsdl4j.jar (Axis loaded the saaj and
jax-rpc apis from the jwsdp libs). happyaxis.jsp reports all core and optional
components are found. I've deployed a few services with JWS and AdminClient, and
so far everything looks fine.
Thanks again!
Cheers,
Mike
Steve Viens wrote:
>
> Mike, someone on the jUDDI-users list was having trouble deploying jUDDI
> to JSWDP 1.2 and I believe they've made some progress. jUDDI
> (http://www.juddi.org) is an open-source UDDI registry (web service)
> that's deployed bundled with Axis 1.1rc2.
>
> I've copy-pasted some of the message below. The whole thread is here:
>
> http://sourceforge.net/mailarchive/forum.php?forum_id=7138
>
> Subject/Title of the thread is "jUDDI & JWSDP 1.2"
>
> Steve
>
> > From: juddi-users-admin@lists.sourceforge.net On Behalf Of Matias
> Cuenca
> > Sent: Thursday, June 26, 2003 8:40 PM
> > To: juddi-users@lists.sourceforge.net
> > Subject: RE: [juddi-Users] jUUDI & JWSDP 1.2 (progress!!)
> >
> > Thanks Anou for your observation. Apparently there is
> > some conflict with the jar files built into juddi and
> > the ones on JWSDP. I removed commons-logging.jar from
> > webapps/juddi/WEB-INF/lib because it was already on
> > common/lib/ and I moved
> > webapps/juddi/WEB-INF/lib/log4j-1.2.4.jar to
> > common/lib/. Now it seems to be working (but I haven't
> > tested much yet).
> >
> > Now that we know what the problem is, can you think
> > of a more "portable/elegant" way of fixing it??? As
> > I said at the beginning I'm new to tomcat and maybe
> > there is some option that can be set on the config
> > file (like search_app_jars_first) to fix it
> >
> > Thanks, Matias
> >
> >> From: juddi-users-admin@lists.sourceforge.net On Behalf Of Anou
> Manavalan
> >> Sent: Thursday, June 26, 2003 6:22 PM
> >> To: juddi-users@lists.sourceforge.net
> >> Subject: RE: [juddi-Users] jUUDI & JWSDP 1.2
> >>
> >> We used to have Axis woes, with not finding log4j and
> >> having a null pointer exception, but this doesn't seem
> >> like that.
> >>
> >> The exception says "No suitable log constructor" --
> >> Could it be that the log4j supplied with the jUDDI
> >> and the one that comes with the JWSDP some how are
> >> not compatible ? May be give that also a shot to
> >> substitute the log4j jars in the jUDDI with new
> >> ones or put jUDDI ones in JWSDP...
>
> >> SEVERE: Exception sending context initialized event to listener
> instance
> >> of class com.sun.faces.config.ConfigListener
> >> org.apache.commons.logging.LogConfigurationException:
> org.apache.commons.logging.LogConfigurationException: No
> suitable Log constructor [Ljava.lang.Class;@bc0eba for
> >> org.apache.commons.logging.impl.Log4JLogger at
> >>
> org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImp
> l.java:532) at
> >>
> org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImp
> l.java:272) at
> org.apache.commons.logging.LogFactory.getLog(LogFactory.java:414) at
> >> org.apache.commons.digester.Digester.<init>(Digester.java:346) at
> >>
> com.sun.faces.config.ConfigParser.createDigester(ConfigParser.java:182)
> at
> >> com.sun.faces.config.ConfigParser.<init>(ConfigParser.java:78) at
> >>
> com.sun.faces.config.ConfigListener.contextInitialized(ConfigListener.ja
> va:114) at
> >>
> >> regards,
> >> -Anou
>
> -----Original Message-----
> From: Michael Woinoski [mailto:michaelw@pineneedleconsulting.com]
> Sent: Thursday, June 26, 2003 12:55 PM
> To: Axis User mailing list
> Subject: Problem installing Axis 1.1 on Tomcat 5
>
> I'm having a problem migrating Axis from Tomcat 4 to Tomcat 5 (the
> version bundled with JWSDP 1.2). I tried the same Axis installation
> process that worked with Tomcat 4 (copy /axis/webapps/axis to Tomcat's
> webapps and copy dom.jar, sax.jar and xercesImpl.jar to axis
> WEB-INF/lib) but the axis app is listed as "stopped" in the Tomcat app
> list. I can't find any error messages in the log files, and if I add a
> <Logger> to the Tomcat webapps/axis.xml, the axis log file is created
> and contains happy startup messages. I then tried deploying axis as a
> war file in Tomcat's webapps but get the same result.
>
> The only clue is that when I try to display the properties of the /axis
> webapp using Tomcat's gui admin tool, it displays this error:
>
> Error retrieving attribute debug
>
> What debug attribute is causing the problem? This error occurs even
> though the <Context> in axis.xml has a debug attribute.
>
> Any help would be much appreciated,
> Thanks,
> Mike
>
> --
>
> Mike Woinoski Pine Needle Consulting
> mailto:michaelw@pineneedleconsulting.com
--
Mike Woinoski Pine Needle Consulting
mailto:michaelw@pineneedleconsulting.com
RE: Problem installing Axis 1.1 on Tomcat 5
Posted by Steve Viens <sv...@attbi.com>.
Mike, someone on the jUDDI-users list was having trouble deploying jUDDI
to JSWDP 1.2 and I believe they've made some progress. jUDDI
(http://www.juddi.org) is an open-source UDDI registry (web service)
that's deployed bundled with Axis 1.1rc2.
I've copy-pasted some of the message below. The whole thread is here:
http://sourceforge.net/mailarchive/forum.php?forum_id=7138
Subject/Title of the thread is "jUDDI & JWSDP 1.2"
Steve
> From: juddi-users-admin@lists.sourceforge.net On Behalf Of Matias
Cuenca
> Sent: Thursday, June 26, 2003 8:40 PM
> To: juddi-users@lists.sourceforge.net
> Subject: RE: [juddi-Users] jUUDI & JWSDP 1.2 (progress!!)
>
> Thanks Anou for your observation. Apparently there is
> some conflict with the jar files built into juddi and
> the ones on JWSDP. I removed commons-logging.jar from
> webapps/juddi/WEB-INF/lib because it was already on
> common/lib/ and I moved
> webapps/juddi/WEB-INF/lib/log4j-1.2.4.jar to
> common/lib/. Now it seems to be working (but I haven't
> tested much yet).
>
> Now that we know what the problem is, can you think
> of a more "portable/elegant" way of fixing it??? As
> I said at the beginning I'm new to tomcat and maybe
> there is some option that can be set on the config
> file (like search_app_jars_first) to fix it
>
> Thanks, Matias
>
>> From: juddi-users-admin@lists.sourceforge.net On Behalf Of Anou
Manavalan
>> Sent: Thursday, June 26, 2003 6:22 PM
>> To: juddi-users@lists.sourceforge.net
>> Subject: RE: [juddi-Users] jUUDI & JWSDP 1.2
>>
>> We used to have Axis woes, with not finding log4j and
>> having a null pointer exception, but this doesn't seem
>> like that.
>>
>> The exception says "No suitable log constructor" --
>> Could it be that the log4j supplied with the jUDDI
>> and the one that comes with the JWSDP some how are
>> not compatible ? May be give that also a shot to
>> substitute the log4j jars in the jUDDI with new
>> ones or put jUDDI ones in JWSDP...
>> SEVERE: Exception sending context initialized event to listener
instance
>> of class com.sun.faces.config.ConfigListener
>> org.apache.commons.logging.LogConfigurationException:
org.apache.commons.logging.LogConfigurationException: No
suitable Log constructor [Ljava.lang.Class;@bc0eba for
>> org.apache.commons.logging.impl.Log4JLogger at
>>
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImp
l.java:532) at
>>
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImp
l.java:272) at
org.apache.commons.logging.LogFactory.getLog(LogFactory.java:414) at
>> org.apache.commons.digester.Digester.<init>(Digester.java:346) at
>>
com.sun.faces.config.ConfigParser.createDigester(ConfigParser.java:182)
at
>> com.sun.faces.config.ConfigParser.<init>(ConfigParser.java:78) at
>>
com.sun.faces.config.ConfigListener.contextInitialized(ConfigListener.ja
va:114) at
>>
>> regards,
>> -Anou
-----Original Message-----
From: Michael Woinoski [mailto:michaelw@pineneedleconsulting.com]
Sent: Thursday, June 26, 2003 12:55 PM
To: Axis User mailing list
Subject: Problem installing Axis 1.1 on Tomcat 5
I'm having a problem migrating Axis from Tomcat 4 to Tomcat 5 (the
version bundled with JWSDP 1.2). I tried the same Axis installation
process that worked with Tomcat 4 (copy /axis/webapps/axis to Tomcat's
webapps and copy dom.jar, sax.jar and xercesImpl.jar to axis
WEB-INF/lib) but the axis app is listed as "stopped" in the Tomcat app
list. I can't find any error messages in the log files, and if I add a
<Logger> to the Tomcat webapps/axis.xml, the axis log file is created
and contains happy startup messages. I then tried deploying axis as a
war file in Tomcat's webapps but get the same result.
The only clue is that when I try to display the properties of the /axis
webapp using Tomcat's gui admin tool, it displays this error:
Error retrieving attribute debug
What debug attribute is causing the problem? This error occurs even
though the <Context> in axis.xml has a debug attribute.
Any help would be much appreciated,
Thanks,
Mike
--
Mike Woinoski Pine Needle Consulting
mailto:michaelw@pineneedleconsulting.com