netstat -a

Its useful when you configure multiple application or web servers on the same system.

ADMU0113E: Program exiting with error:

           com.ibm.websphere.management.exception.AdminException:

           com.ibm.ws.management.launcher.ServerIdentifiers@4890489, resulting

           from: java.io.FileNotFoundException: C:\Program

           Files\Ibm\SDP\runtimes\base_v7\profiles\AppSrv04\config\cells\WRSVDIN120040Node01Cell\nodes\WRSVDIN120040Node01\serverindex.xml

           (Access is denied.)

Root cause: For some reason when I have created the profile in RSA, I used different userid and passpowrd from the one which I am currenlty logged into the system and trying to start the websphere server in the RSA. Its not allowing to accees the file and gives the file not found exception.

Solution- The very simple solution is to login into the system with the credantials with which you have created the RSA profile.

The other workaround is

(1) Go to C:\WINDOWS\system32, right click on the cmd.exe and choose run as option where you can use the same userid and password which you used during the profile creation.

(2) Now cd C:\Program Files\Ibm\SDP\runtimes\base_v7\bin.

(3) Run WASService.exe -start(for stopping use -stop) <node-name>

 You probably can not see the logs on the console but the logs will be available in SystemOut.log

One more workaroud is run RSA (Right click in RSA exe and choose run as option) with the same userid and password whichyou used during profile creation.

DfException:: THREAD: main; MSG: [DM_WORKFLOW_E_WORKITEM_TRANSITION]error:  “Workitem (4a010b1284484102) fails to make the state transition.”

[DM_WORKFLOW_E_ACTION_NOT_ALLOWED]error:  “This operation is not allowed when the object is at ‘paused’ state.”

; ERRORCODE: 100; NEXT: null
        at com.documentum.fc.client.DfSession.createServerException(DfSession.java:3556)
        at com.documentum.fc.client.DfSession.convertToDfException(DfSession.java:3538)
        at com.documentum.fc.client.DfSession.apiExec(DfSession.java:178)
        at com.documentum.fc.client.DfTypedObjHelperSessionBased.apiExec(DfTypedObjHelperSessionBased.java:322)
        at com.documentum.fc.client.DfTypedObject.apiExec(DfTypedObject.java:208)
        at com.documentum.fc.client.DfPersistentObject.apiExec(DfPersistentObject.java:165)
        at com.documentum.fc.client.DfWorkitem.acquire(DfWorkitem.java:352)
        at com.documentum.fc.client.DfWorkitem___PROXY.acquire(DfWorkitem___PROXY.java)

I have verified the following two points-

(1) Activity runtime state is dormant before acquiring it.

(2) Workflow state is running.

Guess, what may be the reason for this issue. There were two method server instance running in the environment. one acquires the task, at the same time second instance try to execute the activity and ends up with the exception.

Exception: DfException:: THREAD: WebContainer : 876; MSG: [DM_OBJECT_E_LOAD_KEYWORD_ERROR]e
rror:  “error loading object — stream should begin with OBJ”
; ERRORCODE: 100; NEXT: null at com.documentum.fc.client.DfSession.createServerException(DfSession.ja va(Compiled Code))
at com.documentum.fc.client.DfSession.convertToDfException(DfSession.java(Compiled Code))
at com.documentum.fc.client.DfSession.apiExec(DfSession.java(Compiled Code))
at com.documentum.fc.client.DfTypedObjHelperSessionBased.apiExec(DfTypedObjHelperSessionBased.java(Compiled Code))
at com.documentum.fc.client.DfTypedObject.apiExec(DfTypedObject.java(Compiled Code))
at com.documentum.fc.client.DfCollection.next(DfCollection.java(Compiled
 Code))
at com.documentum.fc.client.DfDisposableCollection.next(DfDisposableCollection.java(Compiled Code))

Root cause: I could not figure out still, it gives this error when I am trying to iterate the collection.

Solution: There are number of solutions available to fix this on EMC support  forums specifically talking about changing the DMCL.ini for batch_size etc. But in my application I do not use the site caching services for which these changes are applicable.

One more interesting reason posted on the forums about the nested collection. If you are iterating the collection inside the collection.

