Tuesday 26 September 2017

Resolutions for common Oracle SOA Error-Messages

While developing and testing SOA composite or OSB services, an engineer often waste his time for some tricky environment/application/setup/coding issues/mistakes.  So, thought to start a post to give resolutions for some these error messages (most of the errors mentioned below occurs due to the over-sight of an engineer :) -- Jun/27/2013

***********************    ************************* *****************************
BPEL Errors
  • A synchronous BPEL component calls the Asynchronous BPEL component.  If you receive the error "No response found for the reply for conversation id" or "Waiting for response has timed out. The conversation id is null" or "Error while invoking endpoint ... security subject : Administrator" while testing the synchronous BPEL then, make sure to change the synchronousBPEL component's property "bpel.config.transaction" value to "requiresNew".  The other solution is to implement the "correlation set between SynchBPEL and AsynchBPEL Calls".

*************************      ********************** *****************************
  • ORA-28001: the password has expired ... while creating connection for pool "mds -soa": ORA-28001: the password has ...OraSDPMDataSource

Internal Exception: weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogi
c.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException
: Could not create pool connection. The DBMS driver exception was: ORA-28001: th
e password has expired

resolution: 
ALTER USER DEV_SOAINFRA IDENTIFIED BY XXXX ACCOUNT UNLOCK;

************************    ************************    ***************************
  • While compiling the BPEL process, which is with Correlation Set functionality, JDeveloper throws the error message : Error: The XPath segment "child::ns:xxxxx" cannot be resolved
          Solution: Remove "/"  in the query part of path expression defined for "Property Alias".

**********************************        ***************************************    ********************************************

Error: While Harvesting OSB project to OER, getting below error :
log4j:WARN Please initialize the log4j system properly.
com.oracle.oer.sync.framework.MetadataIntrospectionException: com.oracle.oer.syn
c.framework.MetadataIntrospectionException: com.oracle.oer.sync.framework.Metada
taIntrospectionRuntimeException: Error: Unable to find asset type in OER: ed1ed5
34-39b8-11de-bee0-79d657a0a2b0.  Please make sure that the Harvester Solution Pa
ck is installed in OER.


Solution:
import 11.1.1.6.0-OER-Harvester-Solution-Pack.zip file in OER using  Admin (tab) ->  Import/Export (option)

***************** ****************************** ***********************

Not able to start OSB managed server with below error message in the server log :java.lang.NoClassDefFoundError: oracle/dms/http/Request

Solution:
Navigate to Nodemanager properties file "<weblogic_home>\common\nodemanager"
open  nodemanager.properties file
Update the property :
StartScriptEnabled=true

*************************************************************************
JNDI call for Datasource in pojo is throwing error :   
java.lang.UnsupportedOperationException: Remote JDBC disabled

solution:

1) goto $MiddlewareHome$\Domain\DefaultDomain\bin the path may be different depending on your installation
2) edit setDomainEnv.cmd and change "set WLS_JDBC_REMOTE_ENABLED=-Dweblogic.jdbc.remoteEnabled=true"
3) go back to jdev and start servers

**********************************************************************************************************************

While running multiple threads (realted to Weblogic mBeans/JMX), you may receive the error:
<Warning> <Socket> <BEA-000402> <There are: XX active sockets, but the maximum number of socket reader threads allowed by the configuration is: XX. You may want to alter your configuration.> 


solution:

open startWeblogic.cmd
add below line 
set JAVA_OPTIONS=%JAVA_OPTIONS% -Dweblogic.ThreadPoolSize=100 -Dweblogic.ThreadPoolPercentSocketReaders=50 -Dweblogic.SelfTuningThreadPoolSizeMin=100

No comments:

Post a Comment