Nabble - Mule - User

Re: How to send Map type messages

2009-12-22T13:44:29Z

Thanks so much for the replies.

I have found the code that can send Mapmessages using Map holding other maps, but the code works in TIBCO messages, not IBM MQ. I have tried to modify it, just no luck. Anyone knows how to use MapMessage properties?

public class ObjectToEMSMessage extends AbstractJmsTransformer
{
public static final String JMS_TIBCO_MSG_EXT = "JMS_TIBCO_MSG_EXT";

public static final String JMS_TIBCO_PRESERVE_UNDELIVERED = "JMS_TIBCO_PRESERVE_UNDELIVERED";

private static transient Log logger = LogFactory.getLog(ObjectToEMSMessage.class);

private static final long serialVersionUID = 1547034901937834003L;

/* (non-Javadoc)
* @see org.mule.transformer.AbstractMessageAwareTransformer#transform(org.mule.api.MuleMessage, java.lang.String)
*/
public Object transform(MuleMessage message, String outputStr) throws TransformerException
{
Object src = message.getPayload();
Object result = null;

try
{
if (logger.isDebugEnabled())
{
logger.debug("Source object is " + src.getClass().getName());
}

// we want to use embedded MapMessages for translation
// to RV, a simple MapMessage won't work, because it creates
// a flat message as opposed to multiple levels of nesting.
// EMS supports this via an extended implementation
//
if (src instanceof Map)
{
result = getMapMessageForMap((Map) src);
logger.debug("Transformed object to JMS message: " + result);
}
else
{
result = transformToMessage(message);
}

// Setting the EMS Specific properties here.
// AbstractJmsTransformer swallows the custom properties which start
// with "JMS",
// hence these properties are set here.
((Message) result).setBooleanProperty(JMS_TIBCO_PRESERVE_UNDELIVERED, true);

if (logger.isDebugEnabled())
{
logger.debug("Resulting object is " + result.getClass().getName());
}
}
catch (Exception e)
{
throw new TransformerException(this, e);
}
return result;
}

private Object getMapMessageForMap(Map map) throws JMSException, TransformerException
{
MapMessage mapMsg;
try
{
// let's just get an empty message, we need to turn on extended
// properties to properly create maps of maps
mapMsg = (MapMessage) transformToMessage(new DefaultMuleMessage(new HashMap()));
logger.debug("************* Get mapMsg :" + mapMsg);
mapMsg.setBooleanProperty(JMS_TIBCO_MSG_EXT, true);

Map.Entry entry = null;

for (Iterator i = map.entrySet().iterator(); i.hasNext();)
{
entry = (Map.Entry) i.next();
if (entry.getValue() instanceof Map)
{
// recurse
mapMsg.setObject(entry.getKey().toString(), getMapMessageForMap((Map) entry.getValue()));
}
else
{
mapMsg.setObject(entry.getKey().toString(), entry.getValue());
}
}
}
catch (JMSException e)
{
logger.error(e);
throw e;
}

return mapMsg;
}

}

zhifangchang wrote:

We want to send a message in format of TreeMap, which holds its key in String, and its value in HashMap, but we run into exceptions(see below). I have posted the part of the mule-config below. We have defined a custom transformer from Map to JMSMesssage using Mule's ObjectToJMSMessage and tried in mule2.2.1, just no luck. Our application is running in JBOSS and IBM MQ. Any one has ideas on this issue? Is there something special we need to handle in order to send a message in format of TreeMap<String, HashMap>? Thanks!

009-12-22 14:21:34,186 ERROR [jmsXAQueueConnector.dispatcher.24] mule.AbstractExceptionListener (AbstractExceptionListener.java:390) -
********************************************************************************
Message : JMSCC0083: An incorrect object of type 'java.util.HashMap' was provided. (com.ibm.msg.client.jms.DetailedMessageFormatException)
Type : org.mule.api.transformer.TransformerException
Code : MULE_ERROR-64999
Transformer : ObjectToJMSMessage{this=1e37fd24, name='MapToJMSMessage', ignoreBadInput=false, returnClass=interface javax.jms.MapMessage, sourceTypes=[]}
JMS Code : JMSCC0083
JavaDoc : http://www.mulesource.org/docs/site/current2/apidocs/org/mule/api/transformer/TransformerException.html
********************************************************************************
Exception stack is:
1. JMSCC0083: An incorrect object of type 'java.util.HashMap' was provided.(JMS Code: JMSCC0083) (com.ibm.msg.client.jms.DetailedMessageFormatException)
sun.reflect.NativeConstructorAccessorImpl:-2 (null)
2. JMSCC0083: An incorrect object of type 'java.util.HashMap' was provided. (com.ibm.msg.client.jms.DetailedMessageFormatException) (org.mule.api.transformer.TransformerException)
org.mule.transport.jms.transformers.AbstractJmsTransformer:80 (http://www.mulesource.org/docs/site/current2/apidocs/org/mule/api/transformer/TransformerException.html)
********************************************************************************
Root Exception stack trace:
com.ibm.msg.client.jms.DetailedMessageFormatException: JMSCC0083: An incorrect object of type 'java.util.HashMap' was provided. An object was provided to the writeObject() method that was not a Java(tm) primitive wrapper type. Correct the application to ensure that only objects of the permitted types are passed as parameters to the writeObject() method.
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at com.ibm.msg.client.commonservices.j2se.NLSServices.createException(NLSServices.java:313)
at com.ibm.msg.client.commonservices.nls.NLSServices.createException(NLSServices.java:390)
at com.ibm.msg.client.jms.internal.JmsErrorUtils.createException(JmsErrorUtils.java:104)
at com.ibm.msg.client.jms.internal.JmsMapMessageImpl.setObject(JmsMapMessageImpl.java:795)
at com.ibm.jms.JMSMapMessage.setObject(JMSMapMessage.java:622)
at org.mule.transport.jms.JmsMessageUtils.toMessage(JmsMessageUtils.java:129)
at org.mule.transport.jms.transformers.AbstractJmsTransformer.transformToMessage(AbstractJmsTransformer.java:67)
at org.mule.transport.jms.transformers.ObjectToJMSMessage.transform(ObjectToJMSMessage.java:50)
at org.mule.transformer.AbstractMessageAwareTransformer.doTransform(AbstractMessageAwareTransformer.java:68)
at org.mule.transformer.AbstractTransformer.transform(AbstractTransformer.java:254)
at org.mule.DefaultMuleMessage.applyAllTransformers(DefaultMuleMessage.java:620)
at org.mule.DefaultMuleMessage.applyTransformers(DefaultMuleMessage.java:581)
at org.mule.DefaultMuleMessage.applyTransformers(DefaultMuleMessage.java:574)
at org.mule.DefaultMuleEvent.transformMessage(DefaultMuleEvent.java:326)
at org.mule.DefaultMuleEvent.transformMessage(DefaultMuleEvent.java:321)
at org.mule.transport.jms.JmsMessageDispatcher.dispatchMessage(JmsMessageDispatcher.java:151)
at org.mule.transport.jms.JmsMessageDispatcher.doDispatch(JmsMessageDispatcher.java:72)
at org.mule.transport.AbstractMessageDispatcher$Worker.run(AbstractMessageDispatcher.java:262)
at org.mule.work.WorkerContext.run(WorkerContext.java:310)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
at java.lang.Thread.run(Thread.java:595)

********************************************************************************

<custom-transformer name="MapToJMSMessage"
class="org.mule.transport.jms.transformers.ObjectToJMSMessage"
returnClass="javax.jms.MapMessage" />

<service name="AcctWFM_TO_AdapterBO_TO_BO">
<inbound>
<jms:inbound-endpoint ref="BAO"
transformer-refs="JMSMessageToObject">
</jms:inbound-endpoint>
</inbound>
<component
class="com.lehman.tradepath.adapter.accounting.AdapterBO" />
<outbound>
<custom-outbound-router
class="com.lehman.tradepath.mule.FilteringListMessageSplitter">
<jms:outbound-endpoint ref="BO_NOTIFICATION"
transformer-refs="MapToJMSMessage">

<payload-type-filter
expectedType="java.util.Map" />
</jms:outbound-endpoint>
<payload-type-filter expectedType="java.util.List" />
</custom-outbound-router>
</outbound>
</service>

Re: Re: how to access property value from component.

2009-12-22T12:59:48Z

NVM, :-).. I got it figured out.. I was using the wrong transformer on the inbound.
Everything works good now!

