Symptom

Review these issues in when deploying Process Commander into a system which uses IBM's WebSphere application server.

Solutions

• "Potential violation of Java 2 Security Permission" exceptions logged during startup with WebSphere 6.1
• "Unsuccessful execution caused by an unavailable resource" error due to transaction isolation levels in WebSphere
• "PRBootstrap Error initializing PRAppLoader" message when starting Process Commander
• "Loss of session" errors when using WebSphere in a clustered environment
• "Connection Pool Manager could not allocate a Managed Connection" error when using WebSphere
• "Server launched but failed initialization" error when starting PRPC in WebSphere application server
• "Bad or missing database configuration" error when connecting to a DB2 database using a datasource through WebSphere
• "Unable to obtain Datasource object" error when running PRDBUTIL to upgrade from v5.1 to v5.1SP2
• "Could not create pool connection" ELFCLASS64 error when using WebSphere with Oracle
• WebSphere 6.1 property setting prohibiting opening of work object attachments
• WebSphere 5.1 Application Server hangs
• ConnectionWaitTimeoutException due to connection pool exhaustion
• "J2CA0075W: An active transaction should be present" error when running WebSphere
• "Stored procedure does not exist" error when using WebSphere 6.0 with MS-SQL database
• WebSphere 5.1.1.4 will not support Process Commander Version 4.2
• "Unable to use SHA1PRNG algorithm" error