Ella Gerstner wrote:
> 2009/7/15 Ella Gerstner <egerst...@gmail.com>
> 
>> Hi!!
>>
>> i developed a web aplication and in the log of the server show me this
>> exception, and i don“t know what is the problem,  somebody know what i have
>> to do??

Usually, the first step is to look at the relevant line of the source
code. You haven't told us which version, so I am going to assume that
you are using 6.0.20.

The code does change so it is important that when asking a question on
this list as a minimum you tell us:
- Tomcat version
- JDK/JRE version
- OS

So, Tomcat being open source we can browse the source here:
http://svn.apache.org/viewvc/tomcat/

We want Tomcat 6:
http://svn.apache.org/viewvc/tomcat/tc6.0.x/

And we'll look at trunk (where 6.0.x is being developed)
http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/

All the code is under /java and since this is Java, the structure
matches the package names so we want:
http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/java/org/apache/jk/server/JkMain.java?view=log

Click on annotate for HEAD so we get the latest code with line numbers:
http://svn.apache.org/viewvc/tomcat/tc6.0.x/trunk/java/org/apache/jk/server/JkMain.java?view=annotate


>> Jul 10, 2009 9:57:56 AM org.apache.catalina.connector.Connector pause
>> SEVERE: Protocol handler pause failed
>> java.lang.NullPointerException
>>        at org.apache.jk.server.JkMain.pause(JkMain.java:679)

So we want to look around line 679:
678 :               public void pause() throws Exception {
679 : markt 685712    // wEnv sometime null at shutdown - bug45591
680 :                 if (wEnv != null) {
681 :                   for( int i=0; i<wEnv.getHandlerCount(); i++ ) {
682 :                     if( wEnv.getHandler(i) != null ) {
683 :                       wEnv.getHandler(i).pause();
684 :                   }

The comment on line 679 looks rather relevant. Check the bug report to
be sure:
https://issues.apache.org/bugzilla/

Enter the bug number (45591):
https://issues.apache.org/bugzilla/show_bug.cgi?id=45591

Read the bug report and it tells you that this is fixed in 6.0.19
onwards and 5.5.27 onwards.

Mark


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to