Re: [HELP!] - RE: Java chokes on logkit-1.2.2
Antonio Gallardo wrote: Hi: I already read 3 or 5 times all the mails: http://marc.theaimsgroup.com/?t=107823977800010r=1w=2 But I don't understand how to solve the problem. :-( Can someone describe a little bit more what is needed to solve the problem? zip -d logkit-1.2.2.jar META-INF/MANIFEST.MF Vadim
Re: [HELP!] - RE: Java chokes on logkit-1.2.2
Vadim Gritsenko dijo: Antonio Gallardo wrote: Hi: I already read 3 or 5 times all the mails: http://marc.theaimsgroup.com/?t=107823977800010r=1w=2 But I don't understand how to solve the problem. :-( Can someone describe a little bit more what is needed to solve the problem? zip -d logkit-1.2.2.jar META-INF/MANIFEST.MF Vadim: Many Thanks. I already did it. :-D I think it is a VERY NASTY BUG! We need to fix it soon in the CVS! People on the user list using the nightly build are having the same problem. We will similar mails often if we don't change this jar. What about newbies? Can I update the jar in the CVS? The yesterday mails where no clear or I was to sleepy to understand the magic behind the problem. I lost many hours with this thing! :-( Best Regards, Antonio Gallardo.
RE: [HELP!] - RE: Java chokes on logkit-1.2.2
Sure, update the CVS (and please also the 2.2 version, it's the same jar). Now, interestingly, I don't have any problems with it - perhaps because I'm using this great and stable W2K and XP system? Carsten -Original Message- From: Antonio Gallardo [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 03, 2004 4:01 PM To: [EMAIL PROTECTED] Subject: Re: [HELP!] - RE: Java chokes on logkit-1.2.2 Vadim Gritsenko dijo: Antonio Gallardo wrote: Hi: I already read 3 or 5 times all the mails: http://marc.theaimsgroup.com/?t=107823977800010r=1w=2 But I don't understand how to solve the problem. :-( Can someone describe a little bit more what is needed to solve the problem? zip -d logkit-1.2.2.jar META-INF/MANIFEST.MF Vadim: Many Thanks. I already did it. :-D I think it is a VERY NASTY BUG! We need to fix it soon in the CVS! People on the user list using the nightly build are having the same problem. We will similar mails often if we don't change this jar. What about newbies? Can I update the jar in the CVS? The yesterday mails where no clear or I was to sleepy to understand the magic behind the problem. I lost many hours with this thing! :-( Best Regards, Antonio Gallardo.
Re: [HELP!] - RE: Java chokes on logkit-1.2.2
Antonio Gallardo wrote: Vadim Gritsenko dijo: Antonio Gallardo wrote: Hi: I already read 3 or 5 times all the mails: http://marc.theaimsgroup.com/?t=107823977800010r=1w=2 But I don't understand how to solve the problem. :-( Can someone describe a little bit more what is needed to solve the problem? zip -d logkit-1.2.2.jar META-INF/MANIFEST.MF Vadim: Many Thanks. I already did it. :-D I think it is a VERY NASTY BUG! We need to fix it soon in the CVS! People on the user list using the nightly build are having the same problem. We will similar mails often if we don't change this jar. What about newbies? Can I update the jar in the CVS? Can you bring this issue up on avalon-dev? We should fix it in the source.. Vadim
Re: [HELP!] - RE: Java chokes on logkit-1.2.2
Hah hah hah hah I recently switched to mandrake from XP glad my partners don't read this list or I would never hear the end of it :-P Carsten Ziegeler wrote: Sure, update the CVS (and please also the 2.2 version, it's the same jar). Now, interestingly, I don't have any problems with it - perhaps because I'm using this great and stable W2K and XP system? Carsten -Original Message- From: Antonio Gallardo [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 03, 2004 4:01 PM To: [EMAIL PROTECTED] Subject: Re: [HELP!] - RE: Java chokes on logkit-1.2.2 Vadim Gritsenko dijo: Antonio Gallardo wrote: Hi: I already read 3 or 5 times all the mails: http://marc.theaimsgroup.com/?t=107823977800010r=1w=2 But I don't understand how to solve the problem. :-( Can someone describe a little bit more what is needed to solve the problem? zip -d logkit-1.2.2.jar META-INF/MANIFEST.MF Vadim: Many Thanks. I already did it. :-D I think it is a VERY NASTY BUG! We need to fix it soon in the CVS! People on the user list using the nightly build are having the same problem. We will similar mails often if we don't change this jar. What about newbies? Can I update the jar in the CVS? The yesterday mails where no clear or I was to sleepy to understand the magic behind the problem. I lost many hours with this thing! :-( Best Regards, Antonio Gallardo.
RE: [HELP!] - RE: Java chokes on logkit-1.2.2
Carsten Ziegeler dijo: Sure, update the CVS (and please also the 2.2 version, it's the same jar). Maybe, sight. Now, interestingly, I don't have any problems with it - perhaps because I'm using this great and stable W2K and XP system? lol. :- Seriously, I will now update the logkit jar in both CVS 2.1 and 2.2. Best Regards, Antonio Gallardo
RE: [HELP!] - RE: Java chokes on logkit-1.2.2
Carsten Ziegeler dijo: Now, interestingly, I don't have any problems with it - perhaps because I'm using this great and stable W2K and XP system? joking-back mode How you dare to talk about Linux! In Linux it works fine using: ./cocoon.sh servlet or ./cocoon.sh servlet-debug The problem raises when Cocoon is deployed in a bugy container, ie: Tomcat. ... Oh well, ... it is another Apache bugy guys saga! ;-DD /joking-back mode Best Regards, Antonio Gallardo
Re: [HELP!] - RE: Java chokes on logkit-1.2.2
Antonio Gallardo wrote: Carsten Ziegeler dijo: Now, interestingly, I don't have any problems with it - perhaps because I'm using this great and stable W2K and XP system? joking-back mode How you dare to talk about Linux! In Linux it works fine using: ./cocoon.sh servlet or ./cocoon.sh servlet-debug The problem raises when Cocoon is deployed in a bugy container, ie: Tomcat. telegraph-modeXP, Tomcat, Crash./telegraph-mode Vadim
RE: Java chokes on logkit-1.2.2
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:[EMAIL PROTECTED] 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
Re: Java chokes on logkit-1.2.2
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
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
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
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
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 :)
[HELP!] - RE: Java chokes on logkit-1.2.2
Hi: I already read 3 or 5 times all the mails: http://marc.theaimsgroup.com/?t=107823977800010r=1w=2 But I don't understand how to solve the problem. :-( Can someone describe a little bit more what is needed to solve the problem? Please help! ;-) Best Regards, Antonio Gallardo