~matt

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

http://xircles.codehaus.org/manage_email

Quartz started FTP onle gets one (1) file

2009-12-22T12:59:31Z

Hello,

I have the following configuration:

<ftp:endpoint name="FtpEndpoint" path="export/home/enno/scanbatch/in"
port="21" user="enno" password="********" host="localhost" binary="true" passive="true">
</ftp:endpoint>

<file:connector name="fileOutboundConnector"
outputPattern="#[header:originalFilename|http://forums.mulesoft.org/]">
<file:expression-filename-parser />
</file:connector>

<model name="main">
<service name="testService">

<inbound>
<quartz:inbound-endpoint name="FTP"
cronExpression="0,30 * * * * ?" jobName="job1">
<quartz:endpoint-polling-job>
<quartz:job-endpoint ref="FtpEndpoint" />
</quartz:endpoint-polling-job>
</quartz:inbound-endpoint>
</inbound>

<outbound>
<pass-through-router>
<file:outbound-endpoint path="/export/home/enno/scanbatch/out"
connector-ref="fileOutboundConnector" />
</pass-through-router>
</outbound>
</service>
</model>
</mule>

I have multiple files in the 'in' directory.
When I comment-out the quartz inbound part and use the ftp inbound part, all the files in the 'in' directory are ftp-ed into the 'out' directoryand the 'in' directory becomes empty..
But when I use quartz the start the FTP-ing and comment out the FTP inbound (as can be seen in the configuration above), only one/just one, of the files in my 'in' directory is FTP-ed into the 'out' directory and also stays available in the 'in' directory.

Can anyone tell me what I do wrong here and how I can use quartz to start a FTP session which copies all the files from an 'in' to an 'out' directory?

Best regards,

Enno.

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

http://xircles.codehaus.org/manage_email

Re: how to access property value from component.

2009-12-22T12:32:49Z

Matt,

Remove the object-to-string transformer and the OrdersXmlToList from your file:inbound-endpoint, but hold the XmlToDom and addOrderId. This way the ReceiverFileInputStream will be transformed to a DOM tree (assuming the file is an XML file) and the addOrderId will pick the right element and stores it in a message property.

You are saying that the mule-xml namespace doesn't work. Have you added the right schemaLocation for this namespace (http://www.mulesource.org/schema/mule/xml/2.2/mule-xml.xsd)?

HTH
Mario

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

http://xircles.codehaus.org/manage_email

Re: Re: how to access property value from component.

2009-12-22T12:26:35Z

It is basically a ping service provider. Anyway, the transformer thing doesn't work, it seems to want a different namespace for <mule-xml:xml-to-dom-transformer name="XmlToDom" returnClass="org.w3c.dom.Document" /> in which I am using xmlns:mule-xml="http://www.mulesource.org/schema/mule/xml/2.2

Can you show the error you get here? Because this should work and is probably you best shot, as Mario said.

Re: how to access property value from component.

2009-12-22T12:19:55Z

java.lang.ClassCastException: org.mule.transport.file.ReceiverFileInputStream
at com.zipinstalls.connect.esb.service.volusion.component.VolusionCheckNewOrderStatusService.onCall(VolusionCheckNewOrderStatusService.java:35)
at org.mule.model.resolvers.CallableEntryPointResolver.invoke(CallableEntryPointResolver.java:52)
at org.mule.model.resolvers.DefaultEntryPointResolverSet.invoke(DefaultEntryPointResolverSet.java:50)
at org.mule.component.DefaultLifecycleAdapter.invoke(DefaultLifecycleAdapter.java:205)
at org.mule.component.AbstractJavaComponent.invokeComponentInstance(AbstractJavaComponent.java:83)
at org.mule.component.AbstractJavaComponent.doInvoke(AbstractJavaComponent.java:74)
at org.mule.component.AbstractComponent.invokeInternal(AbstractComponent.java:133)
at org.mule.component.AbstractComponent.invoke(AbstractComponent.java:161)
at org.mule.service.AbstractService.invokeComponent(AbstractService.java:929)
at org.mule.model.seda.SedaService.access$100(SedaService.java:56)
at org.mule.model.seda.SedaService$ComponentStageWorker.run(SedaService.java:574)
at org.mule.work.WorkerContext.run(WorkerContext.java:310)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$CallerRunsPolicy.rejectedExecution(ThreadPoolExecutor.java:1895)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:765)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1288)
at org.mule.work.ScheduleWorkExecutor.doExecute(ScheduleWorkExecutor.java:41)
at org.mule.work.MuleWorkManager.executeWork(MuleWorkManager.java:268)
at org.mule.work.MuleWorkManager.scheduleWork(MuleWorkManager.java:231)
at org.mule.model.seda.SedaService.run(SedaService.java:380)
at org.mule.work.WorkerContext.run(WorkerContext.java:310)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
at java.lang.Thread.run(Thread.java:613)
INFO 2009-12-22 14:13:01,494 [volusionInboundFileConnector.dispatcher.15] org.mule.transport.file.FileMessageDispatcher: Connected: endpoint.outbound.file://data/volusion/orders/order
[Fatal Error] :-1:-1: Premature end of file.
ERROR: 'Premature end of file.'
ERROR 2009-12-22 14:13:01,513 [volusionInboundFileConnector.dispatcher.15] org.mule.DefaultExceptionStrategy:

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

