Hi everybody,
We're currently migrating to 4.5 (laugh)...
Our application has its own login mechanism, using a quite standard JEE login
servlet configured in our web.xml and connected to our corporate LDAP
infrastruture.
I'm losing my last hair since a couple of hours trying to understand how
Hi,
since there are some Magnolians developing on Mac OS X, I wonder
whether anyone has run into the same problem as two colleagues of
mine do.
When running Magnolia in Tomcat using Java 7u13, out every couple
(hundreds) of requests some requests from the b
Hi Jörg
We're having the exact same issues. Besides the aborted requests, I can also
manage to crash the JVM. This is why we still use Java 6 on our OS X
development machines.
I have a support ticket open on that matter and AFAIK Magnolia is on it.
Recently there was this discussion:
http://f
Hi Jörg,
I am developing on a Mac but am not using Java7. Indeed, it looks like Java7 on
Mac OS X has some issues, one of them mentioned also here
http://documentation.magnolia-cms.com/administration/certified-stack.html so
that, at least for the time being, it is recommended to keep using Java
Hi Federico and Andreas,
thanks for replying, at least we won't feel entirely alone with
that problem now ;-)
Concerning the aborted requests, I guess the only thing one can do
is to have wireshark running to diagnose them, and taking your
time
If I remember right, the last time I tried to capture the traffic for the
aborted requests I figured out that the connection gets closed on the server
side before anything came back..
There is probably no point in diagnosing the connections.. One should debug the
JVM, maybe we even find the nex
I am facing the same issue. Vishal did you get it resolved.
Thanks,
Ravi
--
Context is everything:
http://forum.magnolia-cms.com/forum/thread.html?threadId=7d18a1e6-44ab-4190-8acb-a06f417b3c33
For list details, see http://www.ma
Hi, Here is how we fixed ISSUE 1: We synched up all the users from
author instance to all public instances. It appeared that there were users
whose login information wasn't identical on author and public instances. For
ex: we had couple of users non-active on author instance while they were stil
