Re: NPE on DefaultClientWindow.getWindowId after long period of inactivity

2014-03-09 Thread Thomas Frühbeck
just to follow up on this: after upgrade to WIldfly 8.0.0.Final the issue is not reproduceable. Thanks for your attention. Regards, Thomas 2014-02-23 22:39 GMT+01:00 Thomas Frühbeck : In fact I found the problem with an 8.0.0.CR1 version, and did not succeed in reproducing the issue by manipula

Re: NPE on DefaultClientWindow.getWindowId after long period of inactivity

2014-02-23 Thread Gerhard Petracek
hi thomas, if you have any issue with the url-handling, please provide details about it. regards, gerhard http://www.irian.at Your JSF/JavaEE powerhouse - JavaEE Consulting, Development and Courses in English and German Professional Support for Apache MyFaces 2014-02-23 22:39 GMT+01:00 Thom

Re: NPE on DefaultClientWindow.getWindowId after long period of inactivity

2014-02-23 Thread Thomas Frühbeck
In fact I found the problem with an 8.0.0.CR1 version, and did not succeed in reproducing the issue by manipulating the windowId cookie. I have activated JSF 2.2 WindowId in web.xml to work around a bug in url handling of DS 0.6 snapshot some time ago, but I cannot imagine, that this has any rel

Re: NPE on DefaultClientWindow.getWindowId after long period of inactivity

2014-02-23 Thread John D. Ament
H You mention WildFly 8 Final Snapshot. Are you using one of their prerelease snapshot builds or the final one? Can you try on the final? On Sun, Feb 23, 2014 at 1:44 PM, Mark Struberg wrote: > Well, from a CDI perspective this is pretty clear. We take whatever the > Session is. Regardles

Re: NPE on DefaultClientWindow.getWindowId after long period of inactivity

2014-02-23 Thread Mark Struberg
Well, from a CDI perspective this is pretty clear. We take whatever the Session is. Regardless if this is an existing one or a new one. Seems to be a WildFly issue. I'm sure the guys over there can fix this. LieGrue, strub On Sunday, 23 February 2014, 19:37, Thomas Frühbeck wrote: Yes, d

Re: NPE on DefaultClientWindow.getWindowId after long period of inactivity

2014-02-23 Thread Thomas Frühbeck
Yes, definitely, in my case it has been about a day. In my opinion the SessionScoped DefaultClientWindowConfig is instantiated by the web layer, but the Wildfly session storage tries to resurrect it from passivation, because an ID is provided. Seems debatable, who's problem it is, but the effec

Re: NPE on DefaultClientWindow.getWindowId after long period of inactivity

2014-02-23 Thread John D. Ament
Is the long period of inactivity longer than your session timeout as defined in your web.xml? On Sun, Feb 23, 2014 at 11:49 AM, Thomas Frühbeck wrote: > Hi, > > I am currently using DeltaSpike 0.6 Snapshot some days old.. working on > Wildfly 8.0.0.Final Snapshot. > > I get an NPE in DefaultClien

NPE on DefaultClientWindow.getWindowId after long period of inactivity

2014-02-23 Thread Thomas Frühbeck
Hi, I am currently using DeltaSpike 0.6 Snapshot some days old.. working on Wildfly 8.0.0.Final Snapshot. I get an NPE in DefaultClientWindow.getWindowId() after long period of inactivity. In this situation the application is _totally inaccessible_ from this client instance, the only remedy