Feedback on TomEE 1.0.0-beta-2
Hi All tests seem to work well, but I get this error no matter what I do (I'm starting using bin/startup.bat) ERROR: OpenEJB webapp was not found (The first line in the console logs) I assume I can ignore, but thought it's worth mentioning if not already known... Thanks
Re: Feedback on TomEE 1.0.0-beta-2
Hi Eran, Yes I get that too, sometimes twice near the top of the log. I think it's the EJBListener trying to initialise but the openejb app (or "tomee" app as it's now known) hasn't started yet. Safe to ignore. Best Regards, Neale - Original Message - From: "Eran Medan" To: Sent: Monday, April 16, 2012 5:16 PM Subject: Feedback on TomEE 1.0.0-beta-2 Hi All tests seem to work well, but I get this error no matter what I do (I'm starting using bin/startup.bat) ERROR: OpenEJB webapp was not found (The first line in the console logs) I assume I can ignore, but thought it's worth mentioning if not already known... Thanks
Re: Feedback on TomEE 1.0.0-beta-2
Hi, yep ignore it, the next release coming soon improove a bit this and log the found webapp when found. We introduced it because sometimes a NPE could happen and no log was present. This log replaced the NPE but the algorithm has a fallback a bit later which can make the container working so sometimes (the case you have) it is safe to ignore this error. - Romain 2012/4/16 Neale Rudd > Hi Eran, > > Yes I get that too, sometimes twice near the top of the log. > > I think it's the EJBListener trying to initialise but the openejb app (or > "tomee" app as it's now known) hasn't started yet. > > Safe to ignore. > > Best Regards, > Neale > > > - Original Message - From: "Eran Medan" > To: > Sent: Monday, April 16, 2012 5:16 PM > Subject: Feedback on TomEE 1.0.0-beta-2 > > > > Hi >> >> All tests seem to work well, but I get this error no matter what I do (I'm >> starting using bin/startup.bat) >> >> ERROR: OpenEJB webapp was not found >> >> (The first line in the console logs) >> >> I assume I can ignore, but thought it's worth mentioning if not already >> known... >> >> Thanks >> >> >
TomEE startup time improvements in 1.0.0 vs beta2
Hey Guys, Been following the latest commits and wanted to report the speed improvements we've noticed in TomEE startup time to the list. This is a comparison of beta2 vs the current 1.0.0 preview in the repository. Railo 3.3 Custom (44mb WAR): 21.3% of beta2 startup time (369% faster) Lift/Scala sample app (23mb WAR): 43.8% of beta2 startup time (128% faster) Confluence 3.5.5 (149mb unpacked): 37.6% of beta2 startup time (166% faster) Also interesting to note that beta2 requires more RAM, it will not start Confluence with a 256mb heap. The 1.0.0 preview starts it ok. Great work, 1.0.0 is looking very snappy! Best Regards, Neale Rudd Metawerx Java Hosting http://www.metawerx.net
Re: can't persist value in TransactionSynchronizationRegistry
Ok our last message was not sent to this mailing list so here we are: / *ME* Wow ok, thanks for the answer. So I understand a bit more: So, first our code is not a so good idea. I thought we would get the connection as a connection pool would do and not the transaction as you've said... and so we have a second problem, once created this connection is never released even after the hibernate close() call. I thought creating entitymanager and number of connection created was linked, but maybe there is something else in here. Thank you for your reply *YOU* Sounds like you might have configured datasources outside the view of the container. Common wrong turn is to configure connection information (drivers, db url, user, pass) in the persistence.xml. This will bypass all of the connection pooling provided by the container and you can easily get leaks. If you configure your datasource like so: http://openejb.apache.org/configuring-datasources.html Then in your persistence.xml just point to the datasource via and , then all should be good. Hope this helps! -David/ So in hibernate manual i've seen this as you've said: /The following properties can only be used in a SE environment where no datasource/JNDI is available: javax.persistence.jdbc.driver: the fully qualified class name of the driver class javax.persistence.jdbc.url: the driver specific URL javax.persistence.jdbc.user the user name used for the database connection javax.persistence.jdbc.password the password used for the database connection/ our persistence.xml doesn't define that, all is defined externally with properties and set int openejb properties: props.put(ds, "new://Resource?type=DataSource"); props.put(ds + ".JdbcDriver", helper.getDriver()); props.put(ds + ".JdbcUrl", url); props.put(ds + ".UserName", user); Is there a way to monitor with jmx connection the openEJB pool?, i've launched jconsole but I can monitor the EJB pool but that's all. thank you -- View this message in context: http://openejb.979440.n4.nabble.com/can-t-persist-value-in-TransactionSynchronizationRegistry-tp4552345p4561697.html Sent from the OpenEJB User mailing list archive at Nabble.com.
How do I *send* JMS messages from an MDB?
I have problems sending JMS messages from my MDB. This MDB listens on a queue and then calls an EJB that updates persistent storage. The EJB then sends out a notification to a JMS topic. All this used to work in GlassFish, but on TomEE-plus I always get this error that stops the notification from being sent: javax.jms.JMSException: The resource is allready being used in transaction context. The error message doesn't specify which resource is the culprit, but I guess it means the JMS Session? My EJB uses an injected ConnectionFactory, just like in the OpenEJB examples. Shouldn't that work also when the EJB is called from an MDB, using one big nice container-managed transaction that starts when the incoming queue message is received? Version: apache-tomee-plus-1.0.0-beta-2 -- Björn Danielsson Cuspy Code AB
Re: How do I *send* JMS messages from an MDB?
Hi, It should work, can you reproduce it in a uniy test? Le 16 avr. 2012 16:48, "Bjorn Danielsson" a écrit : > I have problems sending JMS messages from my MDB. This MDB > listens on a queue and then calls an EJB that updates persistent > storage. The EJB then sends out a notification to a JMS topic. > > All this used to work in GlassFish, but on TomEE-plus I always > get this error that stops the notification from being sent: > > javax.jms.JMSException: The resource is allready being used in transaction > context. > > The error message doesn't specify which resource is the culprit, > but I guess it means the JMS Session? My EJB uses an injected > ConnectionFactory, just like in the OpenEJB examples. Shouldn't > that work also when the EJB is called from an MDB, using one > big nice container-managed transaction that starts when the > incoming queue message is received? > > Version: apache-tomee-plus-1.0.0-beta-2 > > -- > Björn Danielsson > Cuspy Code AB >
Re: How do I *send* JMS messages from an MDB?
Hi, Thanks for your reassuring reply! I have now written a simple test for this, and of course now the test works. So mea culpa, and now I only have to figure out in what way my application code differs from my 100-line test. I'll post back here again when I find the reason, in case anyone else gets this error "resource is allready being used in transaction" and googles it. -- Björn Danielsson Cuspy Code AB Romain Manni-Bucau wrote: > Hi, > > It should work, can you reproduce it in a uniy test? > Le 16 avr. 2012 16:48, "Bjorn Danielsson" > a écrit : > >> I have problems sending JMS messages from my MDB. This MDB >> listens on a queue and then calls an EJB that updates persistent >> storage. The EJB then sends out a notification to a JMS topic. >> >> All this used to work in GlassFish, but on TomEE-plus I always >> get this error that stops the notification from being sent: >> >> javax.jms.JMSException: The resource is allready being used in transaction >> context. >> >> The error message doesn't specify which resource is the culprit, >> but I guess it means the JMS Session? My EJB uses an injected >> ConnectionFactory, just like in the OpenEJB examples. Shouldn't >> that work also when the EJB is called from an MDB, using one >> big nice container-managed transaction that starts when the >> incoming queue message is received? >> >> Version: apache-tomee-plus-1.0.0-beta-2 >> >> -- >> Björn Danielsson >> Cuspy Code AB >>
