Posts

Error Handling about catch and catch all block

By -
Catch & CatchAll block Catch block 1. This is used to handle specific fault 2. Store fault information in fault variable 3. We can add more than one Catch block in one BPEL process. CatchAll block 1. This is used to handle any type of fault. 2. We need to use functions to get the fault details. 3. We can add only on CatchAll block in one BPEL process. Function we use to get Fault Name and Fault description in CatchAll block We use ora:getFaultName() to get fault name  ora:getFaultAsString() function to get fault description  Fault Handling framework Oracle SOA Suite provides generic fault management framework to handle the faults. We use this framework to handle the fault that occur during invocation time. Catch blocks and Fault Handling Framework CatchAll Blocks 1. We use Catch & CatchAll block to handle all types of error. 2. These can be used only for BPEL component. 3. We can use this for all BPEL templates (Sync, Async, Oneway). Fault Han...
1 comment
Read more

Troubleshooting & Debugging Focus for Weblogic

By -
JDBC: Problem Overview: Stale database connections in WebLogic occur when connections remain open but are no longer in use by applications. This leads to: High CPU usage  (database server struggles with managing dead connections) High memory consumption  (each idle connection consumes resources) Database breakdown  (connection pool exhaustion leading to "ORA-00020: maximum number of processes exceeded" or similar errors) Root Causes: Improper Connection Handling Missing  connection.close()  in application code (JDBC leaks) T ransactions left open without commit/rollback JDBC Pool Misconfiguration Missing  TestConnectionsOnReserve  or  InactiveConnectionTimeout Overly large  MaxCapacity  with no proper cleanup Network/DB Failures Database restarts or network drops leaving connections in a zombie state Long-Running Queries Queries that hang indefinitely (e.g., due to locks or bad SQL) Detection Methods: WebLogic Console Checks Navigat...
2 comments
Read more

Troubleshooting & Debugging Focus for Weblogic

By -
The solution for Log files not rotating   Check the Status of the Server ./startWeblogic.sh ./startManagedWeblogic.sh <manageservername> Another option: Check in the console. Check the disk Space(if fit is full, Delete the logs and then  restart the Server) du –kh (folder) df –kh (filesystem) If the avail capacity is  45% 90% If full , mv <source > <destination> Delete, rm –rf <filename: adminserver.log> Major Server Errors: Check the Status of Servers. ./startWeblogic.sh ./startManagedWeblogic.sh <manageservername> Need to do from console. Check the Server logs /apps/bea/domain/gwmp_destop/logs Adminserver.log Managedserver.log For this Database Errors, Check the Connection pool and Datasource. Services->jdbc->connectionpool,datasource Check out the Deployment Descriptors. Weblogic.xml,web.xml Based on the logs we can change Configuration Changes, Make the Changes and then restart instances one by one if...
Post a Comment
Read more

Administration, troubleshooting, and performance tuning in Weblogic

By -
Server Lifecycle Management: # Start Admin Server $DOMAIN_HOME/startWebLogic.sh  # Unix %DOMAIN_HOME%\startWebLogic.cmd  # Windows # Start Managed Server $DOMAIN_HOME/bin/startManagedWebLogic.sh <server_name> <admin_url> # Graceful stop $DOMAIN_HOME/bin/stopWebLogic.sh  # Admin $DOMAIN_HOME/bin/stopManagedWebLogic.sh <server_name> t3://admin_host:port Force Kill (if hung): kill -9 $(pgrep -f "weblogic.Name=<server_name>")  # Unix taskkill /F /PID <pid>  # Windows Deployment Commands: WLST (WebLogic Scripting Tool): # Deploy app deploy('my_app', '/path/to/app.ear', targets='AdminServer') # List deployments ls('/AppDeployments') # Undeploy undeploy('my_app', targets='AdminServer') Command-Line (weblogic.Deployer): java weblogic.Deployer -adminurl t3://localhost:7001 -deploy /path/app.war Log Inspection: Tail Logs in Real-Time tail -f $DOMAIN_HOME/servers/AdminServer/logs/AdminServer.log Search for Er...
Post a Comment
Read more

Configuration the Two Way SSL Communications:

By -
To configure the Two Way SSL. On the Admin Server Select  SSL tab: Advanced options Two Way Client Cert Behaviour should be  Client Cert Requested and Enforced. Save it. Now if you will can try to access the Admin Console over SSL then you will throw some SSL Handshake exception.  Because of this process  two way SSL, Client is also requested to submit the certificate and we have not configured any certificate for our client  So, we need to configure the certificate for the Client and for that  again we need the Certificates for the Client. We will be using the same CertGen utility of Weblogic Server to create the certificate. java utils.CertGen <-certfile >ClientCert <-keyfile>ClientKey <-keyfilepass> keypass Again it will create four certificates for the client. To convert the client certificate into the PKCS12 format because the browsers generally accept PKSC12 keystore format for storing certificates. Go to t...
1 comment
Read more

Deploying Multiple SOA Composites through ANT Script

By -
ANT script solution for deploying multiple SOA composites (SAR files) to Oracle SOA Suite in a single execution. 1. Prerequisites: Oracle SOA Suite 11g/12c installed ANT (1.9+) with Oracle SOA ANT tasks configured Admin server credentials Composite SAR files ready for deployment 2. ANT Script Template Save as deploy-composites.xml <project name="SOA-Composite-Deployer" default="deploy-all" basedir="."> <!-- Properties Configuration --> <property file="build.properties"/> <!-- SOA ANT Task Definitions --> <taskdef name="scac" classname="oracle.tip.tools.ant.SCACompose" classpath="${oracle.home}/soa/modules/oracle.soa.common_11.1.1/tasks.jar"/>  <taskdef name="sca-deploy" classname="oracle.tip.tools.ant.SCADeploy"  classpath="${oracle.home}/soa/modules/oracle.soa.common_11.1.1/tasks.jar"/> <!-- Main Deployment Target --> <target name="depl...
Post a Comment
Read more

Setting Alarm by using Autosys job and tool handling for alarm

By -
Alarms are  automated notifications  triggered when a system detects an abnormal condition that requires  human attention  to resolve. Unlike automated recovery processes, alarms highlight scenarios where: Manual intervention  is necessary (e.g., decision-making, troubleshooting). Automated fixes  are not possible (e.g., missing dependencies, corrupted data). Timely action  is critical to prevent cascading failures. Key Characteristics of Such Alarm Event-Driven Triggered by specific conditions (e.g., a file not arriving on time, a job failing repeatedly). Example: A scheduled ETL job fails because an expected input file is missing. Requires Human Judgment The system cannot auto-resolve (e.g., deciding whether to proceed with incomplete data or wait). Example: A payment processing system flags a transaction for fraud review. Escalation Mechanisms If unacknowledged, alarms escalate (e.g., email → SMS → phone call → on-call engineer). Example: A server ...
Post a Comment
Read more