You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

On this Page:

E2E Bridge Throws Java Heap Space Error

Problem

When processing large amounts of data (e.g. when displaying large persistent state objects or selecting large log files), the Bridge runs out of memory and throws an error: ch.e2e.console.soap.SOAPException: Java heap space.

Solution

Generally, you should try to avoid such big amounts of data that will lead to this exception. If this is not possible, a solution is to increase the java heap space.

Restart the E2E Bridge after you have increased the java heap space to make your changes having effect.

After a Bridge update, these changes will be lost and have to be reapplied.

Windows

You need to edit the Windows registry.

32-bitHKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Procrun 2.0\E2EConsole-<FQDN>\Parameters\Java
64-bitHKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Apache Software Foundation\Procrun 2.0\E2EConsole-<FQDN>\Parameters\Java

Change the following value:

NameTypeData (Java heap in MByte)
JvmMxREG_DWORD0x00000080 (128)

Unix

Edit the file <path to your E2E Bridge PROG folder>/bin/e2e_console.sh and search for -Xmx (e.g. -Xmx192m). The value 192m means 192 MByte of java heap. Increase the value.

Internet Explorer Throws UI Layout Warning

Problem

When wanting to access the E2E Bridge in Internet Explorer, a warning similar to the following is displayed:

UI Layout Initialization Warning
The layout-container "DIV/#layout" has no height.

Solution

You are trying to access the Bridge with Internet Explorer in Compatibility View. This is not possible.

Change the Compatibility View Settings of Internet Explorer in such a way that the E2E Bridge administration interface is displayed in normal mode:

  • Uncheck Display intranet sites in Compatibility View, if checked.
  • Remove localhost from the list of websites, that are added to compatibility mode.

For more information on the compatibility view refer to Introducing Compatibility View in the Microsoft blogs.

Bridge Certificate Exception

Problem

Bridge calls fail (from e.g. the Regression Test Command Line Tool or the Bridge API) and you are getting this error: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: Certificates does not conform to algorithm constraints.

Solution

Check the certificate on your E2E Bridge (see Managing the Bridge Certificate). MD5 certificates are deprecated as insecure. If your Bridge still uses MD algorithm (MD5withRSA), you should create a new certificate and restart the Bridge. The new certificate should have algorithm SHA256withRSA.

  • No labels