not able to start jboss through run.bat

hi,

when i am trying to start jboss-5.1.0.GA using run.bat file , not able to start the server. showing the following message in my command promt.

E:\softwares\jboss-5.1.0.GA\bin>run.bat

Calling E:\softwares\jboss-5.1.0.GA\bin\run.conf.bat

E:\softwares\jboss-5.1.0.GA\bin>ika

could you please help me regarding this?

Thanks,
Ravikanth

Is is possible your files got modified? Try the same with the vanilla version without doing any modifications after unzipping the pack. If the problem persists make sure your java is configured properly. Also you can turn the echo on in the .bat files to see a more verbose output.

Another thing you could try: edit the run.bat file and either comment out of remove the first line; commenting out would look like this:

rem @echo off

Then run it again. That should help pinpoint the line causing the problem.

Better extract the installer again and then run the run.bat file in case if you have not tampered any files.

Ensure that you have JBOSS_HOME, JAVA_HOME configured in your environment variables (Windows) or .bash_profile (RHEL)

Rgds,

Seetesh

I strongly recommend that you do not set JBOSS_HOME, doing so can get you into trouble (you forgot you set it and you install another version of JBoss AS elsewhere and then can't figure out why nothing works). The run scripts will set JBOSS_HOME for you, you don't have to set it.

Hello Peter,

Any other strong reason apart from not being able to set the JBOSS_HOME variable if there are more than one installation version of JBoss.

If I am the owner of the desktop/server, I will definately know which version of JBOSS to use and set environment variables accordingly. Unless its being used by someone novice.

I have hardly noticed installations/configurations of Production servers having "run.conf" configured to required Java/JBoss_Home leave alone memory usage for JBoss unlike AIX machines.

Rgds,

Seetesh

Yes, there have been too many posts in the forums from people who have set JBOSS_HOME and then at some time later nothing works because the forgot that it was set and is now referring to an old copy, and that has caused them to run into a problem. In most cases it takes a few days to get to the bottom of the problem because we don't expect that env var to be set. And of course the typical suggestion of "hmm, it seems you have a corrupted installation, try downloading and installing again" doesn't work. My general guideline is that if the startup script sets the necessary env vars, don't set them yourself.