Forum Problems Installing LAMS: Intel mac - LAMS fails startup.


 
You may request notification for Intel mac - LAMS fails startup..
Search: 

1: Intel mac - LAMS fails startup.
06/20/06 06:18 PM
[ Reply | Forward ]
Hi all.

Macbook Pro - looking at LAMS (noob) on a Mac Book Pro. Installer said LAMS was successfully installed, however fails on startup. When trying via terminal I get the following error(s)

10:05:04,755 INFO [Server] JBoss Release: JBoss-3.0.8 CVSTag=JBoss_3_0_8
10:05:04,763 INFO [Server] Home Dir: /usr/local/lams-1.0.2/jboss
10:05:04,763 INFO [Server] Home URL: file:/usr/local/lams-1.0.2/jboss/
10:05:04,764 INFO [Server] Library URL: file:/usr/local/lams-1.0.2/jboss/lib/
10:05:04,765 INFO [Server] Patch URL: null
10:05:04,765 INFO [Server] Server Name: default
10:05:04,766 INFO [Server] Server Home Dir: /usr/local/lams-1.0.2/jboss/server/default
10:05:04,766 INFO [Server] Server Home URL: file:/usr/local/lams-1.0.2/jboss/server/default/
10:05:04,766 INFO [Server] Server Data Dir: /usr/local/lams-1.0.2/jboss/server/default/db
10:05:04,766 INFO [Server] Server Temp Dir: /usr/local/lams-1.0.2/jboss/server/default/tmp
10:05:04,773 INFO [Server] Server Config URL: file:/usr/local/lams-1.0.2/jboss/server/default/conf/
10:05:04,774 INFO [Server] Server Library URL: file:/usr/local/lams-1.0.2/jboss/server/default/lib/
10:05:04,774 INFO [Server] Root Deployemnt Filename: jboss-service.xml
10:05:04,776 INFO [Server] Starting General Purpose Architecture (GPA)...
10:05:04,797 ERROR [Server] start failed
javax.management.InstanceNotFoundException: JMImplementation:service=LoaderRepository,name=Default
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1010)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:804)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at org.jboss.system.server.ServerImpl.initBootLibraries(ServerImpl.java:440)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:261)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221)
at org.jboss.Main.boot(Main.java:148)
at org.jboss.Main$1.run(Main.java:381)
at java.lang.Thread.run(Thread.java:613)
javax.management.InstanceNotFoundException: JMImplementation:service=LoaderRepository,name=Default
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1010)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:804)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at org.jboss.system.server.ServerImpl.initBootLibraries(ServerImpl.java:440)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:261)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221)
at org.jboss.Main.boot(Main.java:148)
at org.jboss.Main$1.run(Main.java:381)
at java.lang.Thread.run(Thread.java:613)


I have installed using build 20060116. Any help appreciated.
thanks,
Matt

Posted by Matt Hitchcock

2: Re: Intel mac - LAMS fails startup.
In response to 1 06/20/06 07:32 PM
[ Reply | Forward ]
I think your Java version is 1.5, LAMS 1.0 runs on 1.4.2. You can check your java version by typing 'java -version' in a Terminal application.

I'm not too familiar with Mac systems, but I think you may be able to install something called Xcode to get Java 1.4.2 on your system... also, because you have an Intel Mac, you might be able to use Sun's Linux installer for Java 1.4.2 SDK if you're familiar with the command line (http://java.sun.com/j2se/1.4.2/download.html).

Posted by Jun-Dir Liew

3: Re: Re: Intel mac - LAMS fails startup.
In response to 2 06/20/06 07:58 PM
[ Reply | Forward ]
Thanks for prompt response.
I have XCode installed - and yes my Java version is Java 2 Runtime Environment, Standard Edition, build 1.5.0_06-112

hmmmm - will look into issues with downgrading my Java environment. I assume Java is similar to php, apache etc where you should only (in normal circumstances) run a single instance?

Posted by Matt Hitchcock

4: Re: Re: Re: Intel mac - LAMS fails startup.
In response to 3 06/20/06 08:18 PM
[ Reply | Forward ]
Hi Matt,

Downgrading your JAVA might not be a good idea, given that the LAMS v2.0 beta is coming out at the end of this month! :-)

