IT46842: TERMINATING DEBUGGER IN ACE MIGHT CAUSE THE TOOLKIT TO HANG AND RESULTS IN ILLEGALSTATEEXCEPTION IN THE METADATA LOGS.

APAR status

• Closed as program error.

Error description

• In ACE, terminating the debugger either during or after a
  debugging session might cause the toolkit to freeze and results
  in an IllegalStateException appearing in the metadata logs, as
  shown below:
  
  java.lang.IllegalStateException: Call stack for thread main
  at java.base/java.lang.Object.waitImpl(Native Method)
  at java.base/java.lang.Object.wait(Object.java:251)
  at java.base/java.lang.Object.wait(Object.java:219)
  at
  org.eclipse.core.internal.jobs.Semaphore.acquire(Semaphore.java:
  45)
  at
  org.eclipse.core.internal.jobs.OrderedLock.doAcquire(OrderedLock
  .java:173)
  at
  org.eclipse.core.internal.jobs.OrderedLock.acquire(OrderedLock.j
  ava:109)
  at
  org.eclipse.core.internal.jobs.OrderedLock.acquire(OrderedLock.j
  ava:85)
  at
  org.eclipse.core.internal.resources.WorkManager.checkIn(WorkMana
  ger.java:125)
  at
  org.eclipse.core.internal.resources.Workspace.prepareOperation(W
  orkspace.java:2265)
  at
  org.eclipse.core.internal.resources.Workspace.run(Workspace.java
  :2310)
  at
  org.eclipse.core.internal.resources.Workspace.run(Workspace.java
  :2340)
  at
  org.eclipse.debug.core.model.Breakpoint.setAttribute(Breakpoint.
  java:231)
  at
  com.ibm.etools.mft.debug.flow.breakpoints.AbstractFlowBreakpoint
  .decrementInstallCount(AbstractFlowBreakpoint.java:177)
  at
  com.ibm.etools.mft.debug.flow.FlowDebugHelperDelegate.breakpoint
  Removed(FlowDebugHelperDelegate.java:197)
  at
  com.ibm.etools.mft.debug.internal.model.MBBreakpointManager.brea
  kpointRemoved(MBBreakpointManager.java:103)
  at
  com.ibm.etools.mft.debug.internal.model.MBDebugTarget.breakpoint
  Removed(MBDebugTarget.java:146)
  at
  com.ibm.etools.mft.debug.internal.model.MBDebugTarget.cleanUp(MB
  DebugTarget.java:190)
  at
  com.ibm.etools.mft.debug.internal.model.MBDebugTarget.disconnect
  (MBDebugTarget.java:223)
  at
  com.ibm.etools.mft.debug.common.cda.core.CDADebugTarget.disconne
  ct(CDADebugTarget.java:956)
  at
  com.ibm.debug.wsa.internal.core.WSAJavaDebugTarget.disconnect(WS
  AJavaDebugTarget.java:1576)
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All Users of App Connect Enterprise V12 and V13 trying to
  perform debugging in the toolkit.
  
  
  Platforms affected:
  Linux on x86-64 platform, Windows on x86-64 platform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  In App Connect Enterprise, terminating the debugger either
  during or after a debugging session might cause the toolkit to
  freeze and cause an IllegalStateException appearing in the
  metadata logs, as shown below:
  
  java.lang.IllegalStateException: Call stack for thread main
  at java.base/java.lang.Object.waitImpl(Native Method)
  at java.base/java.lang.Object.wait(Object.java:251)
  at java.base/java.lang.Object.wait(Object.java:219)
  at
  org.eclipse.core.internal.jobs.Semaphore.acquire(Semaphore.java:
  45)
  at
  org.eclipse.core.internal.jobs.OrderedLock.doAcquire(OrderedLock
  .java:173)
  at
  org.eclipse.core.internal.jobs.OrderedLock.acquire(OrderedLock.j
  ava:109)
  at
  org.eclipse.core.internal.jobs.OrderedLock.acquire(OrderedLock.j
  ava:85)
  at
  org.eclipse.core.internal.resources.WorkManager.checkIn(WorkMana
  ger.java:125)
  at
  org.eclipse.core.internal.resources.Workspace.prepareOperation(W
  orkspace.java:2265)
  at
  org.eclipse.core.internal.resources.Workspace.run(Workspace.java
  :2310)
  at
  org.eclipse.core.internal.resources.Workspace.run(Workspace.java
  :2340)
  at
  org.eclipse.debug.core.model.Breakpoint.setAttribute(Breakpoint.
  java:231)
  at
  com.ibm.etools.mft.debug.flow.breakpoints.AbstractFlowBreakpoint
  .decrementInstallCount(AbstractFlowBreakpoint.java:177)
  at
  com.ibm.etools.mft.debug.flow.FlowDebugHelperDelegate.breakpoint
  Removed(FlowDebugHelperDelegate.java:197)
  at
  com.ibm.etools.mft.debug.internal.model.MBBreakpointManager.brea
  kpointRemoved(MBBreakpointManager.java:103)
  at
  com.ibm.etools.mft.debug.internal.model.MBDebugTarget.breakpoint
  Removed(MBDebugTarget.java:146)
  at
  com.ibm.etools.mft.debug.internal.model.MBDebugTarget.cleanUp(MB
  DebugTarget.java:190)
  at
  com.ibm.etools.mft.debug.internal.model.MBDebugTarget.disconnect
  (MBDebugTarget.java:223)
  at
  com.ibm.etools.mft.debug.common.cda.core.CDADebugTarget.disconne
  ct(CDADebugTarget.java:956)
  at
  com.ibm.debug.wsa.internal.core.WSAJavaDebugTarget.disconnect(WS
  AJavaDebugTarget.java:1576)
  

Problem conclusion

• The product has been updated to ensure that the toolkit operates
  without any exceptions when terminating the debugger, whether
  during or after a debugging session.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v10.1      10.1.0.5
  v12.0      12.0.12.8
  
  The latest available maintenance can be obtained from:
  http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
  
  If the maintenance level is not yet available,information on
  its planned availability can be found on:
  http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
  ---------------------------------------------------------------
  

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

• Fixed component name

  APP CONN ENT TL

• Fixed component ID

  5724J0561

Applicable component levels