Chapter 10. Troubleshooting

com.levigo.jadice.server.JobException: Failure during server-side initialization on JADICE-SERVER-JS.REQUEST
   at com.levigo.jadice.server.client.jms.JMSJobController.performHandshake(JMSJobController.java:579)
   at com.levigo.jadice.server.client.jms.JMSJobController.submit(JMSJobController.java:365)
   at com.levigo.jadice.server.client.DefaultJobInternalImpl.submit(DefaultJobInternalImpl.java:74)
             

WARN  [; core.ThreadPoolJobScheduler; JadiceServer job scheduler master thread]: Not executing job due to expired request message: (…)
             

The set time and date of the client strongly deviate from those of the server.

Look into the time and date settings of client and server and synchronize them if necessary.

Exception launching job
com.thoughtworks.xstream.converters.ConversionException: SomeNode : SomeNode
---- Debugging information ----
message             : SomeNode
cause-exception     : com.thoughtworks.xstream.mapper.CannotResolveClassException
cause-message       : SomeNode
class               : java.util.ArrayList
required-type       : java.util.ArrayList
converter-type      : com.thoughtworks.xstream.converters.collections.CollectionConverter
path                : /com.levigo.jadice.server.client.internal.DefaultJobInternalImpl/node/successors/SomeNode
line number         : 8
class[1]            : com.levigo.jadice.server.nodes.StreamInputNode
converter-type[1]   : com.thoughtworks.xstream.converters.reflection.ReflectionConverter
class[2]            : com.levigo.jadice.server.client.internal.DefaultJobInternalImpl
version             : 1.4.7
-------------------------------
(…)

The Job generated by the client references a Node class which does not exist in the class path of the server.

Check the class path of the server and add the missing library.

javax.jms.JMSException: Failed to build body from bytes.
   Reason: java.io.IOException:
   com.levigo.jadice.server.shared.jms.ServerMessage$InitializationResponse

javax.jms.JMSException: Failed to build body from bytes.
   Reason: java.io.InvalidClassException:
   com.levigo.util.internal.log.qualified.ResolvedQualifiedLogEvent;
   class invalid for deserialization

There is more than one JMS provider in the class path of the client.

If possible, use only one JMS provider in your application. If this is not possible, change the order of the class path in such a way that the JMS provider which is used for jadice server has precedence.

java.lang.StackOverflowError
  (…)
   at org.lobobrowser.html.parser.HtmlParser.parseToken(HtmlParser.java:642)
   at org.lobobrowser.html.parser.HtmlParser.parseToken(HtmlParser.java:679)
   at org.lobobrowser.html.parser.HtmlParser.parseToken(HtmlParser.java:679)
  (…)
   at org.lobobrowser.html.parser.HtmlParser.parse(HtmlParser.java:507)
   at org.lobobrowser.html.domimpl.HTMLDocumentImpl.load(HTMLDocumentImpl.java:386)
   at org.lobobrowser.html.domimpl.HTMLDocumentImpl.load(HTMLDocumentImpl.java:366)
   at org.lobobrowser.html.parser.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:98)(…)

The parsing of unfavorably structured HTML documents exceeds the maximum allowable stack depth of the JVM.

Increase the maximum allowable stack depth of the JVM, for example by setting the parameter -Xss2048k in the file wrapper/wrapper.conf (if an Oracle / SUN JVM is used).