The login screen opens, and the user is able to enter login name/password, but then receives the following error: Error authenticating user "XXXX": Web Services "http://XXXX/gsoap/gsoap_ssl.dll?sbminternalservices72" returned an error "org.xml.sax.SAXParseException; Premature end of file ."
When you attempt to login to the Application Repository you see an error "Internal Server Error (500)" Look for the following errors in the followng two files on the SBM server. C:\Program Files\Serena\SBM\Common\jboss405\server\default\log\server.log
Check the Application Repository log (Program Files \Serena\SBM\Common\jboss405\server\default\work\jboss.web\localhost\mashupmgr\ log \mashupmgr. log ) for additional errors. Common errors that we have seen are below:
Only the console. log and Tomcat. log files are being updated. All other Tomcat logs are zero bytes. (You can verify this by stopping Tomcat, deleting all of the Tomcat\log files, then starting Tomcat.) At first glance, the Console.log and Tomcat.log do not give any errors and appear to be fine.
Changed from error to warn in the case if the application does not contain *-sdf.xml/*-sla.xml file . Status check was added before processing response from SDF/SLA servers for deploy/undeploy cases in 10.1.1.1
(1) Instead of every day at midnight you can run this event every 3 months. To change the cron job from a nightly to 3-monthly cycle please open the following file and make the changes as below: In SBM\Common\tomcat\server\default\webapps\mashupmgr\WEB-INF\mashupmgr.cfg changeAR_MONITORING_CRON=0 0 0 * * ?
