JPA isn't replaced by JTA...it's hard to speculate what your developers are
saying given the different integration approaches that can be done
with JPA/JTA/EE...(ie perhaps they're now using an extended JTA solution,
perhaps they simply changed some JPA handing from container managed to bean
managed, perhaps they mean the switch from JPA to JDBC and are explicitly
handling the JTA themselves, etc etc).
Have you been successful in deploying this application in a non-clustered
setup? (I ask, because it seems you might not have and removing some
complexity may help diagnose the problems). The application shouldn't
depend on the cluster (decoupled from the platform), so you should be able
to deploy it to a simple single-domain setup. I would suggest trying it on
there...and if you don't have any luck, post the exceptions you find in the
server.log so we can figure out what is going on.
Regards,
S
On Sun, Aug 26, 2012 at 1:00 PM, <forums_at_java.net> wrote:
> Thanks for give me some direction ;) The environment I'm setup is a cluster
> with 2 nodes. Previously the deployable app was JPA, but the developers
> change it to JTA for ( is that correct ? assuming the production will be
> cluster ). There are any specific configuration that I have to set in my
> app
> to "initialize the pool" ( JTA / JPA ) or just the default assumptions of
> JTA/JPA do it ? It's not a first time I tried to deploy this App. I
> re-installed this cluster from scratch to make sure everything is right.
> The
> last deploy I tried in the old one fail in this scenario you describe ( app
> consuming connection resource target to connection pool ). Any tough would
> be
> helpful. Thanks again. Best Regards. Anderson Cruz
>
>
> --
>
> [Message sent by forum member 'anderson.cruz']
>
> View Post: http://forums.java.net/node/**889565<http://forums.java.net/node/889565>
>
>
>