I switched over to sun's 1.2.2 jdk, and I get the same errors. Sun's jdk
doesn't lock up, but it gives exactly the same error messages (the
formatting is a bit different, but they use the same words...)
Has anyone successfully run orionserver on a linux box?
(Victor: Sorry about the duplicate - I noticed the To field as I was
pressing send...)
----- Original Message -----
From: "Victor A. Salaman" <[EMAIL PROTECTED]>
To: "'Aaron Brashears'" <[EMAIL PROTECTED]>
Sent: Thursday, February 24, 2000 15:53
Subject: RE: errors starting orion
> It's your JVM.... :)
>
> -----Original Message-----
> From: Aaron Brashears [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, February 24, 2000 7:04 PM
> To: Orion-Interest
> Subject: errors starting orion
>
>
> Hi there everyone. I'm hope that someone on this list can help out with a
> problem I'm running into starting the orion server. I'm running a debian
> gnu-linux box with blackdown java 1.2.2rc4 and I set up both orion0.9.1b
and
> orion0.9.1.c. But both have the same problem when I try to start them.
> Here's each of the different methods I've tried:
>
> 1. Follow the instructions, and run 'java jar orion.jar'. This generates a
> quick error:
> Exception in thread "main" java.lang.NoDefClassFoundError: jar
>
> 2. Playing around with those parameters yields:
> # java orion
> Exception in thread "main" java.lang.NoDefClassFoundError: orion
> # java orion.jar
> Exception in thread "main" java.lang.NoDefClassFoundError: orion/jar
>
> 3. So, I read the output from typing 'java' and decided that jar needed a
> '-' in front of it for java to work correctly. Here are the results of
that
> little test:
> # java -jar orion.jar
> Received signal: Quit
> SIGSEGV 11* segmentation violation
>
> and the xterm locks - permanently.
>
> 4. Closing that window and moving on to other things I tried:
> #java -jar orion
> Failed to load Main-Class mainfest attribute from:
> orion
>
> 5. As a last resort, I read the readme which suggests that I try to run
the
> app like documented in #3. I decide this is a bad idea (since it locks the
> consol instance), but it also suggests supplying the path to server.xml.
One
> last try:
> #java -jar orion.jar /usr/local/orion/conf/server.xml
> Received signal: Quit
> SIGSEGV 11* segmentation violation
>
>
> Has anyone else experienced this problem? Any solutions?
> TIA
>