http://xircles.codehaus.org/manage_email

Re: how to access property value from component.

2009-12-22T12:15:01Z

The thing is that it is not reading as such.. here is the service I am trying to stand up..

<service name="volusion-new-order-inbound">
<inbound>
<file:inbound-endpoint path="${volusion.inbound.new.path}" pollingFrequency="5000"
connector-ref="volusionInboundFileConnector" >

<object-to-string-transformer />
<transformer refs="OrdersXmlToList XmlToDom addOrderId" />
</file:inbound-endpoint>
</inbound>
<component>
<spring-object bean="volusionCheckNewOrderStatusService" >

</spring-object>
</component>
<outbound>

<filtering-router>
<file:outbound-endpoint path="${volusion.inbound.new.path}"
outputPattern="#[xpath:/xmldata/Orders/OrderID].xml" connector-ref="volusionInboundFileConnector" />
<regex-filter pattern="OrderStatus\>New.*/OrderStatus\>" />
</filtering-router>
<forwarding-catch-all-strategy>
<file:outbound-endpoint path="${volusion.order.path}"
outputPattern="#[function:datestamp:yyyy-MM-dd_HH-mm-ss.S]-id-#[xpath:/xmldata/Orders/OrderID].xml" connector-ref="volusionInboundFileConnector" />
</forwarding-catch-all-strategy>

</outbound>
</service>

It is basically a ping service provider. Anyway, the transformer thing doesn't work, it seems to want a different namespace for <mule-xml:xml-to-dom-transformer name="XmlToDom" returnClass="org.w3c.dom.Document" /> in which I am using xmlns:mule-xml="http://www.mulesource.org/schema/mule/xml/2.2

As far as why I can't use the inbound.. I dunno, I would love to.. but the Callable interface seems to keep passing me a mule message of ReceiverFileInputStream and won't let me cast java.lang.ClassCastException: org.mule.transport.file.ReceiverFileInputStream. Any input on how to make that work would be even better. I have managed to get everything else going except this, and I am a newb to this platform.

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

http://xircles.codehaus.org/manage_email

Re: How to send Map type messages

2009-12-22T12:10:03Z

According to the specs the value of a JMSMapMessage are primitives, so you cannot pass a HashMap as a value.

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

http://xircles.codehaus.org/manage_email

Re: Enable Statistics w/out using JXM?

2009-12-22T12:03:50Z

Also, you can read http://blogs.mulesoft.org/start-me-oh-so-gently/ and create a trivial startup class to enable it automatically. Then again, it's all about how you export the data to the outside world.

HTH,
Andrew

On Tue, Dec 22, 2009 at 2:17 PM, Mike Manske <mule.user.relay@...> wrote:

JMX may not be the best fit for me, but I would like to track with statistics. Is it possible to enable stats on the mule context via the config?

The only way I found to do it was in a script component, but that was burdensome, did not count the first message (which sets enable).

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

http://xircles.codehaus.org/manage_email

Re: Enabling statistics w/out JMX?

2009-12-22T11:54:04Z

We do exactly the same. Enable JMX statistics and export the statistics as csv over a simple http call instead of JMX.

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

http://xircles.codehaus.org/manage_email

Re: How to send Map type messages

2009-12-22T11:53:19Z

Hi,

JMS Map messages do not support Map as a valid value type.

