IT45850: SANDBOX FAILS TO BUILD WHEN DB IS MYSQL OR TABLES DROPPED IN ORACLE OR DB2.

APAR status

• Closed as program error.

Error description

• Problem Description:
  The platform_afc install fails to execute the EFrame SQL files.
  When tables are dropped prior to installation or when using
  internal MySQL, the error is in EFrame_TableChanges.sql.  An
  example of the failure is below.
  
  [saneSqlExec] Executing resource: /ais_local/share/mconners/b2b
  _6200_maint_ora12_mc1_20000/platform_core/install/repository/sc
  ripts/EFrame_TableChanges.sql
  WARNING!!! Pool maximum size exceeded 1 times in 300000(ms).
  Consider increasing MaxSize on pool: oraclePool
  /ais_local/share/mconners/b2b_6200_maint_ora12_mc1_20000/platfo
  rm_core/install/properties/entityDeployer.xml:823:The following
  /ais_local/share/mconners/b2b_6200_maint_ora12_mc1_20000/platfo
  rm_core/install/properties/entityDeployer.xml:803:java.lang.Ille
  
  	at org.apache.tools.ant.ProjectHelper.addLocationToBuildExcept
  ion(ProjectHelper.java:582)
  	at org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroIn
  stance.java:394)
  	at org.apache.tools.ant.UnknownElement.execute(UnknownElement.
  java:299)
  	at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
  
  
  	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingM
  ethodAccessorImpl.java:55)
  

Local fix

• Resolution Summary:
  The error was caused by a change to the SQL Connection handling
  in Ant 1.8.0, and became an issue in the
  CATAMOUNT_BUILD_6020000_BRANCH following the upgrade of ant from
  
  version 1.7.1 to 1.10.13.  The getConnection method that was
  previously inherited from JDBCTask was added to SQLExec and the
  new getConnection was called for each SQL command in the EFrame
  SQL files, when previous a new Connection was requested once per
  
  file.  When the EFrame SQL files contained more than 500 SQL
  commands the JDBC connection pool would be exhausted throwing
  the error above.  The fix was to only request a new Connection
  from the pool once for the first request, then use the cached
  super's connection for each subsequent request.
  
  Following the fix all DBs could be used for sandbox builds.
  

Problem summary

• Summary:
  Sandbox fails to build when DB is MySQL or tables are dropped in
  Oracle or DB2.
  
  Users Affected:
  All
  
  Problem Description:
  The platform_afc install fails to execute the EFrame SQL files.
  When tables are dropped prior to installation or when using
  internal MySQL, the error is in EFrame_TableChanges.sql. An
  example of the failure is below:
  
  [saneSqlExec] Executing resource: /install_dir/platform_core/in
  stall/repository/scripts/EFrame_TableChanges.sql
  WARNING!!! Pool maximum size exceeded 1 times in 300000(ms).
  Consider increasing MaxSize on pool: oraclePool
  /install_dir/platform_core/install/properties/entityDeployer.xm
  l:823:The following error occurred while executing this line:
  /install_dir/platform_core/install/properties/entityDeployer.xm
  l:803:java.lang.IllegalMonitorStateException
  at org.apache.tools.ant.ProjectHelper.addLocationToBuildExcepti
  on(ProjectHelper.java:582)
  at org.apache.tools.ant.taskdefs.MacroInstance.execute(MacroIns
  tance.java:394)
  at org.apache.tools.ant.UnknownElement.execute(UnknownElement.j
  ava:299)
  at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe
  thodAccessorImpl.java:55)
  
  Platforms Affected:
  All
  

Problem conclusion

• Resolution Summary:
  The error was caused by a change to the SQL connection handling
  in Ant 1.8.0 and became an issue in the
  CATAMOUNT_BUILD_6020000_BRANCH following the upgrade of Ant from
  version 1.7.1 to 1.10.13. The getConnection method that was
  previously inherited from JDBCTask was added to SQLExec, and the
  new getConnection was called for each SQL command in the EFrame
  SQL files, when previous a new Connection was requested once per
  file. When the EFrame SQL files contained more than 500 SQL
  commands, the JDBC connection pool would be exhausted, throwing
  the error above. The fix was to only request a new connection
  from the pool once for the first request, then use the cached
  super's connection for each subsequent request.
  
  Following the fix, all DBs could be used for sandbox builds.
  
  Delivered in:
  6020002
  All future Fix Packs can be found in the Release Timeline Matrix
  - https://www.ibm.com/support/pages/node/6194265
  

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:

Modules/Macros

• xxxxxxxx
  

Fix information

• Fixed component name

  STR B2B INTEGRA

• Fixed component ID

  5725D0600

Applicable component levels