Update 2:
As Colm suggested, upgrading to WSS4J 1.6.9 solved this issue. Thanks a lot!
Thanks,
Christian
On Sun, Jan 6, 2013 at 7:37 PM, Christian Müller <
christian.muel...@gmail.com> wrote:
> Update:
> Upgrading to CXF 2.6.4 solved this issue and the performance is better.
> However, if I exec
I couldn't wait until tomorrow... ;-)
This upgrade (including xmlsec to 1.5.3) resolved this issue. Thanks for
saving my time!
Best,
Christian
On Sun, Jan 6, 2013 at 11:54 PM, Christian Müller <
christian.muel...@gmail.com> wrote:
> Thanks a lot Colm! I will try it tomorrow...
> Fyi, I discovere
Thanks a lot Colm! I will try it tomorrow...
Fyi, I discovered the same issue with Karaf 2.3.0 + Camel 2.11-SNAPSHOT +
CXF 2.7.1...
Best,
Christian
On Sun, Jan 6, 2013 at 10:37 PM, Colm O hEigeartaigh wrote:
> It's a bug that was fixed in WSS4J 1.6.9, which has just been released. You
> could tr
It's a bug that was fixed in WSS4J 1.6.9, which has just been released. You
could try WSS4J 1.6.9 with CXF 2.6.4.
Colm.
On Sun, Jan 6, 2013 at 6:37 PM, Christian Müller <
christian.muel...@gmail.com> wrote:
> Update:
> Upgrading to CXF 2.6.4 solved this issue and the performance is better.
> How
Update:
Upgrading to CXF 2.6.4 solved this issue and the performance is better.
However, if I execute the "secure-proxy" test, I get the following
exception and the test failed:
Stacktrace:
org.apache.cxf.binding.soap.SoapFault: General security error (Unable to
load class org.apache.ws.security.p
Environment: SMX 4.5.0-SNAPSHOT (20121127) + CXF 2.6.3 + Camel 2.10.3
For the upcoming ESB Performance Test Round 7 [1], I prepared the test for
the new ServiceMix 4.5.0 and Camel 2.10.3. You can find the complete
project at [2]. The README file [3] explains how I "tuned" my installation.
All tes
