Hi Christian, thanks to your hint we managed to trace the behaviour and we found out that the DBA session was invalidated at each request (thus not passing the login). The point is that we were trying out different deployments on tomcat and Wildfly from the same browser in "rapid" succession and the two guys have a different opinion on how to express the context of the request (trailing / issue). This caused Wildfly, who seems to be much more susceptible, to always ignore the cookie containing two Jsessionids and recreate a new session at each request. Of course it has nothing to do with Basex but rather with an unfortunate situation in our testing setup. Still I thought to explain in order to track this down for possible future similar situations and to validate that Wildfly 10 perfectly runs BaseX indeed! ;-). Thanks for the pointer that helped us out! Best regards, Marco.
On 21/09/2017 00:43, Christian Grün wrote:
Hi Marco,
The additional redirection could indicate that the session variable could not be set, or is being lost again. Maybe you could do some tracing/debugging in the DBA function that checks if a user is logged in [1]?
Cheers, Christian
[1] https://github.com/BaseXdb/basex/blob/master/basex-api/src/main/webapp/dba/m...
On Wed, Sep 20, 2017 at 9:04 PM, Marco Lettere m.lettere@gmail.com wrote:
Hi all, We created an application web app based on the BaseX .WAR distribution.
If we deploy it under tomcat we can access all DBA related functionalities after the login prompt. If we try to do the same under WildFly 10, the application starts without errors but trying to access the DBA pages the browser is just bounced back to the login page. Please check the snippets at [1] and [2] to observe the behaviour reflected in the log files. After arriving to the final page one more request to login?path=databases is received. Is there anyone having experience with running BaseX under Jboss / Wildfly? Thanks a lot, Marco.