| Ganymede JEE - Tomcat 6.0 Server Plugin [message #219057] |
Thu, 07 August 2008 13:24  |
Eclipse User |
|
|
|
Originally posted by: sascha.baumeister.gmail.com
Tomcat 5.5 and 6.0 enable their JULI adapter for java.util.logging by
default. However, in order to enable it when starting a Tomcat server in
Eclipse you need to add the following to the VM arguments of the server
runtime configuration:
" -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogMa nager "
This process is a quite cumbersome as it has to be repeated every time a
server instance is constructed. Furthermore, the server instance needs to
be started at least once to trigger the creation of the server runtime
configuration in the first place.
Additionally, the current settings create quite some confusion with
everyone trying to use java.util.logging using Tomcat under Eclipse, as
the webapp logging.properties files are just silently ignored by default.
You need to first find out that logging messages you expect are missing,
then figure out that Tomcat by default overloads the standard Logger
engine with JULI, and finally that JULI needs special treatment within
Eclipse - I guess this means a couple of hours wasted for everyone
involved.
Is there a chance to have the above setting added to the VM arguments list
the tooling creates for a Tomcat 5.5 and Tomcat 6.0+ server instance? It
doesn't seem to cause any harm even if java.util.logging isn't used, and
just causes a Tomcat server instance to be started the way it would be
outside Eclipse.
For details, please see section "java.util.logging" at
http://tomcat.apache.org/tomcat-6.0-doc/logging.html
Thanks in advance,
Sascha Baumeister
Software Architect and former JCP Spec Lead
|
|
|
| Re: Ganymede JEE - Tomcat 6.0 Server Plugin [message #219065 is a reply to message #219057] |
Thu, 07 August 2008 13:55  |
| Eclipse User |
|
|
|
Originally posted by: dcarver.starstandard.org
One thing that would be helpful is to add this information to the WTP
Tomcat FAQ.
http://wiki.eclipse.org/WTP_Tomcat_FAQ
This way the information is there for others and might help cut down on
some wasted time.
In the meantime, I'd open a feature request, unless Larry has a way to
make this happen automatically.
Dave
sascha wrote:
> Tomcat 5.5 and 6.0 enable their JULI adapter for java.util.logging by
> default. However, in order to enable it when starting a Tomcat server in
> Eclipse you need to add the following to the VM arguments of the server
> runtime configuration:
> " -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogMa nager "
>
> This process is a quite cumbersome as it has to be repeated every time a
> server instance is constructed. Furthermore, the server instance needs
> to be started at least once to trigger the creation of the server
> runtime configuration in the first place.
>
> Additionally, the current settings create quite some confusion with
> everyone trying to use java.util.logging using Tomcat under Eclipse, as
> the webapp logging.properties files are just silently ignored by
> default. You need to first find out that logging messages you expect are
> missing, then figure out that Tomcat by default overloads the standard
> Logger engine with JULI, and finally that JULI needs special treatment
> within Eclipse - I guess this means a couple of hours wasted for
> everyone involved.
>
> Is there a chance to have the above setting added to the VM arguments
> list the tooling creates for a Tomcat 5.5 and Tomcat 6.0+ server
> instance? It doesn't seem to cause any harm even if java.util.logging
> isn't used, and just causes a Tomcat server instance to be started the
> way it would be outside Eclipse.
>
> For details, please see section "java.util.logging" at
> http://tomcat.apache.org/tomcat-6.0-doc/logging.html
>
>
> Thanks in advance,
> Sascha Baumeister
> Software Architect and former JCP Spec Lead
>
|
|
|
| Re: Ganymede JEE - Tomcat 6.0 Server Plugin [message #219073 is a reply to message #219065] |
Thu, 07 August 2008 18:46 |
| Eclipse User |
|
|
|
Originally posted by: sascha.baumeister.gmail.com
The information is already in the FAQ under section 3.1.2, I think I found
the workaround there in the end.
The problem is that you need quite some time to find out about the
Eclipse-JULI-Tomcat connection in the first place, because the problem
symptoms are so secretive ...
|
|
|
| Re: Ganymede JEE - Tomcat 6.0 Server Plugin [message #219179 is a reply to message #219057] |
Tue, 12 August 2008 14:48 |
 Larry Isaacs
Messages: 1354
Registered: July 2009 |
Senior Member |
|
|
Logging configuration is one area not yet tackled in the WTP Tomcat
support. This main issue is that there are a lot more ways to get the
configuration into a non-working state that a working state. The main
advantage of the current "punt" in this area is that across Tomcat
versions, you can safely do whatever logging you choose in your webapps
without fear of the server's logging configuration causing it to break.
Eventually I plan address this, but with limited time and other features
and bugs to address, it's hard to say when that would occur. For now,
those who want to alter server's logging can do so, and assume
responsibility for ensuring it is compatible with any logging present in
webapps that will be deployed to that server.
Cheers,
Larry
sascha wrote:
> Tomcat 5.5 and 6.0 enable their JULI adapter for java.util.logging by
> default. However, in order to enable it when starting a Tomcat server in
> Eclipse you need to add the following to the VM arguments of the server
> runtime configuration:
> " -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogMa nager "
>
> This process is a quite cumbersome as it has to be repeated every time a
> server instance is constructed. Furthermore, the server instance needs
> to be started at least once to trigger the creation of the server
> runtime configuration in the first place.
>
> Additionally, the current settings create quite some confusion with
> everyone trying to use java.util.logging using Tomcat under Eclipse, as
> the webapp logging.properties files are just silently ignored by
> default. You need to first find out that logging messages you expect are
> missing, then figure out that Tomcat by default overloads the standard
> Logger engine with JULI, and finally that JULI needs special treatment
> within Eclipse - I guess this means a couple of hours wasted for
> everyone involved.
>
> Is there a chance to have the above setting added to the VM arguments
> list the tooling creates for a Tomcat 5.5 and Tomcat 6.0+ server
> instance? It doesn't seem to cause any harm even if java.util.logging
> isn't used, and just causes a Tomcat server instance to be started the
> way it would be outside Eclipse.
>
> For details, please see section "java.util.logging" at
> http://tomcat.apache.org/tomcat-6.0-doc/logging.html
>
>
> Thanks in advance,
> Sascha Baumeister
> Software Architect and former JCP Spec Lead
>
|
|
|
|
| Re: Ganymede JEE - Tomcat 6.0 Server Plugin [message #1385575 is a reply to message #1385492] |
Mon, 09 June 2014 15:44 |
Larry Isaacs
Messages: 1354
Registered: July 2009 |
Senior Member |
|
|
On 6/9/2014 9:33 AM, Tom Chatt wrote:
> Sad to say, here it is nearly 6 years later from the above conversation,
> and this is still an issue. I have been pulling my hair out for hours
> trying to figure out why I can't make a simple modification to the
> logging levels of the logs using Tomcat 7 in Eclipse Kepler. I don't
> know if the information above worked 6 years ago, but it's not working
> for me now. When I added the
> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager (along
> with another -D for the logging.properties location, as directed in one
> of the FAQs linked above), Tomcat immediately crashes and burn with a
> ClassNotFound exception on org.apache.juli.ClassLoaderLogManager. It
> really should not be this hard. May I suggest a "bump" to the priority
> on getting this to work right out of the box?
I gave this a quick try (with Kepler on Windows 7) with Tomcat 4.0.47
and encountered no problems. The fact that you encounter a
ClassNotFoundError indicates something is different with your
installation. If you double-click on the Tomcat server in the server's
view to open the server editor, then click on "Open launch
configuration" and go to "Classpath" tab, what do you see under "User
Entries". You should see at least bootstrap.jar and tomcat-juli.jar.
Cheers,
Larry
|
|
|
Powered by
FUDForum. Page generated in 0.04048 seconds
] 
Search
Help
Register
Login
Home
