BPEL Sensor ExceptionsORABPEL 20300 - 20330
BPEL Sensor ExceptionsORABPEL 20300 - 20330
Sensor Exceptions 20300 - 20330
ORABPEL-20300
severity: 10
type: error
name: Reports Error.
description: A problem occurred while processing reports data. {0}
fix: Please examine the log file to determine the problem.
ORABPEL-20301
severity: 10
type: error
name: Data Publisher failed.
description: The Reporting Data Publisher {0} failed.
fix: Please examine the log file for more details.
ORABPEL-20302
severity: 2
type: warning
name: JMS connection setup failed
description: A problem occurred while setting up a connection to the JMS Destination {0} using the connection factory {1}.
fix: Please verify the JMS configuration as well as the error to determine the problem.
ORABPEL-20303
severity: 8
type: error
name: JMS publish failed
description: An error occurred while publishing reporting data to the JMS destination \"{0} \".
fix: Please verify the JMS destination is valid.
ORABPEL-20304
severity: 8
type: error
name: JMS destination lookup failed
description: The JMS destination lookup failed. The related reporting data will not be published Please ensure the JNDI name {0) is valid.
fix: Please configure the JMS Destination or correct its JNDI name.
ORABPEL-20305
severity: 8
type: error
name: JMS connection factory lookup failed
description: The JMS connection factory lookup failed. The related reporting data will not be published Please ensure the JNDI name {0) is valid.
fix: Please verify the JMS configuration.
ORABPEL-20306
severity: 2
type: warning
name: JMS connection cleanup failed
description: A problem occurred while releasing the JNDI resources used to publish to the destination {0}.
fix: Please verify the JMS configuration as well as the error to determine the problem.
ORABPEL-20307
severity: 10
type: error
name: Custom data publisher could not be located
description: The custom data publisher class {0} could not be loaded.
fix: Please verify the class file and all dependencies can be loaded from the suitcase or the application classpath.
ORABPEL-20308
severity: 10
type: error
name: Custom data publisher initialization error
description: The custom data publisher class {0} could not be initialized properly.
fix: Please examine the log file for details.
ORABPEL-20309
severity: 10
type: error
name: Sensor name not defined
description: The sensor could not be registered because it has no name.
fix: Please specify the sensor name
ORABPEL-20310
severity: 10
type: error
name: Sensor name already in use.
description: The sensor \"{0}\" could not be registered because a sensor with the same name is already registered.
fix: Please specify a unique sensor name.
ORABPEL-20311
severity: 10
type: error
name: Invalid sensor specified in sensor-sensor action association.
description: The sensor-sensor action association for sensor \"{0}\", action \"{1}\" could not be created because no sensor named \"{2}\" exists in the registry.
fix: Please specify a valid sensor name in the association.
ORABPEL-20312
severity: 10
type: error
name: Invalid sensor action specified in sensor-sensor action association.
description: The sensor-sensor action association for sensor \"{0}\", action \"{1}\" could not be created because no sensor action named \"{2}\" exists in the registry.
fix: Please register the sensor action before specifying an assocation.
ORABPEL-20313
severity: 10
type: error
name: Sensor action name not defined
description: The sensor action could not be registered because it has no name.
fix: Please specify the sensor action name.
ORABPEL-20314
severity: 10
type: error
name: Sensor action name already in use.
description: The sensor action \"{0}\" could not be registered because a sensor action with the same name is already registered.
fix: Please specify a unique sensor action name.
ORABPEL-20315
severity: 10
type: error
name: Sensor registry error.
description: An error occurred while loading sensors and sensor actions for process {1), revision {2} in domain {0}.
fix: Please examine the log file for more details.
ORABPEL-20316
severity: 10
type: error
name: Missing sensor target.
description: No target was specified for sensor {0}.
fix: Please specify a target.
ORABPEL-20317
severity: 10
type: error
name: Invalid variable sensor target.
description: The target {1) for sensor {0} is invalid.
fix: Please specify a $ before the variable name and make sure the variable exists.
ORABPEL-20318
severity: 10
type: error
name: Invalid variable sensor.
description: The configuration for sensor {0} is missing.
fix: The element must be specified for variable sensors. Please complete the variable sensor definition.
ORABPEL-20319
severity: 10
type: error
name: Invalid variable sensor configuration.
description: Sensor {0} is a variable sensor but has activity or fault configurations defined.
fix: Please remove the unnecessary configuration elements.
ORABPEL-20320
severity: 10
type: error
name: Invalid fault sensor configuration.
description: Sensor {0} is a fault sensor but has activity or variable configurations defined.
fix: Please remove the unnecessary configuration elements.
ORABPEL-20321
severity: 10
type: error
name: Invalid activity sensor.
description: The configuration for sensor {0} is missing.
fix: The element must be specified for activity sensors. Please complete the activity sensor definition.
ORABPEL-20322
severity: 10
type: error
name: Invalid activity sensor configuration.
description: Sensor {0} is an activity sensor but has variable or fault configurations defined.
fix: Please remove the unnecessary configuration elements.
ORABPEL-20323
severity: 10
type: error
name: Invalid sensor kind.
description: Sensor {0} is invalid because {1} is an unrecognized sensor kind.
fix: Please specify a valid sensor kind.
ORABPEL-20324
severity: 10
type: error
name: Invalid sensor action.
description: Sensor action {0} is invalid because it publishes to a JMS destination but no destination has been specified.
fix: Please specify the JMS destination property in the sensor action.
ORABPEL-20325
severity: 10
type: error
name: Invalid sensor action.
description: Sensor action {0} is invalid because it publishes to a JMS destination but no connection factory has been specified.
fix: Please specify the JMS connection factory.
ORABPEL-20326
severity: 10
type: error
name: Invalid sensor action.
description: Sensor action {0} is invalid because it publishes to a custom publisher but no publisher class has been specified.
fix: Please specify the fully qualified class name of the custom data publisher.
ORABPEL-20327
severity: 10
type: error
name: Invalid publish type.
description: Sensor action {0} is invalid because {1} is an unrecognized publish type.
fix: Please specify a valid publish type.
ORABPEL-20328
severity: 10
type: error
name: Invalid sensor association.
description: Sensor action {0} is invalid because the associated sensor {1} cannot be found.
fix: Please ensure sensor names used in the sensor action file match those defined in the sensor file.
ORABPEL-20329
severity: 10
type: error
name: Invalid sensor action.
description: Sensor action {0} is invalid because the connection name is not specified.
fix: Please specify the connection name property in the sensor action.
ORABPEL-20330
severity: 10
type: error
name: JMS Adapter Sensor Action Publisher error.
description: The Sensor.xsd schema could not be loaded from the classpath.
fix: Please ensure the Sensor.xsd file has not been modified in any way.
ORABPEL-20330
severity: 10
type: error
name: JMS Adapter Sensor Action Publisher error.
description: The JMS Adapter could not be loaded from the classpath.
fix: Please ensure the JMS adapter has been properly deployed in the application server.
Sensor Exceptions 20300 - 20330
ORABPEL-20300
severity: 10
type: error
name: Reports Error.
description: A problem occurred while processing reports data. {0}
fix: Please examine the log file to determine the problem.
ORABPEL-20301
severity: 10
type: error
name: Data Publisher failed.
description: The Reporting Data Publisher {0} failed.
fix: Please examine the log file for more details.
ORABPEL-20302
severity: 2
type: warning
name: JMS connection setup failed
description: A problem occurred while setting up a connection to the JMS Destination {0} using the connection factory {1}.
fix: Please verify the JMS configuration as well as the error to determine the problem.
ORABPEL-20303
severity: 8
type: error
name: JMS publish failed
description: An error occurred while publishing reporting data to the JMS destination \"{0} \".
fix: Please verify the JMS destination is valid.
ORABPEL-20304
severity: 8
type: error
name: JMS destination lookup failed
description: The JMS destination lookup failed. The related reporting data will not be published Please ensure the JNDI name {0) is valid.
fix: Please configure the JMS Destination or correct its JNDI name.
ORABPEL-20305
severity: 8
type: error
name: JMS connection factory lookup failed
description: The JMS connection factory lookup failed. The related reporting data will not be published Please ensure the JNDI name {0) is valid.
fix: Please verify the JMS configuration.
ORABPEL-20306
severity: 2
type: warning
name: JMS connection cleanup failed
description: A problem occurred while releasing the JNDI resources used to publish to the destination {0}.
fix: Please verify the JMS configuration as well as the error to determine the problem.
ORABPEL-20307
severity: 10
type: error
name: Custom data publisher could not be located
description: The custom data publisher class {0} could not be loaded.
fix: Please verify the class file and all dependencies can be loaded from the suitcase or the application classpath.
ORABPEL-20308
severity: 10
type: error
name: Custom data publisher initialization error
description: The custom data publisher class {0} could not be initialized properly.
fix: Please examine the log file for details.
ORABPEL-20309
severity: 10
type: error
name: Sensor name not defined
description: The sensor could not be registered because it has no name.
fix: Please specify the sensor name
ORABPEL-20310
severity: 10
type: error
name: Sensor name already in use.
description: The sensor \"{0}\" could not be registered because a sensor with the same name is already registered.
fix: Please specify a unique sensor name.
ORABPEL-20311
severity: 10
type: error
name: Invalid sensor specified in sensor-sensor action association.
description: The sensor-sensor action association for sensor \"{0}\", action \"{1}\" could not be created because no sensor named \"{2}\" exists in the registry.
fix: Please specify a valid sensor name in the association.
ORABPEL-20312
severity: 10
type: error
name: Invalid sensor action specified in sensor-sensor action association.
description: The sensor-sensor action association for sensor \"{0}\", action \"{1}\" could not be created because no sensor action named \"{2}\" exists in the registry.
fix: Please register the sensor action before specifying an assocation.
ORABPEL-20313
severity: 10
type: error
name: Sensor action name not defined
description: The sensor action could not be registered because it has no name.
fix: Please specify the sensor action name.
ORABPEL-20314
severity: 10
type: error
name: Sensor action name already in use.
description: The sensor action \"{0}\" could not be registered because a sensor action with the same name is already registered.
fix: Please specify a unique sensor action name.
ORABPEL-20315
severity: 10
type: error
name: Sensor registry error.
description: An error occurred while loading sensors and sensor actions for process {1), revision {2} in domain {0}.
fix: Please examine the log file for more details.
ORABPEL-20316
severity: 10
type: error
name: Missing sensor target.
description: No target was specified for sensor {0}.
fix: Please specify a target.
ORABPEL-20317
severity: 10
type: error
name: Invalid variable sensor target.
description: The target {1) for sensor {0} is invalid.
fix: Please specify a $ before the variable name and make sure the variable exists.
ORABPEL-20318
severity: 10
type: error
name: Invalid variable sensor.
description: The configuration for sensor {0} is missing.
fix: The element must be specified for variable sensors. Please complete the variable sensor definition.
ORABPEL-20319
severity: 10
type: error
name: Invalid variable sensor configuration.
description: Sensor {0} is a variable sensor but has activity or fault configurations defined.
fix: Please remove the unnecessary configuration elements.
ORABPEL-20320
severity: 10
type: error
name: Invalid fault sensor configuration.
description: Sensor {0} is a fault sensor but has activity or variable configurations defined.
fix: Please remove the unnecessary configuration elements.
ORABPEL-20321
severity: 10
type: error
name: Invalid activity sensor.
description: The configuration for sensor {0} is missing.
fix: The element must be specified for activity sensors. Please complete the activity sensor definition.
ORABPEL-20322
severity: 10
type: error
name: Invalid activity sensor configuration.
description: Sensor {0} is an activity sensor but has variable or fault configurations defined.
fix: Please remove the unnecessary configuration elements.
ORABPEL-20323
severity: 10
type: error
name: Invalid sensor kind.
description: Sensor {0} is invalid because {1} is an unrecognized sensor kind.
fix: Please specify a valid sensor kind.
ORABPEL-20324
severity: 10
type: error
name: Invalid sensor action.
description: Sensor action {0} is invalid because it publishes to a JMS destination but no destination has been specified.
fix: Please specify the JMS destination property in the sensor action.
ORABPEL-20325
severity: 10
type: error
name: Invalid sensor action.
description: Sensor action {0} is invalid because it publishes to a JMS destination but no connection factory has been specified.
fix: Please specify the JMS connection factory.
ORABPEL-20326
severity: 10
type: error
name: Invalid sensor action.
description: Sensor action {0} is invalid because it publishes to a custom publisher but no publisher class has been specified.
fix: Please specify the fully qualified class name of the custom data publisher.
ORABPEL-20327
severity: 10
type: error
name: Invalid publish type.
description: Sensor action {0} is invalid because {1} is an unrecognized publish type.
fix: Please specify a valid publish type.
ORABPEL-20328
severity: 10
type: error
name: Invalid sensor association.
description: Sensor action {0} is invalid because the associated sensor {1} cannot be found.
fix: Please ensure sensor names used in the sensor action file match those defined in the sensor file.
ORABPEL-20329
severity: 10
type: error
name: Invalid sensor action.
description: Sensor action {0} is invalid because the connection name is not specified.
fix: Please specify the connection name property in the sensor action.
ORABPEL-20330
severity: 10
type: error
name: JMS Adapter Sensor Action Publisher error.
description: The Sensor.xsd schema could not be loaded from the classpath.
fix: Please ensure the Sensor.xsd file has not been modified in any way.
ORABPEL-20330
severity: 10
type: error
name: JMS Adapter Sensor Action Publisher error.
description: The JMS Adapter could not be loaded from the classpath.
fix: Please ensure the JMS adapter has been properly deployed in the application server.
Comments