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
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:
Sen
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
some
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/Scal
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 w
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
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 t
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 ge