- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I occasionally get this error when using the dboutput command :
command="dboutput", Unexpected error while performing dboutput: java.lang.ArrayIndexOutOfBoundsException: 100
It appears to relate to the number of records that the command is trying to update. Certainly, whenever the command succeeds the record count is less than 101. I have applied a "| head 100" command to ensure the record count is 100 or less. This seems to be successful in avoiding the error but I am now losing records.
If there is a limit it should be configurable should it not? In this case it looks like the source is hard coded for 100 records and is failing rather than a limit being applied.
Am I interpreting this error correctly?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
![Lucas_K Lucas_K](https://community.splunk.com/legacyfs/online/avatars/117798.jpg)
Might be batch size.
http://docs.splunk.com/Documentation/DBX/latest/DeployDBX/javaspec
[dboutput]
batch.size = <n>
More info in this post : http://answers.splunk.com/comments/88886/view.html
Seems to suggest that type=update uses the batch setting as the total it will support where as type=insert will use the setting as many times as required.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That stopped it. I added the block
[dboutput]
batch.size = 110
to the java.conf file and restarted Splunk. I ran some tests and the error now happens at 110 as set.
Thanks for your help.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
![Lucas_K Lucas_K](https://community.splunk.com/legacyfs/online/avatars/117798.jpg)
Might be batch size.
http://docs.splunk.com/Documentation/DBX/latest/DeployDBX/javaspec
[dboutput]
batch.size = <n>
More info in this post : http://answers.splunk.com/comments/88886/view.html
Seems to suggest that type=update uses the batch setting as the total it will support where as type=insert will use the setting as many times as required.
![](/skins/images/FE4825B2128CA5F641629E007E333890/responsive_peak/images/icon_anonymous_message.png)