BulkConfigurationError event

Highlight

Event	Description	How to recover	Flow Related
BulkConfigurationError	• Emitted when an invalid bulk configuration results in failure (e.g., during bulk creation/opening or validation).	• Fix the bulk specification (unsupported parser, invalid settings). • Restart the application and retry the add component command	no

Event

Description

How to recover

Flow Related

BulkConfigurationError

• Emitted when an invalid bulk configuration results in failure (e.g., during bulk creation/opening or validation).

• Fix the bulk specification (unsupported parser, invalid settings).
• Restart the application and retry the add component command

Operating Questions

Question	Answer	Comments
Could happen in production?	Technically, yes. In practicality, should only be seen in the test phase	This error will only be a result of a misconfigured bulker application and should be caught in the testing phase
Is it fatal?	Yes

Question

Answer

Comments

Could happen in production?

Technically, yes. In practicality, should only be seen in the test phase

This error will only be a result of a misconfigured bulker application and should be caught in the testing phase

Is it fatal?

Yes

Logs

There are no logs giving further information on this issue. The issue is flagged through the system event, and the bulk state is managed (i.e. it remains the same) until a command is retried following resolution (see a resolution steps section below)

Log level	Log message	Also logs underlying exception?
-	-	-

Log level

Log message

Also logs underlying exception?

Resolution Notes

Currently, the only BulkConfigurationError is for an unknown component parser. The system event errorMessage field will be "Bulk specification includes one or more unknown component parsers". Therefore, the resolution notes target this issue.

Unknown Component Parser

#	Action	Comments
1	Check your bulker configuration for configured component parser names. Fix any misconfiguration.	Specifically check the 'component-parser-name' field’s for each 'ipf.bulker.configurations[]' array values. An example value is "xml".
2	Check the application context for matching InsertionPointFinder beans. If missing, then add the bean into the application context.	InsertionPointFinder beans getName() method should return the same String as the configuration (e.g. "xml"). If you are using the ipf-bulker-aggregate-starter maven dependency, then you will automatically have an InsertionPointFinder bean to handle XML files.
3	If remediation steps are taken so far, then restart the application with the updated context or configuration
4	Resubmit the failing command	Resubmit the latest command that caused this issue to be displayed (e.g. ConfigureBulkCommand). You can do this through the client system by hitting the appropriate methods in the aggregate interfaces (i.e. RecurringBulkAggregate, BulkAggregate). For example, if the issue was displayed when submitting a ConfigureBulkCommand, once the underlying issue is fixed you can replay the command by hitting the RecurringBulkAggregate.configureBulk method.

Action

Comments

Check your bulker configuration for configured component parser names.

Fix any misconfiguration.

Specifically check the 'component-parser-name' field’s for each 'ipf.bulker.configurations[]' array values.

An example value is "xml".

Check the application context for matching InsertionPointFinder beans.

If missing, then add the bean into the application context.

InsertionPointFinder beans getName() method should return the same String as the configuration (e.g. "xml").

If you are using the ipf-bulker-aggregate-starter maven dependency, then you will automatically have an InsertionPointFinder bean to handle XML files.

If remediation steps are taken so far, then restart the application with the updated context or configuration

Resubmit the failing command

Resubmit the latest command that caused this issue to be displayed (e.g. ConfigureBulkCommand).

You can do this through the client system by hitting the appropriate methods in the aggregate interfaces (i.e. RecurringBulkAggregate, BulkAggregate).

For example, if the issue was displayed when submitting a ConfigureBulkCommand, once the underlying issue is fixed you can replay the command by hitting the RecurringBulkAggregate.configureBulk method.