Erron Starting Messenger - Solaris 9

Openfire Openfire Support
1

I have made a mistake or just not seeing my mistake in the documention. I get the following error when I try to start messenger on Solaris 9 installation. I have include below the error message what I hope is helpful system and installation facts. Can anyone direct me to what I have missed?

#pwd /opt/jive_messenger/bin

  1. ./messenger start

Starting messenger

  1. Sending output to nohup.out

  2. ls

messenger nohup.out

  1. tail nohup.out

Unrecognized option: -server

Could not create the Java virtual machine.

Unrecognized option: -server

Could not create the Java virtual machine.

Unrecognized option: -server

Could not create the Java virtual machine.

System Info:

  1. java -version

java version “1.5.0_04”

Java™ 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)

Java HotSpot™ Server VM (build 1.5.0_04-b05, mixed mode)

When I run the demos and tests in the java dir, the virutal machines startup and run fine. I do not get any errors or messages in the logs.

MYSQL:

Installed all tests passed, imported the required file into the table per the instructions. I am assumeing that is fine.

Thanks

Dallas

2

Hi Dallas,

I believe on the Solaris version of the JRE the default VM uses the “-server” option. So, edit the messenger startup script and remove the -server option from lines ~226 and ~233 and then see if Messenger will start up. Let us know if that works.

Thanks,

Ryan

3

I remored the references in messener to -server on the lines indicated.

Here is what I get now:

  1. ./messenger start

Starting messenger

  1. Sending output to nohup.out

  2. more nohup.out

Dallas

4

Hi Dallas,

Looks like Messenger started up ok. Did you try going to http://127.0.0.1:9090 to see if the setup wizard comes up?

Thanks,

Ryan

5

Ryan,

Yes and I get a conneciton refused when attempting to contact http://127.0.0.1:9090. I am not seeing any error messages in syslog or messages file. I am not seeing any error message in the apache logs either.

Dallas

6

Hi Dallas,

Is there any info in the nohup.out file?

Thanks,

Ryan

7

Ryan,

I do see this in the logs file for jive:

  1. ls

stderror.log stderror.log-old

  1. more stderror.log

java.lang.UnsupportedClassVersionError: org/jivesoftware/messenger/starter/ServerStarter (Unsupported major.min

or version 49.0)

at java.lang.ClassLoader.defineClass0(Native Method)

at java.lang.ClassLoader.defineClass0(Compiled Code)

at java.lang.ClassLoader.defineClass(Compiled Code)

at java.security.SecureClassLoader.defineClass(Compiled Code)

at java.net.URLClassLoader.defineClass(Compiled Code)

at java.net.URLClassLoader.access$1(Compiled Code)

at java.net.URLClassLoader$1.run(Compiled Code)

at java.security.AccessController.doPrivileged(Native Method)

at java.security.AccessController.doPrivileged(Compiled Code)

at java.net.URLClassLoader.findClass(Compiled Code)

at java.lang.ClassLoader.loadClass(Compiled Code)

at sun.misc.Launcher$AppClassLoader.loadClass(Compiled Code)

at java.lang.ClassLoader.loadClass(Compiled Code)

at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)

at com.install4j.runtime.Launcher.main(Unknown Source)

  1. pwd

/opt/jive_messenger/logs

Maybe this will help?

Dallas

8

Ryan,

the nohup.out file was empty.

Dallas

9

Hi Dallas,

java.lang.UnsupportedClassVersionError:

org/jivesoftware/messenger/starter/ServerStarter

(Unsupported major.min

or version 49.0)

It looks like Messenger is trying to startup using with an older version of Java (which the startup script shouldn’'t let happen). On the ~4 line of the messenger script you can set where Messenger looks for the JVM its going to use, try setting that variable to where you have the JRE installed and then start Messenger.

Thanks,

Ryan

10

Ryan,

Putting in the full path in messenger script worked.

I can not get into the admin console.

Thank you for your help. I knew I was missing something.

Dallas

11

Closed the thread

Dallas