As stated in my original post, I tried the -classic flag also. I got a Java
core dump.
My JDK works fine otherwise so I don't think it is related to the JDK.
Things work great under WinNT.
David T. Smith wrote in message
<[EMAIL PROTECTED]>...
>At 08:49 PM 8/30/99 +0000, Jim Piersol wrote:
>>Hi,
>>
>>I was hoping to get a hint about why I am getting the following error:
>>
>>
>>HotSpot VM warning: Setting of property "java.compiler" is ignored
>>Error [9] in connect() call!
>>err:: Bad file number
>>Socket transport failed to init.
>>Transport dt_socket failed to initialize, rc = -1.
>>FATAL ERROR in native method: No transports initialized
>>
>>My command line looks like this:
>>/opt2/local/java/jdk/jdk1.2.2/jre/bin/java -Xdebug -Xnoagent -Djava.compil
er
>>=NONE -Xrunjdwp:transport=dt_socket,address=eagle:54427,suspend=y -mx32m -
ms
>>16m -DSERVER_URL=t3://eagle:9764 strata.c3c.gui.C3C
>
>
>With HotSpot, you need to prefix debugging parameters with '-classic'; your
>command line should begin as follows:
>
>/opt2/local/java/jdk/jdk1.2.2/jre/bin/java -classic -Xdebug -Xnoagent
>-Djava.compiler=NONE ...
>
>DTS
>
>
>D A V I D T . S M I T H
>Principal Consultant, Network Solutions
>__________________________________________
>USWeb/CKS Corporation http://www.uswebcks.com/
>50 Washington Street 6th Floor
>South Norwalk, CT 06854
>ph: 1 203 857 0080
>fax: 1 203 857 0082
>mailto:[EMAIL PROTECTED]
>
>USWeb/CKS - A Strategic Partner for the Information Age
>
>
