Claus,
It seems I stumbled on a bug in Jsch - must be in my genes...
I have a conversation on their mailing list. Here is a link to the archives.
The latest messages are not yet in the archives but you can have a look in a
day or two.
http://sourceforge.net/mailarchive/forum.php?thread_name=2010
William Tam wrote:
On 06/23/2010 04:18 AM, Willem Jiang wrote:
Hi,
I just tried the solution of the JAXWS Handler, it only print out the
soap message and doesn't change the output stream which is sent to
client.
Is it a bug in CXF then? That's supposed to be the JAXWS way to go
about it
Hi Willem,
Willem.Jiang wrote:
>
> Hi,
>
> As Camel is used within ActiveMQ and ServiceMix, we can't just upgrade
> Spring version in Camel.
> But there is spring3 profile in camel parent/pom.xml, you can build
> camel with spring 3.0.3.RELEASE with that profile if you like.
>
>
Sounds to
Hi,
I added two patches to the jira issue. One for version 2.3.0 and one for
the trunk. Please check the patches and inform me if you will use them
in the next version. If you will use it then I could build my private
patched version until we can upgrade to the next up coming camel version.
Regar
On 06/23/2010 04:18 AM, Willem Jiang wrote:
Hi,
I just tried the solution of the JAXWS Handler, it only print out the
soap message and doesn't change the output stream which is sent to
client.
Is it a bug in CXF then? That's supposed to be the JAXWS way to go
about it.
After digging
Thank you Willem . It worked.
--
View this message in context:
http://camel.465427.n5.nabble.com/Dynamically-setting-retry-count-in-maximumRedilveries-attribute-tp510764p510927.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi
Maybe you could enable more logging and use that to see if you can
spot an obvious time gap between the two?
org.apache.camel.impl.ProducerCache=TRACE
org.apache.camel.util.ServiceHelper=TRACE
The ServiceHelper logs when producers/consumers etc. is being started stopped.
You can also use an
On Wed, Jun 23, 2010 at 1:57 PM, huntc wrote:
>
>
> Claus Ibsen-2 wrote:
>>
>> Can you post a bit more on the stacktrace? Maybe we can find a spot in
>> the camel-jms component to workaround this issue by setting an non
>> null message on the JmsException. This may help prevent this spring
>> bug.
On Wed, Jun 23, 2010 at 4:01 PM, Willem Jiang wrote:
> Hi,
>
> As Camel is used within ActiveMQ and ServiceMix, we can't just upgrade
> Spring version in Camel.
> But there is spring3 profile in camel parent/pom.xml, you can build camel
> with spring 3.0.3.RELEASE with that profile if you like.
>
Hi,
As Camel is used within ActiveMQ and ServiceMix, we can't just upgrade
Spring version in Camel.
But there is spring3 profile in camel parent/pom.xml, you can build
camel with spring 3.0.3.RELEASE with that profile if you like.
If you are using OSGi, camel also has a feature file
(feature
Claus Ibsen-2 wrote:
>
> No you can replace the spring jars.
>
Upgrading to Spring 3.0.3.RELEASE fixes the problem.
Should we move Camel to Spring 3?
Kind regards,
Christopher
--
View this message in context:
http://camel.465427.n5.nabble.com/Problem-with-maintaining-a-JMS-subscription-aft
On Wed, Jun 23, 2010 at 1:56 PM, benxs wrote:
>
> I defined the following for camel in an ActiveMQ installation:
>
>
>
>
>
>
>
> Every incoming JMS msg should simply be duplicated. The dupe should be put
> in
> another queue called "dupequeue". The original jms msg should
> remain i
On Wed, Jun 23, 2010 at 1:57 PM, huntc wrote:
>
>
> Claus Ibsen-2 wrote:
>>
>> Can you post a bit more on the stacktrace? Maybe we can find a spot in
>> the camel-jms component to workaround this issue by setting an non
>> null message on the JmsException. This may help prevent this spring
>> bug.
Claus Ibsen-2 wrote:
>
> Can you post a bit more on the stacktrace? Maybe we can find a spot in
> the camel-jms component to workaround this issue by setting an non
> null message on the JmsException. This may help prevent this spring
> bug.
>
Hi Claus,
That was the entire stack trace I'm afr
I defined the following for camel in an ActiveMQ installation:
Every incoming JMS msg should simply be duplicated. The dupe should be put
in
another queue called "dupequeue". The original jms msg should
remain in the input queue for later retrieval (by other java program).
Tha
Hi Claus,
Thanks for your quick response.
I using WebSphere MQ queues and a SQL Server 2005 database table as my
endpoints. I have made a code change this morning to cache the endpoints
once they have been created from the CamelContext using:
Endpoint endpoint = camelContext.getEndpoint(uri)
T
I think the ActiveMQ jars are enough for you :)
Willem
--
Apache Camel, Apache CXF committer
Open SOA http://www.fusesource.com
Blog http://willemjiang.blogspot.com
Tiwtter http://twitter.com/willemjiang
benxs wrote:
Assume I want to use Java DSL (and not Spring
Hi Christian,
The bean style is support in Camel 2.1, you don't have to upgrade Camel :)
Willem
Schneider Christian wrote:
Hi Claus,
when I use the bean style is it then possible to use ${file:name}? I would
guess this is not possible.
So that means upgrade to 2.3?
Greetings
Christian
C
Logging patch is now attached to the JIRA.
/Bengt
2010/6/23 Bengt Rodehav
> Claus,
>
> I'll try to get some help regarding this on the Jsch mailing list.
>
> Remember I told you nothing turns up in the log. I've looked at the source
> code for camel-ftp (SftpOperations.java) and there is no log
Hi Claus,
when I use the bean style is it then possible to use ${file:name}? I would
guess this is not possible.
So that means upgrade to 2.3?
Greetings
Christian
Christian Schneider
Informationsverarbeitung
Business Solutions
Handel und Dispatching
Tel : +49-(0)721-63-15482
EnBW Systeme
On Wed, Jun 23, 2010 at 11:53 AM, huntc wrote:
>
> After a little more research, I think its because the version of Spring we're
> using has this bug:
>
> https://jira.springsource.org/browse/SPR-5275
>
> Any recommendations?
>
Can you post a bit more on the stacktrace? Maybe we can find a spot i
Claus,
I'll try to get some help regarding this on the Jsch mailing list.
Remember I told you nothing turns up in the log. I've looked at the source
code for camel-ftp (SftpOperations.java) and there is no logger attached to
Jsch. I created a JIRA for that:
https://issues.apache.org/activemq/brow
On Wed, Jun 23, 2010 at 11:47 AM, huntc wrote:
>
> I've just made a discovery on my own machine. Looks as though this issue may
> actually be related to Spring. What I did was start up a broker, start up my
> application that subscribes to a topic, shutdown the broker and:
>
>
> Exception in threa
After a little more research, I think its because the version of Spring we're
using has this bug:
https://jira.springsource.org/browse/SPR-5275
Any recommendations?
Kind regards,
Christopher
--
View this message in context:
http://camel.465427.n5.nabble.com/Problem-with-maintaining-a-JMS-subs
Hi
Can you show a bit more how you use the template and how you obtain
those endpoints.
And what kind of endpoints are those? Are you sending to a MQ or the likes?
Under the covers the Java DSL uses the same foundation as the template
so it ought to be able to run on par in speed.
On Wed, Jun 2
I've just made a discovery on my own machine. Looks as though this issue may
actually be related to Spring. What I did was start up a broker, start up my
application that subscribes to a topic, shutdown the broker and:
Exception in thread "DefaultMessageListenerContainer-1"
java.lang.NullPointer
I am using Apache Camel version 2.2.0-fuse-01-00 in the WebSphere Application
Server web container.
I am looking to use the Apache Camel ProducerTemplate class to send messages
to endpoints from within a Java class and have observed a significant
reduction in message throughput when using the
Pro
On Wed, Jun 23, 2010 at 10:59 AM, Schneider Christian
wrote:
> Hi all,
>
> I got the following problem. I want to configure a file Endpoint using the
> File Language that should additionally have Properties replaced. As we are
> still on Camel 2.1 we can only use properties in Spring Language En
Hello again
After digging even deeper on my side, I have the impression that the
issue is not because of the I'm using a Web Service that's MTOM (which is logical: the WS handles
file download and uploads). Trouble: PHP's SOAP client doesn't support
MTOM (you can google "PHP SOAP MTOM" for det
Hi all,
I got the following problem. I want to configure a file Endpoint using the File
Language that should additionally have Properties replaced. As we are still on
Camel 2.1 we can only use properties in Spring Language Endpoint tags.
So my try was:
The problem is that file:name is not rec
Hi,
I just tried the solution of the JAXWS Handler, it only print out the
soap message and doesn't change the output stream which is sent to client.
After digging a while, I found the StaxOutInterceptor[1] will check the
message context with the key of
"org.apache.cxf.stax.force-start-docume
Just for the record, I've updated the broker to 5.3.2 as well. I'm now using
the latest of everything.
I shall now start looking at the Camel component...
--
View this message in context:
http://camel.465427.n5.nabble.com/Problem-with-maintaining-a-JMS-subscription-after-waking-from-sleep-tp510
32 matches
Mail list logo
