Re: Tomcat 7.0.34 JspC issue?

[Mark Thomas]

Jess Holle  wrote:

>I moved to Tomcat 7.0.34 -- apparently with inadequate testing / too 
>much trust.
>
>Some JSPs that precompiled just fine with 7.0.33 and many previous 
>Tomcat versions now produce the error shown below
>
>Moving back to the ecj jar from Tomcat 7.0.33 resolves the issue. I'm 
>assuming buggy JDT compiler until proven otherwise.

It certainly sounds like a bug in ecj.jar

Do you have a sample JSP you can share that demonstrates the issue?

Mark


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

Tomcat 7.0.34 JspC issue?

[Jess Holle]

I moved to Tomcat 7.0.34 -- apparently with inadequate testing / too 
much trust.


Some JSPs that precompiled just fine with 7.0.33 and many previous 
Tomcat versions now produce the error shown below


Moving back to the ecj jar from Tomcat 7.0.33 resolves the issue. I'm 
assuming buggy JDT compiler until proven otherwise.


--
Jess Holle

  [jasper2] java.lang.ArrayStoreException: 
org.eclipse.jdt.internal.compiler.ast.ReturnStatement
  [jasper2] at 
org.eclipse.jdt.internal.compiler.flow.FinallyFlowContext.recordNullReference(FinallyFlowContext.java:440)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.flow.FinallyFlowContext.recordUsingNullReference(FinallyFlowContext.java:405)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.flow.LoopingFlowContext.complainOnDeferredNullChecks(LoopingFlowContext.java:278)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.DoStatement.analyseCode(DoStatement.java:112)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.Block.analyseCode(Block.java:39)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.IfStatement.analyseCode(IfStatement.java:102)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.Block.analyseCode(Block.java:39)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.TryStatement.analyseCode(TryStatement.java:260)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.Block.analyseCode(Block.java:39)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.IfStatement.analyseCode(IfStatement.java:102)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.LabeledStatement.analyseCode(LabeledStatement.java:54)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.Block.analyseCode(Block.java:39)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.DoStatement.analyseCode(DoStatement.java:69)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.Block.analyseCode(Block.java:39)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.IfStatement.analyseCode(IfStatement.java:102)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.Block.analyseCode(Block.java:39)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.DoStatement.analyseCode(DoStatement.java:69)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.Block.analyseCode(Block.java:39)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.IfStatement.analyseCode(IfStatement.java:102)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.Block.analyseCode(Block.java:39)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.DoStatement.analyseCode(DoStatement.java:69)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.Block.analyseCode(Block.java:39)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.IfStatement.analyseCode(IfStatement.java:102)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.Block.analyseCode(Block.java:39)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.DoStatement.analyseCode(DoStatement.java:69)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.Block.analyseCode(Block.java:39)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.IfStatement.analyseCode(IfStatement.java:102)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.Block.analyseCode(Block.java:39)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.DoStatement.analyseCode(DoStatement.java:69)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.Block.analyseCode(Block.java:39)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.IfStatement.analyseCode(IfStatement.java:102)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.Block.analyseCode(Block.java:39)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.TryStatement.analyseCode(TryStatement.java:336)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.MethodDeclaration.analyseCode(MethodDeclaration.java:110)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.internalAnalyseCode(TypeDeclaration.java:710)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.TypeDeclaration.analyseCode(TypeDeclaration.java:255)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.ast.CompilationUnitDeclaration.analyseCode(CompilationUnitDeclaration.java:111)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.Compiler.process(Compiler.java:776)
  [jasper2] at 
org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:470)
  [jasper2] at 
org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:458)
  [jasper2] at 
org.apache.jasper.compiler.Compiler.compile(Compiler.java:378)
  [jasper2] at org.apache.jasper.JspC.processFile(JspC.java:1179)
  [jasper2] at org.apache.jasper.JspC.execute(JspC.java:1329)
  [jasper2] at 
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
  [jasper2] at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
  [jasper2] at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(Dele

Re: tomcat7-maven-plugin

[Olivier Lamy]

Good detailed description :-).
I just wonder about the cli you are using ?

