Hi,
I had installed 64-bit WebSphere 7.0 in a Windows 2003 64-bit machine. When I am trying to start the server through an ANT script using ws_ant utility
C:/> ws_ant.bat -f build.xml -debug -logfile log.txt
where build.xml looks like this;
<?xml version="1.0"?>
<!-- Build file for our first application -->
<project name="Ant test project" default="build" basedir=".">
<taskdef name="wsStartServer" classname="com.ibm.websphere.ant.tasks.StartServer" />
<target name="build" >
<wsStartServer server="server1" profileName="peoplesoft3" />
</target>
</project>
I get the following error;
startServer profileName=psft_image registry=D:\Anusha\WAS7_Image\properties\profileRegistry.xml
startServer profileHome=D:\Anusha\PT8.51-102-R2\webserv\psft_image
startServer JVMJ9VM007E Command-line option unrecognised: -d64
startServer Usage: java
-options class
http://args...
startServer (to execute a class)
startServer or java
-jar -options jarfile
http://args...
startServer (to execute a jar file)
..............................................................
..............................................................
startServer Could not create the Java virtual machine.
I don't find this kind of a problem in an AIX 5.3 64-bit machine.
Is there any known issue with custom WS_ANT tasks like wsStartServer, wsstopserver etc in Windows 2003 & Win 2008 64-bit boxes.
Note also that this issue happens only with 64-bit version of WebSphere 7.0. I don't see this issue with the 32-bit version of WebSphere 7.0 on Windows 2003 & 2008 64-bit boxes.
If anybody know of a known APAR or a way to workaround this issue let me know.
Thanks,
Hemanth
