-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Scott,
> As a workaround, you can disable the (or PingThread) until I
> figure out why that's happening.
as an idea, I have the following in resin.xm from an old default:
So the ping configuration is actually e
Jan Kriesten wrote:
> Hi Scott,
>
>
>> I've put up a new snapshot. On a restart, you should see additional
>> logging information in both the watchdog-manager.log and the
>> jvm-default.log that should help narrow this down.
>>
>
> the only new entry in the log on restart in the jvm-default
Hi Aaron,
> Out of curiosity do you have multiple instances of Resin (separate JVMs)
> running on that same virtual machine? If so do you use different ports
> for the watchdog on both instances? We had a similar situation and it
> was fixed by just running the watchdog on separate ports for
Out of curiosity do you have multiple instances of Resin (separate JVMs)
running on that same virtual machine? If so do you use different ports
for the watchdog on both instances? We had a similar situation and it
was fixed by just running the watchdog on separate ports for each
instance of R
Hi Wesley,
> Did your resin server have a busy traffic? Did u observed any memory
> leak or heap overflow?
neither nor.
Best regards, --- Jan.
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/res
Hi Jan,
Did your resin server have a busy traffic? Did u observed any memory
leak or heap overflow?
-Wesley
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
Hi Scott,
> I've put up a new snapshot. On a restart, you should see additional
> logging information in both the watchdog-manager.log and the
> jvm-default.log that should help narrow this down.
the only new entry in the log on restart in the jvm-default.log is this:
06:44:16.969] {main} ProRe
Jan Kriesten wrote:
> Hi Scott,
>
>
>> It's not simply the ping because the restart isn't happening here. I'm
>> working on improving the logging on both the Resin and Watchdog to get
>> better information about this.
>>
>
> that would be helpful. Funny thing is, it only happens on one of t
Jan Kriesten wrote:
> Hi Scott,
>
>
>> It's not simply the ping because the restart isn't happening here. I'm
>> working on improving the logging on both the Resin and Watchdog to get
>> better information about this.
>>
>
> that would be helpful. Funny thing is, it only happens on one of t
Hi Scott,
> It's not simply the ping because the restart isn't happening here. I'm
> working on improving the logging on both the Resin and Watchdog to get
> better information about this.
that would be helpful. Funny thing is, it only happens on one of the
machines. The configuration is the sam
Jan Kriesten wrote:
> Hi Scott,
>
> the snapshot hasn't solved the restart-problem on our server:
>
> Resin Professional 4.0.s100809 (built Mon, 09 Aug 2010 11:41:02 PDT)
> [07:19:42.671] {main} ProResin[id=] started in 91076ms
> [...]
> [07:50:33.998] {main} ProResin[id=] started in 77686ms
> [...
Hi Scott,
the snapshot hasn't solved the restart-problem on our server:
Resin Professional 4.0.s100809 (built Mon, 09 Aug 2010 11:41:02 PDT)
[07:19:42.671] {main} ProResin[id=] started in 91076ms
[...]
[07:50:33.998] {main} ProResin[id=] started in 77686ms
[...]
[08:21:38.785] {main} ProResin[id
Jan Kriesten wrote:
> Hi Scott,
>
>
>> I assume there's nothing in the jvm-default.log about why Resin's exiting?
>>
>
> no, nothing.
>
Hmm. Does the postmortem tab in the /resin-admin show any unusual memory
or thread behavior? Or any created hs_* files?
One of the things I want to do
Hi Scott,
> I assume there's nothing in the jvm-default.log about why Resin's exiting?
no, nothing.
Best regards, --- Jan.
___
resin-interest mailing list
resin-interest@caucho.com
http://maillist.caucho.com/mailman/listinfo/resin-interest
Jan Kriesten wrote:
> Hi Scott,
>
>
>> Still, since these are core fixes to critical timing-related
>> capabilities that are hard to test exhaustively, you may want to take
>> extra care in your own testing before deploying on 4.0.9.
>>
>
> at first, resin 4.0.9 looked fine. But now I see
Hi Scott,
> Still, since these are core fixes to critical timing-related
> capabilities that are hard to test exhaustively, you may want to take
> extra care in your own testing before deploying on 4.0.9.
at first, resin 4.0.9 looked fine. But now I see in the jvm-default.log
that resin is sta
You got any release notes for 4.0.9 yet?
On Jul 30, 2010, at 11:29:05, Scott Ferguson wrote:
> Just an important note on Resin 4.0.9.
>
> Most of the work for this release was related to low level improvements
> and fixes to core capabilities like the locking for distributed caching,
> replaci
Oh my god Scott, you rule it!
/**
* Returns the current environment container.
*/
public static InjectManager getCurrent(ClassLoader loader)
{
return _localContainer.get(loader);
}
finally the synchronized (_localContainer) was gone!
You have no idea how I suffered from the lo
Just an important note on Resin 4.0.9.
Most of the work for this release was related to low level improvements
and fixes to core capabilities like the locking for distributed caching,
replacing synchronization with atomic locks in the core thread
dispatching, improving the core alarm/timer func
19 matches
Mail list logo
