Database Reference
In-Depth Information
Before changing the EJB timeout settings, the SOA managed
server(s) should be shut down. Otherwise, you will receive er-
rors while activating the changes. Furthermore,
Plan.xml
for the SOA Infra would have to be copied to all managed
servers (if not on shared storage) and the managed servers
would have to be restarted.
The plan file can be located in your middleware installation
folder at
$MW_HOME/Oracle_SOA1/soa/applications/
Plan.xml
. Ensure that no other file is named
Plan.xml
as
the same file may be used for changes made to resource ad-
apters. A standard convention is to use
DBPlan.xml
for DB
Adapter,
JMSPlan.xml
for JMS,
MQPlan.xml
for MQ Ad-
apter, and so on, so that the plan files are not overwritten as
the adapters are configured.
Tuning connection backlog buffering
More often than not, your SOA infrastructure will be exposing high throughput,
low latency, and synchronous composite applications. If client applications in-
voking your composite endpoints complain of getting
Connection Refused
messages, when trying to access your endpoints, and no other messages ap-
pear in the server logs, then your
Accept Backlog
value may need to be tuned.
The
Accept Backlog
tunes the number of TCP connections that the server in-
stance can buffer in the wait queue. Raise the
Accept Backlog
value from the
default by 25 percent to 30 percent to overcome connection refusals. Continue
increasing the value by 25 percent until the messages cease to appear. For ex-
ample, increase the default value of 300 to around 400. This can be changed
in the
Tuning
tab available under
Environment
|
Servers
|
[soa_server]
|
Tun-
ing
.
