Re: openejb 3.1 error on start under SnowLeopard

2010-08-01 Thread Henri Gomez
2010/7/30 David Blevins david.blev...@visi.com: On Jul 28, 2010, at 6:18 AM, Henri Gomez wrote: Dynamically adding a javaagent should work in java 1.6 and clearly the linux jmv supports it just fine.  Seems like a VM bug in the Snow Leopard box (MacosxAttachProvider MacosxVirtualMachine

Re: openejb 3.1 error on start under SnowLeopard

2010-07-28 Thread Henri Gomez
You might be able to pass it via the JAVA_OPTS variable.  Basically the goal is to copy the openejb-javaagent-3.x.x.jar into the tomcat.home/lib/ directory and make sure this java option is getting passed to the jvm:  -javaagent:$CATALINA_HOME/lib/openejb-javaagent-3.x.x.jar When the

Re: openejb 3.1 error on start under SnowLeopard

2010-07-28 Thread Henri Gomez
Dynamically adding a javaagent should work in java 1.6 and clearly the linux jmv supports it just fine.  Seems like a VM bug in the Snow Leopard box (MacosxAttachProvider MacosxVirtualMachine) Caused by: com.sun.tools.attach.AttachNotSupportedException: Unable to open socket file: target

Re: openejb 3.1 error on start under SnowLeopard

2010-07-24 Thread Henri Gomez
Note, I'm using openejb 3.1 as a webapp in Tomcat 6.0.28 Yep.  The setup should copy the agent jar into the Tomcat lib dir and then mod the catalina.sh so that there's a '-javaagent:' flag passed to the vm on Tomcat startup.  That will ensure the agent is there on boot and should prevent

openejb 3.1 error on start under SnowLeopard

2010-07-16 Thread Henri Gomez
Hi to all, I experience a very strange error on my SnowLeopard for an application using OpenEJB 3.1. This apps works well on Windows but failed on OS/X : Here is the log : at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053) at

Re: persistence.xml in a Jar in Tomcat Common classloader (ERROR : PersistenceUnit already deployed)

2008-10-29 Thread Henri Gomez
In the 3.1 release changelog I could see : EAR-style classpath application discovery groups individual modules as an EAR allowing sharing of persistence units and improved connector and custom MDB deployment. Did it what we discussed in this thread ? That's actually a different feature.

Re: persistence.xml in a Jar in Tomcat Common classloader (ERROR : PersistenceUnit already deployed)

2008-10-28 Thread Henri Gomez
Could it be done for 3.1 release ? Hi to all, In the 3.1 release changelog I could see : EAR-style classpath application discovery groups individual modules as an EAR allowing sharing of persistence units and improved connector and custom MDB deployment. Did it what we discussed in this

Re: persistence.xml in a Jar in Tomcat Common classloader (ERROR : PersistenceUnit already deployed)

2008-10-21 Thread Henri Gomez
Any news about this request ? Could it be done for 3.1 release ? Thanks Le 16 oct. 08 à 12:13, Maxime Thieu [EMAIL PROTECTED] a écrit : Hi David, Thanks for your anwser. I allready try including persistence.xml in my webapp. But this doesn't works because I have Service in service.jar

Re: persistence.xml in a Jar in Tomcat Common classloader (ERROR : PersistenceUnit already deployed)

2008-10-16 Thread Henri Gomez
Not entirely sure though if that's really what you're after. We don't currently have any support for global persistence units. Meaning say a persistence unit declared outside of an ear at server level and available to all ears/apps deployed. It might be something we could add if that's

Re: OpenEJB in an OSGi container

2008-10-15 Thread Henri Gomez
Succeeded to load OpenEJB in Felix 1.2.1 OSGi container. See https://issues.apache.org/jira/browse/OPENEJB-921 for details. It's not perfect but it fits my needs (for now - just had to produce a proof of concept). /zog What about a wiki/blob about this Proof Of Concept. Good works