|
Sun Java System Message Queue Release Notes for Microsoft Windows |
Sun Java™ System Message Queue Release Notes for Microsoft Windows
Version 3 2005Q4 (3.6 SP3)
Part Number 819-4268-10
These release notes contain important information available at the time of release of Sun Java System Message Queue 3 2005Q4 for Windows. Known issues and limitations, and other information are addressed here. Read this document before you begin using Message Queue.
The most up-to-date version of these release notes can be found at the Sun Java System documentation web site: http://docs.sun.com/app/docs/prod/entsys.05q4#hic. Check the web site prior to installing and setting up your software and then periodically thereafter to view the most up-to-date release notes and product documentation.
These release notes contain the following sections:
Third-party URLs are referenced in this document and provide additional, related information.
Release Notes Revision History
Table 1 Revision History
Date
Description of Changes
February 2006
Revenue release.
November 2005
Beta release.
About Message Queue 3 2005Q4 (3.6 SP3)Sun Java System Message Queue is a full-featured message service that provides reliable, asynchronous messaging that conforms to the Java Messaging Specification (JMS) 1.1. In addition, Message Queue provides a host of features that go beyond the JMS specification to provide for the needs of large-scale enterprise deployments.
What’s New in Message Queue 3 2005Q4
New features in Message Queue 3.6 SP3 2005Q4 (3.6) include:
These are described in the following sub-sections.
Dead Message Queue
Message Queue automatically creates a specialized destination at broker startup that is used to store dead messages for diagnostic purposes. A dead message is one that is removed from the system for a reason other than normal processing or explicit administrator action. A message might be considered dead because it has expired, because it has been removed from a destination due to memory limit overruns, or because of failed delivery attempts.
An administrator can configure destinations to either discard dead messages or place them in the dead message queue. When placed in the dead message queue, additional property information is written into the message, providing an administrator with information about the cause of death. A client developer can also set a property value when creating a message that determines whether the message should be placed in the dead message queue were it to die.
For more information, see the Message Queue Administration Guide.
No Acknowledge Mode
The NO_ACKNOWLEDGE acknowledgement mode is an extension to the JMS API. Normally, the broker waits for a client acknowledgement. That acknowledgement must be made programmatically if the client has specified CLIENT_ACKNOWLEDGE or it can be made automatically, by the session, if the client has specified AUTO_ACKNOWLEDGE or DUPS_OK. If a consuming client specifies the NO_ACKNOWLEDGE mode, the broker discards the message as soon as it has sent it to the consuming client. This feature is intended for use by non-durable subscribers consuming non-persistent messages, but it can be used by any consumer.
Using this feature improves performance by reducing protocol traffic and broker work involved in acknowledging a message. This feature can also improve performance for brokers dealing with misbehaving clients who do not acknowledge messages and therefore tie down broker memory resources unnecessarily. Using this mode has no effect on producers.
There is no support for the NO_ACKNOWLEDGE mode in C clients. For more information, see the Message Queue Developer’s Guide for Java Clients.
Client Message Body Compression
The developer can specify that the body of a message can be compressed. Message compression and decompression is handled entirely by the client runtime and does not affect the broker. Therefore, applications can use this feature with a previous version of the broker, but they must use version 3.6 SP3 2005Q4 (3.6) of the Message Queue client runtime library.
Advantages and Limitations of Compression
Although message compression has been added to improve performance, such benefit is not guaranteed. Benefits vary with the size and format of messages, the number of consumers, network bandwidth, and CPU performance. For example, the cost of compression and decompression might be higher than the time saved in sending and receiving a compressed message. This is especially true when sending small messages in a high-speed network. On the other hand, applications that publish large messages to many consumers or who publish in a slow network environment, might improve system performance by compressing messages.
Message consumers deployed with client runtime libraries that precede version 3.6 SP3 2005Q4 (3.6) cannot handle compressed messages. Clients configured to send compressed messages must make sure that consumers are compatible. C clients cannot currently consume compressed messages.
For more information, see the Message Queue Developer’s Guide for Java Clients.
Connection Failure Detection (Client Runtime Ping)
Message Queue 3.6 SP3 2005Q4 introduces a new ConnectionFactory attribute named imqPingInterval. The imqPingInterval attribute specifies the frequency of a ping operation from the client runtime to the broker. By periodically testing the connection, the client runtime can preemptively detect a failed connection. If the ping operation fails, the client runtime throws an exception to the client application’s exception listener object. If the application does not have an exception listener, the application’s next attempt to use the connection fails.
For more information, see the Message Queue Administration Guide.
Certificate Management: C-API NSS Tools
The C-API uses NSS (Network Security Services) libraries to support SSL. These libraries provide APIs and utilities for developing secure applications. These utilities include tools to manage keys and certificate databases. In Message Queue 3.5, we asked developers to use Mozilla to manage NSS keys and certificates. In Message Queue 3.6 SP3 2005Q4, administrators can use the NSS certutil tool to generate the needed keys and certificates.
For more information, see the Message Queue Developer’s Guide for C Clients.
Support for C-API Basic Authentication
Message Queue 3.6 SP3 2005Q4 C-API supports the basic authentication type. Previous releases of Message Queue did not support the basic authentication type.
64-bit C-API Support
Message Queue now contains 64-bit C-API support on the Solaris/SPARC platform. For more information about enabling 64-bit C-API support, see the Message Queue Developer’s Guide for C Clients.
Hardware and Software Requirements
This section specifies or describes the hardware and software required for this release of Message Queue.
The table below lists hardware and software requirements for Windows operating systems.
Message Queue 3.6 SP3 also depends upon other technologies, as indicated in the table below. The table below lists and describes the basic components that you must install in order to be able to develop and run Message Queue clients.
The table below lists and describes the components that you can install to provide additional support for a Message Queue client. You might need some of the components listed. For example, if you are not writing a C client to Message Queue, you will not need any of the components required for C client support.
Bugs Fixed in This Release
Table 5 Fixed Bugs in Message Queue 3.6 SP3 2005Q4
Bug ID
Description
6284053
CLASSPATH environment variable is being set unnecessarily when installing MQ
Important InformationThis section covers the following topics:
Installation Notes
For information about patch requirements and installation, see the following section:
Patch Requirement Information
The following table gives the numbers and minimum versions for the alignment patches. All patches referred to in this section are the minimum version number required for upgrade. It is possible that a new version of the patch has been issued since this document was published. A newer version is indicated by a different version number at the end of the patch. For example: 123456-04 is a newer version of 123456-02 but they are the same patch ID. Refer to the README file for each patch listed for special instructions.
To access the patches, go to http://sunsolve.sun.com.
For detailed information about Upgrade procedure of the Message Queue from JES3 to JES4 refer Sun Java Enterprise System 2005Q4 Upgrade Guide for Microsoft Windows located at http://docs.sun.com/app/docs/doc/819-4461.
Issues Related to the Next Major Release of Message Queue
The next major release of Message Queue may introduce changes that make your clients incompatible with that release. This information is provided now to allow you to prepare for these changes.
- This is the last feature release of Sun Java System Message Queue that will be backwards compatible with Sun One Message Queue 3.0.1. In particular, future releases of Sun Java System Message Queue will not support the following:
- This is the last release of Sun Java System Message Queue that will support being integrated as the 'System JMS Messaging Provider' for Sun Java System Application Server 7.X. Future releases of Sun Java System Message Queue will only support Sun Java System Application Server 8.0 and above.
- This is the last release of Sun Java System Message Queue that will include the SOAP runtime and support the Message Queue SOAP Administered Objects.
- Future releases will only support SOAP in conjunction with a Java 2 Standard Edition Platform version that supports SOAP.
- Sun Java System Message Queue client support for all releases of J2SE 1.3 will be dropped. J2SE 1.4 will continue to be supported.
- The locations of individual files installed as part of Sun Java System Message Queue might change. This could break existing applications that depend on the current location of certain Message Queue files.
- Sun Java System Message Queue clients that use a version of Message Queue older than the next major version might not have access to the new features offered in that version of the product.
Compatibility Issues
This section covers compatibility issues in Message Queue 3 2005Q1 (3.6).
Issues in Message Queue 3 2005Q1 (3.6)
The following points describe issues that affect Windows platform.
Deprecation of Password Options
The following options have been deprecated for security reasons:
If a password is specified as a part of a command such as the following:
imqcmd query bkr -u admin -p adminpassword
a user sees the administrator password while listing or querying a machine's processes. Use the -passfile option instead. The passfile option is explained in the chapter on security in the Message Queue Administration Guide.
Documentation Updates for Message Queue
The following sections describe the documentation updates for Message Queue 3 2005Q1 (3.6) and Message Queue 3 2005Q4 (3.6 SP2).
Documentation Updates for Message Queue 3 2005Q1 (3.6)
The following Message Queue documents were updated from Version 3.5 of the product:
Installation Guide
The Message Queue Installation Guide was updated to reflect branding changes and platform-specific information. This document now contains installation information relevant to Message Queue, Platform Edition.
Message Queue, Enterprise Edition installation information moved to the Sun Java System Installation Guide.
For information on upgrade and migration to Message Queue 3.6 SP3 2005Q4 (3.6), Enterprise Edition, see the Sun Java System Upgrade and Migration Guide.
Technical Overview
The Message Queue Technical Overview Overview is a new document that was introduced with the Message Queue 3 2005Q1 (3.6) release. It has been rewritten for the Message Queue 3 2005Q4 (3.6 SP3) release. It describes the Message Queue product, its features, architecture, technology, and terminology. This new book contains overview information previously contained in other books and is meant to be used by Message Queue users--both administrators and developers--and prospective users, as well.
Administration Guide
The Message Queue Administration Guide has been updated to reflect branding changes and new features. This document has also been reorganized for better usability by Message Queue administrators. Overview information previously contained in this document has been moved to the Message Queue Technical Overview.
Message Queue Developer’s Guide for Java Clients
The Java Client Developer’s Guide has been updated to reflect branding changes and new features. The document has also been renamed to Message Queue Developer’s Guide for Java Clients.
The Message Queue Developer’s Guide for Java Clients has been reorganized for better usability by Message Queue Java Client Developers. Overview information previously contained in this document has been moved to the Message Queue Technical Overview.
C Client Developer’s Guide
The C Client Developer’s Guide was updated to reflect branding changes and new features. The document has also been renamed to Message Queue Developer’s Guide for C Clients.
The Message Queue Developer’s Guide for C Clients has been reorganized for better usability by Message Queue C Client Developers. Overview information previously contained in this document has been moved to the Message Queue Technical Overview.
Documentation Updates for Message Queue 3 2005Q4 (3.6 SP3) Beta
Because Message Queue 3 2005Q4 (3.6 SP2) Beta is a Beta release, only the documents that have been updated from Version 3 2005Q1 (3.6) of the product are located in the Beta documentation collection at http://docs.sun.com/coll/1307.1. For documents that have not changed since the previous release, refer to the Version 3 2005Q1 (3.6) documentation collection at http://docs.sun.com/app/docs/coll/MessageQueue_2005Q1
The following Message Queue documents were updated from Version 3 2005Q1 (3.6) of the product:
Technical Overview
The Message Queue Technical Overview is a new document that was introduced with the Message Queue 3 2005Q1 (3.6) release. It has been rewritten for the Message Queue 3 2005Q4 (3.6 SP2) release. It describes the Message Queue product, its features, architecture, technology, and terminology. This new book contains overview information previously contained in other books and is meant to be used by Message Queue users--both administrators and developers--and prospective users, as well.
Administration Guide
The Message Queue Administration Guide has been reorganized for better usability by Message Queue administrators. Overview information previously contained in this document has been moved to the Message Queue Technical Overview.
Message Queue Developer’s Guide for Java Clients
The Message Queue Developer’s Guide for Java Clients includes a new chapter, “Using the Java API”.
Accessibility Features for People With Disabilities
To obtain accessibility features that have been released since the publishing of this media, consult Section 508 product assessments available from Sun upon request to determine which versions are best suited for deploying accessible solutions. Updated versions of applications can be found at: http://sun.com/software/javaenterprisesystem/get.html.
For information on Sun's commitment to accessibility, visit http://sun.com/access.
Known Issues and LimitationsThis section describes the known issues and limitations of Message Queue 3 2005Q4 for Microsoft Windows. The following component areas are covered:
For a list of current bugs, their status, and workarounds, Java Developer Connection™ members should see the Bug Parade page on the Java Developer Connection web site. Please check that page before you report a new bug. Although all Message Queue bugs are not listed, the page is a good starting place if you want to know whether a problem has been reported.
The relevant page is:
To report a new bug or submit a feature request, send mail to imq-feedback@sun.com.
General Issues
This section covers general issues in Message Queue 3 2005Q1. This section groups issues related to Enterprise Editions of Message Queue.
Both Enterprise and Platform Editions
If you previously relied on any property value in the example ldap user repository properties setup in the default.properties file, your JMS application client will receive a security exception when attempting to create a JMS connection. This will happen after you upgrade to Message Queue 3 2005Q1.
When your JMS client tries to make a connection to the Message Queue 3 2005Q1 broker, you will get a error in the broker log and your JMS client will receive the following exception:
SecurityException.
20/Aug/2004:11:16:41 PDT] ERROR [B4064]: Ldap repository ldap property .uidattr not defined for authentication type basic:com.sun.messaging.jmq.auth.LoginException:
[B4064]: Ldap repository ldap property .uidattr not defined for authentication type basicWorkaround
Set the broker property imq.user_repository.ldap.uidattr following the instructions in the Message Queue Administration Guide.
- Create a connection to the Message Queue broker by calling MQCreateConnection before launching any threads You cannot edit a broker’s instance configuration file without having started the broker instance at least once. This is because the config.properties file does not exist until the broker instance is first started. To configure a broker to use pluggable persistence or to set other configuration properties, run the broker once (with the instance name that should be used to create the broker) to create the config.properties file:.
Enterprise Edition Only
- Only fully-connected broker clusters are supported in this release. This means that every broker in a cluster must communicate directly with every other broker in the cluster. If you are connecting brokers using the imqbrokerd -cluster command line argument, be careful to ensure that all brokers in the cluster are included.
- A client connected to a broker that is part of a cluster cannot currently use QueueBrowser to browse queues that are located on remote brokers in that cluster. The client can only browse the contents of queues that are located on the broker to which it is directly connected. The client may still send messages to any queue or consume messages from any queue on any broker in the cluster; the limitation only affects browsing.
- If a Master Broker is not used in a broker cluster, persistent information stored by a broker being added to the cluster is not propagated to other brokers in the cluster.
- A connection service using SSL is currently limited to supporting only self-signed server certificates, that is, host-trusted mode.
- When a JMS client using the HTTP transport terminates abruptly (for example, using Ctrl-C) the broker takes approximately one minute before the client connection and all the associated resources are released.
If another instance of the client is started within the one minute period and if it tries to use the same ClientID, durable subscription, or queue, it might receive a “Client ID is already in use” exception. This is not a real problem; it is just the side effect of the termination process described above. If the client is started after a delay of approximately one minute, everything should work fine.
Administration/Configuration Issues
The imqadmin and imqobjmgr utilities throw an error when the CLASSPATH contains double quotes on Windows machines (5060769)
Workaround
You can ignore this error message; the broker correctly handles notifying consumers of any error. This error does not affect the reliability of the system.
The -javahome option in all solaris/win scripts does not work if the value has a space (4683029)
The -javahome option is used by the Message Queue commands and utilities to specify an alternate Java 2 compatible runtime to use. However, the path to the alternate Java runtime must be located at a path that does not contain spaces.
Examples of paths that have spaces are:
Windows:
C:\jdk 1.4
Solaris:
/work/java 1.4
Workaround
Install the Java runtime at a location or path that does not contain spaces.
Message Queue output garbage message to syslog in non-C locale (6193884)
Message Queue will send garbage output to the system log when the broker is run in a non-C locale.
Workaround
Run broker in C locale.
Broker Issues
In a broker cluster, a broker will queue messages to a remote connection which may not be started (4951010)
Workaround
The messages will be received by the consumer once the connection is started. The messages will be redelivered to another consumer if the consumer’s connection is closed.
HTTPS createQueueConnection occasionally throws exception on Windows 2000(4953348)
Workaround
Retry the connection.
When using Ctrl-C to shut down broker, transactions may be cleaned up after store is closed (4934446)
The broker may show errors with the following reason “Store method accessed after the store is closed.” if the broker is shutdown while messages or transactions are processed.
Workaround
You can ignore this error message; the broker correctly handles notifying consumers of any error. This error does not affect the reliability of the system.
Broker becomes inaccessible when persistent store opens too many destinations (4953354)
Workaround
This condition is caused by the broker reaching the system open-file descriptor limit. On Solaris and Linux use the ulimit command to increase the file descriptor limit.
Consumers are orphaned when a destination is destroyed (5060787)
Active consumers are orphaned when a destination is destroyed. Once the consumers have been orphaned, they will no longer receive messages (even if the destination is recreated).
Workaround
There is no workaround for this problem.
Message selection using JMSMessageID doesn’t work (6196233)
Message selection using the selector "JMSMessageID = '<message_id>'" does not work.
Workaround
Change the selector from:
JMSMessageID = "ID:message-id-string"
to:
JMSMessageID IN (’ID:message-id-string’, ’message-id-string’)
- Windows platforms set limits to the number of connections to a broker that can be simultaneously started over TCP/IP, in accordance with the maximum value of the backlog size. Backlog is the buffer for connections in the TCP stack. The number of simultaneous TCP connection startups cannot exceed the backlog size. For example, Windows 2000 Professional limits the backlog to 5, and Windows 2000 Server limits the backlog to 200.
- You cannot edit a broker’s instance configuration file without having started the broker instance at least once. This is because the config.properties file does not exist until the broker instance is first started. To configure a broker to use pluggable persistence or to set other configuration properties, run the broker once (with the instance name that should be used to create the broker) to create the config.properties file:
- Only fully-connected broker clusters are supported in this release. This means that every broker in a cluster must communicate directly with every other broker in the cluster. If you are connecting brokers using the imqbrokerd -cluster command line argument, be careful to ensure that all brokers in the cluster are included.
- A client connected to a broker that is part of a cluster cannot currently use QueueBrowser to browse queues that are located on remote brokers in that cluster. The client can only browse the contents of queues that are located on the broker to which it is directly connected. The client may still send messages to any queue or consume messages from any queue on any broker in the cluster; the limitation only affects browsing.
- If a Master Broker is not used in a broker cluster, persistent information stored by a broker being added to the cluster is not propagated to other brokers in the cluster.
- A connection service using SSL is currently limited to supporting only self-signed server certificates in host-trusted mode.
- When a JMS client using the HTTP transport terminates abruptly (for example, using Ctrl-C) the broker takes approximately one minute before the client connection and all the associated resources are released.
If another instance of the client is started within the one minute period and if it tries to use the same Client ID, durable subscription, or queue, it might receive a “Client ID is already in use” exception. This is not a real problem; it is just the side effect of the termination process described above. If the client is started after a delay of approximately one minute, everything should work fine.
Installation Issues
Add/Remove Programs control panel displays Sun Java Enterprise System
Add/Remove Programs control panel lists Sun Java Enterprise System instead of Message Queue.
Location of NSS and NSPR libraries has changed (6271133).
The location of the NSS and NSPR libraries has changed from previous releases, and the Message Queue C Client Developer's Guide may describe these locations incorrectly. These libraries are needed to build C clients and the new location of these libraries is in the 'share\lib' folder.
For example: 'C:\Sun\share\lib'
The file Config_MQ.txt contains incorrect information
The file Config_MQ.txt contains incorrect information. The following items correct some of the error's:
- The Config Now and Config Later options are not available with Message Queue, and there is no option to set the Administrator password at installation time.
- The Configure Automatically option will install and start the MQ Broker Windows service automatically.
- The Configure Manually option allows you to install the MQ Broker without starting it as a Windows service.
Confusing error message when attempting to install on a disk without sufficient disk space.
When installing on a disk that does not have sufficient disk space, the installation may fail with a confusing error message. For example:
"Error: -1603 Fatal error during installation."If you get this error message attempt the installation on a disk with sufficient space.
Cannot install MQ if directory name has space in between (6314103)
e.g C:/Program Files/Sun/MessageQueue
Workaround
Do not install the product in the directory whose name has space in between.
Cannot install MQ if directory name (ex) C:\Software\Sun, has more than 6 characters (6314088, 6392963)
e.g. C:/Software/sun
Workaround
Do not install the product in the directory whose name has more than six characters [inclusive of drive letter, colon and slashes]
SSL
Message Queue C-API SSL and MQ_SSL_BROKER_IS_TRUSTED.
When using C-API SSL connection, if you set MQ_SSL_BROKER_IS_TRUSTED to MQ_FALSE, you must create the broker certificate with the CN to be the hostname with fully-qualified domain name of the running broker, and specify the MQ_BROKER_HOST_PROPERTY to be the same in your C-API application.
If you don't use fully-qualified domain name, your broker certificate would be rejected with error message SSL_ERROR_BAD_CERT_DOMAIN.
Workaround
None.
Redistributable FilesSun Java System Message Queue 3.6 SP3 2005Q4 contains the following set of files which you may use and freely distribute in binary form:
How to Report Problems and Provide FeedbackIf you have problems with Sun Java System Message Queue, contact Sun customer support using one of the following mechanisms:
- Sun Software Support services online at
http://www.sun.com/service/sunone/softwareSo that we can best assist you in resolving problems, please have the following information available when you contact support:
- Description of the problem, including the situation where the problem occurs and its impact on your operation
- Machine type, operating system version, and product version, including any patches and other software that might be affecting the problem
- Detailed steps on the methods you have used to reproduce the problem
- Any error logs or core dumps
Sun Java System Software Forum
There is a Sun Java System Message Queue forum available at the following location:
We welcome your participation.
Java Technology Forum
There is a JMS forum in the Java Technology Forums that might be of interest.
Sun Welcomes Your Comments
Sun is interested in improving its documentation and welcomes your comments and suggestions.
To share your comments, go to http://docs.sun.com and click Send Comments. In the online form, provide the document title and part number. The part number is a seven-digit or nine-digit number that can be found on the title page of the book or at the top of the document. For example, the title of this book is Sun Java System Message Queue 2005Q4 Release Notes for Microsoft Windows, and the part number is 819-4268-10.
Additional Sun ResourcesUseful Sun Java System information can be found at the following Internet locations:
- Documentation for Message Queue
http://docs.sun.com/app/docs/coll/1307.1- Sun Java System Documentation
http://docs.sun.com/app/docs/prod/entsys.05q4#hic- Sun Java System Professional Services
http://www.sun.com/service/sunps/sunone- Sun Java System Software Products and Service
http://www.sun.com/software- Sun Java System Software Support Services
http://www.sun.com/service/sunone/software- Sun Java System Support and Knowledge Base
http://www.sun.com/service/support/software- Sun Support and Training Services
http://training.sun.com- Sun Java System Consulting and Professional Services
http://www.sun.com/service/sunps/sunone- Sun Developer Information
http://developers.sun.com- Sun Developer Support Services
http://www.sun.com/developers/support- Sun Software Data Sheets
http://wwws.sun.com/software
Copyright � 2006 Sun Microsystems, Inc. All rights reserved.
Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.
SUN PROPRIETARY/CONFIDENTIAL.
U.S. Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements.
Use is subject to license terms.
This distribution may include materials developed by third parties.
Portions may be derived from Berkeley BSD systems, licensed from U. of CA.
Sun, Sun Microsystems, the Sun logo, Java and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries.
Copyright � 2006 Sun Microsystems, Inc. Tous droits r�serv�s.
Sun Microsystems, Inc. d�tient les droits de propri�t� intellectuels relatifs � la technologie incorpor�e dans le produit qui est d�crit dans ce document. En particulier, et ce sans limitation, ces droits de propri�t� intellectuelle peuvent inclure un ou plusieurs des brevets am�ricains list�s � l'adresse http://www.sun.com/patents et un ou des brevets suppl�mentaires ou des applications de brevet en attente aux Etats - Unis et dans les autres pays.
Propri�t� de SUN/CONFIDENTIEL.
L'utilisation est soumise aux termes du contrat de licence.
Cette distribution peut comprendre des composants d�velopp�s par des tierces parties.
Des parties de ce produit pourront �tre d�riv�es des syst�mes Berkeley BSD licenci�s par l'Universit� de Californie.
Sun, Sun Microsystems, le logo Sun, Java et Solaris sont des marques de fabrique ou des marques d�pos�es de Sun Microsystems, Inc. aux Etats-Unis et dans d'autres pays.
Toutes les marques SPARC sont utilis�es sous licence et sont des marques de fabrique ou des marques d�pos�es de SPARC International, Inc. aux Etats-Unis et dans d'autres pays.