If you give me a day or two, I can check whether I can get java 1.4.2 and java 1.5 to coexist in a mac without causing major pain.

Thanks,

Ernie

Posted by Ernie Ghiglione

5: Re: Re: Re: Intel mac - LAMS fails startup.
In response to 3 06/20/06 08:25 PM
[ Reply | Forward ]
Matt,

Can you have a look at this directory on your mac and let me know what versions are listed:

/System/Library/Frameworks/JavaVM.framework/Versions/

I have a powerbook (PowerPC) and it seems that I have both 1.4.2 and 1.5 living together. However, I haven't run my LAMS 1.0.x in it for a long time, but it seems that it might be possible if I ensure that my LAMS 1.0.x is running java from the correct version 1.4.2.

Let me run some tests and get back to you.

Ernie

Posted by Ernie Ghiglione

6: Re: Re: Re: Intel mac - LAMS fails startup.
In response to 3 06/20/06 08:27 PM
[ Reply | Forward ]
BTW, this is what I have in my /System/Library/Frameworks/JavaVM.framework/Versions 

ernieg:/System/Library/Frameworks/JavaVM.framework/Versions ernieg$ ls -l
total 40
lrwxr-xr-x   1 root  wheel    5 May 31 12:58 1.3 -> 1.3.1
drwxr-xr-x   8 root  wheel  272 Apr 28  2005 1.3.1
lrwxr-xr-x   1 root  wheel    5 Sep 28  2005 1.4 -> 1.4.2
drwxr-xr-x   8 root  wheel  272 Apr 28  2005 1.4.2
lrwxr-xr-x   1 root  wheel    5 May 31 12:58 1.5 -> 1.5.0
drwxr-xr-x   8 root  wheel  272 May 31 12:58 1.5.0
drwxr-xr-x   6 root  wheel  204 May 31 12:59 A
lrwxr-xr-x   1 root  wheel    1 May 31 12:58 Current -> A
lrwxr-xr-x   1 root  wheel    5 May 31 12:58 CurrentJDK -> 1.5.0   
ernieg:/System/Library/Frameworks/JavaVM.framework/Versions ernieg$ 

Posted by Ernie Ghiglione

7: Re: Intel mac - LAMS fails startup.
In response to 6 06/20/06 09:04 PM
[ Reply | Forward ]
Ernie,

cheers on the speedy communication. Great stuff.

my results are not dissimilar

total 40
lrwxr-xr-x 1 root wheel 5 Jun 6 23:54 1.3 -> 1.3.1
drwxr-xr-x 8 root wheel 272 Apr 8 07:40 1.3.1
lrwxr-xr-x 1 root wheel 5 Apr 8 07:40 1.4 -> 1.4.2
drwxr-xr-x 8 root wheel 272 Apr 8 07:40 1.4.2
lrwxr-xr-x 1 root wheel 5 Jun 6 23:54 1.5 -> 1.5.0
drwxr-xr-x 8 root wheel 272 Apr 8 07:40 1.5.0
drwxr-xr-x 5 root wheel 170 Jun 6 23:57 A
lrwxr-xr-x 1 root wheel 1 Jun 6 23:54 Current -> A
lrwxr-xr-x 1 root wheel 5 Jun 6 23:54 CurrentJDK -> 1.5.0

given the symlinks, currentJDK aliases 1.5.0

maybe if currentJDK were to alias 1.4.2 but unsure i want to go there just yet given other dependencies.

cheers,
Matt

Posted by Matt Hitchcock

8: Re: Intel mac - LAMS fails startup.
In response to 7 06/20/06 09:26 PM
[ Reply | Forward ]
Changing symlink (ln -sf 1.4.2 currentJDK) made no difference to startup of LAMS. No worries - no need for speed. Looking forward to getting more involved as time goes on.

thanks for the help. If you have any other ideas happy to hear them, but am perfectly happy to wait a little for v2 beta as you suggest.

:-)
Matt

Posted by Matt Hitchcock

9: Re: Re: Intel mac - LAMS fails startup.
In response to 8 06/20/06 10:04 PM
[ Reply | Forward ]
I think it will take a bit more than just the ln -sf, as the JAVA_HOME paths might be different. Let me have a poke with it to see if I can get this to work. It should be possible to add a few variables to the LAMS 1.0.x start script to declare the JAVA_* variables to be the 1.4.2 ones... let me play with it and see how I go. Give me a few days as we are going mad with getting LAMS 2.0 beta out of the door by the end of next week.

