Camel- WebSphere MQ Integration

2016-09-19 Thread sari.reach
Messages subscribed to Websphere MQ using camel for a plain text messages are subscribed but when headers are set to camel message and posted. These messages are not being subscribed to websphere MQ however these are subscribed with a standalone application. -- View this message in context: ht

Re: Camel- WebSphere MQ Integration

2016-09-19 Thread sari.reach
On Mon, Sep 19, 2016 at 11:14 PM, sari.reach [via Camel] < ml-node+s465427n5787731...@n5.nabble.com> wrote: > Messages subscribed to Websphere MQ using camel for a plain text messages > are subscribed but > when headers are set to camel message and posted. These messages

cxf-core 3.1.7 Validation issue with camel

2016-09-19 Thread sari.reach
cxf-core 3.1.7 is not validating the xml with xsd at appropriate location Exception says: Could not generate the XML stream caused by: org.xml.sax.SAXParseException: cvc-elt.1: Cannot find the declaration of element 'ATT_CheckRS'.. Sample code is as below import org.apache.camel.Exchange; impor

Re: cxf-core 3.1.7 Validation issue with camel

2016-09-19 Thread sari.reach
Please accept this request On Mon, Sep 19, 2016 at 11:01 PM, sari.reach [via Camel] < ml-node+s465427n5787728...@n5.nabble.com> wrote: > cxf-core 3.1.7 is not validating the xml with xsd at appropriate location > > Exception says: Could not generate the XML s

Re: Camel- WebSphere MQ Integration

2016-09-19 Thread sari.reach
Hi souciane, I am posting message to websphere queue with all the headers set to camel message but this message is not published to MQ. However, when I try to publish it with a standalone applciation, the message is published. Please find sample code below. message.setHeader("provider-uri", provi

Re: Camel- WebSphere MQ Integration

2016-09-19 Thread sari.reach
Sent from my iPhone > On 20-Sep-2016, at 11:31 AM, sari.reach [via Camel] > wrote: > > Hi souciane, > > I am posting message to websphere queue with all the headers set to camel > message but this message is not published to MQ. However, when I try to > publ

Re: cxf-core 3.1.7 Validation issue with camel

2016-09-19 Thread sari.reach
Please find the camel route below. Please let me know if you need additional information. I am pasting the exception trace as well. http://camel.apache.org/schema/spring";>

Re: cxf-core 3.1.7 Validation issue with camel

2016-09-20 Thread sari.reach
Hi, Please find the entire camel-config.xml. Schema information is inside the resource folder(in classpath). For this scenario, request validation is working fine and only response validation is creating an issue http://www.springframework.org/schema/beans"; xmlns:xsi="http://www.w3.or

Re: cxf-core 3.1.7 Validation issue with camel

2016-09-22 Thread sari.reach
Any update on this Willem? -- View this message in context: http://camel.465427.n5.nabble.com/cxf-core-3-1-7-Validation-issue-with-camel-tp5787728p5787946.html Sent from the Camel - Users mailing list archive at Nabble.com.

Very Urgent - Camel direct component issue.

2017-01-14 Thread sari.reach
we are using *camel direct component* in our project. Application will work fine most of the time. But sometimes services won't work because of following exception. if we restart server again things will go normal. we are not following any route startup order to start camel routes. All routes wil

Re: Very Urgent - Camel direct component issue.

2017-01-14 Thread sari.reach
\n\n HOTEL\n wrote: > Did something happen to bring down the route if a restart makes everything > work? What kind of data is being sent before that error occurs? > > On Sat, Jan 14, 2017 at 2:24 PM, sari.reach [via Camel] <[hidden email] > <http:///user/SendEma

Re: Very Urgent - Camel direct component issue.

2017-01-14 Thread sari.reach
254...@n5.nabble.com> wrote: > Try adding the parameter block=true to your producerTemplate when sending > to that direct uri. > > On Sat, Jan 14, 2017 at 2:50 PM, sari.reach [via Camel] <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=5792542&i=0>> wro

Re: Very Urgent - Camel direct component issue.

2017-01-14 Thread sari.reach
omewhere you are sending to that endpoint > > On Sat, Jan 14, 2017 at 5:07 PM, sari.reach [via Camel] <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=5792544&i=0>> wrote: > >> Thank you Souciance. >> >> Just curious to know what is this

Re: Very Urgent - Camel direct component issue.

2017-01-16 Thread sari.reach
Can you please let me know how to add block=true to producertemplate? -- View this message in context: http://camel.465427.n5.nabble.com/Very-Urgent-Camel-direct-component-issue-tp5792539p5792569.html Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Very Urgent - Camel direct component issue.

2017-01-18 Thread sari.reach
We will try with this option but as per our observation. This is never happening in our local machines with windows environment. This issue is happening only in our servers with Linux environment. Once we get this exception, even if we fire the same request after 2 hours or so, we get the same exc

Re: Very Urgent - Camel direct component issue.

2017-01-19 Thread sari.reach
Can you please respond to this query This issue is happening only in our servers with Linux environment. Once we get this exception, even if we fire the same request after 2 hours or so, we get the same exception. Only restart will rectify this. if block=true is the solution then our request after

Urgent - Endpoint wsdl XSD's are stored in heap memory

2017-01-30 Thread sari.reach
Request, response xsd mentioned in wsdl and all the xsds included in request, response xsds are loaded at the server start and stored in heap memory. How to avoid this? Please help -- View this message in context: http://camel.465427.n5.nabble.com/Urgent-Endpoint-wsdl-XSD-s-are-stored-in-hea

Re: Urgent - Endpoint wsdl XSD's are stored in heap memory

2017-01-30 Thread sari.reach
My wsdls contain xsd's which are of 1MB size, All these xsd's are loaded in memory when context is loaded for the first time. I don't want these xsd's to be loaded in memory. Please let me know how to stop this -- View this message in context: http://camel.465427.n5.nabble.com/Urgent-Endpoint-w

Re: Very Urgent - Camel direct component issue.

2017-02-08 Thread sari.reach
Anybody has an update on this -- View this message in context: http://camel.465427.n5.nabble.com/Very-Urgent-Camel-direct-component-issue-tp5792539p5793706.html Sent from the Camel - Users mailing list archive at Nabble.com.