No luck with finding the source of this problem, startup seems fine now and
nothing strange in logs. Just the ajax requests fail, whereas requests that
initiate page (number) changes are fine.
I don't know the Resful spec at all so cannot test the failing actions that
way for comparison.
On Tue,
I'll try another hosting provider
On Tue, Nov 10, 2015 at 2:12 PM, Stephen Cameron wrote:
> No luck with finding the source of this problem, startup seems fine now
> and nothing strange in logs. Just the ajax requests fail, whereas requests
> that initiate page
Hi,
Initially I thought that the load balancers in front of Tomcat are not
configured with sticky sessions support. This is something normal for
services like Google AppEngine, Heroku, and it seems Google Compute Cloud
(I'm not sure whether GCC is a completely new service or just the new name
of
Sorry, here is an error in catalina.out
23:03:39,587 [IsisLogOnExceptionFilter ajp-apr-8009-exec-17 ERROR] Request
caused org.apache.catalina.connector.ClientAbortException:
Hi all,
I just installed my Isis app on Google Compute Cloud as a test system but
have a problem with it in that many menu options are not working.
Specifically those are actions that would require parameters and hence a
pop-up window. So I am thinking these involve AJAX calls from Wicket to the