ArrayIndexOutOfBoundsException: Array index out of range: 0

Hello,

I am getting the following error :

2011-06-14 08:50:01,998 ERROR [STDERR] java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0
2011-06-14 08:50:01,999 ERROR [STDERR] at java.util.Vector.elementAt(Vector.java:266)
2011-06-14 08:50:01,999 ERROR [STDERR] at com.documentum.fc.common.DfList.get(DfList.java:427)
2011-06-14 08:50:01,999 ERROR [STDERR] at com.citibank.tbo.ctbautoapp.CtbAutoApp.copyObject(CtbAutoApp.java:262)
2011-06-14 08:50:01,999 ERROR [STDERR] at com.citibank.tbo.ctbautoapp.CtbAutoApp.attach(CtbAutoApp.java:248)
2011-06-14 08:50:01,999 ERROR [STDERR] at com.citibank.tbo.ctbautoapp.CtbAutoApp.doSave(CtbAutoApp.java:218)
2011-06-14 08:50:01,999 ERROR [STDERR] at com.documentum.fc.client.DfPersistentObject.saveEx(DfPersistentObject.java:899)
2011-06-14 08:50:01,999 ERROR [STDERR] at com.documentum.fc.client.DfPersistentObject.save(DfPersistentObject.java:894)
2011-06-14 08:50:01,999 ERROR [STDERR] at com.citibank.tbo.ctbautoapp.CtbAutoApp___PROXY.save(CtbAutoApp___PROXY.java)

There is a job where ctb_auto_app type objects are created and on save operation of those objects, this TBO is fired. The error log indicates some problem at line no.262 which shows some problem with copyObject() function. Below is the code snippet for copyObject().

public IDfSysObject copyObject(String objectPath, String destinationFolderId)
        throws DfException
    {
        IDfSession sess = getSession();
        IDfClientX moClientX = new DfClientX();
        IDfCopyOperation idfCopyOperation = null;
        idfCopyOperation = moClientX.getCopyOperation();
        IDfSysObject sysObj = (IDfSysObject)sess.getObjectByPath(objectPath);
        idfCopyOperation.setDestinationFolderId(new DfId(destinationFolderId));
        idfCopyOperation.add(sysObj);
        idfCopyOperation.execute();
        return (IDfSysObject)idfCopyOperation.getNewObjects().get(0);
    }

While doing these, it throws the error:

2011-06-14 08:50:01,998 ERROR [STDERR] java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0

Please advise on this.

Thanks and Regards

dev_dctm

Find more posts tagged with

Comments

aflowers001

You need to check the last line of the method and put in some error handling. My guess is that the copy operation execute failed and you thus have nothing to work with on the next line.

Some error handling in there should assist you.

Francois Dauberlieu

As stated in this community's guidelines, this is not the right place for tech questions. If you want more exposure and since it's about development, you should move this thread to the Developer -> Documentum community. this way, much more people will see it and be able to help you

My 2 cents....

dev_dctm

Hello,

Even I think that there might be problem with the last line which is as follows:

idfCopyOperation.execute();
return (IDfSysObject)idfCopyOperation.getNewObjects().get(0);

It might be so that there is no object in the 0th position which is why it throws ArrayIndexOutOfBoundsException. But I have a query. If the copy operation takes place on a particular object(say 1 word document), then how or rather why does it return multiple objects post idfCopyOperation.execute() out of which we are fetching the 0th position object?

Also, in what case might the copy operation fail as you said that the execution of copy operation would have failed? Well, the environment is 6.5SP3 and the piece of code that I had pasted belongs to a TBO which gets fired through jobs as well as at Application level. When triggered through Application, it causes no problem but when it is fired through jobs, it throws this error once in every 2 weeks. But after the JMS is restarted, the problem no more occurs. What might be triggering this error in every 2 weeks. Please advise on this.

Thanks

dev_dctm

ukamal

From this code, you are assuming that the IDfCopyOperation will always work. Unfortuantely, this is not always the case

I can share my experience with the IDfExport and IDfCheckout operations. They gave us nightmares in our custom java methods until we figured out that they do not always work consistently (a DFC 5.3 bug maybe?). I realize you are not on 5.3 but you may be running into this situation as we were in 5.3 SP5. What we ended up doing, as Andy suggested above, was to place logging around these operations. We generated IDfOperation steps and a custom object in the repository was generated in case these operations failed. This object will contain information about any errors on the operation itself. These errors gave us clues on why the operation failed. It turns out, for our cause, the error we were receiving was due to invalid permissions on the objects but DFC was not bubbling the errors up to the server log. So, the IDfCheckout operation would fail but won't give us any clue on why. The cause could range from the document to the server losing connection temporarily with the database etc