docs: @Override
      public byte[] getJMSCorrelationIDAsBytes() throws JMSException {
          if (TraceComponent.isAnyTracingEnabled() && tc.isEntryEnabled())
              SibTr.entry(this, tc, "getJMSCorrelationIDAsBytes");
  
          byte[] result;
  
          try {
              result = msg.getCorrelationIdAsBytes();
          } catch (IllegalArgumentException iae) {
              // No FFDC code needed as JmsErrorUtils will perform one
  
              // d222492 review.
              // No documentation for why getCorrelationIdAsBytes might throw an IAE,
              // presumably this happens when the correlID was set as a string starting ID:
              // but followed by an illegal character sequence. If so, we probably need
              // a better message.
              // On investigation - badly formed ID: strings are trapped at set time, so
              // it should be hard to get to this code path. Default exception ok.
              // d238447 FFDC review. From the above, "hard to get" sounds like a justification for FFDC.
  
              throw (JMSException) JmsErrorUtils.newThrowable(JMSException.class,
                                                              "EXCEPTION_RECEIVED_CWSIA0115",
                                                              new Object[] { iae, "JmsMessageImpl.getCorrelationIdAsBytes" },
                                                              iae,
                                                              "JmsMessageImpl.getJMSCorrelationIDAsBytes#1",
                                                              this,
                                                              tc
                              );
  
          }
  
          if (TraceComponent.isAnyTracingEnabled() && tc.isEntryEnabled())
              SibTr.exit(this, tc, "getJMSCorrelationIDAsBytes", result);
          return result;
      }