Re: Tomcat 8.5.x missing javax.servlet.forward.* attributes in an included jsp?

On Sat, 2016-07-30 at 02:07 +, Wang, Andy wrote: > I did a quick read of the spec just now, and I can't find a good > explanation of which is correct.  Would this be considered a > regression in 8.5.x?  Another quick re-read: 9.4.2 Forwarded Request Parameters states this: These attributes

Tomcat 8.5.x missing javax.servlet.forward.* attributes in an included jsp?

I have a really simply example (courtesy of the developer that discovered this issue) at: https://dl.dropboxusercontent.com/u/24563006/TestApp.war It contains a test.jsp that does: <% String href= "/WEB-INF/jsp/test/test1.jsp"; RequestDispatcher rd = request.getRequestDispatcher(href);

Realm SSHA Code

I was looking at the source code for org.apache.catalina.realm.RealmBase and see that it can handle salted SHA for passwords. Does anyone have some example code that demonstrates generating the SSHA value: generating the salt, doing the digest, and outputting the value so that I could put it

Re: Huge Time Tomcat Manager

I see this on my system as well for all requests, except for the manager/status request, which shows the correct time. On Fri, Jul 29, 2016 at 5:06 PM, George Sexton wrote: > > On 7/21/2016 9:58 AM, Christopher Schultz wrote: > >> -BEGIN PGP SIGNED MESSAGE- >>

Re: Incorrect request processing times in server status

+1, the clock on my system is also correct and in sync. On Fri, Jul 29, 2016 at 5:04 PM, George Sexton wrote: > > > On 6/23/2016 5:12 AM, Mark Thomas wrote: > >> On 23/06/2016 12:11, Mohit Chawla wrote: >> >>> Hi, >>> >>> Can someone suggest if this should be opened as a

Re: Huge Time Tomcat Manager

On 7/21/2016 9:58 AM, Christopher Schultz wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Teresa, On 7/21/16 5:33 AM, Teresa Fasano wrote: I notice on my tomcat manager the huge and wrong values for the thread times. For example: 1469093029135 ms This is the information: Server

Re: Incorrect request processing times in server status

On 6/23/2016 5:12 AM, Mark Thomas wrote: On 23/06/2016 12:11, Mohit Chawla wrote: Hi, Can someone suggest if this should be opened as a bug instead ? Not a bug. Probably just an unstable system clock. I consistently see this on my server for the mod_jk connector. In my case, the

Hanging threads in tomee 1.7.4

Hi all,   I was really hoping you could help – I’m currently workingin application support and one of our key applications as started behavingabnormally when upgrading from Tomee version 1.68 to 1.7.4 (Apache Tomcat(TomEE)/7.0.68 (1.7.4)) .   JDK java version "1.8.0_77" Java(TM) SE

Tomee process status "Running" but application processing no order - Hung Threads?

Hi all, I was really hoping you could help - I'm currently working in application support and one of our key applications as started behaving abnormally when upgrading from Tomee version 1.68 to 1.7.4 (Apache Tomcat (TomEE)/7.0.68 (1.7.4)) . JDK java version "1.8.0_77" Java(TM) SE Runtime

Re: How to do a JNDI look up in a different thread

On 29/07/2016 11:41, Khandelwal, Dinesh wrote: > > Hi, > > As part of my project , we maintain multiple Hibernate session factories and > as building these session factories take lot of time which causes server to > take more time in start-up , we are creating these session factories in >

How to do a JNDI look up in a different thread

Hi, As part of my project , we maintain multiple Hibernate session factories and as building these session factories take lot of time which causes server to take more time in start-up , we are creating these session factories in different threads Each thread creating one factory but when

Problem with Cluster after upgrade to Tomcat 8.0.36.

Hi all. Tomcat-8.0.36; JDK 1.8.0_102; CentOS 6.8. After upgrade from 8.0.28 to 8.0.36 I have problem with my cluster. I use static membership cluster with two nodes with BackupManager. After update I have errors in default.log: "WARN org.apache.catalina.tribes.tipis.AbstractReplicatedMap -

Problem with Cluster after upgrade to Tomcat >8.0.30.

Hi all. Tomcat-8.0.36; JDK 1.8.0_102; CentOS 6.8. After upgrade from 8.0.28 to 8.0.36 I have problem with my cluster. I use static membership cluster with two nodes with BackupManager. After update I have errors in default.log: "WARN  org.apache.catalina.tribes.tipis.AbstractReplicatedMap -