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.
The text was updated successfully, but these errors were encountered:
Thinking further about this, and browsing through SP11 code, I notice there is practically no way to define clientStateTimeout with such a value that would set clientStateTimeoutEnabled to false. This seems incorrect.
The constructor in
WebConfiguration
for theClientStateTimeout
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
""
asLong
, 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.
The text was updated successfully, but these errors were encountered: