Readme file for: IBM® FileNet® P8 Process Engine
Update name: 5.0.0.10
Fix ID: 5.0.0.10-P8PE-FP010
Publication date: 11 August 2017
Last modified date: 11 August 2017
This document provides information about the IBM FileNet P8 Process Engine 5.0.0.10-P8PE-FP010 fix pack.
Click the following link to access the files for this fix pack update: Fix Central for Fix Pack 5.0.0.10-P8PE-FP010.
The following components must be installed before installing this fix pack:
For more information about Process Engine new features and known issues, see the IBM FileNet P8 Release Notes.
None
For additional FileNet P8 compatibility information, see the following documents:
Jar Certificate Expiration Dates (for Applets)
| Release | Release Date | Java Jar Certs Expire |
|---|---|---|
| 5.0.0.1-P8PE-FP001 | 2011-09-16 | 2012-03-16 |
| 5.0.0.2-P8PE-FP002 | 2011-11-21 | 2012-03-16 |
| 5.0.0.3-P8PE-FP003 | 2012-06-12 | 2015-02-19 |
| 5.0.0.4-P8PE-FP004 | 2012-09-04 | 2015-02-19 |
| 5.0.0.5-P8PE-FP005 | 2013-08-15 | 2016-06-10 |
| 5.0.0.5-P8PE-IF001 | 2014-01-13 | 2016-06-10 (Manifest Permissions and SHA-256) |
| 5.0.0.6-P8PE-FP006 | 2014-03-07 | 2016-06-10 (Manifest Permissions and SHA-256) |
| 5.0.0.7-P8PE-FP007 | 2014-10-10 | 2017-06-08 (Manifest Permissions and SHA-256) |
| 5.0.0.8-P8PE-FP008 | 2015-01-30 | 2017-06-08 (Manifest Permissions and SHA-256) |
| 5.0.0.9-P8PE-FP009 | 2015-07-31 | 2018-05-19 (Manifest Permissions and SHA-256) |
| 5.0.0.10-P8PE-FP0010 | 2017-07-28 | 2020-06-28 (Manifest Permissions and SHA-256) |
Introduced in Process Engine fix pack: 5.0.0.9-P8PE-FP009
Introduced in Process Engine fix pack: 5.0.0.8-P8PE-FP008
Introduced in Process Engine fix pack: 5.0.0.7-P8PE-FP007
Introduced in Process Engine fix pack: 5.0.0.6-P8PE-FP006
Introduced in Process Engine fix pack: 5.0.0.5-P8PE-FP005
Introduced in Process Engine fix pack: 5.0.0.4-P8PE-FP004
Introduced in Process Engine fix pack: 5.0.0.3-P8PE-FP003
Introduced in Process Engine fix pack: 5.0.0.2-P8PE-FP002
Introduced in Process Engine fix pack: 5.0.0.1-P8PE-FP001
Before installing this fix pack, verify you have an installed copy of the latest IBM FileNet P8 Platform Documentation package. This documentation package contains additional information that you might need to complete the procedures mentioned in this readme, such as stopping services and applications.
Search is enabled in the help system only if you have installed it as a web site on a web server that supports Java applications.
Before installing this fix pack, create a full backup of Process Engine using your normal backup procedures.
Before installing this fix pack, you must stop all running software, including software on other servers that might be communicating with Process Engine or the Process Engine database.
For procedures and further details, see the IBM FileNet P8 help topic Administering IBM FileNet P8 > Starting and stopping IBM FileNet P8 Components.
ps -ef | grep java
Install the fix pack on the Process Engine as follows:
Install the 5.0.0.10-P8PE-FP010 fix pack server files interactively or silently as follows:
Run the Process Engine client installer that is shipped with this fix pack to synchronize the version of Process Engine files on all other servers where Process Engine client software is installed. Do not update Process Engine client files to this fix pack level if you have not already updated Process Engine server.
You must run the installer once on each of the other servers. Complete one or more of the following procedures, depending on which applications run in your environment.
In some cases, multiple applications will reside on the same server. An example of this would be if Records Manager were collocated with Application Engine. To update multiple applications at the same time, select all collocated applications on the Select Products screen.
To install the Process Engine client files, complete the following steps on all Content Engine servers. Except where noted, the steps apply to WebSphere, WebLogic, and JBoss.
| Operating system | Cache directories to delete |
|---|---|
| UNIX | /opt/bea/user_projects/domains/mydomain/servers/AdminServer/tmp/_WL_user/Engine-wl
/opt/bea/user_projects/domains/mydomain/servers/AdminServer/cache/EJBCompilerCache |
| Windows | C:\bea\user_projects\domains\mydomain\servers\AdminServer\tmp\_WL_user\Engine-wl
C:\bea\user_projects\domains\mydomain\servers\AdminServer\cache\EJBCompilerCache |
| In this screen... | Perform this action... |
|---|---|
| Products to Update | Select Content Engine |
| Stop Running Software | If prompted, stop all running software components |
| Installation Summary | Validate that the information displayed is correct and that there is enough space to complete the installation. |
| Software Components | Select the software components to automatically start after the installation is complete. |
To install the Process Engine client files, complete the following steps on all servers that apply, including application servers where IBM InfoSphere Enterprise Records (Records Manager) applications (such as the Sweep and File Plan Import and Export tools), are installed. Except where noted, the steps apply to WebSphere, WebLogic, and JBoss.
The backup of these files is to ensure that the files are still available in case there is any reason to revert to the previous versions. When redeploying after installing the fix pack, any custom settings will be added back to the deployed working directory.
| In this screen... | Perform this action... |
|---|---|
| Products to Update | Select the appropriate software to update. For example: Application Engine, WPXT, or Infosphere Enterprise Records/Records Manager. |
| Stop Running Software | If prompted, stop all running software components. |
| Installation Summary | Verify that the information displayed is correct and that there is enough disk space to complete the installation. |
| Software Components | Select the software components to automatically start after the installation is complete. |
For IBM Case Manager 5.0 installations
In the Development Domain
In the Production Domain
After the installation
Be sure to clear the Java Runtime Environment (JRE) and browser caches on all client machines.
For IBM Case Manager 5.1 installations
In the Development Domain
In the Production Domain
After the installation
Be sure to clear the Java Runtime Environment (JRE) and browser caches on all client machines.
After the installation:
After the installation:
By selecting the 'Other' option in the Process Engine client installer Select Products screen you can specify where to copy all of the new Process Engine client files. You can then manually update the appropriate files in any installed and deployed locations for other servers where Process Engine client software is installed. You can use this option if the Process Engine client installer does not recognize that a supported product is installed.
Use the following steps to update other servers where Process Engine client software is installed, including Business Process Framework and any custom applications:
| In this screen... | Perform this action... |
|---|---|
| Products to Update | Select Other. |
| Installation Directory | Specify the directory to which the Process Engine client files will be copied. |
| Stop Running Software | If prompted, stop all running software components. |
| Installation Summary | Validate that the information displayed is correct and that there is enough space to complete the installation. |
| Software Components | Select the software components to automatically start after the installation is complete. |
Important Replace files inside any EAR and WAR files that are used by the applications.
This fix pack does not have an uninstall option. To return to an earlier version, restore the files from your backup.
The following tables list the product fixes in this Process Engine server fix pack update.
APAR |
Type |
Description |
|---|---|---|
PJ42964 |
Fix |
Remove unnecessary web.xml file from pe.jar. |
PJ43411 |
Fix |
PSIRT 2048: Update the pe3pt.jar library to include the fix for Open Source Apache Axis and Apache Axis2 X.509 spoofing issue.
See Security Bulletin 1965451 |
PJ43472 |
Fix |
WaitForCondition Assignments may not work correctly after upgrade PE from 3.5 to 5.0.0.x |
PJ43565 |
Fix |
PSIRT 3528: July 2015 Quarterly Java Update - Updates the IBM private JRE of the Process Engine server in response to a Java PSIRT security issue (July 2015 Quarterly JRE Update - CVE-2015-2613, CVE-2015-2601, CVE-2015-2625, and CVE-2015-1931). See Security Bulletin 1967351 |
PJ43582 |
Fix |
CEOperations.getContent() uses the default system encoding (java file.encoding) to convert bytes from the
document into java String object(s). If the default system encoding does not match the encoding of the document whose
contents are being retrieved, the returned String may be corrupted. |
PJ43635 |
Fix |
When a step deadline expires and a defined response is missing, the vwtime daemon is unable to process the work item out of delay queue due to an Exception.
The pesvr_system.log is flooded with a message similar to this: 2015/09/30 06:03:02.548+0200 9392:vwtime Reg#1 [Error] FNRPE2131090212E VwTimeDaemon: Error processing work object number "F476E17EA1C7BE449CDEFEF00DC8AD43".; Exception: Invalid or null response |
PJ43657 |
Fix |
On AIX installs, the fix pack installer left the security of the .../ProcessEngine/java folder as 700 rather
than 755. This meant that if the process engine software was started by a user other than the user who
installed the fix pack, the PE software could start properly because it could not see its JRE. |
PJ43698 |
Fix |
PSIRT 4021: October 2015 Quarterly Java Update - Updates the IBM private JRE of the Process Engine server in response to a Java PSIRT security issue (October 2015 Quarterly JRE Update - CVE-2015-4872, CVE-2015-5006). See Security Bulletin 1969428 |
PJ43868 |
Fix |
The peverify tool sometimes incorrectly reports this error: 'INVALID SEQUENCE/IDENTITY VALUE (0) DOES NOT MATCH WITH
THE TABLE IDENTITY COLUMN "F_UNIQUEID" ' |
PJ43914 |
Fix |
PSIRT 4590: SLOTH - TLS Man-in-the-middle exploit - the IBM private JRE of the Process Engine server in response to a Java PSIRT security issue (January 2016 Quarterly JRE Update - CVE-2015-7575). See Security Bulletin 1975823 |
PJ43920 |
Fix |
PSIRT 4587: January 2016 Quarterly Java Update - Updates the IBM private JRE of the Process Engine server in response to a Java PSIRT security issue (January 2016 Quarterly JRE Update - CVE-2015-7575, CVE-2016-0475, and CVE-2016-0466). See Security Bulletin 1975820 |
PJ43989 |
Fix |
An extraneous "services" folder in the peResources.jar file's META-INF folder can cause the following error:
<BEA-160001> Error deploying Internal Application:
weblogic.application.ModuleException:ModuleException: [HTTP:101216]Servlet: "CoordinatorPortTypeServlethttp" failed to preload on startup in Web application: "wls-wsat.war".
java.lang.NoClassDefFoundError: com.sun.xml.bind.DatatypeConverterImpl. |
PJ44035 |
Fix |
After upgrading from PE 4.x to PE 5.0, expressions containing a call to the xmltransform function may result
in a NullPointerException. This then sends the workitem to the Malfunction map. |
PJ44119 |
Fix |
Automatic updating of a group's "group membership" information was not automatically restored in the case of an API call that should have reinstated refreshing for the case where a group's timestamp was set to the year 9999 because CE was inadvertently down. |
PJ44134 |
Fix |
PSIRT 4782: InstallAnywhere DLL-planting issue (CVE-2016-4560) - Updates the Install Anywhere used to create the PE installers in response to the InstallAnywhere issue. See Security Bulletin 1980209 |
PJ44142 |
Fix |
PSIRT 5254: April 2016 Quarterly JRE update - Update the IBM private JRE of the Process Engine server in response to a Java PSIRT security issue (April 2016 Quarterly JRE Update). |
PJ44265 |
Fix |
When a workflow with a participant step designed with the option to 'disable reassignment' is launched
but the participant has subsequently been deleted from LDAP, no one is allowed to reassign the work.
Members of the SysAdminG group should be able to reassign this task to another person. |
PJ44286 |
Fix |
Duplicate security entries on the region configuration are being created every time an ICM solution is deployed. |
PJ44311 |
Fix |
Workflow is caching the WSDL end point as NULL and causing every request from the workflow
to an external web service to fail with the null pointer exception. |
PJ44342 |
Fix |
Calling the PE "substr" function with a negative "length" parameter causes a Java.lang.STRINGINDEXOUTOFBOUNDSEXCEPTION. |
PJ44410 |
Fix |
peverify fails to checkRegionDBTables due to java.lang.NullPointerException |
PJ44487 |
Fix |
PSIRT 6974: October 2016 Quarterly Java Update - Updates the IBM private JRE of the Process Engine server in response to a Java PSIRT security issue (October 2016 Quarterly JRE Update - CVE-2016-5573, CVE-2016-5597). See Security Bulletin 1993863 |
PJ44626 |
Fix |
PSIRT 7741: January 2017 Quarterly JRE update - Update the IBM private JRE of the Process Engine server in response to a Java PSIRT security issue (January 2017 Quarterly JRE Update - CVE-2016-5548, CVE-2016-5549, CVE-2016-5547, CVE-2016-5552, CVE-2016-2183). See Security Bulletin 1998551 |
PJ44636 |
Fix |
PE 5.0 Component Manager should automatically refresh stale server session instead of terminate. |
APAR |
Type |
Description |
|---|---|---|
PJ43368 |
Fix |
The additional system keys created index will not be seen at the intermediate state before the commit on the server. The effect of the issue is that the extra system keys seen until the commit of the system configuration were the F_TimeStamp and F_SeqNumber will be added as keys on the event log on transfer. |
PJ43369 |
Fix |
vwlog -Z command does not delete events from event log when -e is specified and PA disabled. |
PJ42842 |
Fix |
An "assertion failure" occurs while commiting changes thru Process Configuration Console or while transferring a workflow definition. Assertion Failed in file "ServerTransfer.java", method "renameViewFields", line 3,067. |
PJ42951 |
Fix |
Web Service failing with an "HTTP/1.1 500 Internal Server Error" error. |
PJ43002 |
Fix |
PSIRT 2696: IBM SDK, Java Technology Edition Critical Patch Update - January 2015 - Update the IBM private JRE of the Process Engine (both client and server) to version JRE 1.8.0 (pwi3280-20150129_02)(J9) in response to a Java PSIRT security issue. See Security Bulletin 1697152 |
PJ43338 |
Fix |
orb_rpc_createLiveWorkObject returns FNRPE2130660006E Invalid Work Object number when Creation and Termination events are disabled. |
PJ43015 |
Fix |
Problem with validating WSDL at run time, get error 'Errors: 0 : [Unrecoverable Error] null: line -1, column -1, Premature end of file' |
PJ43445 |
Fix |
Default for Process Task Manager Advanced tab CacheUseExpiredIfNecessary option is now true |
PJ43071 |
Fix |
function "substitute (text, search text, replacement text)" in an expression, if second parameter |
PJ43075 |
Fix |
PSIRT 2913 - Updated Java JRE - FREAK (CVE-2015-0138). See Security Bulletin 1699589 |
PJ43171 |
Fix |
PSIRT 3058 - Updated Java JRE - Bar Mitzvah SSL/TLS - CVE-2015-2808 - Vulnerability in RC4 stream cipher. See Security Bulletin 1701597 |
PJ43386 |
Fix |
Update commons-fileupload.jar to version 1.3.1 |
PJ43195 |
Fix |
PSIRT 3141 - Updated Java JRE - IBM SDK, Java Technology Edition Critical Patch Update - April 2015. See Security Bulletin 1883959 |
PJ43339 |
Fix |
Failed to transfer to region 1. Exception =[FNRPE2131090078E]Transfer failed due to errors in input data. |
PJ43270 |
Fix |
vwusersync stops updating a group's "group members" information and sets the group's environment record DB Time stamp to 12/01/9999 00:00:00 if it can't communicate with the CE |
PJ43345 |
Fix |
PSIRT 3328 - Updated Java JRE - Logjam (CVE-2014-4244, CVE-2014-4263, CVE-2014-3068). See Security Bulletin 1960191 |
PJ43362 |
Fix |
vwtool's hardcopy command doesn't echo the command itself or the timestamp when the command was executed into the hardcopy output text file. |
APAR |
Type |
Description |
|---|---|---|
PJ42830 |
Fix |
vwtool's "environment view persistent" command no longer calls into the CE to get updated data for and environment record
if the environment record is expired. It simply displays whatever is in the PE's persistent environment record
(in the PE's database). |
PJ42829 |
Fix |
When the vwusersync daemon finds that an environment record references a user or group that no longer exists in the LDAP server, it will now set the timestamp on that user's or group's environment record to a date far in the future so that the vwusersync daemon will ignore it for future "refresh" attempts. This avoids unnecessary overhead on the CE and LDAP servers. This allows the vwusersync daemon to spend its time refreshing the users and groups that are currently in LDAP. And it allows a site to keep old environment records around without significant overhead in case they're being referenced by other in-flight workflows. If a user or group that was deleted is subsequently re-added to LDAP and becomes visible again, the administrator can run vwtool and do an env cache name to cause the PE to reinstate the automatic vwusersync refreshing of that particular user or group. Or a vwtool env i f m y command can be used to check then environment records of all users and groups and if the associated users or groups are found in LDAP, vwtool will reinstate the automatic vwusersync refreshing for them.
|
PJ42828 |
Fix |
When information in LDAP is changed, the Process Engine's vwusersync daemon generally automatically refreshes the Process Engine's environment cache so that within a few hours, the new information (such as group membership changes) is being used. vwtool has an env cache name command to allow an administrator to manually bring that updated information into the PE's usage essentially immediately. But previously, that command only updated the information in the PE's database and did not force the PE's memory (runtime) data to be updated. For example, if a user is added or removed from a group in LDAP and we want to get that change immediately "in use" in the Process Engine's runtime environment, vwtool's env cache name command could be used. This would cause the PE's cache information in the PE's database to be updated immediately. But previously, the command did NOT update that information in the PE's memory cache, so the LDAP updates weren't actually used by the Process Engine until the memory cache expired (generally sometime over the next few hours). Now, the env cache name command also triggers an update of the Process Engine's memory cache as well, so the new information (e.g., updated group membership information) will be used immediately by the Process Engine. Note: PE gets its LDAP information using calls into the Content Engine. CE might cache this LDAP data and so the PE MAY not be able to see very recent LDAP changes (e.g., on the order of 20 or 30 minutes old). To check if CE sees newly updated LDAP data, run vwtool and use the sectool command to expand a group, or look at information for a user or group. Once vwtool's sectool output shows that the updated LDAP information is visible in the CE, vwtool's env cache name command can bring that information into the PE's runtime environment. |
PJ42827 |
Fix |
Deleting user environment records in PE 5.0 is sometimes required for normal maintenance of the PE's VWUser table. The only way to do this in the earlier PE 5.0 releases is to use vwtool's env i f m y command to force vwtool to check each user and group. If vwtool finds that user or group is no longer visible in LDAP, vwtool allows the user or group to be deleted. If there are 10,000 users and groups, forcing vwtool to check all of them to clean up (find and delete) a single user or group is tedious, time consuming, and wasteful in the case where you know which group or user you want to delete. Now, if a user or group environment record needs to be deleted, it can be done with this vwtool command: env -> remove -> persistent -> name This feature is also available in CPE 5.2.1, CPE 5.2.0.4, and any newer releases. |
Fix |
Environment Cache Improvement Option A new Process Engine "advanced tab" option has been added to PE 5.0.0.8. CacheUseExpiredIfNecessary defaults to false and the default behavior is to use the Environment Cache exactly as it was on the previous release (no changes). If CacheUseExpiredIfNecessary is added to the advanced tab and set to true, the Process Engine's envirornment record caching behavior changes so that if the PE's cache of user information (e.g., group membership) in the database is old, the Process Engine will use it anyway rather than call into the Content Engine at runtime to get updated information. Generally, these "on demand" calls into the CE to get updated group information happen only if the vwusersync daemon was unable to keep the users and group information up to date in the time allocated by the Cached Entry Timeout setting (defaults to 4 hours). The "on demand" calls (which should not generally be happening) can be very expensive and disruptive if the groups contain many members, and the "on demand" refreshing cause significant response time issues that are visible to end users. For a more detailed explanation of how the environment caching works, see technote 1501780 Setting this new option to true will make the PE Server avoid the costs and response time impacts that are seen when the "on demand" calls to refresh group membership information are made. With this option set to true, the vwusersync daemon will continue to do its background refreshing of the user and group information in the PE's database. And the PE runtime will still notice that the memory cache group information is old and re-read the group membership data from the database (a fast operation). So once vwusersync gets the PE's database updated, the new group membership information will be seen by the Process Engine the next time it's accessed. That is, the group membership is still automatically refreshed and brought into play as soon as possible. But, with the CacheUseExpiredIfNecessary set, the PE Server will use older (slightly expired) group membership information and "carry on" with its work rather than forcing the update to the group membership immediately. This feature is available in CPE 5.2.0.4, CPE 5.2.1.1, and any newer releases as well. |
|
PJ42647 |
Fix |
vwtool env i f m y and env v p * commands stop unexpectedly and don't check and/or display all users and groups. |
PJ42691 |
Fix |
|
PJ42697 |
Fix |
After a step splits and one work item goes to a queue and the other goes to a wait for condition step, this exception is seen: [FNRPE2131090436E]Assertion failed in file "WorkObject.java", method "checkFailed", line 6,793. |
PJ42823 |
Fix |
vwlog will now properly clean up event type 550 records in the vwlog tables |
APAR |
Type |
Description |
|---|---|---|
PJ42471 |
Fix |
Null Pointer Exception at javax.swing.ImageIcon. |
PJ42530 |
Fix |
Work objects waiting for timers fail to move on because the VWTime Daemon fails with this exception in the logs: FNRPE2131090436E VwTimeDaemon: Invalid record value.; Exception: Assertion failed in file "VwTimeDaemon.java", method "doProcessTimers", line 374. |
PJ41705 |
Fix |
The execution of an ILOG WSDL is tested successfully outside
ICM. When attempting to make a web services call inside an ICM
workflow, an XML schema error such as "Cannot resolve the name 'ns1:RequestCase' to a(n)
'element declaration' component" is reported. |
PJ41742 |
Fix |
Widgets for Case Manager Client 5.1.1 not loading due to HTTP
500 errors when accessing P8BPMREST Servlet after implementing
SSO using IBM Tivoli Access Manager WebSEAL 6.1.1. This problem
could also occur under Workplace XT. |
PJ42246 |
Fix |
Setting date property value on a CE Object (like F_CaseFolder) to no time ( -2000000000 ) sets the property to "Aug 16, 1906 12:26:41 am' GMT" |
PJ42011 |
Fix |
peverify displays an "INCORRECT NUMBER OF KEYS." error on multiple tables when using Oracle RAC. |
PJ42049 |
Fix |
Work items in the delay queue fail to process and the following error is seen: FNRCE0051E E_OBJECT_NOT_FOUND
THE REQUESTED ITEM WAS NOT FOUND |
PJ42396 |
Fix |
vwtool dump CDL command incorrectly dumps translated keywords when used on a localized non-English system |
PJ42016 |
Fix |
Process Designer hangs (loops) when the web service is selected from
the PARTNER LINK dropdown and the referenced wsdl has recursive references. |
PJ42079 |
Fix |
A REST API call to retrieve the caseFolderId value does not return the correct value. The value for caseFolderId does not match F_CaseFolder. Instead it matches the value for F_CaseTask. |
PJ42106 |
Fix |
The command vwlog -r 1 -t "DefaultEventLog" -Z -P doesn't delete
the system event log records that it should. |
PJ41985 |
Fix |
PE 5.0.0.5 is sending an incorrect parameter to the
Listener.usage() call. This causes incorrect usage data to
be sent to the IBM System Dashboard tools. That causes incorrect data to be reported by Dashboard and Usage Reporter. |
PJ42088 |
Fix |
A single workflow launch request can result in duplicate workflows being launched if the CreateLiveWorkObject
RPC does not receive a valid exception. A corresponding fix is required in the Content Engine. |
PJ42176 |
Fix |
After the Process Engine has recovered from a database
connectivity issue, the process engine is unable to respond to
client RPCs and must be restarted to restore functionality. |
PJ42197 |
Fix |
After installing 5.1.0.4-P8CE-FP004 or 5.2.0.2-P8CPE-FP002,
CPE/CE server would encounter out of memory exception. Part of the "out of memory" issue could be caused by the calls the process engine was making to the Content Engine APIs to fetch user and group information. |
PJ42255 |
Fix |
When executing a vwlog command to extract user defined fields
in the event log table and one of the user defined fields is a 'Time' type,
the output file is created with the headers, but no content is
extracted and a Fatal exception: java.lang.NullPointerException is seen. |
PJ42222 |
Fix |
When locking a work object, making no changes, and then unlocking it from Process
Administrator, the F_EnqueueTime of that specific work object is sometimes changed to the current time. |
PJ42181 |
Fix |
CE_Operations::setMultipleStringProperty throws a Work Performer
Exception error when the value to be assigned is empty/null. |
PJ42245 |
Fix |
A workitem unexpectedly ends up in the Conductor queue with this exception: [FNRPE2131090436E]Assertion failed in file InstructionSheetInterpreterClass.java, method doSplit, line 9,208. This can happen when a split occurs prior to a Wait for Condition step. |
PJ42261 |
Fix |
During an upgrade from PE 3.5 to PE 5.0, the vwupgrade tool is run. If the underlying Process Engine database is DB2 or SQL Server,
vwupgrade will incorrectly use GUIDs to try to look up users in LDAP and be unable to find any users. This will cause the upgrade to fail. |
PJ42267 |
Fix |
PSIRT 1696 Xalan-J (BPM/Case Foundation) - Apache Xalan-Java could allow a remote attacker to bypass security restrictions, caused by the improper handling of output properties.
An attacker could exploit this vulnerability to bypass the secure processing. |
PJ42270 |
Fix |
Process Engine upgraded to use TLS 1.1. A vulnerability in the specification of the SSL 3.0 and TLS 1.0
protocols could allow an attacker to decrypt encrypted traffic.
Upgrading to TLS 1.1 eliminates a possible vulnerability to this kind of attack. |
PJ42298 |
Fix |
Process Administrator will correctly display a workflow field value defined as string array type;
however if users try to export the displayed data to a file, the output of the string array typed field is truncated. |
PJ42325 |
Fix |
If a parent work object is split into multiple children work objects, changing a workflow field value
of a child work item does not get reflected in the roster until all children work items have rendezvoused. |
PJ42388 |
Fix |
Process Configuration Console is unable to connect to a region if the security specifications (e.g., queue and roster security)
LDAP names of groups or members had been adjusted and no longer matched LDAP. |
PJ42182 |
Fix |
Traces have been improved to help with diagnosing a null pointer exception during e-mail notification that can occur due to a configuration error. |
PJ42519 |
Fix |
Setting CacheSyncInterval to 0 on the Process Task Manager's advanced tab option doesn't disable vwusersync daemon. |
PJ42523 |
Fix |
PSIRT 1929 IBM SDK JAVA TECHNOLOGY EDITION QUARTERLY CRITICAL PATCH UPDATE - JULY 2014. |
APAR |
Type |
Description |
|---|---|---|
PJ41978 |
Fix |
Updates the Process Engine's private JRE to Java 1.6 SR15 in response to a Java PSIRT security issue. See techdoc 1660218 |
PJ40608 |
Fix |
When using the vwtool emptyqueue command to empty a queue that contains workobjects, the queue will be emptied, but the pesvr_system.log file may see "Log Manager not mounted, write of log record skipped for event type |
PJ41699 |
Fix |
Duplicate workflows can be launched if the the network or ORB throws an incorrect exception during a CreateLiveWorkObject PE API call. |
PJ41097 |
Fix |
FNRPE2131090212E VwTimeDaemon gets "FNRPE2131090212E VwTimeDaemon: Error processing work object
number |
PJ41701 |
Fix |
Transferring a workflow with an invalid XML schema will return a generic error that does not explain what is wrong with the schema. |
PJ41182 |
Fix |
Invalid date mask: "mm/dd/yyyy HH:tt:ss" when processing old work objects after upgrading to PE 5.0.0.x. |
PJ41202 |
Fix |
PE Servers in a farm require a separate, random callback port to be opened when communicating with each other on port 32771. |
PJ41219 |
Fix |
In an IBM Case Manager environment, if there is a timer on a work object and the work object ends up in the Conductor queue, timer can repeadedly go off causing the eventlog to log include multiple "FNRCE0051E:E_OBJECT_NOT_FOUND" errors if the work object's task object in CE can't be found (for example because of security or because it hass been deleted). |
PJ41220 |
Fix |
Null Pointer exception in the PE SErver while trying to save changes to a work object after upgrade from PE 4.5.1. |
PJ41511 |
Fix |
Null Pointer exception in the PE Server after a roster query returns F_WORKFLOWNUMBER field as null. |
PJ41262 |
Fix |
Adds a way to specify how long the component manager will wait before attempting to re-send work to a busy component. |
PJ41288 |
Fix |
When using Microsoft SQL Server and setting the "Assign to" column as sortable, using the "All assigned work" in-basket can result an error similar to "The work items for the All Assigned Work in-basket could not be retrieved. (CDEWG1009E)." |
PJ41724 |
Fix |
A workflow sometimes does not terminate all work items if it has split and one of the branches has hit a terminate process step. |
PJ41706 |
Fix |
An attempt to open a workflow definition from within WorkplaceXT by double-clicking on the workflow definition fails to properly open the workflow definition. |
PJ41315 |
Fix |
When using the String function to parse a valid date, an error similar to "The time string 2013-05-28T00:00:00 and the mask xs:datetime, in DTI format, or xs:datetime, in the Java equivalent, must match." may be seen. |
PJ41318 |
Fix |
After upgrading to PE 5.0.0.x, a datetime mask with a single 't' does not work as it did on previous releases. |
PJ41707 |
Fix |
A workflow is incorrectly launched without an attachment when the attachment name contains a veritical bar character |
PJ41420 |
Fix |
An exposed field in a workflow's roster record is not updated when changing the exposed field on a work item when the work item is in the Delay Queue. |
PJ41433 |
Fix |
Process Adminiostrator and Process Configuration Console can display incorrect key information for some indexes. |
PJ41397 |
Fix |
An upgrade from PE 4.5.1 to PE 5.0.0.x can fail because the PE 5.0.0.x upgrade code is assuming that the PE database is configured to be case insensitive. |
PJ41444 |
Fix |
The stringtotime() function, when using 't' as the mask, does not behave the same on PE 5.0 as it did on PE 4.5.1. |
PJ41485 |
Fix |
A ClassCastException occurs when using a subscription (a VWVersion java API object) that contains an invalid WorkSpaceId. |
PJ41525 |
Fix |
When defining a dbexecute connection to call a stored procedure in a DB2 database that is hosted on an AS/400 or iSeries server, the "test connection" button will fail and dbexcute calls will fail. |
PJ41605 |
Fix |
An attempt to call a web service from a workflow can result in an error saying that the partnerLinkRef is "null" and the work object can end up in the Conductor queue. |
PJ41754 |
Fix |
Applet Jars signed with Permissions manifest attribute to support latest client JREs (v1.7.0_051 and newer), and to support SHA-256. See techdoc, 1640073. |
PJ41511 |
Fix |
Work can get stuck in delay steps because the vwtime daemon is
getting NullPointerExceptions that are caused by a roster query that incorrectly returns F_WorkflowNumber as null. |
PJ41654 |
Fix |
After an upgrade from PE 3.5 to PE 5.0, wait-for-event and wait-for-condition can fail if the waited-for workflow was created in PE 3.5 and the waiting workflow was created in PE 5.0 after upgrade. |
PJ41720 |
Fix |
An "Invalid work order type for deadline expiration" assertion failures can occur if web service calls and deadlines are combined. |
PJ41744 |
Fix |
If a user receives an exception when clicking on an attachment
item on the Attachments tab in Process Tracker, the exception information in the java console does not contain a good java stack to help with diagnosing the problem. |
APAR |
Type |
Description |
|---|---|---|
PJ40008 |
Fix |
A race issue between Invoke and Reply causes work items to stick in the WSRequest Queue with the error, "The work queue record is locked. The requested operation is not allowed." |
PJ40394 |
Fix |
A Process Engine 5.0 upgrade fails, causing the error, "[FNRPE2130450021E]The time string 2000-06-08T14:05:32 and the mask xs:datetime, in DTI format, or xs:datetime, in the Java equivalent, must match." |
PJ40408 |
Fix |
WSRequest Thread stops responding, which causes high CPU usage. |
PJ40459 |
Fix |
Users cannot launch Process Engine Applets such as Process Design, PCC, and Process Admin. |
PJ40495 |
Fix |
The F_LastErrorText value only reports a generic error, rather than a specific ORA error, in the Process Engine. |
PJ40519 |
Fix |
The convert function (to convert F_StartTime, for example, to a string) returns the time as a number string ("nnn...nnn") instead of a formatted time string (such as, dd/mm/yy hh:mm:ss) |
PJ40562 |
Fix |
Process Engine upgrade fails on upgrade.cdl file transfer: [FNRPE2130460013E]Invalid field type, -10. |
PJ40577 |
Fix |
Process Engine stops responding when configuring the incoming parameters for the Invoke step that are the same as the web services method and operation. |
PJ40609 |
Fix |
The Process Designer shows Error Message 2 upon validation, without showing the error context. |
PJ40620 |
Fix |
Searching for F_CaseFolder or F_CaseTask, which have Content Engine Guides for values, is difficult when using Process Administration. |
PJ40650 |
Fix |
Using VWTool count with a filter generates the following error message, "[FNRPE1210001000E]Database error ... Cannot bind input to database statement errors." |
PJ40670 |
Fix |
While attempting to call Work Object in the wrong queue, the following error message is logged, "[FNRPE2130660045E]Exception: could not find the object." |
PJ40738 |
Fix |
The VWNotify command tool does not delete the VWNotify record from the correct table when the region backup is enabled and the VWLog record does not exist. |
PJ40800 |
Fix |
Adding a user defined field to an event log through a Process Configuration Console transfer causes an assertion failure while building the table view. |
PJ40808 |
Fix |
After updating to eProcess 5.2.0-002, Component Manager processes some operations twice. |
PJ40959 |
Fix |
Enhancement: user needs p8/v1/users?searchPattern to search the user LDAP environment record using the short name. |
PJ40984 |
Fix |
Using the xmlstringexpr function to extract non-existing attributes from an xml string causes a null exeception in the ConvertOp.internalConvertValue method. |
PJ40993 |
Fix |
When invoking a calling the Process Engine web service the following error message occurs, "Premature end of Content-Length delimited message body." |
PJ41034 |
Fix |
User is unable to launch ICN workflows through the Process Administrator. |
PJ41065 |
Fix |
The transfer error, "invalid operand," is caused during a Process Engine upgrade. |
PJ41083 |
Fix |
After upgrading Process Engine, the existing workflows that contain fields with illegal names, such as "attachment," cause the Tracker to return the error, "Exception reading XML: XML Reading error Syntax in the field name." |
PJ41105 |
Fix |
After making changes to a component step, transferring a workflow task does not present the user with an option to check-in the task to the Object Store. |
PJ41119 |
Fix |
The Process Engine installation program does not create the /bin directory under /opt/IBM/FileNet/WebClient/Router/java/jre. |
APAR |
Type |
Description |
|---|---|---|
PJ40066 |
Fix |
Recursing workflows can lead to Process Engine faults when the BLOB gets too big, the workOrderStackCount gets too large, or both. |
| PJ40103 |
Fix |
"INVALID SEQUENCE/IDENTITY MATCH WITH THE TABLE IDENTITY COLUMN 'F_OBJINT'" error is returned when running PEVerify after an upgrade when there are users from older versions of Process Engine that have F_ObjInt values greater than 1000000000. |
| PJ40172 |
Fix |
Processing Wait-For-Condition waiters that are in the process of terminating might lead to a Process Engine fault. |
| PJ40178 |
Fix |
An expression that contains F_Locked>0, results in a server error: Exception FNRPE2130450018E. |
PJ40228 |
Fix |
The Terminate Process step in a Process Engine workflow does not terminate all associated workitems. |
| PJ40236 |
Fix |
The vwusrsync daemon is only updating 50 records at a time when it needs to update more records. |
| PJ40252 |
Fix |
The vwtfer command returns a java.lang.NullPointerException because of an invalid string literal syntax. |
PJ40270 |
Fix |
A Process Engine upgrade fails with the error "VWUpgrade Reg#n [Error] FNRPE2131090078E Transfer failed; Exception: Transfer failed due to errors in input data" due to expressions that contain the '$' variable. |
PJ40296 |
Fix |
Random(num) function fails with java.lang.ClassCastException if the parameter is a workflow field. |
PJ40314 |
Fix |
The trim and rtrim string functions incorrectly return empty strings. |
PJ40342 |
Fix |
Process Designer displays the wrong field for an operation parameter when switching between queue steps. |
PJ40358 |
Fix |
Using Process Engine time functions, such as adddays, to add time units to system time fields returns incorrect results. |
PJ40376 |
Fix |
Procees Engine returns error "FNRPE2130660064E incorrectly formatted attachment string" when launching workflows using subscriptions with http tunnelling. |
PJ40395 |
Fix |
The Step History tab in Process Tracker shows that the Launch Step is still in progress when it has actually completed. |
PJ40396 |
Fix |
When an InBasket name is localized, a filenet.vw.api.VWServerException is returned when retrieving InBasket items. |
PJ40397 |
Fix |
Process Engine does not prevent launching a workflow with an out of range integer value. |
PJ40398 |
Fix |
Process Configuration Console does not display connection points of the same region ID from different virtual servers on the same host. |
PJ40399 |
Fix |
WaitForCondition system step assigns a value to a field on the tracker work item instead of the participant or queue work item. |
PJ40400 |
Fix |
Process Engine Fix Pack 3 client installer window does not display the correct step after clicking on the "Install" button. |
PJ40401 |
Fix |
Process Engine fails to update the task state when work items from a component step go to the Malfunction queue. |
PJ40422 |
Fix |
A binary attachment is corrupt in an email that is sent using methods of the ContentOperations class. |
PJ40423 |
Fix |
Transfering a CDL fails with error "CDL line 1331: [FNRPE2130601038E]Expecting a semicolon. (line: 1,331, token: 1)" due to routes that have numbers for names. |
PJ40431 |
Fix |
In a localized environment, the subject name and workflow name are not translated correctly when calling the queueelements Process Engine REST API. |
PJ40435 |
Fix |
When calling the getRoleName Process Engine REST API in a localized environment, the roleName in the response is not translated. |
PJ40436 |
Fix |
Validation of a solution using Process Designer fails when the default Malfunction submap has been overridden. |
PJ40458 |
Fix |
The role description is not updated in the Manage Roles dialog after it is modified and the solution is redeployed. |
PJ40508 |
Fix |
The copy and copyMany operations in CE_Operations do not allow documents without content elements. |
APAR |
Type |
Description |
|---|---|---|
PJ39403 |
Fix |
After upgrading a NullPointerException in Axis libraries occurs when Process Designer or P8BPMWSBroker is parsing a complex Web Services Description Language (WSDL). |
PJ39529 |
Fix |
Using Workplace XT process designer, you cannot change a route priority in a Case Manager solution. |
| PJ39530 |
Fix |
The search template in the CE_Operations "SearchForMany" method always returns the attachment for a specific document version instead of the current or released version. |
| PJ39620 |
Fix |
After upgrading to Process Engine 5.0, some existing workflows with a WaitForCondition containing string assignments with the F_WobNum system field can fail with the following error: [FNRPE2131090103E] invalid type: "filenet.jpe.base.Guid". |
| PJ39675 |
Fix |
When transferring and launching a workflow from Process Designer, the F_SourceDoc field of the launched work object references an earlier version of the workflow document. |
| PJ39676 |
Fix |
"[Error] string.format failed on trace of string ..." occurs when turning on Process Engine trace option for application space. |
| PJ39816 |
Fix |
Invoking a Receive/Reply workflow from a Web Services Invoke workflow returns an error at the Reply step, which results in the workitem going into the Conductor queue. |
| PJ39845 |
Fix |
Process Engine client installer does not update peResources.jar for FileNet Deployment Manager 5.x. |
| PJ39870 |
Fix |
The vwtfer command receives a [Err=d502012c] error when importing the application space from a XML/CDL file into a region. |
| PJ39878 |
Fix |
If the expiration date of the timer is set to a date in the past, the workflow is sent to the Conductor queue. |
| PJ39879 |
Fix |
After upgrading from Process Engine 4.5.1 to 5.0.0, using a string containing the @ symbol and the name of a string field containing a user name causes an exception, "0x5c020008, Malfunction: [FNRPE0920020008E]The user or group could not be found." |
| PJ39894 |
Fix |
After running the vwlog tool with the -Z option, the following event types remain in the VWLOG table, 265 (VWNewConfig) and 266 (VWNewWorkClass). |
| PJ39895 |
Fix |
If the termination event logging category is disabled in Process Configuration Console, when launching a new task from IBM Case Manager, the following error is logged "FNRPA0234E The launch step element could not be retrieved." |
PJ39898 |
Fix |
An error occurs when attempting to update a user password in the Process Task Manager after it was changed in the Process Engine database. |
| PJ39900 |
Fix |
If the VWLog table has a high number of event type 352 events, pruning will be slow when running vwlog with -L -T options. |
| PJ39905 |
Fix |
Poor performance occurs when creating a new task. Process Engine executes an excessive number of reads on the case folder object. |
| PJ39928 |
Fix |
Error "[FNRPE2131090426E] Invalid date value" occurs when parsing a time string using the "xs:datetime" mask if the time string contains more than 3 digits in the fractional part of the seconds (milliseconds). |
| PJ39939 |
Fix |
Process Engine 5.0.0.2 advanced upgrade fails with the following error in the logs: "Insert into VWLOG1_XXX Select * From VWLOG1_XXX_ARCHIVE". |
| PJ39940 |
Fix |
After deleting a user from the active directory, work items are not processed from the Delay(0) queue. |
| PJ39948 |
Fix |
You receive an "Exception [FNRPE2131090041E] Invalid data type", when assigning a work object number to a string on a create workflow step. |
| PJ39981 |
Fix |
The F_WobNum and F_WorkFlowNumber field lengths are 0 for a Roster in Process Config Console. |
| PJ39995 |
Fix |
When specifying a routing condition to compare an attachment field to a string field, the validation fails if the attachment data field is on the right side of the operand. |
| PJ39998 |
Fix |
If a column used for sorting has more empty values than the page size, Process Engine Representational State Transfer (REST) results in an error: "the work items for the [xyz] in-basket could not be retrieved", when fetching the Next page on In-Basket items. |
| PJ40002 |
Fix |
If a stored procedure called by DBExecute contains a SELECT 1 statement (or any other SQL statement that causes a result set to be returned), the calling work item receives an exception and is sent to the Conductor queue. |
| PJ40016 |
Fix |
Due to a race condition, a 'WaitForCondition' intermittently overwrites an array element in a farmed environment. |
| PJ40020 |
Fix |
When performing an upgrade from Process Engine 4.5.x to Process Engine 5.0.0, an error occurs: 'VWUpgrade Reg#1 [Error]FNRPE2131090078E Transfer failed; Exception: Transfer failed due to errors in input data'. |
| PJ40034 |
Fix |
The Process Engine REST API can fail to update a case property when the new numeric value entered by the end user is 0. |
| PJ40045 |
Fix |
Process Engine incorrectly adjusting java.naming.factory.url.pkgs property, causing javax.naming.ConfigurationException errors in WebSphere. |
| PJ40051 |
Fix |
Directing a task to a User Principal Name (UPN) username in a workflow causes notification settings in user task preferences to be overwritten. |
| PJ40053 |
Fix |
A workflow transfer fails with the error: "[Err=d524000f] Instruction Sheet has duplicate Authored Workorder Ids." |
| PJ40054 |
Fix |
The Filter Condition defined in Process Configuration Console for an InBasket widget returns an error: "Unable to get Queue elements for inbasket," due to special characters being used for the filter name. This feature is included in the REST API enhancement. For additional details, see the technote 1460838. |
| PJ40056 |
Fix |
When editing a solution, users cannot expose F_LockUser, F_LockTime system fields on a Process Engine queue. |
PJ40082 |
Fix |
Starting a virtual server with a name beginning with 'pesvr' will result in a 'java.lang.ArrayIndexOutOfBoundsException' exception. |
PJ40083 |
Fix |
You receive a NullPointerException when using vwtfer to transfer a cdl, due to an older format of the Wait For Condition definition. |
| PJ40084 |
Fix |
PEVerify -help displays an invalid option '-b.'. |
| PJ40085 |
Fix |
The synctableviews command in vwtool does not work. The function performed by this vwtool option is now part of the PEVerify utility. |
| PJ40086 |
Fix |
Enabling Process Engine database tracing will occasionally log 'java.lang.RuntimeException': Alloc connection. |
| PJ40087 |
Fix |
Process Engine 5.0 upgrade on MS SQL does not complete correctly if the database runtime username for the pre-5.0 Process Engine is different than the default schema name. |
| PJ40160 |
Fix |
Process Engine upgrade fails with a NullPointerException when upgrading a backup enabled database with long raw datatypes. |
| PJ40161 |
Fix |
Receive "FNRPE2131090405E vwtran: Transfer terminated by exception" during long transfers. |
| PJ40166 |
Fix |
LDAP search fails with 'javax.naming.directory.InvalidSearchFilterException' if the LDAP search attribute contains an underscore. |
| PJ40201 |
Fix |
Time column displays as Jan 1, 1970 instead of empty if the field only exists in the queue and not in the workflow. |
| PJ40204 |
Fix |
Concurrently deploying the Process Engine configuration from multiple ICM Case Builder sessions, an exception occurs [FNRPE2131090436E] assertion failed. |
| PJ40205 |
Fix |
Inconsistent exposed system fields for CE_Operations in Process Designer and in Case Builder. The Process Engine only has 5 exposed system fields instead of the default of 21. |
| PJ40206 |
Fix |
The work queue properties dialog is empty when editing a solution to add LDAP groups and users to the queue. |
| PJ40207 |
Fix |
When a Process Designer applet is opened from a Safari browser the window is empty. |
| PJ40208
|
Fix |
The 5.0.0.2 Process Engine client installer outputs log entries to peci5001_install_stderr.txt instead of peci5002_install_stderr.txt. |
| PJ40210
|
Fix |
When assigning F_MinMilestone to a workflow data field of integer type, Tasks are not deployed in IBM Case Manager due to a [FNRPE2131090436E] error in the Process Engine . |
| PJ40211
|
Fix |
Process Engine errors that include a Content Engine GUID does not log them in the correct format. |
| PJ40212
|
Fix |
Process Designer does not display annotations associated with the launch step for a solution. |
| PJ40213
|
Fix |
Unexpected Process Engine errors may occur due to concurrent processing of rules by the Rules Connectivity Framework. |
| PJ40219
|
Fix |
Button to select a single participant in Process Designer does not work with JRE 1.7.x. |
PJ40229 |
Fix |
When using Jiglue to get or set date/time data fields from a work object, incorrect date/time values might be retrieved or set. |
APAR |
Type |
Description |
|---|---|---|
PJ39094 |
Fix |
After the Process Engine private JRE keystore password is changed, you cannot start Process Engine with the Content URI https connection. |
PJ39095 |
Fix |
After the Component Manager private JRE keystore password is changed, you cannot start Component Manager with the Content URI https connection. |
PJ39173 |
Fix |
F_EnqueueTime and all other system fields with time data type fail on the 'timetostring' function. |
PJ39220 |
Fix |
An error occurs when attempting to perform a simulation: 'Multiple outputs and SplitType = "none"'. |
PJ39261 |
Fix |
After losing the database connection, the vwtime daemon can terminate and work objects can remain unprocessed in the delay step. |
PJ39272 |
Fix |
A Process Engine client install error is logged when generating the WAR/EAR files with the executeScriptTmp.bat. |
PJ39303 |
Fix |
The Process Engine server logs an exception when processing a 'WaitForCondition' work item that contains invalid field values. |
| PJ39341 | Fix |
The 'numbertostring' function adds an additional minus sign to the existing minus sign when using a minus sign in masking. |
| PJ39375 | Fix |
Reusing VWSession with different JAAS subjects can result in a deadlock. |
PJ39376 |
Fix |
An "invalid types in compare" error is returned when calling GetQueueElementsRequest using the Process Engine Web Services API. |
| PJ39434 | Fix |
A work item cannot launch another workflow and an exception is returned: 'Exception:[FNRPE2130450007E]Expression Execution error:Invalid data type to convert from'. |
PJ39450 |
Fix |
You cannot use the vwtool's deletewob or emptyqueue commands to delete IBM Case Manager (ICM) work items. |
PJ39451 |
Fix |
A "Failed to Read Schema Document" error is returned during an invoke step after changing Web Service Definition Language contents of an external web service. |
PJ39452 |
Fix |
After a user defined field (UDF) is added into an event log table in a DB2 database, users are not able to remove the UDF using the Process Configuration Console (PCC). |
PJ39485 |
Fix |
Using the timetostring function with xs:datetime mask returns an exception: "[FNRPE2130880002E] the date value cannot be parsed with the mask specified for this operation ". |
PJ39486 |
Fix |
When editing a solution in Process Designer, indexes defined on queues do not persist in the Process Engine configuration file. |
PJ39487 |
Fix |
Process Designer returns a validation error after you re-edit a solution and validate a workflow with a submap that calls a main map. |
PJ39494 |
Fix |
Process Engine incorrectly sets a Case Manager task to 'Failed', and sets the task 'Disabled State' to 'Aborted' after deleting a work item if it is not a main work item. |
PJ39496 |
Fix |
The column label in the In-basket becomes blank if the In-basket column field names match the column labels. |
PJ39508 |
Fix |
'The expression contains an invalid conversion data type' error occurs during phase three (transfer phase) of a Process Engine upgrade. |
PJ39511 |
Fix |
Process Designer validation errors occur with 'Integer Form of the Field Type is Invalid: 0' when a worklfow uses nested array subscripts. |
PJ39521 |
Fix |
After a workflow is finalized, you can still transfer changes to a web services Receive and Reply instruction parameters. |
PJ39522 |
Fix |
Inconsistent workflow processing occurs between single and multi-participant steps that have required responses. |
PJ39525 |
Fix |
When attempting to delete all of the work items from a Case Manager workflow, an 'Invalid input parameter' error occurs. |
PJ39581 |
Fix |
When performing a continuation query to fetch work objects from a workbasket, an error is returned: 'Unable to get queue elements for in-basket index.' |
PJ39582 |
Fix |
With a large number of work items in the queue, calling the Process Engine REST resource 'Queue Elements Count', returns an Out of Memory error. |
PJ39583 |
Fix |
The vwtool hidden password does not work and terminates vwtool. |
PJ39596 |
Fix |
Using the -D option with vwmsg fails with a 'ConversionException' on DB2. |
PJ39597 |
Fix |
The peverify help lists an incorrect property name for the sample property file contents. |
PJ39619 |
Fix |
The vwtool > emptyqueue command hangs if there are corrupt or invalid work objects in the queue. |
PJ39621 |
Fix |
VWQueueStats and VWRosterStats classes are not marked as deprecated. |
PJ39622 |
Fix |
Peverify operations perform excessive database queries, which might impact performance. |
PJ39623 |
Fix |
Duplicate index creation is allowed in the same queue. |
PJ39625 |
Fix |
Process Engine server and client installers and uninstallers do not detect and handle Process Engine related running Java processes. |
PJ39626 |
Fix |
Process Engine installers do not copy debug log files from the temporary folder to a more permanent location. |
PJ39627 |
Fix |
When you page back during an installation, then uncheck the product installation location checkbox, the Process Engine client installer attempts to create the previous product installation directories. |
PJ39628 |
Fix |
The Process Engine client installer runs the Enterprise Records Deployment script when Information Enterprise Records (IER) version 5.1 is detected. |
PJ39629 |
Fix |
Transfer has a hard limit on the number of user defined fields on a queue table, which was based on earlier database restrictions. This causes a FNRPE2131090078E transfer error. |
PJ39630 |
Fix |
Process Designer returns a "Row index out of range" error if users delete all of a queues indices. |
PJ39631 |
Fix |
Transfer uses a nested transaction during the final update to replace the workspace and configuration. |
PJ39632 |
Fix |
An incorrect database index is set on the region-specific timeout table for regions that are backup enabled. |
PJ39636 |
Fix |
A 'java.lang.StringIndexOutOfBoundsException' error occurs on Process Engine due to an IBM Java optimization defect. |
PJ39637 |
Fix |
The invalid field name which causes the following exception is not being logged on the Process Engine: 'FNRPE2131090041E ; Exception: Invalid field type: {0}'. |
APAR |
Type |
Description |
|---|---|---|
PJ38404 |
Fix |
Duplicate users in participant lists cause the parent work object to enter the Conductor queue with a malfunction error: FNRPE2131090436E. |
PJ38405 |
Fix |
A malformed email address causes Process Engine to continuously send notification emails to users with correct email addresses. |
PJ38406 |
Fix |
In a farmed environment, Process Engine transfers do not reliably lock other servers of the farm. |
PJ38407 |
Fix |
When you make a Daylight Savings Time change Process Engine returns an error: "FNRPE2131090068E Security attributes disallow access". |
PJ38437 |
Fix |
The sendMailTemplate function only recognizes the first nine parameters. The tenth parameter is interpreted as the first parameter. |
PJ38446 |
Fix |
Concurrent invokes against the Process Engine Web Services Receive operations intermittently result in a VWKs process to abort. |
PJ38480 |
Fix |
A workflow that inherits data fields and uses the Create system step to launch a copy of itself fails to transfer. |
PJ38547 |
Fix |
An ora-22858 error occurs when transferring a workflow to an isolated region. |
| PJ38636 | Fix |
After forty (40) submaps are added to a workflow, additional submaps are not displayed by Process Designer. |
| PJ38730 | Fix |
In a network deployment of P8 Application Engine where each Application Server instance has more than one Java Virtual Machine (JVM) running, Process Engine Web Services returns a timeout error. |
PJ38815 |
Fix |
A Process Engine workflow transfer fails while executing a 'drop view'. |
| PJ38844 |
Fix |
Some logging events are not disabled as expected when all logging events are set to disabled in the Process Configuration Console. |
| PJ38846 |
Fix |
Using a Custom Simple Object Access Protocol (SOAP) message to invoke a Process Engine Web Services receive operation causes one of the VWKs to crash. |
| PJ38847 |
Fix |
Email notifications for previously set deadlines or reminder timers are not reset for the work item when leaving the Conductor queue. |
| PJ38864 |
Fix |
The Component Adaptor stops abruptly without any error messages when there is a timeout on the adaptor. |
PJ38929 |
Fix |
Process Engine can not properly communicate with the Rules Connectivity Framework (and to the Rules Engine) when multi-byte character sets are involved. Attempts to use a Rules Engine with Chinese characters, for example, fails. |
PJ38996 |
Fix |
A NullPointerException error is returned when starting Process Task Manager on an All-in-One P8 configuration: |
PJ39036 |
Fix |
When attempting to deploy a solution using Process Engine, an error "[FNRPE2130360015E]Instruction Sheet has duplicate Authored Workorder Ids" is returned. |
PJ39038 |
Fix |
With a high volume of records in the won't table, performance problems occur with vwtime when moving workflows out of delay state. |
PJ39039 |
Fix |
Events are being written out of order in the Event Log table. |
PJ39040 |
Fix |
Changing a users short name can cause VWKs processes to abort. |
PJ39041 |
Fix |
Using Process Engine Web Services (PEWS) with Kerberos to interface with Content Engine Web Services hosted on JBoss with Kerberos for Content Engine setup, the user/requester/originator from the first PEWS request is used as the user for all subsequent PEWS requests, even if the request is sent from a different Windows/Kerberos user on a different workstation. |
PJ39074 |
Fix |
WorkFlow malfunction notification email not working if work item goes into the Conductor queue from a Component step. |
PJ39075 |
Fix |
When using a custom template that contains "{}" characters for email notification, incorrect formatting occurs in the emails. |
PJ39076 |
Fix |
With the Process Engine REST API, a null or empty workflow date is returned as "1906 Aug 16." |
PJ39077 |
Fix |
Enabling tracing using fnlog4j.properties might log passwords into the trace output as clear text. |
PJ39081 |
Fix |
Starting Process Designer returns a "workObjectEx" was not found on the server' error. |
PJ39082 |
Fix |
The Process Engine 5.0.0.x uninstaller does not uninstall everything on an HP platform. The jvm directory is not removed. |
PJ39084 |
Fix |
When upgrading from Process Engine 5.0.0.x, some required .jar files on the component manager node are not added to the RequiredLibraries values for Component Manager. |
PJ39085 |
Fix |
The "Database Column Size Factor" field in the Process Task Manager advanced upgrade panel does not offer options 1 and 2. |
PJ39087 |
Fix |
The 5.0.0 Process Engine client Installer silent install file for Windows does not contain a parameter (USER_REQUESTED_RESTART) to control reboots. |
PJ39096 |
Fix |
When a work item is in the system function "WaitForCondition", a GetStepElementsFromRoster() API call fails with the exception: "theFieldType is not a valid field type". |
PJ39114 |
Fix |
An error: "Syntax error in deadline expression : Error: syntax error" occurs when attempting to deploy an ICM solution. |
PJ39125 |
Fix |
An "'Invalid WSDL URL" error occurs when attempting to add an external web service to a workflow definition if the web service WSDL is constructed from imported XSD files. |
PJ39127 |
Fix |
The 'assign' step is missing from the vwlog event log records after upgrading to 5.0.0.x if your system was previously at Process Engine version 3.5.x |
PJ39159 |
Fix |
In-basket changes intermittently fail to commit when using the File->"Transfer Workflow Collection" menu item of the Process Designer. |
PJ39160 |
Fix |
A record in the VWObject table that references a nonexistent VWLog table causes an upgrade to fail. |
PJ39161 |
Fix |
The Parameters message type can not be used on Process Designer when invoking a Web Service. |
PJ39162 |
Fix |
You cannot add Case Manager workflow definitions to a scenario definition. |
PJ39166 |
Fix |
A 'java.lang.IllegalArgumentException: Row index out of range' error is returned when attempting to create or define an index on an empty table. |
PJ39167 |
Fix |
In Process Designer and the Process Configuration Console, the Field Selection dialog does not display newly exposed fields. |
PJ39168 |
Fix |
In Process Designer, when a new Base Work Class is selected, the event log is always set to DefaultEventLog. |
PJ39169 |
Fix |
When editing a solution in Process Designer, the CE_Operations component queue is not available. |
PJ39170 |
Fix |
When a Case Manager solution is being edited in Process Designer, setting the object store ID on an isolated region fails. |
PJ39171 |
Fix |
The Case Type Selection dialog in Process Designer does not display more than four case types without manually resizing the dialog box. |
PJ39172 |
Fix |
The value of the F_CaseFolder field is not converted to a string correctly. |
PJ39174 |
Fix |
You cannot save an XPDL file containing a workflow definition without a main "Workflow" map. |
PJ39175 |
Fix |
If the main map is deleted from a workflow definition using Process Designer and there is only one submap defined, that submap is not written to the XPDL file. |
PJ39177 |
Fix |
The Process Engine Process Task Manager Advanced properties 'SQLServerStoredProcWait' is ignored in Process Engine 5.0. |
PJ39178 |
Fix |
Launching a workflow fails if the initiating attachment is an array. |
PJ39179 |
Fix |
Use of an expression containing F_WobNum, such as: "trim(F_WobNum)", causes a transfer error that includes the message "[FNRPE2130460009E]There is an invalid operand type in the expression." |
PJ39180 |
Fix |
Using the Process Task Manager on the Application Engine with an Arabic locale, the drop down Partnerlink Reference combination box in the Web Services tab has the items in the user interface aligned to the left. The items should be aligned to the right. |
PJ39181 |
Fix |
When using Process Administrator, a "NullPointerException" error occurs when querying the Conductor queue after launching and completing a Case Manager workflow. |
PJ39185 |
Fix |
The peObject_import.bat file is missing the "Set" command. |
PJ39186 |
Fix |
After upgrading or reinstalling Process Engine, if the P8TASKMAN_HOME is not defined, starting the Process Task Manager returns a "java.lang.NoSuchFieldError" error. |
PJ39192 |
Fix |
Region lock (user lock via Process Task Manager) does not prevent vwtool->emptyqueue operation. |
PJ39193 |
Fix |
A 'java.sql.SQLException: Got minus one from a read call' error is returned when using SSL and 11.2.0.1 with Oracle 11gR2. |
PJ39194 |
Fix |
When an LDAP user changes their shortname attribute, if the vwtool ->fixup command is not run, the Process Engine server attempts to create a new Process Engine environment record for that user. Process Engine does not log the user's distinguished name when a duplicate name is encountered when updating environment records for users with a changed shortname. |
PJ39200 |
Fix |
When a workflow reaches a Web Service Invoke step, an exception is returned: "Exception: [FNRPE2131090109E]Step, Invalid number of parameter for the queue operation." |
PJ39203 |
Fix |
All events are enabled after a region is initialized. This causes excessive events to be logged, which can effect performance. |
PJ39204 |
Fix |
If a workflow contains string expressions that use "F_CaseFolder," a validation error might occur in Process Designer during workflow validation. |
PJ39205 |
Fix |
Some In_Basket changes are not applied when a solution is redeployed. |
PJ39208 |
Fix |
A "Workspace timestamp is stale" message is erroneously written to the Process Engine server log file. |
PJ39212 |
Fix |
Dashboard Process Engine server Remote Procedure Call (RPC) counts and durations are incorrect when multiple ORB worker threads are processed consecutively. |
PJ39213 |
Fix |
The VWApplicationSpace getRevision() method does not return the correct version after the application space is modified. |
PJ39214 |
Fix |
Using an index based search, different results are returned from the VWQueueQuery fetchCount() and hasNext() methods. |
PJ39215 |
Fix |
After a database migration, an error "VWTrace.sysLog failed on string.format failed for msg: 'CheckDBMigration:" is returned when starting the Process Engine. |
PJ39216 |
Fix |
The vwtool->readcdl command terminates with the error: "[FNRPE2131090436E]Assertion failed in file "IsolatedRegion.java", method "GetMyRegion", line 170. Assertion failed due to a program error." |
PJ39226 |
Fix |
The MAXVALUE for a sequence created for Oracle or DB2 exceeds the maximum value of the corresponding column data type allowed. |
PJ39227 |
Fix |
If a workflow contains over 25 Trackers, only the first 25 Trackers receive email notification when a milestone is reached. |
PJ39231 |
Fix |
When deleting a work object from Process Administrator, if a problem occurs, the error and stack trace is not returned to the client. Consequently, the client has no information on why the deletion failed. |
PJ39234 |
Fix |
The Syslog/TraceException does not work for Remote Procedure Calls that return an array of exceptions. |
PJ39236 |
Fix |
After migrating the Process Engine database from SQL to DB2, during Process Engine startup, a DB2 error is returned: SQLCODE=-204, SQLSTATE=42704. |
PJ39293 |
Fix |
Process Engine applications, such as Process Administrator, hang when a region is locked by the Process Task Manager. |
PJ39295 |
Fix |
A "Remote Host Refused an Attempted Connect Operation" error occurs during phase 3 of a Process Engine upgrade. For details, see technote: 1499410. |
PJ39296 |
Fix |
When restarting the Process Engine server, a locked region is not detected. |
PJ39297 |
Fix |
User exception messages are erroneously written to the Process Engine server log by default. |
PJ39308 |
Fix |
Process Engine daemon threads polling intervals are in minutes granularity instead of seconds granularity. |
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:
IBM Corporation J74/G4 555 Bailey Avenue San Jose, CA 95141 U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan, Ltd. 19-21, Nihonbashi-Hakozakicho, Chuo-ku Tokyo 103-8510, Japan
The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:
IBM Corporation J46A/G4 555 Bailey Avenue San Jose, CA 95141-1003 U.S.A.
Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.
The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.
Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.
This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
Other product and service names might be trademarks of IBM or other companies.
Date |
Description |
|---|---|
| 11 August 2017 | Initial release of this fix pack. |