Forum Problems Installing LAMS: Lams fialed to build and start

By: David Binney

[ Reply | Forward ]

Sorry guys,

i forgot to attach the rest of the log files.

Thanks in advance for the help!!

Posted by David Binney

By: Fiona Malikoff

[ Reply | Forward ]

Dave,

Add one file to a posting then when is displays the posting hit back and add another file to the posting. I'm told that's how you get more than one file attached to a posting.

btw - that's one sick build you have, just based on the assemble-ear.log. I'm looking around for some ideas.

Fiona

Posted by Fiona Malikoff

By: David Binney

[ Reply | Forward ]

remainder of log files in .zip

:(

Posted by David Binney

By: Fiona Malikoff

[ Reply | Forward ]

The error

16:22:23,588 ERROR [MainDeployer] could not create deployment: file:/usr/local/jboss-4.0.2/server/default/deploy/local-service.xml
org.jboss.deployment.DeploymentException: No ClassLoaders found for: org.jboss.cache.TreeCache; - nested throwable: (java.lang.ClassNotFoundException: No ClassLoaders found for: org.jboss.cache.TreeCache)

in the server log is due to a missed step in the setup of jboss. You need to copy jgroups.jar and jboss-cache.jar from server/all/lib to server/default/lib. This won't fix the build though - that's a different issue.

Fiona

Posted by Fiona Malikoff

By: Fiona Malikoff

[ Reply | Forward ]

The Java warnings in the build logs are not a problem, but the webdoclet errors are a major problem.

But I've never seen them before so I'm just guessing.

* The XDoclet libraries in lams_build/lib/xdoclet aren't being included on the build path properly. There should be 40 files in that directory.
* In lams_build/common.properties, check that you have set osPropertiesName to "unix".
* In lams_buidl/common.properties, check that you have "sharedlib=../lams_build/lib".
* You mentioned you already had an appserver on the box. Could there be an older copy of xdoclet libraries on the server that is on the classpath, and that could be conflicting with the LAMS version?
* Your version of ANT is too old. I'm using org.apache.ant v1.6.5.

The last one is really clutching at straws but I'm running out of ideas and dinner is ready so I have to go. I'll check back tomorrow.

Fiona

Posted by Fiona Malikoff

By: David Binney

[ Reply | Forward ]

Hi Fiona,

I have made the changes that you mentioned but to no avail. The update was made to the newer version of ant and here are the versions of all the relevant software:

[zzz@dagobah lams_build]$ $JAVA_HOME/bin/java -version
java version "1.6.0"
Java(TM) SE Runtime Environment (build 1.6.0-b105)
Java HotSpot(TM) Client VM (build 1.6.0-b105, mixed mode, sharing)
[zzz@dagobah lams_build]$ $ANT_HOME/bin/ant -version
Apache Ant version 1.7.0 compiled on December 13 2006
[zzz@dagobah lams_build]$ ls -la /usr/local | grep jboss
lrwxrwxrwx 1 root other 22 Jan 9 15:45 jboss -> /usr/local/jboss-4.0.2
drwxrwxr-x 7 zzz other 512 Jan 10 15:01 jboss-4.0.2


This time i have only run the assemble-ear ant task because that seems to be the root of the problem at the moment, and included the log file.

I have also tried adding the path: /lams-server-2.0/lams_build/lib to my path $ENV variable to see if the ant script would pick the jars up, but that did now work either. You might have another idea for a method of punching the jars in manually which will solve this problem?

As for the other application server: I have searched the file system and found no xdoclet jars so this is not the problem as far as i can tell!

Cheers David

Posted by David Binney

By: David Binney

[ Reply | Forward ]

There seems to be some server problems at the moment but the log file was the same as the last assemble-ear.log file with the errors in the xdoclet paths!

PS: will try the log upload again later!

Posted by David Binney

By: David Binney

[ Reply | Forward ]

Hi Fiona,

I have made the changes that you mentioned but to no avail. The update was made to the newer version of ant and here are the versions of all the relevant software:

[zzz@dagobah lams_build]$ $JAVA_HOME/bin/java -version
java version "1.6.0"
Java(TM) SE Runtime Environment (build 1.6.0-b105)
Java HotSpot(TM) Client VM (build 1.6.0-b105, mixed mode, sharing)
[zzz@dagobah lams_build]$ $ANT_HOME/bin/ant -version
Apache Ant version 1.7.0 compiled on December 13 2006
[zzz@dagobah lams_build]$ ls -la /usr/local | grep jboss
lrwxrwxrwx 1 root other 22 Jan 9 15:45 jboss -> /usr/local/jboss-4.0.2
drwxrwxr-x 7 zzz other 512 Jan 10 15:01 jboss-4.0.2


This time i have only run the assemble-ear ant task because that seems to be the root of the problem at the moment, and included the log file.

I have also tried adding the path: /lams-server-2.0/lams_build/lib to my path $ENV variable to see if the ant script would pick the jars up, but that did now work either. You might have another idea for a method of punching the jars in manually which will solve this problem?

As for the other application server: I have searched the file system and found no xdoclet jars so this is not the problem as far as i can tell!

Cheers David

Posted by David Binney

By: David Binney

[ Reply | Forward ]

assemble-ear.log file

Posted by David Binney

By: Fiona Malikoff

[ Reply | Forward ]

David,

Yes, we are having a few problems with the server at the moment.

All I can think of is that there is something wrong in the sharedlib setting in the common.properties file in lams_build. But if that was wrong I'd expect a lot more than just xdoclet to be going wrong.

Can you make a change to the build.xml in the lams_central directory. Find the webdoclet target and add the lines given below between <!-- dump the classpath... --> and <!-- end dump>

<target name="webdoclet" depends="preparedirs">
  <!-- dump the classpath to the log for debugging -->
  <pathconvert pathsep="${line.separator}|  |-- "
      property="echo-classpath"
      refid="project.classpath">
  </pathconvert>
  <echo message="Classpath for lams-central build ${echo-classpath}"/>
  <!-- end dump -->

  <webdoclet destdir="${generated.java}" force="${xdoclet.force}">

I'll attach a copy of a modified build.xml file in case that helps.

Then when the build runs, you should get some output like:
Buildfile: C:\EclipseWorkspace\lams_central\build.xml
preparedirs:
webdoclet:
    [echo] Classpath for lams-central build C:\EclipseWorkspace\lams_build\lib\axis\axis-ant.jar
    [echo] |  |-- C:\EclipseWorkspace\lams_build\lib\axis\axis.jar
    [echo] |  |-- C:\EclipseWorkspace\lams_build\lib\axis\jaxrpc.jar
    [echo] |  |-- C:\EclipseWorkspace\lams_build\lib\axis\saaj.jar
    [echo] |  |-- C:\EclipseWorkspace\lams_build\lib\axis\wsdl4j-1.5.1.jar
    [echo] |  |-- C:\EclipseWorkspace\lams_build\lib\catalina\catalina.jar
.....
    [echo] |  |-- C:\EclipseWorkspace\lams_build\lib\wddx\wddx.jar
    [echo] |  |-- C:\EclipseWorkspace\lams_build\lib\xdoclet\maven-xdoclet-plugin-1.2.3.jar
    [echo] |  |-- C:\EclipseWorkspace\lams_build\lib\xdoclet\xdoclet-1.2.3.jar
......
    [echo] |  |-- C:\jboss-4.0.2\server\default\lib\webcallbackhandler.jar


Could you post this as it should tell me what exactly in the classpath for the webdoclet calls.

Fiona

Posted by Fiona Malikoff

By: Fiona Malikoff

[ Reply | Forward ]

The build.xml for lams_central...

Posted by Fiona Malikoff

By: David Binney

[ Reply | Forward ]

Hey Fiona,

I was just doing a diff on the two build.xml files and noticed that your build.xml is much different to the one that i have from the lams repository, including missing tasks assemble-ear, copyfiles etc.

I have attached my build file and hopefully you could modify that version and let me know if i even have the right version?

Posted by David Binney

By: Fiona Malikoff

[ Reply | Forward ]

David,

Different build file altogether.

Each of the projects in LAMS has their own build file, and the build.xml that is in the lams_build project is a master build file, which then calls the individual project build files.

The build file you have attached is the master build file in lams_build directory.

The build file that I have attached is the build file for the lams_central directory. I've put the debugging in lams_central, rather than in the master build, so that I can get the debugging as close to the problem as possible.

Fiona

Posted by Fiona Malikoff

By: David Binney

[ Reply | Forward ]

Hey Fiona,

I have made the changes to the lams_common/build.xml and it has shown up some more usefull information which should be helpful to you!!

Let me know what you find out?

Posted by David Binney

By: David Binney

[ Reply | Forward ]

file upload..

Posted by David Binney

By: David Binney

[ Reply | Forward ]

another attempt before i just upload the text

Posted by David Binney

By: David Binney

[ Reply | Forward ]

another try :(((

Posted by David Binney

By: Fiona Malikoff

[ Reply | Forward ]

David,

Were stumped on this one at the moment. I've passed it to the team and we reckon it is something to do with the classpath, but we can't see what - that dump of the libraries on the path should be the exact list of libraries that xdoclet gets in the webdoclet command, and there is exactly one copy of the xdoclet libraries that I can see.

One of the guys tried it on a solaris blade, jdk 1.6 and ant 1.7 and it worked fine.

Fiona

Posted by Fiona Malikoff

By: Juanma Dodero

[ Reply | Forward ]

Dear Fiona,

Did you eventually fix this issue.
I have the same problem on:

- Windows Vista Home Premium, SP1
- jboss-4.0.2
- jdk1.6.0_06


I repeated the steps you recommended on the lams_central build.xml file, just to know about the classpath for the webdoclet, and got the attached file.

Posted by Juanma Dodero