Which file should I edit to set the system property
java.security.auth.login.config so that LoginContext knows where to look for
a given login configuration?
--
View this message in context:
http://www.nabble.com/system-property-for-login-configuration-file-tp21450978s134p21450978.html
Sent from
I was always thinking that shall we have a better way to handle all the
available setting provided by the third-party modules? As we all know,
usually, all the GBeans only delegate those important and popular settings,
it is impossible for us to allow all the configurations could be done via
GBean.
Thanks Ivan! I've examined the geronimo-tomcat-2.0.1.xsd and
geronimo-tomcat-config-1.0.xsd, and am pretty sure many configurations are
not available, like antiJARLocking, unloadDelay, etc. I understand that many
of these settings might not work in Geronimo. Just try to see how we can
play with the
Basically, Geronimo have created a GBean for each element in the server.xml,
which means we should configure those settings via GBeans in the config.xml.
But so far, I am sure the existing GBeans have not covered all the settings
that tomcat provides. e.g. for server.xml, we have host gbean for the
Hi
I'm try to get WADI clustering to work with Geronimo 2.2-SNAPSHOT and
Jetty6. In front of two Geronimo instances I have a HAProxy instance that
currently just distributes requests evenly among the two nodes using a
round-robin algorithm. This works fine; sessions are replicated and when if
I ki
On Jan 13, 2009, at 6:47 AM, eros wrote:
I wrote a small script to manually start geronimo that (I think)
doesn't
compromise security too much:
#!/bin/bash
mv /dev/random /dev/random.bak
ln -s /dev/urandom /dev/random
/etc/init.d/geronimo start
echo "Waiting for tomcat to start"
sleep 10
On Jan 13, 2009, at 5:49 AM, eros wrote:
I think you have a problem with system entropy that's causing a
problem generating pseudo-random numbers.
While the server startup was stalled, I sent a kill -3 signal to the
server process (think I mentioned doing this earlier in this thread)
and g
I wrote a small script to manually start geronimo that (I think) doesn't
compromise security too much:
#!/bin/bash
mv /dev/random /dev/random.bak
ln -s /dev/urandom /dev/random
/etc/init.d/geronimo start
echo "Waiting for tomcat to start"
sleep 10
rm /dev/random
mv /dev/random.bak /dev/random
> I think you have a problem with system entropy that's causing a
> problem generating pseudo-random numbers.
>
> While the server startup was stalled, I sent a kill -3 signal to the
> server process (think I mentioned doing this earlier in this thread)
> and got the following thread stac
Probably this is not related, but on z/OS it sometimes happens that the
/dev/urandom device hangs (read < /dev/urandom does not return) and Tomcat
within Geronimo will not start.
My workaround was to hack the org.apache.catalina.session.ManagerBase class
file and change urandom to xrandom. I think
10 matches
Mail list logo
