Forum Problems Installing LAMS: Problems with LAMS on Ubuntu


 
You may request notification for Problems with LAMS on Ubuntu.
Search: 

1: Problems with LAMS on Ubuntu
02/16/06 08:29 AM
[ Reply | Forward ]
I'm getting pretty desperate with this installation, I have a fresh version of Ubuntu "breezy", I have installed (as recommended) the versions Java SDK 1.4.2, MySQL 4.0.24, and LAMS 1.0.2. Following the "Manual Installation" guide, everything is fine until I run the ./run.sh command. When I reach the statement "15:23:48,935 INFO [NamingHelper] JNDI InitialContext properties:{}", JBoss throws loads of Java errors. I have read through the log files created, but really the only error I can spot must be related to the following line "15:28:23,151 WARN [SessionFactoryObjectFactory] InitialContext did not implement EventContext".

I have tried different version of Java, and also I managed to run Tomcat on its own. I would love some advice on this.

Thanks in advance,

Jeremy

Posted by Jeremy Toussaint

Attachments:
2: Re: Problems with LAMS on Ubuntu
In response to 1 02/16/06 04:47 PM
[ Reply | Forward ]
Hello,

Do the errors refer to 'tiles-definitions'? Have a look at this thread: http://www.lamscommunity.org/dotlrn/clubs/technicalcommunity/forums/message-view?message%5fid=85765

Those errors shouldn't affect LAMS running.

Posted by Jun-Dir Liew

3: Re: Problems with LAMS on Ubuntu
In response to 1 02/17/06 01:01 AM
[ Reply | Forward ]
Actually no, the erros do not seem to refer to 'tiles-definitions'. Despite the errors, I have also checked the URL http://localhost:8080/lams, but it comes up with a 500 error as follows:

type Exception report

message

description The server encountered an internal error () that prevented it from fulfilling this request.

exception

org.apache.jasper.JasperException: Unable to compile class for JSP

An error occurred at line: -1 in the jsp file: null

Generated servlet error:
[javac] Since fork is true, ignoring compiler setting.
[javac] Compiling 1 source file
[javac] Since fork is true, ignoring compiler setting.



at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:130)
at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:293)
at org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:353)
at org.apache.jasper.compiler.Compiler.compile(Compiler.java:370)
at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:473)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:190)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:295)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:241)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:247)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:193)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:256)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.jboss.web.catalina.security.JBossSecurityMgrRealm.invoke(JBossSecurityMgrRealm.java:227)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:551)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.java:246)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2415)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:180)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherValve.java:171)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:172)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.lamsfoundation.ld.security.valve.LoginRequestValve.invoke(LoginRequestValve.java:79)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:509)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:641)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:174)
at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:643)
at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:480)
at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:995)
at org.apache.coyote.tomcat4.CoyoteAdapter.service(CoyoteAdapter.java:223)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:594)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:392)
at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:565)
at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:619)
at java.lang.Thread.run(Thread.java:534)


Finally, I seem to have a recurring error as follows in my terminal:
08:01:17,182 ERROR [Digester] Parse Error at line 47 column -1: Attribute "value" is not declared for element "put".
org.xml.sax.SAXParseException: Attribute "value" is not declared for element "put".

Thanks for your help..

Jeremy

Posted by Jeremy Toussaint

4: Re: Problems with LAMS on Ubuntu
In response to 1 02/20/06 04:39 PM
[ Reply | Forward ]
> Finally, I seem to have a recurring error as follows in my terminal:
08:01:17,182 ERROR [Digester] Parse Error at line 47 column -1: Attribute "value" is not declared for element "put".
org.xml.sax.SAXParseException: Attribute "value" is not declared for element "put".

This one is OK, it's part of the ommitted DTD that's talked about in the other thread I posted above. The element 'put' and attribute 'value' refer to parts of the DTD.

The 500 error you get is strange though. Can I ask what version JDK you are using with LAMS?

Posted by Jun-Dir Liew

Reply to first post on this page
Back to Problems Installing LAMS