The application fails to create beans of type com.amazonaws.ClientConfiguration due to
Caused by: org.springframework.beans.FatalBeanException: Failed to obtain BeanInfo for class [com.amazonaws.ClientConfiguration]; nested exception is java.beans.IntrospectionException: type mismatch between indexed and non-indexed methods: socketBufferSizeHints
... 43 more
Caused by: java.beans.IntrospectionException: type mismatch between indexed and non-indexed methods: socketBufferSizeHints
The error does not occur in release 3.1.2 or earlier versions.
Matthias, this issue is already resolved in 3.2.0.BUILD-SNAPSHOT, i.e. in the upcoming 3.2 RC1. Is it an option for you to upgrade to that? That particular fix cannot be backported to 3.1.x in a straightforward fashion; this bug can be fixed in any case, but thought I'd mention that 3.2 will "just work" already.
The problem is that we are not allowed to go to production without a final release. However, looking at the road map, the 3.2 GA is not far away so we may just as well use the RC builds in our dev environment for now.
You mention that the bug can be fixed, is that something that you will do, or is it a workaround to our code? If it is fix on our side, can you point us in the right direction?
It's something on our side; there have been a number of similar bugs with an internal component called ExtendedBeanInfo. This class has been removed from the code path for the vast majority of use cases in 3.2, but the change is too significant to backport to 3.1.x for various reasons.
This just needs to be tracked down in ExtendedBeanInfo and fixed. Phil Webb, perhaps you'd like to take a look as you're now familiar with this code. In any case, we'll fix it up for 3.1.4, but it's likely that we'll ship 3.2 GA even before 3.1.4 at this point, so to your comment above, if you're good with using 3.1 RC1 in your dev builds, you're probably even better off (plus you'll have access to everything in 3.2 going forward!)