To answer one part of your question:
Additionally the application is started as root and for the app tier we
use user and group to change the user. When we try to do the same
thing in the web-loadbalancer tier the application fails to start. Is
this normal/to be expected? Is it safe for the
Thanks Mattias
I thought that the idea was that resin started as root in order to
permit binding to the protected ports 1024
and subsequently switched to run as a different user.
Our current setup with resin2 and a single server seems to do that.
Thank you for taking the time to respond.
Can
At the same time as upgrading to Resin 4 we are upgrading to Oracle 11gR2.
Starting/stopping resin was very non-deterministic seeming to hang
sometimes during application startup with references to connection
timeouts in the error logs.
SQLRecoverableException: IO Error: Connection reset
The
On Wed, Sep 28, 2011 at 10:13, Alan Wright
alan.wri...@athenesystems.com wrote:
The solution was to add the following to resin.xml
Add the following what?
FC
___
resin-interest mailing list
resin-interest@caucho.com
At the same time as upgrading to Resin 4 we are upgrading to Oracle 11gR2.
Starting/stopping resin was very non-deterministic seeming to hang
sometimes during application startup with references to connection
timeouts in the error logs.
SQLRecoverableException: IO Error: Connection reset
The
Good to know Alan, thanks.
Who would have thought servers accessing databases might be located in
dedicated machines? Way to go, Oracle! :D
S!
D.
El 28/09/2011 16:19, Alan Wright escribió:
At the same time as upgrading to Resin 4 we are upgrading to Oracle 11gR2.
Starting/stopping resin
Hi Alan,
Given that Resin by default creates work and tmp directories in the
WEB-INF directory of each application, it might be risky to 3 instances
of the application fiddling with those files, so it might be better to
separate those directories per instance.
I haven't done so with 4.X so I
On 09/28/2011 06:03 AM, Alan Wright wrote:
Thanks Mattias
I thought that the idea was that resin started as root in order to
permit binding to the protected ports1024
and subsequently switched to run as a different user.
Our current setup with resin2 and a single server seems to do that.
On 09/25/2011 09:45 AM, Stargazer wrote:
We have a Resin powered JEE app and are expanding it to work with
Android. One of the cool things on Android is you know the user is
logged into a Google account. With the Google App Engine, you can do
more that just authenticate since they provide all
On 09/28/2011 04:47 AM, Alan Wright wrote:
Hi
I am migrating from resin 2 to 4.0.22 and have a single host configured
with a web-loadbalance tier (1 server) and an application tier (3 servers).
We have elected to do this for resilience and also to make adding hosts
at a later date easier to
10 matches
Mail list logo
