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.