POJO Service Engine Logging Codes

POJOSE-4503 

Info 

Initiliazed SU {0}. 

Cause: Service Unit is initialized.

Action: None required.

POJOSE-4513 

Info 

Activated Provisioning endpoint: {0}.  

Cause: POJO provisioning endpoint is activated NMR/Delivery channel.

Action: None required.

POJOSE-4518 

Info 

Found activated consuming endpoint: {0}. 

Cause:

Action: None required.

POJOSE-5001 

Info 

Operation QName was not specified on the Endpoint {0}, not setting it on MessageExchange. 

Cause:

Action: This may be intentional. If the consuming service expects an operation name, make sure the @ConsumerEndpoint property operationQN has the appropriate value.

POJOSE-5501 

Info 

Initialized {0} successfully! 

Cause: The specified component was initialized.

Action: None required.

POJOSE-5502 

Info 

Started {0} successfully! 

Cause: The specified component was started.

Action: None required.

POJOSE-5503 

Info 

Stopped {0} successfully! 

Cause: The specified component was stopped.

Action: None required.

POJOSE-5504 

Info 

Shut down {0} successfully! 

Cause: The specified component was shut down.

Action: None required.

POJOSE-5505 

Info 

POJO SE Component started.  

Cause: The POJO Service Engine was started.

Action: None required.

POJOSE-5506 

Info 

POJOSE Component stopped. 

Cause: The POJO Service Engine was stopped.

Action: None required.

POJOSE-5507 

Info 

Deployed SU {0}. 

Cause: The specified Service Unit was deployed.

Action: None required.

POJOSE-5508 

Info 

Started SU {0} 

Cause: The specified Service Unit was started.

Action: None required.

POJOSE-5509 

Info 

Sopped SU {0} 

Cause: The specified Service Unit was stopped.

Action: None required.

POJOSE-5510 

Info 

Shut down SU {0} 

Cause: The specified Service Unit was shut down.

Action: None required.

POJOSE-5511 

Info 

Undeployed SU {0} 

Cause: The specified Service Unit was undeployed.

Action: None required.

POJOSE-6002 

Warning 

Asynchronous consumer has non void return type for Operation method in class {0}, return type will be ignored. Only return type of OnDone method is considered. 

Cause: Class with @Provider annotation does not have a void return type for the Operation method.

Action: None required, but changing the return type to void will avoid this warning message.

POJOSE-6003 

Warning 

Asynchronous consumer has non void return type for OnReply method in class {0}, return type will be ignored. Only return type of OnDone method is considered. 

Cause: Class with @Provider annotation does not have a void return type for the OnReply method.

Action: None required, but changing the return type to void will avoid this warning message.

POJOSE-6500 

Warning 

Provisioning service ended in error before the response message from consumed service {0}, received. 

Cause: See the exception stack trace for the cause.

Action: This may be expected behavior. If it is not, check for the cause of the error in the Provisioning service.

POJOSE-6501 

Warning 

{0} failed to close DeliveryChannel during shutdown: {1} 

Cause: See the exception stack trace for the cause.

Action: Check the cause in the exception stack trace and take appropriate actions to fix the error.

POJOSE-6502 

Warning 

Exception while handling configuration change in one of the listener.  

Cause: See the exception stack trace for the cause.

Action: Check the cause in the exception stack trace and take appropriate actions to fix the error.

POJOSE-6503 

Warning 

Got ERROR ME status from consuming Endpoint:{0}  

Cause: See the exception stack trace for the cause.

Action: Check the cause in the exception stack trace and take appropriate actions to fix the error.

POJOSE-7001 

Severe 

Error {0} injecting field {1}. 

Cause:

Action: Make sure the type of field matches with the object being injected.

POJOSE-7003 

Severe 

Error, ServiceEndpoint got is null, not injecting field {1}. 

Cause:

Action: Check all the necessary annotation property values that are required to search ServiceEndpoint to be sure the correct values are entered.

POJOSE-7004 

Severe 

No public method with Operation annotation found in class {0}, ignoring this class. 

