JVM thread dump heap dump process count thread count

Thread Dumps:

$JAVA_HOME/bin/jstack -l <pid>  > /tmp/threaddump_pd_runtime1_$(date).txt

Heap Dumps:

$JAVA_HOME/bin/jmap -dump:live,file=/tmp/file_name <PID>

JMAP:

$JAVA_HOME/bin/jmap -heap <pid> > /tmp/heapdump_pd_runtime1_$(date).txt

Getting the open file count:

/usr/sbin/lsof -u oracle | wc –l


Getting process count:
ps -eLf | grep oracle | wc -l

SOA Composite incorrectly appear in failed state in EM Console

SOA Composite incorrectly appear in failed state in EM Console

You just restarted SOA servers, and verified the SOA platform is ready and accepting requests.

However when you look back at "Deployed Composite" tab under SOA folder in EM console, all the composites appear to be in failed state, and the page looks different from how it looks during healthy SOA status.

The below screen shows how the EM console appears in this case. The red dots with white cross encircled do not appears normally.

This usually happens when you continue to use the same browser session that was open before you shutdown and restarted SOA servers. Do not worry, mostly there is no issue with your  SOA servers.

To fix this, Simply log out from SOA EM Console and log back in again, the the EM console page should appear normal.

OAMSSA-20027 oracle.igf.ids.EntityNotFoundException

Sometimes we see the below error in OAM logs:


<Error> <oracle.oam.user.identity.provider> <OAMSSA-20027> <Could not get user : YXXX, idstore: Active Directory, with exception: oracle.igf.ids.EntityNotFoundException: Entity not found for the search filter (&(objectclass=user)(sAMAccountName=YXXX))..>


In our case, we have enabled chained authentication, which authenticates user first in AD, and then in OUD.

The above error is logged if the user is not found in AD. Hence this can be safely ignored.


If you have chained authentication, and not sure if the user was able to login after the above error or not, look at the log file content below "OAMSSA-20027..Entity not found.. " error.

If the issue couldn't further be found in 2nd LDAP of chained authentication, you'd see another error.


### Failed Login Sample ####
PFB the samlpe error wherein I supplied incorrect OUD credentials. Hence there are 2 errors 1) From AD Entity not found and 2) form OUD .. i.e. Inavlid credentials.

<Jan 8, 2018 10:53:19 AM EST> <Error> <oracle.oam.user.identity.provider> <OAMSSA-20023> <Authentication Failure for user : cn=XXX YYY,cn=users,dc=Corp,dc=hq, for idstore OUDIDStore with exception oracle.igf.ids.AuthenticationException: Authentication failed for user cn=XXX YYY,cn=users,dc=Corp,dc=hq. AdditionalInfo: LDAP Error 49 : [LDAP: error code 49 - Invalid Credentials] with primary error message LDAP Error 49 : [LDAP: error code 49 - Invalid Credentials]>


<Jan 8, 2018 10:53:19 AM EST> <Warning> <oracle.ods.virtualization.engine.backend.jndi.adapter1> <LIBOVD-40082> <Could not modify entry.
javax.naming.directory.SchemaViolationException: [LDAP: error code 65 - Entry cn=XXX YYY ,cn=users,dc=Corp,dc=hq cannot not be modified because the resulting entry would have violated the server schema:  Entry cn=XXX YYY,cn=users,dc=Corp,dc=hq violates the Directory Server schema configuration because it includes attribute oblogintrycount which is not allowed by any of the objectclasses defined in that entry]; remaining name 'cn=XXX YYY,cn=users,dc=Corp,dc=hq'
        at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3118)


### Successful Login Sample ####
<Error> <oracle.oam.user.identity.provider> <OAMSSA-20027> <Could not get user : YXXX, idstore: Active Directory, with exception: oracle.igf.ids.EntityNotFoundException: Entity not found for the search filter (&(objectclass=user)(sAMAccountName=YXXX))..>
<Jan 3, 2018 4:12:56 PM EST> <Warning> <oracle.dms.context> <DMS-57008> <The execution context put in place at the start of the request, 005OUMhIiYp6eLWFLz3V8A0000PI004xXg,0:1:1:2, is not the execution context in place at the end of the request, ef9531de2c28bbbd:748b1134:1603f332b01:-8000-00000000006764fa,0. The request is as follows: Request URI:
  /oam/server/auth_cred_submit
Request URL:
  http://XXXidmpdlogin.la-z-boy.com:80/oam/server/auth_cred_submit