tomee-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard W. Smith, Jr." <>
Subject Re: WARNING - Could NOT lazily initialize session context because of null RequestContext + login = context parameter can not be null
Date Sun, 03 Feb 2013 12:43:45 GMT
I haven't tried state saving to client either. I learned long ago to use
server instead of client. :)

+1, I was looking forward to the fix, too, because I downloaded snapshot
(almost a day later) after Romain mentioned the following:

can you give a try with a fresh snapshot please ?(build it from sources or
wait next snapshot deployed tonight)

On Sun, Feb 3, 2013 at 7:24 AM, José Luis Cetina <>wrote:

> What about use the save state method in web.xml i didnt try to set client
> instead of server, when you use server a session is used and i guess the
> session is initialized in the first request.
> When i reported this you sayed this will be fixed, because with this error
> i couldnt run more than 1 webapp in the same ear both using a login method
> (request.login), i didnt have time to verify if this is already fixed.
> I will verify later today and let you know if it works.
> El 03/02/2013 06:10, "Howard W. Smith, Jr." <>
> escribió:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message