You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by de...@xsoftware.biz on 2006/03/28 22:33:27 UTC
tomcat 5.0 vs. 5.5? tomcat 5.5 has been bad!
Anyone have much experience with running on these. On tomcat 5.5, I have
ran into many problems
1. exception fron ServletContextListener.contextInitialized causes the
vague error of "Error listenerStart" with no details. Most people on
lists I have seen don't even know it was caused by Exception out of that
method(Took me a while to figure out too)
2. logging MyFaces logs was not working
3. Facelets example war files don't work in 5.5.16
Now, I have found 5.0 seems to be fine with all these problems. What are
the experiences of other people out there? and why is tomcat 5.5 above
tomcat 5.0 like it is more stable or something on the tomcat page(I guess
I will post that question to their list).
thanks,
dean
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: tomcat 5.0 vs. 5.5? tomcat 5.5 has been bad!
Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
here is the code, the StandardContext.java logs the error,
its just a matter of finding how to get it to spew it out.
Running a tomcat embedded will spit this sucker out, but running it
within the tomcat catalina.sh swallows it.
I will resolve this and let you know what happens to it.
Filip
ServletContextEvent event =
new ServletContextEvent(getServletContext());
for (int i = 0; i < instances.length; i++) {
if (instances[i] == null)
continue;
if (!(instances[i] instanceof ServletContextListener))
continue;
ServletContextListener listener =
(ServletContextListener) instances[i];
try {
fireContainerEvent("beforeContextInitialized", listener);
listener.contextInitialized(event);
fireContainerEvent("afterContextInitialized", listener);
} catch (Throwable t) {
fireContainerEvent("afterContextInitialized", listener);
getLogger().error
(sm.getString("standardContext.listenerStart",
instances[i].getClass().getName()), t);
ok = false;
}
}
Dean Hiller wrote:
> thanks for the link. I need that too. Regardless of logging thought,
> quickly add this to any serlvetlistener
>
> public void contextInitialized(ServletContextEvent evt) {
> throw new RuntimeException("asdfsf");
> }
>
> Run it, and enjoy not being able to know what the heck went wrong with
> your app like I have seen many have done on the posts already. ie.
> Tomcat used to log the stack trace, but in 5.5 does not, and that
> should be high enough warning level that config of logs don't matter.
>
> Making the problem even harder.....
> On a second note, I have fooled around with logging and it works fine
> in my app, and I could configure it and such(with 5.5) and my
> logging.properties file in WEB-INF. I could never get my
> servletlistener to log any statements(making the problem doubly hard).
> thanks,
> dean
>
>
>
> Vamsidhar wrote:
>
>> I am assuming you have been using logger to log stack traces in case of
>> errors in tomcat 5.0. This was deprecated in 5.0 and completely
>> removed in
>> 5.5. So, If you have logger defined for engine, host, or context to
>> record
>> the stack traces in a file in your application this will not work on
>> tomcat
>> 5.5
>>
>> http://tomcat.apache.org/tomcat-5.0-doc/config/logger.html
>> "Please note that Loggers are deprecated in Tomcat 5.0 and removed from
>> Tomcat 5.5. Tomcat 5.5 uses Commons-Logging instead."
>>
>> hope this helps.
>>
>> On 3/28/06, dean@xsoftware.biz <de...@xsoftware.biz> wrote:
>>
>>
>>> On number 1 5.0 logs the entire stack trace, so you can jump to the
>>> line
>>> number. On 5.5, no such stack trace in any file. Also, I searched
>>> a few
>>> lists and many people had questions on what was wron when they saw that
>>> error. I think the cause is the lack of information....it should at
>>> the
>>> very least log the stack trace and does not.
>>>
>>> I just used the latest facelets and it did not work, but worked on 5.0.
>>>
>>> in fact, all the stuff works on 5.0 which leads me to believe 5.5 is
>>> unstable, but I wanted to verify.
>>> dean
>>>
>>>
>>>> On 3/28/06, dean@xsoftware.biz <de...@xsoftware.biz> wrote:
>>>>
>>>>> Anyone have much experience with running on these. On tomcat 5.5, I
>>>>> have
>>>>> ran into many problems
>>>>> 1. exception fron ServletContextListener.contextInitialized causes
>>>>> the
>>>>> vague error of "Error listenerStart" with no details. Most people on
>>>>> lists I have seen don't even know it was caused by Exception out of
>>>>>
>>> that
>>>
>>>>> method(Took me a while to figure out too)
>>>>>
>>>> Yes, it's an extremely myterious log message, as a
>>>> ServletContextListener is a listener for the context.
>>>>
>>>>
>>>>> 2. logging MyFaces logs was not working
>>>>>
>>>> Whatever.
>>>>
>>>>
>>>>> 3. Facelets example war files don't work in 5.5.16
>>>>>
>>>> It uses a bad method for descovering its config, if I remember well,
>>>> which is now fixed.
>>>>
>>>> --
>>>> xxxxxxxxxxxxxxxxxxxxxxxxx
>>>> Rémy Maucherat
>>>> Developer & Consultant
>>>> JBoss Inc
>>>> xxxxxxxxxxxxxxxxxxxxxxxxx
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>>
>>>>
>>>>
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>
>>>
>>>
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: tomcat 5.0 vs. 5.5? tomcat 5.5 has been bad!
Posted by Dean Hiller <de...@xsoftware.biz>.
my problem is solved. I was just trying to poke tomcat team in hopes
that could put something in to help the next newb.
later, I think I am jumping off the list now....just too much email on
this list,
dean
Markus Schönhaber wrote:
>Dean Hiller wrote:
>
>
>> wow! you guys sound pretty harsh when it comes to messages to help
>>users on simple mistakes then. I recently dropped in someone else's
>>example app war file that had the SAME PROBLEM.....latest facelets. I
>>could not even give back information to help them debug the problem. It
>>was standard tomcat 5.5.16. It worked on 5.0 just fine. I now know
>>that I need to unzip their war file, remove log4j(and maybe even hope
>>that they are using commons, because if they are not, I may be utterly
>>screwed). Then I need to redeploy their app. I need to do all this
>>because tomcat is unwilling to give good helpful messages as to what is
>>going on(as seen by all the other posts that have had trouble figuring
>>out their problems behind that error with no reponses either.....I was
>>the lucky one and finally figured out what was wrong). I can only hope
>>others can find my solution post without wasting too much time.
>>
>>
>
>I don't see too much harshness here. And my proposal to provide a patch wasn't
>meant really serious either since I strongly doubt it will be as easy as you
>seem to think.
>Also, Rémy calling such a patch - if there was one - "nonsensical" seems quite
>understandable to me since trying to work around anything a user can do to
>b0rk his webapp would bloat Tomcat's source code beyond all borders.
>OTOH if there are really so many people b0rking their webapps this particular
>way, then maybe this should be added to the FAQ.
>
>Regards
> mks
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: tomcat 5.0 vs. 5.5? tomcat 5.5 has been bad!
Posted by Markus Schönhaber <ma...@schoenhaber.de>.
Dean Hiller wrote:
> wow! you guys sound pretty harsh when it comes to messages to help
> users on simple mistakes then. I recently dropped in someone else's
> example app war file that had the SAME PROBLEM.....latest facelets. I
> could not even give back information to help them debug the problem. It
> was standard tomcat 5.5.16. It worked on 5.0 just fine. I now know
> that I need to unzip their war file, remove log4j(and maybe even hope
> that they are using commons, because if they are not, I may be utterly
> screwed). Then I need to redeploy their app. I need to do all this
> because tomcat is unwilling to give good helpful messages as to what is
> going on(as seen by all the other posts that have had trouble figuring
> out their problems behind that error with no reponses either.....I was
> the lucky one and finally figured out what was wrong). I can only hope
> others can find my solution post without wasting too much time.
I don't see too much harshness here. And my proposal to provide a patch wasn't
meant really serious either since I strongly doubt it will be as easy as you
seem to think.
Also, Rémy calling such a patch - if there was one - "nonsensical" seems quite
understandable to me since trying to work around anything a user can do to
b0rk his webapp would bloat Tomcat's source code beyond all borders.
OTOH if there are really so many people b0rking their webapps this particular
way, then maybe this should be added to the FAQ.
Regards
mks
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: tomcat 5.0 vs. 5.5? tomcat 5.5 has been bad!
Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
Remy Maucherat wrote:
> On 3/30/06, Markus Schönhaber <ma...@schoenhaber.de> wrote:
>
>>> The RuntimeException is to make it more noticeable in the logs. I mean
>>> 953 hits on googling is quite alot of people having trouble. Would be
>>> nice to cut that number down with an easy log statement that tomcat
>>> could add!!!
>>>
>> Well, if it's really that easy you should definitely provide a patch.
>>
>
> I recommend not wasting time, as I would refuse such a nonsensical
> patch. The actual worakround is to learn how to properly use logging,
> which seems to be a useful skill.
>
there is no need for a patch, the exception shows up in the logs under a
standard deployment (ie, unzip the .zip and run an example)
Filip
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: tomcat 5.0 vs. 5.5? tomcat 5.5 has been bad!
Posted by Dean Hiller <de...@xsoftware.biz>.
wow! you guys sound pretty harsh when it comes to messages to help
users on simple mistakes then. I recently dropped in someone else's
example app war file that had the SAME PROBLEM.....latest facelets. I
could not even give back information to help them debug the problem. It
was standard tomcat 5.5.16. It worked on 5.0 just fine. I now know
that I need to unzip their war file, remove log4j(and maybe even hope
that they are using commons, because if they are not, I may be utterly
screwed). Then I need to redeploy their app. I need to do all this
because tomcat is unwilling to give good helpful messages as to what is
going on(as seen by all the other posts that have had trouble figuring
out their problems behind that error with no reponses either.....I was
the lucky one and finally figured out what was wrong). I can only hope
others can find my solution post without wasting too much time.
later,
dean
Remy Maucherat wrote:
>On 3/30/06, Markus Schönhaber <ma...@schoenhaber.de> wrote:
>
>
>>>The RuntimeException is to make it more noticeable in the logs. I mean
>>>953 hits on googling is quite alot of people having trouble. Would be
>>>nice to cut that number down with an easy log statement that tomcat
>>>could add!!!
>>>
>>>
>>Well, if it's really that easy you should definitely provide a patch.
>>
>>
>
>I recommend not wasting time, as I would refuse such a nonsensical
>patch. The actual worakround is to learn how to properly use logging,
>which seems to be a useful skill.
>
>--
>xxxxxxxxxxxxxxxxxxxxxxxxx
>Rémy Maucherat
>Developer & Consultant
>JBoss Inc
>xxxxxxxxxxxxxxxxxxxxxxxxx
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: tomcat 5.0 vs. 5.5? tomcat 5.5 has been bad!
Posted by Remy Maucherat <re...@gmail.com>.
On 3/30/06, Markus Schönhaber <ma...@schoenhaber.de> wrote:
> > The RuntimeException is to make it more noticeable in the logs. I mean
> > 953 hits on googling is quite alot of people having trouble. Would be
> > nice to cut that number down with an easy log statement that tomcat
> > could add!!!
>
> Well, if it's really that easy you should definitely provide a patch.
I recommend not wasting time, as I would refuse such a nonsensical
patch. The actual worakround is to learn how to properly use logging,
which seems to be a useful skill.
--
xxxxxxxxxxxxxxxxxxxxxxxxx
Rémy Maucherat
Developer & Consultant
JBoss Inc
xxxxxxxxxxxxxxxxxxxxxxxxx
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: tomcat 5.0 vs. 5.5? tomcat 5.5 has been bad!
Posted by Markus Schönhaber <ma...@schoenhaber.de>.
Dean Hiller wrote:
> yes, but please look at the solution I found in previous post which
> works WITHOUT stripping down everything.
I never doubted that there is a solution that doesn't require leaving almost
everything out. The fact that the stripped down version behaves as desired
simply proves that it's not a Tomcat problem but a problem with your webapp.
> I think tomcat should fix this
> by reporting something like this
>
> log.log(Level.WARNING, "Application Errors will not be logged because
> webapp has log4j but no config file", new RuntimeException("See
> msg).fillInStackTrace());
>
> The RuntimeException is to make it more noticeable in the logs. I mean
> 953 hits on googling is quite alot of people having trouble. Would be
> nice to cut that number down with an easy log statement that tomcat
> could add!!!
Well, if it's really that easy you should definitely provide a patch.
Regards
mks
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: tomcat 5.0 vs. 5.5? tomcat 5.5 has been bad!
Posted by Dean Hiller <de...@xsoftware.biz>.
yes, but please look at the solution I found in previous post which
works WITHOUT stripping down everything. I think tomcat should fix this
by reporting something like this
log.log(Level.WARNING, "Application Errors will not be logged because
webapp has log4j but no config file", new RuntimeException("See
msg).fillInStackTrace());
The RuntimeException is to make it more noticeable in the logs. I mean
953 hits on googling is quite alot of people having trouble. Would be
nice to cut that number down with an easy log statement that tomcat
could add!!!
thanks,
dean
Markus Schönhaber wrote:
>Dean Hiller wrote:
>
>
>>Okay, a zip file with one *.java file and one *.class file can be found
>>here...
>>
>>https://pro40.abac.com/deanhiller/cgi-bin/moin.cgi/Downloads
>>
>>You can unzip it and copy the folder to tomcat/webapps and watch no
>>Exception get logged. Just the " Error listenerStart" message gets
>>logged an no more information is there. Google has 953 references to
>>"Error listenerStart" and many of them are "what went wrong with my app"
>>as there is no stack trace. I haven't found any posts answering those
>>questions though.
>>
>>
>
>If I strip down this webapp to only contain the LifecycleListener - i. e.
>remove logging.properties, remove the lib dir, remove filters and listeners
>short of LifecycleListener from web.xml - the stacktrace gets logged in
>localhost.<date>.log.
>
>Regards
> mks
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: tomcat 5.0 vs. 5.5? tomcat 5.5 has been bad!
Posted by Markus Schönhaber <ma...@schoenhaber.de>.
Dean Hiller wrote:
> Okay, a zip file with one *.java file and one *.class file can be found
> here...
>
> https://pro40.abac.com/deanhiller/cgi-bin/moin.cgi/Downloads
>
> You can unzip it and copy the folder to tomcat/webapps and watch no
> Exception get logged. Just the " Error listenerStart" message gets
> logged an no more information is there. Google has 953 references to
> "Error listenerStart" and many of them are "what went wrong with my app"
> as there is no stack trace. I haven't found any posts answering those
> questions though.
If I strip down this webapp to only contain the LifecycleListener - i. e.
remove logging.properties, remove the lib dir, remove filters and listeners
short of LifecycleListener from web.xml - the stacktrace gets logged in
localhost.<date>.log.
Regards
mks
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: thanks very much Filip
Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
you're welcome, just doing what I can in the time I have allotted :)
Dean Hiller wrote:
> BTW, I was pretty much stuck until you responded to my post like alot
> of the others I have seen with a similar post and no answer. If you
> had not responded, I would probably still be stuck and still googling,
> reading, trying to solve it. I really really appreciate your help. I
> could not find anything through google, or tomcat docs based on the
> info I had from tomcat logs. I was utterly lost until you prodded
> me(and that gave me some ideas).
> thanks,
> dean
>
> Filip Hanik - Dev Lists wrote:
>
>> ok, that was fairly easy, the error gets logged to the
>> <TOMCAT_HOME>/logs/localhost.2006-03-29.log" this is on the default
>> install, no loggers modified
>>
>> so are you still having a problem?
>>
>> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.ApplicationContext log
>> INFO: org.apache.webapp.balancer.BalancerFilter: init(): ruleChain:
>> [org.apache.webapp.balancer.RuleChain:
>> [org.apache.webapp.balancer.rules.URLStringMatchRule: Target string:
>> News / Redirect URL: http://www.cnn.com],
>> [org.apache.webapp.balancer.rules.RequestParameterRule: Target param
>> name: paramName / Target param value: paramValue / Redirect URL:
>> http://www.yahoo.com],
>> [org.apache.webapp.balancer.rules.AcceptEverythingRule: Redirect URL:
>> http://jakarta.apache.org]]
>> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.ApplicationContext log
>> INFO: ContextListener: contextInitialized()
>> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.StandardContext
>> listenerStart
>> SEVERE: Exception sending context initialized event to listener
>> instance of class listeners.ContextListener
>> java.lang.RuntimeException: sdadasda
>> at
>> listeners.ContextListener.contextInitialized(ContextListener.java:114)
>> at
>> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3729)
>>
>> at
>> org.apache.catalina.core.StandardContext.start(StandardContext.java:4187)
>>
>> at
>> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
>>
>> at
>> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
>> at
>> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
>> at
>> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:904)
>>
>> at
>> org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:867)
>>
>> at
>> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:474)
>> at
>> org.apache.catalina.startup.HostConfig.start(HostConfig.java:1122)
>> at
>> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310)
>>
>> at
>> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
>>
>> at
>> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1021)
>> at
>> org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
>> at
>> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
>> at
>> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
>> at
>> org.apache.catalina.core.StandardService.start(StandardService.java:450)
>> at
>> org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
>> at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
>> 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:585)
>> at
>> org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:275)
>> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
>> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.ApplicationContext log
>> INFO: SessionListener: contextInitialized()
>> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.ApplicationContext log
>>
>>
>> Dean Hiller wrote:
>>
>>> thanks for the link. I need that too. Regardless of logging
>>> thought, quickly add this to any serlvetlistener
>>>
>>> public void contextInitialized(ServletContextEvent evt) {
>>> throw new RuntimeException("asdfsf");
>>> }
>>>
>>> Run it, and enjoy not being able to know what the heck went wrong
>>> with your app like I have seen many have done on the posts already.
>>> ie. Tomcat used to log the stack trace, but in 5.5 does not, and
>>> that should be high enough warning level that config of logs don't
>>> matter.
>>>
>>> Making the problem even harder.....
>>> On a second note, I have fooled around with logging and it works
>>> fine in my app, and I could configure it and such(with 5.5) and my
>>> logging.properties file in WEB-INF. I could never get my
>>> servletlistener to log any statements(making the problem doubly hard).
>>> thanks,
>>> dean
>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
thanks very much Filip
Posted by Dean Hiller <de...@xsoftware.biz>.
BTW, I was pretty much stuck until you responded to my post like alot of
the others I have seen with a similar post and no answer. If you had
not responded, I would probably still be stuck and still googling,
reading, trying to solve it. I really really appreciate your help. I
could not find anything through google, or tomcat docs based on the info
I had from tomcat logs. I was utterly lost until you prodded me(and
that gave me some ideas).
thanks,
dean
Filip Hanik - Dev Lists wrote:
> ok, that was fairly easy, the error gets logged to the
> <TOMCAT_HOME>/logs/localhost.2006-03-29.log" this is on the default
> install, no loggers modified
>
> so are you still having a problem?
>
> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.ApplicationContext log
> INFO: org.apache.webapp.balancer.BalancerFilter: init(): ruleChain:
> [org.apache.webapp.balancer.RuleChain:
> [org.apache.webapp.balancer.rules.URLStringMatchRule: Target string:
> News / Redirect URL: http://www.cnn.com],
> [org.apache.webapp.balancer.rules.RequestParameterRule: Target param
> name: paramName / Target param value: paramValue / Redirect URL:
> http://www.yahoo.com],
> [org.apache.webapp.balancer.rules.AcceptEverythingRule: Redirect URL:
> http://jakarta.apache.org]]
> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.ApplicationContext log
> INFO: ContextListener: contextInitialized()
> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.StandardContext
> listenerStart
> SEVERE: Exception sending context initialized event to listener
> instance of class listeners.ContextListener
> java.lang.RuntimeException: sdadasda
> at
> listeners.ContextListener.contextInitialized(ContextListener.java:114)
> at
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3729)
>
> at
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4187)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
>
> at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
> at
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
> at
> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:904)
>
> at
> org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:867)
>
> at
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:474)
> at
> org.apache.catalina.startup.HostConfig.start(HostConfig.java:1122)
> at
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310)
>
> at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
>
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1021)
> at
> org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
> at
> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
> at
> org.apache.catalina.core.StandardService.start(StandardService.java:450)
> at
> org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
> 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:585)
> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:275)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.ApplicationContext log
> INFO: SessionListener: contextInitialized()
> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.ApplicationContext log
>
>
> Dean Hiller wrote:
>
>> thanks for the link. I need that too. Regardless of logging
>> thought, quickly add this to any serlvetlistener
>>
>> public void contextInitialized(ServletContextEvent evt) {
>> throw new RuntimeException("asdfsf");
>> }
>>
>> Run it, and enjoy not being able to know what the heck went wrong
>> with your app like I have seen many have done on the posts already.
>> ie. Tomcat used to log the stack trace, but in 5.5 does not, and that
>> should be high enough warning level that config of logs don't matter.
>>
>> Making the problem even harder.....
>> On a second note, I have fooled around with logging and it works fine
>> in my app, and I could configure it and such(with 5.5) and my
>> logging.properties file in WEB-INF. I could never get my
>> servletlistener to log any statements(making the problem doubly hard).
>> thanks,
>> dean
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: tomcat 5.0 vs. 5.5? tomcat 5.5 has been bad!
Posted by Dean Hiller <de...@xsoftware.biz>.
I am still getting no log there.....my localhost is empty! Other logs
get filled, I will trim all the fat off. Could it be that I am using
myfaces? BUT myfaces doesn't sit between servletContextListener and
tomcat, so I am really confused. Let me trim the fat(jsp files and
such). All I am doing is throwing a runtimeException. I will send a
zip in a few.\
thanks,
dean
Filip Hanik - Dev Lists wrote:
> ok, that was fairly easy, the error gets logged to the
> <TOMCAT_HOME>/logs/localhost.2006-03-29.log" this is on the default
> install, no loggers modified
>
> so are you still having a problem?
>
> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.ApplicationContext log
> INFO: org.apache.webapp.balancer.BalancerFilter: init(): ruleChain:
> [org.apache.webapp.balancer.RuleChain:
> [org.apache.webapp.balancer.rules.URLStringMatchRule: Target string:
> News / Redirect URL: http://www.cnn.com],
> [org.apache.webapp.balancer.rules.RequestParameterRule: Target param
> name: paramName / Target param value: paramValue / Redirect URL:
> http://www.yahoo.com],
> [org.apache.webapp.balancer.rules.AcceptEverythingRule: Redirect URL:
> http://jakarta.apache.org]]
> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.ApplicationContext log
> INFO: ContextListener: contextInitialized()
> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.StandardContext
> listenerStart
> SEVERE: Exception sending context initialized event to listener
> instance of class listeners.ContextListener
> java.lang.RuntimeException: sdadasda
> at
> listeners.ContextListener.contextInitialized(ContextListener.java:114)
> at
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3729)
>
> at
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4187)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
>
> at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
> at
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
> at
> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:904)
>
> at
> org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:867)
>
> at
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:474)
> at
> org.apache.catalina.startup.HostConfig.start(HostConfig.java:1122)
> at
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310)
>
> at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
>
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1021)
> at
> org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
> at
> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
> at
> org.apache.catalina.core.StandardService.start(StandardService.java:450)
> at
> org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
> 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:585)
> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:275)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.ApplicationContext log
> INFO: SessionListener: contextInitialized()
> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.ApplicationContext log
>
>
> Dean Hiller wrote:
>
>> thanks for the link. I need that too. Regardless of logging
>> thought, quickly add this to any serlvetlistener
>>
>> public void contextInitialized(ServletContextEvent evt) {
>> throw new RuntimeException("asdfsf");
>> }
>>
>> Run it, and enjoy not being able to know what the heck went wrong
>> with your app like I have seen many have done on the posts already.
>> ie. Tomcat used to log the stack trace, but in 5.5 does not, and that
>> should be high enough warning level that config of logs don't matter.
>>
>> Making the problem even harder.....
>> On a second note, I have fooled around with logging and it works fine
>> in my app, and I could configure it and such(with 5.5) and my
>> logging.properties file in WEB-INF. I could never get my
>> servletlistener to log any statements(making the problem doubly hard).
>> thanks,
>> dean
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: tomcat 5.0 vs. 5.5? SOLUTION!!! figured out tomcat bug!
Posted by Dean Hiller <de...@xsoftware.biz>.
Found the solution. This is for all those posters who will run into
this tomcat bug(well, at least, I consider this a bug). Basically,
somehow, I had a log4j jar in my WEB-INF/lib folder. This would cause
logging to work in some places and not others. It would sometimes work
going to java.util.logging and sometimes would not depending on the
siutation. Here is a posted example of it not working....
https://pro40.abac.com/deanhiller/cgi-bin/moin.cgi/Downloads
Just unzip and copy to webapps directory and notice not much information
on why your servlet did not start!!!!! Erase the log4j jar and get
plenty of information.
Keywords for google
Error listenerStart tomcat logging not working
Error listenerStart tomcat logging not working
Error listenerStart tomcat logging not working
Error listenerStart tomcat logging not working
Error listenerStart tomcat logging not working
Error listenerStart tomcat logging not working
Error listenerStart tomcat logging not working
Error listenerStart tomcat logging not working
Error listenerStart tomcat logging not working
Error listenerStart tomcat logging not working
Error listenerStart tomcat logging not working
Dean Hiller wrote:
> Okay, a zip file with one *.java file and one *.class file can be
> found here...
>
> https://pro40.abac.com/deanhiller/cgi-bin/moin.cgi/Downloads
>
> You can unzip it and copy the folder to tomcat/webapps and watch no
> Exception get logged. Just the " Error listenerStart" message gets
> logged an no more information is there. Google has 953 references to
> "Error listenerStart" and many of them are "what went wrong with my
> app" as there is no stack trace. I haven't found any posts answering
> those questions though.
> thanks,
> dean
>
> Filip Hanik - Dev Lists wrote:
>
>> ok, that was fairly easy, the error gets logged to the
>> <TOMCAT_HOME>/logs/localhost.2006-03-29.log" this is on the default
>> install, no loggers modified
>>
>> so are you still having a problem?
>>
>> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.ApplicationContext log
>> INFO: org.apache.webapp.balancer.BalancerFilter: init(): ruleChain:
>> [org.apache.webapp.balancer.RuleChain:
>> [org.apache.webapp.balancer.rules.URLStringMatchRule: Target string:
>> News / Redirect URL: http://www.cnn.com],
>> [org.apache.webapp.balancer.rules.RequestParameterRule: Target param
>> name: paramName / Target param value: paramValue / Redirect URL:
>> http://www.yahoo.com],
>> [org.apache.webapp.balancer.rules.AcceptEverythingRule: Redirect URL:
>> http://jakarta.apache.org]]
>> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.ApplicationContext log
>> INFO: ContextListener: contextInitialized()
>> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.StandardContext
>> listenerStart
>> SEVERE: Exception sending context initialized event to listener
>> instance of class listeners.ContextListener
>> java.lang.RuntimeException: sdadasda
>> at
>> listeners.ContextListener.contextInitialized(ContextListener.java:114)
>> at
>> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3729)
>>
>> at
>> org.apache.catalina.core.StandardContext.start(StandardContext.java:4187)
>>
>> at
>> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
>>
>> at
>> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
>> at
>> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
>> at
>> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:904)
>>
>> at
>> org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:867)
>>
>> at
>> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:474)
>> at
>> org.apache.catalina.startup.HostConfig.start(HostConfig.java:1122)
>> at
>> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310)
>>
>> at
>> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
>>
>> at
>> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1021)
>> at
>> org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
>> at
>> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
>> at
>> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
>> at
>> org.apache.catalina.core.StandardService.start(StandardService.java:450)
>> at
>> org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
>> at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
>> 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:585)
>> at
>> org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:275)
>> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
>> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.ApplicationContext log
>> INFO: SessionListener: contextInitialized()
>> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.ApplicationContext log
>>
>>
>> Dean Hiller wrote:
>>
>>> thanks for the link. I need that too. Regardless of logging
>>> thought, quickly add this to any serlvetlistener
>>>
>>> public void contextInitialized(ServletContextEvent evt) {
>>> throw new RuntimeException("asdfsf");
>>> }
>>>
>>> Run it, and enjoy not being able to know what the heck went wrong
>>> with your app like I have seen many have done on the posts already.
>>> ie. Tomcat used to log the stack trace, but in 5.5 does not, and
>>> that should be high enough warning level that config of logs don't
>>> matter.
>>>
>>> Making the problem even harder.....
>>> On a second note, I have fooled around with logging and it works
>>> fine in my app, and I could configure it and such(with 5.5) and my
>>> logging.properties file in WEB-INF. I could never get my
>>> servletlistener to log any statements(making the problem doubly hard).
>>> thanks,
>>> dean
>>>
>>>
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: tomcat 5.0 vs. 5.5? tomcat 5.5 has been bad!
Posted by Dean Hiller <de...@xsoftware.biz>.
Okay, a zip file with one *.java file and one *.class file can be found
here...
https://pro40.abac.com/deanhiller/cgi-bin/moin.cgi/Downloads
You can unzip it and copy the folder to tomcat/webapps and watch no
Exception get logged. Just the " Error listenerStart" message gets
logged an no more information is there. Google has 953 references to
"Error listenerStart" and many of them are "what went wrong with my app"
as there is no stack trace. I haven't found any posts answering those
questions though.
thanks,
dean
Filip Hanik - Dev Lists wrote:
> ok, that was fairly easy, the error gets logged to the
> <TOMCAT_HOME>/logs/localhost.2006-03-29.log" this is on the default
> install, no loggers modified
>
> so are you still having a problem?
>
> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.ApplicationContext log
> INFO: org.apache.webapp.balancer.BalancerFilter: init(): ruleChain:
> [org.apache.webapp.balancer.RuleChain:
> [org.apache.webapp.balancer.rules.URLStringMatchRule: Target string:
> News / Redirect URL: http://www.cnn.com],
> [org.apache.webapp.balancer.rules.RequestParameterRule: Target param
> name: paramName / Target param value: paramValue / Redirect URL:
> http://www.yahoo.com],
> [org.apache.webapp.balancer.rules.AcceptEverythingRule: Redirect URL:
> http://jakarta.apache.org]]
> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.ApplicationContext log
> INFO: ContextListener: contextInitialized()
> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.StandardContext
> listenerStart
> SEVERE: Exception sending context initialized event to listener
> instance of class listeners.ContextListener
> java.lang.RuntimeException: sdadasda
> at
> listeners.ContextListener.contextInitialized(ContextListener.java:114)
> at
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3729)
>
> at
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4187)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
>
> at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
> at
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
> at
> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:904)
>
> at
> org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:867)
>
> at
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:474)
> at
> org.apache.catalina.startup.HostConfig.start(HostConfig.java:1122)
> at
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310)
>
> at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
>
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1021)
> at
> org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
> at
> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
> at
> org.apache.catalina.core.StandardService.start(StandardService.java:450)
> at
> org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
> 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:585)
> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:275)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.ApplicationContext log
> INFO: SessionListener: contextInitialized()
> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.ApplicationContext log
>
>
> Dean Hiller wrote:
>
>> thanks for the link. I need that too. Regardless of logging
>> thought, quickly add this to any serlvetlistener
>>
>> public void contextInitialized(ServletContextEvent evt) {
>> throw new RuntimeException("asdfsf");
>> }
>>
>> Run it, and enjoy not being able to know what the heck went wrong
>> with your app like I have seen many have done on the posts already.
>> ie. Tomcat used to log the stack trace, but in 5.5 does not, and that
>> should be high enough warning level that config of logs don't matter.
>>
>> Making the problem even harder.....
>> On a second note, I have fooled around with logging and it works fine
>> in my app, and I could configure it and such(with 5.5) and my
>> logging.properties file in WEB-INF. I could never get my
>> servletlistener to log any statements(making the problem doubly hard).
>> thanks,
>> dean
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: tomcat 5.0 vs. 5.5? tomcat 5.5 has been bad!
Posted by Dean Hiller <de...@xsoftware.biz>.
thankyou very much for taking the time to simulate that. I am going to
try your code and compare it to mine and see why mine was not showing up
there at all.
thanks,
dean
Filip Hanik - Dev Lists wrote:
> ok, that was fairly easy, the error gets logged to the
> <TOMCAT_HOME>/logs/localhost.2006-03-29.log" this is on the default
> install, no loggers modified
>
> so are you still having a problem?
>
> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.ApplicationContext log
> INFO: org.apache.webapp.balancer.BalancerFilter: init(): ruleChain:
> [org.apache.webapp.balancer.RuleChain:
> [org.apache.webapp.balancer.rules.URLStringMatchRule: Target string:
> News / Redirect URL: http://www.cnn.com],
> [org.apache.webapp.balancer.rules.RequestParameterRule: Target param
> name: paramName / Target param value: paramValue / Redirect URL:
> http://www.yahoo.com],
> [org.apache.webapp.balancer.rules.AcceptEverythingRule: Redirect URL:
> http://jakarta.apache.org]]
> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.ApplicationContext log
> INFO: ContextListener: contextInitialized()
> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.StandardContext
> listenerStart
> SEVERE: Exception sending context initialized event to listener
> instance of class listeners.ContextListener
> java.lang.RuntimeException: sdadasda
> at
> listeners.ContextListener.contextInitialized(ContextListener.java:114)
> at
> org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3729)
>
> at
> org.apache.catalina.core.StandardContext.start(StandardContext.java:4187)
> at
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
>
> at
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
> at
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
> at
> org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:904)
>
> at
> org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:867)
>
> at
> org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:474)
> at
> org.apache.catalina.startup.HostConfig.start(HostConfig.java:1122)
> at
> org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310)
>
> at
> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
>
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1021)
> at
> org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
> at
> org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
> at
> org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
> at
> org.apache.catalina.core.StandardService.start(StandardService.java:450)
> at
> org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
> 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:585)
> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:275)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.ApplicationContext log
> INFO: SessionListener: contextInitialized()
> Mar 29, 2006 9:12:47 AM org.apache.catalina.core.ApplicationContext log
>
>
> Dean Hiller wrote:
>
>> thanks for the link. I need that too. Regardless of logging
>> thought, quickly add this to any serlvetlistener
>>
>> public void contextInitialized(ServletContextEvent evt) {
>> throw new RuntimeException("asdfsf");
>> }
>>
>> Run it, and enjoy not being able to know what the heck went wrong
>> with your app like I have seen many have done on the posts already.
>> ie. Tomcat used to log the stack trace, but in 5.5 does not, and that
>> should be high enough warning level that config of logs don't matter.
>>
>> Making the problem even harder.....
>> On a second note, I have fooled around with logging and it works fine
>> in my app, and I could configure it and such(with 5.5) and my
>> logging.properties file in WEB-INF. I could never get my
>> servletlistener to log any statements(making the problem doubly hard).
>> thanks,
>> dean
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: tomcat 5.0 vs. 5.5? tomcat 5.5 has been bad!
Posted by Filip Hanik - Dev Lists <de...@hanik.com>.
ok, that was fairly easy, the error gets logged to the
<TOMCAT_HOME>/logs/localhost.2006-03-29.log" this is on the default
install, no loggers modified
so are you still having a problem?
Mar 29, 2006 9:12:47 AM org.apache.catalina.core.ApplicationContext log
INFO: org.apache.webapp.balancer.BalancerFilter: init(): ruleChain:
[org.apache.webapp.balancer.RuleChain:
[org.apache.webapp.balancer.rules.URLStringMatchRule: Target string:
News / Redirect URL: http://www.cnn.com],
[org.apache.webapp.balancer.rules.RequestParameterRule: Target param
name: paramName / Target param value: paramValue / Redirect URL:
http://www.yahoo.com],
[org.apache.webapp.balancer.rules.AcceptEverythingRule: Redirect URL:
http://jakarta.apache.org]]
Mar 29, 2006 9:12:47 AM org.apache.catalina.core.ApplicationContext log
INFO: ContextListener: contextInitialized()
Mar 29, 2006 9:12:47 AM org.apache.catalina.core.StandardContext
listenerStart
SEVERE: Exception sending context initialized event to listener instance
of class listeners.ContextListener
java.lang.RuntimeException: sdadasda
at
listeners.ContextListener.contextInitialized(ContextListener.java:114)
at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3729)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4187)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739)
at
org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524)
at
org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:904)
at
org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:867)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:474)
at
org.apache.catalina.startup.HostConfig.start(HostConfig.java:1122)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:310)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1021)
at
org.apache.catalina.core.StandardHost.start(StandardHost.java:718)
at
org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1013)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:442)
at
org.apache.catalina.core.StandardService.start(StandardService.java:450)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:709)
at org.apache.catalina.startup.Catalina.start(Catalina.java:551)
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:585)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:275)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413)
Mar 29, 2006 9:12:47 AM org.apache.catalina.core.ApplicationContext log
INFO: SessionListener: contextInitialized()
Mar 29, 2006 9:12:47 AM org.apache.catalina.core.ApplicationContext log
Dean Hiller wrote:
> thanks for the link. I need that too. Regardless of logging thought,
> quickly add this to any serlvetlistener
>
> public void contextInitialized(ServletContextEvent evt) {
> throw new RuntimeException("asdfsf");
> }
>
> Run it, and enjoy not being able to know what the heck went wrong with
> your app like I have seen many have done on the posts already. ie.
> Tomcat used to log the stack trace, but in 5.5 does not, and that
> should be high enough warning level that config of logs don't matter.
>
> Making the problem even harder.....
> On a second note, I have fooled around with logging and it works fine
> in my app, and I could configure it and such(with 5.5) and my
> logging.properties file in WEB-INF. I could never get my
> servletlistener to log any statements(making the problem doubly hard).
> thanks,
> dean
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: tomcat 5.0 vs. 5.5? tomcat 5.5 has been bad!
Posted by Dean Hiller <de...@xsoftware.biz>.
thanks for the link. I need that too. Regardless of logging thought,
quickly add this to any serlvetlistener
public void contextInitialized(ServletContextEvent evt) {
throw new RuntimeException("asdfsf");
}
Run it, and enjoy not being able to know what the heck went wrong with
your app like I have seen many have done on the posts already. ie.
Tomcat used to log the stack trace, but in 5.5 does not, and that should
be high enough warning level that config of logs don't matter.
Making the problem even harder.....
On a second note, I have fooled around with logging and it works fine in
my app, and I could configure it and such(with 5.5) and my
logging.properties file in WEB-INF. I could never get my
servletlistener to log any statements(making the problem doubly hard).
thanks,
dean
Vamsidhar wrote:
>I am assuming you have been using logger to log stack traces in case of
>errors in tomcat 5.0. This was deprecated in 5.0 and completely removed in
>5.5. So, If you have logger defined for engine, host, or context to record
>the stack traces in a file in your application this will not work on tomcat
>5.5
>
>http://tomcat.apache.org/tomcat-5.0-doc/config/logger.html
>"Please note that Loggers are deprecated in Tomcat 5.0 and removed from
>Tomcat 5.5. Tomcat 5.5 uses Commons-Logging instead."
>
>hope this helps.
>
>On 3/28/06, dean@xsoftware.biz <de...@xsoftware.biz> wrote:
>
>
>>On number 1 5.0 logs the entire stack trace, so you can jump to the line
>>number. On 5.5, no such stack trace in any file. Also, I searched a few
>>lists and many people had questions on what was wron when they saw that
>>error. I think the cause is the lack of information....it should at the
>>very least log the stack trace and does not.
>>
>>I just used the latest facelets and it did not work, but worked on 5.0.
>>
>>in fact, all the stuff works on 5.0 which leads me to believe 5.5 is
>>unstable, but I wanted to verify.
>>dean
>>
>>
>>
>>>On 3/28/06, dean@xsoftware.biz <de...@xsoftware.biz> wrote:
>>>
>>>
>>>>Anyone have much experience with running on these. On tomcat 5.5, I
>>>>have
>>>>ran into many problems
>>>>1. exception fron ServletContextListener.contextInitialized causes the
>>>>vague error of "Error listenerStart" with no details. Most people on
>>>>lists I have seen don't even know it was caused by Exception out of
>>>>
>>>>
>>that
>>
>>
>>>>method(Took me a while to figure out too)
>>>>
>>>>
>>>Yes, it's an extremely myterious log message, as a
>>>ServletContextListener is a listener for the context.
>>>
>>>
>>>
>>>>2. logging MyFaces logs was not working
>>>>
>>>>
>>>Whatever.
>>>
>>>
>>>
>>>>3. Facelets example war files don't work in 5.5.16
>>>>
>>>>
>>>It uses a bad method for descovering its config, if I remember well,
>>>which is now fixed.
>>>
>>>--
>>>xxxxxxxxxxxxxxxxxxxxxxxxx
>>>Rémy Maucherat
>>>Developer & Consultant
>>>JBoss Inc
>>>xxxxxxxxxxxxxxxxxxxxxxxxx
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>For additional commands, e-mail: users-help@tomcat.apache.org
>>>
>>>
>>>
>>>
>>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>>
>>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: tomcat 5.0 vs. 5.5? tomcat 5.5 has been bad!
Posted by Vamsidhar <va...@gmail.com>.
I am assuming you have been using logger to log stack traces in case of
errors in tomcat 5.0. This was deprecated in 5.0 and completely removed in
5.5. So, If you have logger defined for engine, host, or context to record
the stack traces in a file in your application this will not work on tomcat
5.5
http://tomcat.apache.org/tomcat-5.0-doc/config/logger.html
"Please note that Loggers are deprecated in Tomcat 5.0 and removed from
Tomcat 5.5. Tomcat 5.5 uses Commons-Logging instead."
hope this helps.
On 3/28/06, dean@xsoftware.biz <de...@xsoftware.biz> wrote:
>
>
> On number 1 5.0 logs the entire stack trace, so you can jump to the line
> number. On 5.5, no such stack trace in any file. Also, I searched a few
> lists and many people had questions on what was wron when they saw that
> error. I think the cause is the lack of information....it should at the
> very least log the stack trace and does not.
>
> I just used the latest facelets and it did not work, but worked on 5.0.
>
> in fact, all the stuff works on 5.0 which leads me to believe 5.5 is
> unstable, but I wanted to verify.
> dean
>
> > On 3/28/06, dean@xsoftware.biz <de...@xsoftware.biz> wrote:
> >> Anyone have much experience with running on these. On tomcat 5.5, I
> >> have
> >> ran into many problems
> >> 1. exception fron ServletContextListener.contextInitialized causes the
> >> vague error of "Error listenerStart" with no details. Most people on
> >> lists I have seen don't even know it was caused by Exception out of
> that
> >> method(Took me a while to figure out too)
> >
> > Yes, it's an extremely myterious log message, as a
> > ServletContextListener is a listener for the context.
> >
> >> 2. logging MyFaces logs was not working
> >
> > Whatever.
> >
> >> 3. Facelets example war files don't work in 5.5.16
> >
> > It uses a bad method for descovering its config, if I remember well,
> > which is now fixed.
> >
> > --
> > xxxxxxxxxxxxxxxxxxxxxxxxx
> > Rémy Maucherat
> > Developer & Consultant
> > JBoss Inc
> > xxxxxxxxxxxxxxxxxxxxxxxxx
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> > For additional commands, e-mail: users-help@tomcat.apache.org
> >
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
Re: tomcat 5.0 vs. 5.5? tomcat 5.5 has been bad!
Posted by de...@xsoftware.biz.
On number 1 5.0 logs the entire stack trace, so you can jump to the line
number. On 5.5, no such stack trace in any file. Also, I searched a few
lists and many people had questions on what was wron when they saw that
error. I think the cause is the lack of information....it should at the
very least log the stack trace and does not.
I just used the latest facelets and it did not work, but worked on 5.0.
in fact, all the stuff works on 5.0 which leads me to believe 5.5 is
unstable, but I wanted to verify.
dean
> On 3/28/06, dean@xsoftware.biz <de...@xsoftware.biz> wrote:
>> Anyone have much experience with running on these. On tomcat 5.5, I
>> have
>> ran into many problems
>> 1. exception fron ServletContextListener.contextInitialized causes the
>> vague error of "Error listenerStart" with no details. Most people on
>> lists I have seen don't even know it was caused by Exception out of that
>> method(Took me a while to figure out too)
>
> Yes, it's an extremely myterious log message, as a
> ServletContextListener is a listener for the context.
>
>> 2. logging MyFaces logs was not working
>
> Whatever.
>
>> 3. Facelets example war files don't work in 5.5.16
>
> It uses a bad method for descovering its config, if I remember well,
> which is now fixed.
>
> --
> xxxxxxxxxxxxxxxxxxxxxxxxx
> Rémy Maucherat
> Developer & Consultant
> JBoss Inc
> xxxxxxxxxxxxxxxxxxxxxxxxx
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: tomcat 5.0 vs. 5.5? tomcat 5.5 has been bad!
Posted by Remy Maucherat <re...@gmail.com>.
On 3/28/06, dean@xsoftware.biz <de...@xsoftware.biz> wrote:
> Anyone have much experience with running on these. On tomcat 5.5, I have
> ran into many problems
> 1. exception fron ServletContextListener.contextInitialized causes the
> vague error of "Error listenerStart" with no details. Most people on
> lists I have seen don't even know it was caused by Exception out of that
> method(Took me a while to figure out too)
Yes, it's an extremely myterious log message, as a
ServletContextListener is a listener for the context.
> 2. logging MyFaces logs was not working
Whatever.
> 3. Facelets example war files don't work in 5.5.16
It uses a bad method for descovering its config, if I remember well,
which is now fixed.
--
xxxxxxxxxxxxxxxxxxxxxxxxx
Rémy Maucherat
Developer & Consultant
JBoss Inc
xxxxxxxxxxxxxxxxxxxxxxxxx
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org