Expand my Community achievements bar.

Flex 2 Beta 3 messaging exception

Avatar

Level 1
We are porting our app from Flex 20 Beta 2 to Beta 3 and are
running into this exception.

(The server is Tomcat 5.5.17.).

Has anyone seen this before?

Appreciate any answers,

thanks



05/17 16:57:43 ERROR java.lang.LinkageError: loader
constraints violated when li

nking org/w3c/dom/Node class

at
flex.messaging.config.ApacheXPathClientConfigurationParser.selectSing

leNode(ApacheXPathClientConfigurationParser.java:49)

at
flex.messaging.config.ClientConfigurationParser.parseTopLevelConfig(C

lientConfigurationParser.java:42)

at
flex.messaging.config.AbstractConfigurationParser.parse(AbstractConfi

gurationParser.java:71)

at
flex.messaging.config.AbstractConfigurationParser.parse(AbstractConfi

gurationParser.java:62)

at
flex.messaging.config.ServicesDependencies.getClientConfiguration(Ser

vicesDependencies.java:96)

at
flex.messaging.config.ServicesDependencies.<init>(ServicesDependencie

s.java:35)

at
flex.services.config.Configurator.generateConfiguration(Configurator.

java:202)

at
flex2.server.j2ee.IncrementalCompileFilter.compileMxml(IncrementalCom

pileFilter.java:77)

at
flex2.server.j2ee.BaseCompileFilter.mxmlToSwf(BaseCompileFilter.java:

286)

at
flex2.server.j2ee.BaseCompileFilter.invoke(BaseCompileFilter.java:72)



at
flex2.server.j2ee.RecompileFilter.invoke(RecompileFilter.java:38)

at flex2.server.j2ee.AboutFilter.invoke(AboutFilter.java:48)

at flex2.server.j2ee.MxmlServlet.doGet(MxmlServlet.java:158)

at
javax.servlet.http.HttpServlet.service(HttpServlet.java:689)

at
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

at
flex.bootstrap.BootstrapServlet.service(BootstrapServlet.java:72)

at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl

icationFilterChain.java:252)

at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF

ilterChain.java:173)

at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV

alve.java:213)

at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextV

alve.java:178)

at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j

ava:126)

at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j

ava:105)

at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal

ve.java:107)

at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav

a:148)

at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java

:869)

at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.p

rocessConnection(Http11BaseProtocol.java:664)

at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpo

int.java:527)

at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFol

lowerWorkerThread.java:80)

at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadP

ool.java:684)

at java.lang.Thread.run(Thread.java:534)

1 Reply

Avatar

Level 1
I just successfully deployed all three FDS web applications
on Tomcat 5.5.17 with Sun 1.5.0_06 without any exceptions. From the
stack trace it looks like this is thrown at startup. Can you
confirm?



Are you sure you deployed the war files cleanly?