PM07711: Allow the initialization of the On Demand Configuration component to be bypassed.

Fixes are available

APAR status

Closed as new function.

Error description

Allow the initialization of the On Demand Configuration
component to be bypassed.

Local fix

```
n/a
```

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server V6.1 and V7.0 not utilizing any On   *
*                  Demand Configuration functionality.         *
****************************************************************
* PROBLEM DESCRIPTION: The On Demand Configuration (ODC)       *
*                      component cannot be completely          *
*                      disabled resulting in unnecessary       *
*                      overhead.                               *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Currently you can only disable the communication between
processes for the On Demand Configuration (ODC) component and
all local ODC processing still occurs. This can result
unnecessary cpu and memory usage.

Problem conclusion

A new JVM property, ODCInit.disabled, has been introduced that
when set to 'true' will disable the On Demand Configuration
(ODC) components local processing and its communication
between processes. This will allow users to completely disable
ODC when its not being utilized preventing unnecessary overhead.

In an IBM &#130; &#174; WebSphere &#130; &#174; Application Server Network Deploymen
environment, the on demand configuration component is
exercised by customers deploying Web services-based
applications and customers using the WebSphere Application
Server Proxy Server. If you do not use either of these
functions, then the on demand configuration component is not
utilized and can be disabled.

To disable ODC on a server follow the following procedure.
1. Log on to WebSphere Application Server administrative
console.
2. Click Servers > Application servers.
3. Select the appropriate server. Under Server Infrastructure,
expand Java and process management > Process Definition.
4. Click Java virtual machine. Under Additional Properties,
click Custom Properties.
5. Create a new custom property by clicking New,
then code ODCInit.disabled in the name
field and true in the value field.
6. Click Apply > OK to save the configuration

The fix for this APAR is currently targeted for inclusion in
fix pack 6.1.0.33 and fix pack 7.0.0.11.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

Comments

APAR Information

APAR number
PM07711
Reported component name
WEBSPHERE APP S
Reported component ID
5724J0800
Reported release
61H
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-02-16
Closed date
2010-04-13
Last modified date
2010-04-13

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBSPHERE APP S
Fixed component ID
5724J0800

Applicable component levels

R61A PSY
UP
R61H PSY
UP
R61I PSY
UP
R61P PSY
UP
R61S PSY
UP
R61W PSY
UP
R61Z PSY
UP
R700 PSY
UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 October 2021

Tips

PM07711: Allow the initialization of the On Demand Configuration component to be bypassed.

Fixes are available

Subscribe

APAR status

Closed as new function.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R61A PSY

R61H PSY

R61I PSY

R61P PSY

R61S PSY

R61W PSY

R61Z PSY

R700 PSY

Document Information

Share your feedback

Need support?