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,
>
> 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
> [...
There seems to still be a problem with singletons exposed as hessian
services. I can create a test project if necessary, but I'm seeing
this behavior in two separate applications:
1) Create a @Singleton bean
2) Give the bean a @Startup @PostConstruct method that initializes some data
3) Give the
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
