On Aug 28, 2007, at 11:01 AM, Leland, Robert wrote:
> It could be designed so that it becomes a single service, with only
> one
> instance of the process running no matter how many instances of
> resin are running.
It does that now.
-- Scott
__
You can set the watchdog-port for each server you start up, whether you
use a single resin.conf for a cluster of servers on the same machine, or
multiple resin.confs. 6600 is just the default watchdog port. that is
how you start up multiple resin instances on the same machine.
as for the bug,
I have been googling for several days on this. I agree, it is a
probably a problem on the machine itself. I am just trying to find
clues as to how to find it. I am using the latest java machine:
java -version puts out:
java version "1.6.0_02"
Java(TM) SE Runtime Environment (build 1.6.0_02
> I don't follow. Resin is binding the Watchdog process
> to 127.0.0.1:6600 right?
>
> And all that I am really concerned with is... how
> would/should I start multiple Resin
> servers on the same machine? How will this work if
> each is going to try to bind to 127.
It sounds like the Watch Dog service is bound too closely to the concept
of the resin config file.
It could be designed so that it becomes a single service, with only one
instance of the
process running no matter how many instances of resin are running. So
this seems like a
Design/implementation is
Scott Ferguson wrote:
> On Aug 24, 2007, at 11:23 AM, Vic Simkus wrote:
>
>
>> Hello
>>
>> Sorry for the duplicate if it has been asked before, but I could find
>> anything conclusive...
>>
>> How do I turn off transaction autocommits in Resin? I'm running Resin
>> 3.1.2 against a PosgreSQL dat
Scott Ferguson wrote:
On Aug 28, 2007, at 9:45 AM, Eric Kreiser wrote:
That's interesting. Thanks for finding this.
The Watchdog does bind to port localhost:6600. That's how the "stop"
command works and how the Watchdog can manage multiple Resin JVMs
with a single watchdog process.
On Aug 28, 2007, at 9:45 AM, Eric Kreiser wrote:
That's interesting. Thanks for finding this.
The Watchdog does bind to port localhost:6600. That's how the "stop"
command works and how the Watchdog can manage multiple Resin JVMs
with a single watchdog process.
-- Scott
Is this a bug? or g
Scott Ferguson wrote:
On Aug 28, 2007, at 8:49 AM, Mike Wynholds wrote:
This is an old bug report, but it sounds like it might be the cause:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6206527
Centos is sort of a redhat derivative, right? anyway, assuming you
are
using JDK 5, y
On Aug 28, 2007, at 8:49 AM, Mike Wynholds wrote:
> This is an old bug report, but it sounds like it might be the cause:
> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6206527
>
> Centos is sort of a redhat derivative, right? anyway, assuming you
> are
> using JDK 5, you could try either
This is an old bug report, but it sounds like it might be the cause:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6206527
Centos is sort of a redhat derivative, right? anyway, assuming you are
using JDK 5, you could try either a) upgrading to JDK 6 or b) disable
IPv6.
" A workaround for Re
Here is my netstat dump. I am running in a console as root when I try
to start resin up.
I can start Jetty, but I cannot start Glassfish as well. I get a
similiar error. I thought maybe it had to with resolving its domain
name as it is behind a firewall which is doing NAT, but I think I ha
12 matches
Mail list logo