You have to follow another path like serializing your Treemap payload into binary or XML (using one of Mule's existing filters) and let Mule's JMS transport default ObjectToJMS transformer turn it into a JMS BytesMessage or a JMS TextMessage.

HTH

On Tue, Dec 22, 2009 at 11:42 AM, zhifangchang <Fanny.Chang@...> wrote:

We want to send a message in format of TreeMap, which holds its key in
String, and its value in HashMap, but we run into exceptions(see below). I
have posted the part of the mule-config below. We have defined a custom
transformer from Map to JMSMesssage using Mule's ObjectToJMSMessage and
tried in mule2.2.1, just no luck. Our application is running in JBOSS and
IBM MQ. Any one has ideas on this issue? Is there something special we need
to handle in order to send a message in format of TreeMap<String, HashMap>?
Thanks!

009-12-22 14:21:34,186 ERROR [jmsXAQueueConnector.dispatcher.24]
mule.AbstractExceptionListener (AbstractExceptionListener.java:390) -
********************************************************************************
Message : JMSCC0083: An incorrect object of type
'java.util.HashMap' was provided.
(com.ibm.msg.client.jms.DetailedMessageFormatException)
Type : org.mule.api.transformer.TransformerException
Code : MULE_ERROR-64999
Transformer : ObjectToJMSMessage{this=1e37fd24,
name='MapToJMSMessage', ignoreBadInput=false, returnClass=interface
javax.jms.MapMessage, sourceTypes=[]}
JMS Code : JMSCC0083
JavaDoc :
http://www.mulesource.org/docs/site/current2/apidocs/org/mule/api/transformer/TransformerException.html
********************************************************************************
Exception stack is:
1. JMSCC0083: An incorrect object of type 'java.util.HashMap' was
provided.(JMS Code: JMSCC0083)
(com.ibm.msg.client.jms.DetailedMessageFormatException)
sun.reflect.NativeConstructorAccessorImpl:-2 (null)
2. JMSCC0083: An incorrect object of type 'java.util.HashMap' was provided.
(com.ibm.msg.client.jms.DetailedMessageFormatException)
(org.mule.api.transformer.TransformerException)
org.mule.transport.jms.transformers.AbstractJmsTransformer:80
(http://www.mulesource.org/docs/site/current2/apidocs/org/mule/api/transformer/TransformerException.html)
********************************************************************************
Root Exception stack trace:
com.ibm.msg.client.jms.DetailedMessageFormatException: JMSCC0083: An
incorrect object of type 'java.util.HashMap' was provided. An object was
provided to the writeObject() method that was not a Java(tm) primitive
wrapper type. Correct the application to ensure that only objects of the
permitted types are passed as parameters to the writeObject() method.
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at
com.ibm.msg.client.commonservices.j2se.NLSServices.createException(NLSServices.java:313)
at
com.ibm.msg.client.commonservices.nls.NLSServices.createException(NLSServices.java:390)
at
com.ibm.msg.client.jms.internal.JmsErrorUtils.createException(JmsErrorUtils.java:104)
at
com.ibm.msg.client.jms.internal.JmsMapMessageImpl.setObject(JmsMapMessageImpl.java:795)
at com.ibm.jms.JMSMapMessage.setObject(JMSMapMessage.java:622)
at
org.mule.transport.jms.JmsMessageUtils.toMessage(JmsMessageUtils.java:129)
at
org.mule.transport.jms.transformers.AbstractJmsTransformer.transformToMessage(AbstractJmsTransformer.java:67)
at
org.mule.transport.jms.transformers.ObjectToJMSMessage.transform(ObjectToJMSMessage.java:50)
at
org.mule.transformer.AbstractMessageAwareTransformer.doTransform(AbstractMessageAwareTransformer.java:68)
at
org.mule.transformer.AbstractTransformer.transform(AbstractTransformer.java:254)
at
org.mule.DefaultMuleMessage.applyAllTransformers(DefaultMuleMessage.java:620)
at
org.mule.DefaultMuleMessage.applyTransformers(DefaultMuleMessage.java:581)
at
org.mule.DefaultMuleMessage.applyTransformers(DefaultMuleMessage.java:574)
at org.mule.DefaultMuleEvent.transformMessage(DefaultMuleEvent.java:326)
at org.mule.DefaultMuleEvent.transformMessage(DefaultMuleEvent.java:321)
at
org.mule.transport.jms.JmsMessageDispatcher.dispatchMessage(JmsMessageDispatcher.java:151)
at
org.mule.transport.jms.JmsMessageDispatcher.doDispatch(JmsMessageDispatcher.java:72)
at
org.mule.transport.AbstractMessageDispatcher$Worker.run(AbstractMessageDispatcher.java:262)
at org.mule.work.WorkerContext.run(WorkerContext.java:310)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
at java.lang.Thread.run(Thread.java:595)

********************************************************************************

<custom-transformer name="MapToJMSMessage"
class="org.mule.transport.jms.transformers.ObjectToJMSMessage"
returnClass="javax.jms.MapMessage" />

<service name="AcctWFM_TO_AdapterBO_TO_BO">
<inbound>
<jms:inbound-endpoint ref="BAO"
transformer-refs="JMSMessageToObject">
</jms:inbound-endpoint>
</inbound>
<component
class="com.lehman.tradepath.adapter.accounting.AdapterBO" />
<outbound>
<custom-outbound-router
class="com.lehman.tradepath.mule.FilteringListMessageSplitter">
<jms:outbound-endpoint ref="BO_NOTIFICATION"
transformer-refs="MapToJMSMessage">

<payload-type-filter
expectedType="java.util.Map" />
</jms:outbound-endpoint>
<payload-type-filter expectedType="java.util.List" />
</custom-outbound-router>
</outbound>
</service>
--
View this message in context: http://old.nabble.com/How-to-send-Map-type-messages-tp26893223p26893223.html
Sent from the Mule - User mailing list archive at Nabble.com.

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

http://xircles.codehaus.org/manage_email

Re: how to access property value from component.

2009-12-22T11:50:14Z

But the question is: Why is this necessary?

If I look a little bit closer to your code, it seems that your payload is already a JAXB java object. So getting the orderId from the payload in your service as you already do in your code is just fine.

Mario

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

http://xircles.codehaus.org/manage_email

How to send Map type messages

2009-12-22T11:42:42Z

We want to send a message in format of TreeMap, which holds its key in String, and its value in HashMap, but we run into exceptions(see below). I have posted the part of the mule-config below. We have defined a custom transformer from Map to JMSMesssage using Mule's ObjectToJMSMessage and tried in mule2.2.1, just no luck. Our application is running in JBOSS and IBM MQ. Any one has ideas on this issue? Is there something special we need to handle in order to send a message in format of TreeMap<String, HashMap>? Thanks!

009-12-22 14:21:34,186 ERROR [jmsXAQueueConnector.dispatcher.24] mule.AbstractExceptionListener (AbstractExceptionListener.java:390) -
********************************************************************************
Message : JMSCC0083: An incorrect object of type 'java.util.HashMap' was provided. (com.ibm.msg.client.jms.DetailedMessageFormatException)
Type : org.mule.api.transformer.TransformerException
Code : MULE_ERROR-64999
Transformer : ObjectToJMSMessage{this=1e37fd24, name='MapToJMSMessage', ignoreBadInput=false, returnClass=interface javax.jms.MapMessage, sourceTypes=[]}
JMS Code : JMSCC0083
JavaDoc : http://www.mulesource.org/docs/site/current2/apidocs/org/mule/api/transformer/TransformerException.html
********************************************************************************
Exception stack is:
1. JMSCC0083: An incorrect object of type 'java.util.HashMap' was provided.(JMS Code: JMSCC0083) (com.ibm.msg.client.jms.DetailedMessageFormatException)
sun.reflect.NativeConstructorAccessorImpl:-2 (null)
2. JMSCC0083: An incorrect object of type 'java.util.HashMap' was provided. (com.ibm.msg.client.jms.DetailedMessageFormatException) (org.mule.api.transformer.TransformerException)
org.mule.transport.jms.transformers.AbstractJmsTransformer:80 (http://www.mulesource.org/docs/site/current2/apidocs/org/mule/api/transformer/TransformerException.html)
********************************************************************************
Root Exception stack trace:
com.ibm.msg.client.jms.DetailedMessageFormatException: JMSCC0083: An incorrect object of type 'java.util.HashMap' was provided. An object was provided to the writeObject() method that was not a Java(tm) primitive wrapper type. Correct the application to ensure that only objects of the permitted types are passed as parameters to the writeObject() method.
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at com.ibm.msg.client.commonservices.j2se.NLSServices.createException(NLSServices.java:313)
at com.ibm.msg.client.commonservices.nls.NLSServices.createException(NLSServices.java:390)
at com.ibm.msg.client.jms.internal.JmsErrorUtils.createException(JmsErrorUtils.java:104)
at com.ibm.msg.client.jms.internal.JmsMapMessageImpl.setObject(JmsMapMessageImpl.java:795)
at com.ibm.jms.JMSMapMessage.setObject(JMSMapMessage.java:622)
at org.mule.transport.jms.JmsMessageUtils.toMessage(JmsMessageUtils.java:129)
at org.mule.transport.jms.transformers.AbstractJmsTransformer.transformToMessage(AbstractJmsTransformer.java:67)
at org.mule.transport.jms.transformers.ObjectToJMSMessage.transform(ObjectToJMSMessage.java:50)
at org.mule.transformer.AbstractMessageAwareTransformer.doTransform(AbstractMessageAwareTransformer.java:68)
at org.mule.transformer.AbstractTransformer.transform(AbstractTransformer.java:254)
at org.mule.DefaultMuleMessage.applyAllTransformers(DefaultMuleMessage.java:620)
at org.mule.DefaultMuleMessage.applyTransformers(DefaultMuleMessage.java:581)
at org.mule.DefaultMuleMessage.applyTransformers(DefaultMuleMessage.java:574)
at org.mule.DefaultMuleEvent.transformMessage(DefaultMuleEvent.java:326)
at org.mule.DefaultMuleEvent.transformMessage(DefaultMuleEvent.java:321)
at org.mule.transport.jms.JmsMessageDispatcher.dispatchMessage(JmsMessageDispatcher.java:151)
at org.mule.transport.jms.JmsMessageDispatcher.doDispatch(JmsMessageDispatcher.java:72)
at org.mule.transport.AbstractMessageDispatcher$Worker.run(AbstractMessageDispatcher.java:262)
at org.mule.work.WorkerContext.run(WorkerContext.java:310)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
at java.lang.Thread.run(Thread.java:595)

********************************************************************************

<custom-transformer name="MapToJMSMessage"
class="org.mule.transport.jms.transformers.ObjectToJMSMessage"
returnClass="javax.jms.MapMessage" />

<service name="AcctWFM_TO_AdapterBO_TO_BO">
<inbound>
<jms:inbound-endpoint ref="BAO"
transformer-refs="JMSMessageToObject">
</jms:inbound-endpoint>
</inbound>
<component
class="com.lehman.tradepath.adapter.accounting.AdapterBO" />
<outbound>
<custom-outbound-router
class="com.lehman.tradepath.mule.FilteringListMessageSplitter">
<jms:outbound-endpoint ref="BO_NOTIFICATION"
transformer-refs="MapToJMSMessage">

<payload-type-filter
expectedType="java.util.Map" />
</jms:outbound-endpoint>
<payload-type-filter expectedType="java.util.List" />
</custom-outbound-router>
</outbound>
</service>

Re: how to access property value from component.

2009-12-22T11:40:27Z

I think whatyou are trying to achieve is the following:

1) Get the OrderId from the payload and store this as a property orderId to the message
2) In your service you want to pick the orderId and the order and do something with it.

What you try to do is set a property on the spring bean. This is not correct.

For step 1 you could use the message-property-transformer, see the example below:

<message-properties-transformer name="addOrderId">
<add-message-property key="orderId" value="#[xpath:/xmldata/Orders/OrderID]"/>
</message-properties-transformer>
<mule-xml:xml-to-dom-transformer
name="XmlToDom" returnClass="org.w3c.dom.Document" />

<model name="PropertyExample">
<service name="my-service">
<inbound>
<vm:inbound-endpoint path="inbound-channel"
transformer-refs="XmlToDom addOrderId"/>
</inbound>
<component>
<spring-object bean="yourSpringBean" />
</component>
</service>
</model>

HTH

Regards,

Mario Klaver

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

http://xircles.codehaus.org/manage_email

Enable Statistics w/out using JXM?

2009-12-22T11:17:34Z

JMX may not be the best fit for me, but I would like to track with statistics. Is it possible to enable stats on the mule context via the config?

The only way I found to do it was in a script component, but that was burdensome, did not count the first message (which sets enable).

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

http://xircles.codehaus.org/manage_email

Re: Enabling statistics w/out JMX?

2009-12-22T11:15:52Z

sorry - posted to the wrong forum.

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

http://xircles.codehaus.org/manage_email

Re: Enabling statistics w/out JMX?

2009-12-22T11:07:17Z

Why is it a problem for you? Just enable JMX locally, you don't have to create a remote server connector.

Andrew

On Tue, Dec 22, 2009 at 2:06 PM, Mike Manske <mule.user.relay@...> wrote:

JMX may not be the best fit for me, but I would like to track with statistics. Is it possible to enable stats on the mule context via the config?

The only way I found to do it was in a script component, but that was burdensome, did not count the first message (which sets enable).

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

http://xircles.codehaus.org/manage_email

Enabling statistics w/out JMX?

2009-12-22T11:06:08Z

how to access property value from component.

2009-12-22T10:47:38Z

I am getting frustrated not being able to access the orderId property value.

<component>
<spring-object bean="volusionCheckNewOrderStatusService" >
<property key="orderId" value="#[xpath:/xmldata/Orders/OrderID]" />
</spring-object>
</component>

-------------------------------------
Here is the component. - Note: I have tried several things to get this value... as seen.

package com.zipinstalls.connect.esb.service.volusion.component;

import org.apache.commons.lang.StringUtils;
import org.apache.log4j.Logger;
import org.mule.api.MuleEventContext;
import org.mule.api.lifecycle.Callable;

import com.zipinstalls.connect.esb.common.component.base.BaseOrderService;
import com.zipinstalls.connect.esb.service.volusion.api.http.orders.VolusionSingleOrderDao;
import com.zipinstalls.connect.esb.service.volusion.api.jaxb.orders.Xmldata.Orders;
import com.zipinstalls.connect.esb.service.volusion.message.VolusionOrderData;

public class VolusionCheckNewOrderStatusService implements Callable {
private static final String EMPTY_XML_DATA_ELEMENT = "<xmldata />";
private VolusionSingleOrderDao order;
private int orderId;
private static final Logger logger = Logger.getLogger(VolusionCheckNewOrderStatusService.class);

public VolusionSingleOrderDao getOrder() {
return order;
}

public void setOrder(VolusionSingleOrderDao order) {
this.order = order;
}
public void volusionCheckNewOrder(VolusionOrderData orderData) {

}

public Object onCall(MuleEventContext eventContext) throws Exception {
String xmlData ="";
try {
VolusionOrderData volusionOrderData = new VolusionOrderData();
logger.info(eventContext.getMessage().getProperty("orderId"));
volusionOrderData.setOrderXmlData((com.zipinstalls.connect.esb.service.volusion.api.jaxb.orders.Xmldata) eventContext.getMessage().getPayload());
logger.info("THE ORDER IS THIS!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!"+volusionOrderData.getOrderXmlData().getOrders().get(0).getOrderID());
xmlData = this.getOrder().findOrderWithId(volusionOrderData.getOrderXmlData().getOrders().get(0).getOrderID());
//(xmlData);
if (xmlData.matches("OrderStatus>New.*/OrderStatus>")) {
eventContext.setStopFurtherProcessing(true);
return null;
}
xmlData = xmlData.replaceAll("&","And");
logger.info(xmlData);
} catch (Exception e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
return xmlData;
}

public int getOrderId() {
return orderId;
}

public void setOrderId(int orderId) {
this.orderId = orderId;
}

}

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

http://xircles.codehaus.org/manage_email

Re: File transport writeToDirectory and path questions

2009-12-22T02:34:11Z

Mario,

Thanks, that worked great!.

Cheers,

Enno.

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

http://xircles.codehaus.org/manage_email

Re: File transport writeToDirectory and path questions

2009-12-22T00:57:10Z

Enno,

I can't answer your questions, but you could work around your problem by setting the datestamp expression on your outputPattern instead of the writeToDirectory, like this:

<file:connector name="fileOutboundConnector" outputPattern="#[function:datestamp]/#[header:originalFilename]"
streaming="false">
<file:expression-filename-parser />
</file:connector>
<model name="FileExample">
<service name="enno-service">
<inbound>
<file:inbound-endpoint path="inbox"
pollingFrequency="3000" moveToDirectory="moveto" />
</inbound>
<outbound>
<pass-through-router>
<file:outbound-endpoint path="outbox"
connector-ref="fileOutboundConnector" />
</pass-through-router>
</outbound>
</service>
</model>

HTH

Mario Klaver

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

http://xircles.codehaus.org/manage_email

File transport writeToDirectory and path questions

2009-12-21T19:29:09Z

Hello,

I have the following configuration:

bq. <file:connector name="fileOutboundConnector" writeToDirectory="#[function:dateStamp-yyyy-MM-dd|http://forums.mulesoft.org/]" outputPattern="#[header:originalFilename|http://forums.mulesoft.org/]" streaming="false">
bq. bq. <file:expression-filename-parser />

bq. </file:connector> \\ <model name="FileExample">
bq. bq. <service name="enno-service">

bq. bq. bq. <inbound>

bq. bq. bq. bq. <file:inbound-endpoint path="inbox" \\ pollingFrequency="3000" moveToDirectory="moveto" />

bq. bq. bq. </inbound> \\ <outbound>

bq. bq. bq. bq. <pass-through-router>

bq. bq. bq. bq. bq. <file:outbound-endpoint path="outbox" connector-ref="fileOutboundConnector" />

bq. bq. bq. bq. </pass-through-router>

bq. bq. bq. </outbound>
</service>

bq. </model>

When I run this configuration I notice that mule first creates a directory with the name '#[function:dateStamp-yyyy-MM-dd|http://forums.mulesoft.org/]'
When I manually copy a file into the 'inbox' directory it is copied by mule to a (again) new created directory with the correct current date (2009-11-22). This is what I excepcted.

My questions are:

# Why is mule (also) creating the directory with the name '#[function:dateStamp-yyyy-MM-dd|http://forums.mulesoft.org/]'. This directory stays empty ?
# Why do I need to supply the/a 'path' on the file:outbound-endpoint, as it is not used ?

Best regards,

Enno.

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

http://xircles.codehaus.org/manage_email

Re: WSDL with CFX over JETTY-SSL substitures the wrong URL for the soap por

2009-12-21T14:38:29Z

Thanks for the info and the suggestion.

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

http://xircles.codehaus.org/manage_email

Re: WSDL with CFX over JETTY-SSL substitures the wrong URL for the soap port

2009-12-21T13:46:43Z

See http://www.mulesoft.org/jira/browse/MULE-4311

Perhaps you can fix this using a transformer.

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

http://xircles.codehaus.org/manage_email

WSDL with CFX over JETTY-SSL substitures the wrong URL for the soap port

2009-12-21T13:10:27Z

I have CFX over jetty-ssl to proxy a web service.

<service name="proxy">
<inbound>
<cxf:inbound-endpoint address="jetty-ssl://localhost:63081/StringTestService/services/StringServiceImpl"
proxy="true" synchronous="true" />
</inbound>

<outbound>
<chaining-router>
<cxf:outbound-endpoint
address="http://host3145.pharos.intuit.com:8080/StringTestService/services/StringServiceImpl"
proxy="true" synchronous="true"/>
</chaining-router>
</outbound>
</service>

When I retrieve the WSDL by calling https://localhost:63081/StringTestService/services/StringServiceImpl?wsdl
the returned bind port is wrong, having jetty-ssl as protocol.

<wsdl:port binding="tns:ProxyServiceSoapBinding" name="ProxyServicePort">
<soap:address location="jetty-ssl://localhost:63081/StringTestService/services/StringServiceImpl"/>
</wsdl:port>

Any idea of how to fix this?

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

http://xircles.codehaus.org/manage_email

Re: ActiveMQ JMS to persistent Mule VM queue - possible?

2009-12-21T08:14:08Z

Haha. Fine, you stink. ;)

Yes, I can confirm that's what is in the print version as well.

Seriously, the Mule in Action book has been fantastic and has already helped us on 3 small integration/proof-of-concept projects. So no worries and already looking forward to the next revision that covers Mule 3.x.

Andy

On Thu, Dec 17, 2009 at 6:29 PM, John D'Emic <john.demic@...> wrote:

Hey Andy,

Please level all criticism at me - I wrote this chapter :)

