| Sun Java System Content Delivery Server Error Messages |    
|
| Sun Java System Content Delivery Server Error Messages |
|
| C H A P T E R 2 |
|
Messages From Content Delivery Server Components |
During the operation of the Content Delivery Server, messages from different components are written to the log file CDS.log in the $CDS_HOME/deployment/deployment-name/logs directory. The types of messages written (for example, warning messages or informational messages) depend on the message level specified in the logging.properties file in the $CDS_HOME/deployment/deployment-name/conf directory. See Section 1.2, "Log Files," in the Sun Java System Content Delivery Server System Management Guide for more information on log files.
This chapter describes messages issued by the Content Delivery Server components and suggests actions that you can take in response. Messages are identified by the module that issued the message and a message number.
The following topics are presented in this chapter:
The following messages are issued by the Messaging Service and its subcomponent, the Confirm Listener Service. The messages are organized alphabetically by the service module that issued the message and numerically for each module.
[cds.ConfirmListener] SEVERE <0002> Could not listen on port port-number
Description. The port number specified for the udp.confirm_listener.port property in the $CDS_HOME/deployment/deployment-name/conf/ConfirmListener.properties file might be incorrect, or the port number is not free. port-number identifies the port number used.
Action. Make sure that the port number specified for the udp.confirm_listener.port property is free and not used by any other application. Restart the server.
[cds.MsgServer] ERROR There was an error delivering this message. Message is stored in the JMS queue for MessageId = {ID}
Description. An error response was received while delivering a push message using Java Message Service (JMS) technology.
Action. Review the external push services integration. Also, review the device profiles to verify that the push type is correct.
[cds.MsgServer] SEVERE <0034> Error while sending SMS Push message using CIMD2
Description. CIMD2 push sender SMSC properties might be set incorrectly in the $CDS_HOME/deployment/deployment-name/conf/MsgService.properties file, or the SMSC is down.
Action. Make sure that the SMSC properties for CIMD2 smsc.hostname, smsc.port, esme.system_id, esme.password and other properties are set correctly in the MsgService.properties file. Also, make sure that the SMSC is up and running.
[cds.MsgServer] SEVERE <0040> Connection could not be established java.net.UnknownHostException[cds.MsgServer] SEVERE <0126> FAILED TO CONNECT TO SMSC [cds.MsgServer] INFO <0127> Will try to reconnect after 60000 milliseconds
Description. The Push Listener SMSC properties might be incorrect in the $CDS_HOME/deployment/deployment-name/conf/PushListener.properties file, or the SMSC is down.
Action. Make sure that the Push Listener SMSC properties are set correctly in the PushListener.properties file, and restart the server. Also, make sure that the SMSC is up and running.
[cds.MsgServer] SEVERE <0054> Error while sending message to WAP PPG com.sun.content.server.server.msgserver.protocolPpgConnectionFailedException: Failed to connect to wap ppg server
Description. WAP PPG properties might be set incorrectly in the $CDS_HOME/deployment/deployment-name/conf/MsgService.properties file, or the PPG is down.
Action. Make sure that the WAP PPG properties asyncmsg.wap.ppg, asyncmsg.wap.ip.bearer, and other properties are set correctly in the MsgService.properties file, then restart the server. Also, make sure that the WAP PPG is up and running.
[cds.MsgServer] SEVERE <0070> Error while sending SMS Push message using SMPP
Description. SMPP push sender SMSC properties might be set incorrectly in the $CDS_HOME/deployment/deployment-name/conf/MsgService.properties file, or the SMSC is down.
Action. Make sure that the SMSC properties for SMPP smsc.hostname, smsc.port, esme.system_id, esme.password, and other properties are set correctly in the MsgService.properties file. Also, make sure that the SMSC is up and running.
[cds.MsgServer] SEVERE <0130> CONNECTION BROKEN
Description. The connection to the SMSC is broken, or the SMSC is down.
Action. Make sure that the SMSC is running and accessible.
[cds.MsgServer] SEVERE <0184> Invalid SMSC host name specified in the properties file
Description. SMSC host name is set incorrectly in the $CDS_HOME/deployment/deployment-name/conf/PushListener.properties file.
Action. Make sure that the pushlistener.smsc.hostname property in the PushListener.properties file specifies the correct SMSC host name, then restart the server.
[cds.MsgServer] SEVERE <0185> Invalid SMSC port number specified in the properties file
Description. The SMSC port number is incorrect in the $CDS_HOME/deployment/deployment-name/conf/PushListener.properties file.
Action. Make sure that the pushlistener.smsc.port property in the PushListener.properties file specifies the correct SMSC port number, then restart the server.
[cds.MsgServer] SEVERE <0192> Invalid property-name property value specified in the properties file.
Description. The property-name property in the $CDS_HOME/deployment/deployment-name/conf/MsgService.properties file might be set incorrectly, or the SMTP Server is down. property-name is either mail.smtp.host or mail.smtp.sender.
Action. Make sure that all the SMTP properties are set correctly in the MsgService.properties file, then restart the server. Also, make sure that the SMTP server is up and running.
[cds.MsgServer] SEVERE <0194> Error while sending SMS Push message using HTTP
Description. HTTP push sender SMSC properties might be set incorrectly in the $CDS_HOME/deployment/deployment-name/conf/MsgService.properties file, or the SMSC is down.
Action. Make sure that the SMSC properties for HTTP cds.sms.http.serverurl, cds.sms.http.user, ces.sms.http.password, and other properties are set correctly in the MsgService.properties file. Also, make sure that the SMSC is up and running.
[cds.MsgServer] SEVERE <0195> There was an error delivering this message, Message is stored in the JMS queue for MessageId = message-id
Description. There was an error pushing the message to an external entity using either SMTP, SMS, WAP PPG or MMSC. Either the external entity is down or it is not configured correctly.
Action. Make sure that the external entity is up and running. Also, make sure that the configuration is correct in the $CDS_HOME/deployment/deployment-name/conf/MsgService.properties file.
[cds.MsgServer] SEVERE <0196> Error while sending SMTP message
Description. SMTP properties mail.smtp.host and mail.smtp.sender might be set incorrectly in the $CDS_HOME/deployment/deployment-name/conf/MsgService.properties file, or the SMTP Server is down.
Action. Make sure that the SMTP properties are set correctly in the MsgService.properties file, then restart the server. Also, make sure that the SMTP server is up and running.
The following messages are written to the CDS.log file in the $CDS_HOME/deployment/deployment-name/logs directory by the Notify Service.
[cds.Root] SEVERE <0147> Could not process subscriber `subscriber-Id'
Description. Processing failed for the subscriber with the ID subscriber-Id. Likely reasons include a failure to connect to or receive authorization from an external database, or the subscriber's device does not have the capability to run the content included in the campaign. No notification is sent to this subscriber.
Action. If no problems exist with the database, make corrections and resubmit the campaign. Notifications are resent to all subscribers that meet the criteria.
[cds.Root] SEVERE <0477> Failed executing campaign for subscriber ID subscriber-Id: campaign-message-text
Description. Processing for the campaign identified by campaign-message-text failed for the subscriber with the ID subscriber-ID. Likely reasons include an incorrect phone number or email address or a network problem. No notification is sent to this subscriber.
Action. If no problems exist with the network, make corrections and resubmit the campaign. Notifications are resent to all subscribers that meet the criteria.
The following messages are issued during the process of synchronizing the Catalog Manager and a Vending Manager. The messages are organized numerically by the message number.
[cds.SynchronizationAPI] <0000> Error while sending the Registration Request for Vending Manager
Description. An error occurred while sending the Registration Request for a new Vending Account to JMS. Possible causes include JMS is down, or JMS is not configured correctly.
Action. Correct the configuration and restart JMS. If JMS is down, run the broker.sh command to restart the JMS message broker if you are running with the Sun Java System Application Server, or restart the application server if you are running with WebLogic Server.
[cds.SynchronizationAPI] <0002> Error while getting Content Capability for the Resource Instance
Description. An error occurred at the entity level. Either the entity being accessed does not exist, the referential integrity was violated, or the database is corrupt.
Action. Run the diagnostic tool to get information on the database and contact Content Delivery Server technical support. See Section 4.1, "Diagnostic Tool," in the Sun Java System Content Delivery Server System Management Guide for information on this tool.
[cds.SynchronizationAPI] <0003> Error while getting Model names for the Resource Instance
Description. An error occurred at the entity level. Either the entity being accessed does not exist, the referential integrity was violated, or the database is corrupt.
Action. Run the diagnostic tool to get information on the database and contact Content Delivery Server technical support. See Section 4.1, "Diagnostic Tool," in the Sun Java System Content Delivery Server System Management Guide for information on this tool.
[cds.SynchronizationAPI] <0004> Failed to get Metadata and Pricing Model list for the Resource Class
Description. An error occurred at the entity level. Either the entity being accessed does not exist, the referential integrity was violated, or the database is corrupt.
Action. Run the diagnostic tool to get information on the database and contact Content Delivery Server technical support. See Section 4.1, "Diagnostic Tool," in the Sun Java System Content Delivery Server System Management Guide for information on this tool.
[cds.SynchronizationAPI] <0005> Error while retrieving meta-data for the Resource Class
Description. An error occurred at the entity level. Either the entity being accessed does not exist, the referential integrity was violated, or the database is corrupt.
Action. Run the diagnostic tool to get information on the database and contact Content Delivery Server technical support. See Section 4.1, "Diagnostic Tool," in the Sun Java System Content Delivery Server System Management Guide for information on this tool.
[cds.SynchronizationAPI] <0006> Error while retrieving Pricing Model list for the Resource Class
Description. An error occurred at the entity level. Either the entity being accessed does not exist, the referential integrity was violated, or the database is corrupt.
Action. Run the diagnostic tool to get information on the database and contact Content Delivery Server technical support. See Section 4.1, "Diagnostic Tool," in the Sun Java System Content Delivery Server System Management Guide for information on this tool.
[cds.SynchronizationAPI] <0007> Error while fetching synchronization data from the Catalog Manager.
Description. An error occurred during the initial synchronization of data between the Catalog Manager and a Vending Manager. Possible causes include the following situations:
Action. The following actions can be taken:
[cds.Synchronization] <0009> Please contact system administrator to restart catalog server.
Description. An InvalidClientIdException occurred. Possible causes include two Vending Managers with the same ID are registered as durable subscribers with the CatalogTopic, or a durable subscriber with that ID already exists.
Action. Restart the Catalog Manager. If the problem still exists, contact Content Delivery Server technical support.
[cds.Synchronization] <0006> CatalogEventListener : Could not create jndi context.
Action. If you are running with Sun Java System Application Server, restart your imqbroker using the broker.sh command. If you are running with WebLogic Server, restart your Catalog Manager.
[cds.Synchronization] <0036> QueueConnection is null. Contact System Administrator to restart the server.
Description. The configuration for JMS is incorrect for the Vending Manager.
Action. Correct the configuration for JMS through your application server. If you are running with Sun Java System Application Server, restart JMS. If you are running with WebLogic Server, restart the application server.
The following messages are from the server-side handler that processes the requests from the Content Delivery Server Digital Rights Management (CDS DRM) Agent that is running in a protected MIDlet. The messages are organized by the message number.
[cds.DRM] WARNING <0000> Device Time is not consistent with Server Time for ticket=ticket-ID. Device Time = device-timeServer Time = server-time
Description. When validating usage rights, the CDS DRM Agent sent the device's current time and this time is not consistent with the server's current time.
Action. The subscriber receives a message requesting that the device's time be fixed. If the device's time is correct, the server's time might need to be fixed.
[cds.DRM] SEVERE <0001> Sending purchase error as response: message
Description. An error was encountered while processing a purchase request from a CDS DRM Agent. message provides more information on the exception that occurred.
Action. Have the subscriber retry the action. If the error persists, check the exception detail to determine the root cause of the error, then contact customer support for troubleshooting help.
[cds.DRM] SEVERE <0002> Sending renew per period error as response: message
Description. An error was encountered while processing a period renewal request from a CDS DRM Agent. message provides more information on the exception that occurred.
Action. Have the subscriber retry the action. If the error persists, check the exception detail to determine the root cause of the error, then contact customer support for troubleshooting help.
[cds.DRM] SEVERE <0003> Sending renew per use error as response: message
Description. An error was encountered while processing a usage renewal request from a CDS DRM Agent. message provides more information on the exception that occurred.
Action. Have the subscriber retry the action. If the error persists, check the exception detail to determine the cause of the error, then contact customer support for troubleshooting help.
[cds.DRM] WARNING <0004> Unknown form selection for ticket=ticketID: |form|
Description. An unexpected form selection, form, was encountered while processing a request from a CDS DRM Agent.
Action. Have the subscriber retry their action. If the warning persists, record the warning and contact customer support for troubleshooting help.
[cds.DRM] SEVERE <0005> Sending error as response: message
Description. An error was encountered while processing a request from a CDS DRM Agent. message provides more information on the exception that occurred.
Action. Have the subscriber retry the action. If the error persists, check the exception detail to determine the cause of the error, then contact customer support for troubleshooting help.
[cds.DRM] SEVERE <0050> Could not determine the Billing Response for ticket=ticket-ID
Description. The state of the given ticket cannot be determined. The ticket may be corrupted. ticket-ID identifies the ticket associated with the request.
Action. Contact customer support for troubleshooting help.
[cds.DRM] SEVERE <0051> Purchase authorization failed.
Description. The integrated billing system declined the authorization for a purchase request from a CDS DRM Agent.
Action. Have the subscriber retry the action. If the error persists, contact customer support for troubleshooting help.
[cds.DRM] SEVERE <0052> Purchase authorization failed.
Description. The integrated billing system declined the authorization for a period renewal request from a CDS DRM Agent.
Action. Have the subscriber retry the action. If the error persists, contact customer support for troubleshooting help.
[cds.DRM] SEVERE <0053> Purchase authorization failed.
Description. The integrated billing system declined the authorization for a usage renewal request from a CDS DRM Agent.
Action. Have the subscriber retry the action. If the error persists, contact customer support for troubleshooting help.
The following messages are issued when problems occur during bulk content operations performed in the administration consoles. The messages are generally followed by the report of an exception and a stack trace.
[cds.Admin] SEVERE: <0803> Error during copying a category
Description. Copying a category failed.
Action. See the log for information on the exception that occurred.
[cds.Admin] SEVERE: <0804> Error during moving a category
Description. Moving a category failed.
Action. See the log for information on the exception that occurred.
[cds.Admin] SEVERE: <0805> Error during copying a resource class
Description. Copying an individual resource class failed.
Action. See the log for information on the exception that occurred.
[cds.Admin] SEVERE: <0806> Error during moving a resource class
Description. Moving an individual resource class failed.
Action. See the log for information on the exception that occurred.
[cds.Admin] SEVERE: <0815> CM Bulk operation error: message
Description. Catalog server could not process the bulk content operation.
Action. See the message provided with the error and see the log for information on the exception that occurred.
[cds.Admin] SEVERE: <0816> VM Bulk operation error: message
Description. The Vending Manager could not process the bulk content operation.
Action. See the message provided with the error and see the log for information on the exception that occurred.
[cds.Admin] SEVERE: <0817> CM Bulk operation unsupported
Description. The keyword for the bulk operation was not recognized. The most probable reason is that an incorrect URL was passed to the Catalog Manager.
Action. Check the source that generated the URL to ensure that the correct URL is used.
[cds.Admin] SEVERE: <0818> VM Bulk operation unsupported
Description. The keyword for the bulk operation was not recognized. The most probable reason is that an incorrect URL was passed to the Vending Manager.
Action. Check the source that generated the URL to ensure that the correct URL is used.
[cds.Admin] SEVERE: Error committing transaction
Description. Database transaction failed to commit during bulk stocking operation.
Action. See the log for information on the exception that occurred.
[cds.Admin] SEVERE: Error enqueueing task
Description. The stocking task could not be enqueued.
Action. See the log for information on the exception that occurred.
[cds.Admin] SEVERE: Error persisting stopped stocking task
Description. Information about an unfinished stocking task could not be saved.
Action. Verify that the database server can be reached. See the log for information on the exception that occurred.
[cds.Admin] SEVERE: Error deleting stocking task entity
Description. Information about a finished or deleted stocking task could not be removed.
Action. Verify that the database server can be reached. See the log for information on the exception that occurred.
[cds.Admin] SEVERE: Unable to create new transaction
Description. Bulk stocking failed to create database transaction.
Action. Verify that the database server can be reached and is accepting connections. See the log for information on the exception that occurred.
[cds.Admin] SEVERE: Stocker thread was terminated
Description. Bulk stocking task terminated unexpectedly.
Action. Verify that the server is running. See the log for information on the exception that occurred.
[cds.Admin] SEVERE: Error committing transaction on thread termination
Description. The transaction could not be committed.
Action. Verify that the server is running and the database server can be reached. See the log for information on the exception that occurred.
The following messages are issued by the Vending Manager if errors occur while stocking or updating content.
[cds.Admin] SEVERE <0912> Error while updating metadata of content with resource class Id class-ID
Description. An exception occurred when metadata for the content identified by class-ID was updated. The update failed.
Action. Contact customer support for troubleshooting help.
[cds.Admin] SEVERE <0913> Error while updating pricing model of content with resource class Id class-ID
Description. An exception occurred when the pricing model for the content identified by class-ID was updated. The update failed.
Action. Contact customer support for troubleshooting help.
[cds.Admin] SEVERE <0914> Error while updating metadata and pricing model of content with resource class Id class-ID
Description. An exception occurred when the metadata and pricing model for the content identified by class-ID was updated. The update failed.T
Action. Contact customer support for troubleshooting help.
[cds.Admin] SEVERE <0915> Error while stocking content with resource class Id class-ID
Description. An exception occurred when stocking the content identified by class-ID. The stocking operation failed.
Action. Contact customer support for troubleshooting help.
[cds.Admin] SEVERE <0916> Error while stocking edition edition-ID of content with resource class Id class-ID
Description. An exception occurred when stocking the edition identified by edition-ID of the content identified by class-ID. The stocking operation failed.
Action. Contact customer support for troubleshooting help.
[cds.Admin] SEVERE <0917> Error while auto-stocking content with resource class Id class-ID
Description. An exception occurred when auto-stocking the content identified by class-ID. The auto-stocking operation failed.
Action. Contact customer support for troubleshooting help.
[cds.Admin] SEVERE <0918> Error while auto-stocking edition edition-ID of content with resource class Id class-ID
Description. An exception occurred when auto-stocking the edition identified by edition-ID of the content identified by class-ID. The auto-stocking operation failed.
Action. Contact customer support for troubleshooting help.
The following messages are issued by the other areas of the Content Delivery Server. The messages are organized alphabetically by the module that issued the message.
[cds.DBPoolManager] WARN <0000> Removing failed connection: oracle.jdbc.driver.OracleConnection@connectionId[Task] ERROR <0004> permission denied: permissionError
Description. Database connection failure occurred. connectionId identifies the connection that failed.
Action. Make sure that Oracle is running and is accessible by the Content Delivery Server. Make sure that your database configuration file contains the correct values. See Appendix A, "Deployment Configuration File," in the Sun Java System Content Delivery Server Installation Guide for information on this file.
[cds.Foundation] SEVERE <0614> JMS ERROR
Description. The Content Delivery Server was not started correctly or someone shut down the Content Delivery Server while the Messaging Service is running.
Action. Make sure that the Content Delivery Server is started correctly. Also, make sure that the deployment configuration (.cfg) file contains the correct values for the JMS properties.
[cds.Foundation] ERROR JMS Error
Description. A javax.jms.JMXException has occurred.
Action. This error occurs for a number of reasons. See http://java.sun.com/j2ee/1.4/docs/api/javax/jms/JMSException.html for details about this exception. Review Section 3.1.5, "Set Up the Application Server," in the Sun Java System Content Delivery Server Installation Guide to make sure that JMS is set up correctly.
[cds.Root] ERROR Error while Sending MMS Push message to the JMS queue {exception message}
Description. An exception occurred while sending an MMS push message to the the JMS queue. This happens for a number of reasons, such as JMS is down, the requested JMS queue destination is invalid, the format of the message is invalid, or JMS does not support the requested operation.
Action. See http://java.sun.com/j2ee/1.4/docs/api/javax/jms/QueueSender.html#send(javax.jms.Message) for details on the types of exceptions that can occur. Verify that JMS is running, that the Content Delivery Server-related queues exist and are receiving messages, and that the JMS API matches what is supported by the JMS instance.
[cds.Root] ERROR <0018> Could not get authenticated user: message
Description. A user attempted to log in and the Content Delivery Server could not authorize the user. message provides more information to help determine the cause of the error.
Action. Make sure that the UserManager defined in the security.config file is working properly, then retry the operation.
| Sun Java System Content Delivery Server Error Messages | 819-3214-10 |
|
Copyright © 2005, Sun Microsystems, Inc. All Rights Reserved.