[mule-user] Error 13040 on 1.4 but works ok on 1.3.3 (There are at least 2 connectors matching protocol...)

Pete

unread,

May 27, 2007, 1:37:08 PM5/27/07

to us...@mule.codehaus.org

Greets, following config worked Ok on 1.3.3 (2 jms connectors, one for in
and one for out on other server):

<environment-properties>
<property name="jms.name.queue.Device.in"
value="jms:////queue:device.in"/>
<property name="jms.name.queue.Device.out"
value="jms:////queue:device.out"/>
</environment-properties>

...
...

<connector name="CFMInboundDeviceConnector"
className="org.mule.providers.jms.JmsConnector">
<properties>
<property name="jndiInitialFactory"
value="org.jnp.interfaces.NamingContextFactory"/>
<property name="jndiProviderUrl" value="jnp://127.0.0.1:11099/"/>
<property name="connectionFactoryJndiName"
value="java:/ConnectionFactory"/>
<property name="specification" value="1.1"/>
</properties>
</connector>

...
...

<endpoint-identifiers>
<endpoint-identifier name="CFMInbound"
value="${jms.name.queue.Device.in}"/>
<endpoint-identifier name="CFMOutbound"
value="${jms.name.queue.Device.out}"/>
</endpoint-identifiers>

<inbound-router>
<endpoint address="CFMInbound" synchronous="false"
connector="CFMInboundDeviceConnector" remoteSync="false"/>

....
..
</inbound-router>

<outbound-router>
<endpoint address="CFMOutbound" synchronous="true" remoteSync="false"
connector="CFMOutboundDeviceConnector"/>

...
..
</outbound-router>

Error on start:

