Hi all,
Currently SMX 6.0.0 (and I suspect 6.0.1) bundles AWS SDK with joda-time 2.6, which leads to an error in the signature timestamp when version 3 of the signer is used, see here: https://github.com/aws/aws-sdk-java/issues/514 Upgrading to joda-time 2.8.2 is said to fix the issue, but in the meantime one can override the signer by specifying V4 explicitly, like this: (http://pastebin.com/nGhWr8QZ) 1. <?xml version="1.0" encoding="UTF-8"?> 2. <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0";> 3. 4. <!-- Force V4 Signer (which is the preferred one: http://goo.gl/bClV3W), to work around a SMX 6 bug --> 5. <bean id="sesClientConfiguration" class="com.amazonaws.ClientConfiguration"> 6. <property name="signerOverride" value="AWS4SignerType" /> 7. </bean> 8. 9. <!-- Inject the custom client configuration --> 10. <bean id="sesClient" class="com.amazonaws.services.simpleemail.AmazonSimpleEmailServiceClient"> 11. <argument ref="sesClientConfiguration" /> 12. </bean> 13. 14. </blueprint> Because V4 uses a different and bug-free algorithm to format the timestamp, this solved my problem and maybe save someone else a headache. Kind regards, Dario Cimafonte -----Original Message----- From: Krzysztof Sobkowiak [mailto:[email protected]] Sent: 27 October 2015 23:08 To: [email protected]; [email protected] Subject: [ANN] Apache ServiceMix 6.0.1 released! The ServiceMix team is pleased to announce the availability of Apache ServiceMix 6.0.1. This new patch release contains a few bug fixes and picks up new versions of Apache Karaf, Apache ActiveMQ, Apache Camel and Apache CXF. Major dependency versions for this release: * Activiti 5.17.0 * Apache ActiveMQ 5.12.1 * Apache Camel 2.15.3 * Apache CXF 3.0.6 * Apache Karaf 3.0.5 More information about this new release can be found at http://servicemix.apache.org/downloads/servicemix-6.0.1.html
