Jason, et. al.
You may want to use the admin console to change these logging levels.
If you do edit the domain.xml, be sure to keep a backup, since
unintentional edits can have pretty drastic repercussions.
That is triply true if you are hand-editing the domain.xml of a
production server.
vbk
Hong Zhang wrote:
> Hi, Jason
> What's the difference between your dev box and prod box? Are they
> using the same OS? If you undeploy the application, (restart server)
> and deploy it again, do you see the same problem? And do you have
> other applications deployed on the prod box for this Glassfish
> installation and they all running ok?
>
> Unfortunately, the stack trace in this case really doesn't tell us
> much (this is one of areas we want to improve in 9.1). I suppose it's
> not possible for you to provide your application for us to take a look?
>
> One thing you could try is turn to log level of some sub components
> (the bolded ones below) to "FINE" in the domain.xml (under
> GF_INSTALL/domains/domain1/config, restart server after you modify)
> and see whether server.log has any additional information.
> <module-log-levels admin="*INFO*" classloader="INFO"
> cmp="INFO" cmp-container="INFO" configuration="INFO" connector="INFO"
> corba="INFO" deployment="*INFO*" ejb-container="INFO"
> group-management-service="INFO" javamail="INFO" jaxr="INFO"
> jaxrpc="INFO" jdo="INFO" jms="INFO" jta="INFO" jts="INFO"
> management-event="*INFO*" mdb-container="INFO" naming="INFO"
> node-agent="INFO" resource-adapter="INFO" root="INFO" saaj="INFO"
> security="INFO" self-management="INFO" server="*INFO*"
> synchronization="INFO" util="INFO" verifier="INFO" web-container="INFO"/>
>
>
> - Hong
>
>
>
>