Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Issue: Cannot use WebSphere

Updated on May 21, 2008


Process Commander does not work with WebSphere, due to a bug introduced into that WebSphere version by IBM. 


As part of Process Commander processing, the browser sends encoded data from users’ machines (the client machine) to the Process Commander server, using industry-standard encoding.  Due to the IBM bug, WebSphere takes this data and parses it before passing it to the Process Commander system.  The parsing process alters the data so that Process Commander can no longer read it.




There is no workaround that Pegasystems can apply for this issue.  Instead, use either WebSphere or, both of which do not have this problem.

IBM has identified this bug in their system as PK05760, and has released fixpacks and individual fixes to correct the problem.  Excerpts from PK05760:

In, for a post request with "x-www-form-urlencoded" content-type, its post data can not be read from the InputStream, because it has been consumed by parsing parameters [within WebSphere].

The fix for this APAR is targeted for inclusion in cumulative fixes 5.02.12 and Refer to the recommended updates page for delivery information:

IBM has a patch for this error that may be applied to WebSphere (PK05760_fix_5114.jar). See:

&dc=D421&dc=D422&dc=D42G3&dc=D424&dc =D425&dc=D428&dc=D410&dc=D412&dc=D413&dc=D430

NOTE:  Pegasystems has not tested these fixes. As stated above, WebSphere version or are recommended alternatives.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us