IBM Support

PM75196: A MESSAGE THAT A JAX-RS RESOURCE DOES NOT IMPLEMENT ANY METHODS BOUND TO HTTP OPTIONS MIGHT APPEAR IN THE JVM LOG.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a JAX-RS resource is sent a request containing an HTTP
    OPTIONS method, an  informational message, "The system cannot
    find any method in the <resource_class>class that supports
    OPTIONS. Verify that a method exists" might appear numerous
    times.
    
    This message would be logged if the resource does not
    implement any subresource methods that are annotated with
    javax.ws.rs.OPTIONS.
    
    This does not signify an error, but is logged for
    informational purposes. When an HTTP request with an OPTIONS
    method is sent, even though the JAX-RS resource may not
    explicityl implement a method bound to OPTIONS, this is an
    acceptable situation.
    
    The JAX-RS specification says the following:
    
    "3.3.5 HEAD and OPTIONS
    
    HEAD and OPTIONS requests receive additional automated support.
    ...
    On receipt of an OPTIONS request an implementation MUST either:
    
    1. Call a method annotated with a request method designator
    for OPTIONS or, if none present,
    2. Generate an automatic response using themetadata provided
    by the JAX-RS annotations on the matching
    class and its methods."
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Users of IBM WebSphere Application Server   *
    *                  JAX-RS server-side applications.            *
    ****************************************************************
    * PROBLEM DESCRIPTION: Informational messages about            *
    *                      missing JAX-RS subresources             *
    *                      for HTTP OPTIONS might appear in        *
    *                      JVM logs.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When a JAX-RS resource is sent a request containing an HTTP
    OPTIONS method, an  informational message, "The system cannot
    find any method in the <resource_class>class that supports
    OPTIONS. Verify that a method exists" might appear numerous
    times.
    This message would be logged if the resource does not
    implement any subresource methods that are annotated with
    javax.ws.rs.OPTIONS.
    The message does not signify an error, but is logged for
    informational purposes. When an HTTP request with an OPTIONS
    method is sent, even though the JAX-RS resource may not
    explicity implement a method bound to OPTIONS, this is an
    acceptable situation.
    The JAX-RS specification says the following:
    "3.3.5 HEAD and OPTIONS
    HEAD and OPTIONS requests receive additional automated support.
    ...
    On receipt of an OPTIONS request an implementation MUST either:
    1. Call a method annotated with a request method designator
    for OPTIONS or, if none present,
    2. Generate an automatic response using themetadata provided
    by the JAX-RS annotations on the matching
    class and its methods."
    In other words, a JAX-RS client can send an OPTIONS request to
    a resource containing no subresources bound to OPTIONS, and
    the JAX-RS engine should be able to process the request.
    

Problem conclusion

  • The JAX-RS engine was changed to output the message under
    debug mode only--it should no longer appear in the JVM log but
    in trace.
    
    The fix for this APAR is currently targeted for inclusion in
    fix pack 8.5.0.1.  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

    PM75196

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-17

  • Closed date

    2013-08-14

  • Last modified date

    2013-08-14

  • 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

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
01 November 2021