Subscribe to Mailing List
Submit requests and bugs
Follow Astroboa on Twitter
Installation Guide
Maven Repository
Get Source code at GITHUB
Building from Sources
API Documentation
Submit a Bug or Request

Troubleshooting

This section provides some answers to common problems users may encounter during installation of Astroboa or during deployment of their own projects which use Astroboa as their content repository.

For more complete view please visit Astroboa JIRA.

  1. When executing the create-new-repository.sh script the database is not automatically created
  2. When executing mvn install I get error 'The svn command failed'
  3. When building Astroboa I get error 'An Ant BuildException has occured: Error starting Sun's native2ascii: '
  4. Eclipse, Maven on Windows (XP, Vista, win7) platforms integration error: "The Maven Integration requires that Eclipse be running in a JDK, because a number of Maven core plugins are using jar from the JDK"
  5. When Astroboa is deployed in a Virtual Machine, the WebConsole does not respond while searcing for objects
  6. When deploying a web application as an exploded war and the application uses Seam (e.g. the Astroboa Console) then JBoss 5.1 enters in an infinite loop redeploying the war again and again
  1. When executing the create-new-repository.sh script, the database is not automatically created

    The create-new-repository.sh script is using ssh to create database corresponding to new repository, so if this fail, invoke the following command from your terminal:

    ssh PostgreSQL_USER@PostgreSQL_HOST CREATEDB_DIR/createdb -E UNICODE NEW_REPOSITORY_ID

    Alternatively, log to Postgres backend as PostgreSQL_USER and run the following command:

    createdb -E UNICODE REPOSITORY_ID
    
    
    
    
  2. When executing mvn install I get error 'The svn command failed'

    When building Astroboa, maven connects to SVN in order to retrieve latest revision. In most cases the above error message is included in:

    Provider message: The svn command failed.
    Command output: svn: This client is too old to work with working copy '.';
    
    please get a newer Subversion client  
    [WARNING] Cannot get the revision information from the scm repository, 
    proceeding with revision of unavailable :  Error!
    
    [INFO] Storing buildNumber: unavailable at timestamp:   
    

    In these cases, you have already installed an SVN client but as the message implies you need to install a new one. If you do so and at the same time want to keep an old one, then you must make sure newer client's commands are located in the PATH before the old ones. If you do not want to install a newer client you may ignore this warning. Build number will have the value unavailable.

  3. When building Astroboa I get error 'An Ant BuildException has occured: Error starting Sun's native2ascii:

    When building Astroboa, modules astroboa-cosole and astroboa-portal-commons use Ant task native2ascii provided by Maven plugin maven-antrun-plugin. This plugin requiries library tools.jar which is provided by Java. However, this library is not always available in Maven's classpath depending on which JVM is used (SUN, or other). It is recommended to add the following dependency to pom.xml:

    <dependency>
         <groupId>com.sun</groupId>
         <artifactId>tools</artifactId>
         <version>1.5.0</version>
         <scope>system</scope>
         <systemPath>${java.home}/../lib/tools.jar</systemPath>
     </dependency>
    

    However, systemPath is not the same for all OSes, let alone the fact that you have to manually change pom.xml. What you should do is to locate tools.jar (inside JAVA home directory under lib dir, JAVA_HOME/lib) and to copy it to MAVEN lib directory (MAVEN_HOME/lib).

  4. Eclipse, Maven on Win platforms: The Maven Integration requires that Eclipse be running in a JDK, because a number of Maven core plugins are using jar from the JDK

    Locate the eclipse.ini file, edit it with your favorite editor and add the following "vm" setting assuming that you have already installed a JDK:

    -vm  C:/Program Files/Java/jdk1.6.0_13/bin/javaw.exe 

    Make sure that -vm and the path to javaw.exe are staying on two different lines.

  5. When Astroboa is deployed in a Virtual Machine, the WebConsole does not respond while searcing for objects
    Edit /opt/jboss-5.1.0.GA/bin/run.conf file, locate the JAVA_OPTS variable assignment and increase the JVM stack size by adding the following option: -Xss2048k

  6. When deploying a web application as an exploded war and the application uses Seam (e.g. the Astroboa Console) then JBoss 5.1 enters in an infinite loop redeploying the war again and again.
    Edit /opt/jboss-5.1.0.GA/server/default/deployers/seam.deployer/META-INF/seam-deployers-jboss-beans.xml and enclose in comments the "SeamMTMacher bean":
    		
    <!-- Seam modification type matcher
    
    <bean class="org.jboss.seam.integration.microcontainer.deployers.SeamTempModificationTypeMatcher" name="SeamMTMatcher">
    
    -->
    Restart JBoss and the exploded wars will be deployed just once! There is possibly a problem with the Seam Deployer and expanded wars. We discovered that the above trick stops the infinite redeployment loop but we do not know whether disabling the "SeamMTMatcher" has any other consequences. So please apply the recommended modification with caution.
 

Last Modified: 01 August 2011
ajax activity image Loading...