Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Failed to deploy event map for orchestration "BSGCROrchestrations": Transport error: 404 Error: Not Found
at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:231) at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:443) The ALFEventManager.log in the destination server will throw an error message along the lines of :" Failed to ping the event manager ".
CMS-XML KM-Dim7: How to recover datafiles in the event of 1018-DBIO: connect failed, ora-01092: oracle instance terminated the disconnection forced. error: unable to connect to database
Launch ORACLES SERVER MANAGER . This is usually accomplished by running the program SVRMGRL
CMS-XML KM-Dim9:42907-CM_API_NO_OBJECTError: Failed to construct Content Manager API instance
A detailed control plan report Event logs (Windows OS only) /var/adm/messages file (Unix Only)
CMS-XML Asynch Orchestration doesn't log a failure anywhere if using SSL with a certificate/connection problem to the Target Server
If you use a SSL url for your Event Manager or BPEL server and you have a certificate or connection problem it's extremely hard to troubleshoot because there are no errors logged anywhere for Asynch Orchestrations. The logging you do get doesn't show a problem and it looks like the orch should have run but the event never makes it to the AlfEventManager log. We should either log this connection failure somewhere or at the least make the Test Connect button fail in the Repository when there is an SSL Connection issue.
CMS-XML Event manager log file growing constantly - JMS mail listener issues
If you do not use the email listener option of the Event Manager, you may see message similar to the one below that fill-up the logs and consume disk-space. 2014-02-17 11:36:26,601 ERROR [mailto-Worker-16] [org.apache.axis2.transport.mail.MailTransportListenerEx] [::] -- Error connecting to mail server for address : SBMEventUser@localhost :: Connect failed
CMS-XML During deploy you get this error: "ERROR -- Failed to deploy event map for orchestration...: Access to this endpoint and/or SOAP action is not allowed"
When you try to deploy an application that has an orchestration in it you get the following error in the deploy log and the deploy fails. Deploying to server "Default Event Manager Server " at 11/16/15 2:58 PM. INFO -- Constructing the ALF Event Map(s)...
CMS-XML ALFEventManager.log error if Event Manager email settings are partly configured
- Use SMTP Mail Server for the Event Manager and Application Repository If only the SMTP server is ticked and configured the following error messages are logged in the ALFEventManager.log file 2015-02-25 08:46:58,948 ERROR [mailto-Worker-15] [org.apache.axis2.transport.mail.MailTransportListenerEx] [::] -- Error connecting to mail server for address : SBMEventUser@localhost :: Connect failed
CMS-XML ERROR -- Failed to send notification email to recipient < email address >: Could not connect to SMTP host: localhost, port: 25
Select the Mail Services tab under Standard Settings Select the Application Repository and Event Manager tab Check the box to 'Use SMTP Mail Server for the Event Manager and Application Repository'.
CMS-XML Deploy fails with error: Failed to complete the deployment to server "Default BPEL Server"
Log into the Application Repository In the Environments view, select the environment to which you were trying to deploy. On the Target Servers tab, check the Default BPEL Server URL and the Default Event Manager Server .
CMS-XML org.apache.axis2.transport.mail.SimpleMailListener one or more of Password, User, Host and Protocol are null or empty
This is harmless and it is caused by the failure to enter Password, User, Host or Port number in Configurator > Mail Services > Application Repository and Event Manager . If these parameters are not entered the Event creation via e-mail and Application Repository and Event Manager notifications will not be possible, but no other functionality will be affected.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs