Re: Camel-jdbc snapshots - SQLException
Hi, I just tryed your fix and it works fine. Thank you. However, I have one last problem :camel-jdbc doesn't preserve headers on some INSERT requests. These lines : were moved from JdbcProducer.process to some deeper functions, but now it doesn't get called all the time. For instance, if I want to perform a 'vanilla' INSERT, /JdbcProducer.doCreateAndExecuteSqlStatement/ gets called. It calls /stmtExecutionResult = stmt.execute(sql);/, and if it returns true, it calls / setResultSet/ which preserves headers. However, if it returns false (in my case, or with any INSERT/UPDATE), it doesn't preserve headers. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-jdbc-snapshots-SQLException-tp5755058p5755129.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Camel-jdbc snapshots - SQLException
Hi Ah yeah there was some code missing. I have pushed a fix. You are welcome to test again. On Wed, Aug 13, 2014 at 9:52 AM, A577127 antoine.mat...@worldline.com wrote: Hi, I just tryed your fix and it works fine. Thank you. However, I have one last problem :camel-jdbc doesn't preserve headers on some INSERT requests. These lines : were moved from JdbcProducer.process to some deeper functions, but now it doesn't get called all the time. For instance, if I want to perform a 'vanilla' INSERT, /JdbcProducer.doCreateAndExecuteSqlStatement/ gets called. It calls /stmtExecutionResult = stmt.execute(sql);/, and if it returns true, it calls / setResultSet/ which preserves headers. However, if it returns false (in my case, or with any INSERT/UPDATE), it doesn't preserve headers. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-jdbc-snapshots-SQLException-tp5755058p5755129.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
Re: Camel-jdbc snapshots - SQLException
Everything works fine. Thanks. -- View this message in context: http://camel.465427.n5.nabble.com/Camel-jdbc-snapshots-SQLException-tp5755058p5755158.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Question: camel-sql out of memory error
At present, we do not limit the fetch size on the JDBC driver level which
will fix this issue (e.g.
preparedStatement.setFetchSize(getMaxMessagesPerPoll())).
The drawback is, we don't know how many rows are in the database which will
match our query. We only can assume if fetchSize is equal to
maxMessagesPerPoll, there are more rows to read.
From my point of view, we should go for this change. If nobody has
objections, I will will do the needed changes later this week...
Best,
Christian
-
Software Integration Specialist
Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apache Incubator PMC Member
https://www.linkedin.com/pub/christian-mueller/11/551/642
On Fri, Aug 8, 2014 at 10:34 PM, Matt Payne pa...@mattpayne.org wrote:
I am getting an java.lang.OutOfMemoryError: Java heap space when using
camel sql component with a query that returns a large number of rows.
Using a small value for maxMessagesPerPoll=10 does not help[1].
When reading the source[2], I see:
255 protected ListMapString, Object queryForList(ResultSet rs) throws
SQLException {
256 ColumnMapRowMapper rowMapper = new ColumnMapRowMapper();
257 RowMapperResultSetExtractorMapString, Object mapper = new
RowMapperResultSetExtractorMapString, Object(rowMapper);
258 ListMapString, Object data = mapper.extractData(rs);
259 return data;
260 }
It seems that all of the result set, rs, is going to be read regardless of
how large it is. When stepping through via eclipse's debugger this is
what I see happening.
It's unclear how to ask camel sql component to only take X rows at a time.
Is there a way to do this please?
Thanks! --Matt Payne
[1]
http://camel.465427.n5.nabble.com/Fetching-data-in-batches-td5718366.html
[2]
https://git-wip-us.apache.org/repos/asf?p=camel.git;a=blob;f=components/camel-sql/src/main/java/org/apache/camel/component/sql/SqlEndpoint.java#l255
camel wmq transactions - ack mode as TRANSACTED
Hi Team,
Please find the below scenarios or camel route
from(wmq:queue:eventQueue + ?useMessageIDAsCorrelationID=true)
.transacted()
.bean(orchestrator, processMessage(${body}, ${headers}));
and for transaction i am maintaining JmsTransactionManager. please find the
same. actually i have gone through Chapter 9 in the Camel in Action book.
based on that I configured txn.
bean id=wmq class=org.apache.camel.component.jms.JmsComponent
property name=transacted value=true /
property name=transactionManager ref=txManager /
/bean
bean id=txManager
class=org.springframework.jms.connection.JmsTransactionManager
property name=connectionFactory ref=wmqConnectionFactory /
/bean
Now in Chapter 9 in the Camel in Action book, author mentioned about
ACTIVEMQ.DLQ, but what will happen in case of Websphere MQ.
My requirement is if at all processMessage(${body}, ${headers}) fails to
process and throws exception , camel should not acknowledge and message
should be there as it is inside WMQ.
Could you please help me for the same.
Thanks
Satyajit
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-wmq-transactions-ack-mode-as-TRANSACTED-tp5755162.html
Sent from the Camel - Users mailing list archive at Nabble.com.
HTTP basic authorization with HTTP4?
Is there any way to send HTTP basic authorization(preemptive authentication) to another web service(from HTTP4). I have a proxy with Jetty consuming and HTTP4 producing. Here is some sample code in the webservice documentation - Options options = ipgstub._getServiceClient().getOptions(); HttpTransportProperties.Authenticator auth = new HttpTransportProperties.Authenticator(); auth.setPreemptiveAuthentication(true); auth.setUsername(WS111920._.1); auth.setPassword(0WRtTq1K); options.setProperty(HTTPConstants.AUTHENTICATE,auth); Thanks! -- View this message in context: http://camel.465427.n5.nabble.com/HTTP-basic-authorization-with-HTTP4-tp5755181.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: one context or multiple contexts?
In doing research about implementing multiple CamelContexts within a single JVM, I have seen the information on this page pop up in several different places. http://camel.apache.org/why-use-multiple-camelcontext.html In general, you don't tend to want multiple camel contexts in your application, if you're running Camel as a standalone Java instance. Is there a technical reason why an application would only want 1 CamelContext per JVM? Meaning, does the CamelContext create a singleton classes that have a certain state which may be changed by a different CamelContext? If there isn't, could we get the documentation updated to be a little more accurate? -- View this message in context: http://camel.465427.n5.nabble.com/one-context-or-multiple-contexts-tp5754635p5755184.html Sent from the Camel - Users mailing list archive at Nabble.com.
Limiting thread pool size for parallelProcessing?
My desired flow is:
endpoint routes to bean
bean creates multiple child messages from source
split on body
child messages process in parallel, up to a max
aggregate results
reply w/ aggregated results
I've tried several different configurations. I've been able to make it all
process like a queue, or wide open parallel. Wide open parallel exhausts my
DB pool.
Here are the current route definitions:
main route:
from(stomp:request_queue).
bean(new MyGenerator()).
split(body(), new MyAggregationStrategy()).
parallelProcessing().timeout(0).
inOut(seda:child_queue?timeout=0).
end().
recipientList(simple(stomp:${headers[reply-to]}));
child route:
from(seda:udm_kli_sql_queue?concurrentConsumers=4).
threads(1, 4).
bean(new MyRunner());
I thought that using parallelProcessing in the main route and
concurrentConsumers in the child route would give me the desired behavior,
but it doesn't.
Any suggestions?
--
View this message in context:
http://camel.465427.n5.nabble.com/Limiting-thread-pool-size-for-parallelProcessing-tp5755185.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Limiting thread pool size for parallelProcessing?
Of course, I figure it out 30 minutes after posting. This route works as
desired:
from(stomp:request_queue).
bean(new MyGenerator()).
split(body(), new MyAggregationStrategy()).
parallelProcessing().executorService(Executors.newFixedThreadPool(4)).
bean(new MyRunner()).
end().
recipientList(simple(stomp:${headers[reply-to]}));
--
View this message in context:
http://camel.465427.n5.nabble.com/Limiting-thread-pool-size-for-parallelProcessing-tp5755185p5755186.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Retrieving EXEC_EXIT_VALUE from exec endpoint
No exec headers are set after an invocation of this endpoint, so I'm not
being able to decide what do upon process execution. I'm using Spring DSL
like this:
camel:recipientList
camel:simple
exec://{{cmod.arsLoad}}?useStderrOnEmptyStdout=trueamp;args=-f -g
${in.header.appGroup} -h {{cmod.host}} -u {{cmod.username}} -p
{{cmod.password}} {{tmp.path}}/${id}/camel:simple
/camel:recipientList
I was trying to get the EXEC_EXIT_VALUE using something like:
camel:log message=Exit code: ${out.header.ExecBinding.EXEC_EXIT_VALUE} /
But since I got no output I even tried:
camel:to uri=log:org.apache.camel.example?showAll=trueamp;multiline=true
/
But just got:
[13/08/14 16:57:55:250 CLT] 0077 SystemOut O 2014-08-13 16:57:55,249
INFO [example ] - Exchange[
, Id: ID-thor-altiuz-cl-55058-1407963458446-0-7
, ExchangePattern: InOptionalOut
, Properties: {CamelCorrelationId=ID-thor-altiuz-cl-55058-1407963458446-0-7,
CamelCreatedTimestamp=Wed Aug 13 16:57:44 CLT 2014,
CamelMessageHistory=[DefaultMessageHistory[routeId=route1, node=multicast1],
DefaultMessageHistory[routeId=route1, node=to3],
DefaultMessageHistory[routeId=route4, node=to6],
DefaultMessageHistory[routeId=route4, node=setHeader3],
DefaultMessageHistory[routeId=route4, node=recipientList3],
DefaultMessageHistory[routeId=route4, node=to7]],
CamelMulticastComplete=true, CamelMulticastIndex=0,
CamelRecipientListEndpoint=exec:///opt/ibm/ondemand/V9.0/bin/arsload?args=-f+-g+CCMM+-h+192.168.10.77+-u+admin+-p+password+%2Ftmp%2FID-thor-altiuz-cl-55058-1407963458446-0-1useStderrOnEmptyStdout=true,
CamelToEndpoint=log://org.apache.camel.example?multiline=trueshowAll=true,
isXalanTransformer=false}
, Headers: {appGroup=CCMM,
breadcrumbId=ID-thor-altiuz-cl-55058-1407963458446-0-1,
CamelSpringWebserviceSoapHeader=javax.xml.transform.dom.DOMSource@4be1d2c4}
, BodyType: String
, Body: CCMM
, Out: null:
]
So nothing seems to be coming out as an exit valueany help would be
appreciated
--
View this message in context:
http://camel.465427.n5.nabble.com/Retrieving-EXEC-EXIT-VALUE-from-exec-endpoint-tp5755188.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: transfer exception
Hi Claus, Thanks for the reply. I need to rollback the transaction otherwise my DB statements will commit and a JMS event will be sent. What is the point of the transaction if it's not rolled back on error? Is there no simple way to have the request / reply return immediately upon an exception / transaction rollback? It's not really acceptable for my case to have a timeout be the response. thanks, Matt On Tue, Aug 12, 2014 at 10:40 PM, Claus Ibsen claus.ib...@gmail.com wrote: Hi Then you need to not rollback the tx, and handle the exception and return the response as the stacktrace. On Tue, Aug 12, 2014 at 10:37 PM, Matt Wendling mwendl...@ipass.com wrote: Hi, I'm using Camel with ActiveMQ and InOut request/reply routes. When I set transferException=true i get the exception returned to the caller. However if the route is transacted then the exception is NOT returned and I end up with the 2 ms timeout on the caller. Is there a way to get this exception and return it back to the caller in a transacted route? thanks, Matt -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
Re: Retrieving EXEC_EXIT_VALUE from exec endpoint
Extra, I'm using camel 2.13.2
In my pom.xml:
dependency
groupIdorg.apache.camel/groupId
artifactIdcamel-spring-ws/artifactId
version2.13.2/version
/dependency
Running both in Apache Tomcat 7 (JDK 1.7.0_04-b21 in OSX) and IBM WebSphere
Application Server 8.5.5.2 (IBM JDK 1.7.0_45 in Debian Wheezy 7.2), with the
same results.
Regards,
Gonzalo Vásquez Sáez
Gerente Investigación y Desarrollo (RD)
Altiuz Soluciones Tecnológicas de Negocios Ltda.
Av. Nueva Tajamar 555 Of. 802, Las Condes - CP 7550099
+56 2 335 2461
gvasq...@altiuz.cl
http://www.altiuz.cl
http://www.altiuzreports.com
El 13-08-2014, a las 14:09, gvasquez gvasq...@altiuz.cl escribió:
No exec headers are set after an invocation of this endpoint, so I'm not
being able to decide what do upon process execution. I'm using Spring DSL
like this:
camel:recipientList
camel:simple
exec://{{cmod.arsLoad}}?useStderrOnEmptyStdout=trueamp;args=-f -g
${in.header.appGroup} -h {{cmod.host}} -u {{cmod.username}} -p
{{cmod.password}} {{tmp.path}}/${id}/camel:simple
/camel:recipientList
I was trying to get the EXEC_EXIT_VALUE using something like:
camel:log message=Exit code: ${out.header.ExecBinding.EXEC_EXIT_VALUE} /
But since I got no output I even tried:
camel:to uri=log:org.apache.camel.example?showAll=trueamp;multiline=true
/
But just got:
[13/08/14 16:57:55:250 CLT] 0077 SystemOut O 2014-08-13 16:57:55,249
INFO [example ] - Exchange[
, Id: ID-thor-altiuz-cl-55058-1407963458446-0-7
, ExchangePattern: InOptionalOut
, Properties: {CamelCorrelationId=ID-thor-altiuz-cl-55058-1407963458446-0-7,
CamelCreatedTimestamp=Wed Aug 13 16:57:44 CLT 2014,
CamelMessageHistory=[DefaultMessageHistory[routeId=route1, node=multicast1],
DefaultMessageHistory[routeId=route1, node=to3],
DefaultMessageHistory[routeId=route4, node=to6],
DefaultMessageHistory[routeId=route4, node=setHeader3],
DefaultMessageHistory[routeId=route4, node=recipientList3],
DefaultMessageHistory[routeId=route4, node=to7]],
CamelMulticastComplete=true, CamelMulticastIndex=0,
CamelRecipientListEndpoint=exec:///opt/ibm/ondemand/V9.0/bin/arsload?args=-f+-g+CCMM+-h+192.168.10.77+-u+admin+-p+password+%2Ftmp%2FID-thor-altiuz-cl-55058-1407963458446-0-1useStderrOnEmptyStdout=true,
CamelToEndpoint=log://org.apache.camel.example?multiline=trueshowAll=true,
isXalanTransformer=false}
, Headers: {appGroup=CCMM,
breadcrumbId=ID-thor-altiuz-cl-55058-1407963458446-0-1,
CamelSpringWebserviceSoapHeader=javax.xml.transform.dom.DOMSource@4be1d2c4}
, BodyType: String
, Body: CCMM
, Out: null:
]
So nothing seems to be coming out as an exit valueany help would be
appreciated
--
View this message in context:
http://camel.465427.n5.nabble.com/Retrieving-EXEC-EXIT-VALUE-from-exec-endpoint-tp5755188.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: one context or multiple contexts?
It's certainly far easier to use in such a scenario. Multiple CamelContexts prevents you from using the direct: and seda: components (to name two) in between contexts. Some components may also not be using very modular libraries behind the scenes which may be using singletons and such. In such a scenario, I find that using OSGi (like through Karaf/ServiceMix/Fabric8/etc.) helps a lot in that regard. On 13 August 2014 11:30, peter_mine...@skycreek.com peter_mine...@skycreek.com wrote: In doing research about implementing multiple CamelContexts within a single JVM, I have seen the information on this page pop up in several different places. http://camel.apache.org/why-use-multiple-camelcontext.html In general, you don't tend to want multiple camel contexts in your application, if you're running Camel as a standalone Java instance. Is there a technical reason why an application would only want 1 CamelContext per JVM? Meaning, does the CamelContext create a singleton classes that have a certain state which may be changed by a different CamelContext? If there isn't, could we get the documentation updated to be a little more accurate? -- View this message in context: http://camel.465427.n5.nabble.com/one-context-or-multiple-contexts-tp5754635p5755184.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Matt Sicker boa...@gmail.com
Re: transfer exception
Are you using the unit of work feature? On 13 August 2014 13:36, Matt Wendling mwendl...@ipass.com wrote: Hi Claus, Thanks for the reply. I need to rollback the transaction otherwise my DB statements will commit and a JMS event will be sent. What is the point of the transaction if it's not rolled back on error? Is there no simple way to have the request / reply return immediately upon an exception / transaction rollback? It's not really acceptable for my case to have a timeout be the response. thanks, Matt On Tue, Aug 12, 2014 at 10:40 PM, Claus Ibsen claus.ib...@gmail.com wrote: Hi Then you need to not rollback the tx, and handle the exception and return the response as the stacktrace. On Tue, Aug 12, 2014 at 10:37 PM, Matt Wendling mwendl...@ipass.com wrote: Hi, I'm using Camel with ActiveMQ and InOut request/reply routes. When I set transferException=true i get the exception returned to the caller. However if the route is transacted then the exception is NOT returned and I end up with the 2 ms timeout on the caller. Is there a way to get this exception and return it back to the caller in a transacted route? thanks, Matt -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/ -- Matt Sicker boa...@gmail.com
Re: transfer exception
I'm not using that. On Wed, Aug 13, 2014 at 11:57 AM, Matt Sicker boa...@gmail.com wrote: Are you using the unit of work feature? On 13 August 2014 13:36, Matt Wendling mwendl...@ipass.com wrote: Hi Claus, Thanks for the reply. I need to rollback the transaction otherwise my DB statements will commit and a JMS event will be sent. What is the point of the transaction if it's not rolled back on error? Is there no simple way to have the request / reply return immediately upon an exception / transaction rollback? It's not really acceptable for my case to have a timeout be the response. thanks, Matt On Tue, Aug 12, 2014 at 10:40 PM, Claus Ibsen claus.ib...@gmail.com wrote: Hi Then you need to not rollback the tx, and handle the exception and return the response as the stacktrace. On Tue, Aug 12, 2014 at 10:37 PM, Matt Wendling mwendl...@ipass.com wrote: Hi, I'm using Camel with ActiveMQ and InOut request/reply routes. When I set transferException=true i get the exception returned to the caller. However if the route is transacted then the exception is NOT returned and I end up with the 2 ms timeout on the caller. Is there a way to get this exception and return it back to the caller in a transacted route? thanks, Matt -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/ -- Matt Sicker boa...@gmail.com
Re: transfer exception
Finally found a way to make this work. I was using the activemq component but when I switched to using Direct it works like I want. On Wed, Aug 13, 2014 at 1:23 PM, Matt Wendling mwendl...@ipass.com wrote: I'm not using that. On Wed, Aug 13, 2014 at 11:57 AM, Matt Sicker boa...@gmail.com wrote: Are you using the unit of work feature? On 13 August 2014 13:36, Matt Wendling mwendl...@ipass.com wrote: Hi Claus, Thanks for the reply. I need to rollback the transaction otherwise my DB statements will commit and a JMS event will be sent. What is the point of the transaction if it's not rolled back on error? Is there no simple way to have the request / reply return immediately upon an exception / transaction rollback? It's not really acceptable for my case to have a timeout be the response. thanks, Matt On Tue, Aug 12, 2014 at 10:40 PM, Claus Ibsen claus.ib...@gmail.com wrote: Hi Then you need to not rollback the tx, and handle the exception and return the response as the stacktrace. On Tue, Aug 12, 2014 at 10:37 PM, Matt Wendling mwendl...@ipass.com wrote: Hi, I'm using Camel with ActiveMQ and InOut request/reply routes. When I set transferException=true i get the exception returned to the caller. However if the route is transacted then the exception is NOT returned and I end up with the 2 ms timeout on the caller. Is there a way to get this exception and return it back to the caller in a transacted route? thanks, Matt -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/ -- Matt Sicker boa...@gmail.com
Re: How can I make a RecipientList http component use an HttpConfiguration???
Hi I'm using 2.13.2 The URI option is non-ideal since it sends the credentials in clear text as part of the http (GET) call. That's not very secure. Thanks, Rick -- View this message in context: http://camel.465427.n5.nabble.com/How-can-I-make-a-RecipientList-http-component-use-an-HttpConfiguration-tp5755116p5755193.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Retrieving EXEC_EXIT_VALUE from exec endpoint
Hi,
Did you try to check the EXEC_EXIT_VALUE from in message?
camel:log message=Exit code: ${in.header.ExecBinding.EXEC_EXIT_VALUE} /
You can find more information about in and out message here[1].
[1]http://camel.apache.org/using-getin-or-getout-methods-on-exchange.html
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On August 14, 2014 at 2:52:07 AM, Gonzalo Vasquez (gvasq...@altiuz.cl) wrote:
Extra, I'm using camel 2.13.2
In my pom.xml:
org.apache.camel
camel-spring-ws
2.13.2
Running both in Apache Tomcat 7 (JDK 1.7.0_04-b21 in OSX) and IBM WebSphere
Application
Server 8.5.5.2 (IBM JDK 1.7.0_45 in Debian Wheezy 7.2), with the same results.
Regards,
Gonzalo Vásquez Sáez
Gerente Investigación y Desarrollo (RD)
Altiuz Soluciones Tecnológicas de Negocios Ltda.
Av. Nueva Tajamar 555 Of. 802, Las Condes - CP 7550099
+56 2 335 2461
gvasq...@altiuz.cl
http://www.altiuz.cl
http://www.altiuzreports.com
El 13-08-2014, a las 14:09, gvasquez escribió:
No exec headers are set after an invocation of this endpoint, so I'm not
being able to decide what do upon process execution. I'm using Spring DSL
like this:
exec://{{cmod.arsLoad}}?useStderrOnEmptyStdout=trueargs=-f -g
${in.header.appGroup} -h {{cmod.host}} -u {{cmod.username}} -p
{{cmod.password}} {{tmp.path}}/${id}
I was trying to get the EXEC_EXIT_VALUE using something like:
/
But since I got no output I even tried:
/
But just got:
[13/08/14 16:57:55:250 CLT] 0077 SystemOut O 2014-08-13 16:57:55,249
INFO [example ] - Exchange[
, Id: ID-thor-altiuz-cl-55058-1407963458446-0-7
, ExchangePattern: InOptionalOut
, Properties:
{CamelCorrelationId=ID-thor-altiuz-cl-55058-1407963458446-0-7,
CamelCreatedTimestamp=Wed Aug 13 16:57:44 CLT 2014,
CamelMessageHistory=[DefaultMessageHistory[routeId=route1,
node=multicast1],
DefaultMessageHistory[routeId=route1, node=to3],
DefaultMessageHistory[routeId=route4, node=to6],
DefaultMessageHistory[routeId=route4, node=setHeader3],
DefaultMessageHistory[routeId=route4, node=recipientList3],
DefaultMessageHistory[routeId=route4, node=to7]],
CamelMulticastComplete=true, CamelMulticastIndex=0,
CamelRecipientListEndpoint=exec:///opt/ibm/ondemand/V9.0/bin/arsload?args=-f+-g+CCMM+-h+192.168.10.77+-u+admin+-p+password+%2Ftmp%2FID-thor-altiuz-cl-55058-1407963458446-0-1useStderrOnEmptyStdout=true,
CamelToEndpoint=log://org.apache.camel.example?multiline=trueshowAll=true,
isXalanTransformer=false}
, Headers: {appGroup=CCMM,
breadcrumbId=ID-thor-altiuz-cl-55058-1407963458446-0-1,
CamelSpringWebserviceSoapHeader=javax.xml.transform.dom.DOMSource@4be1d2c4}
, BodyType: String
, Body: CCMM
, Out: null:
]
So nothing seems to be coming out as an exit valueany help would be
appreciated
--
View this message in context:
http://camel.465427.n5.nabble.com/Retrieving-EXEC-EXIT-VALUE-from-exec-endpoint-tp5755188.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: HTTP basic authorization with HTTP4?
If you already know the basic authentication information, you can set up the http4 endpoint uri options just like this http4://BackEndAddress?authUsername=WS111920._.1authPassword=0WRtTq1KauthenticationPreemptive=true -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On August 13, 2014 at 11:52:30 PM, apache999 (leofer...@gmail.com) wrote: Is there any way to send HTTP basic authorization(preemptive authentication) to another web service(from HTTP4). I have a proxy with Jetty consuming and HTTP4 producing. Here is some sample code in the webservice documentation - Options options = ipgstub._getServiceClient().getOptions(); HttpTransportProperties.Authenticator auth = new HttpTransportProperties.Authenticator(); auth.setPreemptiveAuthentication(true); auth.setUsername(WS111920._.1); auth.setPassword(0WRtTq1K); options.setProperty(HTTPConstants.AUTHENTICATE,auth); Thanks! -- View this message in context: http://camel.465427.n5.nabble.com/HTTP-basic-authorization-with-HTTP4-tp5755181.html Sent from the Camel - Users mailing list archive at Nabble.com.