But none of above worked in my case. I have set the concurrent users to the below of specific number of users where it was failing and concluded that the application is not able to take the load of that many users.

Still mystery…Let me know If you guys find some thing in this front.

Reason- When try to access the index of the string’s character which is not available.

String sample = “atul”;                         

//Here you will get the String out of range exception. You are trying to get the index of  ‘,’  which is not the character in the string.

sample = sample.substring(0,sample.lastIndexOf(“,”));

Solution: Character must be present in the string before trying to access it.

Well this can be done by executing query or DFC code. Here is the sample DQL query to update the repeating queries.

Update <Object-Type> object set <attribute-name>=<attribute-value>

Note: If you do not specify the attribute index in the query by default it will be updated at zero index and old value will be replaced with new value.

Query with index.

Update <Object-Type> object set <attribute-name>[index]=<attribute-value>

Let’s assume you want to store the value for repeating attributes where the latest available index is not known. Here is the sample DFC code which first finds out the available index and store the values at that index.

IDfDocument document = null;

int availableIndex = 0;

document = (IDfDocument)documentumSession.getObjectByQualification(…);

availableIndex = ((IDfSysObject) documentumSession.getObject(new DfId(<r_object_id>))).getValueCount(<repeating-attribute-name>);

document.setRepeatingString(“<repeating-attribute-name>”,availableIndex,<repeating-attribute-value>);

document.save();

This setting is similar to the global variable which will be access to all the loaded applications.

Go to Severs->Application servers->click on the your server node->Server Infrastructure->Java & Process Management->Class loader.

Click on new ->select Parent First from drop down->click on Apply.

Now click on the name of Classloader ->click on Libraries (Additional Properties) ->Add your shared libraries here.

Parent first option delegates the class loading to the parent class loader before it loads the classes defined in the class path.

Creating session is the costly matter and assumed to be overhead to the system. Documentum has got session manager to manage sessions effeciently (From Documentum 5.x products).

Along with the session manager, Documentum runs the job to keep track of these sessions and Resource Housekeeper error is one of the results of this job.

Here is the sample code for getting sessions….

IDfClient dfClient = null;
IDfSessionManager dfSessionManager = null;
IDfSession dfSession = null;
try {
          dfClient = new DfClient();
          dfSessionManager = dfClient.newSessionManager();

          IDfLoginInfo loginInfo = new DfLoginInfo();
          loginInfo.setUser(“myUserName”);
          loginInfo.setDomain(“myDomain”);
          loginInfo.setPassword(“myPassword”);
         dfSessionManager.setIdentity(“myDocbase”, loginInfo);

        //newSession method of SessionManager creates the new session.

        dfSession = dfSessionManager.newSession(“myDocbase”);

      //getSession of SessionManager gets the session from the available    session pool instead of creating the new session.

     dfSession = dfSessionManager.getSession(“myDocbase”);
}

catch (DfException ex) {
   ex.printStackTrace();

} 

finally {

      //This way you can release the session back to the session pool and will be available for the next client request.
       if (dfSession != null) dfSessionManager.release(dfSession);

      //This way you can disconnect the session and will not go back to session pool, which is idealy not good since there is a overhead to system to create the new session.

       if (dfSession != null) dfSessionManager.disconnect(dfSession);
}

Error 404: javax.servlet.UnavailableException: SRVE0203E: Servlet [ServletVerify]: <Servlet name with full package name> was found, but it is missing  another required class. SRVE0206E: This error typically implies that the servlet was originally compiled with classes which cannot be located by the server. SRVE0187E: Check your class path to ensure that all classes required by the servlet are present.SRVE0210I:

Root Cause: Error 404 always reminds me the problem with the web.xml file where either the data is incorrect or your file is not properly formatted and you start the application and you would land up with Error 404. As the error message specifies application is not able to locate the required class files which are required at run time.

Solution: You can specify the required files or Classpath under Environment Section (Shared Libraries) of WebSphere 6.0 server. Once you define the shared libraries, next you have to map these shared libraries with your application. Click on Applications->Enterprise Applications, you can find your deployed application listed over here, click on your application. Now in Additional Properties you can see the Libraries where you can set the classpath which you have defined under shared libraries.