I don't have the print copy of Mule in Action handy at the moment, but the
PDF shows has the queue-profile defined outside the service on page 81
(right before the closing </model>)

Let me know if what you're seeing is different or if I'm missing something
obvious.

-jd

David Dossot-3 wrote:
>
>>
>> What's funny is that I was using that placement of the vm:queue-profile -
>> because of you! It's shown like that on p.80-81 of your book. Maybe a
>> typo?
>>
>
> Ouch. We'll look into that, sorry.
>
> D.
>
>

--
View this message in context: http://old.nabble.com/ActiveMQ-JMS-to-persistent-Mule-VM-queue---possible--tp26789398p26837842.html
Sent from the Mule - User mailing list archive at Nabble.com.

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

http://xircles.codehaus.org/manage_email

Re: Preserve message properties after a response from Multicasting router.

2009-12-21T05:17:10Z

The chaining router works just fine for me, I´ve never noticed it dropping previously set message properties. But your implimentation of the Chaining router could push me in the direction of a cleaner solution for my Multicasting Router issue.

I've used the following custom router implementation for this:

public class HeaderPropagatingChainingRouter extends ChainingRouter {

protected void processIntermediaryResult(MuleMessage localResult, MuleMessage intermediaryResult) {
for (Object key : intermediaryResult.getPropertyNames()) {
localResult.setProperty((String) key, intermediaryResult.getProperty((String) key));
}

}
}

