- This topic has 10 replies, 3 voices, and was last updated 20 years, 4 months ago by joelu.
-
AuthorPosts
-
joeluMember– System Setup ——————————-
Operating System and version: Windows XP Professional with latest patch installed
Eclipse version: Eclipse Platform 3.0 final
Eclipse build id:
Fresh Eclipse install (y/n): y
If not, was it upgraded to its current version using the update manager?
Other installed external plugins:
Number of plugins in the <eclipse>/plugins directory that begin with org.eclipse.pde.*:
MyEclipse version: 3.8beta1 and beta2
Eclipse JDK version: 1.4.2_04
Application Server JDK version: 1.4.2_04
Are there any exceptions in the Eclipse log file? no– Message Body ——————————-
When I try to start tomcat 5 server with “-nonaming” within eclipse via myeclipse app launcher, it terminate automatically without giving any message. When I try to launch tomcat 5 without any param, it is just working fine and if I specify “-nonaming start” in the tomcat param box, it is also working properly,
I also tried to launch tomcat 5 with the startup.bat in $tomcat_home\bin\ there is no problem.
I hope I didn’t config anything wrong, (same setting works with tomcat 4)
Riyad KallaMemberjoelu,
Where were you putting that “-nonaming” option under the Tomcat 5 connector settings? I want to try and duplicate the problem.Are you *sure* that is still an accepted command line option for Tomcat 5?
joeluMemberHi, Riyad,
I put “-nonaming” in the Optional Program Arguments box in server settings, it works with tomcat 4 but not for tomcat 5,
I am sure this param is working for tomcat 5 since I can see the message from console “disable tomcat naming….” when I start tomcat 5 in command line with “-nonaming” (tomcat 5.0.25)
and another prove is, when I put “-nonaming start” in the box, it also runs tomcat5 server properly.
I hopethis might help you to duplicate the issue
Regards,
Joe
Riyad KallaMemberJoe,
This doesn’t seem to be a supported command line anymore… I’ve been reading through the archives and it used to be an argument to the catalina script, but now it seems it is not anymore. I did see a message pertaining to the 4.1.12 release of Tomcat saying “I tried using -nonaming and it doesn’t seem to work anymore and I read there is another preferred way to turn off naming, what is it?”, but there was no reply to that user.You may want to try and find out which server setting it was to turn off naming.
Riyad KallaMemberOn a side note, it MAY still work, but if it is infact no longer a supported flag to Catalina, I can’t really help run this down as the connector ‘works as it should’, but if i missed something please point it out ASAP and I’ll dig more.
joeluMember@support-rkalla wrote:
Joe,
This doesn’t seem to be a supported command line anymore… I’ve been reading through the archives and it used to be an argument to the catalina script, but now it seems it is not anymore. I did see a message pertaining to the 4.1.12 release of Tomcat saying “I tried using -nonaming and it doesn’t seem to work anymore and I read there is another preferred way to turn off naming, what is it?”, but there was no reply to that user.You may want to try and find out which server setting it was to turn off naming.
“-nonaming” is working on my tomcat 4.1.30 and 4.1.27 (even launch with ME) there is no problem at all. I don’t know why that guy says “-nonaming is not working for 4.1.12
I also go through the startup code of tomcat 5.0.25
in
package:org.apache.catalina.startup
Class: CatalinaThere is one method which will print out the usage informations. Following is the code I copied from the src
/** * Print usage information for this application. */ protected void usage() { System.out.println ("usage: java org.apache.catalina.startup.Catalina" + " [ -config {pathname} ] [ -debug ]" + " [ -nonaming ] { start | stop }"); }
from the usage method above, I guess “-nonaming” is still support in tomcat 5.0.25
Correct me if I am wrong.
ThanksJoe
Riyad KallaMemberWell how am I suppose to argue with that? You didn’t even give me a loop hole or anything 😀
I actually checked the printed out usage with:
C:\Java\jakarta-tomcat-5.0.25\bin>catalina.bat The system cannot find the path specified. Using CATALINA_BASE: C:\Java\jakarta-tomcat-5.0.25 Using CATALINA_HOME: C:\Java\jakarta-tomcat-5.0.25 Using CATALINA_TMPDIR: C:\Java\jakarta-tomcat-5.0.25\temp Using JAVA_HOME: C:\Java\j2sdk1.4.2_04 Usage: catalina ( commands ... ) commands: debug Start Catalina in a debugger debug -security Debug Catalina with a security manager jpda start Start Catalina under JPDA debugger run Start Catalina in the current window run -security Start in the current window with security manager start Start Catalina in a separate window start -security Start in a separate window with security manager stop Stop Catalina C:\Java\jakarta-tomcat-5.0.25\bin>
And that is why I thought it didn’t support it, especailly after seeing that post from that gentleman… but it seems if you actually found it in the code that it should be supported, let me check with the devs to see what is maybe going wrong.
joeluMemberheh,
How do I suppose to initialize an argument with you (such a nice guy) 🙂
I found the same usage information from tomcat 4.1.30 catalina.bat
echo Usage: catalina ( commands ... ) echo commands: echo debug Start Catalina in a debugger echo debug -security Debug Catalina with a security manager echo embedded Start Catalina in embedded mode echo jpda start Start Catalina under JPDA debugger echo run Start Catalina in the current window echo run -security Start in the current window with security manager echo start Start Catalina in a separate window echo start -security Start in a separate window with security manager echo stop Stop Catalina goto end
I think the params “-config <pathname>” and “-nonaming” are passing to the Bootstrap class itself, it will do nothing with catalina.bat
My guess of the problem in ME is the sequence of params passed to Bootstrap,
Reason is, when I use “-nonaming” itself, server won’t startup
when I use “-nonaming start” server starts up without problem, (This is my workaround of the issue)BTW, to test out this on tomcat 5, you need to disable an reference to the UserDatabase Global Naming Resource in server.xml,
You can also try startup.bat -help, and the first line in the console is the usage information,
Thanks. Appreciate your help
Joe
Riyad KallaMemberwhen I use “-nonaming start” server starts up without problem, (This is my workaround of the issue)
This works? I tried it and Tomcat failed miserably… either way I filed and issue on it, lets see what turns up.
Scott AndersonParticipantJoe,
My guess of the problem in ME is the sequence of params passed to Bootstrap,
You are precisely correct with your keen analysis. We’ve got a bug on this issue that will be fixed for 3.8 GA, thanks to your report. Please continue to use your workaround in the meantime. 🙂
joeluMemberwhen I use “-nonaming start” server starts up without problem, (This is my workaround of the issue)
This works? I tried it and Tomcat failed miserably… either way I filed and issue on it, lets see what turns up.
I think you might not take out the GlobalNamingResources references in the server.xml, the UserDatabase will be failed with -nonaming in tomcat 5
@support-scott wrote:
You are precisely correct with your keen analysis. We’ve got a bug on this issue that will be fixed for 3.8 GA, thanks to your report. Please continue to use your workaround in the meantime.
It is good to know this was already address in your check list, I am looking forward to the GA version. 🙂
Joe
-
AuthorPosts