Projects tigase _server server-core Issues #536
Service wrapper configured incorrectly (#536)
Daniel Wisnewski opened 9 years ago
Due Date
2015-09-29

wrapper.exe (when called to start tigase as a service in windows environment) uses the wrapper.conf file that is incorrectly configured. Java Classpaths are listed in the configuration file by default as follows:

@# Java Classpath (include wrapper.jar) Add class path elements as

  1. needed starting from 1

wrapper.java.classpath.1=libs/wrapper.jar

wrapper.java.classpath.2=jars/tigase-server.jar

wrapper.java.classpath.3=libs/jdbc-mysql.jar

wrapper.java.classpath.4=libs/jdbc-postgresql.jar

wrapper.java.classpath.5=libs/derby.jar

wrapper.java.classpath.6=libs/tigase-utils.jar

wrapper.java.classpath.7=libs/tigase-xmltools.jar

wrapper.java.classpath.8=libs/cindy.jar

wrapper.java.classpath.9=libs/commons-logging.jar

wrapper.java.classpath.10=libs/jml-1.0b2.jar

wrapper.java.classpath.11=libs/jtds-1.2.2.jar

wrapper.java.classpath.12=libs/tigase-muc.jar

wrapper.java.classpath.13=libs/tigase-extras.jar

wrapper.java.classpath.14=libs/tigase-pubsub.jar

wrapper.java.classpath.15=libs/groovy-all-1.5.7.jar

wrapper.java.classpath.16=libs/groovy-engine.jar@

Wrapper.log returns the error

@STATUS | wrapper | 2015/08/06 17:21:41 | Launching a JVM...

INFO | jvm 1 | 2015/08/06 17:21:41 | Error: Could not find or load main class org.tanukisoftware.wrapper.WrapperSimpleApp

ERROR | wrapper | 2015/08/06 17:21:41 | JVM exited while loading the application.@

the /libs directory is not created on installation, could this be an old vestigial directory?

By editing the conf file to use the jars directory instead of libs, wrapper throws no errors and can launch Tigase using the following edits.

@wrapper.java.classpath.1=jars/wrapper.jar

wrapper.java.classpath.2=jars/tigase-server.jar

wrapper.java.library.path.1=jars@

any other edit seem inconsequential.

Artur Hefczyc commented 9 years ago

Yes, you are correct. libs is the old directory where we used to store our libraries. Now everything is located in jars folder.

Daniel Wisnewski commented 9 years ago

Added minor changes to wrapper.conf, wrapper only needs it's own DLL and tigase-server.dll classpaths to operate correctly, older classpaths left for now as they do not cause errors, further testing without classpaths will commence to clean up configuration file.

Diff: 7e7bc16

issue 1 of 1
Type
Bug
Priority
Normal
Assignee
RedmineID
3371
Version
tigase-server-7.1.0
Spent time
2h 6m
Issue Votes (0)
Watchers (0)
Reference
tigase/_server/server-core#536
Please wait...
Page is in error, reload to recover