Re: MDB and IBM WS MQ 7.5 Only one shot

I found solution :) This is a bug, fixed only on Tomee 1.6 branch :( Application, deployed on current 1.6.1 snapshot work well. -- View this message in context: http://openejb.979440.n4.nabble.com/MDB-and-IBM-WS-MQ-7-5-Only-one-shot-tp4668089p4668110.html Sent from the OpenEJB User mailing

Re: disable log for Removing non-required WorkContextHandler INFO messages

you mean - edit $tomee/config/logging.properties - comment handlers = 1catalina.org.apache.juli.FileHandler, 2localhost.org.apache.juli.FileHandler, 3manager.org.apache.juli.FileHandler, 4host-manager.org.apache.juli.FileHandler, java.util.logging.ConsoleHandler - uncomment handlers =

Re: disable log for Removing non-required WorkContextHandler INFO messages

sorry, I was wrong it was an eclipse issue your answer was right thanks [] Leo On Wed, Mar 5, 2014 at 10:04 AM, Leonardo K. Shikida shik...@gmail.comwrote: you mean - edit $tomee/config/logging.properties - comment handlers = 1catalina.org.apache.juli.FileHandler,

Re: disable log for Removing non-required WorkContextHandler INFO messages

Correct. I wanted this for the longest time, and mentioned it a few times in the list, finally the last time I sent mail about it, we finally resolved it via Romain's recommended solution in this thread. :-) On Mar 5, 2014 8:17 AM, Leonardo K. Shikida shik...@gmail.com wrote: sorry, I was wrong

Re: CODI WindowScoped Beans replication

@romain: instances of JsfWindowContext are stored in EditableWindowContextManagerProxy which is (cdi-)session-scoped. (esp. to benefit from session replication,...) regards, gerhard 2014-02-12 12:36 GMT+01:00 Romain Manni-Bucau rmannibu...@gmail.com: sorry, I don't get the question. If

Re: CODI WindowScoped Beans replication

@Gerhard: that's what I thought @Dimitry: maybe check logs, you should see beans persisted accross the cluster after each request Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau

tomee 1.6.1-snapshot tomcat7:exec-war-only failure

Hello, trying to embed tomee into a tomcat 7 executable war via tomcat7-m-p:2.0 (2.1 and 2.2 have huge failures). The executable war is built and seems to want to run except it takes an exception on start up: https://gist.github.com/jieryn/312e8d14fae84ee7da95 This is with pom.xml and

Re: tomee 1.6.1-snapshot tomcat7:exec-war-only failure

It needs a npe protection i was not able to commit tonight (ill try tmr if nby beats be) Thats a case you cant get with normal tomcat/tomee actually. Le 5 mars 2014 20:59, jieryn jie...@gmail.com a écrit : Hello, trying to embed tomee into a tomcat 7 executable war via tomcat7-m-p:2.0 (2.1 and

Re: tomee 1.6.1-snapshot tomcat7:exec-war-only failure

I manually applied your patch found here: https://gist.github.com/rmannibucau/89a60459dd7ed72a560d I confirm that this fixes the problem, and I can run tomee-embedded with tomcat7-m-p:exec-war. Maybe tomee-m-p should be taught how to do this? The java -jar technique is quite powerful. Thanks

Re: tomee 1.6.1-snapshot tomcat7:exec-war-only failure

Actually i started to hack it when i added build goal but the fact the main creates a faked instance in .extract made me thought it was useless...we can still add it btw Le 6 mars 2014 01:20, jieryn jie...@gmail.com a écrit : I manually applied your patch found here:

Re: tomee 1.6.1-snapshot tomcat7:exec-war-only failure

committed + asked Olivier if we can enhance tomcat plugin to make it easier without forking Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-03-06 7:19 GMT+01:00 Romain