2012/12/12 Josh Gooding :
> I didn't want to come here to ask as I always hate to bother anyone, but
> maybe I should have come here first.  I'm coming up short on answers and
> ideas.  I'm having an issue with using maven and the tomcat7 plugin.
>
> Maven version -3.0.4
> Tomcat version - 7.0.29
> .jdk version - 1.6
> tomcat7-maven-plugin version - 2.0
>
> Hey group,  I am having an issue here with using the tomcat7-maven-plugin
> in conjunction with the tomcat 7 manager.  here's what I have so far.
>
> tomcat-users.xml -
>
> 
> 
> 
> 
>  roles="manager-gui,manager-script,admin"/>
> 
>
> in my M2_HOME/conf/settings.xml: (note not in my .m2/ directory)
> (I'll get to this definition in a minute)
>   
> org.apache.tomcat.maven
>   
>
> 
> 
>   LocalTomcatServer
>   localTomcatAdmin
>   password
> 
>   
>
> now for the last piece, in my pom-deploy.xml (parent) I have this:
>
> 
>  org.apache.tomcat.maven
>  tomcat7-maven-plugin
>  2.0
>  
>   LocalTomcatServer
>   /TripTixRX
>   8080
>  
> 
>
> I have verified that the manager works with the applied credentials, I can
> login and supply the credentials to my local /manager/html.
>
> The problem is that when I deploy through maven as mvn tomcat7:deploy and
> returns me the dreaded 401 - Unauthorized page with the same credentials.
> It's almost like maven is not parsing the configuration for the plugin
> maybe?
>
> At this point I don't know what to do.  I've turned on verbose output in
> maven and it shows what appears that the plugin is attempting to upload the
> war file twice and returns the 401 page.
>
>
> I also have a question as to getting this to work initially.  I added the
> org.apache.tomcat.maven to my conf/settings.xml
> to get the tomcat7 plugin to download and work, is this normal or should I
> not have to define it here?  I mean having to change and version maven
> settings.xml files seems a bit counter intuitive for preserving maximum
> portability right, or am I looking at this from the wrong angle?
>
> Any information anyone can provide as to where to look or what could be
> causing this issue, I would be greatly appreciated.
>
> Warmest regards,
>
> - Josh



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

tomcat7-maven-plugin

[Josh Gooding]

I didn't want to come here to ask as I always hate to bother anyone, but
maybe I should have come here first.  I'm coming up short on answers and
ideas.  I'm having an issue with using maven and the tomcat7 plugin.

Maven version -3.0.4
Tomcat version - 7.0.29
.jdk version - 1.6
tomcat7-maven-plugin version - 2.0

Hey group,  I am having an issue here with using the tomcat7-maven-plugin
in conjunction with the tomcat 7 manager.  here's what I have so far.

tomcat-users.xml -








in my M2_HOME/conf/settings.xml: (note not in my .m2/ directory)
(I'll get to this definition in a minute)
  
org.apache.tomcat.maven
  



  LocalTomcatServer
  localTomcatAdmin
  password

  

now for the last piece, in my pom-deploy.xml (parent) I have this:


 org.apache.tomcat.maven
 tomcat7-maven-plugin
 2.0
 
  LocalTomcatServer
  /TripTixRX
  8080
 


I have verified that the manager works with the applied credentials, I can
login and supply the credentials to my local /manager/html.

The problem is that when I deploy through maven as mvn tomcat7:deploy and
returns me the dreaded 401 - Unauthorized page with the same credentials.
It's almost like maven is not parsing the configuration for the plugin
maybe?

At this point I don't know what to do.  I've turned on verbose output in
maven and it shows what appears that the plugin is attempting to upload the
war file twice and returns the 401 page.


I also have a question as to getting this to work initially.  I added the
org.apache.tomcat.maven to my conf/settings.xml
to get the tomcat7 plugin to download and work, is this normal or should I
not have to define it here?  I mean having to change and version maven
settings.xml files seems a bit counter intuitive for preserving maximum
portability right, or am I looking at this from the wrong angle?

Any information anyone can provide as to where to look or what could be
causing this issue, I would be greatly appreciated.

Warmest regards,

- Josh

Re: According to TLD or attribute directive in tag file, attribute xml does not accept any expressions

[Mark Eggers]

On 12/12/2012 8:27 AM, Ferdie Romero wrote:

Hi,

I already tried using

<%@ taglib uri="http://java.sun.com/jsp/jstl/core"; prefix="c" %>^M
and

<%@ taglib uri="http://java.sun.com/jstl/core"; prefix="c" %>^M but I
got the same error.

Thanks.

On Wed, Dec 12, 2012 at 11:56 PM, Mark Eggers 
wrote:


On 12/12/2012 6:51 AM, Ferdie Romero wrote:


Hi Guys,

We are having issues upon testing our newly upgraded
tomcat/apache. We encounter the error below:



Dec 12, 2012 9:13:10 AM
org.apache.catalina.core.**StandardWrapperValve invoke

SEVERE: Servlet.service() for servlet [jsp] in context with path
[] threw exception [/Header.jsp (line: 35, column: 0) According
to TLD or attribute directive in tag file, attribute xml does not
accept any expressions] with root cause


Here’s a portion of the Header.jsp file containing line 35:



32 ^M

33  ^M

34   ^M

35  ^M

37^M

38   ^M

39  ^M



here's a portion of our web.xml:



http://java.sun.com/**xml/ns/javaee



"

xmlns:xsi="http://www.w3.org/**2001/XMLSchema-instance



"

xsi:schemaLocation="http://**java.sun.com/xml/ns/javaee



http://java.sun.com/xml/ns/**javaee/web-app_3_0.xsd"

version="3.0">



We also downloaded and installed in
/opt/app/cms/apache-tomcat-7.**0.32/lib and
/opt/app/cms/apache-tomcat-7.**0.32/webapps/ROOT/WEB-INF/lib the
following:



-rw-r--r--   1 root   sys 407178 Dec 12 07:43
javax.servlet.jsp.jstl-1.2.1.**jar -rw-r--r--   1 root   sys
32522 Dec 12 07:43 javax.servlet.jsp.jstl-api-1.**2.1.jar



Are there any other files we need to update. Your help will be
highly appreciated.



Thanks.



Make sure you're using the right URI in the taglib declaration at
the top of your page. The 1.0 ones don't take expressions if I
recall correctly.

. . . just my two cents. /mde/


Please don't top-post. Top-posting makes the conversation difficult to 
follow for those late to the thread.


I'm thinking it should be:

<%@taglib uri="http://java.sun.com/jsp/jstl/xml"; prefix="x"%>

Then again, I'm a systems person, and not so much of a Java programmer.

I got hit with this when exploring some internationalization work. I needed:

<%@taglib uri="http://java.sun.com/jsp/jstl/fmt"; prefix="fmt"%>

to fix the problem.

. . . . just my two cents.
/mde/

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

Re: According to TLD or attribute directive in tag file, attribute xml does not accept any expressions

[Ferdie Romero]

Hi,

I already tried using

<%@ taglib uri="http://java.sun.com/jsp/jstl/core"; prefix="c" %>^M
and

<%@ taglib uri="http://java.sun.com/jstl/core"; prefix="c" %>^M
but I got the same error.

Thanks.

On Wed, Dec 12, 2012 at 11:56 PM, Mark Eggers  wrote:

>  On 12/12/2012 6:51 AM, Ferdie Romero wrote:
>
>> Hi Guys,
>>
>> We are having issues upon testing our newly upgraded tomcat/apache.
>> We encounter the error below:
>>
>>
>>
>> Dec 12, 2012 9:13:10 AM org.apache.catalina.core.**StandardWrapperValve
>> invoke
>>
>> SEVERE: Servlet.service() for servlet [jsp] in context with path []
>> threw exception [/Header.jsp (line: 35, column: 0) According to TLD
>> or attribute directive in tag file, attribute xml does not accept any
>> expressions] with root cause
>>
>>
>> Here’s a portion of the Header.jsp file containing line 35:
>>
>>
>>
>> 32 ^M
>>
>> 33  ^M
>>
>> 34   ^M
>>
>> 35  >
>> 36   xslt =  "${topNavStylesheet}">^M
>>
>> 37^M
>>
>> 38   > />^M
>>
>> 39  ^M
>>
>>
>>
>> here's a portion of our web.xml:
>>
>>
>>
>> > xmlns="http://java.sun.com/**xml/ns/javaee
>> "
>> xmlns:xsi="http://www.w3.org/**2001/XMLSchema-instance
>> "
>> xsi:schemaLocation="http://**java.sun.com/xml/ns/javaee
>> http://java.sun.com/xml/ns/**javaee/web-app_3_0.xsd"
>> version="3.0">
>>
>>
>>
>> We also downloaded and installed in
>> /opt/app/cms/apache-tomcat-7.**0.32/lib and
>> /opt/app/cms/apache-tomcat-7.**0.32/webapps/ROOT/WEB-INF/lib the
>> following:
>>
>>
>>
>> -rw-r--r--   1 root   sys 407178 Dec 12 07:43
>> javax.servlet.jsp.jstl-1.2.1.**jar -rw-r--r--   1 root   sys
>> 32522 Dec 12 07:43 javax.servlet.jsp.jstl-api-1.**2.1.jar
>>
>>
>>
>> Are there any other files we need to update. Your help will be
>> highly appreciated.
>>
>>
>>
>> Thanks.
>>
>>
> Make sure you're using the right URI in the taglib declaration at the
> top of your page. The 1.0 ones don't take expressions if I recall
> correctly.
>
> . . . just my two cents.
> /mde/
>
> --**--**-
> To unsubscribe, e-mail: 
> users-unsubscribe@tomcat.**apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Re: According to TLD or attribute directive in tag file, attribute xml does not accept any expressions

[Mark Eggers]

On 12/12/2012 6:51 AM, Ferdie Romero wrote:

Hi Guys,

We are having issues upon testing our newly upgraded tomcat/apache.
We encounter the error below:



Dec 12, 2012 9:13:10 AM org.apache.catalina.core.StandardWrapperValve
invoke

SEVERE: Servlet.service() for servlet [jsp] in context with path []
threw exception [/Header.jsp (line: 35, column: 0) According to TLD
or attribute directive in tag file, attribute xml does not accept any
expressions] with root cause


Here’s a portion of the Header.jsp file containing line 35:



32 ^M

33  ^M

34   ^M

35  ^M

37^M

38   ^M

39  ^M



here's a portion of our web.xml:



http://java.sun.com/xml/ns/javaee";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd"; version="3.0">



We also downloaded and installed in
/opt/app/cms/apache-tomcat-7.0.32/lib and
/opt/app/cms/apache-tomcat-7.0.32/webapps/ROOT/WEB-INF/lib the
following:



-rw-r--r--   1 root   sys 407178 Dec 12 07:43
javax.servlet.jsp.jstl-1.2.1.jar -rw-r--r--   1 root   sys
32522 Dec 12 07:43 javax.servlet.jsp.jstl-api-1.2.1.jar



Are there any other files we need to update. Your help will be
highly appreciated.



Thanks.



Make sure you're using the right URI in the taglib declaration at the
top of your page. The 1.0 ones don't take expressions if I recall correctly.

. . . just my two cents.
/mde/

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

Re: I can only access Tomcat 7 when running via console (startup.bat)

[Christopher Schultz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

André,

On 12/11/12 6:28 PM, André Warnier wrote:
> Yuri E wrote:
>>> 
>> I added a exception for the 8080 port in the Windows XP Firewall 
>> settings. Tomcat is working now. Thanks for all the answers.
>> 
> 
> Yuri, for me that still does not explain why you could access
> Tomcat from "outside" when it was running in a console, but not
> when it was running as a service. Just opening port 8080 should
> either allow both, or none. Something here doesn't fit.

Just like Chuck said:

Running from the console runs java.exe (or javaw.exe -- can't
remember). He probably said "Allow" at some point long ago to a pop-up
asking about java.exe accepting network connections.

Running as a service runs Tomcat7.exe and services probably never
pop-up anything asking for allowing incoming network connections, so
it remained blocked.

It's probably worth logging an enhancement request to (optionally)
configure the firewall when installing Tomcat as a service.

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iEYEAREIAAYFAlDIogQACgkQ9CaO5/Lv0PBQVACgn2vhBv1jgCfDnyNKDzgSBNf0
zoIAn00GDKPi8l2epOirBeUmujIGFDQS
=P9Fm
-END PGP SIGNATURE-

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

Re: Tomcat 7.33 update on Windows

[Justin Larose]

Konstantin Kolinko  wrote on 12/11/2012 09:12:16 
AM:

> From: Konstantin Kolinko 
> To: Tomcat Users List 
> Date: 12/11/2012 09:12 AM
> Subject: Re: Tomcat 7.33 update on Windows
> 
> 2012/12/11 Justin Larose :
> > I just updated Tomcat 7 from version 7.11 to 7.33 on my windows server 
but
> > when I goto the URL I am seeing 500 error, "Cannot load JDBC driver 
class
> > 'com.microsoft.sqlserver.jdbc.SQLServerDriver'"
> > Not sure why. I made a copy of all config directories prior to install 
and
> > copied them all to the new Tomcat home. Below is the full stack.
> >
> > (...)
> >
> > root cause
> >
> > java.lang.ClassNotFoundException:
> > com.microsoft.sqlserver.jdbc.SQLServerDriver
> >

> What jar contains the above class and whether it is present in your
> installation? I guess you forgot to copy it.

> (It should be placed into Tomcat's lib/ directory).

Thanks for your help Konstantin.
It was missing a sql file in the lib directory. It wasn't there when I 
copied the old Tomcat directory so I had to copy it from another server.

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

**
This email and any files transmitted with it are intended solely for 
the use of the individual or agency to whom they are addressed. 
If you have received this email in error please notify the Navy 
Exchange Service Command e-mail administrator. This footnote 
also confirms that this email message has been scanned for the
presence of computer viruses.

Thank You!
**

Re: Tomcat 7 Maven Plugin - set MaxPermSize

[Olivier Lamy]

2012/12/11 David Miller :
> I'm using the tomcat-maven plugin to set a value for MaxPermSize but it's
> not working.
>
> You can see in the below plugin my setting for JAVA_OPTS - I've also tried
> MAVEN_OPTS and CATALINA_OPTS.
>
> I can see that it's not working using jvisualvm (can also tell because my
> app eventually craps out).
>
> The only way that I can get an increase in perm gen size is to explicitly
> set it like this:
> MAVEN_OPTS="-XX:MaxPermSize=1024m"
>
> Is it possible to use the tomcat-maven plugin to specify MaxPermSize size?
Nope that's the only way as running tomcat with the plugin is not done
in a jvm forked mode but in the same jvm as maven.
>
> Thanks!
>
> 
> org.apache.tomcat.maven
> tomcat7-maven-plugin
> 2.0
> 
> 
> -XX:MaxPermSize=1024M
> 
> 5
>
> ${project.build.directory}/${project.build.finalName}/META-INF/context.xml
> /xyz
> 
> 
> 
> com.sun.faces
> jsf-api
> 2.0.9
> 
> 
> com.sun.faces
> jsf-impl
> 2.0.9
> 
> 
> 



--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

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

NullPointerException in NioBlockingSelector - not a problem though

[Steffen Heil (Mailinglisten)]

Hi

I cannot reproduce it, but I've seen the following error in my logs a few
times now:

SEVERE: Error reading request, ignored
java.lang.NullPointerException
at
org.apache.tomcat.util.net.NioBlockingSelector.read(NioBlockingSelector.java
:193)
at
org.apache.tomcat.util.net.NioSelectorPool.read(NioSelectorPool.java:246)
at
org.apache.tomcat.util.net.NioSelectorPool.read(NioSelectorPool.java:227)
at
org.apache.coyote.http11.upgrade.UpgradeNioProcessor.fillReadBuffer(UpgradeN
ioProcessor.java:183)
at
org.apache.coyote.http11.upgrade.UpgradeNioProcessor.readSocket(UpgradeNioPr
ocessor.java:144)
at
org.apache.coyote.http11.upgrade.UpgradeNioProcessor.read(UpgradeNioProcesso
r.java:113)
at org.apache.catalina.websocket.WsFrame.nextFrame(WsFrame.java:213)
at
org.apache.catalina.websocket.WsInputStream.nextFrame(WsInputStream.java:68)
at
org.apache.catalina.websocket.StreamInbound.onData(StreamInbound.java:117)
at
org.apache.coyote.http11.upgrade.UpgradeProcessor.upgradeDispatch(UpgradePro
cessor.java:83)
at
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(Abstrac
tProtocol.java:583)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:
1653)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.ja
va:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:9
08)
at java.lang.Thread.run(Thread.java:662)

This error seems to happen only during shutdown.
So it's not a real issue.

I am using an own-build tomcat 7.0.33/rev. 1397285.
I know it's not the current and released version, but it seems that code has
not changed since.

Regards,
  Steffen





smime.p7s
Description: S/MIME cryptographic signature

[ANN] Apache Tomcat 7.0.34 released

[Mark Thomas]

The Apache Tomcat team announces the immediate availability of Apache
Tomcat 7.0.34.
Apache Tomcat is an open source software implementation of the Java
Servlet and JavaServer Pages technologies.

This release contains a small number of bug fixes and improvements
compared to version 7.0.33. The notable changes include:
- Improvements to the AccessLogValve to better handle non-standard DST
  changes and to provide option for the current access log to have a
  standard name.
- Fix various JMX registration and deregistration issues.
- Update the Eclipse JDT compiler to 4.2.1

Please refer to the change log for the complete list of changes:
http://tomcat.apache.org/tomcat-7.0-doc/changelog.html

Note: This version has 4 zip binaries: a generic one and three
  bundled with Tomcat native binaries for Windows operating systems
  running on different CPU architectures.

Note: If you use the APR/native AJP or HTTP connector you *must* upgrade
  to version 1.1.24 or later of the AJP/native library

Downloads:
http://tomcat.apache.org/download-70.cgi

Migration guides from Apache Tomcat 5.5.x and 6.0.x:
http://tomcat.apache.org/migration.html

Thank you,

-- The Apache Tomcat Team

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