Search:

There is definitely no such assertion in BridgeMethodResolver in the latest 2.5.6 code (as committed on July 22nd!).

You could also try downloading the very latest 2.5.6 snapshot and see whether...

It looks like you're running against an old 2.5.4 spring-core.jar there. Make sure that you upgrade *all* of your spring module jars to 2.5.6 (where that assertion in BridgeMethodResolver is gone)!
...

This issue apparently only shows in deployment environments that eagerly resolve such service declarations in the "META-INF/services" directory (which WebSphere seems to do). In regular deployment...

FYI, there is an enhancement request in our JIRA: http://jira.springframework.org/browse/SPR-2495

However, there is no such StatelessSession support at this time. It might happen in the...

With a topic, you'll effectively have to restrict concurrency to 1 consumer: Simply leave the default setting. Otherwise you'll receive the same message multiple times on the same node... This is a...

Well, it's up to the JMS provider to redeliver the message to your DMLC. Configuring the JMS provider for appropriate retry limits and backoff delays is usually sufficient. Is there anything more...

Given your configuration, DefaultMessageListenerContainer should actually cache the connection, sessions and even consumers - since the default is CACHE_CONSUMER if not specifying an external...

The log level is arguably too high there: This is only a temporary error than can be recovered. As of Spring 2.5.2 and 2.0.9, I've changed the log level to INFO. The stacktrace will now even only get...

It seems that your RMISubmissionManagerController has an overridden finalize() method, and Spring's Cglib2AopProxy doesn't properly detect this. I've fixed Cglib2AopProxy to not dispatch such an...

I'm no Sybase expert, but as far as I can infer from the driver documentation, the "chained" property can be set at the JDBC URL level. So provided that your DataSource is driver-based, you should be...

It seems that you're not defining nested ApplicationContexts there in your beanRefContext.xml file... Check out the javadoc of "org.springframework.beans.factory.access.SingletonBeanFactoryLocator"...

Spring Security 2.0 will be compatible with both Spring 2.0 and Spring 2.5. In general, all our upcoming portfolio releases will be supporting Spring 2.5 as far as possible.

Juergen

@ModelAttribute-annotated methods will be executed before the chosen @RequestMapping-annotated handler method. They effectively pre-populate the implicit model with specific attributes, often loaded...

As pointed out in that other thread as well: Have you tried this against Spring 2.5 or one of the recent Spring 2.0.8 snapshots? This very much looks like an issue we've fixed there already:
...

I'm afraid you'll have to upgrade to Spring 2.0 or 2.5. The old Spring 1.2 generation just supports synchronous receiving of messages, with the entire async functionality being available in Spring...

JMS brokers are very much optimized for throughput of many messages - without transactional guarantees. This unfortunately means that, when enforcing transactions, the broker's throughput decreases...

This seems to be the state that things are left when not acknowledging a message in CLIENT_ACKNOWLEGDE mode on WebSphere MQ.

Consider switching to transacted Sessions: property "sessionTransacted"...

<jms:listener-container>'s "concurrency" attribute actually maps to DefaultMessageListenerContainer's "maxConcurrentConsumers" settings, which probably explains the difference that you're seeing. The...

This generally requires the use of separate DefaultMessageListenerContainer instances: one per message selector.

Consider the use of Spring 2.5's <jms:listener-container> tag, which allows for the...

The primary difference between the JCA style and the JMS style of setting up a listener is that the JCA style has built-in support for dynamic scaling (in terms of concurrent receiving of messages),...

The JCA SPI contract doesn't have default support for local transactions, hence Spring's <jms:jca-listener-container> support uses smart detection of provider-specific functionality here. For...

There are only really two options: Either suppress those warnings through corresponding WAS configuration (as indicated in that TSS thread), or use Spring's JtaTransactionManager for talking to the...

Check out the "org.springframework.remoting.jaxws" package javadoc for Spring 2.5's JAX-WS support in the meantime. We'll be updating the reference documentation as soon as possible.

Juergen

Your ExampleListener code seems to be calling the "Session.createProducer" method which is only available in JMS 1.1 = J2EE 1.4 or above! Since you're in a J2EE 1.3 environment, meaning JMS 1.0.2,...

This should work fine when using a shared Connection... DMLC's "clientId" property only applies to such a shared Connection setup in the first place.

The number of concurrent consumers is...