JR57387: YOU MIGHT SEE THE TOOLSMODEL EXCEPTION WHEN IBM PROCESS CENTER INDEXING IS ENABLED ON IBM PROCESS SERVER

bpm.8570.cf2017.03.delta.repository
Downloading IBM Business Process Manager V8.5.7 Cumulative Fix 2017.03

APAR status

• Closed as program error.

Error description

• When IBM Process Server is set as the development server
  (<environment-type>Development</environment-type>), Process
  Center indexing is enabled and you might see the following
  exception in the SystemOut.log file:
  
  com.ibm.bpmsdk.model.exception.ToolsModelException:
  javax.naming.ConfigurationException: A JNDI operation on a
  "java:" name cannot be completed because the server runtime is
  not able to associate the operation's thread with any J2EE
  application component.  This condition can occur when the JNDI
  client using the "java:" name is not executed on the thread of a
  server application request.  Make sure that a J2EE application
  does not execute JNDI operations on "java:" names within static
  code blocks or in threads created by that J2EE application.
  Such code does not necessarily run on the thread of a server
  application request and therefore is not supported by JNDI
  operations on "java:" names. [Root exception is
  javax.naming.NameNotFoundException: Name "comp/UserTransaction"
  not found in context "java:".]
  at
  com.ibm.bpmsdk.model.exception.ToolsModelException.asToolsModelE
  xception(ToolsModelException.java:47)
  at
  com.ibm.bpmsdk.model.transaction.TransactionManager.begin(Transa
  ctionManager.java:114)
  at
  com.ibm.bpmsdk.model.transaction.TransactionManager.begin(Transa
  ctionManager.java:39)
  at
  com.ibm.bpmsdk.model.autosave.dao.AutoSaveDAO.createAutoSaveStat
  usInTransaction(AutoSaveDAO.java:2193)
  at
  com.ibm.bpmsdk.tools.repo.client.RepositoryAccessHelper.findPOBy
  PrimaryKey(RepositoryAccessHelper.java:1096)
  at
  com.ibm.bpmsdk.tools.repo.client.RepositoryAccessHelper.findByPr
  imaryKey(RepositoryAccessHelper.java:1002)
  at
  com.ibm.bpmsdk.tools.repo.client.RepositoryAccessHelper.findArti
  factQuietlyByPrimaryKey(RepositoryAccessHelper.java:800)
  at
  com.ibm.bpmsdk.model.repository.facade.RepositoryAccessFactory.f
  indArtifactQuitelyByPrimaryKey(RepositoryAccessFactory.java:163)
  at
  com.ibm.bpm.search.artifact.repo.impl.dao.RepositoryArtifactRead
  erConfigDAO.generateJsonData(RepositoryArtifactReaderConfigDAO.j
  ava:698)
  at
  com.ibm.bpm.search.artifact.repo.impl.dao.RepositoryArtifactRead
  erConfigDAO.getVersionedArtifactSummaryRecords(RepositoryArtifac
  tReaderConfigDAO.java:263)
  
  PRODUCTS AFFECTED
  IBM Business Process Manager (BPM) Advanced
  IBM BPM Standard
  IBM BPM Express
  

Local fix

• When the fix is not applied, you can resolve this issue by
  setting <artifact-index-enabled>false</artifact-index-enabled>
  in the 100Custom.xml file.
  

Problem summary

• When Process Server is set as the development server, artifact
  indexing is enabled although it should not be enabled on Process
   Server.
  

Problem conclusion

• A fix that disables artifact indexing on Process Server for all
  server types is planned for inclusion in IBM BPM V8.5.7
  cumulative fix 2017.03.
  

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

  BPM STANDARD

• Fixed component ID

  5725C9500

Applicable component levels

• R857 PSY

     UP