Search:

Is the task scheduler just used for polling, or is the message processed (i.e. via a service activator on the destination channel) on the same thread? The thread pool makes sense to me if message...

I'm using the following ftp inbound channel adapter from spring-integration-ftp 2.1.4.RELEASE:



<int-ftp:inbound-channel-adapter id="ftpInboundAdapter"
channel="ftpInChannel"...

When using TransactionAwareConnectionFactoryProxy and DMLC pointed to a DataSourceTransactionManager, I see the following spring trace logging on every DMLC polling interval:



2012-02-28...

ErrorHandler is only available in Spring 3.0+. Is there something equivalent in 2.5.6?

One more question. What is the difference between sessionTransacted and JmsTransactionManager?

OK, I believe I've nailed down the cause of the problems. The Websphere default messaging provider does not work with any of the DMLC caching strategies under any circumstances.

When...

hang on a second. See this page:

http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/index.jsp?topic=%2Fcom.ibm.websphere.express.doc%2Finfo%2Fexp%2Fae%2Ftmj_desap.html



Perhaps Websphere...

You stated earlier that with the default auto acknowledge mode, sessionTransacted set to false and no transactionManager, you may lose messages if you crash... Is that situation limited to JVM...

The javaworld article is an interesting read. If I understand correctly, the "Best Effort 1PC Pattern" will only be applied using a message listener that updates a database when...

Fair enough, I think the problems with sessionTransacted=false are websphere issues and I will pursue those through websphere support. What about the errors reported by websphere when using...

So the use of a transaction manager is mainly related to reliable delivery of the message to the listener. I also noticed that with sessionTransacted=true or a transaction manager, if you throw an...

What's the reasoning behind the following statement from DMLC javadocs:

It is strongly recommended to either set "sessionTransacted" to "true" or specify an external "transactionManager". See the...

I've switched to a very small test application that I can redeploy easily in websphere. I've attached a zip containing the trace.log file from several minutes of websphere running with the following...

I turned on trace logging in websphere with sessionTransacted=false and no transactionManager. I can observe JMS Connections being constantly created and destroyed, but keeping a constant pool size...

Would you expect to see leaking connections with no transactionManager and sessionTransacted set to false?

another update: on websphere with concurrentConsumers and no transactionManager specified the messaging provider leaks connections, eventually consuming all heap space and resulting in...

downgrading to 3.0.7-RELEASE works to correct this problem. I don't find a JIRA issue either, but I don't feel I understand the issue enough to report it.

2 (cont'd) sessionTransacted
Weblogic 10.3.5 - No runtime exceptions, flat resource usage, app does not shut down cleanly, throws following exception, but does eventually go to "prepared"...

No responses. Hmm.

I've done a *LOT* more detailed testing on this issue and found some interesting results when comparing various DMLC configurations on Websphere 8 and Weblogic 11g (10.3.5). I'm...

I'm working on an application that uses Spring DefaultMessageListenerContainer on Websphere using the default message provider (service integration bus). The behavior I'm seeing is that when not...

I've been banging my head against this issue for a couple days now.

I'm working on a web application that uses Spring and we just upgraded from Spring 2.5.5 to 3.1.0. We're encountering some kind...