You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The constructor in WebConfiguration for the ClientStateTimeout value defines the default value as "".
The init() method of ClientSideStateHelper, however, contains the following:
So if the value in the web.xml is invalid, an attempt is made to read "" as Long, which in turn results in NumberFormatException.
The above behaviour is present in 2.3.9.SP03 (WildFly 18.0.0). The code for 2.3.9.SP11 seems like that as well but I haven't tested with that version.
Browsing further I realized that there is no way to define a value for clientStateTimeout such that there will be no timeout (similar to the behaviour if there is no value defined in web.xml). This also seems wrong - it would be good if one is able to explicitly disable the timeout.
The same issue is described also here: jboss/mojarra#78
The text was updated successfully, but these errors were encountered:
The constructor in
WebConfiguration
for theClientStateTimeout
value defines the default value as""
.The
init()
method ofClientSideStateHelper
, however, contains the following:So if the value in the web.xml is invalid, an attempt is made to read
""
asLong
, which in turn results inNumberFormatException
.The above behaviour is present in 2.3.9.SP03 (WildFly 18.0.0). The code for 2.3.9.SP11 seems like that as well but I haven't tested with that version.
Browsing further I realized that there is no way to define a value for clientStateTimeout such that there will be no timeout (similar to the behaviour if there is no value defined in web.xml). This also seems wrong - it would be good if one is able to explicitly disable the timeout.
The same issue is described also here:
jboss/mojarra#78
The text was updated successfully, but these errors were encountered: