IV27868: EWAS CRASH WHEN THE DEFAULT STACK FOR EWAS IS NOT SUFFICINET

APAR status

• Closed as fixed if next.

Error description

• The problem was reproduced during the 8.6.0 GA, and the
  workaround was well provided in the release notes, increase the
  native stack for native thread flag  -Xmso<size>.
  
  Release notes of TWS 8.6:
  AWSUI0796E The specified action cannot be performed.
  
  Reason: AWSJCS011E An internal error has occurred. The error is
  the
  following:
  "javax.naming.ServiceUnavailableException: A communication
  failure
  occurred while attempting to obtain an initial context with the
  provider
  URL: "corbaloc:iiop:nc123456.it.ibm.com:31117". Make sure that
  any
  bootstrap address information in the URL is correct and that the
  target
  name server is running. A bootstrap address with no port
  specification
  defaults to port 2809. Possible causes other than an incorrect
  bootstrap
  address or unavailable name server include the network
  environment and
  workstation network configuration. [Root exception is
  org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection
  refused:host=nc123456.it.ibm.com,port=31117 vmcid: IBM minor
  code: E02
  completed: No]".
  Workaround: Specify the value -Xmso512k for the
  attribute genericJvmArguments in the
  file/opt/ibm/TWA/eWAS/profiles/TIPProfile/config/cells/TIPCell/n
  odes/TIP
  Node/
  servers/server1/server.xml,
  to obtain the following property:
  
  jvmEntries xmi:id="JavaVirtualMachine_1311759672130"
  verboseModeClass="false" verboseModeGarbageCollection="false"
  verboseModeJNI="false" initialHeapSize="256"
  maximumHeapSize="1024"
  runHProf="false" hprofArguments="" debugMode="false"
  debugArgs="-Djava.compiler=NONE -Xdebug -Xnoagent
  -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=7777"
  genericJvmArguments="-Xmso512k" disableJIT="false" (40567)
  
  This document can be found in the TDWV 8.6 reelase notes, here :
  http://www-01.ibm.com/support/docview.wss?uid=swg27020873
  

Local fix

• AWSUI0796E The specified action cannot be performed.
  
  Reason: AWSJCS011E An internal error has occurred. The error is
  the
  following:
  "javax.naming.ServiceUnavailableException: A communication
  failure
  occurred while attempting to obtain an initial context with the
  provider
  URL: "corbaloc:iiop:nc123456.it.ibm.com:31117". Make sure that
  any
  bootstrap address information in the URL is correct and that the
  target
  name server is running. A bootstrap address with no port
  specification
  defaults to port 2809. Possible causes other than an incorrect
  bootstrap
  address or unavailable name server include the network
  environment and
  workstation network configuration. [Root exception is
  org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection
  refused:host=nc123456.it.ibm.com,port=31117 vmcid: IBM minor
  code: E02
  completed: No]".
  Workaround: Specify the value -Xmso512k for the
  attribute genericJvmArguments in the
  file/opt/ibm/TWA/eWAS/profiles/TIPProfile/config/cells/TIPCell/n
  odes/TIP
  Node/
  servers/server1/server.xml,
  to obtain the following property:
  
  jvmEntries xmi:id="JavaVirtualMachine_1311759672130"
  verboseModeClass="false" verboseModeGarbageCollection="false"
  verboseModeJNI="false" initialHeapSize="256"
  maximumHeapSize="1024"
  runHProf="false" hprofArguments="" debugMode="false"
  debugArgs="-Djava.compiler=NONE -Xdebug -Xnoagent
  -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=7777"
  genericJvmArguments="-Xmso512k" disableJIT="false" (40567)
  
  This document can be found in the TDWV 8.6 reelase notes, here :
  http://www-01.ibm.com/support/docview.wss?uid=swg27020873
  

Problem summary

• see apar description
  

Problem conclusion

Temporary fix

Comments

APAR Information

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

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

Fix information

Applicable component levels

• R860 PSY

     UP