This propagates the headers from each response to the next endpoint in the chain...

HTH
-jd

wb123 wrote:

Hi.
I´ve got a simple Mule config that goes something like this
Inbound request
Outbound chaining router
first outbound endpoint routes via VM to a multicasting router, synchronous, response transformer merges all the response payloads (String) into a single String.
Second outbound endpoint routes the merged response to a destination.

My "problem" is that going through the multicasting router and getting the response, I lose all the original message properties. I can conserve them by using another response transformer and getting the properties from the DefaultMessageCollection (and I´ve already done this), but I was wondering if there is a another, possibly simpler, way to preserve the message properties of the original inbound request.
Are there some context properties I can configure? Should I just expand my "responseMessagePropertiesCollector" transformer to loop over the whole DefaultMessageCollection and get all the properties from there?

Re: Preserve message properties after a response from Multicasting router.

2009-12-21T02:56:42Z

Hey Ross,

Opened here:

http://www.mulesoft.org/jira/browse/MULE-4687

Cheers,
-jd

Ross Mason-5 wrote:

Hi John,

Would you mind opening a Jira for this? we could just a flag to the current
chaining router.

Cheers,

Ross Mason
CTO, Founder
MuleSoft Inc.
http://twitter.com/rossmason

http://mulesoft.com | http://blog.rossmason.com

