||Home | Products | Documents | Downloads | Purchase | Support | Company | Partners | Contact ||
Java EE (Java Enterprise Edition) is the new name for the Java platform. But J2EE (Java 2 Enterprise Edition) is still widely used. In this document J2EE and Java EE are interchangeable.
Java 5 (JDK 1.5)
Super (the client, not the server side) should run under JDK 1.4.x. If you want to use Java 5 (JDK 1.5.x) you need to:
Super (the client) will support JDK 1.5 when J2EE server vendors use it on the server side.
Context sensitive help may not always work at the beginning. This happens when IBM's java is used (Websphere requires IBM's Java).
The version we checked is:
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2) Classic VM (build 1.4.2, J2RE 1.4.2 IBM Windows 32 build cn142sr1w-20041028 (JIT enabled: jitc))
There is an error when MBean notification is used as a trigger of SuperWatchdog. It seems a configuration related error. We hope the open source community will help. The error is:
RemoteException: Could not bind a listener proxy
inJNDI:javax.naming.NoInitialContextException: Need to specify class name in
environment or system property, or as an applet parameter, or in an application
resource file: java.naming.factory.initial
User credentials and administration port: If you explicitly set the Administration port for your cluster (the default configuration does not set this port), you need to log in not as an administrator. For example, a user from Monitors group will be okay. Also you need to use regular listening port, not the administration port on the Connect Panel. When you want to deploy or shutdown server, you need to specify user credentials on the panel in question. You also need to set SSL parameters on file setEnvironment.bat (Windows) or setEnvironment.sh (Unix) as part of the value of JAVA_OPTIONS. For example: -Dweblogic.security.TrustKeyStore=DemoTrust.
You may see error like:
16, 2006 2:51:16 PM EST> <Error> <RMI> <BEA-080001> <Error in Dispatcher
java.lang.AssertionError: Assertion violated.
java.lang.AssertionError: Assertion violated
We believe this is an Weblogic server issue. It looks harmless.
You can ignore the following message when you start Super:
Sep 29, 2005 10:16:10 AM SASRas AUDIT: security.GettingConfig
EasyEJB and SuperStress
You may see bogus error messages like:
SEVERE: javaAccessorNotSet Sep 29, 2005 8:35:25 AM com.ibm.ws.naming.java.javaURLContextFactory SEVERE: javaAccessorNotSet
You can ignore them.
Super fully supports version is 5.0.2, not 5.0.
jBoss 3.2.6 - 4.0.0
If you use configuration "all", you need to deploy ejb-management.jar:
Copy <jboss-home>\server\standard\deploy\management\ejb-management.jar to
The following functions have not been implemented for this release:
Support for jBoss is for version 4.0.0 only. In version 4.0.0, there is a directory server/standard as the configuration for J2EE 1.4 compliance. But we did not find such directory for version 4.0.1. We did not find related services either. So, no support for jBoss 4.0.1. If you can find these required services, Super should work.