You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@juddi.apache.org by Matias Cuenca <gr...@matiascuenca.com.ar> on 2003/06/26 20:24:11 UTC
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
At 16:21 6/26/2003 -0600, you wrote:
>
>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(LogFactoryImpl.java:532)
>at
>org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.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.java:114)
>at
>
>regards,
>-Anou
>-----Original Message-----
>From: juddi-users-admin@lists.sourceforge.net
>[mailto:juddi-users-admin@lists.sourceforge.net]On Behalf Of Viens, Steve
>Sent: Thursday, June 26, 2003 4:01 PM
>To: 'juddi-users@lists.sourceforge.net'
>Subject: RE: [juddi-Users] jUUDI & JWSDP 1.2
>
>I don't sorry.
>
>I did see a post on the Axis users list today from someone that's having
>trouble deploying Axis to JWSDP (i.e. Tomcat 5) so this is more likely an
>Axis issue than a jUDDI issue. So, you might want to try installing Axis
>under JWSDP successfully first.
>
>Steve
>-----Original Message-----
>From: Matias Cuenca [mailto:grid@matiascuenca.com.ar]
>Sent: Thursday, June 26, 2003 5:49 PM
>To: juddi-users@lists.sourceforge.net
>Subject: RE: [juddi-Users] jUUDI & JWSDP 1.2
>
> I was going to email you about that. I just got juddi to run on a
> friend's tomcat v4 and he said that mine is v5 (your url tells me this
> Java TM Web Services Developer Pack 1.2)
>
> Any clues on how the version might affect it??
>
> Thanks
> Matias
>
>PS:Sorry for the earlier duplicate post
>
>At 16:51 6/26/2003 -0400, you wrote:
>>
>>Matias, can you tell what version of Tomcat is running?
>>
>> <http://localhost:8080/index.html>http://localhost:8080/index.html
>>
>>I'm wondering if JWSDP ships with Tomcat 5.x (which theoretically should
>>work but I'm not certain anyone has tried it yet).
>>
>>Steve
>>-----Original Message-----
>>From: Matias Cuenca [mailto:grid@matiascuenca.com.ar]
>>Sent: Thursday, June 26, 2003 4:30 PM
>>To: juddi-users@lists.sourceforge.net
>>Subject: Re: [juddi-Users] jUUDI & JWSDP 1.2
>>
>> First, thanks to Andy & Steve for their replies and sorry that I
>> took so long to write back :)
>> Steve: I have now tried the latest CVS source code and I'm still
>> getting the same error.
>> Andy: Tomcat is running fine, I have been able to run the
>> examples that come with the tutorial. My web.xml file is the one inside
>> the war file with the corrected paths. This is my log4j.properties
>>log4j.debug
>>log4j.appender.juddilog=org.apache.log4j.RollingFileAppender
>>log4j.appender.juddilog.File=/home/mcuenca/WebServices/juddi/juddi.log
>>log4j.appender.juddilog.MaxFileSize=10MB
>>log4j.appender.juddilog.MaxBackupIndex=3
>>log4j.appender.juddilog.layout=org.apache.log4j.TTCCLayout
>>log4j.appender.juddilog.layout.ContextPrinting=true
>>log4j.appender.juddilog.layout.DateFormat=ISO8601
>>log4j.additivity.org.juddi=false
>>log4j.rootLogger=DEBUG,juddilog
>>log4j.logger.org.juddi=DEBUG,juddilog
>> Can it be a classpath problem?? since it says
>>
>>Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger at
>>java.lang.Class.getDeclaredConstructors0(Native Method) at
>>java.lang.Class.privateGetDeclaredConstructors(Class.java:1590) at
>>java.lang.Class.getConstructor0(Class.java:1762) at
>>java.lang.Class.getConstructor(Class.java:1002) at
>>org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:429)
>>
>> Thanks for your help
>> Matias
>>
>>At 10:02 6/20/2003 -0700, you wrote:
>>>hi,
>>>
>>>have you run tomcat without running juddi? i'd try that first. also, can
>>>we see how you've configured your log4j? this appears to be a logging
>>>initialization error. have you modified web.xml?
>>>
>>>cheers,
>>>andy
>>>
>>>grid@matiascuenca.com.ar wrote:
>>>
>>>>Hi, I'm just in the first steps in order to get jUDDI to run. I basically
>>>>have tomcat (as installed by JWSDP) running), I have copied juddi's war
>>>>file into the webapps directory and then configured the appropriate paths
>>>>for juddi.properties & log4j.properties (and its log file). Now the
>>>>problem is that tomcat can't start juddi (below are the errors from the
>>>>log file). Any suggestions ?? Thanks
>>>>Matias
>>>>PS: Note that this is my first time using tomcat so it might be something
>>>>completely unrelated to jUDDI. INFO: Installing web application at
>>>>context path /juddi from URL
>>>>file:/farm-unsupported/java/jwsdp-1.2/webapps/juddi Jun 19, 2003 6:11:46
>>>>PM org.apache.catalina.core.StandardContext listenerStart
>>>>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(LogFactoryImpl.java:532)
>>>>at
>>>>org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.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.java:114)
>>>>at
>>>>org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3670)
>>>>at
>>>>org.apache.catalina.core.StandardContext.start(StandardContext.java:4106)
>>>>at
>>>>org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:843)
>>>>at
>>>>org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:827) at
>>>>org.apache.catalina.core.StandardHost.addChild(StandardHost.java:623) at
>>>>org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.java:315)
>>>>at
>>>>org.apache.catalina.core.StandardHost.install(StandardHost.java:837) at
>>>>org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:630)
>>>>at
>>>>org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:470) at
>>>>org.apache.catalina.startup.HostConfig.start(HostConfig.java:835) at
>>>>org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:429)
>>>>at
>>>>org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:166)
>>>>at
>>>>org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1241) at
>>>>org.apache.catalina.core.StandardHost.start(StandardHost.java:804) at
>>>>org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1233) at
>>>>org.apache.catalina.core.StandardEngine.start(StandardEngine.java:532) at
>>>>org.apache.catalina.core.StandardService.start(StandardService.java:519)
>>>>at
>>>>org.apache.catalina.core.StandardServer.start(StandardServer.java:2314) at
>>>>org.apache.catalina.startup.Catalina.start(Catalina.java:577) at
>>>>sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
>>>>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>at
>>>>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>at
>>>>java.lang.reflect.Method.invoke(Method.java:324) at
>>>>org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:328) at
>>>>org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425) at
>>>>sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
>>>>sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>>>>at
>>>>sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>>>>at
>>>>java.lang.reflect.Method.invoke(Method.java:324) at
>>>>org.apache.commons.launcher.ChildMain.run(ChildMain.java:269) Caused
>>>>by: 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.getLogConstructor(LogFactoryImpl.java:432)
>>>>at
>>>>org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:525)
>>>>... 36
>>>>more Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger at
>>>>java.lang.Class.getDeclaredConstructors0(Native Method) at
>>>>java.lang.Class.privateGetDeclaredConstructors(Class.java:1590) at
>>>>java.lang.Class.getConstructor0(Class.java:1762) at
>>>>java.lang.Class.getConstructor(Class.java:1002) at
>>>>org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryImpl.java:429)
>>>>... 37
>>>>more Jun 19, 2003 6:11:46 PM org.apache.catalina.core.StandardContext
>>>>start SEVERE: Error listenerStart Jun 19, 2003 6:11:46 PM
>>>>org.apache.catalina.core.StandardContext start SEVERE: Context startup
>>>>failed due to previous errors Jun 19, 2003 6:11:47 PM
>>>>org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote
>>>>HTTP/1.1 on port 8080 Jun 19, 2003 6:11:47 PM
>>>>org.apache.catalina.startup.Catalina start
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>-------------------------------------------------------
>>>>This SF.Net email is sponsored by: INetU
>>>>Attention Web Developers & Consultants: Become An INetU Hosting Partner.
>>>>Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
>>>>INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
>>>>_______________________________________________
>>>>juddi-users mailing list
>>>>juddi-users@lists.sourceforge.net
>>>>https://lists.sourceforge.net/lists/listinfo/juddi-users
>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>-------------------------------------------------------
>>>This SF.Net email is sponsored by: INetU
>>>Attention Web Developers & Consultants: Become An INetU Hosting Partner.
>>>Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
>>>INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
>>>_______________________________________________
>>>juddi-users mailing list
>>>juddi-users@lists.sourceforge.net
>>>https://lists.sourceforge.net/lists/listinfo/juddi-users
[juddi-Users] jUUDI & JWSDP 1.2 (best solution so far)
Posted by Francisco Cuenca <mc...@matiascuenca.com.ar>.
I got around to do more testing under jwsdp, so I wanted to keep
the list updated in case somebody has the same scenario.
I checked out the latest juddi code and observed the new axis.jar
doesn't solve the problem. My cleanest solution so far is to copy
log4j-1.2.8.jar into common/lib and to put a log4j.properties file on
common/classes. With this changes I can run juddi unmodified on jwsdp.
I hope this helps others
Matias
PS: This is the content of my log4j.properties (an spin-off of juddi's file)
# Uncomment to have log4j be verbose while parsing this file
#log4j.debug
# CONSOLE is set to be a ConsoleAppender using a PatternLayout.
log4j.appender.CONSOLE=org.apache.log4j.ConsoleAppender
log4j.appender.CONSOLE.layout=org.apache.log4j.PatternLayout
log4j.appender.CONSOLE.layout.ConversionPattern=- %m%n
log4j.appender.CONSOLE.Threshold=INFO
# LOGFILE is set to be a RollingFileAppender appender using a TTCCLayout.
log4j.appender.LOGFILE=org.apache.log4j.RollingFileAppender
log4j.appender.LOGFILE.layout=org.apache.log4j.TTCCLayout
log4j.appender.LOGFILE.layout.ContextPrinting=true
log4j.appender.LOGFILE.layout.DateFormat=ISO8601
log4j.appender.LOGFILE.MaxFileSize=10MB
log4j.appender.LOGFILE.MaxBackupIndex=3
log4j.appender.LOGFILE.File=../logs/launcher.server.log
# Set root category priority to DEBUG and its appender to LOGFILE.
#log4j.rootCategory=WARN, LOGFILE
log4j.rootCategory=INFO, LOGFILE
#log4j.rootCategory=DEBUG, LOGFILE
# Set the Axis enterprise logger category to FATAL and its only appender to
CONSOLE.
log4j.logger.org.apache.axis.enterprise=FATAL, CONSOLE
RE: [juddi-Users] jUUDI & JWSDP 1.2 (progress!!)
Posted by Steve Viens <sv...@attbi.com>.
Hmmm. The Axis libraries that are included with jUDDI 0.7.0 and 0.7.1
were taken from the Axis 1.1rc2 release. I would be interested to find
out if upgrading the Axis libraries to Axis 1.1 (just released) would
correct this problem. I have noticed that the Log4j.jar in Axis 1.1rc is
version 1.2.4 and the the log4j.jar in Axis 1.1 is version 1.2.8.
Steve
-----Original Message-----
From: juddi-users-admin@lists.sourceforge.net
[mailto: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
At 16:21 6/26/2003 -0600, you wrote:
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: juddi-users-admin@lists.sourceforge.net
[mailto:juddi-users-admin@lists.sourceforge.net]On Behalf Of Viens,
Steve
Sent: Thursday, June 26, 2003 4:01 PM
To: 'juddi-users@lists.sourceforge.net'
Subject: RE: [juddi-Users] jUUDI & JWSDP 1.2
I don't sorry.
I did see a post on the Axis users list today from someone that's having
trouble deploying Axis to JWSDP (i.e. Tomcat 5) so this is more likely
an Axis issue than a jUDDI issue. So, you might want to try installing
Axis under JWSDP successfully first.
Steve
-----Original Message-----
From: Matias Cuenca [mailto:grid@matiascuenca.com.ar]
Sent: Thursday, June 26, 2003 5:49 PM
To: juddi-users@lists.sourceforge.net
Subject: RE: [juddi-Users] jUUDI & JWSDP 1.2
I was going to email you about that. I just got juddi to run on
a friend's tomcat v4 and he said that mine is v5 (your url tells me this
Java TM Web Services Developer Pack 1.2)
Any clues on how the version might affect it??
Thanks
Matias
PS:Sorry for the earlier duplicate post
At 16:51 6/26/2003 -0400, you wrote:
Matias, can you tell what version of Tomcat is running?
http://localhost:8080/index.html
I'm wondering if JWSDP ships with Tomcat 5.x (which theoretically should
work but I'm not certain anyone has tried it yet).
Steve
-----Original Message-----
From: Matias Cuenca [mailto:grid@matiascuenca.com.ar]
Sent: Thursday, June 26, 2003 4:30 PM
To: juddi-users@lists.sourceforge.net
Subject: Re: [juddi-Users] jUUDI & JWSDP 1.2
First, thanks to Andy & Steve for their replies and sorry that I
took so long to write back :)
Steve: I have now tried the latest CVS source code and I'm still
getting the same error.
Andy: Tomcat is running fine, I have been able to run the
examples that come with the tutorial. My web.xml file is the one inside
the war file with the corrected paths. This is my log4j.properties
log4j.debug
log4j.appender.juddilog=org.apache.log4j.RollingFileAppender
log4j.appender.juddilog.File=/home/mcuenca/WebServices/juddi/juddi.log
log4j.appender.juddilog.MaxFileSize=10MB
log4j.appender.juddilog.MaxBackupIndex=3
log4j.appender.juddilog.layout=org.apache.log4j.TTCCLayout
log4j.appender.juddilog.layout.ContextPrinting=true
log4j.appender.juddilog.layout.DateFormat=ISO8601
log4j.additivity.org.juddi=false
log4j.rootLogger=DEBUG,juddilog
log4j.logger.org.juddi=DEBUG,juddilog
Can it be a classpath problem?? since it says
Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger at
java.lang.Class.getDeclaredConstructors0(Native Method) at
java.lang.Class.privateGetDeclaredConstructors(Class.java:1590) at
java.lang.Class.getConstructor0(Class.java:1762) at
java.lang.Class.getConstructor(Class.java:1002) at
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFact
oryImpl.java:429)
Thanks for your help
Matias
At 10:02 6/20/2003 -0700, you wrote:
hi,
have you run tomcat without running juddi? i'd try that first. also, can
we see how you've configured your log4j? this appears to be a logging
initialization error. have you modified web.xml?
cheers,
andy
grid@matiascuenca.com.ar wrote:
Hi, I'm just in the first steps in order to get jUDDI to run. I
basically
have tomcat (as installed by JWSDP) running), I have copied juddi's war
file into the webapps directory and then configured the appropriate
paths
for juddi.properties & log4j.properties (and its log file). Now the
problem is that tomcat can't start juddi (below are the errors from the
log file). Any suggestions ?? Thanks
Matias
PS: Note that this is my first time using tomcat so it might be
something
completely unrelated to jUDDI. INFO: Installing web application at
context path /juddi from URL
file:/farm-unsupported/java/jwsdp-1.2/webapps/juddi
<file://\farm-unsupported\java\jwsdp-1.2\webapps\juddi> Jun 19, 2003
6:11:46
PM org.apache.catalina.core.StandardContext listenerStart
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
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.j
ava:3670) at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4106
) at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.ja
va:843) at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:827)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:623) at
org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeploy
er.java:315) at
org.apache.catalina.core.StandardHost.install(StandardHost.java:837) at
org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java
:630) at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:470)
at
org.apache.catalina.startup.HostConfig.start(HostConfig.java:835) at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:42
9) at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSu
pport.java:166) at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1241) at
org.apache.catalina.core.StandardHost.start(StandardHost.java:804) at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1233) at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:532)
at
org.apache.catalina.core.StandardService.start(StandardService.java:519)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:2314)
at
org.apache.catalina.startup.Catalina.start(Catalina.java:577) at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25) at
java.lang.reflect.Method.invoke(Method.java:324) at
org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:328) at
org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425) at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav
a:39) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor
Impl.java:25) at
java.lang.reflect.Method.invoke(Method.java:324) at
org.apache.commons.launcher.ChildMain.run(ChildMain.java:269) Caused
by: 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.getLogConstructor(LogFact
oryImpl.java:432) at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImp
l.java:525) ... 36
more Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger
at
java.lang.Class.getDeclaredConstructors0(Native Method) at
java.lang.Class.privateGetDeclaredConstructors(Class.java:1590) at
java.lang.Class.getConstructor0(Class.java:1762) at
java.lang.Class.getConstructor(Class.java:1002) at
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFact
oryImpl.java:429) ... 37
more Jun 19, 2003 6:11:46 PM org.apache.catalina.core.StandardContext
start SEVERE: Error listenerStart Jun 19, 2003 6:11:46 PM
org.apache.catalina.core.StandardContext start SEVERE: Context startup
failed due to previous errors Jun 19, 2003 6:11:47 PM
org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote
HTTP/1.1 on port 8080 Jun 19, 2003 6:11:47 PM
org.apache.catalina.startup.Catalina start
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
juddi-users mailing list
juddi-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/juddi-users
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
juddi-users mailing list
juddi-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/juddi-users
RE: [juddi-Users] jUUDI & JWSDP 1.2 (progress!!)
Posted by Anou Manavalan <an...@trysybase.com>.
JAVA has this problem, there is nothing jUDDI can do about it. Each product
comes with its own version of jar which causes these problems. There is a
version ( opensource ) project (
http://metamorphosis.krysalis.org/version/ ) which hopes to help the users
to find out what are the versions used during runtime.
I have used Sybase EAServer ( Application Server ) not Tomcat, so no idea on
the configs. AppServers have the concept of loading the webapp jars
separately using a different class loader, that also will cause problems,
since the logs are started at the server level.
We will also try to build jUDDI with the latest jars ( once we get gump
working in the next release which has the directory structure changed
accordingly ) to make sure it is compatible, but mixing 2 versions and 2
classloaders will be a problem in JAVA.
regards,
-Anou
-----Original Message-----
From: juddi-users-admin@lists.sourceforge.net
[mailto:juddi-users-admin@lists.sourceforge.net]On Behalf Of Matias Cuenca
Sent: Thursday, June 26, 2003 6: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
At 16:21 6/26/2003 -0600, you wrote:
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(LogFactoryImpl.ja
va:532) at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.ja
va: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.java:1
14) at
regards,
-Anou
-----Original Message-----
From: juddi-users-admin@lists.sourceforge.net
[mailto:juddi-users-admin@lists.sourceforge.net]On Behalf Of Viens, Steve
Sent: Thursday, June 26, 2003 4:01 PM
To: 'juddi-users@lists.sourceforge.net'
Subject: RE: [juddi-Users] jUUDI & JWSDP 1.2
I don't sorry.
I did see a post on the Axis users list today from someone that's
having trouble deploying Axis to JWSDP (i.e. Tomcat 5) so this is more
likely an Axis issue than a jUDDI issue. So, you might want to try
installing Axis under JWSDP successfully first.
Steve
-----Original Message-----
From: Matias Cuenca [mailto:grid@matiascuenca.com.ar]
Sent: Thursday, June 26, 2003 5:49 PM
To: juddi-users@lists.sourceforge.net
Subject: RE: [juddi-Users] jUUDI & JWSDP 1.2
I was going to email you about that. I just got juddi to run
on a friend's tomcat v4 and he said that mine is v5 (your url tells me this
Java TM Web Services Developer Pack 1.2)
Any clues on how the version might affect it??
Thanks
Matias
PS:Sorry for the earlier duplicate post
At 16:51 6/26/2003 -0400, you wrote:
Matias, can you tell what version of Tomcat is running?
http://localhost:8080/index.html
I'm wondering if JWSDP ships with Tomcat 5.x (which theoretically
should work but I'm not certain anyone has tried it yet).
Steve
-----Original Message-----
From: Matias Cuenca [mailto:grid@matiascuenca.com.ar]
Sent: Thursday, June 26, 2003 4:30 PM
To: juddi-users@lists.sourceforge.net
Subject: Re: [juddi-Users] jUUDI & JWSDP 1.2
First, thanks to Andy & Steve for their replies and sorry
that I took so long to write back :)
Steve: I have now tried the latest CVS source code and I'm
still getting the same error.
Andy: Tomcat is running fine, I have been able to run the
examples that come with the tutorial. My web.xml file is the one inside the
war file with the corrected paths. This is my log4j.properties
log4j.debug
log4j.appender.juddilog=org.apache.log4j.RollingFileAppender
log4j.appender.juddilog.File=/home/mcuenca/WebServices/juddi/juddi.log
log4j.appender.juddilog.MaxFileSize=10MB
log4j.appender.juddilog.MaxBackupIndex=3
log4j.appender.juddilog.layout=org.apache.log4j.TTCCLayout
log4j.appender.juddilog.layout.ContextPrinting=true
log4j.appender.juddilog.layout.DateFormat=ISO8601
log4j.additivity.org.juddi=false
log4j.rootLogger=DEBUG,juddilog
log4j.logger.org.juddi=DEBUG,juddilog
Can it be a classpath problem?? since it says
Caused by: java.lang.NoClassDefFoundError: org/apache/log4j/Logger
at
java.lang.Class.getDeclaredConstructors0(Native Method) at
java.lang.Class.privateGetDeclaredConstructors(Class.java:1590) at
java.lang.Class.getConstructor0(Class.java:1762) at
java.lang.Class.getConstructor(Class.java:1002) at
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryI
mpl.java:429)
Thanks for your help
Matias
At 10:02 6/20/2003 -0700, you wrote:
hi,
have you run tomcat without running juddi? i'd try that first.
also, can we see how you've configured your log4j? this appears to be a
logging initialization error. have you modified web.xml?
cheers,
andy
grid@matiascuenca.com.ar wrote:
Hi, I'm just in the first steps in order to get jUDDI to run. I
basically
have tomcat (as installed by JWSDP) running), I have copied
juddi's war
file into the webapps directory and then configured the
appropriate paths
for juddi.properties & log4j.properties (and its log file). Now
the
problem is that tomcat can't start juddi (below are the errors
from the
log file). Any suggestions ?? Thanks
Matias
PS: Note that this is my first time using tomcat so it might be
something
completely unrelated to jUDDI. INFO: Installing web application
at context path /juddi from URL
file:/farm-unsupported/java/jwsdp-1.2/webapps/juddi Jun 19, 2003
6:11:46
PM org.apache.catalina.core.StandardContext listenerStart
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(LogFactoryImpl.ja
va:532) at
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.ja
va: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.java:1
14) at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:
3670) at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4106) at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:8
43) at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:827) at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:623) at
org.apache.catalina.core.StandardHostDeployer.install(StandardHostDeployer.j
ava:315) at
org.apache.catalina.core.StandardHost.install(StandardHost.java:837) at
org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:630
) at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:470) at
org.apache.catalina.startup.HostConfig.start(HostConfig.java:835) at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:429)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSuppor
t.java:166) at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1241) at
org.apache.catalina.core.StandardHost.start(StandardHost.java:804) at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1233) at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:532) at
org.apache.catalina.core.StandardService.start(StandardService.java:519) at
org.apache.catalina.core.StandardServer.start(StandardServer.java:2314) at
org.apache.catalina.startup.Catalina.start(Catalina.java:577) at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25) at
java.lang.reflect.Method.invoke(Method.java:324) at
org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:328)
at
org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:425)
at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25) at
java.lang.reflect.Method.invoke(Method.java:324) at
org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
Caused
by: 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.getLogConstructor(LogFactoryI
mpl.java:432) at
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.ja
va:525) ... 36
more Caused by: java.lang.NoClassDefFoundError:
org/apache/log4j/Logger at
java.lang.Class.getDeclaredConstructors0(Native Method) at
java.lang.Class.privateGetDeclaredConstructors(Class.java:1590)
at
java.lang.Class.getConstructor0(Class.java:1762) at
java.lang.Class.getConstructor(Class.java:1002) at
org.apache.commons.logging.impl.LogFactoryImpl.getLogConstructor(LogFactoryI
mpl.java:429) ... 37
more Jun 19, 2003 6:11:46 PM
org.apache.catalina.core.StandardContext
start SEVERE: Error listenerStart Jun 19, 2003 6:11:46 PM
org.apache.catalina.core.StandardContext start SEVERE: Context
startup
failed due to previous errors Jun 19, 2003 6:11:47 PM
org.apache.coyote.http11.Http11Protocol start INFO: Starting
Coyote
HTTP/1.1 on port 8080 Jun 19, 2003 6:11:47 PM
org.apache.catalina.startup.Catalina start
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting
Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly
Commission!
INetU Dedicated Managed Hosting
http://www.inetu.net/partner/index.php
_______________________________________________
juddi-users mailing list
juddi-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/juddi-users
-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting
Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly
Commission!
INetU Dedicated Managed Hosting
http://www.inetu.net/partner/index.php
_______________________________________________
juddi-users mailing list
juddi-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/juddi-users