Cheers,

Ernie

Posted by Ernie Ghiglione

10: Re: Re: Re: Intel mac - LAMS fails startup.
In response to 9 06/20/06 10:20 PM
[ Reply | Forward ]
Ernie,

greatly appreciated but please no need. I fully appreciate what it's like getting software out the door. Knowing that v2.0 is imminent I am more than happy to wait.

:-)
Matt

Posted by Matt Hitchcock

11: Re: Re: Re: Re: Intel mac - LAMS fails startup.
In response to 10 06/22/06 12:31 AM
[ Reply | Forward ]
Matt,

On the Mac OSX Java FAQ page, I found out this:

2: Does Mac OS X support multiple J2SE versions on a single OS installation?

Mac OS X Tiger currently supports three major JDK versions (1.3.1, 1.4.2, 1.5.0). The standard command-line commands such as java and javac typically use the latest available version (1.5 in the case of Mac OS X Tiger). Apple developer tools such as Jar Bundler and Xcode both allow you to request a minimum or specific Java version for double-clickable apps to use. Please see the Java 1.4 Info.plist Dictionary Keys documentation for details on how this is done. End users can specify which version of Java should be used for applications and Applets using the Java Preferences Application located at /Applications/Utilities/Java/J2SE 5.0/Java Preferences.app.

That should do the trick. Let us know how it goes.

Thanks,

Ernie

Posted by Ernie Ghiglione

12: Re: Intel mac - LAMS fails startup.
In response to 11 06/22/06 03:38 AM
[ Reply | Forward ]
Starting LAMS Server 1.0.2...
================================================================================

JBoss Bootstrap Environment

JBOSS_HOME: /usr/local/lams-1.0.2/jboss

JAVA: java

JAVA_OPTS: -Dprogram.name=startlams.sh

CLASSPATH: /usr/local/lams-1.0.2/jboss/bin/run.jar:/lib/tools.jar

================================================================================

19:33:31,694 INFO [Server] JBoss Release: JBoss-3.0.8 CVSTag=JBoss_3_0_8
19:33:31,702 INFO [Server] Home Dir: /usr/local/lams-1.0.2/jboss
19:33:31,703 INFO [Server] Home URL: file:/usr/local/lams-1.0.2/jboss/
19:33:31,703 INFO [Server] Library URL: file:/usr/local/lams-1.0.2/jboss/lib/
19:33:31,704 INFO [Server] Patch URL: null
19:33:31,705 INFO [Server] Server Name: default
19:33:31,705 INFO [Server] Server Home Dir: /usr/local/lams-1.0.2/jboss/server/default
19:33:31,705 INFO [Server] Server Home URL: file:/usr/local/lams-1.0.2/jboss/server/default/
19:33:31,705 INFO [Server] Server Data Dir: /usr/local/lams-1.0.2/jboss/server/default/db
19:33:31,706 INFO [Server] Server Temp Dir: /usr/local/lams-1.0.2/jboss/server/default/tmp
19:33:31,712 INFO [Server] Server Config URL: file:/usr/local/lams-1.0.2/jboss/server/default/conf/
19:33:31,712 INFO [Server] Server Library URL: file:/usr/local/lams-1.0.2/jboss/server/default/lib/
19:33:31,712 INFO [Server] Root Deployemnt Filename: jboss-service.xml
19:33:31,714 INFO [Server] Starting General Purpose Architecture (GPA)...
19:33:31,737 ERROR [Server] start failed
javax.management.InstanceNotFoundException: JMImplementation:service=LoaderRepository,name=Default
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1010)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:804)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at org.jboss.system.server.ServerImpl.initBootLibraries(ServerImpl.java:440)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:261)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221)
at org.jboss.Main.boot(Main.java:148)
at org.jboss.Main$1.run(Main.java:381)
at java.lang.Thread.run(Thread.java:613)
javax.management.InstanceNotFoundException: JMImplementation:service=LoaderRepository,name=Default
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getMBean(DefaultMBeanServerInterceptor.java:1010)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:804)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at org.jboss.system.server.ServerImpl.initBootLibraries(ServerImpl.java:440)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:261)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221)
at org.jboss.Main.boot(Main.java:148)
at org.jboss.Main$1.run(Main.java:381)
at java.lang.Thread.run(Thread.java:613)


