The problem is that, if I create a simple webapp without database, richfaces,
etc and try to deploy in GF 3.1.2.2, all works fine. I think there is a
problem with Timers registered by GF 3.1.2.2 that are better managed by
3.1.1. I made the following test in 3.1.2.2: 1) start GF 2) deploy webapp1 3)
stop GF 4) start GF 5) deploy webapp2 ALL worked fine!!! But I hadn't the
same luck deploying webapp3. I think GF 3.1.2.2 leaves the Timers "arrested"
and arises some conflits here. My webapp has 4 Timers configured by
ejb-jar.xml. But, again, this doesn't occur in GF 3.1.1, and today I have 7
same webapps running fine.
--
[Message sent by forum member 'edilmar']
View Post: http://forums.java.net/node/891698