J2ee logging approach
hi,
i am currently exploring on what approach to use for logging messages for my application. i am using the sun one appserver and stateless ejb's. may i know the best logging approach for ejb's? is there a logging software that would require less coding for logs? thanks.
regards,
andrew
Well, that's not quite fair. With Commons Logging you can use log4j, or jdk1.4 logging, or build your own logger. You're still tied into the Commons Logging system (as much as you're tied into anything) but it's more flexible than log4j specifically.
IIRC you can build adaptors to use other loggers into log4j as well, but it's tricker. Commons Logging makes it easier, but has the overhead of requiring another layer to your configuration.
Like everything it's a tradeoff.
Similar Messages
-
I would like to hear how people have implemented various error
logging approaches in Forte applications.
Forte produces log files automatically for service partitions in
$FORTE_ROOT/log and pops up dialog boxes with uncaught exceptions
for client partitions.
Some of the current problems with the existing Forte error logging
include the famously painfull task of determining which log file
in the $FORTE_ROOT/log pertains to your partition and how to
correctly log client errors.
We have taken the approach of opening our own error file for each
Forte project containing a start class method. All exceptions are
then caught and written to the application error file. This takes
the guess work out of finding the correct error file but raises
some interesting design questions:
1) Should service objects maintain their own error files or should
all problems just be handled as exceptions to be logged by the
calling method. ( In some cases the calling method may not care
that a service object is having a problem. In this case the service
object may try an alternative approach. If the request is finally
filled an error with the service object's functioning has occurred
but not with the calling method's functionality ).
2) Should all error messages be handled by a central message
logger operating as a service object. In this case if various clients
are running on different platforms all error message from an
application are centralized. This saves the effort of checking error
files for the same application on multiple platforms. It also means
that a separate error file does not need to be created for each
client that is instantiated. The message logger service in this
case could be accessed by reference among several applications.
Paul Buchkowski
Merrill Lynch Canada
[email protected]Never mind...my password to access file server contained a character that was not acceptable. Once changed, access restored.
-
The SiteLog_ appl_name .log file in $ORACLE_HOME/j2ee/log is not created
Hello experts,
The SiteLog_<appl_name>.log file in the $ORACLE_HOME/j2ee/log directory stopped to be created 2 days ago.
No errors.
Which reason can be for that? How to enable creating this file?
Regards,
RamHi,
Are there any error when login OWA or ECP?
As Ed mentioned, please post specific information about your question for further troubleshooting.
Besides, please check to see if there is a SharedWebConfig.Config file in the following directories:
<install drive>\Program Files\Microsoft\Exchange Server\V15\ClientAccess
<install drive>\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy
Also, here’s an thread about miss this file in relevant location. For your reference:
https://social.technet.microsoft.com/Forums/office/en-US/6699ad92-701d-4966-b202-90c9be6bf735/exchange-2013-cu6-event-id-1003?forum=exchangesvrgeneral
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support -
J2ee Log is filled all time with "error in opening zip file"
Hi,
When I check the J2ee log in NWA, there is a lot of messages
" java.util.zip.ZipException: error in opening zip file", all time!.
any idea???
thanks in advance.
Detail:
error 2008-11-11 20:44:12:544 java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:111)... [see details]
/System/Server com.sapmarkets.bam.jmxadapter.AbstractLog sap.com/tcwddispwda server-epdesa Server 0 0_36836
error 2008-11-11 20:44:12:404 java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:111)... [see details]
/System/Server com.sapmarkets.bam.jmxadapter.AbstractLog sap.com/tcwddispwda server-epdesa Server 0 0_36836
error 2008-11-11 20:44:12:404 java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:111)... [see details]
/System/Server com.sapmarkets.bam.jmxadapter.AbstractLog sap.com/tcwddispwda server-epdesa Server 0 0_36836
error 2008-11-11 20:44:12:404 java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:111)... [see details]Hi Guys -
I am facing a similar issue while trying to run a VC model. I am using BAPI_SALESORDER_GETLIST with two input fields and some output columns.
The problem here is that when I check the output using this BAPI on the backend system (ABAP), I can see the output. However, with VC it always generated a log in defaultTrace file with the following content;
#1.5 #001E0BC934680032000001D300001A500004633307D8A2D2#1234970732710#com.sapmarkets.bam.jmxadapter.AbstractLog##com.sapmarkets.bam.jmxadapter.AbstractLog#Administrator#57787##n/a##61c79e80fdd011ddcf25001e0bc93468#SAPEngine_Application_Thread[impl:3]_7##0#0#Error#1#/System/Server#Plain###java.util.zip.ZipException: error in opening zip file
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:111)
at java.util.zip.ZipFile.<init>(ZipFile.java:127)
at com.sapmarkets.bam.jmxadapter.AbstractLog.getArchiveInfo(AbstractLog.java:328)
at com.sapmarkets.bam.jmxadapter.AbstractLog.getArchives(AbstractLog.java:454)
at com.sapmarkets.bam.jmxadapter.AbstractLog.getArchives(AbstractLog.java:477)
at sun.reflect.GeneratedMethodAccessor905.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.getAttribute(DefaultMBeanInvoker.java:129)
at javax.management.StandardMBean.getAttribute(StandardMBean.java:229)
at com.sap.pj.jmx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1296)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getAttribute(MBeanServerWrapperInterceptor.java:181)
at com.sap.engine.services.jmx.CompletionInterceptor.getAttribute(CompletionInterceptor.java:309)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getAttribute(BasicMBeanServerInterceptor.java:169)
at com.sap.jmx.provider.ProviderInterceptor.getAttribute(ProviderInterceptor.java:195)
at com.sap.engine.services.jmx.RedirectInterceptor.getAttribute(RedirectInterceptor.java:232)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.getAttribute(MBeanServerSecurityWrapper.java:234)
at com.sap.engine.services.jmx.ClusterInterceptor.getAttribute(ClusterInterceptor.java:522)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)
at com.sapmarkets.bam.logcontroller.jmx.LogControllerFacade.getLogInfo(LogControllerFacade.java:227)
at com.sapmarkets.bam.logcontroller.jmx.LogControllerFacade.getLogInfosWithPattern(LogControllerFacade.java:193)
at com.sapmarkets.bam.logcontroller.jmx.LogControllerFacade.getLogInfos(LogControllerFacade.java:174)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.getAttribute(DefaultMBeanInvoker.java:129)
at javax.management.StandardMBean.getAttribute(StandardMBean.java:229)
at com.sap.pj.jmx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:1296)
at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.getAttribute(MBeanServerWrapperInterceptor.java:181)
at com.sap.engine.services.jmx.CompletionInterceptor.getAttribute(CompletionInterceptor.java:309)
at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.getAttribute(BasicMBeanServerInterceptor.java:169)
at com.sap.jmx.provider.ProviderInterceptor.getAttribute(ProviderInterceptor.java:195)
at com.sap.engine.services.jmx.RedirectInterceptor.getAttribute(RedirectInterceptor.java:232)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)
at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.getAttribute(MBeanServerSecurityWrapper.java:234)
at com.sap.engine.services.jmx.ClusterInterceptor.getAttribute(ClusterInterceptor.java:522)
at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.getAttribute(MBeanServerInterceptorChain.java:124)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sapmarkets.bam.jmx.connector.AbstractLVServer.invoke(AbstractLVServer.java:183)
at sun.reflect.GeneratedMethodAccessor470.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.services.rmi_p4.P4DynamicSkeleton.dispatch(P4DynamicSkeleton.java:161)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
An error was returned from the back-end system: [V4213] No data found
Do you have a clue as to why this is happening?
Kind Regards,
Raza. -
WD app Deployment Error - Where can we find J2ee log file for linux install
Hi,
I have a problem with deploying a web dynpro application. There are no errors before deployment but when I deploy the application, I get a deployment error with the following description.
I tried to view the trace or log file but we have SAP installed on a linux OS and I do not know where can we see the log or trace file. Please help.
Version:
SAP NW 2004s SP15
NWDS 7.0
xRPM 4.5
Error Description:
May 14, 2008 12:49:50 AM /userOut/deploy (com.sap.ide.eclipse.sdm.threading.DeployThreadManager)
[Thread[Deploy Thread,5,main]] ERROR:
[008]Deployment aborted
Settings
SDM host : BS307
SDM port : 50718
URL to deploy : file:/C:/DOCUME1/SMULLA1/LOCALS~1/Temp/2/temp20045SempraDemo4.5.ear
Result
=> deployment aborted : file:/C:/DOCUME1/SMULLA1/LOCALS~1/Temp/2/temp20045SempraDemo4.5.ear
Aborted: development component 'SempraDemo4.5'/'local'/'LOKAL'/'0.2008.05.14.00.49.36'/'0':Caught exception during application deployment from SAP J2EE Engine's deploy service:java.rmi.RemoteException: Cannot deploy application local/SempraDemo4.5.. Reason: Clusterwide exception: Failed to deploy application local/SempraDemo4.5. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine?; nested exception is: com.sap.engine.services.deploy.container.DeploymentException: Clusterwide exception: Failed to deploy application local/SempraDemo4.5. Check causing exception for details (trace file). Hint: Are all referenced components deployed and available on the engine? (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
Deployment exception : The deployment of at least one item aborted
Edited by: Subramanya Srinivas Mullapudi on May 14, 2008 8:34 AMHi Reza,
Hope you are doing good.
You can set the trace level in the SAP/Java Gui dynamically :
Call transaction SMICM
Choose the menu Goto → Trace Level → Set
In the pop-up window, set the desired level (0,1,2,3)
To switch on an /nSMICM or ICM HTTP trace via command line you should go to
usr\sap\<SID>\<instance_number>\exe directory and run the icmon program with the following command:
icmon◦◦pf=\usr\sap\<SID>\SYS\profile\<SID>_<instance_name>_<HOST>
where you fill in the SID, instance name and host corresponding to your system.
The icmon program is interactive and to increase trace level you must write
"+" and pres enter.To quit you must write "q" and press enter.
The trace will be written◦to the following file: usr\sap\<SID>\<instance_number>\work\dev_icm
Thank you!
Kind Regards,
Hemanth
SAP AGS -
Hi folks,
I am not new to Java, but new to J2EE. I would like to tap your creativity for suggestions for a design approach. Basically, I would like to create a basic JSP/Servlet-based web application that interfaces with an Oracle database. I would like the JSP pages to be almost completely bereft of logic (i.e. use HTML and JSP tags only), with one or two very small snipplets. I would like the servlets to serve as "traffic cops"; that is, state machines that merely redirect to JSPs.
My most pressing question is the following: as with one of my last J2EE projects, I would like to create a 'DatabaseManager' class. This class would basically "wrap" the JDBC calls to establish and maintain a connection, as well as provide convenient methods for querying (i.e. have a method that simply takes in a String represting the query), and returns back a data structure (another class) that wraps the "ResultSet" object (I'll call it "QueryResults", for now).
Should the DatabaseManager and/or QueryResults classes be EJBs?
Thanks!
TomUse of EJbs would depend on the scalability , security of your application.If yours is a very small scale application with 10 - 15 users , EJbs wont be a better choice.However if you need to set variety of security constraints like method level privileges and all , you can go for them.Also complicated transactions should encourage you to use EJbs.
Just a thought.
thx. -
Logging approach for a SOA application
Hi All,
I am working on a design for logging in an integrated application which uses the Oracle SOA suite for a telecom industry solution. I have a BSS system which interacts with the SOA suite to communicate to OSS systems( Network elements in telecom).
I am interested in developing an approach for system logs and audit logs. Since all the system are disparate, can someone suggest a good approach. and references.
Thanks,
PurushottamanAt a high level there are two types of logging. System Logging for technical diagnostic problem and Logging for Auditing / Tracking that involves reporting business data
In any SOA integration its better to differentiate these two entirely different categories of logging to detect and resolve problems within a IT infrastructure.
The next hurdle would be to create a centralized hook for logging (not necessarily a central log ) that can integrate various logging formats by individual system at the same time have minimum dependencies between applications.
Taking into consideration challenges due to disparate services , multiple servers, different interaction schemes, and different types of user activities it helps to rely on ESB. -
Best Logging approach when using ALSB
Hi,
We are exploring various possibilities for logging with ESB (i am using ALSB version
3.0).
I was thinking of using Log4J logging to SysLog (http://wiki.apache.org/logging-log4j/syslog) to capture metrics from different processes.
I have intereactions in my web application (MyWebApp) where i have to fetch some results from a 3rd party web application (MyWebApp2) and i use the ESB to interact between the 2 applications.
I can depict the interections to be of the form depicted below.
Browser --> MyWebApp network request / MyWebApp processing / MyWebApp -ESB network request / ESB processing / ESB-MyWebApp2 network request / MyWebApp2 processing ) -
How can i capture or measure performance profile ?
Among other alternatives
I was thinking if i can use Log4j as a seperate service and can invoke it within the ESB each time i want to log something.
The only concern i have with this is that it might turn out to be a costly operation.
Can Some one provide me a quick reply for this as i need to wrap it a bit quickly.
Cheers
Edited by: user8352312 on Oct 28, 2008 11:40 AMCurrently OSB 10gR3 is out! with nice cool stuff (debugging).
But, you could at logging to your service by applying log actions in your service. This wil generate log information in the log file. Or you could create Alert or Report actions.
Marc
http://orasoa.blogspot.com -
Hi,
The portal went down for an hour and unable to investigate the cause.
However, there is an option of going through .log file.
1. Is there any way to upload this log file and get the analysis?
2. If not, any other solution to identify the cause of the outage?
Regards
KKIf you can access SAP Netweaver Adminidtrator NWA you have the option to view all log files (it highlights the error/warnings) , default trace files, dev_jrrfc.log etc and it also gives you the option to download them all (or based on some filter) in one shot. (staring Netweaver 7.0)
NWA :
http://hostname.dnsname:5<instance num>00/nwa
login as Administrator user (ex J2EE_ADMIN) goto the "Monitoring" Section --> select the type of logs you need from Drop Down --> Apply data source Filter ( if you want for specific Server node or Dispatcher) --> apply filter and you get all the needed files.
At the top you a download button, which lets you download everything. -
J2ee log viewer not functioning
I get the error "BAMConfiguration.xml could not be created" in the j2ee logviewer iview. Anyone know what this is ?
Thanks
JBWhete do you set that path? In SAP note # 655898 it says to
If you need a different directory (or on UNIX), you will need a workaround: create a Page (or add to an existing one), an iView from the Portal Archive. Select "com.sap.portal.logviewer620" and follow the next instructions. Use the "logviewer620" profile (not default). Afterwards edit the properties of the iView like setting the used J2EE server etc. and especially add the attribute "Directory path where BAMConfiguration.xml will reside" (or "bamConfigPath") and set it according to your system (change it from C:\Temp to ...):
How do you add the iview com.sap.portal.logviewer620 to a page, I cannot find it.
Jerey -
Error logging facility and approach
What kind of facilities does Java provide for error logging? I like to be able to globally turn logging on and off, and the logging output can be directly to either the console or log file.
What are some of the general logging approaches java programmers take?Adding to my question:
Some application provide crash reporting capabilities.
How do I do that in Java, and where can I read more
about this subject? Should logging generally be
turned off in production system for to improve
performance?If it is turned on in the same way that it is turned on when it is delivered to QA. -
Logging HTTP and/or SOAP packets in standalong OC4J v10.1.3.2
I'm running OC4J standalone v10.1.3.2 on RH5 linux. I'd like to know how to turn on logging so that all incoming HTTP data can be viewed.
I've basically got a Web Service which is failing to execute from some clients (but not all) due to a SOAP11 version mismatch problem. If I could see the incoming HTTP and/or SOAP request then I could determine where the inconsistency is coming from.
Here's an extract of the returned SOAP error:
<faultcode>env:VersionMismatch</faultcode>
<faultstring>Version Mismatch</faultstring>
<faultactor>http://schemas.xmlsoap.org/soap/actor/next</faultactor>
I've tried editing j2ee-logging.xml and set the logging level to FINEST and TRACE but it's still not logging out the HTTP traffic.
Any ideas welcomed,
ThanksAndy,
Which log files are you looking at? There is a server.log that will be impacted when you set the logging level to FINEST. Since you want to look at http requests, have you considered using Fiddler on the client side? It's pretty verbose but you can see all sorts of info including data posted to forms.
-Michael
PS
URL:
http://www.oracle.com/technology/tech/java/oc4j/htdocs/oc4j-logging-debugging-technote.htmlTake a look at the "Debug Options in OC4J" section. There are several HTTP debugging options listed.
Edited by: Michael F. Hardy on Dec 17, 2008 9:40 AM -
Announcement: Super 5.10 - a suite of J2EE tools
Announcement: Super 5.10 - a suite of J2EE tools.
Super 5.10 comes with:
SuperEnvironment
SuperLogging
SuperPeekPoke
SuperReport
SuperScheduler
SuperStress
SuperWatchdog
and SuperPatrol, as a schedule job.
The evaluation edition can be anonymously downloaded from:
http://www.ACElet.com.
Super is a component based monitor and administration tool
for EJB/J2ee. It provides built-in functionality as well as
extensions, as SuperComponents. Users can install
SuperComponents onto it, or uninstall them from it.
Super has the following functions:
* A J2EE monitor.
* A gateway to J2EE/EJB servers from different vendors.
* A framework holding user defined SuperComponents.
* A full-featured J2EE logging and J2EE tracing tool for centralized,
chronological logging.
* An EJB tool for Peeking and Poking attributes from EJBs.
* An EJB Stress test tool.
* A J2EE global environment tool.
* A J2EE report tool.
* A J2EE Scheduler tool.
* A J2EE Business patrol tool.
It is written entirely in the Java(TM) programming language.
The current version support:
* JOnAS 2.4 and 2.6
* SunONE 7.0
* Universal servers.
* Weblogic 6.1, 7.0 and 8.1
* Websphere 4.0, 5.0.2 and 5.1
* jBoss 3.0 and 3.2
********** What is new:
Version 5.10 January, 2004
Enhancement:
1. SuperScheduler 4.1: Multiple holiday set is an advanced feature now.
This arrangement is convenient for most of users.
2. Support WebSphere 5.1.
Change:
1. SuperScheduler 4.1: Repeating "At specified times" changes from "all
things considered" algorithm to POSIX cron compatible implementation.
Bug fix:
1. SuperScheduler 4.1: Repeating Daily did not consider "Day time saving",
so there were one hour shift in April and October.
Version 5.00 January, 2004
Enhancement:
1. SuperScheduler 4.00: Rewritten SuperScheduler with bug fixes and enhancements,
including: 1. Add task duration. 2. Add Email, JMS Queue and Topic jobs.
3. Add Retry tasks. 4. Add GUI version of Unix cron repeating.
5. Rewritten holiday facilities.
2. SuperWatchdog 1.00 with File, JMS Queue, JMS Topic and User triggers and
the same group of actions as SuperScheduler.
3. SuperLogigng 4.01: Improved Alarm/Alert GUI.
Version 4.00 November, 2003
Enhancement:
1. Support for both native protocol (RMI-IIOP) mode and HTTP/HTTPS
(with/without proxy) protocol mode for SuperEnvironment,
SuperLogging, SuperReport and SuperScheduler.
2. SuperLogging 4.00: tracing can work on both live database and retired database.
3. SuperReport 3.00: works for both live database and retired database.
4. SuperScheduler 3.00: add URL job type (for Servlet/JSP). Add DoerTalker Table
Panel.
Bug fix:
1. SuperScheduler 3.00: Interval change did not take effect until restart Super.
Version 3.00 July, 2003
Enhancement:
1. SuperLoggingLibrary 3.00: New implementation for change scope adding "Smart"
scope,
with enhancements and bug fixes.
2. SuperLoggingLibrary 3.00: Support mail server which requires user name and
password.
Add MenuTreePanel.
3. Improved GUI and document.
4. Add support to WebLogic 8.1.
Bug fix:
1. SuperScheduler 2.0: Fix a bug in FutureView for Hourly and Minutely.
2. SuperScheduler 2.0: Startup should never be reported as missed.
3. SuperScheduler 2.0: Could not reset job for existing task in some situation.
Version 2.20 Jan. 2003
Enhancement:
1. Add desktop and start menu shortcuts for MS-Windows.
2. Add support for SunONE 7, JOnAS 2.6 and jBoss 3.0.
3. SuperLogging 2.40: Add new sendAlarmEmail() method.
4. SuperScheduler 1.40: Add SuperSchedulerEJB for managing when
direct database is not practical; Allow user to choose
favorite logging software; Add Last day as Monthly
repeating attribute.
Change:
1. Change Unusual to PatrolAlarm. The name "Unusual" was misleading.
Bug fix:
1. SuperEnvironment 1.31: Bug fix: if database is broken, could not
open Environment Manager.
2. SuperLogging client 1.52: Annoying exception thrown when you use
JDK 1.4 (the program runs okay).
3. SuperPeekPoke 1.61: Fix bug where input object contains
java.lang.Double and alike.
4. SuperScheduler 1.40: Bug fixes in: Memory leak; Reporting
PatrolAlarm for SuperPatrol; Composite task with members;
Non-scheduled run on other host; Around edges of last
days in Monthly with holiday policy.
Version 2.10 July 2002
Enhancement:
1. SuperScheduler 1.3: Add Future View to check future schedule in
both text and Gantt-chart mode.
2. SuperScheduler 1.3: Add graphic Gantt view for monitoring task's
activities.
3. SuperEnvironment 1.3: uses new graphic package adding print and
preference facilities.
4. SuperPeekPoke 1.6: uses new graphic package adding print and
preference facilities.
5. SuperStress 1.21: uses new graphic package.
Bug fix:
1. SuperStress 1.21: fixed graphic related bugs.
Version 2.01 June 2002
Enhancement:
1. Add options for Look & Feel.
2. Preference is persistent now.
Bug fix:
1. Installation for WebLogic 7.0: extEnv may not be installed on the
right place, so SuperLibrar on the server side was not loaded and
causes other problems.
Version 2.00 June 2002
Enhancement:
1. SuperScheduler 1.2: All copies of SuperScheduler refresh themselves
when any Doer causes things to change.
2. SuperScheduler 1.2: Support default HTML browser for reading HTML document.
3. SuperReport 1.2: Support default HTML browser for reading HTML document.
4. Support WebLogic 7.0.
5. SuperEnvironment 1.21: Database Panel appears when it is necessary.
6. SuperEnvironment 1.21: New SuperEnvironment tour.
Bug fix:
1. WebSphere Envoy did not always list all JNDI names.
Version 1.90 May 2002
Enhancement:
1. Rewritten SuperLogging engine. Add Alarm Email on SuperLogging.
2.Rewritten SuperScheduler allowing multiple Doers. Add support to holiday policy,
effective period. Add Patrol job type as SuperPatrol.
3. Add support for both JOnAS and jBoss.
4. Add more elements on Report criteria.
Change:
1. Now, both left and right mouse clicks are the same on Table Panel: toggle ascend
and descend.
2. New log database.
Bug fix:
1. Alert email should be sent once in the interval, regarding number of servers
in the clustering.
2. Minor bug fixes to make errors handled better on SuperLogging.
3. If withFileInfo or withTimestamp are changed alone, Style Panel did not save
them.
4. Rewritten SuperLogging and SuperScheduler with many bug fixes.
Version 1.80 March 2002
Enhancement:
1. Add new component: SuperScheduler
Bug fix:
1. SuperLogging: Verbose should ignore class registration.
2. SuperLogging-tracing: an exception was thrown if the java class without package
name.
Version 1.70 January 2002
Enhancement:
1. SuperLogging: Scope can dynamically change both for upgrade to downgrade (for
weblogic 6.1, need download an application).
2. Add alias names for log threshold as new Java suggests.
3. New component: SuperReport.
Change:
1. SuperLogging: Log database parameters are specified in a properties file, instead
of EJB's deployment descriptor. It is more convenient and it avoids some potential
problems. No change for development, easier for administration.
Bug fix:
1. Add Source Path Panel now accepts both directory and jar file.
2. Bug in SuperEnvironment example (for version 1.60 only).
Version 1.60 December 2001
Enhancement:
1. SuperPeekPoke and SuperStress can use user defined dynamic argument list.
2. Add timeout parameter to logging access.
3. New installation program with A). Easy install. B). Remote command line install.
4. Support EJB 2.0 for Weblogic 6.1.
5. Support SuperPeekPoke, SuperEnvironment and SuperStress for Websphere 4.0 (SuperLogging
was supported since version 1.5).
Change:
1. Poke: argument list is set at define time, not invoke time.
2. Default log database change to server mode from web server mode, booting performance
to 10-20 times.
Bug fix:
1. If the returned object is null, Peek did not handle it correctly.
2. If the value was too big, TimeSeries chart did not handle it correctly. Now
it can handle up to 1.0E300.
3. Help message was difficult to access in installation program.
4. Source code panel now both highlights and marks the line in question (before
it was only highlight using JDK 1.2, not JDK 1.3).
5. Delete an item on PeekPoke and add a new one generated an error.
Version 1.50 August, 2001
Enhancement:
1. Source code level tracing supports EJB, JSP, java helper and other
programs which are written in native languages (as long as you
write correct log messages in your application).
2. Redress supports JSP now.
3. New installation with full help document: hope it will be easier.
4. Support WebSphere 4.0
Version 1.40 June, 2001
Enhancement:
1. Add SuperEnvironment which is a Kaleidoscope with TableView, TimeSeriesView
and PieView for GlobalProperties.
GlobalProperties is an open source program from Acelet.
2. SuperPeekPoke adds Kaleidoscope with TableView, TimeSeriesView and PieView.
Changes:
1. The structure of log database changed. You need delete old installation and
install everything new.
2. The format of time stamp of SuperLogging changed. It is not locale dependent:
better for report utilities.
3. Time stamp of SuperLogging added machine name: better for clustering environment.
Bug fix:
1. Under JDK 1.3, when you close Trace Panel, the timer may not be stopped and
Style Panel may not show up.
Version 1.30 May, 2001
Enhancement:
1. Add ConnectionPlugin support.
2. Add support for Borland AppServer.
Version 1.20 April, 2001
Enhancement:
1. Redress with option to save a backup file
2. More data validation on Dump Panel.
3. Add uninstall for Super itself.
4. Add Log Database Panel for changing the log database parameters.
5. Register Class: you can type in name or browse on file system.
6. New tour with new examples.
Bug fix:
1. Redress: save file may fail.
2. Install Bean: some may fail due to missing manifest file. Now, it is treated
as foreign beans.
3. Installation: Both installServerSideLibrary and installLogDatabase can be worked
on the original file, do not need copy to a temporary directory anymore.
4. PeekPoke: if there is no stub available, JNDI list would be empty for Weblogic5-6.
Now it pick up all availble ones and give warning messages.
5. Stress: Launch>Save>Cancel generated a null pointer exception.
Changes:
1. installLogDatabase has been changed from .zip file to .jar file.
2. SuperLogging: If the log database is broken, the log methods will not try to
access the log database. It is consistent with the document now.
3. SuperLogging will not read system properties now. You can put log database
parameters in SuperLoggingEJB's deployment descriptor.
Version 1.10 Feb., 2001
Enhancement:
1. Re-written PeekPoke with Save/Restore functions.
2. New SuperComponent: SuperStress for stress test.
3. Set a mark at the highlighted line on<font size=+0> the Source Code
Panel (as a work-a-round for JDK 1.3).</font>
4. Add support for WebLogic 6.0
Bug fix:
1. Uninstall bean does physically delete the jar file now.
2. WebLogic51 Envoy may not always list all JNDI names. This is fixed.
Version 1.00 Oct., 2000
Enhancement:
1. Support Universal server (virtual all EJB servers).
2. Add Lost and Found for JNDI names, in case you need it.
3. JNDI ComboBox is editable now, so you can PeekPoke not listed JNDI name (mainly
for Envoys which do not support JNDI list).
Version 0.90: Sept, 2000
Enhancement:
1. PeekPoke supports arbitrary objects (except for Vector, Hashtable
and alike) as input values.
2. Reworked help documents.
Bug fix:
1. Clicking Cancel button on Pace Panel set 0 to pace. It causes
further time-out.
2. MDI related bugs under JDK 1.3.
Version 0.80: Aug, 2000
Enhancement:
1. With full-featured SuperLogging.
Version 0.72: July, 2000
Bug fix:
1. Ignore unknown objects, so Weblogic5.1 can show JNDI list.
Version 0.71: July, 2000
Enhancement:
1. Re-worked peek algorithm, doing better for concurent use.
2. Add cacellable Wait dialog, showing Super is busy.
3. Add Stop button on Peek Panel.
4. Add undeploy example button.
Bug fix:
1. Deletion on Peek Panel may cause error under JDK 1.3. Now it works for both
1.2 and 1.3
Version 0.70: July, 2000
Enhancement:
1. PeekPoke EJBs without programming.
Bug fix:
1. Did not show many windows under JDK 1.3. Now it works for both 1.2 and 1.3
Changes:
1. All changes are backward compatible, but you may need to recompile monitor
windows defined by you.
Version 0.61: June, 2000
Bug fix:
1. First time if you choose BUFFER as logging device, message will not show.
2. Fixed LoggingPanel related bugs.
Version 0.60: May, 2000
Enhancement:
1. Add DATABASE as a logging device for persistent logging message.
2. Made alertInterval configurable.
3. Made pace for tracing configurable.
Bug fix:
1. Fixed many bugs.
Version 0.51, 0.52 and 0.53: April, 2000
Enhancement:
1. Add support to Weblogic 5.1 (support for Logging/Tracing and
user defined GUI window, not support for regular monitoring).
Bug fix:
1. Context sensitive help is available for most of windows: press F1.
2. Fix installation related problems.
Version 0.50: April, 2000
Enhancement:
1. Use JavaHelp for help system.
2. Add shutdown functionality for J2EE.
3. Add support to Weblogic 4.5 (support for Logging/Tracing and
user defined GUI window, not support for regular monitoring).
Bug fix:
1. Better exception handling for null Application.
Version 0.40: March, 2000
Enhancement:
1.New installation program, solves installation related problems.
2. Installation deploys AceletSuperApp application.
3. Add deploy/undeploy facilities.
4. Add EJB and application lists.
Change:
1.SimpleMonitorInterface: now more simple.
Version 0.30: January, 2000
Enhancement:
1. Add realm support to J2EE
2. Come with installation program: you just install what you want
the first time you run Super.
Version 0.20: January, 2000
Enhancement:
Add support to J2EE Sun-RI.
Change:
1. Replace logging device "file" with "buffer" to be
compliant to EJB 1.1. Your code do not need to change.
Version 0.10: December, 1999
Enhancement:
1. provide SimpleMonitorInterface, so GUI experience is
not necessary for developing most monitoring applications.
2. Sortable table for table based windows by mouse
click (left or right).
Version 0.01 November., 1999:
1. Bug fix: An exception thrown when log file is large.
2. Enhancement: Add tour section in Help information.
Version 0.00: October, 1999
Thanks.i use the adobe creative suite (indesign) for all print
documentation...i use captivate for online tutorials, but from what
i'm hearing the captivate team has been disbanded by adobe and
they've outsourced the 'development' of future releases to india.
buyer beware. -
Super 5.40 - a suite of J2EE tools. It is free.
Announcement:
Super 5.40 - a suite of J2EE tools. It is free.
Standard license can be freely anonymously downloaded.
Super 5.40 comes with:
SuperEnvironment
SuperLogging
SuperPeekPoke
SuperReport
SuperScheduler
SuperStress
SuperWatchdog
and SuperPatrol, as a schedule job.
Most of enhancements of this release are for
SuperScheduler at http://www.acelet.com/super/SuperScheduler/index.html
SuperWatchdog at http://www.acelet.com/super/SuperWatchdog/index.html
Super is a component based monitor and administration tool
for EJB/J2ee. It provides built-in functionality as well as
extensions, as SuperComponents. Users can install
SuperComponents onto it, or uninstall them from it.
Super has the following functions:
* A J2EE monitor.
* A gateway to J2EE/EJB servers from different vendors.
* A framework holding user defined SuperComponents.
* A full-featured J2EE logging and J2EE tracing tool for centralized,
chronological logging.
* An EJB tool for Peeking and Poking attributes from EJBs.
* An EJB Stress test tool.
* A J2EE global environment tool.
* A J2EE report tool.
* A J2EE Scheduler tool.
* A J2EE Business patrol tool.
It is written entirely in the Java(TM) programming language.
The current version support:
* Universal servers.
* Weblogic 8.1
* Websphere 5
It can be anonymously downloaded from:
http://www.ACElet.com.
********** What is new:
Version 5.40 Aug., 2004
1. SuperScheduler 4.40 and SuperWatchdog 1.40: Add new tasks and chores:
scp (Secure CoPy) and ssh (Secure SHell).
2. SuperWatchdog 1.40: fixed bug for slow grow file trigger.
3. SuperLogging 4.11: Add timeout for LogAgent; bug fix: Attribute did
not show correct values for the first call.
4. SuperArch 2.00: Add Deployment and ServerShutdown.
5. Introduce SuperEjbGateway to replace SuperServlets.
Version 5.31 Aug, 2004
1. Bug fix: Triggering missing for SuperWatchdog.
2. Bug fix: Websphere 5.1 license did not working due to new IBM java.
Version 5.30 May, 2004
1. Provides Auto login and Hibernation features with SuperEnvironment 3.1,
SuperPeekPoke 2.1, SuperScheduler 4.30 and SuperWatchdog 1.30.
2. SuperLogging 4.1: Add timeout for client site logging facility LogAgent.
3. SuperScheduler 4.30 and SuperWatchdog 1.30: Add new Deploy (deploy,
redeploy, start, stop, undeploy, ...) jobs.
4. Bug fixes.
Version 5.20 February, 2004
1. Both SuperScheduler 4.20 and SuperWatchdog 1.20 use own alarm facilities.
2. SuperScheduler 4.20: Bug fix: in some conditions, nextRunTime may equals
to lastRunTime and the task will not run anymore (for HypersonicSQL
database only, we did not find this problem for Oracle, nor DB2).
3. SuperLogging 4.02: With better error handling; better Alert/Alarm Email.
Version 5.10 January, 2004
Enhancement:
1. SuperScheduler 4.1: Multiple holiday set is an advanced feature now.
This arrangement is convenient for most of users.
2. Support WebSphere 5.1.
Change:
1. SuperScheduler 4.1: Repeating "At specified times" changes from "all
things considered" algorithm to POSIX cron compatible implementation.
Bug fix:
1. SuperScheduler 4.1: Repeating Daily did not consider "Day time saving",
so there were one hour shift in April and October.
Version 5.00 January, 2004
Enhancement:
1. SuperScheduler 4.00: Rewritten SuperScheduler with bug fixes and enhancements,
including: 1. Add task duration. 2. Add Email, JMS Queue and Topic jobs.
3. Add Retry tasks. 4. Add GUI version of Unix cron repeating.
5. Rewritten holiday facilities.
2. SuperWatchdog 1.00 with File, JMS Queue, JMS Topic and User triggers and
the same group of actions as SuperScheduler.
3. SuperLogigng 4.01: Improved Alarm/Alert GUI.
Version 4.00 November, 2003
Enhancement:
1. Support for both native protocol (RMI-IIOP) mode and HTTP/HTTPS
(with/without proxy) protocol mode for SuperEnvironment,
SuperLogging, SuperReport and SuperScheduler.
2. SuperLogging 4.00: tracing can work on both live database and retired database.
3. SuperReport 3.00: works for both live database and retired database.
4. SuperScheduler 3.00: add URL job type (for Servlet/JSP). Add DoerTalker Table Panel.
Bug fix:
1. SuperScheduler 3.00: Interval change did not take effect until restart Super.
Version 3.00 July, 2003
Enhancement:
1. SuperLoggingLibrary 3.00: New implementation for change scope adding "Smart" scope,
with enhancements and bug fixes.
2. SuperLoggingLibrary 3.00: Support mail server which requires user name and password.
Add MenuTreePanel.
3. Improved GUI and document.
4. Add support to WebLogic 8.1.
Bug fix:
1. SuperScheduler 2.0: Fix a bug in FutureView for Hourly and Minutely.
2. SuperScheduler 2.0: Startup should never be reported as missed.
3. SuperScheduler 2.0: Could not reset job for existing task in some situation.
Version 2.20 Jan. 2003
Enhancement:
1. Add desktop and start menu shortcuts for MS-Windows.
2. Add support for SunONE 7, JOnAS 2.6 and jBoss 3.0.
3. SuperLogging 2.40: Add new sendAlarmEmail() method.
4. SuperScheduler 1.40: Add SuperSchedulerEJB for managing when
direct database is not practical; Allow user to choose
favorite logging software; Add Last day as Monthly
repeating attribute.
Change:
1. Change Unusual to PatrolAlarm. The name "Unusual" was misleading.
Bug fix:
1. SuperEnvironment 1.31: Bug fix: if database is broken, could not
open Environment Manager.
2. SuperLogging client 1.52: Annoying exception thrown when you use
JDK 1.4 (the program runs okay).
3. SuperPeekPoke 1.61: Fix bug where input object contains
java.lang.Double and alike.
4. SuperScheduler 1.40: Bug fixes in: Memory leak; Reporting
PatrolAlarm for SuperPatrol; Composite task with members;
Non-scheduled run on other host; Around edges of last
days in Monthly with holiday policy.
Version 2.10 July 2002
Enhancement:
1. SuperScheduler 1.3: Add Future View to check future schedule in
both text and Gantt-chart mode.
2. SuperScheduler 1.3: Add graphic Gantt view for monitoring task's
activities.
3. SuperEnvironment 1.3: uses new graphic package adding print and
preference facilities.
4. SuperPeekPoke 1.6: uses new graphic package adding print and
preference facilities.
5. SuperStress 1.21: uses new graphic package.
Bug fix:
1. SuperStress 1.21: fixed graphic related bugs.
Version 2.01 June 2002
Enhancement:
1. Add options for Look & Feel.
2. Preference is persistent now.
Bug fix:
1. Installation for WebLogic 7.0: extEnv may not be installed on the
right place, so SuperLibrar on the server side was not loaded and
causes other problems.
Version 2.00 June 2002
Enhancement:
1. SuperScheduler 1.2: All copies of SuperScheduler refresh themselves
when any Doer causes things to change.
2. SuperScheduler 1.2: Support default HTML browser for reading HTML document.
3. SuperReport 1.2: Support default HTML browser for reading HTML document.
4. Support WebLogic 7.0.
5. SuperEnvironment 1.21: Database Panel appears when it is necessary.
6. SuperEnvironment 1.21: New SuperEnvironment tour.
Bug fix:
1. WebSphere Envoy did not always list all JNDI names.
Version 1.90 May 2002
Enhancement:
1. Rewritten SuperLogging engine. Add Alarm Email on SuperLogging.
2.Rewritten SuperScheduler allowing multiple Doers. Add support to holiday policy, effective period. Add Patrol job type as SuperPatrol.
3. Add support for both JOnAS and jBoss.
4. Add more elements on Report criteria.
Change:
1. Now, both left and right mouse clicks are the same on Table Panel: toggle ascend and descend.
2. New log database.
Bug fix:
1. Alert email should be sent once in the interval, regarding number of servers in the clustering.
2. Minor bug fixes to make errors handled better on SuperLogging.
3. If withFileInfo or withTimestamp are changed alone, Style Panel did not save them.
4. Rewritten SuperLogging and SuperScheduler with many bug fixes.
Version 1.80 March 2002
Enhancement:
1. Add new component: SuperScheduler
Bug fix:
1. SuperLogging: Verbose should ignore class registration.
2. SuperLogging-tracing: an exception was thrown if the java class without package name.
Version 1.70 January 2002
Enhancement:
1. SuperLogging: Scope can dynamically change both for upgrade to downgrade (for weblogic 6.1, need download an application).
2. Add alias names for log threshold as new Java suggests.
3. New component: SuperReport.
Change:
1. SuperLogging: Log database parameters are specified in a properties file, instead of EJB's deployment descriptor. It is more convenient and it avoids some potential problems. No change for development, easier for administration.
Bug fix:
1. Add Source Path Panel now accepts both directory and jar file.
2. Bug in SuperEnvironment example (for version 1.60 only).
Version 1.60 December 2001
Enhancement:
1. SuperPeekPoke and SuperStress can use user defined dynamic argument list.
2. Add timeout parameter to logging access.
3. New installation program with A). Easy install. B). Remote command line install.
4. Support EJB 2.0 for Weblogic 6.1.
5. Support SuperPeekPoke, SuperEnvironment and SuperStress for Websphere 4.0 (SuperLogging was supported since version 1.5).
Change:
1. Poke: argument list is set at define time, not invoke time.
2. Default log database change to server mode from web server mode, booting performance to 10-20 times.
Bug fix:
1. If the returned object is null, Peek did not handle it correctly.
2. If the value was too big, TimeSeries chart did not handle it correctly. Now it can handle up to 1.0E300.
3. Help message was difficult to access in installation program.
4. Source code panel now both highlights and marks the line in question (before it was only highlight using JDK 1.2, not JDK 1.3).
5. Delete an item on PeekPoke and add a new one generated an error.
Version 1.50 August, 2001
Enhancement:
1. Source code level tracing supports EJB, JSP, java helper and other
programs which are written in native languages (as long as you
write correct log messages in your application).
2. Redress supports JSP now.
3. New installation with full help document: hope it will be easier.
4. Support WebSphere 4.0
Version 1.40 June, 2001
Enhancement:
1. Add SuperEnvironment which is a Kaleidoscope with TableView, TimeSeriesView and PieView for GlobalProperties.
GlobalProperties is an open source program from Acelet.
2. SuperPeekPoke adds Kaleidoscope with TableView, TimeSeriesView and PieView.
Changes:
1. The structure of log database changed. You need delete old installation and install everything new.
2. The format of time stamp of SuperLogging changed. It is not locale dependent: better for report utilities.
3. Time stamp of SuperLogging added machine name: better for clustering environment.
Bug fix:
1. Under JDK 1.3, when you close Trace Panel, the timer may not be stopped and Style Panel may not show up.
Version 1.30 May, 2001
Enhancement:
1. Add ConnectionPlugin support.
2. Add support for Borland AppServer.
Version 1.20 April, 2001
Enhancement:
1. Redress with option to save a backup file
2. More data validation on Dump Panel.
3. Add uninstall for Super itself.
4. Add Log Database Panel for changing the log database parameters.
5. Register Class: you can type in name or browse on file system.
6. New tour with new examples.
Bug fix:
1. Redress: save file may fail.
2. Install Bean: some may fail due to missing manifest file. Now, it is treated as foreign beans.
3. Installation: Both installServerSideLibrary and installLogDatabase can be worked on the original file, do not need copy to a temporary directory anymore.
4. PeekPoke: if there is no stub available, JNDI list would be empty for Weblogic5-6. Now it pick up all availble ones and give warning messages.
5. Stress: Launch>Save>Cancel generated a null pointer exception.
Changes:
1. installLogDatabase has been changed from .zip file to .jar file.
2. SuperLogging: If the log database is broken, the log methods will not try to access the log database. It is consistent with the document now.
3. SuperLogging will not read system properties now. You can put log database parameters in SuperLoggingEJB's deployment descriptor.
Version 1.10 Feb., 2001
Enhancement:
1. Re-written PeekPoke with Save/Restore functions.
2. New SuperComponent: SuperStress for stress test.
3. Set a mark at the highlighted line on<font size=+0> the Source Code
Panel (as a work-a-round for JDK 1.3).</font>
4. Add support for WebLogic 6.0
Bug fix:
1. Uninstall bean does physically delete the jar file now.
2. WebLogic51 Envoy may not always list all JNDI names. This is fixed.
Version 1.00 Oct., 2000
Enhancement:
1. Support Universal server (virtual all EJB servers).
2. Add Lost and Found for JNDI names, in case you need it.
3. JNDI ComboBox is editable now, so you can PeekPoke not listed JNDI name (mainly for Envoys which do not support JNDI list).
Version 0.90: Sept, 2000
Enhancement:
1. PeekPoke supports arbitrary objects (except for Vector, Hashtable
and alike) as input values.
2. Reworked help documents.
Bug fix:
1. Clicking Cancel button on Pace Panel set 0 to pace. It causes
further time-out.
2. MDI related bugs under JDK 1.3.
Version 0.80: Aug, 2000
Enhancement:
1. With full-featured SuperLogging.
Version 0.72: July, 2000
Bug fix:
1. Ignore unknown objects, so Weblogic5.1 can show JNDI list.
Version 0.71: July, 2000
Enhancement:
1. Re-worked peek algorithm, doing better for concurent use.
2. Add cacellable Wait dialog, showing Super is busy.
3. Add Stop button on Peek Panel.
4. Add undeploy example button.
Bug fix:
1. Deletion on Peek Panel may cause error under JDK 1.3. Now it works for both 1.2 and 1.3
Version 0.70: July, 2000
Enhancement:
1. PeekPoke EJBs without programming.
Bug fix:
1. Did not show many windows under JDK 1.3. Now it works for both 1.2 and 1.3
Changes:
1. All changes are backward compatible, but you may need to recompile monitor windows defined by you.
Version 0.61: June, 2000
Bug fix:
1. First time if you choose BUFFER as logging device, message will not show.
2. Fixed LoggingPanel related bugs.
Version 0.60: May, 2000
Enhancement:
1. Add DATABASE as a logging device for persistent logging message.
2. Made alertInterval configurable.
3. Made pace for tracing configurable.
Bug fix:
1. Fixed many bugs.
Version 0.51, 0.52 and 0.53: April, 2000
Enhancement:
1. Add support to Weblogic 5.1 (support for Logging/Tracing and
user defined GUI window, not support for regular monitoring).
Bug fix:
1. Context sensitive help is available for most of windows: press F1.
2. Fix installation related problems.
Version 0.50: April, 2000
Enhancement:
1. Use JavaHelp for help system.
2. Add shutdown functionality for J2EE.
3. Add support to Weblogic 4.5 (support for Logging/Tracing and
user defined GUI window, not support for regular monitoring).
Bug fix:
1. Better exception handling for null Application.
Version 0.40: March, 2000
Enhancement:
1.New installation program, solves installation related problems.
2. Installation deploys AceletSuperApp application.
3. Add deploy/undeploy facilities.
4. Add EJB and application lists.
Change:
1.SimpleMonitorInterface: now more simple.
Version 0.30: January, 2000
Enhancement:
1. Add realm support to J2EE
2. Come with installation program: you just install what you want
the first time you run Super.
Version 0.20: January, 2000
Enhancement:
Add support to J2EE Sun-RI.
Change:
1. Replace logging device "file" with "buffer" to be
compliant to EJB 1.1. Your code do not need to change.
Version 0.10: December, 1999
Enhancement:
1. provide SimpleMonitorInterface, so GUI experience is
not necessary for developing most monitoring applications.
2. Sortable table for table based windows by mouse
click (left or right).
Version 0.01 November., 1999:
1. Bug fix: An exception thrown when log file is large.
2. Enhancement: Add tour section in Help information.
Version 0.00: October, 1999
Thanks.Adrain,
Its a very good thought and reorganisation might help most of them with their critical issues in 2004s.Its not that the critical issues are not taken care off in the present system but definetly the new names might bring in more attraction and meaning.
I would vote for renaming.
thanks. -
Announcement: Super 4.00 - a suite of EJB/J2EE monitoring/admin tools.
Announcement: Super 4.00 - a suite of EJB/J2EE monitoring/admin tools.
Acelet is the leader in J2EE tools area. If you google "j2ee tools",
"j2ee logging", "j2ee scheduler" or alike, you will find Acelet
is at the top of the result.
Super 4.00 comes with:
SuperEnvironment
SuperLogging
SuperPeekPoke
SuperReport
SuperScheduler
SuperStress
and SuperPatrol, as a schedule job.
The evaluation edition can be anonymously downloaded from:
http://www.ACElet.com.
Super is a component based monitor and administration tool
for EJB/J2ee. It provides built-in functionality as well as
extensions, as SuperComponents. Users can install
SuperComponents onto it, or uninstall them from it.
Super has the following functions:
* A J2EE monitor.
* A gateway to J2EE/EJB servers from different vendors.
* A framework holding user defined SuperComponents.
* A full-featured J2EE logging and J2EE tracing tool for centralized,
chronological logging.
* An EJB tool for Peeking and Poking attributes from EJBs.
* An EJB Stress test tool.
* A J2EE global environment tool.
* A J2EE report tool.
* A J2EE Scheduler tool.
* A J2EE Business patrol tool.
It is written entirely in the Java(TM) programming language.
The current version support:
* JOnAS 2.4 and 2.6
* SunONE 7.0
* Universal servers.
* Weblogic 6.1, 7.0 and 8.1
* Websphere 4.0 and 5.0.2
* jBoss 3.0 and 3.2
********** What is new:
Version 4.00 November, 2003
Enhancement:
1. Support for both native protocol (RMI-IIOP) mode and HTTP/HTTPS
(with/without proxy) protocol mode for SuperEnvironment,
SuperLogging, SuperReport and SuperScheduler.
2. SuperLogging 4.00: tracing can work on both live database and retired database.
3. SuperReport 3.00: works for both live database and retired database.
4. SuperScheduler 3.00: add URL job type (for Servlet/JSP). Add DoerTalker Table
Panel.
Bug fix:
1. SuperScheduler 3.00: Interval change did not take effect until restart Super.
Version 3.00 July, 2003
Enhancement:
1. SuperLoggingLibrary 3.00: New implementation for change scope adding "Smart"
scope,
with enhancements and bug fixes.
2. SuperLoggingLibrary 3.00: Support mail server which requires user name and
password.
Add MenuTreePanel.
3. Improved GUI and document.
4. Add support to WebLogic 8.1.
Bug fix:
1. SuperScheduler 2.0: Fix a bug in FutureView for Hourly and Minutely.
2. SuperScheduler 2.0: Startup should never be reported as missed.
3. SuperScheduler 2.0: Could not reset job for existing task in some situation.
Version 2.20 Jan. 2003
Enhancement:
1. Add desktop and start menu shortcuts for MS-Windows.
2. Add support for SunONE 7, JOnAS 2.6 and jBoss 3.0.
3. SuperLogging 2.40: Add new sendAlarmEmail() method.
4. SuperScheduler 1.40: Add SuperSchedulerEJB for managing when
direct database is not practical; Allow user to choose
favorite logging software; Add Last day as Monthly
repeating attribute.
Change:
1. Change Unusual to PatrolAlarm. The name "Unusual" was misleading.
Bug fix:
1. SuperEnvironment 1.31: Bug fix: if database is broken, could not
open Environment Manager.
2. SuperLogging client 1.52: Annoying exception thrown when you use
JDK 1.4 (the program runs okay).
3. SuperPeekPoke 1.61: Fix bug where input object contains
java.lang.Double and alike.
4. SuperScheduler 1.40: Bug fixes in: Memory leak; Reporting
PatrolAlarm for SuperPatrol; Composite task with members;
Non-scheduled run on other host; Around edges of last
days in Monthly with holiday policy.
Version 2.10 July 2002
Enhancement:
1. SuperScheduler 1.3: Add Future View to check future schedule in
both text and Gantt-chart mode.
2. SuperScheduler 1.3: Add graphic Gantt view for monitoring task's
activities.
3. SuperEnvironment 1.3: uses new graphic package adding print and
preference facilities.
4. SuperPeekPoke 1.6: uses new graphic package adding print and
preference facilities.
5. SuperStress 1.21: uses new graphic package.
Bug fix:
1. SuperStress 1.21: fixed graphic related bugs.
Version 2.01 June 2002
Enhancement:
1. Add options for Look & Feel.
2. Preference is persistent now.
Bug fix:
1. Installation for WebLogic 7.0: extEnv may not be installed on the
right place, so SuperLibrar on the server side was not loaded and
causes other problems.
Version 2.00 June 2002
Enhancement:
1. SuperScheduler 1.2: All copies of SuperScheduler refresh themselves
when any Doer causes things to change.
2. SuperScheduler 1.2: Support default HTML browser for reading HTML document.
3. SuperReport 1.2: Support default HTML browser for reading HTML document.
4. Support WebLogic 7.0.
5. SuperEnvironment 1.21: Database Panel appears when it is necessary.
6. SuperEnvironment 1.21: New SuperEnvironment tour.
Bug fix:
1. WebSphere Envoy did not always list all JNDI names.
Version 1.90 May 2002
Enhancement:
1. Rewritten SuperLogging engine. Add Alarm Email on SuperLogging.
2.Rewritten SuperScheduler allowing multiple Doers. Add support to holiday policy,
effective period. Add Patrol job type as SuperPatrol.
3. Add support for both JOnAS and jBoss.
4. Add more elements on Report criteria.
Change:
1. Now, both left and right mouse clicks are the same on Table Panel: toggle ascend
and descend.
2. New log database.
Bug fix:
1. Alert email should be sent once in the interval, regarding number of servers
in the clustering.
2. Minor bug fixes to make errors handled better on SuperLogging.
3. If withFileInfo or withTimestamp are changed alone, Style Panel did not save
them.
4. Rewritten SuperLogging and SuperScheduler with many bug fixes.
Version 1.80 March 2002
Enhancement:
1. Add new component: SuperScheduler
Bug fix:
1. SuperLogging: Verbose should ignore class registration.
2. SuperLogging-tracing: an exception was thrown if the java class without package
name.
Version 1.70 January 2002
Enhancement:
1. SuperLogging: Scope can dynamically change both for upgrade to downgrade (for
weblogic 6.1, need download an application).
2. Add alias names for log threshold as new Java suggests.
3. New component: SuperReport.
Change:
1. SuperLogging: Log database parameters are specified in a properties file, instead
of EJB's deployment descriptor. It is more convenient and it avoids some potential
problems. No change for development, easier for administration.
Bug fix:
1. Add Source Path Panel now accepts both directory and jar file.
2. Bug in SuperEnvironment example (for version 1.60 only).
Version 1.60 December 2001
Enhancement:
1. SuperPeekPoke and SuperStress can use user defined dynamic argument list.
2. Add timeout parameter to logging access.
3. New installation program with A). Easy install. B). Remote command line install.
4. Support EJB 2.0 for Weblogic 6.1.
5. Support SuperPeekPoke, SuperEnvironment and SuperStress for Websphere 4.0 (SuperLogging
was supported since version 1.5).
Change:
1. Poke: argument list is set at define time, not invoke time.
2. Default log database change to server mode from web server mode, booting performance
to 10-20 times.
Bug fix:
1. If the returned object is null, Peek did not handle it correctly.
2. If the value was too big, TimeSeries chart did not handle it correctly. Now
it can handle up to 1.0E300.
3. Help message was difficult to access in installation program.
4. Source code panel now both highlights and marks the line in question (before
it was only highlight using JDK 1.2, not JDK 1.3).
5. Delete an item on PeekPoke and add a new one generated an error.
Version 1.50 August, 2001
Enhancement:
1. Source code level tracing supports EJB, JSP, java helper and other
programs which are written in native languages (as long as you
write correct log messages in your application).
2. Redress supports JSP now.
3. New installation with full help document: hope it will be easier.
4. Support WebSphere 4.0
Version 1.40 June, 2001
Enhancement:
1. Add SuperEnvironment which is a Kaleidoscope with TableView, TimeSeriesView
and PieView for GlobalProperties.
GlobalProperties is an open source program from Acelet.
2. SuperPeekPoke adds Kaleidoscope with TableView, TimeSeriesView and PieView.
Changes:
1. The structure of log database changed. You need delete old installation and
install everything new.
2. The format of time stamp of SuperLogging changed. It is not locale dependent:
better for report utilities.
3. Time stamp of SuperLogging added machine name: better for clustering environment.
Bug fix:
1. Under JDK 1.3, when you close Trace Panel, the timer may not be stopped and
Style Panel may not show up.
Version 1.30 May, 2001
Enhancement:
1. Add ConnectionPlugin support.
2. Add support for Borland AppServer.
Version 1.20 April, 2001
Enhancement:
1. Redress with option to save a backup file
2. More data validation on Dump Panel.
3. Add uninstall for Super itself.
4. Add Log Database Panel for changing the log database parameters.
5. Register Class: you can type in name or browse on file system.
6. New tour with new examples.
Bug fix:
1. Redress: save file may fail.
2. Install Bean: some may fail due to missing manifest file. Now, it is treated
as foreign beans.
3. Installation: Both installServerSideLibrary and installLogDatabase can be worked
on the original file, do not need copy to a temporary directory anymore.
4. PeekPoke: if there is no stub available, JNDI list would be empty for Weblogic5-6.
Now it pick up all availble ones and give warning messages.
5. Stress: Launch>Save>Cancel generated a null pointer exception.
Changes:
1. installLogDatabase has been changed from .zip file to .jar file.
2. SuperLogging: If the log database is broken, the log methods will not try to
access the log database. It is consistent with the document now.
3. SuperLogging will not read system properties now. You can put log database
parameters in SuperLoggingEJB's deployment descriptor.
Version 1.10 Feb., 2001
Enhancement:
1. Re-written PeekPoke with Save/Restore functions.
2. New SuperComponent: SuperStress for stress test.
3. Set a mark at the highlighted line on<font size=+0> the Source Code
Panel (as a work-a-round for JDK 1.3).</font>
4. Add support for WebLogic 6.0
Bug fix:
1. Uninstall bean does physically delete the jar file now.
2. WebLogic51 Envoy may not always list all JNDI names. This is fixed.
Version 1.00 Oct., 2000
Enhancement:
1. Support Universal server (virtual all EJB servers).
2. Add Lost and Found for JNDI names, in case you need it.
3. JNDI ComboBox is editable now, so you can PeekPoke not listed JNDI name (mainly
for Envoys which do not support JNDI list).
Version 0.90: Sept, 2000
Enhancement:
1. PeekPoke supports arbitrary objects (except for Vector, Hashtable
and alike) as input values.
2. Reworked help documents.
Bug fix:
1. Clicking Cancel button on Pace Panel set 0 to pace. It causes
further time-out.
2. MDI related bugs under JDK 1.3.
Version 0.80: Aug, 2000
Enhancement:
1. With full-featured SuperLogging.
Version 0.72: July, 2000
Bug fix:
1. Ignore unknown objects, so Weblogic5.1 can show JNDI list.
Version 0.71: July, 2000
Enhancement:
1. Re-worked peek algorithm, doing better for concurent use.
2. Add cacellable Wait dialog, showing Super is busy.
3. Add Stop button on Peek Panel.
4. Add undeploy example button.
Bug fix:
1. Deletion on Peek Panel may cause error under JDK 1.3. Now it works for both
1.2 and 1.3
Version 0.70: July, 2000
Enhancement:
1. PeekPoke EJBs without programming.
Bug fix:
1. Did not show many windows under JDK 1.3. Now it works for both 1.2 and 1.3
Changes:
1. All changes are backward compatible, but you may need to recompile monitor
windows defined by you.
Version 0.61: June, 2000
Bug fix:
1. First time if you choose BUFFER as logging device, message will not show.
2. Fixed LoggingPanel related bugs.
Version 0.60: May, 2000
Enhancement:
1. Add DATABASE as a logging device for persistent logging message.
2. Made alertInterval configurable.
3. Made pace for tracing configurable.
Bug fix:
1. Fixed many bugs.
Version 0.51, 0.52 and 0.53: April, 2000
Enhancement:
1. Add support to Weblogic 5.1 (support for Logging/Tracing and
user defined GUI window, not support for regular monitoring).
Bug fix:
1. Context sensitive help is available for most of windows: press F1.
2. Fix installation related problems.
Version 0.50: April, 2000
Enhancement:
1. Use JavaHelp for help system.
2. Add shutdown functionality for J2EE.
3. Add support to Weblogic 4.5 (support for Logging/Tracing and
user defined GUI window, not support for regular monitoring).
Bug fix:
1. Better exception handling for null Application.
Version 0.40: March, 2000
Enhancement:
1.New installation program, solves installation related problems.
2. Installation deploys AceletSuperApp application.
3. Add deploy/undeploy facilities.
4. Add EJB and application lists.
Change:
1.SimpleMonitorInterface: now more simple.
Version 0.30: January, 2000
Enhancement:
1. Add realm support to J2EE
2. Come with installation program: you just install what you want
the first time you run Super.
Version 0.20: January, 2000
Enhancement:
Add support to J2EE Sun-RI.
Change:
1. Replace logging device "file" with "buffer" to be
compliant to EJB 1.1. Your code do not need to change.
Version 0.10: December, 1999
Enhancement:
1. provide SimpleMonitorInterface, so GUI experience is
not necessary for developing most monitoring applications.
2. Sortable table for table based windows by mouse
click (left or right).
Version 0.01 November., 1999:
1. Bug fix: An exception thrown when log file is large.
2. Enhancement: Add tour section in Help information.
Version 0.00: October, 1999
Thanks.
Maybe you are looking for
-
Error while installing Oracle Data miner 10G Release 2
Hello, I am a student involved in research in Data mining. I am new to Oracle Database and data miner. I installed Oracle Enterprise Manager 10g Grid Control Release 2 (10.2.0.1). Now I am trying to install ORacle data miner (10.2.0.1). However, at t
-
Error message on Windows 2000 startup, "Tcmsvr.dll, File is missing"
We get the same error messages three times on Windows 2000 startup on some of our companys computers: "Tcmsvr.dll, File is missing". The computers are Tecra s1 models. Which Toshiba driver is this related to?
-
I am using 2013 Macbook air and download the lasted version of Skype. However, I can't do video call because of the camera. It can't be connected to either Yahoo messenger or Skype. I went to Skype > Preferences > Audio/Video to set up the camera but
-
"Import Error" with Word Document (google doc)
I tried to open a word document that I created using Google's online document program and I keep getting 'import error' when I try to open with Pages. I tried it several times on several different .doc documents created with the Google program and ge
-
Oracle linux 6 iptables SNAT error!
hello every one I use oracle linux 6.1,and use iptables do snat, but the POSTROUTING CHAIN can't receive packets (i see it use 'iptables-save') echo 1 > /proc/sys/net/ipv4/ip_forward 'iptables-save' like this: # Generated by iptables-save v1.4.7 on T