WSVR0703W

Problem 

After stopping the WebSphere Application Server, it does not restart and in the native_stdout.log we see the below error :
.
WSVR0703W
com.ibm.ws.runtime.WsServer
java.lang.NoClassDefFoundError:
org.eclipse.hyades.logging.events.cbe.impl.EventFactoryContext
at com.ibm.ejs.ras.Tr.<clinit>(Tr.java:304)
at java.lang.J9VMInternals.initializeImpl(Native Method)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:200)
at com.ibm.ejs.ras.RasHelper.setServer(RasHelper.java:249)
at com.ibm.ws.runtime.WsServer.<clinit>(WsServer.java:50)
..........
at com.ibm.wsspi.bootstrap.WSPreLauncher.main(WSPreLauncher.java:111)
Caused by: java.lang.ClassNotFoundException:
org.eclipse.hyades.logging.events.cbe.impl.EventFactoryContext
at org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:402)
.
Cause
 Possible osgi class cache got corrupted

Resolution :: 

Run the following steps in order to clear Websphere class caches :

.
- cd IBM/WebSphere/AppServer/profiles/Dmgr01/bin
- run ./clearClassCache.sh
- run ./osgiCfgInit.sh
- cd /tmp/ to confirm that javasharedresources folder is gone
- remove the contents of the following directories:
- profile_root/temp/
- profile_root/wstemp/
- profile_root/config/temp/

then run ./startNode.sh

Also see reference TN:

"How to clear the WebSphere class caches"
http://www-01.ibm.com/support/docview.wss?uid=swg21607887 

Above info find on :: 

http://www-01.ibm.com/support/docview.wss?uid=swg21672201

Read More

WSVR0232E

Problem(Abstract)

The deployment manager JVM fails to start.
Symptom

The SystemOut.log file shows the following errors:

WSVR0232E: Unable to resolve cross document link identified by the uri:  
serverindex.xml#NamedEndPoint_1188855255542, and referenced by document  serverindex.xml        

WSVR0009E: Error occurred during startup
com.ibm.ws.exception.ConfigurationError: com.ibm.ws.exception.ConfigurationError: Exception encountered while extracting configuration information for the Name Space


Cause

The following entry is seen in the serverindex.xml file for one of the nodes in the cell:

<specialEndpoints href="serverindex.xml#NamedEndPoint_1188855255542" />

Resolving the problem

The problem can be resolved by removing the entry from the serverindex.xml file.

    Find the serverindex.xml for the node that contains the NamedEndPoint entry in the WSVR0232E message.


    <DMGR_Profile_Home>/config/cells/cell_name/nodes/node_name/serverindex.xml

    Backup the serverindex.xml file outside of the IBM® WebSphere® Application Server install path if needed.

    Remove the following entries that match the NamedEndPoint in the WSVR0232E messages:


    <specialEndpoints href="serverindex.xml#NamedEndPoint_1188855255542" />

    Save the serverindex.xml file.

    Start the dmgr.

    Issue the SyncNode command from the nodes to synchronize the changes.

Above info find from ::

http://www-01.ibm.com/support/docview.wss?uid=swg21285710

Read More

WTRN0037W

Problem(Abstract)

When WebSphere Application Server attempts to recover Oracle database transactions, the following exception is issued:

WTRN0037W: The transaction service encountered an error on an xa_recover operation. The resource was com.ibm.ws.rsadapter.spi.WSRdbXaResourceImpl@1114a62. The error code was XAER_RMERR. The exception stack trace follows: javax.transaction.xa.XAException
at oracle.jdbc.xa.OracleXAResource.recover(OracleXAResource.java:726)
at com.ibm.ws.rsadapter.spi.WSRdbXaResourceImpl.recover(WSRdbXaResourceImpl.java:954)
at com.ibm.ws.Transaction.JTA.XARminst.recover(XARminst.java:137)
at com.ibm.ws.Transaction.JTA.XARecoveryData.recover(XARecoveryData.java:609)
at com.ibm.ws.Transaction.JTA.PartnerLogTable.recover(PartnerLogTable.java:511)
at com.ibm.ws.Transaction.JTA.RecoveryManager.resync(RecoveryManager.java:1784)
at com.ibm.ws.Transaction.JTA.RecoveryManager.run(RecoveryManager.java:2241)
Cause

Oracle requires that you have special permissions to attempt to perform the recovery.
If there is a system crash during a distributed transaction, the WebSphere Application Server transaction manager will attempt to clean up any failed transactions which it finds in the transaction logs.
When the recovery involves an Oracle XAResource, the Oracle JDBC driver
oracle.jdbc.xa.OracleXAResource.recover function will make a call to DIST_TXN_SYNC.

The above error occurs when the user trying to execute the .recover method does not have sufficient privileges to make a call to DIST_TXN_SYNC.

Environment

This problem can occur with all versions of Oracle: 8i, 9i, 10g, and 11g.

Resolving the problem

Run the following commands as user SYS:

 grant select on pending_trans$ to <user>;
grant select on dba_2pc_pending to <user>;
grant select on dba_pending_transactions to <user>;
grant execute on dbms_system to <user>;  (If using Oracle 10.2.0.3 or lower JDBC driver)
grant execute on dbms_xa to <user>; (If using Oracle 10.2.0.4 or higher JDBC driver)

Where <user> is the username configured in the Oracle datasource's authentication alias.

This problem is mentioned under Oracle bug: 3979190. Running the preceding commands solve the problem.

Update: Since the SYS.DBMS_SYSTEM package contains many procedures, granting execute privileges to that package gives access to all of them. In Oracle patch 5892995 (JDBC driver) and 5945463 (server), Oracle has moved the DIST_TXN_SYNC procedure to a new package called DBMS_XA. These patches are available in 10.2.0.4 and higher. By using the new DBMS_XA package, it will reduce the security risk which DBMS_SYSTEM might cause.

If the recovery of the inflight transactions is not important, then one possible workaround to this problem is to remove the transaction logs. (Does NOT apply to WebSphere Process Server and IBM Business Process Manager, please see note below for details)

The transaction logs are stored in the following folder:
<WebSphere Application Server_install_root>\profiles\<PROFILE_NAME>\tranlog\<CELL_NAME>\<NODE_NAME>\<SERVER_NAME>\transaction

To remove the transaction logs, do the following:
(1) Stop the server.
(2) Delete the '\transaction' folder and all subdirectories.
(3) Restart the server.
The above exceptions will no longer occur.


NOTE: Transaction logs should NOT be deleted if running in a WebSphere Process Server or IBM Business Process Manager environment.
The WebSphere Process Server and IBM Business Process Manager systems can get into an inconsistent state because the logs are tightly coupled with information in other places like BPEDB, WPSDB, SIB messages and MQ, if it is configured.

Above info taken from :: 

http://www-01.ibm.com/support/docview.wss?uid=swg21196663

Read More