On Fri, Dec 18, 2009 at 2:38 AM, John D'Emic <john.demic@gmail.com> wrote:

>
> I've used the following custom router implementation for this:
>
> public class HeaderPropagatingChainingRouter extends ChainingRouter {
>
> protected void processIntermediaryResult(MuleMessage localResult,
> MuleMessage intermediaryResult) {
> for (Object key : intermediaryResult.getPropertyNames()) {
> localResult.setProperty((String) key,
> intermediaryResult.getProperty((String) key));
> }
>
> }
> }
>
> This propagates the headers from each response to the next endpoint in the
> chain...
>
> HTH
> -jd
>
>
> wb123 wrote:
> >
> > Hi.
> > I´ve got a simple Mule config that goes something like this
> > Inbound request
> > Outbound chaining router
> > first outbound endpoint routes via VM to a multicasting router,
> > synchronous, response transformer merges all the response payloads
> > (String) into a single String.
> > Second outbound endpoint routes the merged response to a destination.
> >
> > My "problem" is that going through the multicasting router and getting
> the
> > response, I lose all the original message properties. I can conserve them
> > by using another response transformer and getting the properties from the
> > DefaultMessageCollection (and I´ve already done this), but I was
> wondering
> > if there is a another, possibly simpler, way to preserve the message
> > properties of the original inbound request.
> > Are there some context properties I can configure? Should I just expand
> my
> > "responseMessagePropertiesCollector" transformer to loop over the whole
> > DefaultMessageCollection and get all the properties from there?
> >
>
> --
> View this message in context:
> http://old.nabble.com/Preserve-message-properties-after-a-response-from-Multicasting-router.-tp26809274p26837921.html
> Sent from the Mule - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>

Re: Pb JMS Connector (IBM MQ Series) : org.mule.api.MuleRuntimeException: Couldn't submit a work item to the WorkManager

2009-12-20T22:51:55Z

A little bit surprising that a jdk upgrade fixes this. This would suggest that there was a bug in the getJMSRedelivered() method.

Anyway, happy that this works for you.

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

http://xircles.codehaus.org/manage_email

Re: Pb JMS Connector (IBM MQ Series) : org.mule.api.MuleRuntimeException: Couldn't submit a work item to the WorkManager

2009-12-20T01:16:44Z

Hello Andrew,

I dont use wmq transport because we chose in this time the community edition.
In short, the configuration used is the classic JMS configuration follows:

<spring:bean name="mqConnectionFactory" class="com.ibm.mq.jms.MQQueueConnectionFactory">
<spring:property name="hostName" value="PCXYZ" />
<spring:property name="port" value="1415" />
<spring:property name="queueManager" value="KMI007" />
<spring:property name="channel" value="C_mule" />
<spring:property name="transportType" value="1" />
</spring:bean>

AND IN MODEL/SERVICE

<inbound>
<jms:inbound-endpoint queue="DEV.FOR.HERMES"
connector-ref="hermesQueueConnector" synchronous="true">

<jms:object-to-jmsmessage-transformer
name="JMSMessageToObject" />
<transformer ref="NettoyeurDeMessageProperties" />
<transformer ref="JmsHermesTransformer" />
</jms:inbound-endpoint>
</inbound>

Regards.
Karim

Re: JMS retries and errors help with requirements

2009-12-19T13:17:55Z

Actually this is best achievable by configuring maxRedelivery attr on the jms connector, using exception strategy and running on Mule 2.2.x/3.x Given that you reference UMOs, it might be a very old Mule release.

HTH,
Andrew

On Dec 19, 2009 2:58 PM, "dhenton9000" <dhenton@...> wrote:

I've got a very dumb question. I have a jms queue that I place under
transactions:

Read jmsQueue --> UMOA --> UMOB

UmoA and UmoB are mule code, and I have this all under a transaction so that
if UmoB fails the message is returned to the jmsQueue. If B fails
persistantly because of some obnoxious property of the message that it is
processing, I'd like to use retry policies/transactions (hopefully with no
custom code) that would result in X number of retries, then shunting the
offensive message to an error queue.

I think I'm misunderstanding transactions. If message X fails consistently,
the transaction will always place it back on the queue, which means that
I'll get a flood of error messages and a loop.

Is there a way to combine transactions, and retry policies to reprocess a
message X times and then shunt it to an error queue?

