...
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.
Info |
---|
|
Restart the Bridge after you have changed the Java heap space to make your changes have effect. |
Note |
---|
|
After a Bridge update, these changes will be lost and have to be reapplied. |
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.
Panel |
---|
borderColor | #EAA01E |
---|
bgColor | white |
---|
borderWidth | 2 |
---|
borderStyle | solid |
---|
|
LinuxEdit file <path to your Bridge PROG folder>/bin/e2e_console.sh and search for a command similar to Code Block |
---|
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: Code Block |
---|
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. |
Div |
---|
|
Expand |
---|
title | Java Heap Space in Bridge 6 |
---|
| ProblemWhen 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 . SolutionGenerally, 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. | E2E Bridge after you have increased the java heap space to make your changes |
| having Note |
---|
| After a Bridge update, these changes will be lost and have to be reapplied. |
WindowsYou 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 MByte) |
---|
JvmMx | REG_DWORD | 0x00000080 (128) | Panel |
---|
borderColor | #EAA01E |
---|
bgColor | white |
---|
borderWidth | 2 |
---|
borderStyle | solid |
---|
|
| Unix the E2E Bridge PROG folder>/bin/e2e_console.sh and search for -Xmx (e.g. -Xmx192m ).
|
| The value MByte MB of java heap. Increase the value. |
|
|
Internet Explorer Throws UI Layout Warning
Multiexcerpt |
---|
MultiExcerptName | ie_compatibility_view |
---|
|
ProblemWhen wanting to access the E2E Bridge in with Internet Explorer, a warning similar to the following is displayed: UI Layout Initialization Warning The layout-container "DIV/#layout" has no height. SolutionYou 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. |
...
Multiexcerpt |
---|
MultiExcerptName | bridge_certificate_exception |
---|
|
ProblemBridge 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 . SolutionCheck 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. |
...