Cause: The class with the @Provider annotation is missing a public method with the @Operation annotation.

Action:

POJOSE-7005 

Severe 

Error loading class {0}  

Cause: A required Java class could not be loaded.

Action: Make sure all the dependent classes are available for the POJO SE.

POJOSE-7100 

Severe 

At least one public method should be present in class {0} with @Operation annotation. 

Cause: The class with the @Provider annotation is missing a public method with the @Operation annotation.

Action: Annotate a public method with @Operation so the POJO SE can invoke with the message for the Endpoint.

POJOSE-7101 

Severe 

Operation method {0} should be public in class {1}. 

Cause:

Action:

POJOSE-7102 

Severe 

Operation method {0} should not be static in class {1}.  

Cause:

Action:

POJOSE-7106 

Severe 

OnDone annotated method {0} should be public in class {1}. 

Cause:

Action:

POJOSE-7107 

Severe 

OnReply method {0} should be public in class {1}. 

Cause:

Action:

POJOSE-7108 

Severe 

More than one method is annotated with @Operation in class {0}. 

Cause:

Action: Make sure only one method is annotated with @Operation.

POJOSE-7109 

Severe 

More than one method is annotated with @OnDone in class {0}. 

Cause:

Action: Make sure only one method is annotated with @OnDone.

POJOSE-7110 

Severe 

OnReply annotated method {0} should not be static in class {1}. 

Cause:

Action:

POJOSE-7111 

Severe 

Method annotated with @OnDone is required when asynch call is used in class {0}. 

Cause:

Action:

POJOSE-7112 

Severe 

OnDone annotated method {0} should not be static in class {1}.  

Cause:

Action:

POJOSE-7113 

Severe 

Method annotated with @OnReply found in class {0} without a public method annotated with @Operation. 

Cause: The class with @Provider annotation is missing a public method with the @Operation annotation.

Action: Annotate a public method with @Operation so the POJO SE can invoke with the message for the Endpoint.

POJOSE-7201 

Severe 

ServiceEndpoint object can not be null. 

Cause: The service endpoint passed directly or set through the @ConsumerEndpoint annotation property is null.

Action: Make sure the ServiceEndpoint object passed is valid and is not null.

POJOSE-7301 

Severe 

Delivery Channel failed to deliver the message to the endpoint. 

Cause:

Action: Check the cause in the exception stack trace and take appropriate actions to fix the error.

POJOSE-7302 

Severe 

Exception while transforming and sending In message. 

Cause:

Action: Check the cause in the exception stack trace and take appropriate actions to fix the error.

POJOSE-7303 

Severe 

Exception while transforming Out message. 

Cause:

Action: Check the cause in the exception stack trace and take appropriate actions to fix the error.

POJOSE-7304 

Severe 

Error while sending a message to the endpoint. 

Cause:

Action: Check the cause in the exception stack trace and take appropriate actions to fix the error.

POJOSE-7305 

Severe 

Node is not of type org.w3c.dom.Element, org.w3c.dom.Text or org.w3c.dom.DocumentFragment 

Cause:

Action:

POJOSE-7306 

Severe 

ServiceEndpoint not set, set ServiceEndpoint or Service on Consumer. 

Cause: The ServiceEndpoint object passed directly or set through the @ConsumerEndpoint annotation property is null.

Action: Make sure a valid, non-null ServiceEndpoint object instance is passed or correct values for the @ConsumerEndpoint property are set.

POJOSE-7307 

Severe 

Sever internal error: Provider "in" MessageExchange is null in ConsumerImpl. 

Cause:

Action: Contact Sun support.

POJOSE-7308 

Severe 

No ServiceEndpoint found for the Service set on Consumer {0}. 

Cause:

Action: Make sure a valid, non-null ServiceEndpoint object instance is passed or correct values for the @ConsumerEndpoint property are set.

POJOSE-7309 

Severe 

Severe internal error while creating Fault instance. 

Cause: Internal error.

Action: Check the cause in the exception stack trace and take appropriate actions to fix the error, or contact Sun support.

POJOSE-7310 

Severe 

Error while converting payload (String or Node or Source) to JBI elements wrapped Source.  

Cause: The payload (String, Node, Source) passed by the user might be invalid.

Action: Make sure the payload (String, Node or Source) passed to construct the FaultMessage object is valid XML.

POJOSE-7500 

Severe 

Exception while sending error status {0}. 

Cause:

Action: Check the cause in the exception stack trace and take appropriate actions to fix the error, or contact Sun support.

POJOSE-7501 

Severe 

Exception while propagating SU status. {0} 

Cause:

Action: Check the cause in the exception stack trace and take appropriate actions to fix the error, or contact Sun support.

POJOSE-7502 

Severe 

Exception while activating endpoint {0}. 

Cause:

Action: Check the cause in the exception stack trace and take appropriate actions to fix the error, or contact Sun support.

POJOSE-7503 

Severe 

Error deactivating Provisioning endpoint: {0}. 

Cause:

Action: Check the cause in the exception stack trace and take appropriate actions to fix the error, or contact Sun support.

POJOSE-7504 

Severe 

Can not deploy SU {0} with below errors. 

Cause: The cause is in the error message.

Action: Correct the errors and redeploy.

POJOSE-7505 

Severe 

Activated consuming endpoint: {0} not found. 

Cause:

Action: Make sure the consuming service is deployed and active.

POJOSE-7506 

Severe 

Endpoint attribute for ConsumerEndpoint annotation can not be empty: {0}. 

Cause:

Action: Enter the required property value.

POJOSE-7507 

Severe 

Failed to parse component descriptor: {0} 

Cause:

Action: Contact Sun support.

POJOSE-7508 

Severe 

Failed to initialize component bootstrap: {0} 

Cause:

Action: Contact Sun support.

POJOSE-7509 

Severe 

Failed to register component bootstrap: {0}  

Cause:

Action: Contact Sun support.

POJOSE-7510 

Severe 

Error while stopping the component. {0} 

Cause:

Action: Check the cause in the exception stack trace and take appropriate actions to fix the error.

POJOSE-7511 

Severe 

Got ERROR ME status for Endpoint:{0} 

Cause:

Action:

POJOSE-7512 

Severe 

Did not get the expected InOnly ME, got {0} 

Cause: The POJO SE Service expects an InOnly MessageExchange but instead received an InOut exchange.

Action: If InOut is expected, make sure the POJO service method annotated with @Operation returns a type other than void.

POJOSE-7513 

Severe 

Did not get the expected InOut ME, got {0} 

Cause: POJO SE Service is expecting InOut MessageExchange but got InOnly.

Action: If InOnly ME is expected make sure POJO service method annotated with @Operation returns void.

POJOSE-7514 

Severe 

Got exception while sending error MessageExchange. {0} 

Cause:

Action:

POJOSE-7515 

Severe 

Internal Error. ProviderTracker not found for Endpoint {0}. 

Cause:

Action: Contact Sun support.

POJOSE-7516 

Severe 

POJO Service ended with exception before response message recieved. 

Cause: Provisioning service ended in an error before the response from the asynchronously consumed service was received.

Action: This may be expected behavior. If it is not, check for the cause of the Provisioning service error.

POJOSE-7517 

Severe 

Allocated threads and blocking queue are full. Please configure to allocate higher resources: Core and Max pool size and blocking queue size of ThreadPoolExecutor. 

Cause:

Action:

POJOSE-7518 

Severe 

Internal error. POJO Metadata not found for endpoint {0}. 

Cause:

Action: Contact Sun support.

POJOSE-7519 

Severe 

Could not find appropriate method with Operation annotation in class {0}. 

Cause:

Action: Make sure a public method to call with incoming message is annotated with @Operation.

POJOSE-7520 

Severe 

Exception while accepting ME from delivery channel. {0} 

Cause:

Action:

POJOSE-7521 

Severe 

Exception while persisting configuration changes. {0}  

Cause:

Action: