2010/7/30 David Blevins :
>
> 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 ("Ma
> 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:
> 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 th
>> 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
> pr
> Haven't seen this before but looks like it's related to the javaagent and
> dynamically attaching. Maybe try running the setup to put the agent on the
> command line.
Note, I'm using openejb 3.1 as a webapp in Tomcat 6.0.28
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 org.apache.catalina.core.Standar
>> 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 diffe
> 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 threa
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 wi
> 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
>
> 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
11 matches
Mail list logo
