|
|
Right Java tools for J2EE, Web Service, Grid and more |
| |Home | Products | Documents | Downloads | Purchase | Support | Company | Partners | Contact | |
You may get this exception on your server STDERR screen. When SuperLogging
is loaded, it tries to read database parameters (driver name, database URL, user name and log database password) from system properties. If the
security policy does not allow this, you will get this error and the system
properties will be ignored. You should modify your server security policy
to allow any one to read system properties (this is allowed by EJB specification
1.1). The script should be like:
permission java.util.PropertyPermission
"*", "read";
You can ignore this error if you use default values.
java.lang.ClassNotFoundException
Common errors are:
Example: java.lang.ClassNotFoundException: com.sun.estore.account.ejb.AccountHome
Java Pet Store demo needs a client jar, which does not come with the
default downloaded package. You need to deploy the application and get the
client jar. Then install the client jar onto Super.
java.lang.InstantiationException
Common error: The class does not have a default constructor (empty argument
list constructor).
javax.naming.NameNotFoundException: Unable to resolve 'examples.CasinoWithLoggingExampleHome'
examples.CasinoWithLoggingExampleHome is the JNDI name of an example. It is a part of example EJBs.
This error means that the example EJB was not deployed.
Common errors:
javax.naming.NameNotFoundException: Unable to resolve 'com.acelet.logging.SuperLoggingHome'
com.acelet.logging.SuperLoggingHome is the JNDI name of SuperLogging EJB. It is a part of dowry EJBs. This error means that SuperLoggingEJB was not deployed.
Common errors:
java.lang.reflection.InvocationTargetException
Errors happened from remote invocation.
Common errors:
This is a general error. If you get this error on error message
window, please click the "Detail" check box on Message to see detailed
information which will give you more clues.
Either you do not have enough privilege or the access is restricted
by the program
Address of local log database in use
The address (port number) of local log database is used by another program. Local log database can not start. Maybe another copy of local log database is running. If so, you can ignore this error.
Local log database is installed when you choose "Simple Install". For
production use, you may want to use a different log database from local log database.
This application already exists. New deployment was ignored.
Application name is not unique
Application name is not unique. Super expects unique application names.
Argument size does not match size of WSDL
The number of arguments does not match the number of parameters in the WSDL.
Attempt to run duplicated task
Attempt to run a task while an instance of the same task is running. A task can be run one at a time.
Authentication error: check your login name and password
Bean name already used by other beans, this one will not be loaded
The name of the bean is already taken, please choose another one. If
you still want to use this name, delete it first.
Can not connect to database.
Common errors:
Check your database, database parameters and try again.
Cannot connect to the registry
Cannot connect to the registry.
Common errors: the information (including user name and password) are not correct.
Can not connect to the application server.
Common errors:
The file can not be copied onto itself. Operating Systems do not allow
this.
Cannot find the datasource. Is the datasource set on your J2EE application server?
Cannot find DataSource for SuperSchedulerServlet
Cannot find DataSource for SuperSchedulerServlet. See SuperSchedulerServlet for detailed information.
Cannot find favorite panel.
Cannot find gateway EJB. Is the EJB deployed?
Can not find jndi.properties. You need to provide it, or re-install Super.
See JNDI properties for information.
Cannot find RegistryObject.
Can not find result record.
Can not find task. The task may be changed or deleted.
Common errors:
Can not find the working task.
Common errors:
Cannot get application name.
Can not get EJB specified by that JNDI name.
Common errors:
Cannot get EJB for the following JNDI names
Can not get EJB specified by that JNDI name.
Note: This is a warning. It may or may not important for you. If the JNDI names are not directly related to your application, you can ignore this error. Some EJBs are internal EJBs for server only, so Super can not get them. EasyEJB is a general tool. It has to report all potential errors.
Common errors:
Cannot get EJB gateway version number
Error occurred when Super tried to get the EJB gateway version. Common problems: the EJB gateway is not deployed properly.
Cannot get home object for JNDI name
The home interface of that JNDI name is not found.
Common errors:
Cannot get information from server
Cannot get information from server. Is the server running?
There is an EJB home object on your server, but Super can not get its JNDI name.
Common errors:
The client jar file (stub) for the EJB is not on CLASSPATH.
Cannot get log database parameters
Cannot get the log database parameters from the server. The log database is probably down.
Cannot get preference data. Is another copy of Super running?
Can not get preference data. Probably another copy of Super is running on the same installation. Only one copy of Super can run on an installation. If you want to run another copy of Super, you need to install another copy.
If there is no other copy of Super running. Reboot your machine. If the problem still exists, you need re-install Super.
A Chore with the same name exists. Please delete the Chore before import.
A Task with the same name exists. Please delete the Task before import.
Cannot init environment delegate
Cannot init environment delegate.
Common errors:
Cannot init report delegate.
Common errors:
Cannot init api object for SuperScheduler.
Common errors:
Cannot init api object for SuperWatchdog.
Common errors:
Envoy bean can not be installed over an existing one. If you need another Envoy, install another Super with the Envoy you want.
Cannot instantiate user defined class
Cannot instantiate user defined class.
Common errors:
Cannot instantiate argument interface
Cannot instantiate argument interface.
Common errors:
Can not list JNDI names.
Common errors:
Cannot show result record. The data is not valid or corrupted.
Cannot start local log database
Can not start the local log database. You can get more information about this error by going to <Super-home>/logDatabase directory and run logDatabase.bat (Windows) or logDatabase.sh (Unix).
The local log database is installed when you choose "Simple Install". For
production use, you may want to use a different log database from the local log database.
Can not start an external process.
The class file must be on CLASSPATH when Super is started.
CLASSPATH is not correct on your client machine when Super starts.
CLASSPATH should include all classes and jar files that the EJB serer requires.
Conflict between data and weekend policy
There is a conflict between data and weekend policy. For example, you choose a task to run on Sunday, but you also choose weekend policy to skip on weekends.
Conflict between period and holiday policy
There is a conflict between period and holiday policy.
For example, if the period is one day, the holiday policy can not be the previous business day.
Cannot create directory.
Common problems:
Can not create shortcut. The main part of installation is done.
You can run Super using super.bat (Windows) or super.sh (Unix).
Usually, this occurs on Windows using national languages other than English. Please contact us.
Database must be selected as log device
The database must be selected as a log device.
Database does not exist.
Data from servlet error.
Data is not valid or in wrong format
Data is not valid or in wrong format.
The copy of your data is stale. Some one, or the system has changed data. Please restart your operation.
Date is not in the future.
The data type is not supported.
Date is not in schedule period
Date is not in specified schedule period.
Common errors:
Date is not valid
Delete default value is not allowed
Delete default value is not allowed.
Error occurred during deployment.
Domain directory is not valid. Missing
The domain home directory is not valid. At least a file or directory is missing.
Do not support object in keyboard input
The input data contains object. It is not supported for keyboard input.
Do not use reserved "localhost"
Please do not use "localhost". Use the machine's real name (hostname).
The new instance uses exactly the same arguments as an existing one. You can either create a new one using different argument values or use an existing one.
The item specified already exists.
Your Stress case is empty.
Data is empty.
The input field can not be empty.
JNDI name is empty, you must provide a valid JNDI name.
There are errors from VM (Virtual Machine) which runs Stress.
Favorite data is invalid. Do you want to delete it?
Favorite data is invalid. You probably want to delete it.
The file does not exists
File not found. Check source path
Your source code must be on CLASSPATH or source path. You can click
on Source Path button of Tail
Panel to add a new path.
The holiday already exists.
The holiday rule already exists.
Holiday set is in use, cannot delete
The holiday set is in use, can not be deleted. Please update the tasks which use this holiday set, then delete.
Holiday set is in use, cannot rename
Holiday set is in use, can not rename. Please update the tasks which use this holiday set, then rename.
Gateway mode does not support schedule Doer
Gateway mode does not support schedule Doer. Schedule Doer can not run in gateway mode. But, Schedule Talker can run in gateway mode. See Direct database connect for details.
installation error. Please reinstall
installation error. Please reinstall.
Installation error. You still can use EasyEJB and SuperStress
An error occurred in installation. This part of installation was not
successful. But you still can use other parts of Super, such as EasyEJB
and SuperStress.
Instance directory is not valid. Missing
The instance directory is not valid. At least a file or directory is missing.
Instance not selected. You must select EJB instance.
The file is not valid.
Common errors:
The log data file is not a valid LimpidLog data file.
Common errors:
The line number for highlighting is invalid.
Possible errors:
The JNDI properties file _jndi.properties is not valid. You have modified it and it is not correct.
Invalid project data, or the project data is for an older version.
The WSDL is invalid.
The data, which is in XML format, is invalid.
Common errors:
The JNDI name not found. Have you set it on the application server?
The job for the task is not set. You need to click on the Browse button to set the job.
License has expired.
The license file is not valid
LimpidLog database validation error
LimpidLog database validation error.
Common errors:
LimpidLog datasource not open yet
LimpidLog datasource not open yet. You need to open a valid project, or open a valid database.
LimpidLog record not found. LimpidDebugger can not find required log record.
LimpidLog versions are not the same
LimpidLog versions are not the same. May or may not work. Please check document for compatibility issues
LimpidLog versions not compatible
LimpidLog versions not compatible. The version of LimpidDebugger is not compatible with the data version from LimpidLog. Check the data version and the required data version.
There was an error when the bean was loaded
The EJB server can not find or load the log database driver.
Common error is:
An Exception was thrown from the log database. You can see detail error message by clicking Detail button.
Common error is:
Mail box not set yet. Please go to the mail menu > System > Mail Box > and open Mail Server Panel to setup email box.
This chore is a member of a Composite chore or a Retry chore. If you want delete it, please delete the composite/retry chore, or remove this chore from the composite/retry chore first.
This task is a member of a Composite task or Retry task. If you want delete it, please delete the composite/retry task, or remove this task from the composite/retry task first.
An error occurred with JMS topic. Please check JMS settings.
You can not mix SuperComponents with different licenses on one installation. You can install a separate copy of Super.
More than one item selected. Please do one item at a time
You should select one item from the list only.
Name contains forbidden chars,
such as: <space> % & * : ; '' ' / \ , . < >
Please do not use these characters in names.
Item name can not have a back quote in it.
The name is already taken. An item with that name exists in the program. The requested operation is ignored.
There is no any break point set.
You have not select a category.
No element for report. You need to define at least one element by clicking Element tab on Report Panel.
The Java file was not compiled with debug information.
There is no initial context. You probably have not connected to the server yet.
No more record in debug session
No more record in debug session.
You should highlight an item from the list before doing this operation.
The project has not been defined yet.
The class does not have public fields (attributes).
The server is not connected.
You are not entitled to open SuperScheduler Doer or SuperWatchdog Doer panels. Your entitlement is based on your role.
The file is not a Java file
This feature is not supported by the server or your license.
Not supported for gateway mode
This feature is not supported for gateway mode.
Not supported for direct database connection
This feature is not supported for direct database connection.
Not supported for Standalone mode
Not supported for Standalone mode.
Not valid LimpidDebugger project file
The project file is not a valid file: either the extension is not ".project", or the format is incorrect.
Number of MBean items is not one
Number of MBean items is more than one. This is not a valid MBean data file.
Number of poke items is not one
Number of poke items must be one. You need to prepare a Poke file which contains one poke item to be used by SuperScheduler.
The password field is empty, please type your password in this
field
Peek Panel tries to peek EJB server, but can not get all data in a
peek cycle. A peek cycle is the period set on Peek
Panel.
When this happens, the monitoring process stops. You can press the Refresh
button to restart the peeking process.
Common problems:
The period that you have chosen is in history, not in the future.
Project exists choose different one
The named project exists. Please choose a different project name. Note: the extension of the project of LimpidDebugger is ".project". If you do not specify, it will be automatically added.
Properties file error. Need reinstall
Properties file error. Need to reinstall Super.
Time out when fetching radar information.
You have not selected a registry.
Restart SuperLoggingLibrary error. Please check log messages
Could not restart SuperLoggingLibrary. Please check log messages for detailed information.
Remote deployment not supported
Remote deployment and undeployment are not supported.
Remote method name not selected. You must select a remote method.
Errors happened when reading report files.
Note: there is a report name and many report file names. The name mentioned in the error message is the report name, not report file name. Report file names are with digital extensions.
Common problems:
Schedule term error. Please click on "Set term" button to set it correctly
Schedule term error. Please click on "Set term" button to set it correctly.
The syntax for scp is not correct.
Common errors:
There is an error when setting logging device.
Server home is not valid. Missing file
The server home directory is not valid. At least one file or directory is missing.
You do not have to have a complete server installation on client machine, but the file structure must be the same as a complete server installation. Super uses some files under server home directory.
The data on the business registry does not have a service binging.
The SSH command you inputted is not valid.
Common errors:
Sub directory is missing. The sub directory is part of the server directories. Either you inputted a wrong directory or the sub directory is deleted. Please input a valid server directory.
SuperLoggingChange topic is not set. This change is not allowed
SuperLoggingChange topic is not set on the server side. This topic change may raise issues if you have more than one application servers. See Scope and Change Scope for detailed information.
An exception was thrown from SuperLogging.
SuperScheduler interval is too small
SuperScheduler interval is too small. See Preference Panel for details.
Common problems:
Task's Repeating attribute must be Standby.
Temporary task exists. A temporary task is created for manually, immediate execution. A temporary task is a short lived task. When the task is done, the temporary task is deleted immediately. You can run the task again when the previous temporary task is done.
In case of error, if a temporary task is not deleted, you can manually delete it.
The name of a temporary task starts with "(TMP)". This is reserved. Do not use the naming pattern with your task names.
There are more than one service binding
There are more than one service binding. For multiple bindings, you need to specify which binding to use. So, to consume this Web Service, you need to do it from either the Service Binding Panel or the Specification Link Panel, not from the Service Panel.
Time is not valid
The process is time out.
Messaging topic not found on the server. Message is part of JMS. It is used to send messaging to the server to change the scope.
Common error:
The Tail Panel tries to get log messages, but can not get all data in a pace cycle. A pace cycle is the period set by Tail Panel. When this happens, the tail process stops. You can press the Refresh button to restart the tail process.
Common problems:
Two passwords are not identical or empty
Two passwords are not identical or empty.
Update failed: the row has been modified
Update failed. The data has been modified after you read it. Your copy of data is stale.
Try to re-read and re-edit again.
Url and adminurl both are empty
Url and adminurl both are empty. You need to input at least one field.
The working task is not running.
Wrong argument interface. The class does not implement com.acelet.s.argument.ArgumentInterface.
Wrong EJB type.
The login name or password is not correct.
The task will never run according to this period.
The task job is wrong, or the job object is corrupted. The easiest way to fix this problem is to delete the task and add a new task.
Too many URLs in super.properties
Too many URLs in super.properties. This facility requires one URL in super.properties.
The user defined class is a wrong type.
You can run either doer or talker, but not both on the same Super installation at the same time
You can run either doer or talker, but not both on the same Super installation at the same time.