Problem in WebSphere 6.0 ejbdeploy

[Sivachandran Sundararajan]

Hi all,

I am using WebSphere 6.0 and try to do ejbdeploy but i got the error.Can anyone please help me in this regard.This works fine in WebSphere 5.1.0 & 5.1.1.6

Unable to parse setupCmdLine: null\bin\setupCmdLine.bat (The system cannot find the path specified)

[Graham Thorpe]

your webspehere corrupted,so u have to reinstall .

[Scott Selikoff]

You can create a new profile instead of doing a reinstall. This has the same effect as a reinstall but works a heck of a lot faster. Run the profile wizard in the WAS_HOME directory. Can't remember the exact folder/file name but its pretty easy to find.

[Sivachandran Sundararajan]

The profile or WebSphere didnt get corrupted it seems to be fine.
I saw in forums lot of them post the same problem but no one is conveyiing a fix.Please refer the following links

http://www.theserverside.com/discussions/thread.tss?thread_id=32285

http://www.theserverside.com/news/thread.tss?thread_id=32285

http://www.webservertalk.com/showthread.php?s=083e3346aa5023d440a795d0b8bf074b&threadid=1167196&goto=nextoldest


Can anyone suggest any idea regd this?

[Scott Selikoff]

There is one fix, delete WAS and never install it .

WAS6 is still a tad unstable compared to it WAS5 counterpart so you just have to struggle with it into they make it more stable.

[Scott Selikoff]

BTW, since WAS is unstable and cannot be repaired when it breaks, its not all bad. It forces application developers to think about scripting server setup (a very good thing) early on.

After all, if your server can be corrupted at any minute, its good to be able to use scripts to rebuild a new server in about 5 minutes.

[Roland Barcia]

Not exactly sure how running EJB deploy, a stand alone utility for generating EJB proxy and stubs, has to do with the server being corrupted?

Please do not spread lies like this?

Are there any error messages in the logs?

[Roland Barcia]

Unable to parse setupCmdLine: null\bin\setupCmdLine.bat (The system cannot find the path specified)


This seems to be that the WAS_HOME variable is not set properly.

[Scott Selikoff]

Your right Roland, I had read this post a tad too briefly (relying on Graham Thorpe comment that the server was all ready corrupted). Fixing the variable should repair most of the issues.

In the case that the server configuration was corrupt, though, do you have a way repair it without creating a new profile, or regardless, is it easier to just create a new profile?

[Roland Barcia]

Anytime you deal with resources on a file system, you run the risk of files becoming corrupt. I have have corupt servers in WAS, WebLogic, JBoss, and many other servers that store their configurations in XML on the file system. Because we provide a sophisticated file replication over the network for WAS ND, there is risk of networks going down during tranmission of files, etc...

Luckly, we have provided a tool since WAS 5 called backupConfig.bat and restoreCOnfig.bat. They are located in the bin directory of WebSphere. One of the Best practices we have is running the backupConfig.bat utility when making major config changes. The backup config file will store these changes in a single file. Then if a configuration becomes corrupt, you can run restoreConfig and point to the file. You should do this with each profile.

[Scott Selikoff]

Sounds like a useful tool, I think it would have saved me some time had I used it in the past.

[Sivachandran Sundararajan]

Thanks this was a nice piece of information.I will try and let you know

[Peter Hawkins]

No matter what environment or java properties I set, I get:

BUILD FAILED
C:\xxxx\build.xml:800: Unable to parse setupCmdLine: null\bin\setupCmdLine.bat (The system cannot find the path specified)

The plan is to automate installation for nightly build/testing.

Guess I have to decompile this buggy stuff.

[Vivek Srinivasan]

When i run the wsejbDeploy ANT task , i get the following error message.

C:\dev\vsriniva_Core_4_2\WFX_Core\core\components\ant\xml\ejb-builder-template.xml:495: Unable to parse setupCmdLine: null\bin\setupCmdLine.bat (The system cannot find the path specified)

I found a lot of thread with out any concrete solution. Is this a known probelm in WAS 6.0.2.x?

Please let me know of a fix..

Is there a workaround or a soultion yet? PLease let me know

[Qin Geng]

Originally posted by Sivachandran Sundararajan:
Hi all,

I am using WebSphere 6.0 and try to do ejbdeploy but i got the error.Can anyone please help me in this regard.This works fine in WebSphere 5.1.0 & 5.1.1.6

Unable to parse setupCmdLine: null\bin\setupCmdLine.bat (The system cannot find the path specified)

Hello,

I had the same problem last month, and struggled for a while. I found the point is, we have to use <ws_home>\profiles\AppSrv01\bin\ws_ant.bat to call ant, instead of calling ant directly. By using ws_ant.bat, it will initialize some env variables, and using IBM's JVM to do the job. Another thing is, in build script, I need to define property "wasinstall" as websphere install home. This property will be used as ejb deploy task's attribute "wasHome"'s value.

[nancy andrew]

If you are running the build.xml from RAD/RSA then try setting user.install.root=<was_home> in
Windows-->Preferences-->Ant-->Runtime-->Add Property

This worked for me as I was facing the same issue.