Tomcat has few fallback approach for catalina.properties: 1.First it look at system properties for config url, with property name "catalina.config" 2.If it could not find in step-1, it looks at CATALINA_BASE/conf/ 3.If it again could'n find above, it tries to load it from the classpath of bootstrap classloader. 4.If it couldn't find even there, it will spit a WARNING log.
Given that: a. as you mentioned 2nd is not a problem and CATALINA_BASE/conf/catalina.properties have valid common.loader values b. 3rd should not be a problem, because as can be seen bootstrap.jar is there, and if everything is okay, catalina.properties should be included inside it(you can verify it by unzipping the bootstrap.jar and sneaking at org/apache/catalina/startup) c. and finally you don't see any warning log I will imagine you are passing "catalina.config" as a system property, which is pointing to a catalina.properties which doesn't have a valid common.loader value. And if this is not the case, then catalina.jar which is being picked us is corrupted and doesn't contain org.apache.catalina.startup.Catalina. This you can verify by manually sneaking into the jar, by unzipping it. Apart from these, there is little else which I could imagine is a problem. And off-course these are all under the assumption that you are using standard distribution and haven't tweaked with the build process/or even customizing the code. Also, I will suggest you past your catalina.log somewhere for us to see, probably you may be missing something? Regards, Ameer Mawia On Sat, Dec 13, 2014 at 7:50 AM, Filip Hanik <fi...@hanik.com> wrote: > 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 > > > > >
