Unable to display Flowtrace due to exception while initializing object

It is most likely the issue is caused by missing roles and grants from the system-jazn-data.xml file. Make sure the system-jazn-data has the proper Roles and Grants by comparing with another working environment, if not possible use attached file "system-jazn-data.zip" that contains 2 system-jazn-data to compare, "system-jazn-data_BAD.xml" and "system-jazn-data_GOOD.xml" here you can see the differences between a good and bad one
1.- Stop all servers (admin and managed)
2.- Back up your "<DomanHome>/config/fmwconfig/system-jazn-data.xml" file
3.- Add the missing Roles and grants to the file from a previous backup or another working environment file
4.- start admin and then managed servers
5.- retest the issue

Even after that we observed that issue still persists. then we refer to (Doc ID 1644021.1) where the file DOMAIN_HOME/config/fmwconfig/audit-store.xml is 0 bytes or otherwise corrupted.

To resolve this issue:
1. Stop all the WebLogic servers in the domain, including AdminServer.
2. Restore the corrupted file DOMAIN_HOME/config/fmwconfig/audit-store.xml from a backup. Note that the backup must be the same version, patchset and PSU as the active environment.
3. Start all the WebLogic servers in the domain

FAILED_NOT_RESTARTABLE for ManagedServer in 11g

OPTION 1 :

It has been observed that Manager server went to FAILED_NOT_RESTARTABLE state. For first check what we can do below activities :

1. Stop all manageserver of that particular server.
2. Then nodemanager need to stop.
3. And then nodemanager need to start first.
4. Then manageserver need to start from admin console.

Many time this will resolved the issue.

OPTION 2 :

Normally When weblogic server starts, it creates two lock files :

• $DOMAIN_HOME/servers/{$ManagedServer}/tmp/{$ManagedServer}.lok
• $DOMAIN_HOME/servers/{$ManagedServer}/data/ldap/ldapfiles/EmbeddedLDAP.lok

When WebLogic server stops, it removes these two files. If you not stop server properly these lock files remain. In that case these files need to delete.

OPTION 3 :

But sometime when some more file got corrupted, the such basic thing does not help to resolve the issue. In that cache all data/cache/tmp folder need to remove. Below activities can be performed for the same.

1. Stop all manageserver of that particular server.
2. Then nodemanager need to stop.
3. Keep a backup of 3 folder :

• $DOMAIN_HOME/servers/{$ManagedServer}/tmp
• $DOMAIN_HOME/servers/{$ManagedServer}/cache
• $DOMAIN_HOME/servers/{$ManagedServer}/data

4. After taking backup you can delete these folder.

5. Start nodemanager.

6. Start ManagedServer from admin console.

This will help to resolved the issue.

HTTP 500 error : 'java.io.IOException: Stream closed'

Whenever you are getting below error while accessing instances in em console you can try this :

If you are getting below error while clicking on instances :

==================================================

HTTP 500 error :
'java.io.IOException: Stream closed'

==================================================
CAUSE
==================================================

This means EM console instances got corrupted due to FlowTrace.jspx.xml file. After looking for $DOMAIN_HOME/sysman/mds/partition1/ai/sca/share/audit/mdssys/cust/user/weblogic/FlowTrace.jspx.xml file we found this file was 0 byte file after the disk filling failure.

==================================================
SOLUTION
==================================================

Restore the file $DOMAIN_HOME/sysman/mds/partition1/ai/sca/share/audit/mdssys/cust/user/weblogic/FlowTrace.jspx.xml with a backup or from a working environment.