| Causes | Solution |
|---|---|
| Undefined error has occurred | See the accompanying error messages which should indicate the cause of the error. |
| Causes | Solution |
|---|---|
| [Initial context factory name] of the global resource is wrong, or class library ha not been copied. | Check [Initial context factory name] of the global resource.Or check if the class library has been copied. |
| Causes | Solution |
|---|---|
| [Provider URL] of the global resource is incorrect. | Confirm [Provider URL] of the global resource. |
| Causes | Solution |
|---|---|
| [Topic factory] or [Queue factory] of the global resource is incorrect. | Confirm [Topic factory] or [Queue factory] of the global resource. |
| [Topic name] or [Queue name] of the global resource is incorrect. | Confirm [Topic name] or [Queue name] of the global resource . |
| Causes | Solution |
|---|---|
| JMS provider is not running, or the connection settings are incorrect. | Check whether JMS provider is running, or check the contents of connections setting of the global resource. |
| Causes | Solution |
|---|---|
| Message type specified at [Input data] of Send Message operation is invalid. | Check message type. |