The other interesting thing is that the server.log contains out of memory
errors before the JVM invocation that started this server.
So at some time in the past, the server ran out of memory and was killed.
Then my colleague did an asadmin start-domain, and ran an asadmin deploy
our/ear/file, the results of which you see here.
I've noticed on many occasions that the Felix cache, whatever that is (I know
it has to do with OSGI, about which I remain blissfully ignorant, and about
which I wish to remain blissfully ignorant :-)), when removed, cleans lots of
things up.
Is it possible that the cache--whatever it caches--has some stale corrupt
information left over from an OOME that is impacting *this* startup?
Best,
Laird
--
[Message sent by forum member 'ljnelson']
View Post: http://forums.java.net/node/713753