You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by Thomas Frühbeck <fr...@aon.at> on 2014/02/23 17:49:33 UTC
NPE on DefaultClientWindow.getWindowId after long period of inactivity
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 is to delete the session cookies and
reset the URL:
2014-02-23 16:59:13,319 ERROR [io.undertow.request] (default task-36)
Servlet request failed HttpServerExchange{ GET
/mssms2/faces/csms/groupManagement.xhtml}: java.lang.NullPoi
nterException
at
org.jboss.weld.context.beanstore.http.AbstractSessionBeanStore.getLockStore(AbstractSessionBeanStore.java:113)
[weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
at
org.jboss.weld.context.beanstore.AttributeBeanStore.lock(AttributeBeanStore.java:210)
[weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
at
org.jboss.weld.context.AbstractContext.get(AbstractContext.java:88)
[weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
at
org.jboss.weld.context.PassivatingContextWrapper$AbstractPassivatingContextWrapper.get(PassivatingContextWrapper.java:76)
[weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:
53]
at
org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:98)
[weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
at
org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:78)
[weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
at
org.apache.deltaspike.jsf.spi.scope.window.DefaultClientWindowConfig$Proxy$_$$_WeldClientProxy.getClientWindowRenderMode(Unknown
Source) [deltaspike-jsf-module-api-0.
6-SNAPSHOT.jar:0.6-SNAPSHOT]
at
org.apache.deltaspike.jsf.impl.scope.window.DefaultClientWindow.getWindowId(DefaultClientWindow.java:119)
[deltaspike-jsf-module-impl-0.6-SNAPSHOT.jar:0.6-SNAPSHOT]
at
org.apache.deltaspike.jsf.impl.scope.window.DefaultClientWindow$Proxy$_$$_WeldClientProxy.getWindowId(Unknown
Source) [deltaspike-jsf-module-impl-0.6-SNAPSHOT.jar:0.6
-SNAPSHOT]
at
org.apache.deltaspike.jsf.impl.listener.request.DeltaSpikeLifecycleWrapper.execute(DeltaSpikeLifecycleWrapper.java:78)
[deltaspike-jsf-module-impl-0.6-SNAPSHOT.jar:0.
6-SNAPSHOT]
Re: NPE on DefaultClientWindow.getWindowId after long period of inactivity
Posted by Thomas Frühbeck <fr...@aon.at>.
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 <fr...@aon.at>:
>> 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.
>>
Re: NPE on DefaultClientWindow.getWindowId after long period of inactivity
Posted by Gerhard Petracek <ge...@gmail.com>.
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 Thomas Frühbeck <fr...@aon.at>:
> 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 relevance in this case, because the exception happens when DS
> DefaultClientWindow tries to detect the WindowId handling config..
>
> <param-name>javax.faces.CLIENT_WINDOW_MODE</param-name>
> <param-value>url</param-value>
>
> Unfortunately I yet do not have any clue, how to reproduce the problem
> else than waiting _very_(??) long :-/
> Not really sure, how URL jfwid and cookies work together..
>
> But anycase I will upgrade to 8.0.0.Final ASAP - or 8.0.1.Final, or... :-)
>
> Thomas
>
> Am 23.02.2014 22:02, schrieb John D. Ament:
>
> Hmmmm
>>
>> 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 <st...@yahoo.de> wrote:
>>
>>> 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 <fr...@aon.at>
>>> wrote:
>>>
>>> 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 effect is painful :-/
>>>>
>>>>
>>>> Am 23.02.2014 19:28, schrieb 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 <fr...@aon.at>
>>>>> 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 DefaultClientWindow.getWindowId() after long period
>>>>>> of
>>>>>> inactivity.
>>>>>> In this situation the application is _totally inaccessible_ from this
>>>>>> client
>>>>>> instance, the only remedy is to delete the session cookies and reset
>>>>>> the
>>>>>> URL:
>>>>>>
>>>>>> 2014-02-23 16:59:13,319 ERROR [io.undertow.request] (default task-36)
>>>>>> Servlet request failed HttpServerExchange{ GET
>>>>>> /mssms2/faces/csms/groupManagement.xhtml}: java.lang.NullPoi
>>>>>> nterException
>>>>>> at
>>>>>> org.jboss.weld.context.beanstore.http.AbstractSessionBeanStore.
>>>>>> getLockStore(AbstractSessionBeanStore.java:113)
>>>>>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
>>>>>> at
>>>>>> org.jboss.weld.context.beanstore.AttributeBeanStore.
>>>>>> lock(AttributeBeanStore.java:210)
>>>>>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
>>>>>> at
>>>>>> org.jboss.weld.context.AbstractContext.get(AbstractContext.java:88)
>>>>>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
>>>>>> at
>>>>>> org.jboss.weld.context.PassivatingContextWrapper$
>>>>>> AbstractPassivatingContextWrapper.get(PassivatingContextWrapper.
>>>>>> java:76)
>>>>>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:
>>>>>> 53]
>>>>>> at
>>>>>> org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(
>>>>>> ContextBeanInstance.java:98)
>>>>>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
>>>>>> at
>>>>>> org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(
>>>>>> ProxyMethodHandler.java:78)
>>>>>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
>>>>>> at
>>>>>> org.apache.deltaspike.jsf.spi.scope.window.DefaultClientWindowConfig$
>>>>>> Proxy$_$$_WeldClientProxy.getClientWindowRenderMode(Unknown
>>>>>> Source) [deltaspike-jsf-module-api-0.
>>>>>> 6-SNAPSHOT.jar:0.6-SNAPSHOT]
>>>>>> at
>>>>>> org.apache.deltaspike.jsf.impl.scope.window.DefaultClientWindow.
>>>>>> getWindowId(DefaultClientWindow.java:119)
>>>>>> [deltaspike-jsf-module-impl-0.6-SNAPSHOT.jar:0.6-SNAPSHOT]
>>>>>> at
>>>>>> org.apache.deltaspike.jsf.impl.scope.window.
>>>>>> DefaultClientWindow$Proxy$_$$_WeldClientProxy.getWindowId(Unknown
>>>>>> Source) [deltaspike-jsf-module-impl-0.6-SNAPSHOT.jar:0.6
>>>>>> -SNAPSHOT]
>>>>>> at
>>>>>> org.apache.deltaspike.jsf.impl.listener.request.
>>>>>> DeltaSpikeLifecycleWrapper.execute(DeltaSpikeLifecycleWrapper.
>>>>>> java:78)
>>>>>> [deltaspike-jsf-module-impl-0.6-SNAPSHOT.jar:0.
>>>>>> 6-SNAPSHOT]
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>>
>>>>
>
Re: NPE on DefaultClientWindow.getWindowId after long period of inactivity
Posted by Thomas Frühbeck <fr...@aon.at>.
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 relevance in this case, because the exception happens when
DS DefaultClientWindow tries to detect the WindowId handling config..
<param-name>javax.faces.CLIENT_WINDOW_MODE</param-name>
<param-value>url</param-value>
Unfortunately I yet do not have any clue, how to reproduce the problem
else than waiting _very_(??) long :-/
Not really sure, how URL jfwid and cookies work together..
But anycase I will upgrade to 8.0.0.Final ASAP - or 8.0.1.Final, or... :-)
Thomas
Am 23.02.2014 22:02, schrieb John D. Ament:
> Hmmmm
>
> 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 <st...@yahoo.de> wrote:
>> 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 <fr...@aon.at> wrote:
>>
>> 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 effect is painful :-/
>>>
>>>
>>> Am 23.02.2014 19:28, schrieb 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 <fr...@aon.at> 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 DefaultClientWindow.getWindowId() after long period of
>>>>> inactivity.
>>>>> In this situation the application is _totally inaccessible_ from this client
>>>>> instance, the only remedy is to delete the session cookies and reset the
>>>>> URL:
>>>>>
>>>>> 2014-02-23 16:59:13,319 ERROR [io.undertow.request] (default task-36)
>>>>> Servlet request failed HttpServerExchange{ GET
>>>>> /mssms2/faces/csms/groupManagement.xhtml}: java.lang.NullPoi
>>>>> nterException
>>>>> at
>>>>> org.jboss.weld.context.beanstore.http.AbstractSessionBeanStore.getLockStore(AbstractSessionBeanStore.java:113)
>>>>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
>>>>> at
>>>>> org.jboss.weld.context.beanstore.AttributeBeanStore.lock(AttributeBeanStore.java:210)
>>>>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
>>>>> at
>>>>> org.jboss.weld.context.AbstractContext.get(AbstractContext.java:88)
>>>>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
>>>>> at
>>>>> org.jboss.weld.context.PassivatingContextWrapper$AbstractPassivatingContextWrapper.get(PassivatingContextWrapper.java:76)
>>>>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:
>>>>> 53]
>>>>> at
>>>>> org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:98)
>>>>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
>>>>> at
>>>>> org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:78)
>>>>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
>>>>> at
>>>>> org.apache.deltaspike.jsf.spi.scope.window.DefaultClientWindowConfig$Proxy$_$$_WeldClientProxy.getClientWindowRenderMode(Unknown
>>>>> Source) [deltaspike-jsf-module-api-0.
>>>>> 6-SNAPSHOT.jar:0.6-SNAPSHOT]
>>>>> at
>>>>> org.apache.deltaspike.jsf.impl.scope.window.DefaultClientWindow.getWindowId(DefaultClientWindow.java:119)
>>>>> [deltaspike-jsf-module-impl-0.6-SNAPSHOT.jar:0.6-SNAPSHOT]
>>>>> at
>>>>> org.apache.deltaspike.jsf.impl.scope.window.DefaultClientWindow$Proxy$_$$_WeldClientProxy.getWindowId(Unknown
>>>>> Source) [deltaspike-jsf-module-impl-0.6-SNAPSHOT.jar:0.6
>>>>> -SNAPSHOT]
>>>>> at
>>>>> org.apache.deltaspike.jsf.impl.listener.request.DeltaSpikeLifecycleWrapper.execute(DeltaSpikeLifecycleWrapper.java:78)
>>>>> [deltaspike-jsf-module-impl-0.6-SNAPSHOT.jar:0.
>>>>> 6-SNAPSHOT]
>>>>>
>>>>>
>>>>>
>>>
>>>
>>>
Re: NPE on DefaultClientWindow.getWindowId after long period of inactivity
Posted by "John D. Ament" <jo...@gmail.com>.
Hmmmm
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 <st...@yahoo.de> wrote:
> 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 <fr...@aon.at> wrote:
>
> 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 effect is painful :-/
>>
>>
>>Am 23.02.2014 19:28, schrieb 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 <fr...@aon.at> 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 DefaultClientWindow.getWindowId() after long period of
>>>> inactivity.
>>>> In this situation the application is _totally inaccessible_ from this client
>>>> instance, the only remedy is to delete the session cookies and reset the
>>>> URL:
>>>>
>>>> 2014-02-23 16:59:13,319 ERROR [io.undertow.request] (default task-36)
>>>> Servlet request failed HttpServerExchange{ GET
>>>> /mssms2/faces/csms/groupManagement.xhtml}: java.lang.NullPoi
>>>> nterException
>>>> at
>>>> org.jboss.weld.context.beanstore.http.AbstractSessionBeanStore.getLockStore(AbstractSessionBeanStore.java:113)
>>>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
>>>> at
>>>> org.jboss.weld.context.beanstore.AttributeBeanStore.lock(AttributeBeanStore.java:210)
>>>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
>>>> at
>>>> org.jboss.weld.context.AbstractContext.get(AbstractContext.java:88)
>>>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
>>>> at
>>>> org.jboss.weld.context.PassivatingContextWrapper$AbstractPassivatingContextWrapper.get(PassivatingContextWrapper.java:76)
>>>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:
>>>> 53]
>>>> at
>>>> org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:98)
>>>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
>>>> at
>>>> org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:78)
>>>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
>>>> at
>>>> org.apache.deltaspike.jsf.spi.scope.window.DefaultClientWindowConfig$Proxy$_$$_WeldClientProxy.getClientWindowRenderMode(Unknown
>>>> Source) [deltaspike-jsf-module-api-0.
>>>> 6-SNAPSHOT.jar:0.6-SNAPSHOT]
>>>> at
>>>> org.apache.deltaspike.jsf.impl.scope.window.DefaultClientWindow.getWindowId(DefaultClientWindow.java:119)
>>>> [deltaspike-jsf-module-impl-0.6-SNAPSHOT.jar:0.6-SNAPSHOT]
>>>> at
>>>> org.apache.deltaspike.jsf.impl.scope.window.DefaultClientWindow$Proxy$_$$_WeldClientProxy.getWindowId(Unknown
>>>> Source) [deltaspike-jsf-module-impl-0.6-SNAPSHOT.jar:0.6
>>>> -SNAPSHOT]
>>>> at
>>>> org.apache.deltaspike.jsf.impl.listener.request.DeltaSpikeLifecycleWrapper.execute(DeltaSpikeLifecycleWrapper.java:78)
>>>> [deltaspike-jsf-module-impl-0.6-SNAPSHOT.jar:0.
>>>> 6-SNAPSHOT]
>>>>
>>>>
>>>>
>>
>>
>>
>>
Re: NPE on DefaultClientWindow.getWindowId after long period of inactivity
Posted by Mark Struberg <st...@yahoo.de>.
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 <fr...@aon.at> wrote:
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 effect is painful :-/
>
>
>Am 23.02.2014 19:28, schrieb 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 <fr...@aon.at> 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 DefaultClientWindow.getWindowId() after long period of
>>> inactivity.
>>> In this situation the application is _totally inaccessible_ from this client
>>> instance, the only remedy is to delete the session cookies and reset the
>>> URL:
>>>
>>> 2014-02-23 16:59:13,319 ERROR [io.undertow.request] (default task-36)
>>> Servlet request failed HttpServerExchange{ GET
>>> /mssms2/faces/csms/groupManagement.xhtml}: java.lang.NullPoi
>>> nterException
>>> at
>>> org.jboss.weld.context.beanstore.http.AbstractSessionBeanStore.getLockStore(AbstractSessionBeanStore.java:113)
>>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
>>> at
>>> org.jboss.weld.context.beanstore.AttributeBeanStore.lock(AttributeBeanStore.java:210)
>>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
>>> at
>>> org.jboss.weld.context.AbstractContext.get(AbstractContext.java:88)
>>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
>>> at
>>> org.jboss.weld.context.PassivatingContextWrapper$AbstractPassivatingContextWrapper.get(PassivatingContextWrapper.java:76)
>>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:
>>> 53]
>>> at
>>> org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:98)
>>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
>>> at
>>> org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:78)
>>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
>>> at
>>> org.apache.deltaspike.jsf.spi.scope.window.DefaultClientWindowConfig$Proxy$_$$_WeldClientProxy.getClientWindowRenderMode(Unknown
>>> Source) [deltaspike-jsf-module-api-0.
>>> 6-SNAPSHOT.jar:0.6-SNAPSHOT]
>>> at
>>> org.apache.deltaspike.jsf.impl.scope.window.DefaultClientWindow.getWindowId(DefaultClientWindow.java:119)
>>> [deltaspike-jsf-module-impl-0.6-SNAPSHOT.jar:0.6-SNAPSHOT]
>>> at
>>> org.apache.deltaspike.jsf.impl.scope.window.DefaultClientWindow$Proxy$_$$_WeldClientProxy.getWindowId(Unknown
>>> Source) [deltaspike-jsf-module-impl-0.6-SNAPSHOT.jar:0.6
>>> -SNAPSHOT]
>>> at
>>> org.apache.deltaspike.jsf.impl.listener.request.DeltaSpikeLifecycleWrapper.execute(DeltaSpikeLifecycleWrapper.java:78)
>>> [deltaspike-jsf-module-impl-0.6-SNAPSHOT.jar:0.
>>> 6-SNAPSHOT]
>>>
>>>
>>>
>
>
>
>
Re: NPE on DefaultClientWindow.getWindowId after long period of inactivity
Posted by Thomas Frühbeck <fr...@aon.at>.
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 effect is painful :-/
Am 23.02.2014 19:28, schrieb 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 <fr...@aon.at> 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 DefaultClientWindow.getWindowId() after long period of
>> inactivity.
>> In this situation the application is _totally inaccessible_ from this client
>> instance, the only remedy is to delete the session cookies and reset the
>> URL:
>>
>> 2014-02-23 16:59:13,319 ERROR [io.undertow.request] (default task-36)
>> Servlet request failed HttpServerExchange{ GET
>> /mssms2/faces/csms/groupManagement.xhtml}: java.lang.NullPoi
>> nterException
>> at
>> org.jboss.weld.context.beanstore.http.AbstractSessionBeanStore.getLockStore(AbstractSessionBeanStore.java:113)
>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
>> at
>> org.jboss.weld.context.beanstore.AttributeBeanStore.lock(AttributeBeanStore.java:210)
>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
>> at
>> org.jboss.weld.context.AbstractContext.get(AbstractContext.java:88)
>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
>> at
>> org.jboss.weld.context.PassivatingContextWrapper$AbstractPassivatingContextWrapper.get(PassivatingContextWrapper.java:76)
>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:
>> 53]
>> at
>> org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:98)
>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
>> at
>> org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:78)
>> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
>> at
>> org.apache.deltaspike.jsf.spi.scope.window.DefaultClientWindowConfig$Proxy$_$$_WeldClientProxy.getClientWindowRenderMode(Unknown
>> Source) [deltaspike-jsf-module-api-0.
>> 6-SNAPSHOT.jar:0.6-SNAPSHOT]
>> at
>> org.apache.deltaspike.jsf.impl.scope.window.DefaultClientWindow.getWindowId(DefaultClientWindow.java:119)
>> [deltaspike-jsf-module-impl-0.6-SNAPSHOT.jar:0.6-SNAPSHOT]
>> at
>> org.apache.deltaspike.jsf.impl.scope.window.DefaultClientWindow$Proxy$_$$_WeldClientProxy.getWindowId(Unknown
>> Source) [deltaspike-jsf-module-impl-0.6-SNAPSHOT.jar:0.6
>> -SNAPSHOT]
>> at
>> org.apache.deltaspike.jsf.impl.listener.request.DeltaSpikeLifecycleWrapper.execute(DeltaSpikeLifecycleWrapper.java:78)
>> [deltaspike-jsf-module-impl-0.6-SNAPSHOT.jar:0.
>> 6-SNAPSHOT]
>>
>>
>>
Re: NPE on DefaultClientWindow.getWindowId after long period of inactivity
Posted by "John D. Ament" <jo...@gmail.com>.
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 <fr...@aon.at> 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 DefaultClientWindow.getWindowId() after long period of
> inactivity.
> In this situation the application is _totally inaccessible_ from this client
> instance, the only remedy is to delete the session cookies and reset the
> URL:
>
> 2014-02-23 16:59:13,319 ERROR [io.undertow.request] (default task-36)
> Servlet request failed HttpServerExchange{ GET
> /mssms2/faces/csms/groupManagement.xhtml}: java.lang.NullPoi
> nterException
> at
> org.jboss.weld.context.beanstore.http.AbstractSessionBeanStore.getLockStore(AbstractSessionBeanStore.java:113)
> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
> at
> org.jboss.weld.context.beanstore.AttributeBeanStore.lock(AttributeBeanStore.java:210)
> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
> at
> org.jboss.weld.context.AbstractContext.get(AbstractContext.java:88)
> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
> at
> org.jboss.weld.context.PassivatingContextWrapper$AbstractPassivatingContextWrapper.get(PassivatingContextWrapper.java:76)
> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:
> 53]
> at
> org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:98)
> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
> at
> org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:78)
> [weld-core-impl-2.1.0.CR1.jar:2013-09-26 16:53]
> at
> org.apache.deltaspike.jsf.spi.scope.window.DefaultClientWindowConfig$Proxy$_$$_WeldClientProxy.getClientWindowRenderMode(Unknown
> Source) [deltaspike-jsf-module-api-0.
> 6-SNAPSHOT.jar:0.6-SNAPSHOT]
> at
> org.apache.deltaspike.jsf.impl.scope.window.DefaultClientWindow.getWindowId(DefaultClientWindow.java:119)
> [deltaspike-jsf-module-impl-0.6-SNAPSHOT.jar:0.6-SNAPSHOT]
> at
> org.apache.deltaspike.jsf.impl.scope.window.DefaultClientWindow$Proxy$_$$_WeldClientProxy.getWindowId(Unknown
> Source) [deltaspike-jsf-module-impl-0.6-SNAPSHOT.jar:0.6
> -SNAPSHOT]
> at
> org.apache.deltaspike.jsf.impl.listener.request.DeltaSpikeLifecycleWrapper.execute(DeltaSpikeLifecycleWrapper.java:78)
> [deltaspike-jsf-module-impl-0.6-SNAPSHOT.jar:0.
> 6-SNAPSHOT]
>
>
>