Page 1 of 1

Unable to Login to SAC Now?

Posted: Wed Aug 17, 2005 12:59 pm
by BigBirdy
For some reasons I can no longer log in to the SAC console. I get the login box, I can type in the corrent id and password and then it just sits there with "Attempting to login" and thats where it stays?

Output from caa.log:

2005-08-17 09:52:40,069 INFO [SOAPDispatcherServlet.init:76] ====> CAA is starting up, standby <====
2005-08-17 09:52:40,320 WARN [CAAConfigLoader.parseConfigDocument:224] No services are configured in this config file
2005-08-17 09:52:40,345 ERROR [CAAConfigLoader.parseComponentNode:244] Service scalix.res, Component disabled has no class defined!
2005-08-17 09:52:40,649 INFO [GuidToServerCache$CleanupThread.run:39] Guid2Server cache is empty. Skipping cleanup
2005-08-17 09:52:40,655 INFO [NotificationEventListener.launch:243] Main Notification Event Listener thread launched...
2005-08-17 09:52:40,658 INFO [NotificationEventListener.launch:246] Notification Worker thread com.scalix.sac.ubermgr.events.NotificationEventListener$WorkerThread-thread-0 launched...
2005-08-17 09:52:40,677 INFO [NotificationEventListener.launch:246] Notification Worker thread com.scalix.sac.ubermgr.events.NotificationEventListener$WorkerThread-thread-1 launched...
2005-08-17 09:52:40,683 INFO [RESInitializer.initNotificationListener:201] RESMonitor-thread Thread launched...
2005-08-17 09:52:40,703 INFO [SOAPDispatcherServlet.init:118] ====> CAA started, you may fire when ready <====

Followup. Scalix-caa_log output as well

Posted: Wed Aug 17, 2005 1:01 pm
by BigBirdy
2005-08-17 09:59:16 StandardWrapperValve[dispatcher]: Servlet.service() for servlet dispatcher threw exception
javax.xml.transform.TransformerFactoryConfigurationError: Provider org.apache.xalan.processor.TransformerFactoryImpl not found
at javax.xml.transform.TransformerFactory.newInstance(Unknown Source)
at com.sun.xml.messaging.saaj.util.transform.EfficientStreamingTransformer.newTransformer(EfficientStreamingTransformer.java:273)
at com.sun.xml.messaging.saaj.soap.EnvelopeFactory.createEnvelope(EnvelopeFactory.java:60)
at com.sun.xml.messaging.saaj.soap.ver1_1.SOAPPart1_1Impl.createEnvelopeFromSource(SOAPPart1_1Impl.java:34)
at com.sun.xml.messaging.saaj.soap.SOAPPartImpl.getEnvelope(SOAPPartImpl.java:82)
at com.scalix.caa.soap.SOAPHelper.getElementValue(SOAPHelper.java:106)
at com.scalix.caa.soap.SOAPHelper.getServiceType(SOAPHelper.java:73)
at com.scalix.caa.soap.SOAPDispatcherServlet.onMessage(SOAPDispatcherServlet.java:161)
at com.scalix.caa.soap.SAAJServlet.doPost(SAAJServlet.java:123)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:237)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:157)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:214)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardContextValve.invokeInternal(StandardContextValve.java:198)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:152)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:137)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:118)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:102)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.core.StandardValveContext.invokeNext(StandardValveContext.java:104)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:520)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:929)
at org.apache.coyote.tomcat5.CoyoteAdapter.service(CoyoteAdapter.java:160)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:799)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:705)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:577)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:683)
at java.lang.Thread.run(Thread.java:595)

Posted: Wed Aug 17, 2005 2:53 pm
by ls-al
I hope this is not the result to my post from yesterday?

Posted: Wed Aug 17, 2005 3:14 pm
by BigBirdy
I didnt see the post, but I have now resolved the problem. Had upgraded to jdk 1.5, and so reverted back to 1.42 and this solved it.

Posted: Thu Nov 03, 2005 5:31 am
by aaronjstanley
So, what is the definitive answer as to the required version of the JDK?

In the release notes for the Scalix C.E. it repeats the warning from the Fedora Core 4 release notes:
Fedora Core 4 users are advised not to use the Java RPM provided by Sun. It contains Provides that conflict with names used in packages provided as part of Fedora Core 4. Because of this, Sun Java might disappear from an installed system during package upgrade operations.
Fedora Core 4 users should use either the RPM from jpackage.org or manually install the Sun Java tarball into /opt. Sun Java 1.5+ is recommended for stability purposes.


However, I have tried to install Scalix with JDK1.5.0_5 and can not open the SAC page.
I read on this site that it absolutely requires a 1.4 version of the java sdk.

Is that so?

What versions of Java are people successfully using? What method are the using to install java on FC4? JPackage? RPM? Manually copying and linking?

Thank you..

Posted: Fri Nov 04, 2005 1:16 pm
by florian
i usually use 1.4.2_09, sdk, downloaded from java.sun.com as a rpm and that has always worked.

starting with the next release of scalix, we'll be supporting 1.5.

-- f.

Posted: Mon Nov 07, 2005 4:10 pm
by aaronjstanley
Success!
I have a successful Scalix deployment on RHEL 3 with the lates RHN patches applied.
I had to install the Sun J2SDK manually, instead of the RPM version.
The RPM version gets overwriten when you do an update from the RHN.
I followed the instructions on the Fedora Forums site for installing java on Fedora Core 4.

Thank you all for your help.

aaron