> -----Original Message----- > From: KARR, DAVID (ATTCINW) > Sent: Sunday, January 31, 2010 12:17 PM > To: [email protected] > Subject: Changing to use log4j logging causes error about missing Java > agent > > I've been working ok with my OpenJPA 1.2.2 app for a while. I'm using > build-time enhancement, and "openjpa.RuntimeUnenhancedClasses" is set > to > "unsupported". I had my "openjpa.Log" property set with the "basic" > strategy, not using log4j or commons-logging. It was working fine. I > then decided since I was using log4j with other components, I wanted > openjpa to use that also. I changed the value to "log4j", then added a > "logger" element in my log4j.xml for openjpa. I started up the server, > and got the exception that follows this. > > I don't see why it suddenly thinks I need to use a -javaagent. I'd > prefer not to do this. I certainly don't need "load-time class > transformation", if that's what the build-time enhancer does.
Additional information: It appears it isn't just happening when I try to use log4j. If I have any "openjpa.Log" setting that enables logging, I get this error. If I turn off logging completely, the app starts up and works fine. I had logging on all the time when I was developing the app with OpenJPA 1.2.1. I recently upgraded to 1.2.2, and about that time I turned off logging. It seems like now that I'm using 1.2.2, I'm getting this new error if I try to use logging.
