FYIwe fixed this, changing the split strategy from an XPATH to a
tokenized split. When we "load tested" our routes with both strategies, we
were able to recreate the errors consistently with the XPATH split. When we
changed to the tokenized split we never got an error, all
splits/aggregations
"What OS, JDK, and JAXB version do you use?"
windows server 2008 R2 Standard 64bit
jdk1.6.0_17\jre\bin\server\jvm.dll
Not sure about the JAXB...here are the jars pulled in from maven.
"And have you added saxon to the classpath, eg using camel-saxon. Saxon
is usually faster and better as xpath
Thanks to Claus I was able to get this resolved. It was a classpath issue,
which was obvious, but which one caused the issue, see explanation below.
The jetty dependencies seemed to be ok, except these:
[INFO] | +- org.eclipse.jetty:jetty-webapp:jar:7.1.6.v20100715:compile
[INFO] | \-
or
Here is the maven dependency tree from maven:
[INFO] [dependency:tree {execution: default-cli}]
[INFO] com.infarmbureau:CSP-Services:war:0.0.1
[INFO] +- com.infarmbureau.esb:ESBClientJava6:jar:2.0.0:compile
[INFO] | \- org.apache.activemq:activemq-optional:jar:5.5.0:compile
[INFO] | +- org.e
I've tried several combinations of log4j and slf4j...with no success, any
ideas how to proceed, thanks!
Any other information needed?
tomcat:6
jdk:1.6.21
stack trace:
SEVERE: Exception sending context initialized event to listener instance of
class org.springframework.web.context.ContextLoaderLi
Jetty version we are trying to use: 7.5.4.v20111024We pull in our jetty api
from the following:*org.apache.camel
camel-jetty 2.10.3 *so maven
dependency looks like this:[INFO] +-
org.apache.camel:camel-jetty:ja
We are migrating to 2.10.3 from 2.7.4. So far everything worked great just
changing the camel version, however I'm getting the following error trying
to use a jetty:https endpoint. What dependency am I missing?
java.lang.NoSuchMethodException:
org.eclipse.jetty.server.ssl.SslSelectChannelConnect
