Jithin's Oracle Tuning Corner

The Oracle Weblog

CHECK APPSERVER LOGS. THE SITE BOOTED WITH INTERNAL DEFAULT SETTINGS, BECAUSE OF: bea.jolt.ApplicationException: TPESVCFAIL – application level service failure

I got this error when I fired up Peoplesoft signon page for the first time after a fresh install. The Message is misleading as I was unable to find anything in the app server logs. So what is the cause?

It turns out that the password for the user (PTWEBSERVER in my case) that is used to start the web server was not correct in my configuration.properties file.

I updated the password (you have to change and encrypt it) using instructions from here and bounce the app server and web server. After that everything was working as expected.

How to Change PTWEBSERVER (user that starts web server) password in Peoplesoft

Due to many reasons, you may need to change the password for the user that starts the webserver. In my case, the user is PTWEBSERVER.

Part I => Change in UI

  • Login to Peoplesoft
  • Peopletools–>Security–>User Profiles
  • Search for PTWEBSERVER
  • In the next screen, delete the existing password in the two password fields and update the new password
  • Save.

Part II => Encrypt Password

  • Open a command prompt (in windows) or Terminal (*nix)
  • Navigate to PS_CFG_HOME\webserv\<domain_name>\piabin
  • Run PSCipher <new_password> .It should display something similar to below. Copy the Value after Encrypted text:

Encrypted text: {V1.2}8GZt0MGixBIhd8CyB21lRQ==

Part III => Update configuration file

  • Backup and then open the file PS_CFG_HOME/webserv/<DOMAIN_NAME>/peoplesoft/applications/peoplesoft /PORTAL.war/WEB-INF/psftdocs/ps/configuration.properties
  • Look for an entry called WebPassword. Update the value with the encrypted text that you copied earlier.
  • Restart the web server.

oacore / forms stdout eating up your CPU and I/O? It’s a bug!!

We’re going live ina few weeks and and my performance tests showed me a distrubing trend. The oacore processes would consume about 40% CPU between them and were churning out 8 GB’s of stdout files for each managed servers in a few hours.

Opening an SR gave me a method to create a filter that would filterout these message but I had to use the EBS scritps to start and stop these managed servers then. And I liked the WL control console :)

After a bit of further digging, I chanced upon Oracle Doc ID 1981206.1, which points to bug 18345006.


After applying the patch jbo messages are no longer being thrown into teh std out, and the CPU and I/O are very normal now


Get every new post delivered to your Inbox.

%d bloggers like this: