Buy a nice big Solaris and co-locate all the modules/databases/webserver/appserver on that one box so propagation delay is at a minimum or at least eliminate prop delay as the cause
Martin
> From: reza.rahman_at_oracle.com
> Date: Fri, 12 Jun 2015 17:32:42 -0400
> To: users_at_glassfish.java.net
> Subject: [gf-users] Re: @Schedule job being killed
>
> Understood. Let's hope someone can step in to help. Unfortunately I am not sure what to tell you. If I were you I would try remote debugging the code that the exception might be coming from if all other easier debugging possibilities are exhausted.
>
> Sent from my iPhone
>
> > On Jun 12, 2015, at 5:24 PM, Will Hartung <willh_at_mirthcorp.com> wrote:
> >
> >> On Fri, Jun 12, 2015 at 1:41 PM, Reza Rahman <reza.rahman_at_oracle.com> wrote:
> >> If the engineers don't have the time to respond at the moment, I suggest trying to enter an easily reproducible bug report.
> >
> > Hey Raza,
> >
> > That would be difficult.
> >
> > I mean, the job is pretty basic, but this happens rarely, so it's not
> > reliably reproducible.
> >
> > But thank you for the quick feedback,
> >
> > --
> > This message, and any documents attached hereto, may contain confidential
> > or proprietary information intended only for the use of the addressee(s)
> > named above or may contain information that is legally privileged. If you
> > are not the intended addressee, or the person responsible for delivering it
> > to the intended addressee, you are hereby notified that reading,
> > disseminating, distributing or copying this message is strictly prohibited.
> > If you have received this message by mistake, please immediately notify us
> > by replying to the message and delete the original message and any copies
> > immediately thereafter. Thank you for your cooperation.