Large Item History causes: Unbuffered entity enclosing request can not be repeated

[driekhof]

Some of our items with lots of history cause an error.  There is about a 2 minute delay as it tries to process the item, and then throws this error:

EXCEPTION: com.mks.api.response.APIConnectionException: Unbuffered entity enclosing request can not be repeated.

sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)

sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)

java.lang.reflect.Constructor.newInstance(Unknown Source)

java.lang.Class.newInstance(Unknown Source)

com.mks.api.response.APIExceptionFactory.getAPIExceptionObject(APIExceptionFactory.java:134)

com.mks.api.response.APIExceptionFactory.createAPIException(APIExceptionFactory.java:80)

com.mks.connect.AbstractCmdRunner.executeCommand(AbstractCmdRunner.java:317)

com.mks.connect.AbstractCmdRunner.executeCommand(AbstractCmdRunner.java:242)

com.mks.connect.AbstractCmdRunner.execute(AbstractCmdRunner.java:394)

foo.bar.MksClient.buildIssue(MksClient.java:268)

Code causing error:

----------------------------------------------

Command cmd = new Command();

cmd.setApp( Command.IM );

cmd.setCommandName( "viewissue" );

cmd.addOption( new Option( "showHistory"));

cmd.addOption( new Option( "showAnnotations"));

cmd.addSelection( issueId );

Response respViewissue  = cmdRunner.execute(cmd); // exception occurs here

If I remove the "showHistory" option it runs without problems, but obviously we don't get the history, which we want.

Is there some server setting we can change so the API will work with large items with lots of history?  We're running on JBoss.

It looks like it may be a looping issue though.  This item refers to another item, which refers back to this item.

[KaelLizak · Accepted solution]

Hello Darrel Riekhof‌,

There isn't really a good way to avoid that error, except to stop using showHistory, but as you mentioned, you want the history.

There is an enhancement request for this:  CS92695.  You could contact PTC Integrity Support to add your organization to that enhancement request, and contacting your Account Manager to prioritize this request if you feel the importance of this functionality warrants it.  The need for this enhancement is certainly valid.  It's not currently scheduled.

Regards,
Kael

[driekhof]

Thanks for the info.

After some more testing on our data, we noticed only had one issue had this problem, so It's not a show stopper for us.  We can export the history manually for the one really big issue.

I thought it might be a looping problem with issues pointing back at each other, but that was not the case.  It seems to only be caused by really large history.