********************************************************************************
Message : MuleManager Failed to initialise
Type : org.mule.config.ConfigurationException
Code : MULE_ERROR-13040
JavaDoc :
http://mule.mulesource.org/docs/apidocs/org/mule/config/ConfigurationException.html
********************************************************************************
Exception stack is:
1. There are at least 2 connectors matching protocol "jms", so the
connector to use must be specified on the endpoint using the 'connector'
property/attribute (java.lang.IllegalStateException)
org.mule.providers.service.TransportFactory:438
(http://java.sun.com/j2se/1.5.0/docs/api/java/lang/IllegalStateException.html)
2. MuleManager Failed to initialise
(org.mule.config.ConfigurationException)
org.mule.config.builders.MuleXmlConfigurationBuilder:255
(http://mule.mulesource.org/docs/apidocs/org/mule/config/ConfigurationException.html)
********************************************************************************
Root Exception stack trace:
java.lang.IllegalStateException: There are at least 2 connectors matching
protocol "jms", so the connector to use must be specified on the endpoint
using the 'connector' property/attribute
at
org.mule.providers.service.TransportFactory.getConnectorByProtocol(TransportFactory.java:438)
at
org.mule.providers.service.TransportFactory.getOrCreateConnectorByProtocol(TransportFactory.java:396)
at
org.mule.providers.service.TransportFactory.getOrCreateConnectorByProtocol(TransportFactory.java:390)
at
org.mule.impl.ImmutableMuleEndpoint.initialise(ImmutableMuleEndpoint.java:660)
at
org.mule.impl.ImmutableMuleDescriptor.initialise(ImmutableMuleDescriptor.java:357)
at
org.mule.impl.model.AbstractComponent.initialise(AbstractComponent.java:129)
at org.mule.impl.model.AbstractModel.initialise(AbstractModel.java:464)
at org.mule.MuleManager.initialise(MuleManager.java:781)
at org.mule.MuleManager.start(MuleManager.java:883)
at
org.mule.config.builders.MuleXmlConfigurationBuilder.configure(MuleXmlConfigurationBuilder.java:250)
at
org.mule.config.builders.MuleXmlConfigurationBuilder.configure(MuleXmlConfigurationBuilder.java:211)
at org.mule.MuleServer.initialize(MuleServer.java:290)
at org.mule.MuleServer.run(MuleServer.java:203)
at org.mule.MuleServer.start(MuleServer.java:191)
at org.mule.MuleServer.main(MuleServer.java:162)
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:585)
at com.intellij.rt.execution.application.AppMain.main(AppMain.java:90)

Is this config error or something on 1.4?

Thanks,

___________________________________________________________
The all-new Yahoo! Mail goes wherever you go - free your email address from your Internet provider. http://uk.docs.yahoo.com/nowyoucan.html

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

http://xircles.codehaus.org/manage_email

Andrew Perepelytsya

unread,

May 27, 2007, 1:53:47 PM5/27/07

to us...@mule.codehaus.org

Pete,

This is http://mule.mulesource.org/jira/browse/MULE-1665

I'm not sure it may be fixed in 1.4.1 (coming out next week), but I'll try to come up with a fix or at least a patch to disable the exception. You're welcome to experiment with the code as well.

Andrew

( http://java.sun.com/j2se/1.5.0/docs/api/java/lang/IllegalStateException.html)

2. MuleManager Failed to initialise
(org.mule.config.ConfigurationException)
   org.mule.config.builders.MuleXmlConfigurationBuilder :255
(http://mule.mulesource.org/docs/apidocs/org/mule/config/ConfigurationException.html)
********************************************************************************
Root Exception stack trace:
java.lang.IllegalStateException: There are at least 2 connectors matching
protocol "jms", so the connector to use must be specified on the endpoint
using the 'connector' property/attribute
        at
org.mule.providers.service.TransportFactory.getConnectorByProtocol(TransportFactory.java:438)
        at
org.mule.providers.service.TransportFactory.getOrCreateConnectorByProtocol(TransportFactory.java :396)
        at
org.mule.providers.service.TransportFactory.getOrCreateConnectorByProtocol(TransportFactory.java:390)
        at
org.mule.impl.ImmutableMuleEndpoint.initialise(ImmutableMuleEndpoint.java:660)
        at
org.mule.impl.ImmutableMuleDescriptor.initialise(ImmutableMuleDescriptor.java:357)
        at
org.mule.impl.model.AbstractComponent.initialise(AbstractComponent.java:129)

at org.mule.impl.model.AbstractModel.initialise (AbstractModel.java:464)

        at org.mule.MuleManager.initialise(MuleManager.java:781)
        at org.mule.MuleManager.start(MuleManager.java:883)
        at

org.mule.config.builders.MuleXmlConfigurationBuilder.configure (MuleXmlConfigurationBuilder.java:250)

        at
org.mule.config.builders.MuleXmlConfigurationBuilder.configure(MuleXmlConfigurationBuilder.java:211)
        at org.mule.MuleServer.initialize(MuleServer.java:290)
        at org.mule.MuleServer.run(MuleServer.java:203)
        at org.mule.MuleServer.start(MuleServer.java:191)
        at org.mule.MuleServer.main(MuleServer.java:162)

at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)

Pete

unread,

May 27, 2007, 2:31:28 PM5/27/07

to us...@mule.codehaus.org

Ok, missed that jira issue, but it is same.

disabling exception on getConnectorByProtocol will always return first
connector if I see it right.

Should do match for 'connector' attribute on endpoint, but I do not know
mule internals so well where to do it :)

Anyway, I'll take look on monday if I can figure it out.

Thanks,

Andrew Perepelytsya <aper...@gmail.com> kirjoitti Sun, 27 May 2007
20:53:47 +0300:

>> 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:585)
>> at
>> com.intellij.rt.execution.application.AppMain.main(AppMain.java
>> :90)
>>
>> Is this config error or something on 1.4?
>>
>> Thanks,
>>
>>
>>
>>
>> ___________________________________________________________
>> The all-new Yahoo! Mail goes wherever you go - free your email address
>> from your Internet provider. http://uk.docs.yahoo.com/nowyoucan.html
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list please visit:
>>
>> http://xircles.codehaus.org/manage_email
>>
>>

--
Käytössä Operan vallankumouksellinen sähköpostiohjelma:
http://www.opera.com/mail/

___________________________________________________________
All new Yahoo! Mail "The new Interface is stunning in its simplicity and ease of use." - PC Magazine

Reply all

Reply to author

Forward