Error BPEA0010E can occur in the following situations:
- When a user tries to start a process in the Web client, but the queue
manager is not started. In this case, the user receives a message similar
to:
BPEA0010E: Unexpected exception during execution
- When a user tries to start a process in the Web client, but the
database access does not work. In this case, the user receives a message
similar to:
BPEA0010E: Unexpected exception during execution
- When a user tries to use a staff verb which is not supported for the
selected user registry, for example when using an LDAP-only staff verb
together with the local OS user registry.
In this case, the user reveives a message similar to:
BPEA0010E: Unexpected exception during execution.
java.lang.reflect.InvocationTargetException:
com.ibm.bpe.api.UnexpectedFailureException: BPEA0010E: Unexpected
exception during execution.
com.ibm.bpe.plugins.DeploymentBPELStaffActivityException: BPED0333E:
Deployment of staff activity 'ApprovalStep' failed with exception:
'null'.
1. Queue manager not started:
Find out whether the QueueManager is running properly. For example,
have your WebSphere administrator perform the following steps:
- Open the WebSphere systemout.log file.
- Watch out for the following error message in the log file:
javax.jms.JMSException:
MQJMS2005: failed to create MQQueueManager for
'..._<servername>'
- If this error is found in the log file, start the Queue Manager and
verify that it is running properly.
If the Queue manager was down before step 3
and is running after step 3, try again to start the process in the Web
client.
2. Database access not working:
Find out whether the database is working properly and the access from
WebSphere to the database is working. For example, if the database is DB2
and your operating system is Windows, the password for the user ID
responsible for accessing DB2, for example, db2admin should be specified
in 3 different places:
- The Windows User Registry for the db2admin user ID
- The "Log On" tab for the properties of the "DB2 - DB2" service
- The J2EE role for accessing DB2 as specified in the administrative
console
3. Unsupported staff verb:
Some staff verbs are only supported in conjunction with certain staff
repositories. For example, the verb "Manager of Employee" is only
supported when using an LDAP staff repository.
The error situation with the error message described above can be
reproduced when doing the following (illegal) sequence of steps in
WSADIE:
- create a BPEL process
- in a staff specification (e.g. in a staff activity), use a verb that is
supported only for LDAP
- however select "UserRegistryConfiguration" as staff plugin
- do the operation "generate deploy code"
- do the operation "publish" to server
To get rid of this error, do either of the following corrections:
- use the LDAP staff plugin, or
- usage another staff verb which is supported by the used
staff plugin
The same error may show up if you added your own staff verb by editing
verbset.xml and LDAPTransformation.xsl, but the modification is not
available on the server where you deploy the business process. In this
case, make sure the used verb is available on the target server as well.
If none of these scenarios apply to your situation, please provide us with
feedback on your problem:
- In the document feedback section, type the Web client
error code that you received (format is BPEcnnnnc) and a brief description
of the problem.
- Note: This information will be used to update the
technical support information only. To receive a response to your problem,
submit a service request.
|