I get the following warnings whenever I try to access datasource connection from a timer thread. 33aae011 ConnectionMan W J2CA0075W: An active transaction should be present while processing method allocateMCWrapper. 33aae011 ConnectionMan W J2CA0075W: An active transaction should be present while processing method initializeForUOW.
While I realize these warnings are harmless they still do flood the logs. Is there anyways to get rid of them? [ September 03, 2003: Message edited by: Joseph Magerramov ]
This is a new feature only available in WAS 5. As IBM continues to tighten the noose on developers ability to do interesting things in the app, even the ability to create a thread in a servlet will be denied. This is only a warning and you will need to come up with an alternate way to make db calls from a thread in the future. Maybe use an HTTP post at the designated interval???
Look, we're doing this because of the specifications -- we don't make this stuff up on our own, you know. It's not that we want to keep you from doing interesting things -- it's we want to follow the way that the J2EE specifications clearly dictate J2EE apps should work.
The way to do asynchronous database calls is either through JMS (see my recent Javaranch article on that) or (in WBI-Sf 5.1) through the use of Async beans.
Hi Kyle, hopefully you can help me. We just upgraded to WAS 5 this weekend and are seeing these messages for one particular part of our system. What's confusing me is, we don't use EJB's and our servlets do not spin threads. The part of the system that's throwing the message does use RMI. Do you have any idea what could be causing the messages? Does RMI do anything to cause it?
posted 15 years ago
or anyone can help, not just Kyle. Any help is appreciated.
If we don't do the shopping, we won't have anything for dinner. And I've invited this tiny ad: