RE: Using a differnent version of a jar than the one supplied with Tomee

2013-09-27 Thread Adam Steen
Hi Romain I tried what you suggested and it appears everything is behaving correctly, openejb.classloader.forced-load=org.quartz worked a treat. Thank you for your help Cheers Adam -Original Message- From: Romain Manni-Bucau [mailto:rmannibu...@gmail.com] Sent: Friday, 27 September 20

Re: JNDI_LOOKUP error=Cannot open input stream to server

2013-09-27 Thread wlad
Romain Manni-Bucau wrote > is your client using the same version as the server? It's a simple client, just plain "public static void main" method, that should demonstrate using of JNDI service for EJB bean lookup, and calling bean method. Here is the zipped eclipse project, so you can try to run

Re: JNDI_LOOKUP error=Cannot open input stream to server

2013-09-27 Thread Romain Manni-Bucau
the client version is different from the server one it seems. Please align it *Romain Manni-Bucau* *Twitter: @rmannibucau * *Blog: **http://rmannibucau.wordpress.com/* *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: h

Re: JNDI_LOOKUP error=Cannot open input stream to server

2013-09-27 Thread wlad
Romain Manni-Bucau wrote > the client version is different from the server one it seems. Please align > it I have downloaded another Tomcat/EE version: "apache-tomee-plus-1.5.0" and set it up with Eclipse. But still, I am not able to run this example. Log message I am getting now is: Buildfile: /

Re: JNDI_LOOKUP error=Cannot open input stream to server

2013-09-27 Thread Romain Manni-Bucau
i thought you used tomee 1.5.2 *Romain Manni-Bucau* *Twitter: @rmannibucau * *Blog: **http://rmannibucau.wordpress.com/* *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https://github.com/rmannibucau* 2013/9/27 wla

Re: JNDI_LOOKUP error=Cannot open input stream to server

2013-09-27 Thread wlad
I did use tomee 1.5.2 at first, but then when you mentioned version aligning I tried with 1.5.0, but nothing. -- View this message in context: http://openejb.979440.n4.nabble.com/JNDI-LOOKUP-error-Cannot-open-input-stream-to-server-tp4665304p4665320.html Sent from the OpenEJB User mailing list

Re: JNDI_LOOKUP error=Cannot open input stream to server

2013-09-27 Thread Romain Manni-Bucau
Hi tested on trunk (I don't have 1.5 anymore locally and not the time to setup it through ant): ┌( rmannibucau @ ubuntu )─( 1.7.0_40 -:- 3.1.0 ) └( /tmp/Vezbe03 )·> ant runClient1 Buildfile: /tmp/Vezbe03/build.xml runClient1: [java] Sep 27, 2013 3:45:02 PM org.apache.openejb.client.EventLog

Re: JNDI_LOOKUP error=Cannot open input stream to server

2013-09-27 Thread wlad
You made it, nice to see it running. I'm still struggling with it, still getting error: Buildfile: /home/vladimir/workspace/MBS-Vezbe/Vezbe03/build.xml runClient1: [java] Sep 27, 2013 4:34:26 PM org.apache.openejb.client.EventLogger log [java] INFO: RemoteInitialContextCreated{providerU

Unsupported HTTP Request Method :OPTIONS

2013-09-27 Thread Can Eskikaya
I have a openejb 4.6.0 standalone server running and a method with javax.ws.rs.OPTIONS; annotaded. The server starts and shows me the line: ep 27, 2013 4:07:03 PM org.apache.openejb.server.cxf.rs.CxfRsHttpListener logEndpoints NFO: OPTIONS http://0.0.0.0:4204/dcservice/api/node/show

Re: Unsupported HTTP Request Method :OPTIONS

2013-09-27 Thread Romain Manni-Bucau
thanks, that's fixed: https://issues.apache.org/jira/browse/OPENEJB-2038 *Romain Manni-Bucau* *Twitter: @rmannibucau * *Blog: **http://rmannibucau.wordpress.com/* *LinkedIn: **http://fr.linkedin.com/in/rmannibucau* *Github: https:

Re: JNDI_LOOKUP error=Cannot open input stream to server

2013-09-27 Thread Romain Manni-Bucau
Your script was referring 1.5.2, are you sure you updated it to use 1.5.0 (or update openejb-client to 4.5.2)? *Romain Manni-Bucau* *Twitter: @rmannibucau * *Blog: **http://rmannibucau.wordpress.com/* *LinkedIn: **http://fr.linked

Re: JNDI_LOOKUP error=Cannot open input stream to server

2013-09-27 Thread wlad
Romain Manni-Bucau wrote > Your script was referring 1.5.2, are you sure you updated it to use 1.5.0 I am using tomee 1.5.2. I have only tried to run this example with 1.5.0, but didn't help, so I've switched back to 1.5.2. Romain Manni-Bucau wrote > (or update openejb-client to 4.5.2)? (May s

Re: JNDI_LOOKUP error=Cannot open input stream to server

2013-09-27 Thread wlad
This is what I've just tried(update from openejb-client-4.5.0 to openejb-client-4.5.2): - copy ...tomee-1.5.2/lib/openejb-client-4.5.2.jar - paste in runtime-libs folder of my example - removed openejb-client-4.5.0.jar that was there Eclipse recognized openejb-client-4.5.2.jar under runtime-libs.

Re: JNDI_LOOKUP error=Cannot open input stream to server

2013-09-27 Thread Romain Manni-Bucau
Im pretty sure you have an environment issues since we use since the first release of tomee ejbd to be certified. Maybe start from an empty/clean environment. Le 27 sept. 2013 18:35, "wlad" a écrit : > This is what I've just tried(update from openejb-client-4.5.0 to > openejb-client-4.5.2): > > -

Re: JNDI_LOOKUP error=Cannot open input stream to server

2013-09-27 Thread wlad
Romain Manni-Bucau wrote > Maybe start from an empty/clean environment. Yes, it sounds like only solution. I will remove current Eclipse IDE, and install fresh one, and try everything from beginning. I will post the results here. Thanks for help. -- View this message in context: http://open

Re: Memory leak by openejb.pool.scheduler

2013-09-27 Thread zmirc
I've just seen the LEAK error logs of Tomme now on another production server, which runs 1.6.0 from 29.07.13. I'll try now with the latest Snapshot and come with feedback ASAP. Thanks. -- View this message in context: http://openejb.979440.n4.nabble.com/Memory-leak-by-openejb-pool-scheduler-tp4

Re: Memory leak by openejb.pool.scheduler

2013-09-27 Thread jieryn
Greetings, On Wed, Sep 25, 2013 at 12:39 PM, Romain Manni-Bucau wrote: > I was not able to reproduce the "leak" on trunk but only the other issue. I > opened https://issues.apache.org/jira/browse/TOMEE-1048 Thanks for that fix, I see it has dramatically improved 1.6.0-SNAPSHOT shutdown messages

Re: Memory leak by openejb.pool.scheduler

2013-09-27 Thread Romain Manni-Bucau
Hi Thats related to hsql. Define your datasource in src/main/tomee/conf/tomee.xml and it should be gone Side note: you can type quit to shutdown the container instead of ctl+c with mvn plugin Le 27 sept. 2013 21:12, "jieryn" a écrit : > Greetings, > > On Wed, Sep 25, 2013 at 12:39 PM, Romain Ma