Bridge and Java Heap Space
Bridge 7 The JVM automatically assigns a value to the maximum heap space, depending on the actual system resources at Bridge start. You can see the allocated and the actually used memory on the Bridge on the node instance preferences page.
Nevertheless, you can manually assign a value.
Windows
You need to edit the Windows registry.
32-bit | HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Procrun 2.0\E2EConsole-<FQDN>\Parameters\Java |
64-bit | HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Apache Software Foundation\Procrun 2.0\E2EConsole-<FQDN>\Parameters\Java |
Change the following value:
Name | Type | Data (Java heap in MB) |
---|---|---|
JvmMx | REG_DWORD | 0x00000080 (128) |
If this value is not yet present in the registry, you need to add it.
Linux
Edit file <path to your Bridge PROG folder>/bin/e2e_console.sh
and search for a command similar to
echo "\"$JAVA\" -classpath \"$CLASSPATH\" [...] >> $TOMCAT_SCRIPT
This command may look different in future versions of the Bridge.
Add option –Xmx
to this command as follows:
echo "\"$JAVA\" -Xmx192m -classpath \"$CLASSPATH\" [...] >> $TOMCAT_SCRIPT
Value 192m
in above example claims 192 MB of java heap. Add a value that reflects your needs.
Internet Explorer Throws UI Layout Warning
When wanting to access the Bridge with Internet Explorer, a warning similar to the following is displayed: UI Layout Initialization Warning 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 Bridge administration interface is displayed in normal mode: For more information on the compatibility view refer to Introducing Compatibility View in the Microsoft blogs.Problem
The layout-container "DIV/#layout" has no height.Solution
Bridge Certificate Exception
Bridge calls fail (from e.g. the Regression Test Command Line Tool or the Bridge API) and you are getting this error: Check the certificate on your 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.Problem
javax.net.ssl.SSLHandshakeException:
java.security.cert.CertificateException: Certificates does not conform
to algorithm constraints
.Solution