com.microsoft.sqlserver.jdbc.SQLServerException: Lock request time out period exceeded

000029e5 DataStoreCont E com.ibm.wps.datastore.impl.DataStoreContext handleException EJPDB0099E: Error occurred during database access. Last SQL statement is [SELECT UNIQUE_ID, CREATED, MODIFIED, NAME, TYPE, LOGGED_OUT, LAST_LOGIN FROM release.USER_DESC WHERE (UNIQUE_ID = ? AND TYPE = ?)]. Transaction has status [STATUS_ACTIVE], global ID [0000013031c772210000000100068b30d17c6e28060142e650cd39de7f3c0101e72b7e670000013031c772210000000100068b30d17c6e28060142e650cd39de7f3c0101e72b7e6700000001] and local ID [428848].
                                 com.ibm.wps.util.DataBackendException: EJPDB0098E: Error occurred during database access. Transaction has status [STATUS_ACTIVE], global ID [0000013031c772210000000100068b30d17c6e28060142e650cd39de7f3c0101e72b7e670000013031c772210000000100068b30d17c6e28060142e650cd39de7f3c0101e72b7e6700000001] and local ID [428848].
    at com.ibm.wps.datastore.impl.DataStoreContext.handleException(DataStoreContext.java:339)
    at com.ibm.wps.datastore.impl.ResourcePersister.findInternal2(ResourcePersister.java:981)
    at com.ibm.wps.datastore.impl.ResourcePersister.findInternal(ResourcePersister.java:880)

Caused by: com.ibm.wps.util.DataBackendException: EJPDB0098E: Error occurred during database access. Transaction has status [STATUS_ACTIVE], global ID [0000013031c762520000000100068b22d17c6e28060142e650cd39de7f3c0101e72b7e670000013031c762520000000100068b22d17c6e28060142e650cd39de7f3c0101e72b7e6700000001] and local ID [428834].
    at com.ibm.wps.datastore.impl.DataStoreContext.handleException(DataStoreContext.java:339)


Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Lock request time out period exceeded.
    at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(Unknown Source)
    at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(Unknown Source)
    at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(Unknown Source)
    at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(Unknown Source)
    at com.microsoft.sqlserver.jdbc.TDSCommand.execute(Unknown Source)



Solution # 1:
Restart the SQL Server services and Portal.

Solution # 2:
If that doesn't work then increase the Lock timeout settings from Admin console and then restart SQL Server services and Portal

How to find Ports for Websphere Portal and WAS

Locate serverindex.xml
@ (Path : C:\IBM\WebSphere\wp_profile\config\cells\<HostName>\nodes\<NodeName>)

You can check the ports here
portal admin console: search for "WC_adminhost_secure"

    <specialEndpoints xmi:id="NamedEndPoint_1282247807415" endPointName="WC_adminhost_secure">
    <endPoint xmi:id="EndPoint_1282247807415" host="*" port="10032"/>
    </specialEndpoints>

portal : search for "WC_defaulthost"
    <specialEndpoints xmi:id="NamedEndPoint_1282247807413" endPointName="WC_defaulthost">
      <endPoint xmi:id="EndPoint_1282247807413" host="*" port="10039"/>
    </specialEndpoints>

Unique Names Problem in IBM WebSphere Portal 6.1

When creating page even if we assign unique names to the pages, yet they don't work properly.

Solution:
This can be resolved by exporting those pages and in the exported xml file you need to replace the generated unique name with the one you want to assign.
Then import that xml again.

Technical Blog: OutOfMemoryError in WebSphere Portal

Technical Blog: OutOfMemoryError in WebSphere Portal: "00001ff4 LogAdapter W DCSV9410W: Failed to allocate memory: 1103 bytes. Exception is java.lang.OutOfMemoryError at com.ibm.rmm.mtl..."

OutOfMemoryError in WebSphere Portal

00001ff4 LogAdapter    W   DCSV9410W: Failed to allocate memory: 1103 bytes. Exception is java.lang.OutOfMemoryError
    at com.ibm.rmm.mtl.receiver.MessageStream.gotMessage(MessageStream.java:553)
    at com.ibm.rmm.mtl.receiver.MessageStream.processData(MessageStream.java:1320)
    at com.ibm.rmm.mtl.receiver.MessageStream.onPacket(MessageStream.java:371)
    at com.ibm.rmm.ptl.tchan.receiver.PacketProcessor.run(PacketProcessor.java:973)


Solution:

Java Virtual machine heap size need to be increased:
Steps:
Open Administration Console:  Locate Servers > Application Servers > WebSphere Portal > Server Infrastructure: Java and Process Management > Process Definition > Java Virtual Machine

Increase heap size.
But need to take care about the paging file. In any case paging file should not be generating for portal instance. You can do this by setting a heap size which doesn't not exceed your physical available memory.