Portus Control Centre (Eclipse) issues

Eclipse unexpectedly terminates or throws "java.lang.OutOfMemoryError: PermGen space" errors

Some memory limit defaults imposed by the Java VM might be too low, append the following parameters to (add at the end of) eclipse.ini (located in your top level Eclipse directory:

-XX:PermSize=128m
-XX:MaxPermSize=256m

Missing bundle "org.apache.axis" during Portus Control Centre install

Ensure the "Web, XML and Java EE Development" plugins have been installed from the Eclipse update site.

The Control Centre does not react as expected, functions appear to 'do nothing', but do not give any messages indicating the cause of the misbehaviour.

Usually at least a brief notice about any error is displayed in the Portus Log View.

If the Log View does not give any information, or the information presented is not sufficient to identify the problem, consult the Eclipse Error Log which is accessible from the Eclipse main menu bar via:

• Help
• About Eclipse SDK (this brings up a popup windows)
• Click "Installation Details"
• Select the Configuration tab
• Click "View Error Log"
• Scroll to the bottom of the error log to view information about the last error having occurred.

Possible cause: please check if the JRE (Java Runtime Environment) in use it at least JRE 1.5, earlier levels may cause the behaviour described above !

The Eclipse update manager times out with network errors and does not get access to the update site(s)

When accessing the outside world from an intranet, it may be required to specify a HTTP proxy to Eclipse, this is done as follows:

• Bring up the Preferences dialog by selecting Window -> Preferences from the Eclipse main menu.

• Select the Network Connctions section, specify the Proxy settings as appropriate

  
• Click OK to confirm the settings.

Font issues

The overall font of the Portus Control Centre can be modified by selecting

Window, Preferences, General, Appearance, Colours and Fonts, and the Portus item from this. The Portus Control Centre must be restarted after modifications.

Check Apache's error_log file for error messages from the Portus server.

The default location of the Apache error_log is [SOAG_INST]/apache2/logs/error_log replacing [SOAG_INST] with the location you installed Portus in.

# A fatal error has been detected by the Java Runtime Environment

# A fatal error has been detected by the Java Runtime Environment:
# SIGSEGV (0xb) at pc=0x9bbfc3e3, pid=13780, tid=3062007584
#
# JRE version: 6.0_29-b11
# Java VM: Java HotSpot(TM) Client VM (20.4-b02 mixed mode linux-x86 )
# Problematic frame:
# C [libxul.so+0xb573e3] JSD_GetValueForObject+0x35319
#

Include the following option in the eclipse.ini file

-Dorg.eclipse.swt.browser.XULRunnerPath=/dev/null