JMX is enabled by default... so this is because of the fact that Callout
mediator creates and endpoint and calls the send on that, since that
doesn't have a name the name of the endpoint will be anonymous and on
the second message onwards it will through this error since the endpoint
is going to be anonymous in all the cases.

This has no harm for the functionality though; I will get this fixed for
the next version.

Thanks,
Ruwan

Harm Verhagen wrote:
> Hi,
>
> I noticed that whenever I put a call-out mediator in my synapse.xml I
> get exceptions in the logging.
> Everything seems to work fine, but still the exception look alarming.
>
> synapse.xml snippet.
> If you put the following in in a sequence I get errors when I press
> update/save.
>
>        <syn:source
> xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:ns="http://org.apache.synapse/xsd";
> xmlns:ns2="http://org.apache.synapse/xsd"; xpath="s11:Body/getFoo"/>
>             <syn:target
> xmlns:s11="http://schemas.xmlsoap.org/soap/envelope/";
> xmlns:ns="http://org.apache.synapse/xsd";
> xmlns:ns2="http://org.apache.synapse/xsd";
> xpath="s11:Body/getFooResponse"/>
>         </syn:callout>
>
> exceptions:
> [2009-08-27 14:16:12,875]  WARN - TransportMBeanSupport Error
> registering a MBean with objectname ' org.apache.synapse:T
> ype=Transport,ConnectorName=jms-sender ' for JMX management
> javax.management.InstanceAlreadyExistsException:
> org.apache.synapse:Type=Transport,ConnectorName=jms-sender
>         at
> com.sun.jmx.mbeanserver.RepositorySupport.addMBean(RepositorySupport.java:452)
>         at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1
> 410)
>         at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:936)
>         at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:337)
>         at
> com.sun.jmx.mbeanserver.JmxMBeanServer.registerMBean(JmxMBeanServer.java:497)
>         at
> org.apache.axis2.transport.base.TransportMBeanSupport.register(TransportMBeanSupport.java:91)
>         at
> org.apache.axis2.transport.base.AbstractTransportSender.init(AbstractTransportSender.java:84)
>         at
> org.apache.axis2.transport.jms.JMSSender.init(JMSSender.java:61)
>         at
> org.apache.axis2.context.ConfigurationContextFactory.initTransportSenders(ConfigurationContextFactory.java:30
> ....
> [2009-08-27 14:16:13,078]  WARN - TransportMBeanSupport Error
> registering a MBean with objectname ' org.apache.synapse:T
> ype=Transport,ConnectorName=mailto-listener ' for JMX management
> javax.management.InstanceAlreadyExistsException:
> org.apache.synapse:Type=Transport,ConnectorName=mailto-listener
>         at
> com.sun.jmx.mbeanserver.RepositorySupport.addMBean(RepositorySupport.java:452)
>         at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.internal_addObject(DefaultMBeanServerInterceptor.java:1
> 410)
>         at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerObject(DefaultMBeanServerInterceptor.java:936)
>         at
> com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.registerMBean(DefaultMBeanServerInterceptor.java:337)
> ...
> ....
>
> Afaik I don't use jmx.
>
>
> Regards,
> Harm
> ------------------------------------------------------------------------
>
> _______________________________________________
> Esb-java-user mailing list
> [email protected]
> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
>   


-- 
Ruwan Linton
Technical Lead & Product Manager; WSO2 ESB; http://wso2.org/esb
WSO2 Inc.; http://wso2.org
email: [email protected]; cell: +94 77 341 3097
blog: http://blog.ruwan.org



_______________________________________________
Esb-java-user mailing list
[email protected]
https://wso2.org/cgi-bin/mailman/listinfo/esb-java-user

Reply via email to