You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Vadim Gritsenko <va...@reverycodes.com> on 2004/03/02 16:01:17 UTC
Java chokes on logkit-1.2.2
Java:
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b28)
Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)
Starting tomcat fails with:
javaw.exe -Xms64m -Xmx64m -Dcatalina.home=C:\Java\jakarta-tomcat-4.1.24
-classpath C:\Java\jakarta-tomcat-4.1.24\bin\bootstrap.jar -Xdebug
-Xnoagent -Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,address=ANIMAL:2351,suspend=y,server=n
org.apache.catalina.startup.Bootstrap start
02.03.2004 9:44:56 org.apache.coyote.http11.Http11Protocol init
INFO: Initializing Coyote HTTP/1.1 on port 8080
Starting service Tomcat-Standalone
Apache Tomcat/4.1.24
Catalina.start: LifecycleException: start: :
java.lang.IllegalArgumentException:
avalon-framework,log4j,commons-logging,servletapi,javamail,jms,junit-Extension-Name
LifecycleException: start: : java.lang.IllegalArgumentException:
avalon-framework,log4j,commons-logging,servletapi,javamail,jms,junit-Extension-Name
at org.apache.catalina.loader.WebappLoader.start(WebappLoader.java:678)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:3530)
...
----- Root Cause -----
java.lang.IllegalArgumentException:
avalon-framework,log4j,commons-logging,servletapi,javamail,jms,junit-Extension-Name
at java.util.jar.Attributes$Name.<init>(Attributes.java:434)
at java.util.jar.Attributes.getValue(Attributes.java:97)
at org.apache.catalina.loader.Extension.getRequired(Extension.java:415)
at org.apache.catalina.loader.Extension.getRequired(Extension.java:338)
at
org.apache.catalina.loader.WebappClassLoader.addJar(WebappClassLoader.java:706)
at
org.apache.catalina.loader.WebappLoader.setRepositories(WebappLoader.java:1067)
at org.apache.catalina.loader.WebappLoader.start(WebappLoader.java:665)
...
After removing manifest, following exception is thrown:
Logging Error: Could not set up Cocoon Logger, will use screen instead
org.apache.avalon.framework.configuration.ConfigurationException: No log
targets configured for the root logger.
at
org.apache.avalon.excalibur.logger.LogKitLoggerManager.setupLoggers(LogKitLoggerManager.java:531)
at
org.apache.avalon.excalibur.logger.LogKitLoggerManager.configure(LogKitLoggerManager.java:407)
at
org.apache.cocoon.servlet.CocoonServlet.initLogger(CocoonServlet.java:853)
at org.apache.cocoon.servlet.CocoonServlet.init(CocoonServlet.java:338)
at gov.dc.octo.hsmp.servlet.CocoonServlet.init(CocoonServlet.java:57)
...
So, what happened with logkit?
Vadim
Re: Java chokes on logkit-1.2.2
Posted by JD Daniels <jd...@datatrio.com>.
JD Daniels wrote:
> Vadim Gritsenko wrote:
>
>> JD Daniels wrote:
>>
>>> Vadim Gritsenko wrote:
>>>
>>>> Carsten Ziegeler wrote:
>>>>
>>>>> Did you try a clean build?
>>>>
>>>>
>>>>
>>>>
>>>> It's not a cocoon cvs; it's copy of cocoon libs into web-inf/lib.
>>>
>>>
>>>
>> ...
>>
>>> Did you figure how to fix this? I just did a fresh cvs checkout and
>>> clean build and get the same error (jdk 1.4.1_01)
>>
>>
>>
>>
>> I killed manifest from logkit, which is the reason.
>>
>> Vadim
>>
>>
>>
> ok
>
> <dummy>
> manifest?
> I have never actually messed with any of the
> logkit stuff.. the defaults do just what I want :S
> </dummy>
>
>
>
oops.. ok i get it now :)
Re: Java chokes on logkit-1.2.2
Posted by JD Daniels <jd...@datatrio.com>.
Vadim Gritsenko wrote:
> JD Daniels wrote:
>
>> Vadim Gritsenko wrote:
>>
>>> Carsten Ziegeler wrote:
>>>
>>>> Did you try a clean build?
>>>
>>>
>>>
>>> It's not a cocoon cvs; it's copy of cocoon libs into web-inf/lib.
>>
>>
> ...
>
>> Did you figure how to fix this? I just did a fresh cvs checkout and
>> clean build and get the same error (jdk 1.4.1_01)
>
>
>
> I killed manifest from logkit, which is the reason.
>
> Vadim
>
>
>
ok
<dummy>
manifest?
I have never actually messed with any of the
logkit stuff.. the defaults do just what I want :S
</dummy>
Re: Java chokes on logkit-1.2.2
Posted by Vadim Gritsenko <va...@reverycodes.com>.
JD Daniels wrote:
> Vadim Gritsenko wrote:
>
>> Carsten Ziegeler wrote:
>>
>>> Did you try a clean build?
>>
>>
>> It's not a cocoon cvs; it's copy of cocoon libs into web-inf/lib.
>
...
> Did you figure how to fix this? I just did a fresh cvs checkout and
> clean build and get the same error (jdk 1.4.1_01)
I killed manifest from logkit, which is the reason.
Vadim
Re: Java chokes on logkit-1.2.2
Posted by JD Daniels <jd...@datatrio.com>.
Vadim Gritsenko wrote:
> Carsten Ziegeler wrote:
>
>> Did you try a clean build?
>>
>>
>
> It's not a cocoon cvs; it's copy of cocoon libs into web-inf/lib.
>
>
>> I have the same jdk and for me it works perfectly :)
>> The second exception you get is due to a change in excalibur-logger.
>> The logkit.xconf needs an entry for the root category (category
>> without a name). I have fixed this some days ago in the CVS.
>>
>>
>
> Ah! Did not expect migration issues from 2.1.4 to 2.1.5-dev. Ok, thanks.
>
> Vadim
>
>
>
Did you figure how to fix this? I just did a fresh cvs checkout and
clean build and get the same error (jdk 1.4.1_01)
JD
Re: Java chokes on logkit-1.2.2
Posted by Vadim Gritsenko <va...@reverycodes.com>.
Carsten Ziegeler wrote:
>Did you try a clean build?
>
>
It's not a cocoon cvs; it's copy of cocoon libs into web-inf/lib.
>I have the same jdk and for me it works perfectly :)
>The second exception you get is due to a change in excalibur-logger.
>The logkit.xconf needs an entry for the root category (category
>without a name). I have fixed this some days ago in the CVS.
>
>
Ah! Did not expect migration issues from 2.1.4 to 2.1.5-dev. Ok, thanks.
Vadim
RE: Java chokes on logkit-1.2.2
Posted by Carsten Ziegeler <cz...@s-und-n.de>.
Did you try a clean build?
I have the same jdk and for me it works perfectly :)
The second exception you get is due to a change in excalibur-logger.
The logkit.xconf needs an entry for the root category (category
without a name). I have fixed this some days ago in the CVS.
Carsten
> -----Original Message-----
> From: Vadim Gritsenko [mailto:vadim@reverycodes.com]
> Sent: Tuesday, March 02, 2004 4:01 PM
> To: Cocoon Developers
> Subject: Java chokes on logkit-1.2.2
>
> Java:
> java version "1.4.2"
> Java(TM) 2 Runtime Environment, Standard Edition (build
> 1.4.2-b28) Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode)
>
> Starting tomcat fails with:
> javaw.exe -Xms64m -Xmx64m
> -Dcatalina.home=C:\Java\jakarta-tomcat-4.1.24
> -classpath C:\Java\jakarta-tomcat-4.1.24\bin\bootstrap.jar
> -Xdebug -Xnoagent -Djava.compiler=NONE
> -Xrunjdwp:transport=dt_socket,address=ANIMAL:2351,suspend=y,server=n
> org.apache.catalina.startup.Bootstrap start
> 02.03.2004 9:44:56 org.apache.coyote.http11.Http11Protocol init
> INFO: Initializing Coyote HTTP/1.1 on port 8080 Starting
> service Tomcat-Standalone Apache Tomcat/4.1.24
> Catalina.start: LifecycleException: start: :
> java.lang.IllegalArgumentException:
> avalon-framework,log4j,commons-logging,servletapi,javamail,jms
> ,junit-Extension-Name
> LifecycleException: start: : java.lang.IllegalArgumentException:
> avalon-framework,log4j,commons-logging,servletapi,javamail,jms
> ,junit-Extension-Name
> at
> org.apache.catalina.loader.WebappLoader.start(WebappLoader.java:678)
> at
> org.apache.catalina.core.StandardContext.start(StandardContext
> .java:3530)
> ...
> ----- Root Cause -----
> java.lang.IllegalArgumentException:
> avalon-framework,log4j,commons-logging,servletapi,javamail,jms
> ,junit-Extension-Name
> at java.util.jar.Attributes$Name.<init>(Attributes.java:434)
> at java.util.jar.Attributes.getValue(Attributes.java:97)
> at
> org.apache.catalina.loader.Extension.getRequired(Extension.java:415)
> at
> org.apache.catalina.loader.Extension.getRequired(Extension.java:338)
> at
> org.apache.catalina.loader.WebappClassLoader.addJar(WebappClas
> sLoader.java:706)
> at
> org.apache.catalina.loader.WebappLoader.setRepositories(Webapp
> Loader.java:1067)
> at
> org.apache.catalina.loader.WebappLoader.start(WebappLoader.java:665)
> ...
>
>
> After removing manifest, following exception is thrown:
> Logging Error: Could not set up Cocoon Logger, will use screen instead
> org.apache.avalon.framework.configuration.ConfigurationExcepti
> on: No log targets configured for the root logger.
> at
> org.apache.avalon.excalibur.logger.LogKitLoggerManager.setupLo
> ggers(LogKitLoggerManager.java:531)
> at
> org.apache.avalon.excalibur.logger.LogKitLoggerManager.configu
> re(LogKitLoggerManager.java:407)
> at
> org.apache.cocoon.servlet.CocoonServlet.initLogger(CocoonServl
> et.java:853)
> at
> org.apache.cocoon.servlet.CocoonServlet.init(CocoonServlet.java:338)
> at
> gov.dc.octo.hsmp.servlet.CocoonServlet.init(CocoonServlet.java:57)
> ...
>
>
> So, what happened with logkit?
>
> Vadim
>