Problem
What is the root cause for this error in ACS-server.log? And what can be done?2011-08-19 17:06:38,923 [] ERROR ACS - getACSManagerInternal() problem getting ACSManager javax.naming.CommunicationException [Root exception is java.rmi.RemoteException: Service unavailable.], returning null
2011-08-19 17:06:38,923 [] ERROR ACS - getACSManager() could not acquire handle to ACSManager on application server
Environment
Solaris 10
Oracle 10
JBoss 4.0.4GA
apache Tomcat 5.5.25
Cause
The customer uses 4 interfaces per server and wants to let different communications streams run through a different interface.
JBoss standard binds to all interfaces and we had to figure out a way to create fix bindings to interfaces for SG WebGUI and for managed services.
Solution
Changes made:
1) /usr/local/sprt//servicegateway/jboss_launch.sh added:
# The ip address
IP_ADDRESS=193.192.238.154
to the Configurable section.
and the -b option to the launch command:
## Command to launch if successful connection is made
LAUNCH_COMMAND="$DOMAIN_BASE_DIR/bin/run.sh -c $INSTANCE_NAME -b $IP_ADDRESS"
2) To bind the Web GUI address I made changes to:
/opt/jboss-4.0.4.GA/server//deploy/jbossweb-tomcat55.sar/server.xml
changed
into
In above example the managed services are bound to the .154 address and the Web GUI is bound to the .180 address.
1) /usr/local/sprt//servicegateway/jboss_launch.sh added:
# The ip address
IP_ADDRESS=193.192.238.154
to the Configurable section.
and the -b option to the launch command:
## Command to launch if successful connection is made
LAUNCH_COMMAND="$DOMAIN_BASE_DIR/bin/run.sh -c $INSTANCE_NAME -b $IP_ADDRESS"
2) To bind the Web GUI address I made changes to:
/opt/jboss-4.0.4.GA/server//deploy/jbossweb-tomcat55.sar/server.xml
changed
into
In above example the managed services are bound to the .154 address and the Web GUI is bound to the .180 address.
All works fine including JBoss cluster and both Web GUI's used.
Priyanka Bhotika
Comments