It means they didn't take into effect. On the command line you should be able to do
java -verbose:class -version and see if that flag works, if it does, then I suggest you create a setenv.sh file next to startup.sh and put JAVA_OPTS="-verbose:class -Dibm.cl.verbose=ClassToTrace" export JAVA_OPTS and hopefully that way it takes into effect On Fri, Dec 12, 2014 at 6:47 PM, James H. H. Lampert < jam...@touchtonecorp.com> wrote: > On 12/12/14 5:36 PM, Filip Hanik wrote: > > We're not looking for change, we're looking for the output, that may tell >> us what is going on. Please post it, if you're not getting any output, >> then >> either those aren't supported (which I definitely thought they would be), >> or you're invoking it incorrectly >> > > Of course I wasn't expecting any change in behavior. "No change" > implicitly meant "no change in the output." And I then explicitly said that > the exceptions in catalina.out look the same, what gets sent to STDOUT > looks the same, and the joblogs from what QSHELL spawned off look the same. > > If there's anyplace else that additional output from those parameters > could have gone, besides catalina.out, STDOUT, or a spool file, I can't > imagine where, and I have over 20 years of experience with AS/400s. > > > -- > JHHL > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >