Home > SOA Suite > Pitfall with active-passive oc4j

Pitfall with active-passive oc4j

We recently had some issues with SOA Suite 10.1.3.3 using an active-passive oc4j configured in the usual way with service-failover and service-weight added and numprocs removed.

Service-failover added, numprocs removed

Extract from opmn.xml

Failover worked, but sometimes opmn started BOTH instances. Only one should be running. To produce the error:

node 1: opmnctl shutdown
(wait until down)
node 2: opmnctl shutdown
(wait until down)
node 2: opmnctl startall
(wait until up)
node 1: opmnctl startall
(wait until up – running on node 2, stopped on node 1)
node 2: opmnctl stopproc process-type=oc4j_apsa
(wait until down – down on node 2, running on node 1)
node 1: opmnctl stopproc process-type=oc4j_apsa
(wait until down – stopped on both)
node 2: opmnctl startproc process-type=oc4j_apsa
(wait until up – started on BOTH nodes!!!)

The solution was simple, though not obvious. It is not good enough to specify process-type or gid, one has to supply ias-component as well! To start:

opmnctl startproc ias-component=apsa_group process-type=oc4j_apsa

To stop:

opmnctl stopproc ias-component=apsa_group process-type=oc4j_apsa

To debug the odd behaviour opmnctl debug was invaluable.

Advertisements
Categories: SOA Suite
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: