• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Paul Clapham
  • Bear Bibeault
  • Jeanne Boyarsky
Sheriffs:
  • Ron McLeod
  • Tim Cooke
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Jj Roberts
  • Stephan van Hulst
  • Carey Brown
Bartenders:
  • salvin francis
  • Scott Selikoff
  • fred rosenberger

Warning when accessing datasource from a separate thread

 
Ranch Hand
Posts: 35
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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 ]
 
Greenhorn
Posts: 15
Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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???

Visit this page for more info:
http://www-1.ibm.com/support/docview.wss?rs=180&context=SSEQTP&q=J2CA0075W&uid=swg21109248&loc=en_US&cs=utf-8&lang=en+en
 
author
Posts: 3892
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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.

Kyle
 
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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?

Thanks!
 
Rob Desmarais
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
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:
the value of filler advertising in 2020
https://coderanch.com/t/730886/filler-advertising
reply
    Bookmark Topic Watch Topic
  • New Topic