Enterprise Client Community

Hello community,

We had some difficulties with our application on Wildfly 8 Final. Our application is using CaptainCasa and maybe our solution is helpfull for others too.
Our problem was that with Wildfly RC1 everything works fine. With Wildfly Final, we got a session expired exception with the first sent request (a click on our "login" button).

With help from Mr. Müller, we where able to locate the problem: CaptainCasa uses the jsessionid appended in the URL, no cookies are used. Wildfly Final is using cookies for its session handling as default. Therefore the CaptainCasa Client gets no jsessionid at all.

To change this behaviour, you must change your web.xml and set the tracking-mode to URL.
Here is an example of what works for us:
<session-config>
<session-timeout>30</session-timeout>
<tracking-mode>URL</tracking-mode>
</session-config>

Greetings
Markus

Hello,

we are using wildfly and call our application with the following URL

"http: //IPAdress : PORT/webterminal/around.ccapplet"

After the wildfly is restarted and if the session expires the call of the URL is responding
404 - Not Found

So we have to call our application the first time with
" http: //IPAdress : PORT/webterminal "
after its loaded once the other URL-Call works.

Has anybody same problems with wildfly?

Best regards

Frank