1 of 1 people found this helpful
It is trying to connect to the other service instances in the domain, as in domain mode there is more than one process. It it possible you have a firewall that is blocking this?
Thanks for replying. My company chose to use the standalone and am trying to get the applictaion deployed in there I am getting the exception below. I am using iBatis in the persistence layer ... is the exception related to that ?
hc-sysmgmt-sample.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."hc-sysmgmt-sample.war".INST
ALL: Failed to process phase INSTALL of deployment "hc-sysmgmt-sample.war"
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_20]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_20]
at java.lang.Thread.run(Thread.java:619) [:1.6.0_20]
Caused by: java.lang.NullPointerException
... 5 more
No, the persistence issue is not causing the Connection refused error. It sounds like two separate problems to me.
What does your persistence.xml look like? Currrently, AS7 works with Hibernate 4 as the persistence provider. We added a way to work with Hibernate 3 as well recently. I googled for information on IBatis but didn't get clear answers. Is it a JPA 2.0 persistence provider? We are also working on the ability to plug in other persistence providers (that effort is continuing on a git branch).
No persistence xml is being used. The Spring is being bound to the iBatis in a context xml. The jndi definition to the datasource are being defined a spring context file and is used in iBatis definitions. The deployment's working fine in Weblogic. The error's appearing when I try to deploy the same war in JBoss AS7.
As per my knowledge iBatis doesnt match the JPA 2.0. It give's more control on SQL statements. Is iBatis in list of persistence provider plug ins that's being worked upon ?