Shanti Subramanyam

Sun Microsystems, Inc.

 

Art Technology Group Inc.(ATG)		BEA Systems		Borland Software Corporation
Compaq Computer Corporation		Fujitsu Limited		Hewlett-Packard
Hitachi, Ltd.		IBM		Kayser, William
Macromedia, Inc.		Novell, Inc.		Oracle
Persistence Software Inc.		Pramati Technologies		Sun Microsystems, Inc.
Sybase

Expert Group Private Page

JSR Community Update Page

 

Original Java Specification Request (JSR)

Identification | Request | Contributions | Additional Information

Section 1. Identification

Submitting Member: Sun Microsystems, Inc

Name of Contact Person: Shanti Subramanyam

E-Mail Address: shanti@eng.sun.com

Telephone Number: +1 650 786 6147

Fax Number: +1 650 786 7353

Specification Lead: Shanti Subramanyam

E-Mail Address: shanti@eng.sun.com

Telephone Number: +1 650 786 6147

Fax Number: +1 650 786 7353

Initial Expert Group Membership:

Sun

Section 2: Request

2.1 Please describe the proposed Specification:

ECperf 1.1 is a maintenance release of ECperf 1.0. The goal is to fix any bugs or discrepencies found as we gain more experience with ECperf 1.0. We may undertake minor enhancements if deemed necessary to make this a better workload.

2.2 What is the target Java platform? (i.e., desktop, server, personal, embedded, card, etc.)

Server

2.3 What need of the Java community will be addressed by the proposed specification?

A stable, robust, standard EJB performance workload

2.4 Why isn't this need met by existing specifications?

There are no standard workloads today

2.5 Please give a short description of the underlying technology or technologies:

Various APIS in J2EE 1.2, primarily EJB 1.1

2.6 Is there a proposed package name for the API Specification? (i.e., javapi.something, org.something, etc.)

com.sun.ecperf

2.7 Does the proposed specification have any dependencies on specific operating systems, CPUs, or I/O devices that you know of?

No

2.8 Are there any security issues that cannot be addressed by the current security model?

No

2.9 Are there any internationalization or localization issues?

No

2.10 Are there any existing specifications that might be rendered obsolete, deprecated, or in need of revision as a result of this work?

No

2.11 Please describe the anticipated schedule for the development of this specification.

Since this is a maintenance release, we hope to turn it around in 7 months, targetting a final release by Feb 2002.

2.12 Please describe the anticipated working model for the Expert Group working on developing this specification.

The Expert Group will work in the same way the ECperf 1.0 Expert Group has. This has worked successfully for us. We have weekly conference calls with proposals sent in via email in advance. Discussions are informal and most decisions are made via consensus.

Section 3: Contributions

3.1 Please list any existing documents, specifications, or implementations that describe the technology. Please include links to the documents if they are publicly available.

See java.sun.com/j2ee/ecperf for the ECperf 1.0 specification.

3.2 Explanation of how these items might be used as a starting point for the work.

Section 4: Additional Information (Optional)

4.1 This section contains any additional information that the submitting Member wishes to include in the JSR.

None