:-(

thanks though.
I set the Java Applet Runtime Settings and the Java Application Runtime Settings to use 1.4.2 but still no luck.

Posted by Matt Hitchcock

13: Re: Intel mac - LAMS fails startup.
In response to 1 06/22/06 05:43 PM
[ Reply | Forward ]
Try this -

Edit the file /usr/local/lams-1.0.2/etc/lams.conf

Add this line:
export JAVA_HOME=/System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home

It doesn't seem to be the 'proper' way, but it may get you straight to the version of Java that you want to use... see if it works.

Posted by Jun-Dir Liew

14: Re: Re: Intel mac - LAMS fails startup.
In response to 13 06/25/06 12:00 AM
[ Reply | Forward ]
many thnx - has certainly made a difference in something. The startup gets a lot further but ends with a webpage addressed as http://localhost:8080/lams/login.jsp;jsessionid=xxxxxetc

with the following messages. . . . . . .

type Exception report

message

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

exception

org.apache.jasper.JasperException
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:254)
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:80)
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:552)

root cause

javax.servlet.ServletException
at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:536)
at org.apache.jsp.login_jsp._jspService(login_jsp.java:260)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:210)
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:80)
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:552)

Posted by Matt Hitchcock

15: Re: Intel mac - LAMS fails startup.
In response to 1 06/27/06 08:46 AM
[ Reply | Forward ]
and in command line . . .
(purely for future reference and fyi)
looking forward to v2.0
:-)

Last packet sent to the server was 1 ms ago.))), ObjectName: jboss.j2ee:jndiName=ejb/service/LearnerService,service=EJB
state: FAILED
I Depend On:
Depends On Me: java.rmi.ServerException: Could not bind home; nested exception is:
javax.naming.CommunicationException [Root exception is java.rmi.NoSuchObjectException: object not exported], ObjectName: jboss.j2ee:jndiName=ejb/tool/urlcontent/URLContentService,service=EJB
state: FAILED
I Depend On:
Depends On Me: java.rmi.ServerException: Could not bind home; nested exception is:
javax.naming.CommunicationException [Root exception is java.rmi.NoSuchObjectException: object not exported]]
00:44:07,266 ERROR [STDERR] at org.jboss.deployment.MainDeployer.checkIncompleteDeployments(MainDeployer.java:1134)
00:44:07,266 ERROR [STDERR] at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:594)
00:44:07,266 ERROR [STDERR] at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:575)
00:44:07,266 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
00:44:07,266 ERROR [STDERR] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
00:44:07,266 ERROR [STDERR] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
00:44:07,267 ERROR [STDERR] at java.lang.reflect.Method.invoke(Method.java:324)
00:44:07,267 ERROR [STDERR] at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
00:44:07,267 ERROR [STDERR] at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
00:44:07,267 ERROR [STDERR] at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:324)
00:44:07,267 ERROR [STDERR] at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221)
00:44:07,267 ERROR [STDERR] at org.jboss.Main.boot(Main.java:148)
00:44:07,267 ERROR [STDERR] at org.jboss.Main$1.run(Main.java:381)
00:44:07,267 ERROR [STDERR] at java.lang.Thread.run(Thread.java:552)

Posted by Matt Hitchcock

16: Re: Intel mac - LAMS fails startup.
In response to 1 06/27/06 06:01 PM
[ Reply | Forward ]
That second one seems to be saying that a port is being used;

java.rmi.ServerException: Could not bind home;

Maybe there's an instance of LAMS still running?

Posted by Jun-Dir Liew

17: Re: Intel mac - LAMS fails startup.
In response to 1 08/03/06 07:37 PM
[ Reply | Forward ]
See point no. 3 in this post http://www.lamscommunity.org/dotlrn/clubs/technicalcommunity/forums/message-view?message%5fid=264239#267008

Probably there were some instances of JBoss that were still running on the system after clicking 'stop lams server'.

Posted by Jun-Dir Liew

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