IBM Support

JR62410: THE "ORG.APACHE.CXF.*=ALL:COM.IBM.WS.JAXWS.*=ALL" LIBERTY JAX-WS TRACE STRING DOESN'T WORK AS EXPECTED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Enabling the "org.apache.cxf.*=all:com.ibm.ws.jaxws.*=all"
    JAX-WS trace string in IBM Business Automation Workflow on
    Containers doesn't  generate web service soap message tracing
    unless the server is restarted. You might see exceptions such as
    
    [2020-05-29T05:47:56.457+0000] 00000136
    com.ibm.tx.jta.embeddable.impl.EmbeddableTimeoutManager      I
    WTRN0124I: When the timeout occurred the thread with which the
    transaction is, or was most recently, associated was
    Thread[BPM-EM-Thread-39653,5,Default Executor Thread Group]. The
    stack trace of this thread when the timeout occurred was:
         java.io.FileOutputStream.writeBytes(Native Method)
         java.io.FileOutputStream.write(FileOutputStream.java:342)
    
    com.ibm.ws.logging.internal.impl.CountingOutputStream.write(Coun
    tingOutputStream.java:47)
         java.io.PrintStream.write(PrintStream.java:504)
         sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:233)
    [2020-05-29T04:36:42.421+0000] 000000b4 id=00000000
    com.ibm.tx.jta.embeddable.impl.EmbeddableTimeoutManager      I
    WTRN0124I: When the timeout occurred the thread with which the
    transaction is, or was most recently, associated was
    Thread[Default Executor-thread-28496,5,Default Executor Thread
    Group]. The stack trace of this thread when the timeout occurred
    was:
    com.ibm.ws.logging.internal.impl.BaseTraceService.writeStreamOut
    put(BaseTraceService.java:1807)
    com.ibm.ws.logging.internal.impl.ConsoleLogHandler.synchronousWr
    ite(ConsoleLogHandler.java:166)
    com.ibm.ws.collector.manager.buffer.BufferManagerImpl.add(Buffer
    ManagerImpl.java:108)
    com.ibm.ws.logging.source.TraceSource.publish(TraceSource.java:9
    2)
    com.ibm.ws.logging.internal.impl.BaseTraceService.publishTraceLo
    gRecord(BaseTraceService.java:1178)
    com.ibm.ws.logging.internal.impl.BaseTraceService.publishLogReco
    rd(BaseTraceService.java:1128)
    com.ibm.ws.logging.internal.impl.BaseTraceService$2.publish(Base
    TraceService.java:283)
    java.util.logging.Logger.log(Logger.java:749)
    [2020-05-29T04:37:24.203+0000] 00000187 id=00000000
    com.ibm.tx.jta.embeddable.impl.EmbeddableTimeoutManager      I
    WTRN0124I: When the timeout occurred the thread with which the
    transaction is, or was most recently, associated was
    Thread[Default Executor-thread-28504,5,Default Executor Thread
    Group]. The stack trace of this thread when the timeout occurred
    was:
    com.ibm.ws.logging.collector.CollectorJsonHelpers.addToJSON(Coll
    ectorJsonHelpers.java:111)
    com.ibm.ws.logging.collector.CollectorJsonHelpers.addUnchangingF
    ieldsJSON_Trace(CollectorJsonHelpers.java:266)
    com.ibm.ws.logging.collector.CollectorJsonHelpers.startTraceJson
    Fields(CollectorJsonHelpers.java:609)
    com.ibm.ws.logging.collector.CollectorJsonUtils_JSON.jsonifyTrac
    eAndMessage(CollectorJsonUtils_JSON.java:282)
    com.ibm.ws.logging.collector.CollectorJsonUtils_JSON.jsonifyEven
    t(CollectorJsonUtils_JSON.java:71)
    com.ibm.ws.logging.collector.CollectorJsonUtils.jsonifyEvent(Col
    lectorJsonUtils.java:59)
    com.ibm.ws.logging.internal.impl.JsonLogHandler.formatEvent(Json
    LogHandler.java:162)
    com.ibm.ws.logging.internal.impl.ConsoleLogHandler.synchronousWr
    ite(ConsoleLogHandler.java:106)
    com.ibm.ws.collector.manager.buffer.BufferManagerImpl.add(Buffer
    ManagerImpl.java:108)
    com.ibm.ws.logging.source.TraceSource.publish(TraceSource.java:9
    2)
    com.ibm.ws.logging.internal.impl.BaseTraceService.publishTraceLo
    gRecord(BaseTraceService.java:1178)
    com.ibm.ws.logging.internal.impl.BaseTraceService.publishLogReco
    rd(BaseTraceService.java:1128)
    com.ibm.ws.logging.internal.impl.BaseTraceService$2.publish(Base
    TraceService.java:283)
    java.util.logging.Logger.log(Logger.java:749)
    
    PRODUCTS AFFECTED
    IBM Business Automation Workflow on Containers
    

Local fix

Problem summary

  • Liberty generates numerous unnecessary traces when enabling the
    "org.apache.cxf.*=all:com.ibm.ws.jaxws.*=all" JAX-WS trace and
    sometimes the function breaks on Business Automation Workflow on
     Containers. Also, you must restart the server so that web
    service soap messages are in the trace.
    

Problem conclusion

  • A fix is available or will be available that ensures the
    "org.apache.cxf.*=all:com.ibm.ws.jaxws.*=all" JAX-WS trace
    string works as expected.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR62410

  • Reported component name

    CLOUD PAK FOR A

  • Reported component ID

    5737I2300

  • Reported release

    K00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-06-25

  • Closed date

    2020-07-10

  • Last modified date

    2025-07-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

    BUS AUTO WORKFL

  • Fixed component ID

    5737H4100

Applicable component levels

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS8JB4","label":"IBM Business Automation Workflow"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"20.0.0.1","Line of Business":{"code":"LOB76","label":"Data Platform"}}]

Document Information

Modified date:
14 July 2025