[mule-dev] Fwd: Re: [mule-builds] [Bamboo] Mule - Mule 1.4.x build 659 has FAILED (3 tests failed, 1 failures were new). Change made by Andrey Shaposhnikov

0 views
Skip to first unread message

Holger Hoffstätte

unread,
Jan 30, 2008, 10:53:19 AM1/30/08
to mule-dev
I accidentally sent this to builds@ which seems to be one-way. Resending
since it seems to be a recurring problem.

-------- Original Message --------
Most recent failures seem to have the same cause:

org.mule.providers.FatalConnectException: ReconnectStrategy
"org.mule.providers.SingleAttemptConnectionStrategy" failed to reconnect
receiver on endpoint "JmsConnector{this=10d6874, started=false,
initialised=true, name='connector.jms.0', disposed=false,
numberOfConcurrentTransactedReceivers=4,
createMultipleTransactedReceivers=true, connected=false,
supportedProtocols=[jms], serviceOverrides=null}"
at
org.mule.providers.SingleAttemptConnectionStrategy.doConnect(SingleAttemptConnectionStrategy.java:29)
at
org.mule.providers.AbstractConnectionStrategy.connect(AbstractConnectionStrategy.java:97)
at
org.mule.providers.AbstractConnector.startConnector(AbstractConnector.java:350)
at org.mule.MuleManager.startConnectors(MuleManager.java:932)
at org.mule.MuleManager.start(MuleManager.java:888)
at org.mule.extras.client.MuleClient.init(MuleClient.java:245)
at org.mule.extras.client.MuleClient.<init>(MuleClient.java:123)
at
org.mule.test.integration.spring.events.SpringEventsJmsExampleTestCase.testReceivingASubscriptionEvent(SpringEventsJmsExampleTestCase.java:65)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at junit.framework.TestCase.runTest(TestCase.java:164)
at junit.framework.TestCase.runBare(TestCase.java:130)
at org.mule.tck.AbstractMuleTestCase.runBare(AbstractMuleTestCase.java:175)
at junit.framework.TestResult$1.protect(TestResult.java:106)
at junit.framework.TestResult.runProtected(TestResult.java:124)
at junit.framework.TestResult.run(TestResult.java:109)
at junit.framework.TestCase.run(TestCase.java:120)
at org.mule.tck.AbstractMuleTestCase.run(AbstractMuleTestCase.java:155)
at junit.framework.TestSuite.runTest(TestSuite.java:230)
at junit.framework.TestSuite.run(TestSuite.java:225)
at sun.reflect.GeneratedMethodAccessor28.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:213)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:140)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:127)
at org.apache.maven.surefire.Surefire.run(Surefire.java:177)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:334)
at
org.apache.maven.surefire.booter.SurefireBooter.main(SurefireBooter.java:980)
Caused by: org.mule.providers.FatalConnectException: ReconnectStrategy
"org.mule.providers.SingleAttemptConnectionStrategy" failed to reconnect
receiver on endpoint "JmsConnector{this=10d6874, started=false,
initialised=true, name='connector.jms.0', disposed=false,
numberOfConcurrentTransactedReceivers=4,
createMultipleTransactedReceivers=true, connected=false,
supportedProtocols=[jms], serviceOverrides=null}"
at
org.mule.providers.SingleAttemptConnectionStrategy.doConnect(SingleAttemptConnectionStrategy.java:29)
at
org.mule.providers.AbstractConnectionStrategy.connect(AbstractConnectionStrategy.java:97)
at org.mule.providers.AbstractConnector.connect(AbstractConnector.java:1169)
at
org.mule.providers.SingleAttemptConnectionStrategy.doConnect(SingleAttemptConnectionStrategy.java:25)
... 34 more
Caused by: org.mule.providers.ConnectException: Failed to create Jms Connector
at org.mule.providers.jms.JmsConnector.doConnect(JmsConnector.java:368)
at org.mule.providers.AbstractConnector.connect(AbstractConnector.java:1159)
at
org.mule.providers.SingleAttemptConnectionStrategy.doConnect(SingleAttemptConnectionStrategy.java:25)
... 37 more
Caused by: org.mule.umo.lifecycle.InitialisationException: The required
object/property "jndiInitialFactory" is null
at org.mule.providers.jms.JmsConnector.initJndiContext(JmsConnector.java:203)
at org.mule.providers.jms.JmsConnector.doConnect(JmsConnector.java:333)
... 39 more
Caused by: org.mule.providers.FatalConnectException: ReconnectStrategy
"org.mule.providers.SingleAttemptConnectionStrategy" failed to reconnect
receiver on endpoint "JmsConnector{this=10d6874, started=false,
initialised=true, name='connector.jms.0', disposed=false,
numberOfConcurrentTransactedReceivers=4,
createMultipleTransactedReceivers=true, connected=false,
supportedProtocols=[jms], serviceOverrides=null}"
at
org.mule.providers.SingleAttemptConnectionStrategy.doConnect(SingleAttemptConnectionStrategy.java:29)
at
org.mule.providers.AbstractConnectionStrategy.connect(AbstractConnectionStrategy.java:97)
at org.mule.providers.AbstractConnector.connect(AbstractConnector.java:1169)
at
org.mule.providers.SingleAttemptConnectionStrategy.doConnect(SingleAttemptConnectionStrategy.java:25)
... 34 more
Caused by: org.mule.providers.ConnectException: Failed to create Jms Connector
at org.mule.providers.jms.JmsConnector.doConnect(JmsConnector.java:368)
at org.mule.providers.AbstractConnector.connect(AbstractConnector.java:1159)
at
org.mule.providers.SingleAttemptConnectionStrategy.doConnect(SingleAttemptConnectionStrategy.java:25)
... 37 more
Caused by: org.mule.umo.lifecycle.InitialisationException: The required
object/property "jndiInitialFactory" is null
at org.mule.providers.jms.JmsConnector.initJndiContext(JmsConnector.java:203)
at org.mule.providers.jms.JmsConnector.doConnect(JmsConnector.java:333)
... 39 more

so why is the reconnection suddenly flunking out, and where does the JNDI
info go? Is ActiveMQ dying prematurely or what? When I run these tests
locally, they succeed but I always (repeatably) get the old
DefaultMessageAdapter "Non-owner writing to message" warning -
disturbingly enough from the jmsConnector.receiver.1
thread, which indicates that there is still something seriously wrong with
the JMS message receiver and message property handling in general.

Could these changes be related to the recent changes in either JMS or
maybe AbstractMessageDispatcher? I'll skim the recent changes but this is
all very disturbing :(

---------------------------------------------------------------------
To unsubscribe from this list please visit:

http://xircles.codehaus.org/manage_email

Reply all
Reply to author
Forward
0 new messages