IJ35725: MAXIMO BIRT REPORT SOMETIMES DOES NOT RUN AS THERE IS NO RESPONSE FROM THE DATABASE CONNECTION

APAR status

• Closed as program error.

Error description

• PROBLEM DESCRIPTION
  Birt report sometimes do not execute. It is intermittent. This
  is because the database connection does not respond.
  
  Therefore the reportusage still shows the report entries that
  are yet to receive a respinse from the database connection.
  
  
  REPRODUCTION STEPS
  Log into Maximo
  Go to Work order tracking, select run ALL work orders for today
  This is a Birt report
  Then nothing happens
  
  RESULTS
  The report does not complete
  
  STACK TRACE
  ####<Jul 8, 2021 4:04:01,858 PM CEST> <Error> <WebLogicServer>
  <server001.ibm.com> <MaxServer01> <[ACTIVE] ExecuteThread: '3'
  for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS
  Kernel>> <> <3d56e6c4-2701-4567-a948-e71ebc76be1b-0000017e>
  <1625746681858> <[severity-value: 8] [rid: 0] [partition-id: 0]
  [partition-name: DOMAIN] > <BEA-000337> <[STUCK] ExecuteThread:
  '23' for queue: 'weblogic.kernel.Default (self-tuning)' has been
  busy for "659" seconds working on the request "Http Request
  Information:
  weblogic.servlet.internal.ServletRequestImpl@3fbc24a3[POST
  /maximo/bridge/frameset]
  ", which is more than the configured time (StuckThreadMaxTime)
  of "600" seconds in "server-failure-trigger". Stack trace:
  	sun.nio.ch.FileDispatcherImpl.read0(Native Method)
  	sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39)
  	sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223)
  	sun.nio.ch.IOUtil.read(IOUtil.java:197)
  	sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380)
  	oracle.net.nt.TimeoutSocketChannel.read(TimeoutSocketChannel.j
  ava:144)
  
  REPORTED IN VERSION
  Maximo Asset Management 7.6.1.1
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * MAXIMO                                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Once in a while when BIRT report database connection is not  *
  * used for a long time, it doesn't respond and the thread gets *
  * stuck for a long time.                                       *
  ****************************************************************
  

Problem conclusion

• _The fix for this APAR is contained in the following maintenance
  package: release\fix pack for Release 7.6.1.3 Product_
  

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

  MAXIMO REPORTIN

• Fixed component ID

  TIVOREPTS

Applicable component levels