Custom code is always an option, but I'd like to see if I could do it out of
the box.

Thanks!
--
View this message in context: http://old.nabble.com/JMS-retries-and-errors-help-with-requirements-tp26858055p26858055.html
Sent from the Mule - User mailing list archive at Nabble.com.

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

http://xircles.codehaus.org/manage_email

JMS retries and errors help with requirements

2009-12-19T11:58:27Z

I've got a very dumb question. I have a jms queue that I place under transactions:

Read jmsQueue --> UMOA --> UMOB

UmoA and UmoB are mule code, and I have this all under a transaction so that if UmoB fails the message is returned to the jmsQueue. If B fails persistantly because of some obnoxious property of the message that it is processing, I'd like to use retry policies/transactions (hopefully with no custom code) that would result in X number of retries, then shunting the offensive message to an error queue.

I think I'm misunderstanding transactions. If message X fails consistently, the transaction will always place it back on the queue, which means that I'll get a flood of error messages and a loop.

Is there a way to combine transactions, and retry policies to reprocess a message X times and then shunt it to an error queue?

Custom code is always an option, but I'd like to see if I could do it out of the box.

Thanks!

Re: Preserve message properties after a response from Multicasting router.

2009-12-18T13:16:48Z

Hi John,

Would you mind opening a Jira for this? we could just a flag to the current chaining router.

Cheers,

Ross Mason
CTO, Founder
MuleSoft Inc.
http://twitter.com/rossmason

http://mulesoft.com | http://blog.rossmason.com

On Fri, Dec 18, 2009 at 2:38 AM, John D'Emic <john.demic@...> wrote:

I've used the following custom router implementation for this:

public class HeaderPropagatingChainingRouter extends ChainingRouter {

protected void processIntermediaryResult(MuleMessage localResult,
MuleMessage intermediaryResult) {
for (Object key : intermediaryResult.getPropertyNames()) {
localResult.setProperty((String) key,
intermediaryResult.getProperty((String) key));
}

}
}

This propagates the headers from each response to the next endpoint in the
chain...

HTH
-jd

wb123 wrote:
>
> Hi.
> I´ve got a simple Mule config that goes something like this
> Inbound request
> Outbound chaining router
> first outbound endpoint routes via VM to a multicasting router,
> synchronous, response transformer merges all the response payloads
> (String) into a single String.
> Second outbound endpoint routes the merged response to a destination.
>
> My "problem" is that going through the multicasting router and getting the
> response, I lose all the original message properties. I can conserve them
> by using another response transformer and getting the properties from the
> DefaultMessageCollection (and I´ve already done this), but I was wondering
> if there is a another, possibly simpler, way to preserve the message
> properties of the original inbound request.
> Are there some context properties I can configure? Should I just expand my
> "responseMessagePropertiesCollector" transformer to loop over the whole
> DefaultMessageCollection and get all the properties from there?
>

--

View this message in context: http://old.nabble.com/Preserve-message-properties-after-a-response-from-Multicasting-router.-tp26809274p26837921.html

Sent from the Mule - User mailing list archive at Nabble.com.

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

http://xircles.codehaus.org/manage_email

Re: JBoss versions JMS

2009-12-18T09:58:19Z

I need to pick up a JMS message from a JBoss 4.2.1 server and forward it to a
JMS queue on a JBoss 5.1 server.

I was about to suggest using Stomp against JBoss 5.1 when I read this.

Unless you can resolve the classpath hell, an option is to have two Mule instances, one embedding an ActiveMQ broker, exposed over TCP so the other Mule instance can access it.

Then establish this chain: JBoss 4.2.1 -(Mule XA bridge)-> ActiveMQ -(Mule XA bridge)-> Jboss 5.1

Re: Pb JMS Connector (IBM MQ Series) : org.mule.api.MuleRuntimeException: Couldn't submit a work item to the WorkManager

2009-12-18T06:40:14Z

Mule does not set those properties, it just copies them over from existing message. Hard to advise exactly without full config and understanding your flow. Also, I don't remember seeing anything like that in our WMQ transport tests (both with mq 6 and 7). But my understanding is you're not using wmq transport.

Andrew

On Dec 18, 2009 8:17 AM, "megui75" <megzarikarim@...> wrote:

Initially, I introduced the latest version of jdk 1.6_017 and now it works
but with errors (not important for the proper functioning of the service).

-----DEBUG ObjectToJMSMessage : Unable to set property 'JMSXAppID' of type
String': MQJMS1058: Invalid message property name: JMSXAppID
-----DEBUG ObjectToJMSMessage : Unable to set property 'JMSXDeliveryCount'
of type Integer': MQJMS1058: Invalid message property name:
JMSXDeliveryCount
-----DEBUG ObjectToJMSMessage : Unable to set property 'JMSXUserID' of type
String': MQJMS1058: Invalid message property name: JMSXUserID
----DEBUG ObjectToJMSMessage : Resulting object is JMSBytesMessage
---- DEBUG ObjectToJMSMessage : Object after transform:
JMS Message class: jms_bytes

JMSType: null JMSDeliveryMode: 2 JMSExpiration: 0 JMSPriority: 0
JMSMessageID: ID:414d512043323032202020202020202049f489c4215a9402
JMSTimesta...
-----DEBUG ObjectToJMSMessage : The transformed object is of expected type.
Type is: JMSBytesMessage
-----INFO JmsHermesTransformer : Transformation processing ...

message avec HT envoyé à Hermes .......................................
026204 DT-280792650 ZPPLAN888DUP11200908

FR FR19990808KMI KMIKMI ...
------ INFO JmsHermesTransformer : insert service processing ...
------ INFO JmsHermesTransformer : insert service processing terminé avec
succès ...

In a 2nd time, I used your recommendation
<message-properties-transformer name="NettoyeurDeMessageProperties">
<delete-message-property key="JMSXAppID" />
<delete-message-property key="JMSXDeliveryCount" />
<delete-message-property key="JMSXUserID" />
</message-properties-transformer>

and finally, I managed to delete the errors JMS "warning" from the log file.

Thank you very mutch.
Karim MEGZARI

you work at mulesoft ?

--
View this message in context: http://old.nabble.com/Pb-JMS-Connector-%28IBM-MQ-Series%29-%3A-org.mule.api.MuleRuntimeException%3A-Couldn%27t-submit-a-work-item-to-the-WorkManager-tp26835742p26843204.html

Sent from the Mule - User mailing list archive at Nabble.com. ------------------------------------...
To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email