On 14/7/09 16:59, Achal Patel wrote:
Thanks for the inputs.
We hv traced this problem to a bug with Tomcat server.
Have you filed a bug report? I'd be curious to see both the bug and
your solution. You can file a patch along with the bug.
https://issues.apache.org/bugzilla/
p
Basical
Thanks for the inputs.
We hv traced this problem to a bug with Tomcat server.
Basically the tomcat server is sending the response before the
context/session is set.
Since it is open source, we modified the code and that change has resolved
this 500 error.
The change we hv made is not the best poss
On 4/7/09 00:22, Konstantin Kolinko wrote:
HttpSession session = request.getSession();
Is the request a legit one (that is, the one that is being served by
Tomcat now)?
Requests are recycled immediately after their processing is done,
and it can result in null being returned by that method (th
> HttpSession session = request.getSession();
Is the request a legit one (that is, the one that is being served by
Tomcat now)?
Requests are recycled immediately after their processing is done,
and it can result in null being returned by that method (though throwing
an IllegalStateException would
Keep it simple. Try this first, if your problem is the "missing"
attribute from http session. At least this what i would do in your
place:
> Maybe, you're getting a new session every time you're calling
> this page
> and "settings" reference is getting null. I *think* this can happe
Hi, Achal.
On Sat, 2009-07-04 at 00:47 +0530, Achal Patel wrote:
> Hi Daniel,
>
> Yes, at Weblogic, request.getSession() is returning a non-null value AND
> "(Settings) session.getAttribute(ATTR_NAME)" is
>
> > working.
Ok.
>
> On Tomcat out of 5 requests this is happening for 2 times.
>
>
Hi Daniel,
Yes, at Weblogic, request.getSession() is returning a non-null value AND
"(Settings) session.getAttribute(ATTR_NAME)" is
> working.
On Tomcat out of 5 requests this is happening for 2 times.
Let me explain the deployment architecture:
1. User invokes JSP page
2. JSP calls homegrown f
On 3/7/09 15:18, Achal Patel wrote:
Its basically below:
HttpSession session = request.getSession();
Settings settings = (Settings) session.getAttribute(ATTR_NAME);
I debugged it and got to know that session is getting null and again
invoking the same resource from UI serves fine.
The same is w
How can the session been null if you're calling request.getSession() ?
"(...) Returns the current session associated with this request, or if
the request does not have a session, creates one. (...)"
http://java.sun.com/products/servlet/2.2/javadoc/javax/servlet/http/HttpServletRequest.ht
Hi, Achal.
On Fri, 2009-07-03 at 19:48 +0530, Achal Patel wrote:
> Its basically below:
>
> HttpSession session = request.getSession();
> Settings settings = (Settings) session.getAttribute(ATTR_NAME);
>
> I debugged it and got to know that session is getting null and again
> invoking the same
Its basically below:
HttpSession session = request.getSession();
Settings settings = (Settings) session.getAttribute(ATTR_NAME);
I debugged it and got to know that session is getting null and again
invoking the same resource from UI serves fine.
The same is working fine on Weblogic.
Regards,
Ach
On 3/7/09 14:25, Achal Patel wrote:
Hi,
I am facing strange issue with Tomcat 6 Jsp deployment.
I have JSP pages deployed which internally performs operations and generates
XML response which will be parsed using XSL and then finally displayed on
the UI.
Now when I invoke JSP pages from UI, sess
Hi,
I am facing strange issue with Tomcat 6 Jsp deployment.
I have JSP pages deployed which internally performs operations and generates
XML response which will be parsed using XSL and then finally displayed on
the UI.
Now when I invoke JSP pages from UI, session is getting null between the
reques
13 matches
Mail list logo
