Skip to end of metadata
Go to start of metadata

Frequently Asked Questions

Frequently asked questions that pop up in the forum

Locating the log file

Internal application messages are logged to the eHour log file. In case you run into an Internal System Error or any other anomaly, please include the log file in your forum posting.

 

To locate the log file you first have to change directory to the eHour Home Directory. In that directory there's a log directory holding the ehour.log file.

On Windows, how do I start and stop the standalone eHour?

eHour runs as a service and is started everytime Windows boots. To stop or start eHour, go to start -> run -> services.msc.

In the list of services, locate and double click eHour; use the start and stop buttons.

On Windows, how do I prevent standalone eHour from starting automatically?

To prevent eHour from starting automatically when Windows boots, go to start -> run -> services.msc.

In the list of services, locate and double click eHour; change the startup type to "Manual".

How can I change the default port (8000) standalone eHour listens on?

Edit the configuration file and change the ehour.standalone.port value.

On Windows you need to stop eHour before you can edit the configuration file.

 

I have a lot of assignments and this breaks the timesheet form when running with Tomcat (6)

Apache Tomcat by default can handle a limited amount of data being sent by the browser. When you have a large timesheet (50+ assignments), you may be not able to submit hours on the timesheet as Tomcat will throw an error.

You can increase the amount of data Tomcat accepts by adding the following line to /usr/share/tomcat6/conf/catalina.properties:

org.apache.tomcat.util.http.Parameters.MAX_COUNT=10000

eHour is running out of memory

eHour is limited to use a specific amount of memory. In some cases this memory it may use is not enough and you will end up with out of memory errors in your logfile, either: java.lang.OutOfMemoryError: PermGen space or java.lang.OutOfMemoryError: Java heap space.

Luckily it's easy to fix. For the standalone version, navigate to the directory where eHour is installed en open the file ehour.vmoptions. Modify it so that it looks like (order is important!):

-XX:MaxPermSize=128m
-Xmx512m
-DEHOUR_HOME=${installer:sys.installationDir} 

And restart eHour

 

If you deployed the WAR on Tomcat:

Windows: in your Tomcat's bin directory, create a file called setenv.bat with the following contents and restart Tomcat

set JAVA_OPTS=-server -Xmx512m -XX:MaxPermSize=128m

 

Linux: in your Tomcat's bin directory, create a file called setenv.sh and make it executable with chmod 700 setenv.sh. Edit the contents of that file with the following and restart Tomcat:

export JAVA_OPTS="-server -Xmx512m -XX:MaxPermSize=128m"

 

 

 

 

 

  • No labels