if you get a 500 error, then it is definitely logged somewhere, you don't
need to enable any debug flags. Look in:
standard error and standard out (console or redirected to a file)
global-application.log
Your app's application.log
On Tue, 14 Aug 2001, Curt Smith wrote:
> I searched the orion doc for this argument as well as the recently offered
>
> -out <file> -err <file>
>
> Is there a place where these orion cmd line args are at least listed ?
>
> The -verbosity 10 is the type of debug logging switches that would be
> very helpful in seeing what's going on.
>
> BTW, my area of hair pullin has to do with
>
> ... getRequestDispatcher ( "somePath.jsp" ).forward (request, response);
>
> And getting no logging that the somePath.jsp was not found, just a 500 error.
> Very frustrating to debug other than using monkey testing; try all combinations.
>
> :))
>
> curt
>
>
> >>> Jason Westra <[EMAIL PROTECTED]> 08/14/01 09:34AM >>>
> Hi Tom,
>
> Try turning "-verbosity 10" in the java -jar orion.jar commandline.
> Orion console output should say something like "Binding xyxEJB to
> xyzJNDIName" and indicating the EJB(s) is deployed.
>
> Jason
>
> --- Tom Jordan <[EMAIL PROTECTED]> wrote:
> > Is there anyway to determine that a set of EJBs that are in an ear
> > have been
> > deployed onto that server. I just want to know if an ear that was
> > suppose to
> > autodeploy has infact deployed.
> >
> > Thanks
> > Tom
> >
> > _________________________________________________________________
> > Get your FREE download of MSN Explorer at
> > http://explorer.msn.com/intl.asp
> >
> >
> >
> >
>
>
> __________________________________________________
> Do You Yahoo!?
> Make international calls for as low as $.04/minute with Yahoo! Messenger
> http://phonecard.yahoo.com/
>
>
>
>
