Running RMI client in Tomcat 7 got ClassNotFoundException

Hi, I posted a question on stackoverflow but got no answer, can anybody help me here? I am having some difficulties with RMI and Tomcat. This is the big picture of this project I am working on: the RMI client is called by a Java servlet that runs in Tomcat, the servlet accept user input and pass t

Re: tomcat session mixing

Hi Chris, First, my apologies. Much of the terminology is unfamiliar to me here. I hope that I've managed to fully answer your questions. The "server calls" are all rmi calls on java-based servers on the same machine. There are no separate threads directly in the .jsp pages. The userToken

Precompiled tag compatibility issue between 5.5 and 7.0

We have precompiled tags which were compiled under 5.5.35 and don't work under 7.0.34. From my investigation, it appears it's due to an interface change in JspSourceDependent. The return type of getDependants() changed. For us the solution isn't as simple as recompiling for two reasons: we have

Re: tomcat session mixing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Joel, On 6/17/13 5:12 PM, joel wrote: > Thanks for the help. I'm not an expert with tomcat management, > There are no servlets. I don't know what Threadlocal, > doGet/doPost/etc are, so presumably haven't used them. Eventually, everything is a ser

Re: tomcat session mixing

Hi Chris, Thanks for the help. I'm not an expert with tomcat management, There are no servlets. I don't know what Threadlocal, doGet/doPost/etc are, so presumably haven't used them. No references are kept to request,response, session, or stream objects. At login, a user session token is stored

Re: Init params picked up before SCI?

On 17/06/2013 20:35, Nick Williams wrote: On Jun 17, 2013, at 2:33 PM, Mark Thomas wrote: On 17/06/2013 14:26, Nicholas Williams wrote: On Jun 17, 2013, at 8:15, Nick Williams wrote: It seems obvious, but I couldn't find it mentioned in the spec, which concerns me. Hopefully I'm overlooki

Re: Init params picked up before SCI?

On Jun 17, 2013, at 2:33 PM, Mark Thomas wrote: > On 17/06/2013 14:26, Nicholas Williams wrote: >> On Jun 17, 2013, at 8:15, Nick Williams >> wrote: >> >>> It seems obvious, but I couldn't find it mentioned in the spec, which >>> concerns me. Hopefully I'm overlooking something. >>> >>> All

Re: Init params picked up before SCI?

On 17/06/2013 14:26, Nicholas Williams wrote: On Jun 17, 2013, at 8:15, Nick Williams wrote: It seems obvious, but I couldn't find it mentioned in the spec, which concerns me. Hopefully I'm overlooking something. All s in the (merged?) deployment descriptor are guaranteed to be picked up an

Re: tomcat session mixing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Joel, On 6/17/13 12:01 PM, joel wrote: > Thanks for the info! I'll look into making the upgrade. > > Can you advise how an application bug can cause this when > restarting tomcat will fix it? That would help me wrap my mind > around something that

Re: tomcat session mixing

Hi Mark, Thanks for the info! I'll look into making the upgrade. Can you advise how an application bug can cause this when restarting tomcat will fix it? That would help me wrap my mind around something that isn't imaginable, yet. Thanks! Joel On 2013-06-17 10:46, Mark Thomas wrote:

Re: tomcat session mixing

On 17/06/2013 16:32, joel wrote: Hi, I'm using Apache Tomcat/6.0.24 running on centos and have several times observed a rare issue in which user sessions are "mixed". When this occurs, userA clicks on a link and is provided with userB specific content, content that should only be accessible to

tomcat session mixing

Hi, I'm using Apache Tomcat/6.0.24 running on centos and have several times observed a rare issue in which user sessions are "mixed". When this occurs, userA clicks on a link and is provided with userB specific content, content that should only be accessible to userB. When this "mixing" occurs

Re: Init params picked up before SCI?

On Jun 17, 2013, at 8:15, Nick Williams wrote: > It seems obvious, but I couldn't find it mentioned in the spec, which > concerns me. Hopefully I'm overlooking something. > > All s in the (merged?) deployment descriptor are guaranteed to be > picked up and placed in the ServletContext before an

Init params picked up before SCI?

It seems obvious, but I couldn't find it mentioned in the spec, which concerns me. Hopefully I'm overlooking something. All s in the (merged?) deployment descriptor are guaranteed to be picked up and placed in the ServletContext before any ServletContainerInitializers are triggered, right? Nic