IBM Support

JAX-RPC Handlers must be programmed to be thread-safe

Troubleshooting


Problem

If multiple services have the same handler specified in webservices.xml, they may share a single instance of the handler. JAX-RPC Handlers must be programmed to be thread-safe.

Cause

This is by design. The JAX-RPC specication states "Handler instances in a handler chain should not rely on the thread local state to share state between handler instances." This means that the implementation of the Web Services engine may create a single instance or multiple instances of the handler.

Resolving The Problem

Program your JAX-RPC handler to be thread-safe. There may be other web service implementations that create multiple handler instances, but to be safe the customer must make their handlers thread-safe.

[{"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Web Services (for example: SOAP or UDDI or WSGW or WSIF)","Platform":[{"code":"PF033","label":"Windows"}],"Version":"5.1;6.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}},{"Product":{"code":"SSNVBF","label":"Runtimes for Java Technology"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Java SDK","Platform":[{"code":"","label":""}],"Version":"","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
15 June 2018

UID

swg21215894