Sun GlassFish Communications Server 2.

0 Error Message Reference

Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95054 U.S.A.
Part No: 8210189 October 2009

Copyright 2009 Sun Microsystems, Inc.

4150 Network Circle, Santa Clara, CA 95054 U.S.A.

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 U.S. patents or pending patent applications in the U.S. and in other countries. 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. This distribution may include materials developed by third parties. Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and other countries, exclusively licensed through X/Open Company, Ltd. Sun, Sun Microsystems, the Sun logo, the Solaris logo, the Java Coffee Cup logo, docs.sun.com, Java, Java, and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. or its subsidiaries 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. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. The OPEN LOOK and SunTM Graphical User Interface was developed by Sun Microsystems, Inc. for its users and licensees. Sun acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry. Sun holds a non-exclusive license from Xerox to the Xerox Graphical User Interface, which license also covers Sun's licensees who implement OPEN LOOK GUIs and otherwise comply with Sun's written license agreements. Products covered by and information contained in this publication are controlled by U.S. Export Control laws and may be subject to the export or import laws in other countries. Nuclear, missile, chemical or biological weapons or nuclear maritime end uses or end users, whether direct or indirect, are strictly prohibited. Export or reexport to countries subject to U.S. embargo or to entities identified on U.S. export exclusion lists, including, but not limited to, the denied persons and specially designated nationals lists is strictly prohibited. DOCUMENTATION IS PROVIDED AS IS AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. Copyright 2009 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 95054 U.S.A. Tous droits rservs.

Sun Microsystems, Inc. dtient les droits de proprit intellectuelle relatifs la technologie incorpore dans le produit qui est dcrit dans ce document. En particulier, et ce sans limitation, ces droits de proprit intellectuelle peuvent inclure un ou plusieurs brevets amricains ou des applications de brevet en attente aux Etats-Unis et dans d'autres pays. Cette distribution peut comprendre des composants dvelopps par des tierces personnes. Certaines composants de ce produit peuvent tre drives du logiciel Berkeley BSD, licencis par l'Universit de Californie. UNIX est une marque dpose aux Etats-Unis et dans d'autres pays; elle est licencie exclusivement par X/Open Company, Ltd. Sun, Sun Microsystems, le logo Sun, le logo Solaris, le logo Java Coffee Cup, docs.sun.com, Java, Java et Solaris sont des marques de fabrique ou des marques dposes de Sun Microsystems, Inc., ou ses filiales, aux Etats-Unis et dans d'autres pays. Toutes les marques SPARC sont utilises sous licence et sont des marques de fabrique ou des marques dposes de SPARC International, Inc. aux Etats-Unis et dans d'autres pays. Les produits portant les marques SPARC sont bass sur une architecture dveloppe par Sun Microsystems, Inc. L'interface d'utilisation graphique OPEN LOOK et Sun a t dveloppe par Sun Microsystems, Inc. pour ses utilisateurs et licencis. Sun reconnat les efforts de pionniers de Xerox pour la recherche et le dveloppement du concept des interfaces d'utilisation visuelle ou graphique pour l'industrie de l'informatique. Sun dtient une licence non exclusive de Xerox sur l'interface d'utilisation graphique Xerox, cette licence couvrant galement les licencis de Sun qui mettent en place l'interface d'utilisation graphique OPEN LOOK et qui, en outre, se conforment aux licences crites de Sun. Les produits qui font l'objet de cette publication et les informations qu'il contient sont rgis par la legislation amricaine en matire de contrle des exportations et peuvent tre soumis au droit d'autres pays dans le domaine des exportations et importations. Les utilisations finales, ou utilisateurs finaux, pour des armes nuclaires, des missiles, des armes chimiques ou biologiques ou pour le nuclaire maritime, directement ou indirectement, sont strictement interdites. Les exportations ou rexportations vers des pays sous embargo des Etats-Unis, ou vers des entits figurant sur les listes d'exclusion d'exportation amricaines, y compris, mais de manire non exclusive, la liste de personnes qui font objet d'un ordre de ne pas participer, d'une faon directe ou indirecte, aux exportations des produits ou des services qui sont rgis par la legislation amricaine en matire de contrle des exportations et la liste de ressortissants spcifiquement designs, sont rigoureusement interdites. LA DOCUMENTATION EST FOURNIE "EN L'ETAT" ET TOUTES AUTRES CONDITIONS, DECLARATIONS ET GARANTIES EXPRESSES OU TACITES SONT FORMELLEMENT EXCLUES, DANS LA MESURE AUTORISEE PAR LA LOI APPLICABLE, Y COMPRIS NOTAMMENT TOUTE GARANTIE IMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L'APTITUDE A UNE UTILISATION PARTICULIERE OU A L'ABSENCE DE CONTREFACON.

091103@22749

Contents

Preface .....................................................................................................................................................7

Unexpected Errors ...............................................................................................................................13 Analyze the System .............................................................................................................................. 13

ACC Error Messages ..............................................................................................................................15 ACC Messages ........................................................................................................................................ 15

ACT Error Messages ..............................................................................................................................21 ACT Messages ........................................................................................................................................ 21

ADM Error Messages ..............................................................................................................................23 ADM Messages ........................................................................................................................................ 23

CIS Error Messages ..............................................................................................................................71 CIS Messages ........................................................................................................................................ 71

CMNUTIL Error Messages .....................................................................................................................85 CMNUTIL Messages ................................................................................................................................ 85

CONF Error Messages ............................................................................................................................89 CONF Messages ...................................................................................................................................... 89

CORE Error Messages ............................................................................................................................91 CORE Messages ...................................................................................................................................... 91

3

Contents

DIAG Error Messages ..........................................................................................................................109 DIAG Messages .................................................................................................................................... 109

10

DPL Error Messages ............................................................................................................................119 DPL Messages ...................................................................................................................................... 119

11

DTX Error Messages ............................................................................................................................135 DTX Messages ...................................................................................................................................... 135

12

EEADM Error Messages ........................................................................................................................139 EEADM Messages .................................................................................................................................. 139

13

EJB Error Messages ............................................................................................................................141 EJB Messages ...................................................................................................................................... 141

14

IOP Error Messages ............................................................................................................................165 IOP Messages ...................................................................................................................................... 165

15

JBISE Error Messages ........................................................................................................................179 JBISE Messages .................................................................................................................................. 179

16

JDO Error Messages ............................................................................................................................183 JDO Messages ...................................................................................................................................... 183

17

JML Error Messages ............................................................................................................................187 JML Messages ...................................................................................................................................... 187

18

JMS Error Messages ............................................................................................................................189 JMS Messages ...................................................................................................................................... 189

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

Contents

19

JTS Error Messages ............................................................................................................................197 JTS Messages ...................................................................................................................................... 197

20

LAUNCHER Error Messages .................................................................................................................201 LAUNCHER Messages ........................................................................................................................... 201

21

LCM Error Messages ............................................................................................................................203 LCM Messages ...................................................................................................................................... 203

22

LDR Error Messages ............................................................................................................................205 LDR Messages ...................................................................................................................................... 205

23

MDB Error Messages ............................................................................................................................213 MDB Messages ...................................................................................................................................... 213

24

NAM Error Messages ............................................................................................................................223 NAM Messages ...................................................................................................................................... 223

25

RAR Error Messages ............................................................................................................................225 RAR Messages ...................................................................................................................................... 225

26

SEC Error Messages ............................................................................................................................255 SEC Messages ...................................................................................................................................... 255

27

SERVER Error Messages .....................................................................................................................267 SERVER Messages ................................................................................................................................ 267

28

SGMT Error Messages ..........................................................................................................................273 SGMT Messages .................................................................................................................................... 273

Contents

29

SYNC Error Messages ..........................................................................................................................287 SYNC Messages .................................................................................................................................... 287

30

UTIL Error Messages ..........................................................................................................................289 UTIL Messages .................................................................................................................................... 289

31

VRFY Error Messages ..........................................................................................................................307 VRFY Messages .................................................................................................................................... 307

32

WEB Error Messages ............................................................................................................................311 WEB Messages ...................................................................................................................................... 311

33

WSS Error Messages ............................................................................................................................355 WSS Messages ...................................................................................................................................... 355

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

Preface

This guide describes error messages you may encounter when using the Sun JavaTM System Communications Server 2.0. The error messages described here can also be viewed with the Communications Server Log Viewer.

Who Should Use This Book

The Sun GlassFish Communications Server 2.0 Error Message Reference is intended for developers and administrators who use the Sun GlassFish Communications Server to assemble and deploy distributed and Web-based applications. This guide assumes you are familiar with the following topics:

Java APIs as defined in the Java Servlet, JavaServer PagesTM (JSPTM), Enterprise JavaBeansTM (EJBTM), and Java Database Connectivity (JDBCTM) specifications The SQL structured database query languages Relational database concepts

How This Book Is Organized

This guide is a compilation of messages that you may encounter while running the Communications Server. Each message begins with a message ID, which has a format like the following:
<Subsystem\><IntegerId\>:

The subsystem is identified by the initial characters in the message ID. For example, in JMS0001, the subsystem is JMS. The error messages in this guide are divided into chapters based on the subsystem prefix:

Chapter 1, Unexpected Errors Chapter 2, ACC Error Messages Chapter 3, ACT Error Messages Chapter 4, ADM Error Messages
7

Preface

Chapter 5, CIS Error Messages Chapter 6, CMNUTIL Error Messages Chapter 7, CONF Error Messages Chapter 8, CORE Error Messages Chapter 9, DIAG Error Messages Chapter 10, DPL Error Messages Chapter 11, DTX Error Messages Chapter 12, EEADM Error Messages Chapter 13, EJB Error Messages Chapter 14, IOP Error Messages Chapter 15, JBISE Error Messages Chapter 16, JDO Error Messages Chapter 17, JML Error Messages Chapter 18, JMS Error Messages Chapter 19, JTS Error Messages Chapter 20, LAUNCHER Error Messages Chapter 21, LCM Error Messages Chapter 22, LDR Error Messages Chapter 23, MDB Error Messages Chapter 24, NAM Error Messages Chapter 25, RAR Error Messages Chapter 26, SEC Error Messages Chapter 27, SERVER Error Messages Chapter 28, SGMT Error Messages Chapter 29, SYNC Error Messages Chapter 30, UTIL Error Messages Chapter 31, VRFY Error Messages Chapter 32, WEB Error Messages Chapter 33, WSS Error Messages

The messages defined in this reference guide also include the following information:

Message The brief text description accompanying the numeric message ID when viewed in the Communications Server Log Viewer. Cause Meaning and likely cause of the message. Solutions/Workarounds Instructions on how to address the condition that caused the message to be generated.

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

Preface

Communications Server Documentation Set

The Communications Server documentation set describes deployment planning and system installation. For an introduction to Communications Server, refer to the books in the order in which they are listed in the following table.
TABLE P1 Book Title

Books in the Communications Server Documentation Set

Description

Documentation Center Release Notes

Communications Server documentation topics organized by task and subject. Late-breaking information about the software and the documentation. Includes a comprehensive, table-based summary of the supported hardware, operating system, Java Development Kit (JDKTM), and database drivers. How to get started with the Communications Server product. Installing the software and its components. Deployment of applications and application components to the Communications Server. Includes information about deployment descriptors. Creating and implementing Java Platform, Enterprise Edition (Java EE platform) applications intended to run on the Communications Server that follow the open Java standards model for Java EE components and APIs. Includes information about developer tools, security, debugging, and creating lifecycle modules. Using Java EE 5 platform technologies and APIs to develop Java EE applications. Developing web applications using the Web Service Interoperability Technologies (WSIT). Describes how, when, and why to use the WSIT technologies and the features and options that each technology supports. System administration for the Communications Server, including configuration, monitoring, security, resource management, and web services management. Setting up clusters, working with node agents, and using load balancers. Editing the Communications Server configuration file, domain.xml. Tuning the Communications Server to improve performance. Utility commands available with the Communications Server; written in man page style. Includes the asadmin command line interface.

Quick Start Guide Installation Guide Application Deployment Guide Developers Guide

Java EE 5 Tutorial Java WSIT Tutorial

Administration Guide High Availability Administration Guide Administration Reference Performance Tuning Guide Reference Manual

Preface

Default Paths and File Names

The following table describes the default paths and file names that are used in this book.
TABLE P2 Placeholder

Default Paths and File Names

Description Default Value

as-install

Represents the base installation directory for Communications Server.

SolarisTM and Linux installations, non-root user: users-home-directory/SUNWappserver Solaris and Linux installations, root user: /opt/SUNWappserver Windows, all installations: SystemDrive:\Sun\AppServer

domain-root-dir

Represents the directory containing all domains. Represents the directory for a domain. In configuration files, you might see domain-dir represented as follows: ${com.sun.aas.instanceRoot}

All installations: as-install/domains/ domain-root-dir/domain-dir

domain-dir

instance-dir samples-dir docs-dir

Represents the directory for a server instance. Represents the directory containing sample applications. Represents the directory containing documentation.

domain-dir/instance-dir as-install/samples as-install/docs

Typographic Conventions
The following table describes the typographic changes that are used in this book.
TABLE P3 Typeface

Typographic Conventions
Meaning Example

AaBbCc123

The names of commands, files, and directories, and onscreen computer output

Edit your .login file. Use ls -a to list all files. machine_name% you have mail.

10

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

Preface

TABLE P3 Typeface

Typographic Conventions
Meaning

(Continued)
Example

AaBbCc123

What you type, contrasted with onscreen computer output A placeholder to be replaced with a real name or value Book titles, new terms, and terms to be emphasized (note that some emphasized items appear bold online)

machine_name% su Password: The command to remove a file is rm filename. Read Chapter 6 in the User's Guide. A cache is a copy that is stored locally. Do not save the file.

AaBbCc123 AaBbCc123

Symbol Conventions
The following table explains symbols that might be used in this book.
TABLE P4 Symbol

Symbol Conventions
Description Example Meaning

[]

Contains optional arguments ls [-l] and command options. Contains a set of choices for a -d {y|n} required command option. Indicates a variable reference. Joins simultaneous multiple keystrokes. Joins consecutive multiple keystrokes. Indicates menu item selection in a graphical user interface. ${com.sun.javaRoot} Control-A Ctrl+A+N File New Templates

The -l option is not required. The -d option requires that you use either the y argument or the n argument. References the value of the com.sun.javaRoot variable. Press the Control key while you press the A key. Press the Control key, release it, and then press the subsequent keys. From the File menu, choose New. From the New submenu, choose Templates.

{|}

${ } +

11

Preface

Accessing Sun Resources Online

The docs.sun.com web site enables you to access Sun technical documentation online. You can browse the docs.sun.com archive or search for a specific book title or subject. Books are available as online files in PDF and HTML formats. Both formats are readable by assistive technologies for users with disabilities. To access the following Sun resources, go to http://www.sun.com:

Downloads of Sun products Services and solutions Support (including patches and updates) Training Research Communities (for example, Sun Developer Network)

Third-Party Web Site References

Third-party URLs are referenced in this document and provide additional, related information.
Note Sun is not responsible for the availability of third-party web sites mentioned in this

document. Sun does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Sun will not be responsible or liable for any actual or alleged damage or loss caused or alleged to be caused by or in connection with use of or reliance on any such content, goods, or services that are available on or through such sites or resources.

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 full document title and part number. The part number is a 7-digit or 9-digit number that can be found on the book's title page or in the document's URL. For example, the part number of this book is 821-0189.

12

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

C H A P T E R

Unexpected Errors

This chapter provides general advice to help you deal with unexpected errors.

Analyze the System

Unexpected errors generally result from problems in the configuration (system configuration, JVM configuration, server configuration or application-level configuration). They can also occur when the system runs out of memory, or when there is a system crash, hardware failure, or power failure. To find cases in which the error has been reported, search for occurrences of the error code (for example, DIAG9001) at http://www.sunsolve.sun.com. In the event of a general system failure, the error message can generally be ignored, because the error is unlikely to reoccur when the system is working properly. If system memory is an issue, consult the Performance Tuning Guide for suggestions on optimizing your configuration. (Consider taking other actions to remedy the problem as well, such as adding memory or decreasing system load.) When the system is not the cause, the problem may be due to the configuration settings. If you have recently made changes, consider backing them out.

Detailed information from the body of the message Stack trace information System logs

13

14

C H A P T E R

ACC Error Messages

This chapter describes messages for errors with a ACC prefix.

ACC Messages
ACC001

Using ClientContainer file: [{0}]. Cause: TBD

Solution: TBD ACC003

Application threw an exception. Cause: TBD

Solution: TBD ACC004

Login error: Incorrect login and/or password. Cause: TBD

Solution: TBD ACC005

Failed to load application client descriptors for: [{0}] Cause: TBD

Solution: TBD
15

ACC Messages

ACC006

No application client descriptor defined for: [{0}] Cause: TBD

Solution: TBD ACC007

Initiating Login ... Cause: TBD

Solution: TBD ACC008

Using default callback ... Cause: TBD

Solution: TBD ACC009

Load Application Class: [{0}] Cause: TBD

Solution: TBD ACC010

Make sure the server port is not disabled and that you are looking up a valid name Cause: TBD
Solution: TBD ACC011

Duplicated display name in multiple application. Please try to use "-mainclass <appClass-name>" option. Cause: TBD
Solution: TBD ACC012
16 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

ACC Messages

For multiple application, user must specify main class name or display name using "-mainclass <appClass-name>" or "-name <display name>" option. Cause: TBD
Solution: TBD ACC013

ORB port number: [{0}] Cause: TBD

Solution: TBD ACC014

ORB host name: [{0}] Cause: TBD

Solution: TBD ACC013

ORB port number: [{0}] Cause: TBD

Solution: TBD ACC014

ORB host name: [{0}] Cause: TBD

Solution: TBD ACC015

Error in XML file: [{0}]. Please check your XML and make sure that your XML and DTD files exist in the correct location (refer to the user doc.) {1} Cause: TBD
Solution: TBD ACC016

Chapter 2 ACC Error Messages

17

ACC Messages

Client Container xml: [{0}] not found or unable to read. Cause: TBD
Solution: TBD ACC017

Either SSL KeyStore and TrustStore are not specified or KeyStore and TrustStore initialization failed. Cause: TBD
Solution: TBD ACC018

Failed to create client side logger Cause: TBD

Solution: TBD ACC019

Failed to load application client descriptors for: {0} Cause: TBD

Solution: TBD ACC020

For applications containing multiple appclient jars, please specify -mainclass or -name option. Cause: TBD
Solution: TBD ACC021

Error from Handler with regards to DTD resolution {0} Cause: TBD
Solution: TBD ACC022

18

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

ACC Messages

Warning from Handler during DTD resolution {0} Cause: TBD

Solution: TBD ACC023

The best practice in case of appclients is to set the endpoints as <target-server> elements in sun-acc.xml. Please avoid using the com.sun.appserv.iiop.endpoints property for appclients. Cause: TBD
Solution: TBD

Chapter 2 ACC Error Messages

19

20

C H A P T E R

ACT Error Messages

This chapter describes messages for errors with a ACT prefix.

ACT Messages
ACT5001

Error occured in image loading =[{0}] Cause: TBD

Solution: TBD ACT5002

Invalid outputstream in TextEditor! not saving!. Cause: TBD

Solution: TBD ACT5003

TextEditor Save Operation failed with Exception. Cause: TBD

Solution: TBD ACT5004

Bad .mime.types entry: [{0}] Cause: TBD

Solution: TBD
21

ACT Messages

ACT5005

Exception parsing mailcap file Cause: TBD

Solution: TBD

22

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

C H A P T E R

ADM Error Messages

This chapter describes messages for errors with a ADM prefix.

ADM Messages
ADM023

JMX Implementation Version:[{0}] Cause: TBD

Solution: TBD ADM024

MBeanServer ID:[{0}] Cause: TBD

Solution: TBD ADM025

MBeanServer Implementation Classname:[{0}] Cause: TBD

Solution: TBD ADM026

Using HtmlAdaptorServer for viewing MBeans, its state is:[{0}] Cause: TBD
Solution: TBD
23

ADM Messages

ADM027

Using HtmlAdaptorServer for viewing MBeans, its port is: [{0}]. Connect the Browser to this port Cause: TBD
Solution: TBD ADM028

The MBean with ObjectName[{0}] was created anew and registered with the MBeanServer Cause: TBD
Solution: TBD ADM029

The MBean with ObjectName[{0}] already exists, accessing its management interface Cause: TBD
Solution: TBD ADM030

The ObjectName [{0}] cant be registered as the configuration does not have it Cause: TBD
Solution: TBD ADM031

Html Adaptor Server stopped Cause: TBD

Solution: TBD ADM032

The System MBeanServer released Cause: TBD

Solution: TBD ADM0001
24 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

ADM Messages

MBeanServer initialized successfully Cause: TBD

Solution: TBD ADM0002

System MBean initialized:[{0}] Cause: TBD

Solution: TBD ADM0003

MBeanServer initialization failed Cause: TBD

Solution: TBD ADM0004

MBeanServer method invocation:[{0}] Cause: TBD

Solution: TBD ADM0005

Timestamp files for configuration created for:[{0}] Cause: TBD

Solution: TBD ADM0006

Timestamp files not created - Detailed Message: Cause: TBD

Solution: TBD ADM0007

Chapter 4 ADM Error Messages

25

ADM Messages

The folder [{0}] where admin server uploads the remote files for deployment already exists. This is probably because admin-server could not delete this folder during last shutdown. This should not be cause of any problem Cause: TBD
Solution: TBD ADM0008

Admin Server could not create the temporary folder for internal purposes at [{0}]. This may cause problems with deployment etc. It is alright if some space is freed at this location without shutting down the Admin Server. Also look at the operating systems artefacts like file permissions etc. to resolve the problem Cause: TBD
Solution: TBD ADM0009

Created temporary folder at [{0}] for internal purpose Cause: TBD

Solution: TBD ADM0010

Deleted temporary folder at [{0}] successfully Cause: TBD

Solution: TBD ADM0011

Could not reregister HttpListener with DomainRegistry. Cause: TBD

Solution: TBD ADM0012

A Domain Registry Exception occured. Details are: Cause: TBD

Solution: TBD
26 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

ADM Messages

ADM0013

A config exception occurred. Details are: Cause: TBD

Solution: TBD ADM0014

The temporary folder required by the administrative console (graphical user interface) could not be created at [{0}]. This will pose some problems while trying to deploy archives from the console. Some space can be freed at this location without restarting the administrative server to correct this probleme. Cause: TBD
Solution: TBD ADM0015

The temporary folder required by the administrative console (graphical user interface) was created at [{0}]. This is where the archives to be deployed will be uploaded. Cause: TBD
Solution: TBD ADM0016

Unable to determine java home. This suggests that you are using a version of J2EE plugin incompatible with administration server. Cause: TBD
Solution: TBD ADM0017

Admin server could not be initialized with java home from j2ee plugin. Cause: TBD
Solution: TBD ADM0018

Chapter 4 ADM Error Messages

27

ADM Messages

Support for batched reconfiguration is disabled. Cause: TBD

Solution: TBD ADM0019

Admin service is running without server context. Cause: TBD

Solution: TBD ADM0020

Following is the information about the JMX MBeanServer used: Cause: TBD
Solution: TBD ADM0021

MBeanServer Implementation Name:[{0}] Cause: TBD

Solution: TBD ADM0022

MBeanServer Implementation Vendor:[{0}] Cause: TBD

Solution: TBD ADM0033

Admin Service configuration could not be read and Admin Service type is being defaulted to [{0}] Cause: TBD
Solution: TBD ADM0034

28

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

ADM Messages

Preinvoke failed for MBeanServer interceptor [{0}]. Cause: TBD

Solution: TBD ADM0035

Preinvoke exception for MBeanServer interceptor. Cause: TBD

Solution: TBD ADM0036

Postinvoke failed for MBeanServer interceptor [{0}]. Cause: TBD

Solution: TBD ADM0037

Preinvoke exception for MBeanServer interceptor. Cause: TBD

Solution: TBD ADM0038

A read-write version of configuration files could not be loaded. Server can not be administered. Root cause: [{0}] Cause: TBD
Solution: TBD ADM0039

Read/Write version of configuration files not loaded because of exception. Cause: TBD
Solution: TBD ADM0040

Chapter 4 ADM Error Messages

29

ADM Messages

Config context for runtime initialized to [{0}] Cause: TBD

Solution: TBD ADM0041

Config context for admin initialized to [{0}] Cause: TBD

Solution: TBD ADM0042

Log Manager MBean could not be registered, the changes to logger log levels will be effective after server restart. Cause: TBD
Solution: TBD ADM0043

Log Manager MBean registration aborted because of exception. Cause: TBD

Solution: TBD ADM0044

Admin authentication using realm [{0}] did not work. Cause: TBD
Solution: TBD ADM0045

Error in admin authentication. Cause: TBD

Solution: TBD ADM0046

30

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

ADM Messages

Error during callflow agent creation. Cause: TBD

Solution: TBD ADM0101

Error getting manual changes Cause: TBD

Solution: TBD ADM0102

Starting a thread for tracking manual changes Cause: TBD

Solution: TBD ADM0103

Stopping the thread for tracking manual changes Cause: TBD

Solution: TBD ADM1001

New Server Instance [{0}] created successfully Cause: TBD

Solution: TBD ADM1002

Create Instance failed Cause: TBD

Solution: TBD ADM1003

Deleted Server Instance [{0}] successfully Cause: TBD

Solution: TBD
Chapter 4 ADM Error Messages 31

ADM Messages

ADM1004

Delete Instance failed Cause: TBD

Solution: TBD ADM1006

Uploading the file to:[{0}] Cause: TBD

Solution: TBD ADM1007

Uploaded the remote file at: [{0}] Cause: TBD

Solution: TBD ADM1008

Upload falied for file at: [{0}] Cause: TBD

Solution: TBD ADM1009

Cant get MBeanInfo for: [{0}] Cause: TBD

Solution: TBD ADM1010

Preparing to download the file:[{0}] Cause: TBD

Solution: TBD ADM1011

32

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

ADM Messages

Starting the download ... Cause: TBD

Solution: TBD ADM1012

Downloading the file to client failed Cause: TBD

Solution: TBD ADM1021

Deploying the archive:[{0}] Cause: TBD

Solution: TBD ADM1022

Deployment failed - Detailed Message: Cause: TBD

Solution: TBD ADM1023

Undeploying the deployed archive:[{0}] Cause: TBD

Solution: TBD ADM1024

Undeployment failed - Detailed Message: Cause: TBD

Solution: TBD ADM1025

Redeploying the deployed archive:[{0}] Cause: TBD

Solution: TBD
Chapter 4 ADM Error Messages 33

ADM Messages

ADM1026

Redeployment failed - Detailed Message: Cause: TBD

Solution: TBD ADM1027

Listing entities Cause: TBD

Solution: TBD ADM1028

List operation failed - Detailed Message: Cause: TBD

Solution: TBD ADM1029

Creating resource:[{0}] Cause: TBD

Solution: TBD ADM1030

Resource creation failed - Detaile Message: Cause: TBD

Solution: TBD ADM1031

Deleting resource:[{0}] Cause: TBD

Solution: TBD ADM1032

34

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

ADM Messages

Resource creation failed - Detaile Message: Cause: TBD

Solution: TBD ADM1033

Deleting JDBC Connection Pool: [{0}] Cause: TBD

Solution: TBD ADM1034

Deletion of Connection Pool failed - Detailed Message: Cause: TBD

Solution: TBD ADM1036

Created lifecycle module:[{0}] Cause: TBD

Solution: TBD ADM1037

Lifecycle module creation failed - Detailed Message: Cause: TBD

Solution: TBD ADM1038

Deleted lifecycle module:[{0}] Cause: TBD

Solution: TBD ADM1039

Lifecycle module deletion failed - Detailed Message: Cause: TBD

Solution: TBD
Chapter 4 ADM Error Messages 35

ADM Messages

ADM1040

Client-jar location:[{0}] Cause: TBD

Solution: TBD ADM1041

Sent the event to instance:[{0}] Cause: TBD

Solution: TBD ADM1042

Status of dynamic reconfiguration event processing:[{0}] Cause: TBD

Solution: TBD ADM1043

Response of instance on listening event:[{0}] Cause: TBD

Solution: TBD ADM1044

This event will not be applied:[{0}]. This is because it was applied as a part of a prior event. Cause: TBD
Solution: TBD ADM1045

Sent the event:[{0}] Cause: TBD

Solution: TBD ADM1046
36 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

ADM Messages

A change notification was not handled successfully. The server will need a restart for the change to be effective. Cause: TBD
Solution: TBD ADM1047

Setting jvm debug options in configuration file failed Cause: TBD

Solution: TBD ADM1048

Stopping the server instance:[{0}] Cause: TBD

Solution: TBD ADM1049

Starting the server instance:[{0}] Cause: TBD

Solution: TBD ADM1050

Starting instance [{0}] failed. See instance logs for more details Cause: TBD
Solution: TBD ADM1051

Debug options for the instance are set to:[{0}] Cause: TBD
Solution: TBD ADM1052

Chapter 4 ADM Error Messages

37

ADM Messages

Beginning to check status of START instance:[{0}] Cause: TBD

Solution: TBD ADM1053

Beginning to check status of STOP instance:[{0}] Cause: TBD

Solution: TBD ADM1054

Checking of START instance timedout for: [{0}] Cause: TBD

Solution: TBD ADM1055

Checking of STOP instance timedout for: [{0}] Cause: TBD

Solution: TBD ADM1056

Successfully started instance: [{0}] Cause: TBD

Solution: TBD ADM1057

Successfully stopped instance: [{0}] Cause: TBD

Solution: TBD ADM1058

Restarting the server instance : [{0}] Cause: TBD

Solution: TBD
38 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

ADM Messages

ADM1059

Security check failed - Detailed Message: Cause: TBD

Solution: TBD ADM1060

isDebug check failed. Detailed Message: Cause: TBD

Solution: TBD ADM1061

Skipping notifications because instance [{0}] is not running. Cause: TBD

Solution: TBD ADM1062

The temporary file uploaded at [{0}] deleted. This does not necessarily imply that the deployment request from an administrative interface was served successfully Cause: TBD
Solution: TBD ADM1063

The temporary file [{0}] used to upload before deployment could not be deleted, most likely because the file handle is occupied by admin server runtime. If a file with the same name is to be deployed again, this file will be overwritten during upload, which should not be a problem in future deployments. Please try deleting this file, if you see this message. Cause: TBD
Solution: TBD ADM1064

Chapter 4 ADM Error Messages

39

ADM Messages

The upload file at [{0}] exists and will be overwritten. Cause: TBD
Solution: TBD ADM1065

Beginning to stop the domain [{0}]. The administrative server will also be shutdown alongwith all the other running non administrative SunONE Application Server instances Cause: TBD
Solution: TBD ADM1066

Beginning to stop the domain [{0}]. The administrative server will not be shutdown. Only the non administrative SunONE Application Server instances will be shutdown Cause: TBD
Solution: TBD ADM1067

Deletion of JMS service instance failed. Cause: TBD

Solution: TBD ADM1068

Stopping instance [{0}] failed. See instance logs for more details Cause: TBD
Solution: TBD ADM1069

Starting the server instance failed. Detailed message: Cause: TBD

Solution: TBD ADM1070
40 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

ADM Messages

Starting the server instance:[{0}] in debug mode with JPDA port number [{1}] Cause: TBD
Solution: TBD ADM1071

Ownership of deployment directories could not be changed. [{0}] Cause: TBD

Solution: TBD ADM1072

Size of the file [{0}] could not be verified Cause: TBD

Solution: TBD ADM1073

Error while trying to determine fully qualified name of this host. Cause: TBD
Solution: TBD ADM1074

Could not determine fully qualified name of current host, will use localhost. Cause: TBD
Solution: TBD ADM1075

Error on listening event:[{0}] Cause: TBD

Solution: TBD ADM1076

Chapter 4 ADM Error Messages

41

ADM Messages

Could not determine port to form web service endpoint, will use default port [{0}]. Cause: TBD
Solution: TBD ADM1077

IOException while accessing autostart file. Cause: TBD

Solution: TBD ADM1078

Autostart could not be enabled. Access to file [{0}] failed with error [{1}]. Cause: TBD
Solution: TBD ADM1079

Initialization of AMX MBeans successful Cause: TBD

Solution: TBD ADM1080

Initialization of AMX MBeans failed. Detailed message: Cause: TBD

Solution: TBD ADM1081

Creating the application reference [{0}] Cause: TBD

Solution: TBD ADM1082

42

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

ADM Messages

Creating the application reference failed - Detailed Message: Cause: TBD

Solution: TBD ADM1083

Deleting the application reference [{0}] Cause: TBD

Solution: TBD ADM1084

Deleting the application reference failed - Detailed Message: Cause: TBD

Solution: TBD ADM1085

Starting the application [{0}] Cause: TBD

Solution: TBD ADM1086

Starting the application failed - Detailed Message: Cause: TBD

Solution: TBD ADM1087

Stopping the application [{0}] Cause: TBD

Solution: TBD ADM1088

Stopping the application failed - Detailed Message: Cause: TBD

Solution: TBD
Chapter 4 ADM Error Messages 43

ADM Messages

ADM1089

A change notification was not handled successfully. Details about each server instance and its corresponding notification success status [{0}]. Cause: TBD
Solution: TBD ADM1090

A change notification was not handled successfully. Details about each server instance and its corresponding notification exceptions and messages [{0}]. Cause: TBD
Solution: TBD ADM1500

Initializing the lifecycle module for JMX Connector Cause: TBD

Solution: TBD ADM1501

Here is the JMXServiceURL for the JMXConnectorServer: [{0}]. This is where the remote administrative clients should connect using the standard JMX Connectors. Cause: TBD
Solution: TBD ADM1502

Status of System JMX Connector: Active = [{0}] Cause: TBD

Solution: TBD ADM1503

The system-jmx-connector port [{0}] is not enabled to start with server startup. Thus JSR 160 JMX Connector will not be started. Cause: TBD
Solution: TBD
44 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

ADM Messages

ADM1504

Here is the JMXServiceURL for the Standard JMXConnectorServer: [{0}]. This is where the remote administrative clients should connect using the standard JMX connectors Cause: TBD
Solution: TBD ADM1506

Status of Standard JMX Connector: Active = [{0}] Cause: TBD

Solution: TBD ADM1509

JSR 160 JMX Connector Server at address [{0}] is now stopping Cause: TBD
Solution: TBD ADM1510

JSR 160 JMX Connector Server is now shutdown Cause: TBD

Solution: TBD ADM5001

Root Monitoring MBean [{0}] registered successfully Cause: TBD

Solution: TBD ADM5002

Attempt to register non-compliant monitoring mbean [{0}] Cause: TBD

Solution: TBD ADM5003
Chapter 4 ADM Error Messages 45

ADM Messages

MBean Server initialization for monitoring failed. Cause: TBD

Solution: TBD ADM5004

Monitoring channel initialization error. Monitoring will be disabled. Cause: TBD

Solution: TBD ADM5005

Initialization of monitoring failed for component [{0}] Cause: TBD

Solution: TBD ADM5006

Monitoring MBean for component [{0}] could not be purged. Cause: TBD
Solution: TBD ADM5007

Monitoring MBean could not be purged. Cause: TBD

Solution: TBD ADM5008

User ORB monitoring component name [{0}] is in use. Cause: TBD

Solution: TBD ADM5009

ORB monitoring mbean named [{0}] registered Cause: TBD

Solution: TBD
46 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

ADM Messages

ADM5010

Invalid hint [{0}] for user ORB monitoring component name will be ignored. Cause: TBD
Solution: TBD ADM5601

Multicast event from instance [{0}] to [{1}] not supported. Cause: TBD
Solution: TBD ADM5602

Event handler initialization error [{0}] Cause: TBD

Solution: TBD ADM5603

Event listener error [{0}] Cause: TBD

Solution: TBD ADM5604

Processing config change [{0}] Cause: TBD

Solution: TBD ADM5605

Config Change or its xpath is null! Ignoring [{0}] Cause: TBD

Solution: TBD ADM5606

Chapter 4 ADM Error Messages

47

ADM Messages

Extracting changes to [{0}] Cause: TBD

Solution: TBD ADM5607

Config change xpath is [{0}] Cause: TBD

Solution: TBD ADM5608

Purging NO-OP event [{0}] Cause: TBD

Solution: TBD ADM5609

Unknown server context type [{0}]. Unable to set the config context from the event multicaster. Cause: TBD
Solution: TBD ADM5610

List of updated attributes is null for xpath [{0}]. Cause: TBD

Solution: TBD ADM5611

Attempt to extract token number [{1}] from [{0}] when it contains only [{2}] tokens. Cause: TBD
Solution: TBD ADM5612

48

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

ADM Messages

Attempt to replace config context in ConfigFactory Failed. Cause: TBD

Solution: TBD ADM5613

The key type of the following class, is not allowed in admin event: [{0}] Cause: TBD
Solution: TBD ADM5614

The object key in the current event is malformed : [{0}] Cause: TBD
Solution: TBD ADM5615

The following object name is malformed: [{0}] Cause: TBD

Solution: TBD ADM5616

Admin channel did not return RMI client. Could not reset restart required. Cause: TBD
Solution: TBD ADM5617

Unexpected error during resetting of restart required flag. Cause: TBD

Solution: TBD ADM5618

Chapter 4 ADM Error Messages

49

ADM Messages

Restart required status is not updated correctly for the following configuration change (XPath is [{0}]). Cause: TBD
Solution: TBD ADM5619

Target [{0}] could not be resolved. Invalid Name. Cause: TBD

Solution: TBD ADM5620

Target [{0}] does not contain any servers. Restart required is not set for this target. Cause: TBD
Solution: TBD ADM5801

Admin server channel creation failed. Cause: TBD

Solution: TBD ADM5802

Error reading key file. Cause: TBD

Solution: TBD ADM5803

Error writing key file. Cause: TBD

Solution: TBD ADM5804

50

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

ADM Messages

Client host is null. Cause: TBD

Solution: TBD ADM5805

Local access to admin server channel. Cause: TBD

Solution: TBD ADM5806

Address mismatch: client/[{0}] server/[{1}] Cause: TBD

Solution: TBD ADM5807

Unable to determine local host. Cause: TBD

Solution: TBD ADM5808

Shared key mismatch: client/[{0}] server/[{1}] Cause: TBD

Solution: TBD ADM5809

Error sending reconfig signal. Cause: TBD

Solution: TBD ADM5810

Attempt to initialize admin channel client with null arguments. Cause: TBD
Solution: TBD
Chapter 4 ADM Error Messages 51

ADM Messages

ADM5811

Admin channel auto refresh thread interrupted. Cause: TBD

Solution: TBD ADM5812

Event notification fialed. Cause: TBD

Solution: TBD ADM5813

Event notification retry failed. Cause: TBD

Solution: TBD ADM5814

File [{0}] does not exist or can not be read. Cause: TBD
Solution: TBD ADM5815

Error initializing admin channel client. Cause: TBD

Solution: TBD ADM5816

Communication error over admin channel [{0}]. Cause: TBD

Solution: TBD ADM5817

52

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

ADM Messages

Dynamic Reconfiguration module for web tier could not be enabled. Cause: TBD
Solution: TBD ADM5818

Shared key file (last modified [{0}) is older than channel file (last modified [{1}]). Cause: TBD
Solution: TBD ADM6001

Remote client communication started Cause: TBD

Solution: TBD ADM6002

Received remote administration request Cause: TBD

Solution: TBD ADM6003

Invoked the mbean:[{0}] Cause: TBD

Solution: TBD ADM6004

Remote invocation failed - Detailed Message: Cause: TBD

Solution: TBD ADM6005

Chapter 4 ADM Error Messages

53

ADM Messages

Got attribute from the mbean:[{0}] Cause: TBD

Solution: TBD ADM6006

Get attribute failed - Detailed Message: Cause: TBD

Solution: TBD ADM6007

Set attribute in the mbean:[{0}] Cause: TBD

Solution: TBD ADM6008

Set attribute failed - Detailed Message: Cause: TBD

Solution: TBD ADM6005

Got attributes from the mbean:[{0}] Cause: TBD

Solution: TBD ADM6006

Get attributes failed - Detailed Message: Cause: TBD

Solution: TBD ADM6007

Set attributes in the mbean:[{0}] Cause: TBD

Solution: TBD
54 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

ADM Messages

ADM6008

Set attributes failed - Detailed Message: Cause: TBD

Solution: TBD ADM7001

Name of the attribute:[{0}] Cause: TBD

Solution: TBD ADM7002

Name of the instance:[{0}] Cause: TBD

Solution: TBD ADM7003

JAVA_HOME value can not be derived from admin servers configuration file, instance can not be created Cause: TBD
Solution: TBD ADM7003

Instance creation failed - Detailed Message: Cause: TBD

Solution: TBD ADM7004

Executing the command in a subprocess:[{0}] Cause: TBD

Solution: TBD ADM7005
Chapter 4 ADM Error Messages 55

ADM Messages

Stopping the Server Instance failed. Deleting the configuration folder, please kill the processes Cause: TBD
Solution: TBD ADM7006

Process of finding out free port on this system failed. Generally not being able to find a free port indicates a current or potential problem. Administration server will try to proceed by using default ports. See dtd/manuals for default port assignments Cause: TBD
Solution: TBD ADM7007

Permanent certs in certdb:[{0}] Cause: TBD

Solution: TBD ADM7008

CA certs in certdb:[{0}] Cause: TBD

Solution: TBD ADM7009

Cert nickname:[{0}] Cause: TBD

Solution: TBD ADM7010

Unexpected exception or error. Cause: TBD

Solution: TBD ADM7011
56 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

ADM Messages

Although instance {0} was removed, it was not deleted completely. Some files or directories may have been in use at the time. Please manually delete the instance directory to ensure complete deletion. Cause: TBD
Solution: TBD ADM2001

Attribute [{0}] is not found Cause: TBD

Solution: TBD ADM2002

Can not get MBean Info. Cause: TBD

Solution: TBD ADM2003

GenericConfigurator: getting attribute for dotted name: [{0}] Cause: TBD

Solution: TBD ADM2004

GenericConfigurator: setting attribute for dotted name: [{0}]=[{1}] Cause: TBD

Solution: TBD ADM2005

ConfigMBeanBase:getting value for attribute [{0}] Cause: TBD

Solution: TBD ADM2006

Chapter 4 ADM Error Messages

57

ADM Messages

ConfigMBeanBase:set attribute [{0}]=[{1}] Cause: TBD

Solution: TBD ADM2007

ConfigMbeanBase:Returned value for attribute [{0}] is [{1}](string)/[{2}](after conversion) Cause: TBD

Solution: TBD ADM2008

ConfigMBeanBase: getting property [{0}] Cause: TBD

Solution: TBD ADM2009

ConfigMBeanBase: setting property [{0}]=[{1}] Cause: TBD

Solution: TBD ADM2010

ConfigMBeanBase:getting default value for attribute [{0}] Cause: TBD

Solution: TBD ADM2011

Apply Changes failed for admin instance. Root cause: [{0} Cause: TBD
Solution: TBD ADM2012

58

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

ADM Messages

Check to determine whether changes can be applied failed, assuming can not apply changes. Root cause: [{0}] Cause: TBD
Solution: TBD ADM2013

Unable to use manual changes to configuration. Root Cause: [{0}] Cause: TBD
Solution: TBD ADM2014

Unable to determine whether admin instance configuration has been changed and not applied. Root cause: [{0}] Cause: TBD
Solution: TBD ADM2015

Get config bean by xpath: [{0}] Cause: TBD

Solution: TBD ADM2016

Get list continuations for dotted name: [{0}] Cause: TBD

Solution: TBD ADM2017

Malformed dotted name: [{0}] Cause: TBD

Solution: TBD ADM2018

Chapter 4 ADM Error Messages

59

ADM Messages

Exception during List names continuation operation. Detailed message: Cause: TBD
Solution: TBD ADM2019

Getting default values for instance: {0}; MBean Type: {1} Cause: TBD
Solution: TBD ADM2020

Error initializing dotted Names Cause: TBD

Solution: TBD ADM2021

MBean class [{0}] using is config id [{1}] Cause: TBD

Solution: TBD ADM3000

Exception adding password alias {0} Cause: TBD

Solution: TBD ADM3000

Exception removing password alias {0} Cause: TBD

Solution: TBD ADM3000

Exception updating password for alias {0} Cause: TBD

Solution: TBD
60 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

ADM Messages

ADM3000

Exception listing password aliases Cause: TBD

Solution: TBD ADM8001

Failed to publish Web Service {0} to registries. Cause: TBD

Solution: TBD ADM8002

Failed to publish Web Service to registries. Cause: TBD

Solution: TBD ADM8003

Web Service {0} published successfully to registries. Cause: TBD

Solution: TBD ADM8004

Failed to unpublish Web Service {0} from registries. Cause: TBD

Solution: TBD ADM8005

Failed to unpublish Web Service from registries. Cause: TBD

Solution: TBD ADM8006

Chapter 4 ADM Error Messages

61

ADM Messages

Unpublished Web Service {0} from registries. Cause: TBD

Solution: TBD ADM8007

Cannot find a connector module of type {0}. Deploy a connector module with type {0} Cause: TBD
Solution: TBD ADM8008

Registry type unspecified. Registry type has to be either {0} or {1}. Cause: TBD
Solution: TBD ADM8009

Cannot add Registry Location to Web Service End point in domain.xml Cause: TBD
Solution: TBD ADM8010

Invalid Web Service Name {0}. Cannot publish Web Service to registries. Cause: TBD
Solution: TBD ADM8011

WSDL not found for Web Service {0}. Cannot publish Web Service to registries. Cause: TBD
Solution: TBD ADM8012

62

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

ADM Messages

Registry Location {0} not found. Cannot publish Web Service to it. Cause: TBD
Solution: TBD ADM8013

Registry Location not found. Cannot publish Web Service to it. Cause: TBD
Solution: TBD ADM8014

Web Service {0} not published. Look at preceding errors for probable causes. Cause: TBD
Solution: TBD ADM8015

Invalid Web Service Name {0}. Cannot publish Web Service from registries. Cause: TBD
Solution: TBD ADM8016

Registry Location {0} not found. Cannot unpublish Web Service from it. Cause: TBD
Solution: TBD ADM8017

Registry Location not found. Cannot unpublish Web Service to it. Cause: TBD
Solution: TBD ADM8018

Web Service {0} not unpublished. Look at preceding errors for probable causes. Cause: TBD
Solution: TBD
Chapter 4 ADM Error Messages 63

ADM Messages

ADM8019

Cannot list registry location. Cause: TBD

Solution: TBD ADM8020

WSDL not found for Web Service {0}. Cause: TBD

Solution: TBD ADM8021

Access URI for Web Serivce {0} is {1}. Cause: TBD

Solution: TBD ADM8022

Cannot create Service Object in the registry. Cause: TBD

Solution: TBD ADM8023

Cannot create Service Binding Object in the registry. Cause: TBD

Solution: TBD ADM8024

Failed to create Slots to categorize categories in the registry. Cause: TBD

Solution: TBD ADM8025

64

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

ADM Messages

Failed to create Classification and ClassificationScheme Object in the registry/ Cause: TBD
Solution: TBD ADM8026

Organization {0} successfully published to registry. Cause: TBD

Solution: TBD ADM8027

Organization {0} could not be published to registry. Look at the following exceptions for probable causes. Cause: TBD
Solution: TBD ADM8028

Cannot find Classification Scheme for Web Service {0}. Cannot unpublish from registry. Please unpublish manually. Cause: TBD
Solution: TBD ADM8029

Issuing request to unpublish {0} from Organization {1}. Cause: TBD

Solution: TBD ADM8030

Failed to unpublish Web Service from Registry. Cause: TBD

Solution: TBD ADM8031

Chapter 4 ADM Error Messages

65

ADM Messages

Failed to delete Classification Scheme Object {0} from the registry. Please delete manually. Cause: TBD
Solution: TBD ADM8032

Deleted Classification Scheme Object {0} successfully for Web Service {1}. Cause: TBD
Solution: TBD ADM11001

Error creating table {0} as table already exists Cause: TBD

Solution: TBD ADM11002

Error creating table {0}. Most likely cause is that table already exists. Please look at the following exception. Cause: TBD
Solution: TBD ADM11003

Error enabling callflow. Cause: TBD

Solution: TBD ADM11004

Failed getting a connection to the callflow database Cause: TBD

Solution: TBD ADM11005

66

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

ADM Messages

Error executing query request information to the database. Cause: TBD

Solution: TBD ADM11006

Error executing query callstack information to the database. Cause: TBD

Solution: TBD ADM11007

Error executing query pie information to the database. Cause: TBD

Solution: TBD ADM11008

ClearData disabled. Turn Call Flow off before calling clearData. Cause: TBD
Solution: TBD ADM11009

CallFlow enable successful. Cause: TBD

Solution: TBD ADM11010

CallFlow disable successful Cause: TBD

Solution: TBD ADM11011

Call flow request start operation failed. Cause: TBD

Solution: TBD
Chapter 4 ADM Error Messages 67

ADM Messages

ADM11012

Call flow add request info operation failed. Cause: TBD

Solution: TBD ADM11013

Adding request information is disallowed after request initialization is completed. Request initialization is completed during the first startTime operation. Cause: TBD
Solution: TBD ADM11014

Call flow request end operation failed. Cause: TBD

Solution: TBD ADM11015

Call flow start time operation failed. Cause: TBD

Solution: TBD ADM11016

Call flow end time operation failed. Cause: TBD

Solution: TBD ADM11017

Call flow EJB method start operation failed. Cause: TBD

Solution: TBD ADM11018
68 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

ADM Messages

Call flow EJB method end operation failed. Cause: TBD

Solution: TBD ADM11019

Call flow web method start operation failed. Cause: TBD

Solution: TBD ADM11020

Call flow web method end operation failed. Cause: TBD

Solution: TBD ADM11021

Call flow asynchronous writer thread interrupted. Cause: TBD

Solution: TBD ADM11022

Database write operation by call flow asynchronous thread failed. Cause: TBD
Solution: TBD ADM11023

Data transfer to call flow asynchronous thread interrupted. Cause: TBD

Solution: TBD

Chapter 4 ADM Error Messages

69

70

C H A P T E R

CIS Error Messages

This chapter describes messages for errors with a CIS prefix.

CIS Messages
CIS0001

EndPoint: [{0}] Cause: TBD

Solution: TBD CIS0002

ConnectException thrown from the Acceptor constructor while creating serverConnection Cause: TBD
Solution: TBD CIS0003

Unable to obtain the Endpoint for host [{0}], port [{1,number,integer}] Cause: TBD
Solution: TBD CIS0004

71

CIS Messages

SecurityException thrown while waiting for the forked thread to join Cause: TBD
Solution: TBD CIS0005

Going to wait mode since the main thread asked us to stop accepting Cause: TBD
Solution: TBD CIS0006

Coming out from wait mode since the main thread asked us to wake up and start accepting Cause: TBD
Solution: TBD CIS0007

Thread [{0}], port [{1,number,integer}] going into indefinite accept Cause: TBD
Solution: TBD CIS0008

Thread [{0}], port [{1,number,integer}] going into timedout accept Cause: TBD
Solution: TBD CIS0009

ConnectException thrown while accepting on thread [{0}] Cause: TBD

Solution: TBD CIS0010

72

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

CIS Messages

TooManyTasksException thrown while adding to the queue Cause: TBD

Solution: TBD CIS0011

QueueClosedException thrown while adding to the queue Cause: TBD

Solution: TBD CIS0012

Host: [{0}] Port: [{1,number,integer}] ThreadCount: [{2,number,integer}] Timeout: [{3,number,integer}] Cause: TBD
Solution: TBD CIS0013

Error in closing derInputStream Cause: TBD

Solution: TBD CIS0014

Unable to get Certificate factory of type X.509 Cause: TBD

Solution: TBD CIS0015

ChannelManager: Creating ServerChannel at local: [{0}] certname: [{1}] sslVersion: [{2,number,integer}] ssl2Ciphers: [{3}] ssl3Ciphers: [{4}] tlsRollback: [{5}] backlog: [{6,number,integer}] Cause: TBD
Solution: TBD CIS0016
Chapter 5 CIS Error Messages 73

CIS Messages

Exception in ChannelManager::poll() Cause: TBD

Solution: TBD CIS0017

Creating SSL connection to remote: [{0}] certname: [{1}] sslVersion: [{2,number,integer}] [{3,number,integer}] [{4,number,integer}] [{5}] Cause: TBD
Solution: TBD CIS0018

Created SSL connection to remote: [{0}] certname: [{1}] sslVersion: [{2,number,integer}] [{3,number,integer}] [{4,number,integer}] [{5}] Cause: TBD
Solution: TBD CIS0019

channel: [{0}] isSSLConnection: [{1}] Cause: TBD

Solution: TBD CIS0020

MaxSize in connection list: [{0,number,integer}] Cause: TBD

Solution: TBD CIS0021

Creating new connection. currentSize: [{0,number,integer}] maxSize: [{1,number,integer}] Cause: TBD

Solution: TBD CIS0022
74 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

CIS Messages

Connection: [{0}] Cause: TBD

Solution: TBD CIS0023

Added newly created connection to the connection array Cause: TBD

Solution: TBD CIS0024

CurrentSize incremented here = [{0,number,integer}] Cause: TBD

Solution: TBD CIS0025

Returning already created connection Cause: TBD

Solution: TBD CIS0026

PeerEP: [{0}] LocalEP: [{1}] Hashcode: [{2,number,integer}] Cause: TBD

Solution: TBD CIS0027

size: [{0,number,integer}] minSize: [{1,number,integer}] Cause: TBD

Solution: TBD CIS0028

size: [{0,number,integer}] Cause: TBD

Solution: TBD
Chapter 5 CIS Error Messages 75

CIS Messages

CIS0029

Closing connection: [{0}] timeStamp: [{1,number,integer}] clockTime: [{2,number,integer}] interval: [{3,number,integer}] Cause: TBD
Solution: TBD CIS0030

ConnectException thrown while closing the initiated Connection Cause: TBD

Solution: TBD CIS0031

ConnectionException thrown while closing the intitated Connection Cause: TBD

Solution: TBD CIS0032

Connection List at e1: [{0}] is [{1}] Cause: TBD

Solution: TBD CIS0033

Connection List at e2: [{0}] is [{1}] Cause: TBD

Solution: TBD CIS0034

InitiatedConnSetSize: [{0,number,integer}] AcceptedConnSetSize: [{1,number,integer}] ConnectionListSize: [{2,number,integer}] Cause: TBD

Solution: TBD CIS0035
76 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

CIS Messages

Reaper thread created Cause: TBD

Solution: TBD CIS0036

Reaper thread started Cause: TBD

Solution: TBD CIS0037

InterruptedException thrown while the reaper thread was sleeping Cause: TBD
Solution: TBD CIS0038

ConnectException thrown while closing the accepted connection socket Cause: TBD
Solution: TBD CIS0039

Reaper thread kicking in Cause: TBD

Solution: TBD CIS0040

Reaper going to sleep Cause: TBD

Solution: TBD CIS0041

Reaper coming out of sleep Cause: TBD

Solution: TBD
Chapter 5 CIS Error Messages 77

CIS Messages

CIS0042

Cleaning up the connection object [{0}] since the lastTimestamp on that object was [{1,number,integer}] and the reapers interval is [{2,number,integer}] Cause: TBD
Solution: TBD CIS0043

ConnectException thrown while closing the connection Cause: TBD

Solution: TBD CIS0044

Interrupted exception thrown from the Reaper Thread Cause: TBD

Solution: TBD CIS0045

SSLBlocking server channel is created for: [{0}] Cause: TBD

Solution: TBD CIS0046

ssl2ciphers.length: [{0,number,integer}] ssl3Ciphers.length: [{1,number,integer}] Cause: TBD

Solution: TBD CIS0047

Returning from SSLBlockingServerChannel for [{0}] Cause: TBD

Solution: TBD CIS0048
78 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

CIS Messages

Before accept in SSLBlockingServerChannel at [{0}] Cause: TBD

Solution: TBD CIS0049

After accept in SSLBlockingServerChannel at [{0}] Cause: TBD

Solution: TBD CIS0050

Creating ServerConnection at: [{0}] [{1}] [{2,number,integer}] [{3}] [{4}] [{5}] [{6,number,integer}] Cause: TBD
Solution: TBD CIS0051

Before Accept in tcp blocking server channel: [{0}] timeout: [{1,number,integer}] Cause: TBD
Solution: TBD CIS0052

NonBlockingChannel: timeout [{0,number,integer}] Cause: TBD

Solution: TBD CIS0053

FLUSH: position: [{0,number,integer}] bytesSent: [{1,number,integer}] Cause: TBD

Solution: TBD CIS0054

Chapter 5 CIS Error Messages

79

CIS Messages

Creating TCP Connection from [{0}] to [{1}] Cause: TBD

Solution: TBD CIS0054

Created TCP Connection from [{0}] to [{1}] Cause: TBD

Solution: TBD CIS0056

Creating TCP ServerConnection at [{0}] Cause: TBD

Solution: TBD CIS0057

Created TCP ServerConnection at [{0}] Cause: TBD

Solution: TBD CIS0058

Creating SSL_MUTUALAUTH ServerConnection at [{0}] certname: [{1}] sslVersion: [{2,number,integer}] ssl2Ciphers: [{3}] ssl3Ciphers: [{4}] tlsRollback: [{5}] Cause: TBD
Solution: TBD CIS0059

Creating SSL ServerConnection at [{0}] certname: [{1}] sslVersion: [{2,number,integer}] ssl2Ciphers: [{3}] ssl3Ciphers: [{4}] tlsRollback: [{5}] Cause: TBD
Solution: TBD CIS0060

80

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

CIS Messages

Created SSL_MUTUALAUTH ServerConnection at [{0}] certname: [{1}] sslVersion: [{2,number,integer}] ssl2Ciphers: [{3}] ssl3Ciphers: [{4}] tlsRollback: [{5}] Cause: TBD
Solution: TBD CIS0061

Created SSL ServerConnection at [{0}] certname: [{1}] sslVersion: [{2,number,integer}] ssl2Ciphers: [{3}] ssl3Ciphers: [{4}] tlsRollback: [{5}] Cause: TBD
Solution: TBD CIS0062

Waiting for accept at [{0}] Cause: TBD

Solution: TBD CIS0063

Successful accept at [{0}] Cause: TBD

Solution: TBD CIS0064

Before ServerConnection close() at [{0}] Cause: TBD

Solution: TBD CIS0065

Successful ServerConnection close() at [{0}] Cause: TBD

Solution: TBD CIS0066

Chapter 5 CIS Error Messages

81

CIS Messages

Creating TCPBlockingServerChannel at [{0}] Cause: TBD

Solution: TBD CIS0067

Created TCPBlockingServerChannel at [{0}] Cause: TBD

Solution: TBD CIS0068

Successful Accept in TCPBlockingServerChannel at [{0}] timeout: [{1,number,integer}] Cause: TBD

Solution: TBD CIS0069

Creating TCPBlockingChannel from [{0}] to [{1}] Cause: TBD

Solution: TBD CIS0070

Created TCPBlockingChannel from [{0}] to [{1}] Cause: TBD

Solution: TBD CIS0071

Initializing NSS with [{0}] as cert directory and [{1}] as password Cause: TBD
Solution: TBD CIS0072

82

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

CIS Messages

Successfully initialized NSS with [{0}] as cert directory. Cause: TBD

Solution: TBD CIS0073

Creating SSLBlockingChannel from [{0}] to [{1}] with certname [{2}] sslVersion [{3,number,integer}] Cause: TBD
Solution: TBD CIS0074

Created SSLBlockingChannel from [{0}] to [{1}] with certname [{2}] sslVersion [{3,number,integer}] Cause: TBD
Solution: TBD

Chapter 5 CIS Error Messages

83

84

C H A P T E R

CMNUTIL Error Messages

This chapter describes messages for errors with a CMNUTIL prefix.

CMNUTIL Messages
CMNUTL1000

Failed to process class {0} with bytecode preprocessor {1} Cause: TBD
Solution: TBD CMNUTL1001

Class {0} is being reset to its original state Cause: TBD

Solution: TBD CMNUTL1002

Class {0} is being reset to the last successful preprocessor Cause: TBD
Solution: TBD CMNUTL1003

85

CMNUTIL Messages

The supplied preprocessor class {0} is not an instance of com.sun.appserv.BytecodePreprocessor Cause: TBD
Solution: TBD CMNUTL1004

Bytecode preprocessor disabled Cause: TBD

Solution: TBD CMNUTL1005

Initialization failed for bytecode preprocessor {0} Cause: TBD

Solution: TBD CMNUTL1006

Error setting up preprocessor Cause: TBD

Solution: TBD CMNUTL9001

Error releasing URLClassLoader Cause: TBD

Solution: TBD CMNUTL9002

Error closing JAR file {0} Cause: TBD

Solution: TBD CMNUTL9003

86

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

CMNUTIL Messages

Error getting information for field {0} Cause: TBD

Solution: TBD CMNUTL9004

name not available Cause: TBD

Solution: TBD CMNUTL9005

Error releasing JAR file./appserv-commons/src/java/com/sun/logging/enterprise/resource/corba/LogStrings.p Cause: TBD

Solution: TBD CMNUTL9005

Error releasing JAR file./appserv-commons/src/java/com/sun/logging/enterprise/resource/corba/LogStrings.p Cause: TBD

Solution: TBD

Chapter 6 CMNUTIL Error Messages

87

88

C H A P T E R

CONF Error Messages

This chapter describes messages for errors with a CONF prefix.

CONF Messages
CONF5005

Exception occured in getting nodelist Cause: TBD

Solution: TBD CONF5006

Exception occured in getAttribute Cause: TBD

Solution: TBD

89

90

C H A P T E R

CORE Error Messages

This chapter describes messages for errors with a CORE prefix.

CORE Messages
CORE5001

Exception: Cause: TBD

Solution: TBD CORE5002

[{0}] reloaded successfully! Cause: TBD

Solution: TBD CORE5003

[{0}] failed to reload! Cause: TBD

Solution: TBD CORE5004

Resource Deployed: [{0}]. Cause: TBD

Solution: TBD
91

CORE Messages

CORE5005

Error in resource deploy. Cause: TBD

Solution: TBD CORE5006

Resource UnDeployed: [{0}]. Cause: TBD

Solution: TBD CORE5007

Error in resource un-deploy. Cause: TBD

Solution: TBD CORE5008

Resource Redeployed: [{0}]. Cause: TBD

Solution: TBD CORE5009

Error in resource re-deploy. Cause: TBD

Solution: TBD CORE5010

Resource Enabled: [{0}]. Cause: TBD

Solution: TBD CORE5011

92

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

CORE Messages

Error in resource enable. Cause: TBD

Solution: TBD CORE5012

Resource Disabled: [{0}]. Cause: TBD

Solution: TBD CORE5013

Error in resource disable. Cause: TBD

Solution: TBD CORE5014

Error occurred while getting deployed application list from config. Cause: TBD
Solution: TBD CORE5015

Error occurred while loading applications Cause: TBD

Solution: TBD CORE5016

Unexpected error occurred while loading applications Cause: TBD

Solution: TBD CORE5017

Error occurred while redeploying application Cause: TBD

Solution: TBD
Chapter 8 CORE Error Messages 93

CORE Messages

CORE5018

Error while loading connector module Cause: TBD

Solution: TBD CORE5019

Error occurred while reloading ejb module Cause: TBD

Solution: TBD CORE5020

Error while loading ejb module Cause: TBD

Solution: TBD CORE5021

Application NOT loaded: [{0}] Cause: TBD

Solution: TBD CORE5022

All ejb(s) of [{0}] were unloaded successfully! Cause: TBD

Solution: TBD CORE5023

Error while unloading application [{0}] Cause: TBD

Solution: TBD CORE5024

94

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

CORE Messages

EJB module [{0}] unloaded successfully! Cause: TBD

Solution: TBD CORE5025

Error while unloading ejb module [{0}] Cause: TBD

Solution: TBD CORE5026

********Application Environment Dump********* Cause: TBD

Solution: TBD CORE5027

Error occurred while reloading war module Cause: TBD

Solution: TBD CORE5028

Exception while creating mime ts file Cause: TBD

Solution: TBD CORE5029

File IO exception: Cause: TBD

Solution: TBD CORE5030

Unsupported Javac option [{0}] found in server configuration. Cause: TBD

Solution: TBD
Chapter 8 CORE Error Messages 95

CORE Messages

CORE5031

License exception occurred while loading license. Cause: TBD

Solution: TBD CORE5032

UnExpected error occurred, license file is not valid. Cause: TBD

Solution: TBD CORE5033

Thank you for trying the Sun Java System Application Server. Your evaluation license has expired. Please contact your Sun Microsystems representative to obtain the released software. You can also visit the Sun Microsystems Web Site at http://www.sun.com/as7upgrade for Sun Java System product information and downloads. Cause: TBD
Solution: TBD CORE5034

Unexpected error occurred while setting remote permissions Cause: TBD

Solution: TBD CORE5035

UnExpected error occurred while setting instance limit Cause: TBD

Solution: TBD CORE5036

Your license is invalid. Please go to http://www.sun.com/as7upgrade to get a valid license. Cause: TBD
Solution: TBD
96 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

CORE Messages

CORE5037

Thank you for trying the Sun Java System Application Server. Your evaluation license will expire in [{0}] days. Please contact your Sun Microsystems representative to obtain the released software. You can also visit the Sun Microsystems Web Site at http://www.sun.com/as7upgrade for Sun Java System product information and downloads. Cause: TBD
Solution: TBD CORE5038

Thank you for trying the Sun Java System Application Server. Your evaluation license has expired. Please contact your Sun Microsystems representative to obtain the released software. You can also visit the Sun Microsystems Web Site at http://www.sun.com/as7upgrade for Sun Java System product information and downloads. Cause: TBD
Solution: TBD CORE5039

Resource named {0} [Type: {1}] is disabled. It was not loaded. Cause: TBD
Solution: TBD CORE5040

Application [{0}] is disabled. It was not loaded. Cause: TBD

Solution: TBD CORE5041

EJB module [{0}] is disabled. It was not loaded. Cause: TBD

Solution: TBD CORE5042
Chapter 8 CORE Error Messages 97

CORE Messages

Resource Undeployed: [{0}]. Server restart needed. Cause: TBD

Solution: TBD CORE5043

Resource Redeployed: [{0}]. Server restart needed. Cause: TBD

Solution: TBD CORE5044

Resource Enabled: [{0}]. Server restart needed. Cause: TBD

Solution: TBD CORE5045

Resource Disabled: [{0}]. Server restart needed. Cause: TBD

Solution: TBD CORE5046

core.failed to get connectorresourcesloader. Cause: TBD

Solution: TBD CORE5046

Unexpected error occurred while loading the applications Cause: TBD

Solution: TBD CORE5047

Config exception occurred while loading the applications Cause: TBD

Solution: TBD
98 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

CORE Messages

CORE5048

Config exception occurred while retrieving the dynamic reload enabled attribute value Cause: TBD
Solution: TBD CORE5049

Unexpected error occurred while shutting down applications Cause: TBD

Solution: TBD CORE5050

Error occurred while shutting down applications Cause: TBD

Solution: TBD CORE5051

Shutting down all J2EE applications ... Cause: TBD

Solution: TBD CORE5052

Application shutdown complete. Cause: TBD

Solution: TBD CORE5053

Unexpected error occurred while terminating applications Cause: TBD

Solution: TBD CORE5053
Chapter 8 CORE Error Messages 99

CORE Messages

Application onReady complete. Cause: TBD

Solution: TBD CORE5054

Unexpected error occurred while calling onReady Cause: TBD

Solution: TBD CORE5055

No such resource {0} Cause: TBD

Solution: TBD CORE5056

Error in reading connector resources from domain.xml Cause: TBD

Solution: TBD CORE5057

No resource deployer for resource type {0} Cause: TBD

Solution: TBD CORE5058

No such resource type {0} Cause: TBD

Solution: TBD CORE5059

Error in loading resource Cause: TBD

Solution: TBD
100 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

CORE Messages

CORE5060

Stopping all J2EE Connector 1.5 Compliant resource adapters ... Cause: TBD
Solution: TBD CORE5061

Resource adapters Stop() Complete Cause: TBD

Solution: TBD CORE5060

IOException: Cause: TBD

Solution: TBD CORE5061

Exception: Cause: TBD

Solution: TBD CORE5062

Exception: Cause: TBD

Solution: TBD CORE5063

j2eerunner.startupError. Cause: TBD

Solution: TBD CORE5070

Chapter 8 CORE Error Messages

101

CORE Messages

A server context could not be created Cause: TBD

Solution: TBD CORE5071

An error occured during initialization Cause: TBD

Solution: TBD CORE5072

An error occured during startup/reconfig Cause: TBD

Solution: TBD CORE5073

Application server shutdown in progress Cause: TBD

Solution: TBD CORE5074

An error occured during shutdown Cause: TBD

Solution: TBD CORE5075

Your license is invalid. Please obtain a valid license. [{0}] Cause: TBD
Solution: TBD CORE5076

Using [{0}, Version {1}] from [{2}] Cause: TBD

Solution: TBD
102 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

CORE Messages

CORE5080

Exception resolving initial reference of ORB: Cause: TBD

Solution: TBD CORE5081

Exception while creating ORB: [{0}] Cause: TBD

Solution: TBD CORE5082

Exception running j2ee services: [{0}] Cause: TBD

Solution: TBD CORE5083

Exception in creating or binding jarinstaller: [{0}] Cause: TBD

Solution: TBD CORE5084

Exception in creating or binding server object: [{0}] Cause: TBD

Solution: TBD CORE5085

Exception in listing registered servers Cause: TBD

Solution: TBD CORE5086

Chapter 8 CORE Error Messages

103

CORE Messages

Some remote exception occurred loading jar Cause: TBD

Solution: TBD CORE5086

Exception in registering server: [{0}] Cause: TBD

Solution: TBD CORE5087

Error installing servers: [{0}] Cause: TBD

Solution: TBD CORE5088

Exception installing ORB server [{0}] Cause: TBD

Solution: TBD CORE5089

Exception initing realmmanager: [{0}] Cause: TBD

Solution: TBD CORE5090

Cannot write the seed file for fast startup. The next startup will be slow. Cause: TBD
Solution: TBD CORE5091

Error executing J2EE server ... Cause: TBD

Solution: TBD
104 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

CORE Messages

CORE5092

J2EE server reported following error: [{0}] Cause: TBD

Solution: TBD CORE5093

Error executing J2EE server Cause: TBD

Solution: TBD CORE5094

Exception looking up server object: [{0}] Cause: TBD

Solution: TBD CORE5095

Unable to shutdown the J2EE server: [{0}] Cause: TBD

Solution: TBD CORE5096

Relative pathname specified for transaction log directory: [{0}] Cause: TBD
Solution: TBD CORE5097

Unexpected exception determining whether a server has a reference to an application or resource. Cause: TBD
Solution: TBD CORE5098
Chapter 8 CORE Error Messages 105

CORE Messages

AS Socket Service Initialization has been completed. Cause: TBD

Solution: TBD CORE5100

Loading system apps Cause: TBD

Solution: TBD CORE5101

Exception occured while deploying system apps Cause: TBD

Solution: TBD CORE5102

Deploying system apps to target {0} from directory {1} Cause: TBD
Solution: TBD CORE5103

Deployed system apps to target {0} Cause: TBD

Solution: TBD CORE5104

Directory {0} not found or cannot read Cause: TBD

Solution: TBD CORE5105

Exception occured while getting targets Cause: TBD

Solution: TBD
106 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

CORE Messages

CORE5106

Exception occured while finding application registration Cause: TBD

Solution: TBD CORE5200

Bytecode preprocessor configuration error Cause: TBD

Solution: TBD CORE5201

Bytecode preprocessor disabled Cause: TBD

Solution: TBD

Chapter 8 CORE Error Messages

107

108

C H A P T E R

DIAG Error Messages

This chapter describes messages for errors with a DIAG prefix.

DIAG Messages
DIAG9001

Could not copy {0} due to {1} Cause: TBD

Solution: TBD DIAG9002

Could not copy config files to dir {0} due to {1} Cause: TBD
Solution: TBD DIAG9003

Destination log file is {0} Cause: TBD

Solution: TBD DIAG9004

domain.xml DTD file name is {0} Cause: TBD

Solution: TBD
109

DIAG Messages

DIAG9005

Generated report name is {0} Cause: TBD

Solution: TBD DIAG9006

diagnostic-service Attribute Name is {0} Cause: TBD

Solution: TBD DIAG9007

diagnostic-service Attribute value is {0} Cause: TBD

Solution: TBD DIAG9008

diagnostic-service capture-app-dd value is {0} Cause: TBD

Solution: TBD DIAG9009

diagnostic-service capture-hadb-info value is {0} Cause: TBD

Solution: TBD DIAG9010

diagnostic-service capture-install-log value is {0} Cause: TBD

Solution: TBD DIAG9011

110

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

DIAG Messages

diagnostic-service compute-checksum value is {0} Cause: TBD

Solution: TBD DIAG9012

diagnostic-service min-log-level value is {0} Cause: TBD

Solution: TBD DIAG9013

diagnostic-service max-log-entries value is {0} Cause: TBD

Solution: TBD DIAG9014

Report Generation target is {0} Cause: TBD

Solution: TBD DIAG9015

Error loading domain.xml due to {0} Cause: TBD

Solution: TBD DIAG9016

Loading domain.xml at {0} Cause: TBD

Solution: TBD DIAG9017

Error while collecting data due to {0} Cause: TBD

Solution: TBD
Chapter 9 DIAG Error Messages 111

DIAG Messages

DIAG9018

Could not compute checksum of {0} due to {1} Cause: TBD

Solution: TBD DIAG9019

Invalid target {0} Cause: TBD

Solution: TBD DIAG9020

Target while validating local target : {0} & targetDir {1} Cause: TBD
Solution: TBD DIAG9021

target {0}, targetDir {1} , type {2} ,instances {3} Cause: TBD
Solution: TBD DIAG9022

Error initializing client pluggable factory {0} Cause: TBD

Solution: TBD DIAG9033

While resolving target dir, instanceRoot = {0 } and targetDir = {1} Cause: TBD
Solution: TBD DIAG9034

112

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

DIAG Messages

Execution Context is DAS Cause: TBD

Solution: TBD DIAG9035

Execution Context is not DAS Cause: TBD

Solution: TBD DIAG9036

Target Dir is {0} Cause: TBD

Solution: TBD DIAG9037

Target is {0} Cause: TBD

Solution: TBD DIAG9038

Target type is {0} Cause: TBD

Solution: TBD DIAG9039

Execution Context is {0} Cause: TBD

Solution: TBD DIAG9040

Using EE local Target resolver for resolving target details Cause: TBD
Solution: TBD
Chapter 9 DIAG Error Messages 113

DIAG Messages

DIAG9041

Using EE remote Target resolver for resolving target details Cause: TBD
Solution: TBD DIAG9042

During invocation of report generation using Node Agent MBean instances are{0} Cause: TBD
Solution: TBD DIAG9043

Exception in retrieving node agent name for a server Cause: TBD

Solution: TBD DIAG9044

Creating NodeAgent Diagnostic MBean for node agent : {0} Cause: TBD
Solution: TBD DIAG9045

Error creating NodeAgent Diagnostic MBean Cause: TBD

Solution: TBD DIAG9046

Error generating report on nodeagent Cause: TBD

Solution: TBD DIAG9047

114

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

DIAG Messages

Repository Dir is {0} Cause: TBD

Solution: TBD DIAG9048

Unable to retrieve Pluggable Feature Factory Cause: TBD

Solution: TBD DIAG9001

Could not copy {0} due to {1} Cause: TBD

Solution: TBD DIAG9002

Could not copy config files to dir {0} due to {1} Cause: TBD
Solution: TBD DIAG9003

Destination log file is {0} Cause: TBD

Solution: TBD DIAG9004

domain.xml DTD file name is {0} Cause: TBD

Solution: TBD DIAG9005

Generated report name is {0} Cause: TBD

Solution: TBD
Chapter 9 DIAG Error Messages 115

DIAG Messages

DIAG9006

diagnostic-service Attribute Name is {0} Cause: TBD

Solution: TBD DIAG9007

diagnostic-service Attribute value is {0} Cause: TBD

Solution: TBD DIAG9008

diagnostic-service capture-app-dd value is {0} Cause: TBD

Solution: TBD DIAG9009

diagnostic-service capture-hadb-info value is {0} Cause: TBD

Solution: TBD DIAG9010

diagnostic-service capture-install-log value is {0} Cause: TBD

Solution: TBD DIAG9011

diagnostic-service compute-checksum value is {0} Cause: TBD

Solution: TBD DIAG9012

116

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

DIAG Messages

diagnostic-service min-log-level value is {0} Cause: TBD

Solution: TBD DIAG9013

diagnostic-service max-log-entries value is {0} Cause: TBD

Solution: TBD DIAG9014

Report Generation target is {0} Cause: TBD

Solution: TBD DIAG9015

Error loading domain.xml due to {0} Cause: TBD

Solution: TBD DIAG9016

Loading domain.xml at {0} Cause: TBD

Solution: TBD DIAG9017

Error while collecting data due to {0} Cause: TBD

Solution: TBD DIAG9018

Could not compute checksum of {0} due to {1} Cause: TBD

Solution: TBD

Chapter 9 DIAG Error Messages

117

118

10
C H A P T E R

1 0

DPL Error Messages

This chapter describes messages for errors with a DPL prefix.

DPL Messages
DPL5001

Class loader could not be made Cause: TBD

Solution: TBD DPL5002

Cannot Add Icon Cause: TBD

Solution: TBD DPL5003

SAX Parser cannot validate Cause: TBD

Solution: TBD DPL5004

Cannot add jar to output stream Cause: TBD

Solution: TBD
119

DPL Messages

DPL5005

Unexpected I/O Exception Cause: TBD

Solution: TBD DPL5006

Error reading connector xml Cause: TBD

Solution: TBD DPL5007

Error loading class [{0}] Cause: TBD

Solution: TBD DPL5008

Error loading class Cause: TBD

Solution: TBD DPL5009

Error loading the ejb class [{0}] in getFields on EjbDescriptor\n [{1}] Cause: TBD
Solution: TBD DPL5010

Error loading ejb class in getFields on EjbDescriptor Cause: TBD

Solution: TBD DPL5011

120

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

DPL Messages

Error loading the ejb class in getFieldForName on EjbDescriptor [{0}] Cause: TBD
Solution: TBD DPL5012

Error loading the ejb class in getFieldForName on EjbDescriptor [{0}] Cause: TBD
Solution: TBD DPL5013

Mail Configuration Exception Cause: TBD

Solution: TBD DPL5014

[{0}] not found in [{1}] Cause: TBD

Solution: TBD DPL5015

Method not found Cause: TBD

Solution: TBD DPL5016

Cannot instantiate implementation of [{0}] Cause: TBD

Solution: TBD DPL5017

Cannot instantiate implementation Cause: TBD

Solution: TBD
Chapter 10 DPL Error Messages 121

DPL Messages

DPL5018

Error while parsing Cause: TBD

Solution: TBD DPL5019

Illegal Argument(s) Cause: TBD

Solution: TBD DPL5020

SAX Parser cannot parse given stream Cause: TBD

Solution: TBD DPL5021

No method found for XML query element Cause: TBD

Solution: TBD DPL5022

Supplied External Descriptors are incorrect Cause: TBD

Solution: TBD DPL5023

class not found Cause: TBD

Solution: TBD DPL5024

122

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

DPL Messages

Cannot expand jar archive Cause: TBD

Solution: TBD DPL5025

Error in SAX parser configuration Cause: TBD

Solution: TBD DPL5026

Exception in SAX parser Cause: TBD

Solution: TBD DPL5027

Cannot create package Cause: TBD

Solution: TBD DPL5028

Unexpected exception in MethodDescriptor.getMethod() Cause: TBD

Solution: TBD DPL5029

Cannot read runtime descriptor nodes Cause: TBD

Solution: TBD DPL5030

Cannot read EJB nodes Cause: TBD

Solution: TBD
Chapter 10 DPL Error Messages 123

DPL Messages

DPL5031

Cannot read method descriptor nodes Cause: TBD

Solution: TBD DPL5032

An authentication method was not defined in the web.xml descriptor. Using default BASIC for login configuration. Cause: TBD
Solution: TBD DPL5033

Error parsing application.xml Cause: TBD

Solution: TBD DPL5034

Rollback failed Cause: TBD

Solution: TBD DPL5035

Error while running ejbc Cause: TBD

Solution: TBD DPL5036

Duplicate entry in jar archive Cause: TBD

Solution: TBD DPL5037
124 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

DPL Messages

Error reading runtime descriptor nodes Cause: TBD

Solution: TBD DPL5038

Verification Results: \n\tNumber of Failure(s): {0}\n\tNumber of Warning(s): {1}\n\tNumber of Error(s): {2} Cause: TBD
Solution: TBD DPL5039

Caught a Throwable in POST_DEPLOY Event Cause: TBD

Solution: TBD DPL5040

Caught a Throwable in PRE_UNDEPLOY Event Cause: TBD

Solution: TBD DPL5041

Unknown port-component-name {0} port, all sub elements will be ignored" Cause: TBD
Solution: TBD DPL5100

EJBC - Could not generate new source Cause: TBD

Solution: TBD DPL5101

Chapter 10 DPL Error Messages

125

DPL Messages

EJBC - Could not invoke rmic Cause: TBD

Solution: TBD DPL5102

EJBC - rmic compilation failed Cause: TBD

Solution: TBD DPL5103

EJBC - compilation failed Cause: TBD

Solution: TBD DPL5104

EJBC - code gen required check error Cause: TBD

Solution: TBD DPL5105

EJBC - Start of CMP section for [{0}] Cause: TBD

Solution: TBD DPL5106

EJBC - End of CMP section for [{0}] Cause: TBD

Solution: TBD DPL5107

EJBC - Generated code for EJBLocalHOme, EJBLocalObject implementations for [{0}] Cause: TBD
Solution: TBD
126 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

DPL Messages

DPL5108

EJBC - Generated code for remote home and EJBObject implementations for [{0}] Cause: TBD
Solution: TBD DPL5109

EJBC - START of EJBC for [{0}] Cause: TBD

Solution: TBD DPL5110

EJBC - END of EJBC for [{0}] Cause: TBD

Solution: TBD DPL5150

Run time exception during R/O bean notifier initialization Cause: TBD
Solution: TBD DPL5200

Could not invoke rmic Cause: TBD

Solution: TBD DPL5201

rmic compilation failed... Cause: TBD

Solution: TBD DPL5202

Chapter 10 DPL Error Messages

127

DPL Messages

Exception occurred compiling ejb Cause: TBD

Solution: TBD DPL5203

Output jarfile [{0}] already exists Cause: TBD

Solution: TBD DPL5204

Exception occurred while loading class [{0}] Cause: TBD

Solution: TBD DPL5205

Exception occurred while generating ejb Cause: TBD

Solution: TBD DPL5206

Class not found Cause: TBD

Solution: TBD DPL5207

Some IO exception occurred Cause: TBD

Solution: TBD DPL5208

Some exception occurred Cause: TBD

Solution: TBD
128 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

DPL Messages

DPL5209

Adding to generated files: [{0}] Cause: TBD

Solution: TBD DPL5210

Error generating code: [{0}] Cause: TBD

Solution: TBD DPL5211

Error in setting message status Cause: TBD

Solution: TBD DPL5212

Error in notification Cause: TBD

Solution: TBD DPL5212

Attempt to override reserved ejb interface method [{0}] in [{1}]. Override will be ignored. Cause: TBD
Solution: TBD DPL5300

Interrupted while waiting for execution of [{0}] Cause: TBD

Solution: TBD DPL5301
Chapter 10 DPL Error Messages 129

DPL Messages

Timeout [{0}] milliseconds reached, Interrupting execution of command [{1}]. Cause: TBD
Solution: TBD DPL5302

Process creation failed. Cause: TBD

Solution: TBD DPL5303

Error in closing process output or error stream. Cause: TBD

Solution: TBD DPL5303

Execution of command in a sub-process interrupted. Cause: TBD

Solution: TBD DPL5304

Execution of process failed Cause: TBD

Solution: TBD DPL5305

Error reading from process output or error stream Cause: TBD

Solution: TBD DPL5306

{0} Web Service Endpoint [{1}] listening at address [{2}] Cause: TBD
Solution: TBD
130 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

DPL Messages

DPL5400

Exception occurred : {0}.\ Cause: TBD

Solution: TBD DPL5401

Optional package {0} does not exist or its Specification-Version doesnot match!! Unable to satisfy dependency for {1} Cause: TBD
Solution: TBD DPL5402

Optional package dependency satisfied for {0} Cause: TBD

Solution: TBD DPL5403

Either Extension-Name or Specification-Version for the optional package is not specified for {0}.\ Cause: TBD
Solution: TBD DPL5404

Specification-Version for the optional package {0} is null!!! Please provide a valid specification version for this optional package Cause: TBD
Solution: TBD DPL8001

Event subsystem does not recognize the new implementation of the server context found in runtime. Cause: The instance may not be of expected type
Solution: Ensure that the descriptor type is set as expected. Set log level for deployment to view more details.
Chapter 10 DPL Error Messages 131

DPL Messages

DPL8002

Copying of files failed. Cause: May be because of lack of space or permission.

Solution: Ensure that the permissions are set as expected and that there is enough disk space. DPL8003

ArchivistFactory.getArchivist() failed Cause: The module type may not be as expected.

Solution: Ensure that the module type is one of the supported types. DPL8004

Opening of files failed. Cause: May be because of lack of permission or wrong file name.
Solution: Ensure that the file name is correct, and that the permissions are set as expected. DPL8005

Error while parsing the deployment descriptor. Cause: May be because of malformed descriptor or absence of all required descriptor elements.
Solution: Ensure that the descriptor is well formed and as per specification. Also ensure that

the SAX parser configuration is correct and the descriptor has right permissions.
DPL8006

Adding or getting a descriptor failed. Cause: May be because the node/information to be added is not valid; may also be because of the descriptor was not registered.
Solution: Ensure that the node to be added is valid, and that the permissions are set as

expected.
DPL8007

Failed to find the resource specified in the deployment descriptor. Cause: May be because of wrong specification in the descriptor.
Solution: Ensure that the resource specified is present, and that there is no typo in the

resource specified in the descriptor.

132 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

DPL Messages

DPL8008

Failed to load the class/method. Cause: May be because of wrong class/method name.
Solution: Ensure that the class/method specified is present, and that the path information is

correct.
DPL8009

Failed to load the deployment manager. Cause: May be because of wrong URI specification or deployment factory not installed at all.
Solution: Ensure that the resource specified is present, and that there is no typo in the URI

specified.
DPL8010

Failed in autodeployment. Cause: May be because of failure in creating the autodeployer or while reading the autodeploy configuration info.
Solution: Ensure that the autodeploy is enabled properly, and that their autodeploy configuration is set properly. DPL8011

Failed in autodeployment of applications. Cause: Mostly because of application specific failure.

Solution: Ensure that the application can be deployed using CLI, and that there autodeploy

configuration is set properly and the server is up and running.

DPL8012

Failed to rename directory. Cause: May be because of lack of permissions.

Solution: Ensure that the permissions are set as expected, and that the there is no directory name clash. DPL8013

Chapter 10 DPL Error Messages

133

DPL Messages

Failed to create JAR file. Cause: May be because of lack of permissions or lack of space.
Solution: Ensure that the permissions are set as expected, and that the there is enough space. DPL8014

Failed to complete application deployment. Cause: May be because of lack of permissions or lack of space or wrong application.
Solution: Ensure that the permissions are set as expected, and that the there is enough space.

134

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

11
C H A P T E R

1 1

DTX Error Messages

This chapter describes messages for errors with a DTX prefix.

DTX Messages
DTX5001

Exception occurred while enlisting the resource. Solution: Make sure that the resource usage is from a standard J2EE component or a life cycle component. If this exception occurs from a standard component, this is an Unexpected Internal Error and please contact Sun with the complete error log message.
DTX5002

Exception occurred while delisting the resource. Solution: Make sure that the resource usage is from a standard J2EE component or a life cycle component. If this exception occurs from a standard component, this is an Unexpected Internal Error and please contact Sun with the complete error log message.
DTX5003

Trying to register the sync object while transaction is marked for rollback. Solution: This is an Unexpected Internal Error. Please contact Sun with the complete error log message.
DTX5004

Exception occurred while enlisting the component resource. Solution: Make sure that the resource usage is from a standard J2EE component or a life cycle component. If this exception occurs from a standard component, this is an Unexpected Internal Error and please contact Sun with the complete error log message.
135

DTX Messages

DTX5005

Exception occurred while delisting the component resources. Solution: Make sure that the resource usage is from a standard J2EE component or a life cycle component. If this exception occurs from a standard component, this is an Unexpected Internal Error and please contact Sun with the complete error log message.
DTX5006

Exception occurred while delisting the component resources. Solution: Make sure that the resource usage is from a standard J2EE component or a life cycle component. If this exception occurs from a standard component, this is an Unexpected Internal Error and please contact Sun with the complete error log message.
DTX5007

Exception : Cause: TBD

Solution: TBD DTX5008

Exception occurred while closing the connection. Solution: Check if database is up and running.
DTX5009

Invalid integer passed to set the timeout. Solution: Check the timeout that is being given in the server configuration file.
DTX5010

Could not register the JTA statistics for monitoring due to configuration problem. Solution: This is an Unexpected Internal Error. Please contact Sun with the complete error log message.
DTX5011

Requested attribute is not monitorable. Solution: This is an Unexpected Internal Error. Please contact Sun with the complete error log message.
DTX5012
136 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

DTX Messages

JTAStats implementation class is not found. Solution: This is an Unexpected Internal Error. Please contact Sun with the complete error log message.
DTX5013

Attribute is not part of transaction monitoring Cause: TBD

Solution: TBD

Chapter 11 DTX Error Messages

137

138

12
C H A P T E R

1 2

EEADM Error Messages

This chapter describes messages for errors with an EEADM prefix.

EEADM Messages
EEADM0069

Error while sending event to remote instance. Cause: Most likely an error in the connection layer. User name, password, host name or port number of the remote server instance may be incorrect.
Solution: Verify that user name, password, host name, or port number of the remote server instance is correct.

139

140

13
C H A P T E R

1 3

EJB Error Messages

This chapter describes messages for errors with a EJB prefix.

EJB Messages
EJB5013

Problem occurred while deserializing stateful bean state. Solution: Check the application classpath to ensure that all classes needed during deserialization are available.
EJB5017

An error occurred during the removal of an entity bean. One common cause is when the application throws a system exception from the ejbRemove method of an entity bean. Solution: Check the exception stack trace to see if the exception originated from the entity bean implementation class.
EJB5031

An error occurred while looking up a Read Only Bean Notifier. The most common cause for this failure is that the string supplied to the getReadOnlyBeanNotifier method either does not refer to a read-only bean. Solution: Check the application code that calls this method to make sure the string passed in refers to a valid read-only bean.
EJB5069

141

EJB Messages

The beans Home or LocalHome does not define a no-arg create method. Solution: Check the Home or LocalHome interface for the appropriate create method signature. Running the verifier will help identify the error as well.
EJB5071

Some problem occurred during the beforeCompletionphase of the transaction lifecycle. This error often happens when application code throws a system exception from its ejbStore method or if the transaction manager encounters a system exception. Solution: Check the stack trace to see if the exception originated from the applications ejbStore method. Also check the resource configuration to ensure that all resource managers involved in the transaction are configured properly and are healthy.
EJB5090

Problem during EJB container runtime initialization. See stack trace for more details. Some common causes are global JNDI name conflicts, classnotfound errors, and configuration errors for resources needed by the EJB. Solution: If the EJB has a Remote view, check that its JNDIname does not clash with any other EJB's JNDI name or any other globalJNDI name. Check that all needed classes are available to the EJB. Also ensure that any resources needed by the EJB are available. If the EJB uses a data source make sure the corresponding database is running. If it uses a queue makes sure the physical queue has been created.
EJB5111

This error indicates a mismatch in the required method signature rules between a method defined on a [Home, Remote, LocalHome, Local] interface and the corresponding bean implementation class. E.g., this would happen if a create method in a Home interface did not have a matching ejbCreate method in the bean class. Solution: Run the verifier tool to check that the methods defined on the bean class are correct with respect to the exposed interface.
EJB5117

Error while creating the persistent representation of an EJB timer. This typically means there is some configuration error or runtime problem with the EJB timer service data source. Solution: Double-check the JDBC data source (and its associated connection pool) assigned to the timer-data source element in domain.xml. Common causes are that the database is not running, the timer table has not been created within that database, or that the connection pool's JDBC driver URL information is incorrect.
142 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

EJB Messages

EJB5128

A problem occurred while the container was activating a stateful session bean. One possible cause is that the bean code threw a system exception from its ejbActivate method. Solution: Check the stack trace to see whether the exception was thrown from the ejbActivate method and if so double-check the application code to determine what caused the exception.
EJB5129

An error occurred during the afterCompletion phase of the transaction lifecycle. Solution: Check stack trace for details of error encountered by EJB container
EJB5014

Exception resolving object Cause: TBD

Solution: TBD EJB5015

Exception while adding method monitoring mbean Cause: TBD

Solution: TBD EJB5016

Exception creating BaseContainer : [{0}] Cause: TBD

Solution: TBD EJB5018

An exception was thrown during an ejb invocation on [{0}] Cause: TBD

Solution: TBD EJB5019

Chapter 13 EJB Error Messages

143

EJB Messages

Some application or system exception occurred : [{0}] Cause: TBD

Solution: TBD EJB5020

Exception while unregistering monitormbean Cause: TBD

Solution: TBD EJB5021

Session bean transaction is incomplete : [{0}] Cause: TBD

Solution: TBD EJB5022

Messagedriven bean transaction is incomplete : [{0}] Cause: TBD

Solution: TBD EJB5023

Exception while registering monitormbean Cause: TBD

Solution: TBD EJB5024

Exception while registering child monitormbean Cause: TBD

Solution: TBD EJB5024

Exception while unregistering child monitormbean : [{0}] Cause: TBD

Solution: TBD
144 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

EJB Messages

EJB5025

Exception while releasing ejb context : [{0}] Cause: TBD

Solution: TBD EJB5026

Exception in removing ejb local object : [{0}] Cause: TBD

Solution: TBD EJB5027

Exception in removing ejb : [{0}] Cause: TBD

Solution: TBD EJB5028

Exception in getting ejb local object : [{0}] Cause: TBD

Solution: TBD EJB5029

Exception getting ejb context : [{0}] Cause: TBD

Solution: TBD EJB5030

Exception while comparing ejbs : [{0}] Cause: TBD

Solution: TBD EJB5032

Chapter 13 EJB Error Messages

145

EJB Messages

Exception in creating new bean : [{0}] Cause: TBD

Solution: TBD EJB5033

Illegal state exception occurred : [{0}] Cause: TBD

Solution: TBD EJB5035

Some application or unchecked exception occurred : [{0}] Cause: TBD

Solution: TBD EJB5039

Some runtime exception occurred : [{0}] Cause: TBD

Solution: TBD EJB5041

Exception while running postinvoke : [{0}] Cause: TBD

Solution: TBD EJB5042

Exception setting bean context : [{0}] Cause: TBD

Solution: TBD EJB5043

Exception cleaning up ejb subclass : [{0}] Cause: TBD

Solution: TBD
146 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

EJB Messages

EJB5044

Name not found exception : [{0}] Cause: TBD

Solution: TBD EJB5045

Class cast exception : [{0}] Cause: TBD

Solution: TBD EJB5048

Exception creating new attribute Cause: TBD

Solution: TBD EJB5049

Exception obtaining attribute [{0}] Cause: TBD

Solution: TBD EJB5050

Exception in printStackTrace Cause: TBD

Solution: TBD EJB5051

Exception in printStackTrace of super Cause: TBD

Solution: TBD EJB5052

Chapter 13 EJB Error Messages

147

EJB Messages

Exception closing session : [{0}] Cause: TBD

Solution: TBD EJB5053

Exception closing server session pool : [{0}] Cause: TBD

Solution: TBD EJB5054

Exception closing topic session: [{0}] Cause: TBD

Solution: TBD EJB5055

Exception in init of ejb : [{0}] Cause: TBD

Solution: TBD EJB5056

Exception in undeploying the bean : [{0}] Cause: TBD

Solution: TBD EJB5057

Exception creating session : [{0}] Cause: TBD

Solution: TBD EJB5058

Exception creating sessionfilecachestore Cause: TBD

Solution: TBD
148 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

EJB Messages

EJB5058

Exception while getting ejb stub : [{0}] Cause: TBD

Solution: TBD EJB5059

Exception creating ejb object : [{0}] Cause: TBD

Solution: TBD EJB5060

Exception creating ejb local object [{0}] Cause: TBD

Solution: TBD EJB5061

Exception removing ejb : [{0}] Cause: TBD

Solution: TBD EJB5062

Exception removing bean : [{0}] Cause: TBD

Solution: TBD EJB5063

Some exception removing bean : [{0}] Cause: TBD

Solution: TBD EJB5064

Chapter 13 EJB Error Messages

149

EJB Messages

Exception in afterCompletion : [{0}] Cause: TBD

Solution: TBD EJB5065

Exception in deserializing [{0}] Cause: TBD

Solution: TBD EJB5066

Some generic ejb exception : [{0}] Cause: TBD

Solution: TBD EJB5067

Exception activating ejb : [{0}] Cause: TBD

Solution: TBD EJB5068

Exception in serializing : [{0}] Cause: TBD

Solution: TBD EJB5070

Exception creating stateless session bean : [{0}] Cause: TBD

Solution: TBD EJB5072

Error initializing home of container: [{0}] Cause: TBD

Solution: TBD
150 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

EJB Messages

EJB5083

Error -- invalid maxMsgs prop = [{0}] Cause: TBD

Solution: TBD EJB5085

Error -- invalid msg bean pool size = [{0}] Cause: TBD

Solution: TBD EJB5087

[{0}]: Invalid value [{1}] for [{2}] , use [{3}] instead Cause: TBD
Solution: TBD EJB5088

Number format exception Cause: TBD

Solution: TBD EJB5089

Error -- invalid cleanup interval prop = [{0}] Cause: TBD

Solution: TBD EJB5091

Exception occurred in postInvoke : [{0}] Cause: TBD

Solution: TBD EJB5092

Chapter 13 EJB Error Messages

151

EJB Messages

Exception occurred in postInvokeTx : [{0}] Cause: TBD

Solution: TBD EJB5093

Exception occured in passiveIdleBeans Cause: TBD

Solution: TBD EJB5094

container.getClassLoader() returned null Cause: TBD

Solution: TBD EJB5095

Exception occured in selectVictims() Cause: TBD

Solution: TBD EJB5096

Unable to lookup UserTransaction Cause: TBD

Solution: TBD EJB5097

Exception during undeploy Cause: TBD

Solution: TBD EJB5098

Exception in preInvokeTx Cause: TBD

Solution: TBD
152 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

EJB Messages

EJB5099

Exception in checkUnfinishedTx Cause: TBD

Solution: TBD EJB5100

Exception in useClientTx Cause: TBD

Solution: TBD EJB5101

Transaction Aborted Cause: TBD

Solution: TBD EJB5102

Unable to complete container-managed transaction Cause: TBD

Solution: TBD EJB5103

Exception in releaseContext Cause: TBD

Solution: TBD EJB5104

Exception in callEJBStore Cause: TBD

Solution: TBD EJB5105

Chapter 13 EJB Error Messages

153

EJB Messages

Exception in createContainer Cause: TBD

Solution: TBD EJB5106

Exception in EntityContainer Cause: TBD

Solution: TBD EJB5107

Exception while getting server session Cause: TBD

Solution: TBD EJB5108

Unable to initialize EJB Timer Service. The likely cause is the database has not been started or the timer database table has not been created. Cause: TBD
Solution: TBD EJB5109

EJB Timer Service started successfully for datasource [{0}] Cause: TBD
Solution: TBD EJB5110

Attempt to override reserved ejb interface method [{0}] in [{1}]. Override will be ignored. Cause: TBD
Solution: TBD EJB5112

154

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

EJB Messages

Error cancelling timer with pkey [{0}] Cause: TBD

Solution: TBD EJB5113

Error cancelling timers for container [{0}] and pkey [{1}] Cause: TBD
Solution: TBD EJB5114

Error destroying timers for container [{0}] Cause: TBD

Solution: TBD EJB5115

Error destroying timer [{0}] Cause: TBD

Solution: TBD EJB5116

Delivering missed timer for timer id [{0}]. Timer should have fired at [{1}] Cause: TBD
Solution: TBD EJB5118

Failure removing timer bean [{0}] Cause: TBD

Solution: TBD EJB5119

Expunging timer [{0}] after [{1}] failed deliveries Cause: TBD

Solution: TBD
Chapter 13 EJB Error Messages 155

EJB Messages

EJB5120

EJB Timer Service last shutdown at [{0}] Cause: TBD

Solution: TBD EJB5121

EJB Timer Service shutdown info [{0}] not found. Shutdown time unknown. Cause: TBD
Solution: TBD EJB5122

EJB Timer Service shutdown at [{0}] Cause: TBD

Solution: TBD EJB5123

Rolling back timed out transaction [{0}] for [{1}] Cause: TBD
Solution: TBD EJB5124

Commit Option A is not currently supported. Using Commit Option B for [{0}] Cause: TBD
Solution: TBD EJB5125

Cannot add idle bean cleanup task Cause: TBD

Solution: TBD EJB5126

156

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

EJB Messages

Cannot add asynchronous task Cause: TBD

Solution: TBD EJB5127

Error during passivation of [{0}] Cause: TBD

Solution: TBD EJB5130

Error while adding idle bean passivator task Cause: TBD

Solution: TBD EJB5131

Error while adding idle bean removal task Cause: TBD

Solution: TBD EJB5132

Could not determine passivation directory Cause: TBD

Solution: TBD EJB5133

Error while creating SFSBStore manager Cause: TBD

Solution: TBD EJB5134

Error while removing idle beans Cause: TBD

Solution: TBD
Chapter 13 EJB Error Messages 157

EJB Messages

EJB5135

Error while removing expired beans Cause: TBD

Solution: TBD EJB5136

Creation of passivation directory failed for {0} Cause: TBD

Solution: TBD EJB5137

Initialization of store manager failed. Directory: {0} Cause: TBD

Solution: TBD EJB5138

Initialization of store manager failed Cause: TBD

Solution: TBD EJB5139

Error while loading bean state from store. Key: {0} Cause: TBD
Solution: TBD EJB5140

Error while loading bean state from store Cause: TBD

Solution: TBD EJB5141

158

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

EJB Messages

Error while removing bean state from store. Key: {0} Cause: TBD
Solution: TBD EJB5142

Error while removing bean state from store Cause: TBD

Solution: TBD EJB5143

Error while removing passivation directory: {0} Cause: TBD

Solution: TBD EJB5144

Error while removing passivation directory Cause: TBD

Solution: TBD EJB5145

Error while undeploying store manager Cause: TBD

Solution: TBD EJB5146

Error while undeploying store manager Cause: TBD

Solution: TBD EJB5147

Error while saving bean state to store. Key: {0} Cause: TBD
Solution: TBD
Chapter 13 EJB Error Messages 159

EJB Messages

EJB5148

Error while saving bean state to store Cause: TBD

Solution: TBD EJB5149

Error while initializing file store manager {0} Cause: TBD

Solution: TBD EJB5150

Error while initializing file store manager Cause: TBD

Solution: TBD EJB5151

Error while creating enterprise bean context for {0} during jacc callback Cause: TBD
Solution: TBD EJB5152

No methods registered yet for monitoring for {0} ; {1} ; {2} Cause: TBD
Solution: TBD EJB5153

Error while registering method {3} for {0} ; {1} ; {2} Cause: TBD
Solution: TBD EJB5154

160

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

EJB Messages

Unexpected error while registering method {3} for {0} ; {1} ; {2} Cause: TBD
Solution: TBD EJB5155

Error while unregistering method {3} for {0} ; {1} ; {2} Cause: TBD
Solution: TBD EJB5156

Unexpected error while unregistering method {3} for {0} ; {1} ; {2} Cause: TBD
Solution: TBD EJB5157

Error while registering container stats for {0} ; {1} ; {2} Cause: TBD
Solution: TBD EJB5158

Unexpected error while registering container stats for {0} ; {1} ; {2} Cause: TBD
Solution: TBD EJB5159

Error while unregistering container stats for {0} ; {1} ; {2} Cause: TBD
Solution: TBD EJB5160

Unexpected error while unregistering container stats for {0} ; {1} ; {2} Cause: TBD
Solution: TBD
Chapter 13 EJB Error Messages 161

EJB Messages

EJB5161

Error while registering pool stats for {0} ; {1} ; {2} Cause: TBD
Solution: TBD EJB5162

Unexpected error while registering pool stats for {0} ; {1} ; {2} Cause: TBD
Solution: TBD EJB5163

Error while unregistering pool stats for {0} ; {1} ; {2} Cause: TBD
Solution: TBD EJB5164

Unexpected error while unregistering pool stats for {0} ; {1} ; {2} Cause: TBD
Solution: TBD EJB5165

Error while registering cache stats for {0} ; {1} ; {2} Cause: TBD
Solution: TBD EJB5166

Unexpected error while registering cache stats for {0} ; {1} ; {2} Cause: TBD
Solution: TBD EJB5167

162

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

EJB Messages

Error while unregistering cache stats for {0} ; {1} ; {2} Cause: TBD
Solution: TBD EJB5168

Unexpected error while unregistering cache stats for {0} ; {1} ; {2} Cause: TBD
Solution: TBD

Chapter 13 EJB Error Messages

163

164

14
C H A P T E R

1 4

IOP Error Messages

This chapter describes messages for errors with a IOP prefix.

IOP Messages
IOP5001

Exception creating security tagged component: [{0}] Cause: TBD

Solution: TBD IOP5002

Exception occurred in init of IIOPSSLSocketFactory Cause: TBD

Solution: TBD IOP5003

Exception occurred in init of IIOPSSLSocketFactory client Cause: TBD

Solution: TBD IOP5004

Exception occurred in ciphers Cause: TBD

Solution: TBD
165

IOP Messages

IOP5005

Exception getting End point info: [{0}] Cause: TBD

Solution: TBD IOP5006

Exception creating socket: [{0}, {1}]. Please make sure the port is not being used. Cause: TBD
Solution: TBD IOP5008

Exception creating code base component: [{0}] Cause: TBD

Solution: TBD IOP5009

Exception occurred in starting transaction service :[{0}] Cause: TBD

Solution: TBD IOP5010

Exception creating POA: [{0}] Cause: TBD

Solution: TBD IOP5011

Exception getting the servant: [{0}] Cause: TBD

Solution: TBD IOP5012
166 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

IOP Messages

Some runtime exception ocurred in IIOP: [{0}] Cause: TBD

Solution: TBD IOP5013

Unable to create reference: [{0}] Cause: TBD

Solution: TBD IOP5014

Some exception occurred in handling a BadServerId call from the ORB in J2EEServer Cause: TBD
Solution: TBD IOP5015

Unable to read transaction.interoperability config property Cause: TBD

Solution: TBD IOP5016

No Security Service registered. Exiting interception point Cause: TBD

Solution: TBD IOP5017

No Security Service registered.Status not set Cause: TBD

Solution: TBD IOP5018

Exception occurred in importing name Cause: TBD

Solution: TBD
Chapter 14 IOP Error Messages 167

IOP Messages

IOP5019

Exception occurred in creating exported name Cause: TBD

Solution: TBD IOP5020

Exception getting password Cause: TBD

Solution: TBD IOP5021

Exception encoding Cause: TBD

Solution: TBD IOP5022

Exception decoding Cause: TBD

Solution: TBD IOP5023

Exception getting username and password Cause: TBD

Solution: TBD IOP5024

IOexception in IIOP Cause: TBD

Solution: TBD IOP5025

168

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

IOP Messages

name exception in IIOP Cause: TBD

Solution: TBD IOP5026

Found [{0}] instances of class([{1}]) Cause: TBD

Solution: TBD IOP5027

Invalid Security Mechanism! Cause: TBD

Solution: TBD IOP5028

Some runtime exception ocurred in IIOP Cause: TBD

Solution: TBD IOP5029

Exception occurred creating authentication token Cause: TBD

Solution: TBD IOP5030

Exception occurred creating ID token Cause: TBD

Solution: TBD IOP5031

Service Context exception Cause: TBD

Solution: TBD
Chapter 14 IOP Error Messages 169

IOP Messages

IOP5032

Reply message not one of CompleteEstablishContext or ContextError. Cause: TBD

Solution: TBD IOP5033

Unknown identity assertion type Cause: TBD

Solution: TBD IOP5034

Received Message not an EstablishContext message. Cause: TBD

Solution: TBD IOP5035

Error while creating a JAAS subject credential. Cause: TBD

Solution: TBD IOP5036

Security exception in IIOP Cause: TBD

Solution: TBD IOP5037

some generic exception occurred in IIOP Cause: TBD

Solution: TBD IOP5038

170

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

IOP Messages

Cannot propagate username/password required by target when using run as identity Cause: TBD
Solution: TBD IOP5039

The given mechanism type is unsupported. Cause: TBD

Solution: TBD IOP5040

Could not lookup the domain name of IP address = [{0}] Cause: TBD
Solution: TBD IOP5041

Principal propagation: Cannot find principal information in subject Cause: TBD

Solution: TBD IOP5042

Principal propagation: Cannot find credential information in subject. Cause: TBD

Solution: TBD IOP5043

Exception creating ASContext Cause: TBD

Solution: TBD IOP5044

Exception getting peer certificate chain Cause: TBD

Solution: TBD
Chapter 14 IOP Error Messages 171

IOP Messages

IOP5045

Invalid security mechanism: [{0}] Cause: TBD

Solution: TBD IOP5046

Invalid ID token: [{0}] Cause: TBD

Solution: TBD IOP5047

Security mechanism exception: [{0}] Cause: TBD

Solution: TBD IOP5048

Authentication exception: [{0}] Cause: TBD

Solution: TBD IOP5049

Login exception: [{0}] Cause: TBD

Solution: TBD IOP5050

Unknown message type Cause: TBD

Solution: TBD IOP5051

172

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

IOP Messages

More than one TAG_CSI_SEC_MECH_LIST tagged component found Cause: TBD

Solution: TBD IOP5052

Error starting bootserver Cause: TBD

Solution: TBD IOP5053

Received a locate request on a disabled connection. Locate requests are permitted. Cause: TBD
Solution: TBD IOP5054

Received a request on a disabled connection. Rejecting! Cause: TBD

Solution: TBD IOP5056

Exception when creating listener Cause: TBD

Solution: TBD IOP5055

Could not create listener on port [{0,number,integer}], host [{1}] Cause: TBD
Solution: TBD IOP5058

Chapter 14 IOP Error Messages

173

IOP Messages

Host unknown exception Cause: TBD

Solution: TBD IOP5059

Problem processing monitored attribute [{0}] Cause: TBD

Solution: TBD IOP5060

Exception when processing monitored attribute Cause: TBD

Solution: TBD IOP5057

Unknown host [{0}] - Cannot create listener Cause: TBD

Solution: TBD IOP5061

NameService did not start successfully Cause: TBD

Solution: TBD IOP5062

Unable to read IMR database Cause: TBD

Solution: TBD IOP5063

Unable to write to IMR database Cause: TBD

Solution: TBD
174 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

IOP Messages

IOP5064

Could not invoke [{0}] Cause: TBD

Solution: TBD IOP5065

Shutdown for server [{0,number,integer}] threw exception Cause: TBD

Solution: TBD IOP5066

locateServer: server held down ---- [{0,number,integer}] Cause: TBD

Solution: TBD IOP5067

ServerManagerImpl: handle throws OBJECT_NOT_EXIST exception Cause: TBD

Solution: TBD IOP5068

Error in ServerTableEntry == method=[{0}], server=[{1,number,integer}], state=[{2}], message=[{3}] Cause: TBD

Solution: TBD IOP5069

Exception in BindingIterator.Destroy() Cause: TBD

Solution: TBD IOP5070
Chapter 14 IOP Error Messages 175

IOP Messages

Unable to find DynAnyFactory Cause: TBD

Solution: TBD IOP5071

System exception in unknown_adapter call Cause: TBD

Solution: TBD IOP5077

Bad threads inactivity timeout property Cause: TBD

Solution: TBD IOP5072

Error in parsing ORBConstants.CLIENT_SSLVERSION Cause: TBD

Solution: TBD IOP5073

Caught NumberFormatException while parsing port Cause: TBD

Solution: TBD IOP5074

Bad disabled ports format Cause: TBD

Solution: TBD IOP5075

Bad minimum threads property Cause: TBD

Solution: TBD
176 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

IOP Messages

IOP5076

Bad maximum threads property Cause: TBD

Solution: TBD IOP5078

Cannot get peer certificate Cause: TBD

Solution: TBD IOP5079

Alias name {0} does not identify a key entry. Cause: TBD
Solution: TBD IOP5080

The server port {0} is not specified in iiop listener for SSL. Cause: TBD
Solution: TBD IOP5081

The cipher {0} is unknown or unsupported for given secure protocol. Cause: TBD
Solution: TBD IOP5082

The cipher attribute {0} is invalid. It must start with + or -. Cause: TBD
Solution: TBD

Chapter 14 IOP Error Messages

177

178

15
C H A P T E R

1 5

JBISE Error Messages

This chapter describes messages for errors with a JBISE prefix.

JBISE Messages
JBISE6001

JavaEEServiceEngine: Registering End Point : Service Name: [{0}] , Endpoint Name: [{1}] Cause: TBD
Solution: TBD JBISE6002

JavaEEServiceEngine: End Point : Service Name: [{0}] , Endpoint Name: [{1}] registered successfully Cause: TBD
Solution: TBD JBISE6003

JavaEEServiceEngine: Error occurred during registration of End Point : Service Name: [{0}] , Endpoint Name: [{1}] Cause: TBD
Solution: TBD JBISE6004
179

JBISE Messages

JavaEEServiceEngine: Web Service End point configuration not found in domain.xml Cause: TBD
Solution: TBD JBISE6005

JavaEEServiceEngine: End Point : Service Name: [{0}] , Endpoint Name: [{1}] enabled successfully Cause: TBD
Solution: TBD JBISE6006

JavaEEServiceEngine: End Point : Service Name: [{0}] , Endpoint Name: [{1}] disabled successfully Cause: TBD
Solution: TBD JBISE6007

JavaEEServiceEngine: End Point : Service Name: [{0}] , Endpoint Name: [{1}] removed successfully Cause: TBD
Solution: TBD JBISE6008

JavaEEServiceEngine: Error occurred during enabling of End Point : Service Name: [{0}] , Endpoint Name: [{1}] Cause: TBD
Solution: TBD JBISE6009

JavaEEServiceEngine: Error occurred during disabling of End Point : Service Name: [{0}] , Endpoint Name: [{1}] Cause: TBD
Solution: TBD JBISE6010
180 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

JBISE Messages

JavaEEServiceEngine: Processing incoming request for End Point : Service Name: [{0}] , Endpoint Name: [{1}] Cause: TBD
Solution: TBD JBISE6011

JavaEEServiceEngine: Processed incoming request for End Point : Service Name: [{0}] , Endpoint Name: [{1}] successfully Cause: TBD
Solution: TBD JBISE6012

JavaEEServiceEngine: Error occurred while processing request for End Point : Service Name: [{0}] , Endpoint Name: [{1}] Cause: TBD
Solution: TBD JBISE6013

JavaEEServiceEngine : Java EE Service Engine started successfully. Cause: TBD

Solution: TBD JBISE6014

JavaEEServiceEngine : Error occurred during startup of Java EE Service Engine [{0}] Cause: TBD
Solution: TBD JBISE6015

JavaEEServiceEngine : Java EE Service Engine stopped successfully../appserv-commons/src/java/com/sun/logging/enterprise/system/container/a Cause: TBD

Solution: TBD JBISE6015
Chapter 15 JBISE Error Messages 181

JBISE Messages

JavaEEServiceEngine : Java EE Service Engine stopped successfully../appserv-commons/src/java/com/sun/logging/enterprise/system/container/appcli Cause: TBD

Solution: TBD

182

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

16
C H A P T E R

1 6

JDO Error Messages

This chapter describes messages for errors with a JDO prefix.

JDO Messages
JDO7000

Error loading the default mapping policy which is used by database schema generation. Solution: Check that the classpath settings are not corrupted.
JDO74003

Internal error in CMP module. Solution: This is an Unexpected Internal Error. Please contact Sun with your application and the complete error log message.
JDO74005

CMR field is accessed in ejbCreate. Solution: Change bean code to access CMR fields in ejbPostCreate.
JDO74006

Parameter passed to Collection CMR set method is null. Solution: Use Collection.remove() method to remove all related beans from this Collection.
JDO74019
183

JDO Messages

Possible error in EJB Container and CMR runtime life cycle. Solution: This is an Unexpected Internal Error. Please turn on JDO and CMP logging and contact Sun with the complete error log message.
JDO74020

Possible error in EJB Container and CMR runtime life cycle. Solution: This is an Unexpected Internal Error. Please turn on JDO and CMP logging and contact Sun with the complete error log message.
JDO74021

ejbRemove or ejbStore is called in an active transaction without bean being loaded in the same transaction. Possible error in EJB Container and CMR runtime life cycle. Solution: This is an Unexpected Internal Error. Please turn on JDO and CMP logging and contact Sun with the complete error log message.
JDO74043

Create, remove, or update is called on a read-only bean. Solution: Do not attempt to update read-only beans. If update is required, the bean must be deployed as two different EJBs: as a read-only bean, and as an updateable bean. All updates must be done on the second bean.
JDO74045

State class is not generated properly for this CMP bean. Solution: This is an Unexpected Internal Error. Please contact Sun with your application and the complete error log message.
JDO75007

Internal error in CMP module. Solution: This is an Unexpected Internal Error. Please contact Sun with your application and the complete error log message.
JDO76604

JNDI name for the CMP resource is misspelled. CMP resource with this JNDI name is not registered with this instance. Solution: Check JNDI name for the resource you plan to use. Check JNDI name of the CMP resource specified in the module.
JDO7704
184 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

JDO Messages

Cannot identify related field. Cannot identify related class. Solution: Verify that relationship definition is correct.
JDO82000

System was not able to create specified logger. Error loading message bundle that corresponds to this logger. Solution: Check that the classpath settings are not corrupted. Check error log for the detailed reason.

Chapter 16 JDO Error Messages

185

186

17
C H A P T E R

1 7

JML Error Messages

This chapter describes messages for errors with a JML prefix.

JML Messages
JML5002

Unexpected exception occurred when encoding data Cause: TBD

Solution: TBD JML5003

Unexpected exception occurred when flushing data Cause: TBD

Solution: TBD JML5004

Unexpected IOException occurred when creating a new MimeMessage Cause: TBD

Solution: TBD JML5005

Unexpected Messaging Exception occurred when creating a new MimeMessage Cause: TBD
Solution: TBD
187

JML Messages

JML5006

Unexpected Exception occurred while reading the server response line(s) and adding them to the buffer Cause: TBD
Solution: TBD JML5007

Illegal characters in QP encoded stream [{0}] Cause: TBD

Solution: TBD JML5008

Failed to decode message Cause: TBD

Solution: TBD

188

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

18
C H A P T E R

1 8

JMS Error Messages

This chapter describes messages for errors with a JMS prefix.

JMS Messages
JMS5001

Starting JMS service... Cause: TBD

Solution: TBD JMS5002

Binding [{0}] Cause: TBD

Solution: TBD JMS5003

Couldnt start JMS service... Cause: TBD

Solution: TBD JMS5004

Session cannot be closed Cause: TBD

Solution: TBD
189

JMS Messages

JMS5005

resource handle could not be created Cause: TBD

Solution: TBD JMS5006

resource handle could not be registered Cause: TBD

Solution: TBD JMS5007

Illegal connection factory access to [{0}]. J2EE Components should access JMS Connection Factories through a resource-ref in java:comp/env Cause: TBD
Solution: TBD JMS5008

A resource-reference for JMS Connection Factory specifies container authorization but no username/password is available [{0}] Cause: TBD
Solution: TBD JMS5009

Calling createQueueConnection() on resource-ref with APPLICATION authentication. Should use createQueueConnection(username, password) instead Cause: TBD
Solution: TBD JMS5010

JMS Connection with container authentication cannot programmatically set username and password Cause: TBD
Solution: TBD
190 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

JMS Messages

JMS5011

Calling createTopicConnection() on resource-ref with APPLICATION authentication. Should use createTopicConnection(username, password) instead Cause: TBD
Solution: TBD JMS5012

Connection Factory [{0}] not found Cause: TBD

Solution: TBD JMS5013

Connection Factory not found Cause: TBD

Solution: TBD JMS5014

Unexpected pooling exception creating resource Cause: TBD

Solution: TBD JMS5015

Install JMS resources ... Cause: TBD

Solution: TBD JMS5016

Install JMS resources error: [{0}] Cause: TBD

Solution: TBD JMS5017
Chapter 18 JMS Error Messages 191

JMS Messages

Install JMS resources throw Exception Cause: TBD

Solution: TBD JMS5018

Delete Connection factory resource error: [{0}] Cause: TBD

Solution: TBD JMS5019

Delete connection factory resource got exception Cause: TBD

Solution: TBD JMS5020

Delete destination resource error: [{0}] Cause: TBD

Solution: TBD JMS5021

Delete destination resource got exception Cause: TBD

Solution: TBD JMS5022

A Message Queue broker instance [{0}] is already running at port [{1}]. Please configure a different port number for the JMS service. Cause: TBD
Solution: TBD JMS5023

192

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

JMS Messages

JMS service successfully started. Instance Name = {0}, Home = [{1}]. Cause: TBD
Solution: TBD JMS5024

JMS service startup failed. Cause: TBD

Solution: TBD JMS5025

JMS service shutting down. Cause: TBD

Solution: TBD JMS5026

JMS service shutdown complete. Cause: TBD

Solution: TBD JMS5027

Exception in creating JMS destination administered object [{0}]: [{1}] Cause: TBD
Solution: TBD JMS5028

Exception in creating JMS connection factory resource [{0}]: [{1}] Cause: TBD
Solution: TBD JMS5029

Successfully attached to an existing Message Queue broker. Instance Name = {0} Cause: TBD
Solution: TBD
Chapter 18 JMS Error Messages 193

JMS Messages

JMS5030

JMS resource {0} [Type: {1}] is disabled. Cause: TBD

Solution: TBD JMS5031

Exception in creating JMS destination administered object Cause: TBD

Solution: TBD JMS5032

Exception in creating JMS connection factory resource Cause: TBD

Solution: TBD JMS5033

Could not attach to an existing JMS service broker process. Cause: TBD
Solution: TBD JMS5034

Could not start the JMS service broker process. Cause: TBD
Solution: TBD JMS5035

Timed out after {0} milliseconds while trying to verify if the JMS service startup succeeded. Cause: TBD
Solution: TBD JMS5036
194 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

JMS Messages

More details may be available in the log file for the JMS service broker instance {0}. Please refer to the JMS provider documentation for the exact location of this log file. Cause: TBD
Solution: TBD JMS5037

Check permissions of MQ instance directory {0} Cause: TBD

Solution: TBD JMS5038

jms-service element in domain.xml is configured to have type={0}. JMS service will be started locally only if type is LOCAL. Cause: TBD
Solution: TBD

Chapter 18 JMS Error Messages

195

196

19
C H A P T E R

1 9

JTS Error Messages

This chapter describes messages for errors with a JTS prefix.

JTS Messages
JTS5001

Servant is already active. Servant is not active. Solution: This is an Unexpected Internal Error. Please contact Sun with the complete error log message.
JTS5005

Recovery or resync process got interrupted. Solution: See the server log for more details. This is an Unexpected Internal Error. Please contact Sun with the complete error log message.
JTS5008

Transaction log directory is not accessible. Solution: Make sure that the Transaction log directory (transaction-service.tx-log-dir in server configuration file) is proper and has the read, write permissions for the user of the application server.
JTS5015

ORB may not be running. Solution: Make sure that ORB is running. If ORB is running, this is an Unexpected Internal Error. Please contact Sun with the complete error log message.
197

JTS Messages

JTS5020

Configuration problem while giving the log path. Solution: Check the Transaction log path in server configuration file (transaction-service.tx-log-dir).
JTS5028

XAResource.recover has thrown an exception during recovery. Solution: See the exception Stack trace for more details.
JTS5032

Server could not communicate with the resource manager with in the retry limit. Solution: Make sure that resource manager is up and running or increase the retry limit (transaction-service.retry-timeout-in-seconds in the server configuration file).
JTS5040

ORB may not be running. Solution: See the server log for more details. This is an Unexpected Internal Error. Please contact Sun with the complete error log message.
JTS5041

Database driver or Resource Adapter has thrown XAException with the error message The resource manager is doing work outside a global transaction Solution: Check if the application is using the same XA pool outside the transactional context as well as in the transactional context. Some drivers do not allow this scenario. Another scenario to verify is, two separate XA pools pointing to the same backend with the same credentials and the second connection is obtained with in the same transaction, without closing the first connection.
JTS5064

Unexpected exception thrown from XAResource.end. Solution: See the server log for more details.
JTS5065

Transaction Log directory path is not valid or proper permissions are not there. Solution: Make sure that transaction log directory is valid and files in that directory have read write permissions.
JTS5066
198 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

JTS Messages

Possible cause is that transaction logs are corrupted. Solution: Please clean up the transaction-service.tx-log-dir/tx/* files and restart the server.

Chapter 19 JTS Error Messages

199

200

C H A P T E R

LAUNCHER Error Messages

20

2 0

This chapter describes messages for errors with a LAUNCHER prefix.

LAUNCHER Messages
LAUNCHER001

The laucher wasnt able to execute due to the following Exception. Cause: TBD
Solution: TBD LAUNCHER002

The launcher wasnt able to Cause: TBD

Solution: TBD LAUNCHER003

The Launcher encountered a problem with the configuration data from either domain.xml or processLauncher.xml. The launcher could not continue processing the request. Cause: TBD
Solution: TBD LAUNCHER004

201

LAUNCHER Messages

The log file {0} cant be created and/or written to. Cause: TBD
Solution: TBD LAUNCHER005

Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C\:\\Program Files\\Java\\jdk1.5.0\\bin; ) or the Appserver may not be able to start and/or stop. Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components. Cause: TBD
Solution: TBD

202

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

C H A P T E R

LCM Error Messages

21

2 1

This chapter describes messages for errors with a LCM prefix.

LCM Messages
LCM0101

Exception loading lifecycle module [{0}]; [{1}] Cause: TBD

Solution: TBD LCM0103

Treating failure loading the lifecycle module [{0}] as fatal; please check your classpath and the is-failure-fatal property. Cause: TBD
Solution: TBD LCM0201

Lifecycle module [{0}] threw an Exception; please check your lifecycle module. Cause: TBD
Solution: TBD LCM0203

203

LCM Messages

Lifecycle module [{0}] threw ServerLifecycleException Cause: TBD

Solution: TBD LCM0205

Treating the exception from lifecycle module event handler as fatal; please check the is-failure-fatal property. Cause: TBD
Solution: TBD

204

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

C H A P T E R

LDR Error Messages

22

2 2

This chapter describes messages for errors with a LDR prefix.

LDR Messages
LDR5001

ApplicationLoader: Cannot convert [{0}] into a URL. Cause: TBD

Solution: TBD LDR5002

UnExpected error occured while unloading ejb containers Cause: TBD

Solution: TBD LDR5003

Duplicate unique id [{0}] found in ejb descriptor [{1}]. Cause: TBD

Solution: TBD LDR5004

UnExpected error occured while creating ejb container Cause: TBD

Solution: TBD
205

LDR Messages

LDR5005

ApplicationLoader exception : Cause: TBD

Solution: TBD LDR5006

Failed to load deployment descriptor Cause: TBD

Solution: TBD LDR5007

Exception : Cause: TBD

Solution: TBD LDR5008

ConfigException : Cause: TBD

Solution: TBD LDR5009

UnExpected error occurred while creating URL. Check if filename and path is correct. Cause: TBD
Solution: TBD LDR5010

All ejb(s) of [{0}] loaded successfully! Cause: TBD

Solution: TBD LDR5011
206 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

LDR Messages

Class not found exception occurred while loading the ejbs Cause: TBD
Solution: TBD LDR5012

Jndi name conflict found in [{0}]. Jndi name [{1}] for bean [{2}] is already in use. Cause: TBD
Solution: TBD LDR5013

Naming exception while creating EJB container: Cause: TBD

Solution: TBD LDR5014

Cannot load policy file while loading EJB. Cause: TBD

Solution: TBD LDR5015

Exception : Cause: TBD

Solution: TBD LDR5016

Cannot load web service monitoring Cause: TBD

Solution: TBD LDR5017

Chapter 22 LDR Error Messages

207

LDR Messages

Cannot unload web service Cause: TBD

Solution: TBD LDR5018

ERROR while initializing ConnectorResourcesLoader [{0}] Cause: TBD

Solution: TBD LDR5100

Configuration exception encountered Cause: TBD

Solution: TBD LDR5101

Could not get classpath Cause: TBD

Solution: TBD LDR5102

Could not get classpath for appclient module Cause: TBD

Solution: TBD LDR5200

MalformedURLException. Cause: TBD

Solution: TBD LDR5201

208

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

LDR Messages

Environment property [{0}] is not set. Unable to construct code source path for [{1}] in ejb class loader. Cause: TBD
Solution: TBD LDR5202

Exception in EJBClassLoader Cause: TBD

Solution: TBD LDR5203

An error occurred while adding URL [{0}] to the EJB class loader. Please check the content of this URL. Cause: TBD
Solution: TBD LDR5204

Error : Request made to load class or resource [{0}] on an EJBClassLoader instance that has already been shutdown. [{1}] Cause: TBD
Solution: TBD LDR5205

Cannot load the foreign URL {0} using the stream handler for {1} Cause: TBD
Solution: TBD LDR5206

EJBClassLoader {1} was requested to find resource {0} after done was invoked from the following stack trace Cause: TBD
Solution: TBD LDR5207
Chapter 22 LDR Error Messages 209

LDR Messages

EJBClassLoader {1} was requested to find class {0} after done was invoked from the following stack trace Cause: TBD
Solution: TBD LDR5208

Invalid attempt to close JarFile managed by EJBClassLoader Cause: TBD

Solution: TBD LDR5209

Error closing an open stream during loader clean-up Cause: TBD

Solution: TBD LDR5210

Input stream has been finalized or forced closed without being explicitly closed; stream instantiation reported in following stack trace Cause: TBD
Solution: TBD LDR5211

Error checking for existing of {0} in {1} Cause: TBD

Solution: TBD LDR5212

Error processing file with path {0} in {1} Cause: TBD

Solution: TBD LDR5213

210

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

LDR Messages

Error closing zip file for class path entry {0} Cause: TBD
Solution: TBD LDR5214

Error closing zip file for duplicate class path entry {0}./appserv-commons/src/java/com/sun/logging/enterprise/system/core/LogStrings.prope Cause: TBD
Solution: TBD LDR5214

Error closing zip file for duplicate class path entry {0}./appserv-commons/src/java/com/sun/logging/enterprise/system/core/LogStrings.prope Cause: TBD
Solution: TBD

Chapter 22 LDR Error Messages

211

212

C H A P T E R

MDB Error Messages

23

2 3

This chapter describes messages for errors with a MDB prefix.

MDB Messages
MDB0002

Could not get server session: [{0}] Cause: TBD

Solution: TBD MDB0003

Exception on getting server session Cause: TBD

Solution: TBD MDB0006

Get session failed: [{0}] Cause: TBD

Solution: TBD MDB0007

Get session throws exception Cause: TBD

Solution: TBD
213

MDB Messages

MDB0008

Session.run() throws Exception [{0}] Cause: TBD

Solution: TBD MDB0009

Session.run() throws Exception Cause: TBD

Solution: TBD MDB00010

Exception while cleaning up ServerSession [{0}] Cause: TBD

Solution: TBD MDB00011

Exception while cleaning up ServerSession Cause: TBD

Solution: TBD MDB00012

ServerSession.getSession() must be called first before calling ServerSession.start() ! Cause: TBD

Solution: TBD MDB00013

Create ServerSession error: [{0}] Cause: TBD

Solution: TBD MDB00014
214 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

MDB Messages

Exception while Creating ServerSession Cause: TBD

Solution: TBD MDB00015

[{0}]: Message-driven bean destination name [{1}] not found Cause: TBD
Solution: TBD MDB00016

[{0}]: Name not found exception: [{1}] Cause: TBD

Solution: TBD MDB00017

An error occurred during the message-driven beancontainer initialization at runtime. Cause: The most common cause for this is that the physical resource (e.g. Queue) from which the message-driven bean is consuming either does not exist or has been configured incorrectly. Another common error is that the message-driven bean implementation class does not correctly implement the required javax.ejb.MessageBean or MessageListener interfaces.
Solution: Double-check that the JNDI name of the message-driven bean's resource in sun-ejb-jar.xml is correct. It is also useful to run the verifier to check that the code requirements for the message-driven bean class have been fulfilled. MDB00018

[{0}]: Closing message-driven bean container connection Cause: TBD

Solution: TBD MDB00019

[{0}]: Message-driven bean container connection closed Cause: TBD

Solution: TBD
Chapter 23 MDB Error Messages 215

MDB Messages

MDB00020

[{0}]: Exception in closing message-driven bean container: [{1}] Cause: TBD

Solution: TBD MDB00021

[{0}]: Message-driven bean destination type mismatch. Destination [{1}] is not of type [{2}] Cause: TBD
Solution: TBD MDB00022

[{0}]: Message-driven bean listening on JMS destination [{1}] Cause: TBD

Solution: TBD MDB00023

[{0}]: Invalid max-messages-load [{1}] Cause: TBD

Solution: TBD MDB00024

[{0}]: Message-driven bean container connection factory [{1}] not found: [{2}] Cause: TBD
Solution: TBD MDB00025

[{0}]: Message-driven bean connection factory type mismatch. Connection factory [{1}] is not of type [{2}] Cause: TBD
Solution: TBD MDB00026
216 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

MDB Messages

[{0}]: Unable to start message-driven bean container connection: [{1}] Cause: TBD
Solution: TBD MDB00027

[{0}]: Connection exception event for [{1}], [{2}], [{3}] Cause: TBD
Solution: TBD MDB00028

[{0}]: Message-driven bean container using external connection factory object: [{1}] Cause: TBD
Solution: TBD MDB00029

[{0}]: Register message-driven bean container bean-pool monitor failed: [{1}] Cause: TBD
Solution: TBD MDB00030

[{0}]: Exception in setting up message-driven bean container: [{1}] Cause: TBD

Solution: TBD MDB00031

[{0}]: Message-driven bean container connection factory [{1}] not found. Use default Cause: TBD
Solution: TBD MDB00032

Chapter 23 MDB Error Messages

217

MDB Messages

[{0}]: Message-driven bean container connection factory not specified. Use default Cause: TBD
Solution: TBD MDB00033

[{0}]: Message-driven bean container reconnecting ... Cause: TBD

Solution: TBD MDB00034

[{0}]: Message-driven bean container reconnected Cause: TBD

Solution: TBD MDB00035

[{0}]: Exception on message-driven bean pool close: [{1}] Cause: TBD

Solution: TBD MDB00036

[{0}]: Message-driven bean preInvoke() failed Cause: TBD

Solution: TBD MDB00037

[{0}]: Message-driven bean invocation exception: [{1}] Cause: TBD

Solution: TBD MDB00038

218

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

MDB Messages

[{0}]: No message-driven bean context in message listener : [{1}] Cause: TBD

Solution: TBD MDB00039

[{0}]: Message sent to a destroyed message-driven bean : [{1}] , [{2}] Cause: TBD
Solution: TBD MDB00040

[{0}]: Message-driven bean CMT can not be supported. Cause: TBD

Solution: TBD MDB00041

[{0}]: Message-driven bean onMessage error: [{1}] Cause: TBD

Solution: TBD MDB00042

[{0}]: No invocation for message [{1}] Cause: TBD

Solution: TBD MDB00043

[{0}]: Exception in reading mdb-container configuration: [{1}] Cause: TBD

Solution: TBD MDB00044

Deploying message-driven bean [{0}], consuming from [{1}] Cause: TBD

Solution: TBD
Chapter 23 MDB Error Messages 219

MDB Messages

MDB00045

Undeploying message-driven bean [{0}] Cause: TBD

Solution: TBD MDB00046

Message-driven bean [{0}]: onMessage RuntimeException occurred: [{1}]. [{2}] Cause: TBD
Solution: TBD MDB00047

Message-driven bean [{0}]: Some application or unchecked exception occurred : [{1}] Cause: TBD
Solution: TBD MDB00048

An error occurred during the pre-invocation processing before a message-driven bean MessageListener method is called. Cause: This is often caused by some transaction-related errors.
Solution: Double-check the transaction configuration for the message-driven bean and consult stack trace for additional details. MDB00049

Message-driven bean [{0}]: Exception in postinvoke : [{1}] Cause: TBD

Solution: TBD MDB00050

An error occurred during the lifecycle initialization of a message-driven bean instance. Cause: This typically means a system exception was thrown from the bean code during the execution of the no-arg constructor, the setMessageDrivenContext method, or the ejbCreate method. Common causes are failed naming service lookups coding errors, or ClassNotFound errors.
220 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

MDB Messages

Solution: Check the stack trace to see which method threw the exception. If the error was caused by a NamingException, double-check the environment configuration (ejb-refs, resource-refs, etc.) in the deployment descriptor against the coded names. It would also be useful to run the verifier. MDB00051

An error occurred while the container was destroying an instance of a message-driven bean. Cause: The most common cause is that a message-driven bean class threw a system exception from its ejbRemove method.
Solution: Check the message driven bean's ejbRemove implementation to determine what would result in an exception. Also consult the stack trace for more information. MDB00052

An error occurred while the container was enabling the message flow into a message-driven bean. Cause: This is an internal error that typically means there is a problem with the messaging system from which the message-driven bean is consuming.
Solution: Check the stack trace for more details. MDB00053

Message-driven bean [{0}] container cleanup exception: [{1}] Cause: TBD

Solution: TBD MDB00054

Message-driven bean [{0}]: Exception setting bean context : [{1}] Cause: TBD
Solution: TBD MDB00055

Message-driven bean [{0}]: Exception in closing consumer : [{1}] Cause: TBD

Solution: TBD MDB00056
Chapter 23 MDB Error Messages 221

MDB Messages

Message-driven bean [{0}]: start cleanup for shutdown Cause: TBD

Solution: TBD MDB00057

Message-driven bean [{0}]: finished cleanup for shutdown Cause: TBD

Solution: TBD MDB00058

Message-driven bean [{0}]: connection exception [{1}] during server shutdown. ignore. Cause: TBD
Solution: TBD MDB00059

{0}]: Exception on unregistering monitor mbean: [{1}] Cause: TBD

Solution: TBD MDB00060

[{0}]: Invalid value [{1}] for [{2}] , use [{3}] instead Cause: TBD
Solution: TBD

222

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

C H A P T E R

NAM Error Messages

24

2 4

This chapter describes messages for errors with an NAM prefix.

NAM Messages
NAM0002

Problem with serializing or deserializing of the object Solution: Check the class hierarchy to see if all the classes are Serializable.
NAM0003

Problem in creating a remote object for SerialContextProvider. Cause: Problem during publishing SerialContextProvider in CosNaming Service.
Solution: Check if ORB CosNaming Service initialized. Check if ORB CosNaming Service initialized. NAM0004

Communications Server may not be running at port intended. Cause: Possible Network Error.
Solution: Check to see if the Communications Server is up and running on the port intended. The problem could be because of incorrect port. Check to see if you can access the host on which the Communications Server is running. NAM0005

The JMS Connection Factory may not be bound to a JNDI name. Solution: Check the list of JNDI bindings by clicking on the JNDI tree on the Administrators console. Check the JMS resource references bindings.
223

NAM Messages

NAM0006

The JMS destination may not be bound to a JNDI name. Solution: Check the list of JNDI bindings by clicking on the JNDI tree on the Administrators console. Check the JMS resource references bindings.
NAM0007

Unresolved Message Destination Reference Solution: Check if the Message Destination has been linked to a Message Destination
NAM0008

Invalid Destination Name Solution: Check Destination Name

NAM1000

No endpoints selected. Solution: Check system property com.sun.appserv.iiop.endpoints.

NAM1001

No endpoints selected. Solution: Check system property com.sun.appserv.iiop.endpoints.

NAM1002

Bad JNDI provider URL Solution: Check system property java.naming.provider.url.

NAM1003

Bad host:port entry Solution: Check system property com.sun.appserv.iiop.endpoints.

NAM1004

Unknown host Solution: Check the host entry.

NAM1005

No endpoints selected. Solution: Check system property com.sun.appserv.iiop.endpoints.

224 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

C H A P T E R

RAR Error Messages

25

2 5

This chapter describes messages for errors with a RAR prefix.

RAR Messages
RAR5003

Error loading J2EE resource file Cause: TBD

Solution: TBD RAR5004

JDBC driver threw an exception while recovery. Cause: Resource Adapter threw an exception during recovery in case of connectors.
Solution: Check database or EIS log for details. Check whether the connection pool configuration is proper. Check whether domain.xml is accessible. RAR5005

The XA resource has been deleted before attempting recovery Cause: The XA resource is no longer referenced in domain.xml. The database server that the XA resource points to is no longer running. The configuration information for the XA Resource has been changed before attempting recovery.
Solution: Check that the XA Resource and the pool it points to is still defined in domain.xml.

Check that the XA Resource is present in the list of resource-refs in domain.xml. Check that the Database server is up and running. Check if the configuration info of the XA resource
225

RAR Messages

and the pool it points to is sane. In particular check that the datasourceclassname in the pool is correct and the XA resource points to the correct pool.
RAR5007

Exception while creating persistent manager resource. Solution: Check whether the persistent manager factory class is configured properly and is available in the classpath. Check whether the JDBC resource name is correct and is configured properly.
RAR5008

Naming provider and port are not set in the initial context Cause: The Naming provider is not up.
Solution: Check the jndi.properties file has the naming provider host and port specified.

Check if the naming provider is up and listening on the port specified in domain.xml
RAR5009

Could not create an instance of factory-class. Solution: Make sure that factory-class name is configured correctly. Make sure that factory-class is available in the classpath of the application server
RAR5010

External JNDI resource has a wrong factory-class configuration Solution: Verify that factory class is an instance of javax.naming.spi.InitialContextFactory.
RAR5011

Could not create Initial Context. Solution: Make sure that the external-jndi-resource configuration is sufficient to create an initial context.
RAR5012

Could not create Initial context factory. Solution: Make sure that the external-jndi-resource configuration is sufficient to create an initial context factory.
RAR5013
226 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

RAR Messages

Error in installing connection factories Cause: TBD

Solution: TBD RAR5014

Cannot load class [{0}]. Cause: TBD

Solution: TBD RAR5015

Classpath is not properly set in domain.xml Cause: The application server process does not have read permissions on the directory that holds the classes/jar.
Solution: Check that the classpath attribute in the java-config includes a reference to the jar/package directory for the class. You do not have read permissions on the directory that holds the classes/jar. RAR5016

Error accessing configuration file. Cause: TBD

Solution: TBD RAR5017

Cannot locate connection descriptor by name Cause: TBD

Solution: TBD RAR5018

Cannot create connection factory Cause: TBD

Solution: TBD RAR5019
Chapter 25 RAR Error Messages 227

RAR Messages

Unexpected exception in creating new file Cause: TBD

Solution: TBD RAR5020

Could not configure persistent manager resource properly. Solution: Make sure that the JDBC resource name, you have configured is correct. Check whether the persistent manager factory class is proper. Check whether the persistent manager factory class has a setConnectionFactoryName method.
RAR5021

Error in installing resource adapters Cause: TBD

Solution: TBD RAR5022

Error in binding to JNDI namespace Cause: TBD

Solution: TBD RAR5023

Error removing connection factory Cause: TBD

Solution: TBD RAR5024

Error adding J2EE resource Cause: TBD

Solution: TBD RAR5025

Error removing J2EE resource Cause: TBD

Solution: TBD
228 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

RAR Messages

RAR5026

Failed to complete transaction.Error Message: [{0}]. Cause: TBD

Solution: TBD RAR5027

Unexpected exception in resource pooling Cause: TBD

Solution: TBD RAR5029

Unexpected exception while registering component Cause: TBD

Solution: TBD RAR5030

Unexpected exception while registering synchronization Cause: TBD

Solution: TBD RAR5031

System Exception Cause: TBD

Solution: TBD RAR5032

Unexpected exception while returning resource to pool Cause: TBD

Solution: TBD RAR5033

Chapter 25 RAR Error Messages

229

RAR Messages

ASSERT FAILED!!! Cause: TBD

Solution: TBD RAR5034

Failed to resize pools Cause: TBD

Solution: TBD RAR5035

Error while closing the physical connection. Error while destroying the connector managed connection. Solution: Examine the exception stack trace for details.
RAR5036

Resource reference is not defined for JNDI name [{0}] Cause: TBD
Solution: TBD RAR5037

Username/password not specified for resource reference [{0}]. Defaulting to one in the pool. Cause: TBD
Solution: TBD RAR5038

Could not create a physical connection. Solution: Connection pool is configured incorrectly. Check that database is running properly. Check that EIS (in case of connectors) is running properly. Check that SJS MQ (in case of JMS) is running properly. Verify that network connection to Database/EIS/MQ is properly configured.
RAR5042

The XA resource has been deleted before attempting recovery. Cause: The XA resource is not properly referenced because:
230 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

RAR Messages

The XA resource is no longer referenced in domain.xml. The database server that the XA resource points to is no longer running The configuration information for the XA Resource has been changed before attempting recovery

Solution: Check that the XA Resource and the pool it points to is still defined in domain.xml.

Check that the XA Resource is present in the list of resource-refs in domain.xml. Check that the Database server is up and running. Check if the configuration info of the XA resource and the pool it points to is sane. In particular check that the datasourceclassname in the pool is correct and the XA resource points to the correct pool.
RAR5043

Exception while creating persistent manager resource. Solution: Check whether the persistent manager factory class is configured properly and is available in the classpath. Check whether the JDBC resource name is correct and is configured properly.
RAR5044

Could not configure persistent manager resource properly. Solution: Make sure that the JDBC resource name, you have configured is correct. Check whether the persistent manager factory class is proper. Check whether the persistent manager factory class has a setConnectionFactoryName method.
RAR5045

Naming provider and port are not set in the JNDI providers property file Cause: The Naming provider is not up
Solution: Check the jndi.properties file has the naming provider host and port specified.

Check if the naming provider is up and listening on the port specified in domain.xml.
RAR5046

Classpath is not properly set in domain.xml Cause: You do not have read permissions on the directory that holds the classes/jar.
Solution: Check that the classpath attribute in the java-config includes a reference to the jar/package directory for the class. Check that the directory where the classes/jars reside have read permission for the application server process. RAR5047
Chapter 25 RAR Error Messages 231

RAR Messages

Could not create Initial Context. Solution: Make sure that the external-jndi-resource configuration is sufficient to create an initial context.
RAR5048

The configuration for the JDBC resource could not be read from domain.xml Cause: This is an internal server error. Please contact Sun Microsystems with the complete error log
RAR5051

Jdbc pool monitoring bean registration failure Cause: TBD

Solution: TBD RAR5052

Failed to look up connection pool resource name Cause: TBD

Solution: TBD RAR5053

underlying connection not valid Cause: TBD

Solution: TBD RAR5055

Missing parameter in properties file [{0}]. Cause: TBD

Solution: TBD RAR5058

Could not create physical connection during connection pool resizing. Solution: Check whether your network connection to the database or EIS is proper. Check your database/ EIS logs for possible connection creation errors.
RAR5059
232 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

RAR Messages

Binding [JDBC DataSource Name: {0}, Pool Name: {1}] Cause: TBD
Solution: TBD RAR5060

Install JDBC Datasources ... Cause: TBD

Solution: TBD RAR5061

Exception caught and ignored: {0} Cause: TBD

Solution: TBD RAR5062

Exception caught while getting Local Transaction Cause: TBD

Solution: TBD RAR5062

Exception while closing connection Cause: TBD

Solution: TBD RAR5063

The class specified in datasourceclassname attribute in the jdbc-connection-pool is not of type javax.sql.XADataSource. Please consult your database vendors documentation to identify the class that implements the javax.sql.XADataSource Solution: Check if the datasourceclass implements the javax.sql.XADataSource interface. Try using the javap tool for this purpose.
RAR5065

Chapter 25 RAR Error Messages

233

RAR Messages

The class specified in datasourceclassname attribute in the jdbc-connection-pool is not of type javax.sql.ConnectionPoolDataSource. Please consult your database vendors documentation to identify the class that implements the javax.sql.ConnectionPoolDataSource. Solution: Check if the datasourceclass implements the javax.sql.ConnectionPoolDataSource interface. Try using the javap tool for this purpose.
RAR5066

Exception while getting pooled connection. Cause: The Database server is not up and running. The connection pool is full and cannot allocate more connections. The Database server threw some unexpected exception. Please study the exception message for more details
RAR5067

Exception while getting XA Connection: {0} Cause: TBD

Solution: TBD RAR5068

There are no managed connections in the connection pool at this time There is an internal server error. Please contact Sun Microsystems with the complete log message. Solution: This is an internal server error. Please contact Sun Microsystems with the complete error log. This is an internal server error. Please contact Sun Microsystems with the complete error log.
RAR5069

The Connection object is now invalid due to database restart Cause: The connection object is now invalid since the database has either restarted or is not up and running. The JDBC driver cannot provide the required information.
Solution: Switch on the connection validation property of the connection pool and try again. If the database has restarted, restart the application server as well or set the connection validation property in the pool to avoid this in the future. If the database server is not up, please bring it up. Check the server log and please contact Sun Microsystems with the complete error log. RAR5070
234 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

RAR Messages

The Connection object is now invalid due to database restart. Cause: The connection object is now invalid since the database has either restarted or is not up and running. The JDBC driver cannot provide the required information.
Solution: Switch on the connection validation property of the connection pool and try again. If the database has restarted, restart the application server as well or set the connection validation property in the pool to avoid this in the future. If the database server is not up, please bring it up. Check the server log and please contact Sun Microsystems with the complete error log. RAR5071

Exception creating CciInteraction object Cause: TBD

Solution: TBD RAR5072

Exception while clearing warnings from Statement object Cause: TBD

Solution: TBD RAR5073

Exception while getting warnings from Statement object Cause: TBD

Solution: TBD RAR5074

The Connection object is now invalid due to database restart Cause: The connection object is now invalid since the database has either restarted or is not up and running. The JDBC driver cannot provide the required information.
Solution: Switch on the connection validation property of the connection pool and try again. If the database has restarted, restart the application server as well or set the connection validation property in the pool to avoid this in the future. If the database server is not up, please bring it up. Check the server log and please contact Sun Microsystems with the complete error log. RAR5075
Chapter 25 RAR Error Messages 235

RAR Messages

Exception while setting up Statement according to Spec Cause: TBD

Solution: TBD RAR5076

Exception while preparing statement Cause: TBD

Solution: TBD RAR5077

Exception while closing statement Cause: TBD

Solution: TBD RAR5078

Exception while beginning local transaction Cause: TBD

Solution: TBD RAR5079

Exception while commiting local transaction Cause: TBD

Solution: TBD RAR5080

Exception while commiting xa transaction Cause: TBD

Solution: TBD RAR5081

Exception while rolling back local transaction Cause: TBD

Solution: TBD
236 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

RAR Messages

RAR5082

Exception while creating CciManagedConnection Cause: TBD

Solution: TBD RAR5083

Exception while destroying physical connection Cause: TBD

Solution: TBD RAR5084

Exception while creating physical connection Cause: TBD

Solution: TBD RAR5085

Exception while getting XA resource Cause: TBD

Solution: TBD RAR5086

Exception creating CciManagedConnectionMetaData Cause: TBD

Solution: TBD RAR5087

The Connection object is now invalid due to database restart Cause: The connection object is now invalid since the database has either restarted or is not up and running. The JDBC driver cannot provide the required information.
Solution: Switch on the connection validation property of the connection pool and try again. If the database has restarted, restart the application server as well or set the connection validation property in the pool to avoid this in the future. If the database server is not up, please bring it up. Check the server log and please contact Sun Microsystems with the complete error log.
Chapter 25 RAR Error Messages 237

RAR Messages

RAR5088

Exception while checking if ResultSet can detect deletes Cause: TBD

Solution: TBD RAR5089

Exception while checking if ResultSet can detect updates Cause: TBD

Solution: TBD RAR5090

Exception while checking if ResultSet can detect other deletes Cause: TBD
Solution: TBD RAR5091

Exception while checking if ResultSet can detect inserts Cause: TBD

Solution: TBD RAR5092

Exception while checking if ResultSet can detect other updates Cause: TBD
Solution: TBD RAR5093

Exception while checking if ResultSet can detect own updates Cause: TBD
Solution: TBD RAR5094

238

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

RAR Messages

Exception while checking if ResultSet can detect other inserts Cause: TBD
Solution: TBD RAR5095

Exception while checking if ResultSet can detect own inserts Cause: TBD
Solution: TBD RAR5096

Exception while checking if ResultSet can detect own deletes Cause: TBD
Solution: TBD RAR5097

Exception while checking if RA supports concurrency in combo with give RS Cause: TBD
Solution: TBD RAR5098

Exception while checking if RA supports a type of RS Cause: TBD

Solution: TBD RAR5099

Classpath is not properly set in domain.xml Cause: The application server process does not have read permissions on the directory that holds the classes/jar.
Solution: Check if the server classpath specified in the java-config element in domain.xml has an entry for the jar containing this class. Check that the directory where the classes/jars reside have read permission for the application server process. RAR5100
Chapter 25 RAR Error Messages 239

RAR Messages

Classpath is not properly set in domain.xml Cause: The application server process does not have read permissions on the directory that holds the classes/jar.
Solution: Verify that the read permissions on the classes/jar directory are set properly. RAR5101

The Communications Server process does not have read access to the directory where this class resides. The Communications Server process does not have security permissions to access this code. Solution: Check if the application server has read permissions on the directory where this class/jar containing this class resides. Check if your security manager policy is configured properly.
RAR5102

The application server process do not have permission to access the code base where the class resides. This is an internal server/JVM error. Please contact Sun Microsystems with the complete error log. Solution: See if the application server process has permission to read the directory where the class/jar resides. Check if all relevant JVM patches are installed on your machine. Please contact Sun Microsystems with the complete error log.
RAR5103

Error configuring the DataSource object. Cause: The pool parameters in domain.xml are improper. The application server process does not have enough permissions to access the DataSource class.
Solution: Check that the pool parameters specified in domain.xml are correct. For example, check that parameters that expect numeric values are numerals. Check that the application server process has permissions to read the directory where the class resides. RAR5104

Error configuring the DataSource object. Cause: The pool parameters in domain.xml are improper. The application server process does not have enough permissions to access the DataSource class.
Solution: Check that the pool parameters specified in domain.xml are correct. For example, check that parameters that expect numeric values are numerals. Check that the application server process has permissions to read the directory where the class resides.
240 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

RAR Messages

RAR5105

The connection validation method is incorrect, it should be one of auto-commit, meta-data, table. The connection is no longer valid. It could have been rendered invalid due to database restart/shutdown. Solution: Check if the connection validation is one of: auto-commit, meta-data, or table. If the method is table, check that the table name is correct. If the database has been restarted, restart the application server as well. If the database is down, start it up.
RAR5106

The database connection is invalid. Cause: The cause can be either:

The database has been shutdown or restarted. The network connection to the database has been lost.

Solution: If the database has been restarted, restart the application server as well. To avoid this in the future set the connection validation property in the pool. Check that the database is up and running and the network connection to the database is still alive. RAR5107

The database connection is invalid. Cause: The cause can be either:

The database has been shutdown or restarted. The network connection to the database has been lost.

Solution: If the database has been restarted, restart the application server as well. To avoid this in the future set the connection validation property in the pool. Check that the database is up and running and the network connection to the database is still alive. RAR5108

The database connection is invalid. Cause: The cause can be either

The database has been shutdown or restarted. The network connection to the database has been lost.

Solution: If the database has been restarted, restart the application server as well. To avoid this in the future set the connection validation property in the pool. Check that the database is up and running and the network connection to the database is still alive. RAR5109
Chapter 25 RAR Error Messages 241

RAR Messages

JDBC driver has thrown an SQLException while setting the isolation level. Solution: Check your connection pool configuration and make sure that the isolation level is correct. Check whether your driver supports the isolation level you have specified in the connection pool.
RAR5110

The URL specified is incorrect. The database server is not up and running. Solution: Check if the URL specified in the getConnection call is correct. Consult the JDBC driver vendor's documentation for the correct URL format. Check that the Database server is up and running.
RAR5111

The class specified in datasourceclassname attribute in the jdbc-connection-pool is not of type javax.sql.DataSource. Solution: Please consult your database vendors documentation to identify the class that implements javax.sql.DataSource. Try using the javap tool for this purpose.
RAR5112

The class specified in datasourceclassname attribute in the jdbc-connection-pool is not of type javax.sql.XADataSource. Solution: Please consult your database vendors documentation to identify the class that implements the javax.sql.XADataSource. Try using the javap tool for this purpose.
RAR5113

Error creating a connection from the supplied information. Cause: The connection pool is full and cannot allocate more connections. The Database server threw some unexpected exception. Please study the exception message for more details.
Solution: Check that the Database server is up and running. Check if the size of your

connection pool is sufficiently large for serving all requests. Check the server log and please contact Sun Microsystems with the full error log.
RAR5114

Error creating a connection from the supplied info. Cause: The Connection pool is full and incapable of serving more requests at this point. The database is down. Please try later. There is an internal server error. Please contact Sun Microsystems with the complete log message.
242 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

RAR Messages

Solution: Check if the database server is correctly configured. Check if your pool size is sufficient to server all simultaneous connection requests. Check the server log and contact Sun Microsystems with the complete error message RAR5115

Error cleaning up handles associated with this ManagedConnection Cause: TBD

Solution: TBD RAR5116

Error creating a connection from the supplied info. Cause: The Database server is not up and running. The connection pool is full and cannot allocate more connections. The Database server threw some unexpected exception. Please study the exception message for more details.
Solution: Check that the Database server is up and running. Check if the size of your connection pool is sufficiently large for serving all requests. Check the server log and please contact Sun Microsystems with the full error log. RAR5117

Error while obtaining a connection from the pool. Solution: Check your connection pool configuration.
RAR6000

Illegal access Error while instantiating one of the resource adapter JavaBeans like ManagedConnectionFactory or ResourceAdapter JavaBean classes. Solution: Check whether the resource adapter has any specific security requirements.
RAR6001

Error while locating one of the resource adapter JavaBeans like ManagedConnectionFactory or ResourceAdapter JavaBean classes. Solution: Check if the resource adapter is bundled properly. Resource adapter jar file deployment descriptor specifies correct class names.
RAR6002

Chapter 25 RAR Error Messages

243

RAR Messages

Error while instantiating one of the resource adapter JavaBeans like ManagedConnectionFactory or ResourceAdapter JavaBean. Solution: Check if the resource adapter is bundled properly with all the classes.
RAR6003

Could not access class: {0} Cause: TBD

Solution: TBD RAR6004

Illegal access Error while instantiating one of the resource adapter JavaBeans like ManagedConnectionFactory or ResourceAdapter JavaBean classes. Solution: Check whether the resource adapter has any specific security requirements.
RAR6005

Error while creating ManagedConnectionFactory. Solution: Check if the resource adapter is bundled properly. Check whether connection pool configuration has correct properties for MCF. Check resource adapter documentation for configuring correct properties of MCF.
RAR6006

Failed to get ResourcesUtil object: {0} Cause: TBD

Solution: TBD RAR6007

Runtime could not obtain list of resources of this resource adapter. Solution: Check whether the resource adapter configuration is proper.
RAR6008

Resource Adapter threw an exception during ResourceAdapter.stop() method. Solution: Check your resource adapter documentation about ResourceAdapter.stop() method.
RAR6009

244

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

RAR Messages

A resource (connection pool, connector resource or admin object) pertaining to the resource adapter is existing. Solution: Check whether the cascade option of undeploy is false.
RAR6010

Resource Adapter is already active in the connector runtime. Solution: Check whether a previous resource adapter deployment is still available.
RAR6011

Failed to obtain the classloader: {0} Cause: TBD

Solution: TBD RAR6012 Solution: There is an internal server error. Please contact Sun Microsystems with the

complete log message. Check whether resource adapter threw a null pointer exception.
RAR6013 Solution: There is an internal server error. Please contact Sun Microsystems with the

complete log message.

RAR6014

Incomplete or erroneous resource adapter deployment. Solution: Check whether the RA deployment is proper and complete.
RAR6015

Connection pool is not created properly. Solution: Check your resource configuration, whether you are using correct connection pool name.
RAR6016

Resource Adapter is not yet initialized in the connector runtime. Solution: Check whether the deployment of the resource adapter is complete.
RAR6017

Chapter 25 RAR Error Messages

245

RAR Messages

Incomplete or erroneous connection pool creation. Solution: Check whether connection pool is created and is proper.
RAR6018

Failed to add MCF to connector registry: {0} Cause: TBD

Solution: TBD RAR6019

Incomplete or erroneous resource adapter deployment. Solution: Check whether the RA deployment is proper and complete.
RAR6020

Failed to publish connection pool object in JNDI: {0} Cause: TBD

Solution: TBD RAR6021

Error while creating ManagedConnectionFactory. Solution: Check if the resource adapter is bundled properly. Check whether connection pool configuration has correct properties for MCF. Check whether the resource adapter require security permissions to load the classes. Some adapters require getClassLoader() permission.
RAR6022

NullPointerException while creating ManagedConnectionFactory. Solution: Check whether resource adapter throws null pointer exception.
RAR6023 Solution: There is an internal server error. Please contact Sun Microsystems with the

complete log message.

RAR6024

Failed to bind connector resource in JNDI: {0} Cause: TBD

Solution: TBD
246 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

RAR Messages

RAR6025

Could not read the deployment descriptor of the resource adapter. Solution: Check whether the resource adapter is packaged correctly. Check the correctness of deployment descriptor.
RAR6026

Could not parse the deployment descriptor of the resource adapter. Solution: Check whether the resource adapter is packaged correctly. Check the correctness of deployment descriptor.
RAR6027

Malformed URL to add to path of classloader: {0} Cause: TBD

Solution: TBD RAR6028

Resource Adapter does not contain resource adapter JavaBean. Solution: Make sure that the resource adapter is 1.5 compliant.
RAR6029

Failed to delete admin object from jndi: {0} Cause: TBD

Solution: TBD RAR6030

MCF cleanup in connector runtime failed. Solution: Check whether connection pool has already been deleted.
RAR6031

Failed to unbind connectionPool from jndi: {0} Cause: TBD

Solution: TBD RAR6032
Chapter 25 RAR Error Messages 247

RAR Messages

Connection Pool Name of the Resource configuration is wrong. Solution: Check whether the connection pool is created.
RAR6033

Wrong connector connection pool entry in the domain.xml. No corresponding resource adapter deployed. Resource Adapter Name: Cause: TBD
Solution: TBD RAR6034

Resource Adapter Name of the admin object configuration is wrong. Solution: Check whether the resource adapter is deployed.
RAR6035

Could not start the resource adapter instance. Solution: Check whether domain.xml is accessible. Check your resource adapter documentation for possible causes of failure during ResourceAdapter.start().
RAR6036

Resource Adapter throws exception during ManagedConnectionFactory.setResourceAdapter(). Solution: If you are using third party resource adapter, contact resource adapter vendor. If you are a resource adapter developer, please check the resource adapter code.
RAR6037

Resource Adapter threw an exception during ResourceAdapter.stop() method. Solution: Check your resource adapter documentation about ResourceAdapter.stop() method.
RAR7000

Check for a new version of MQ installation failed: {0} Cause: TBD

Solution: TBD RAR7001

248

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

RAR Messages

Could not unzip the MQ resource adapter archive from upgraded MQ. Solution: Check whether new MQ resource adapter archive in imq_home/lib is accessible.
RAR7002

MQ Resource adapter upgradation started. Cause: TBD

Solution: TBD RAR7003

MQ Resource adapter upgradation completed. Cause: TBD

Solution: TBD RAR7004

Resource Adapter is requesting endpoints to the MDB, before MDB deployment is complete. Solution: There is an internal server error. Please contact Sun Microsystems with the complete log message.
RAR7005

Could not access the class loader specific to the MDB. Solution: There is an internal server error. Please contact Sun Microsystems with the complete log message.
RAR7006

ActivationSpec validation failed. Solution: Check your JMS related configuration in MDB deployment descriptor. Check your activation configuration in the MDB deployment descriptor.
RAR7007

Resource Adapter is trying to invoke an unknown method during message delivery. Solution: Check your resource adapter documentation for possible issues during message delivery.
RAR7008

Chapter 25 RAR Error Messages

249

RAR Messages

Initialized monitoring registry and listeners Cause: TBD

Solution: TBD RAR7009

Cannot set autocommit mode for physical connection Cause: TBD

Solution: TBD RAR7010

Could not find the connection pool specified. Solution: Try the following:

Check whether the connection pool creation was successful. Check whether the pool name used is correct. There is an internal server error. Please contact Sun Microsystems with the complete log message.

RAR7011

Unexpected exception determining whether resource is referenced. Cause: TBD

Solution: TBD RAR7012

J2EE Connector 1.5 specification compliant Resource Adapter stop() status Cause: TBD
Solution: TBD RAR7013

Resource Adapter stop() call successful Cause: TBD

Solution: TBD RAR7014
250 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

RAR Messages

Could not read shutdown-timeout-in-seconds from domain.xml properly. Solution: Make sure that domain.xml is configured correctly.
RAR7092

Wrong transaction-support connection pool attribute setting. Cause: The connection pool specifies a transaction-support attribute value that is greater than the one specified in the pool according to this mathematical inequality: NoTransaction < LocalTransaction < XATransaction.
Solution: Change the transaction-attribute value in the pool to be less than or equal to

the one specified in the resource adapters ra.xml.

RAR7093

Error while cleaning up ManagedConnection Cause: TBD

Solution: TBD RAR7094

{0} shutdown successful. Cause: TBD

Solution: TBD RAR7095

{0} shutdown unsuccessful. Please refer the server and/or resource adapter logs for more information. Cause: TBD
Solution: TBD RAR7096

Error while trying to invoke the setter method for the specified property. Solution: Check if the value and the property name specified are valid.
RAR7097

Error in finding a mutator method for the specified property. Solution: Check if the property has been specified correctly and an appropriate public setter method [method] is available in the class.
Chapter 25 RAR Error Messages 251

RAR Messages

RAR7099

Cannot unregister pool from monitoring registry: {0} Cause: TBD

Solution: TBD RAR7099

The mcf being used to allocate the connection and the MCF in the pool are not equal. Cause: TBD
Solution: TBD RAR7100

Physical destination {0} is autocreated by application server. Cause: TBD

Solution: TBD RAR7102

Default-jms-host of jms-service is not configured properly. Using the first jms-host as the Cause: TBD
Solution: TBD RAR7103

The physical destination {0} is already created. Cause: TBD

Solution: TBD RAR7104

Exception while stopping Derby: Cause: TBD

Solution: TBD RAR7105
252 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

RAR Messages

Derby Embedded Driver not found: Cause: TBD

Solution: TBD RAR7106

Invalid property combination (LazyConnectionEnlistment-false, LazyConnectionAssociation-true) for pool: {0} Cause: TBD
Solution: TBD RAR8000

The method {0} is not present in the class: {1} Cause: TBD
Solution: TBD RAR8001

Error in executing the method: {0} Cause: TBD

Solution: TBD

Chapter 25 RAR Error Messages

253

254

C H A P T E R

SEC Error Messages

26

2 6

This chapter describes messages for errors with a SEC prefix.

SEC Messages
SEC1000

security
Cause: TBD Solution: TBD SEC1050

security
Cause: TBD Solution: TBD SEC1100

security
Cause: TBD Solution: TBD SEC1101

security
Cause: TBD Solution: TBD
255

SEC Messages

SEC1102

security
Cause: TBD Solution: TBD SEC1103

security
Cause: TBD Solution: TBD SEC1104

security
Cause: TBD Solution: TBD SEC1105

security
Cause: TBD Solution: TBD SEC1106

security
Cause: TBD Solution: TBD SEC1109

security
Cause: TBD Solution: TBD SEC1110

256

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

SEC Messages

security
Cause: TBD Solution: TBD SEC1120

security
Cause: TBD Solution: TBD SEC1122

security
Cause: TBD Solution: TBD SEC1123

security
Cause: TBD Solution: TBD SEC1130

security
Cause: TBD Solution: TBD SEC1131

security
Cause: TBD Solution: TBD SEC1132

security
Cause: TBD Solution: TBD
Chapter 26 SEC Error Messages 257

SEC Messages

SEC1133

security
Cause: TBD Solution: TBD SEC1140

security
Cause: TBD Solution: TBD SEC1141

security
Cause: TBD Solution: TBD SEC1142

security
Cause: TBD Solution: TBD SEC1143

security
Cause: TBD Solution: TBD SEC1144

security
Cause: TBD Solution: TBD SEC1145

258

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

SEC Messages

security
Cause: TBD Solution: TBD SEC1146

security
Cause: TBD Solution: TBD SEC1147

security
Cause: TBD Solution: TBD SEC2000

security
Cause: TBD Solution: TBD SEC2001

security
Cause: TBD Solution: TBD SEC2002

security
Cause: TBD Solution: TBD SEC2003

security
Cause: TBD Solution: TBD
Chapter 26 SEC Error Messages 259

SEC Messages

SEC2004

security
Cause: TBD Solution: TBD SEC2005

security
Cause: TBD Solution: TBD SEC2006

security
Cause: TBD Solution: TBD SEC5019

security
Cause: TBD Solution: TBD SEC5022

security
Cause: TBD Solution: TBD SEC5023

security
Cause: TBD Solution: TBD SEC5024

260

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

SEC Messages

security
Cause: TBD Solution: TBD SEC5026

security
Cause: TBD Solution: TBD SEC5028

security
Cause: TBD Solution: TBD SEC5029

security
Cause: TBD Solution: TBD SEC5030

security
Cause: TBD Solution: TBD SEC5031

security
Cause: TBD Solution: TBD SEC5032

security
Cause: TBD Solution: TBD
Chapter 26 SEC Error Messages 261

SEC Messages

SEC5034

security
Cause: TBD Solution: TBD SEC5035

security
Cause: TBD Solution: TBD SEC5036

security
Cause: TBD Solution: TBD SEC5037

security
Cause: TBD Solution: TBD SEC5038

security
Cause: TBD Solution: TBD SEC5039

security
Cause: TBD Solution: TBD SEC5040

262

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

SEC Messages

security
Cause: TBD Solution: TBD SEC5041

security
Cause: TBD Solution: TBD SEC5042

security
Cause: TBD Solution: TBD SEC5043

security
Cause: TBD Solution: TBD SEC5044

security
Cause: TBD Solution: TBD SEC5046

security
Cause: TBD Solution: TBD SEC5047

security
Cause: TBD Solution: TBD
Chapter 26 SEC Error Messages 263

SEC Messages

SEC5048

security
Cause: TBD Solution: TBD SEC5049

security
Cause: TBD Solution: TBD SEC5050

security
Cause: TBD Solution: TBD SEC5051

security
Cause: TBD Solution: TBD SEC5052

security
Cause: TBD Solution: TBD SEC5053

security
Cause: TBD Solution: TBD SEC5100

264

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

SEC Messages

security
Cause: TBD Solution: TBD SEC5101

security
Cause: TBD Solution: TBD SEC8001

security
Cause: TBD Solution: TBD SEC8002

security
Cause: TBD Solution: TBD SEC8003

security
Cause: TBD Solution: TBD SEC1107

security
Cause: TBD Solution: TBD SEC1108

security
Cause: TBD Solution: TBD

Chapter 26 SEC Error Messages

265

266

C H A P T E R

SERVER Error Messages

27

2 7

This chapter describes messages for errors with a SERVER prefix.

SERVER Messages
SERVER5001

IOException : Cause: TBD

Solution: TBD SERVER5002

Exception : Cause: TBD

Solution: TBD SERVER5003

Exception : Cause: TBD

Solution: TBD SERVER5004

j2eerunner.startupError. Cause: TBD

Solution: TBD
267

SERVER Messages

SERVER0001

A server context could not be created Cause: TBD

Solution: TBD SERVER0002

An error occured during initialization Cause: TBD

Solution: TBD SERVER0003

An error occured during startup/reconfig Cause: TBD

Solution: TBD SERVER0004

Application server shutdown in progress Cause: TBD

Solution: TBD SERVER0005

An error occured during shutdown Cause: TBD

Solution: TBD SERVER0007

Your license is invalid. Please obtain a valid license. [{0}] Cause: TBD
Solution: TBD SERVER0008

268

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

SERVER Messages

Using [{0}, Version {1}] from [{2}] Cause: TBD

Solution: TBD SERVER0009

Pluggable features using class {0} could not be initialized. Server will run with default features. Cause: TBD
Solution: TBD SERVER5010

Exception resolving initial reference of ORB: Cause: TBD

Solution: TBD SERVER5011

Exception while creating ORB: [{0}] Cause: TBD

Solution: TBD SERVER5012

Exception running j2ee services: [{0}] Cause: TBD

Solution: TBD SERVER5013

Exception in creating or binding jarinstaller: [{0}] Cause: TBD

Solution: TBD SERVER5013

Chapter 27 SERVER Error Messages

269

SERVER Messages

Exception in creating or binding server object: [{0}] Cause: TBD

Solution: TBD SERVER5014

Exception in listing registered servers Cause: TBD

Solution: TBD SERVER5018

Some remote exception occurred loading jar Cause: TBD

Solution: TBD SERVER5019

Exception in registering server: [{0}] Cause: TBD

Solution: TBD SERVER5044

Error installing servers: [{0}] Cause: TBD

Solution: TBD SERVER5020

Exception installing ORB server [{0}] Cause: TBD

Solution: TBD SERVER5021

Exception initing realmmanager: [{0}] Cause: TBD

Solution: TBD
270 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

SERVER Messages

SERVER5039

Cannot write the seed file for fast startup. The next startup will be slow. Cause: TBD
Solution: TBD SERVER5045

Error executing J2EE server ... Cause: TBD

Solution: TBD SERVER5040

J2EE server reported following error: [{0}] Cause: TBD

Solution: TBD SERVER5041

Error executing J2EE server Cause: TBD

Solution: TBD SERVER5022

Exception looking up server object : [{0}] Cause: TBD

Solution: TBD SERVER5023

Unable to shutdown the J2EE server: [{0}] Cause: TBD

Solution: TBD

Chapter 27 SERVER Error Messages

271

272

C H A P T E R

SGMT Error Messages

28

2 8

This chapter describes messages for errors with a SGMT prefix.

SGMT Messages
SGMT0005

Self Management Service on Shutdown Cause: TBD

Solution: TBD SGMT0006

Self Management Service on Termination Cause: TBD

Solution: TBD SGMT0008

Self Management Service not configured Cause: TBD

Solution: TBD SGMT0013

273

SGMT Messages

Error in registring action : {1} in Rule : {0}. Possbile error with action, try redeploying the application Cause: TBD
Solution: TBD SGMT0017

Error creating and configuring the rule : {0} due to IlegalArguments specified for its event type : {1}. Create the rule with correct arugments for the configured event. Cause: TBD
Solution: TBD SGMT0018

Configured action name={1} for Rule name={0} is disabled. The action would not be executed till it is enabled. Cause: TBD
Solution: TBD SGMT0019

Could not delete rule. No configured rule exists with name={0} Cause: TBD
Solution: TBD SGMT0020

Error encountered while trying to delete rule={0}. Reason - {1} Cause: TBD
Solution: TBD SGMT0021

Successfully deleted rule={0}, with description= {1} Cause: TBD

Solution: TBD SGMT0201
274 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

SGMT Messages

Error in sending the alert for event : {0} as no configured mail recipients Cause: TBD
Solution: TBD SGMT0200

Error in sending the alert me2sage for event : {0} due to : {1} Cause: TBD
Solution: TBD SGMT0203

Error in sending the alert for event : {0} due to configured mail resource {1} not found Cause: TBD
Solution: TBD SGMT0210

{0}- Cannot check for potential non-responsive requests/threads. This is because internal statistics are not available due HttpService monitoring being switched OFF. Set it to non-OFF value for successful checks to occur. Cause: TBD
Solution: TBD SGMT0211

{0}- No http requests received Cause: TBD

Solution: TBD SGMT0212

{0}- Could not send mail alert due to invalid ref, {1} ,configured. Please ensure that the configured mail alert application is available. Cause: TBD
Solution: TBD SGMT0213
Chapter 28 SGMT Error Messages 275

SGMT Messages

{0}- Error encountered while trying to send mail alert. Would proceed to log the detail. Cause: TBD
Solution: TBD SGMT0214

{0}- Potential request/threads found to be non-responsive={1}. Cause: TBD

Solution: TBD SGMT0215

{0}- Error encountered while trying to stop/interrupt the potential unrepsonsive request/thread/ Cause: TBD
Solution: TBD SGMT0216

{0}- Error encountered while trying to retrieve statistics to determine potential non-responsive requests/threads. Cause: TBD
Solution: TBD SGMT0217

{0}- Found non-responsive http request/thread on listener port:{1}, for URI={2} Cause: TBD
Solution: TBD SGMT0218

{0}- Stopped non-repsonsive http request/thread on listener port={1}, for URI={2} Cause: TBD
Solution: TBD SGMT0219
276 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

SGMT Messages

{0}- Cannot send mail alert on the check for non-responsive requests/threads, as applicatoin ref for mail alert is not provided. Cause: TBD
Solution: TBD SGMT0220

{0}- HttpService monitoring switched ON. Statistics for check for non-responsive http request/threads would now be enabled. Cause: TBD
Solution: TBD SGMT0221

{0}- HttpService monitoring switched OFF. It would not be possible to check for non-responsive http requests/threads, due to non-availability of internal statistics. Cause: TBD
Solution: TBD SGMT0222

{0}- Due ThresholdWaitInMillis:{1} being less than load balancer default timeout value of:{2}; resetting it to load balancer default. Cause: TBD
Solution: TBD SGMT0223

{0}- Due ThresholdWaitInMillis:{1} being less than load balancer response timeout:{2}, resetting it to load balancer response timeout. Cause: TBD
Solution: TBD SGMT0224

Chapter 28 SGMT Error Messages

277

SGMT Messages

Instance hang check - Listener: {1} of server :{0} is not responding to the for instance hang check request. The request timeout occured for the timeout value of={2}. Cause: TBD
Solution: TBD SGMT0225

Instance hang check - Listener: {1} of server: {0} has not responded to the ping request for instance hang check. However it still has scope to receive further http requests, as it has not maxd out on threads. No. of busy http threads={2}. Cause: TBD
Solution: TBD SGMT0226

Instance hang check - Listener: {1} of server: {0} has not responded to instance hang check request. The listener has maxd out on threads. No. of busy http threads={2}. Cause: TBD
Solution: TBD SGMT0227

Instance hang check - Listener: {1} of server: {0} is healthy for the instance hang check carried out. Cause: TBD
Solution: TBD SGMT0228

Instance hang check - Server {0} is healthy. Cause: TBD

Solution: TBD SGMT0229

Instance hang check - Server: {0} is not responding; is unhealthy. Cause: TBD
Solution: TBD
278 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

SGMT Messages

SGMT0230

Instance hang check - Invalid name : {0} specified in the check list of the rule. Ignoring this value. Cause: TBD
Solution: TBD SGMT0231

Instance hang check - The threshold timeout= {1} specified for cluster: {0} is less than the load balancer health checker configured for it. Raising this timeout to its load balancer health checker value of {2}. Cause: TBD
Solution: TBD SGMT0232

Instance hang check - The threshold timeout= {1} specified for server: {0} is l Cause: TBD
Solution: TBD SGMT0233

Instance hang check - There are no instances specified in the check list to check for instance hang. Cause: TBD
Solution: TBD SGMT0234

Started instance hang check for server: {0} in cluster: {1} Cause: TBD
Solution: TBD SGMT0235

Started instance hang check for server: {0} Cause: TBD

Solution: TBD
Chapter 28 SGMT Error Messages 279

SGMT Messages

SGMT0236

Instance hang check - Server: {0} in Cluster {1} is healthy. Cause: TBD
Solution: TBD SGMT0237

Instance hang check - Server: {0} in Cluster {1} is unhealthy. Cause: TBD
Solution: TBD SGMT0239

Instance hang check - Trying to restart non-responsive instance: {0} Cause: TBD
Solution: TBD SGMT0240

Instance hang check - Trying to stop non-responsive instance: {0} in cluster: {1} Cause: TBD
Solution: TBD SGMT0241

Instance hang check - Successfully stopped instance: {0} Cause: TBD

Solution: TBD SGMT0242

Instance hang check - Successfully stopped instance: {0} in cluster: {1} Cause: TBD
Solution: TBD SGMT0243

280

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

SGMT Messages

Instance hang check - Error in stopping non-responsive instance: {0}. Cannot restart this instance. Cause: TBD
Solution: TBD SGMT0244

Instance hang check - Error in stopping non-responsive instance: {0} in cluster: {1}. Cannot restart this instance. Cause: TBD
Solution: TBD SGMT0245

Instance hang check - Trying to restart instance: {0} Cause: TBD

Solution: TBD SGMT0246

Instance hang check - Trying to restart instance: {0} in cluster: {1} Cause: TBD
Solution: TBD SGMT0247

Instance hang check - Successfully restarted instance: {0} Cause: TBD

Solution: TBD SGMT0248

Instance hang check - Successfully restarted instance: {0} in cluster: {1} Cause: TBD
Solution: TBD SGMT0249

Chapter 28 SGMT Error Messages

281

SGMT Messages

Instance hang check - Error in trying to restart non-responsive instance: {0} Cause: TBD
Solution: TBD SGMT0259

Instance hang check - Error in trying to restart non-responsive instance: {0} in cluster: {1} Cause: TBD
Solution: TBD SGMT0260

Instance hang check cycle completed. Cause: TBD

Solution: TBD SGMT0261

This action can only be deployed on a DAS instance. Cause: TBD

Solution: TBD SGMT0262

Could not obtain MBeanServerConnection. Cause: TBD

Solution: TBD SGMT0301

Reconfig notification received for creation Cause: TBD

Solution: TBD SGMT0302

282

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

SGMT Messages

Reconfig notification received for updation Cause: TBD

Solution: TBD SGMT0303

Reconfig notification received for deletion Cause: TBD

Solution: TBD SGMT0304

Reconfig notification received for handling rules creation Cause: TBD

Solution: TBD SGMT0305

Reconfig notification received for handling rules updation Cause: TBD

Solution: TBD SGMT0306

Reconfig addition for rule - {0} Cause: TBD

Solution: TBD SGMT0307

Reconfig notification received for handling rules deletion Cause: TBD

Solution: TBD SGMT0308

Reconfig deletion for - {0} Cause: TBD

Solution: TBD
Chapter 28 SGMT Error Messages 283

SGMT Messages

SGMT0309

Reconfig update on - {0} Cause: TBD

Solution: TBD SGMT0310

Reconfig - Disabling self management service. All enabled rules would be implicitly disableld. Cause: TBD
Solution: TBD SGMT0311

Reconfig - Enabling self management service. All enabled rules would be activated. Cause: TBD
Solution: TBD SGMT0313

Reconfig - Error encountered while deleting rule, name= {0}. Reason for error : {1}. Cause: TBD
Solution: TBD SGMT0314

Reconfig - Successfully deleted management rule, Name= {0}, its Description= {1}. Cause: TBD
Solution: TBD SGMT0315

Reconfig - Updating management rule attribute={0}. Old value= {1}, new value= {2} Cause: TBD
Solution: TBD
284 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

SGMT Messages

SGMT0316

Error encountered while disabling rule, name= {0}. Reason is : {1}. Cause: TBD
Solution: TBD SGMT0317

Error encountered while enabling management rules. Reason is :{0}. Cause: TBD
Solution: TBD SGMT0318

Reconfig - Cannot activate rule, name= {0}, Description= {1} as the management rules is disbaled. First enable the management rules to activate this rule. Cause: TBD
Solution: TBD SGMT0319

Reconfig - Cannot disable rule, name= {0}, Description= {1} as it is already not active due to the management rules being disabled. Cause: TBD
Solution: TBD

Chapter 28 SGMT Error Messages

285

286

C H A P T E R

SYNC Error Messages

29

2 9

This chapter describes messages for errors with a SYNC prefix.

SYNC Messages
SYNC002

User name, password, host name or port number may be incorrect. Cause: DAS may be down or unreachable.
Solution: Check if User name, password, host name and port number are correct. Make sure DAS is running and can connect from the current instance(host). SYNC006

Synchronization module subsystems meta-data.xml file is corrupted. Solution: There are several possible solutions:

Check synchronization-meta-data.xml and na-synchronization-meta-data.xml exist in appserv-se.jar and is a valid XML file. Check if synchronization-meta-data.xml is not part of server classpath. synchronization-meta-data.xml is not valid. synchronization-meta-data.xml found in server classpath is not well formed.

SYNC029

This could be either a config Exception or IOException Solution: Check domain.xml and das.properties. If the problem persists, you may backup and remove applications, generated, config, docroot and lib directories in the local repository and restart the server. The local repository will be synchronized again.
287

SYNC Messages

SYNC047

Connection problem during download. File(s) could not be written to synchronization store. Solution: Check if DAS is up. Check for connection errors during download. Check if synchronization repository has enough space and has permission. If the repository is on NFS, may be NFS is down.
SYNC049

File(s) could not be written to synchronization store. Solution: Check if synchronization repository has enough space and has permission. If the repository is on NFS, may be NFS is down.
SYNC052

domain.xml is incorrect. Solution: Make sure domain.xml errors are fixed. It may have been manually edited.
SYNC074

This could be a network communication error. Solution: Please check domain.xml, das.properties and server log.
SYNC075

This could be a network communication error or Domain Administration Server is not running. Solution: Please ensure that Domain Administration Server is running. If DAS is accessible and the problem persists, you may backup and remove applications, generated, config, docroot and lib directories in the local repository and restart the server. The local repository will be synchronized again.

288

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

C H A P T E R

UTIL Error Messages

30

3 0

This chapter describes messages for errors with a UTIL prefix.

UTIL Messages
UTIL5001

Some system exception occurred Cause: TBD

Solution: TBD UTIL5002

Exception occurred getting property Cause: TBD

Solution: TBD UTIL5003

Exception occurred setting property Cause: TBD

Solution: TBD UTIL5004

Exception occurred getting config object Cause: TBD

Solution: TBD
289

UTIL Messages

UTIL5005

Exception occurred setting config object Cause: TBD

Solution: TBD UTIL5006

Exception occurred getting config key Cause: TBD

Solution: TBD UTIL5007

Exception occurred getting or setting config key Cause: TBD

Solution: TBD UTIL5008

Exception occurred removing property Cause: TBD

Solution: TBD UTIL5009

Exception occurred removing object Cause: TBD

Solution: TBD UTIL5014

Exception in listing registered servers Cause: TBD

Solution: TBD UTIL5015

290

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

UTIL Messages

Could not load class: [{0}] Cause: TBD

Solution: TBD UTIL5016

Configuration exception Cause: TBD

Solution: TBD UTIL5017

Some exception occurred loading deployed applications Cause: TBD

Solution: TBD UTIL5024

IOException occurred in get server repository Cause: TBD

Solution: TBD UTIL5025

Exception occurred in file handling Cause: TBD

Solution: TBD UTIL5026

Privileged Action Exception : [{0}] Cause: TBD

Solution: TBD UTIL5027

Managed connection factory exception : [{0}] Cause: TBD

Solution: TBD
Chapter 30 UTIL Error Messages 291

UTIL Messages

UTIL5028

Resource Exception: [{0}] Cause: TBD

Solution: TBD UTIL5029

Exception in resource to raw info Cause: TBD

Solution: TBD UTIL5030

Raw info to resource exception Cause: TBD

Solution: TBD UTIL5031

Empty resource Cause: TBD

Solution: TBD UTIL5032

Exception finding value from repository Cause: TBD

Solution: TBD UTIL5033

Exception adding value in repository Cause: TBD

Solution: TBD UTIL5034

292

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

UTIL Messages

Exception removing value from repository Cause: TBD

Solution: TBD UTIL5035

Naming exception occurred Cause: TBD

Solution: TBD UTIL5036

Exception storing resource mappings Cause: TBD

Solution: TBD UTIL5036

Exception loading resource mappings Cause: TBD

Solution: TBD UTIL5037

Could not connect to the naming .. lets use a local copy Cause: TBD
Solution: TBD UTIL5038

Some exception occurred creating ConfigurationImpl Cause: TBD

Solution: TBD UTIL5042

Error initing repository: [{0}] Cause: TBD

Solution: TBD
Chapter 30 UTIL Error Messages 293

UTIL Messages

UTIL5043

Enterprise repository property error : [{0}] Cause: TBD

Solution: TBD UTIL5046

Exception creating data source Cause: TBD

Solution: TBD UTIL5047

Connection Pool does not exist: [{0}] Cause: TBD

Solution: TBD UTIL5048

Error Loading Jdbc Resource: [{0}] Cause: TBD

Solution: TBD UTIL5049

Resource named {0} [Type: {1}] is disabled. It was not loaded. Cause: TBD
Solution: TBD UTIL6001

isJmsDestinationReference has been deprecated; Please use isResourceEnvReference instead. Cause: TBD
Solution: TBD UTIL6002
294 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

UTIL Messages

Exception in main(). Cause: TBD

Solution: TBD UTIL6003

MalformedURLException in addResourceAdapter(). Cause: TBD

Solution: TBD UTIL6004

IOException in load(). Cause: TBD

Solution: TBD UTIL6005

IOException in copyFile. Cause: TBD

Solution: TBD UTIL6006

Exception in JarAccess create(). Cause: TBD

Solution: TBD UTIL6007

Exception in LegacyConfigConverter convert(). Cause: TBD

Solution: TBD UTIL6008

ConfigException in ORBManager. Cause: TBD

Solution: TBD
Chapter 30 UTIL Error Messages 295

UTIL Messages

UTIL6009

Unexcpected Exception in createORB. Cause: TBD

Solution: TBD UTIL6010

Error Cannot load library. [{0}] Cause: TBD

Solution: TBD UTIL6011

jms-client-id is an obsolete property. Set client id on a JMS Connection Factory and use the mdb-connection-factory property instead. Cause: TBD
Solution: TBD UTIL6012

message-driven beans with container-managed transactions cant have a jms acknowledge mode. Cause: TBD
Solution: TBD UTIL6013

You have chosen to make this bean manage its own transactions. This is illegal for entity beans, and the (session) bean cannot specifiy any method level container transactions. Cause: TBD
Solution: TBD UTIL6014

error converting properties file. Cause: TBD

Solution: TBD
296 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

UTIL Messages

UTIL6015

Unexpected Exception in ResourceCache getResource(). Cause: TBD

Solution: TBD UTIL6016

Exception in ServerViewer refresh(). Cause: TBD

Solution: TBD UTIL6017

Excpetion in SimpleUniqueValueGenerator getGeneratorBackendId(). Cause: TBD

Solution: TBD UTIL6018

Excpetion in SimpleUniqueValueGenerator nextNumberInternal(). Cause: TBD

Solution: TBD UTIL6019

WARNING : runAsRole and runAsPrincipal cannot exist independent of each other. Ignore... Cause: TBD
Solution: TBD UTIL6020

Error in removing resource adapters Cause: TBD

Solution: TBD UTIL6021
Chapter 30 UTIL Error Messages 297

UTIL Messages

Error [{0}] occurred Cause: TBD

Solution: TBD UTIL6022

Error connecting server viewer: [{0}] Cause: TBD

Solution: TBD UTIL6023

Exception in DebugController setInfo. Cause: TBD

Solution: TBD UTIL6024

Exception in FileUtil CountWords(). Cause: TBD

Solution: TBD UTIL6025

The main method is either not public or not static. Cause: TBD
Solution: TBD UTIL6026

The main methods return type is not void. Cause: TBD

Solution: TBD UTIL6027

Exception in invokeApplicationMain [{0}]. Cause: TBD

Solution: TBD
298 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

UTIL Messages

UTIL6028

Exception in FileUtil Cause: TBD

Solution: TBD UTIL6029

Exception in checkORBInitialHost Cause: TBD

Solution: TBD UTIL6030

Exception in checkORBInitialPort Cause: TBD

Solution: TBD UTIL6031

Number Format Exception, Using default value(s). Cause: TBD

Solution: TBD UTIL6032

Could not initialize connection monitoring Cause: TBD

Solution: TBD UTIL6033

Could not initialize Thread Pool monitoring Cause: TBD

Solution: TBD UTIL6034

Chapter 30 UTIL Error Messages

299

UTIL Messages

Could not initialize ORB monitoring Cause: TBD

Solution: TBD UTIL6035

Exception converting to integer Cause: TBD

Solution: TBD UTIL6036

System property reference missing trailing "}" at {0} in domain.xml. Cause: TBD
Solution: TBD UTIL6037

System property reference missing starting "${" at {0} in domain.xml. Cause: TBD
Solution: TBD UTIL6038

Unknown property {0} found unresolving {1}. Cause: TBD

Solution: TBD UTIL6039

Exception {0} resolving password alias {1} in property {2}. Cause: TBD
Solution: TBD UTIL6040

Error attempting to delete {0} Cause: TBD

Solution: TBD
300 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

UTIL Messages

UTIL6041

Performing gc to try to force file closures Cause: TBD

Solution: TBD UTIL6042

Attempt to delete {0} succeeded after {1} retries Cause: TBD

Solution: TBD UTIL6043

Attempt to delete {0} failed after {1} retries Cause: TBD

Solution: TBD UTIL6044

Error attempting to rename {0} Cause: TBD

Solution: TBD UTIL6045

Attempt to rename {0} to {1} succeeded after {2} retries Cause: TBD
Solution: TBD UTIL6046

Attempt to rename {0} to {1} failed after {2} retries Cause: TBD
Solution: TBD UTIL6047

Chapter 30 UTIL Error Messages

301

UTIL Messages

Attempt to rename {0} to {1} succeeded without any retries Cause: TBD
Solution: TBD UTIL6048

Attempt to delete {0} failed; now marked for delete-on-exit Cause: TBD
Solution: TBD UTIL6100

Windows file path {0} is too long; consider shortening the module name or the installation directory path Cause: TBD
Solution: TBD UTIL6101

Error preparing class loader Cause: TBD

Solution: TBD UTIL6537

PropertyWrapper::PropertyWrapper() does not have security access to [{0}] > [{1}] Cause: TBD
Solution: TBD UTIL6538

Error creating filecachestore Cause: TBD

Solution: TBD UTIL6539

302

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

UTIL Messages

Error doing lookup Cause: TBD

Solution: TBD UTIL6540

Storing error Cause: TBD

Solution: TBD UTIL6541

[{0}] : lookup failed for: [{1}] Cause: TBD

Solution: TBD UTIL6542

Lookup failed for Key: [{0}] Cause: TBD

Solution: TBD UTIL6543

Exception converting to array Cause: TBD

Solution: TBD UTIL6544

CallerInfo Exception Cause: TBD

Solution: TBD UTIL6045

Internal Error in Reporter -- couldnt find/make default reporter! Cause: TBD

Solution: TBD
Chapter 30 UTIL Error Messages 303

UTIL Messages

UTIL6546

Bad Location Exception Cause: TBD

Solution: TBD UTIL6547

Got exception in ReporterImpl.pr(): Cause: TBD

Solution: TBD UTIL6548

Got some exception Cause: TBD

Solution: TBD UTIL6549

Some IOException occurred Cause: TBD

Solution: TBD UTIL6550

Error in local string manager - resource bundle is probably missing. Cause: TBD
Solution: TBD UTIL6551

Error while caching the local string manager - package name may be null. Cause: TBD
Solution: TBD UTIL6552

304

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

UTIL Messages

Error while constructing the local string manager object. Cause: TBD
Solution: TBD UTIL6553

Error while formating the local string. Cause: TBD

Solution: TBD

Chapter 30 UTIL Error Messages

305

306

C H A P T E R

VRFY Error Messages

31

3 1

This chapter describes messages for errors with a VRFY prefix.

VRFY Messages
VRFY5001

Could not instantiate class [{0}]. Cause: TBD

Solution: TBD VRFY5002

Class [{0}] not found. Cause: TBD

Solution: TBD VRFY5003

Could not access class [{0}]. Cause: TBD

Solution: TBD VRFY5004

Verifier class [{0}] not found. Cause: TBD

Solution: TBD
307

VRFY Messages

VRFY5005

Verifier method not found. Cause: TBD

Solution: TBD VRFY5006

Problem in initializing verifier. Cause: TBD

Solution: TBD VRFY5100

About to get all test names from props file. Cause: TBD
Solution: TBD VRFY5101

loadTestsFromPropsFile...IOException Cause: TBD

Solution: TBD VRFY5102

loadTestsFromPropsFile...ParserConfigException Cause: TBD

Solution: TBD VRFY5103

loadTestsFromPropsFile...SAXException Cause: TBD

Solution: TBD VRFY5104

308

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

VRFY Messages

error while executing test Cause: TBD

Solution: TBD VRFY5105

Server XML Verified Test Results are written in [{0}] Cause: TBD
Solution: TBD VRFY5106

Error Writing File Cause: TBD

Solution: TBD VRFY5107

Error getting LocalStringsManager Cause: TBD

Solution: TBD VRFY5108

ERROR : Could not create a Server Object Cause: TBD

Solution: TBD VRFY5109

Looking at file [{0}] Cause: TBD

Solution: TBD VRFY5110

Could not find class Cause: TBD

Solution: TBD
Chapter 31 VRFY Error Messages 309

VRFY Messages

VRFY5111

Exception Cause: TBD

Solution: TBD VRFY5112

Error in instantiation : [{0}] Cause: TBD

Solution: TBD

310

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

C H A P T E R

WEB Error Messages

32

3 2

This chapter describes messages for errors with a WEB prefix.

WEB Messages
WEB0100

Loading web module [{0}] in virtual server [{1}] at [{2}] Cause: TBD
Solution: TBD WEB0101

Error loading web module [{0}] in virtual server [{1}]: {2} Cause: TBD
Solution: TBD WEB0102

This web container has already been started Cause: TBD

Solution: TBD WEB0103

This web container has not yet been started Cause: TBD
Solution: TBD
311

WEB Messages

WEB0104

A web container has not been created for the server configuration Cause: TBD
Solution: TBD WEB0105

An error occurred while starting the web container Cause: TBD

Solution: TBD WEB0106

An error occurred while stopping the web container Cause: TBD

Solution: TBD WEB0107

An error occurred while parsing the server configuration Cause: TBD

Solution: TBD WEB0108

extra-class-path component [{0}] is not a valid pathname Cause: TBD

Solution: TBD WEB0109

Property [{0}] is not yet supported Cause: TBD

Solution: TBD WEB0110

312

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WEB Messages

Ignoring invalid property [{0}] = [{1}] Cause: TBD

Solution: TBD WEB0111

Enabling file-based persistence for web module [{0}]s sessions Cause: TBD
Solution: TBD WEB0112

This web container was unable to load application [{0}] Cause: TBD
Solution: TBD WEB0113

Virtual server [{0}] already has a web module loaded at [{1}]; therefore web module [{2}] cannot be loaded at this context path on this virtual server. Cause: TBD
Solution: TBD WEB0114

SSO is disabled in virtual server [{0}] Cause: TBD

Solution: TBD WEB0115

Error in SSO configuration: {0} Cause: TBD

Solution: TBD WEB0116

Chapter 32 WEB Error Messages

313

WEB Messages

Using alternate deployment descriptor [{0}] for web module [{1}] Cause: TBD
Solution: TBD WEB0117

Error loading web module [{0}] in virtual server [{1}]: {2} Cause: TBD
Solution: TBD WEB0118

Error in Applications configuration. Cause: TBD

Solution: TBD WEB0119

Error in HttpService configuration. Cause: TBD

Solution: TBD WEB0120

Cannot load policy file. Cause: TBD

Solution: TBD WEB0121

Enabled session ID reuse for web module [{0}] in virtual server [{1}] Cause: TBD
Solution: TBD WEB0122

Cannot map admin application to virtual-server. Cause: TBD

Solution: TBD
314 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WEB Messages

WEB0123

WebModule [{0}] failed to deploy and has been disabled: [{1}]. Cause: TBD
Solution: TBD WEB0124

Property element in sun-web.xml has null name or value Cause: TBD

Solution: TBD WEB0125

class-loader attribute dynamic-reload-interval in sun-web.xml not supported Cause: TBD

Solution: TBD WEB0126

Failed to parse sun-web.xml singleThreadedServletPoolSize property value ({0}) of web module deployed at {1}, using default ({2}) Cause: TBD
Solution: TBD WEB0127

Web module [{0}] is not loaded in virtual server [{1}] Cause: TBD
Solution: TBD WEB0128

Invalid Session Management Configuration for app [{0}] - defaulting to memory: persistence-type = [{1}] / persistenceFrequency = [{2}] / persistenceScope = [{3}] Cause: TBD
Solution: TBD WEB0129
Chapter 32 WEB Error Messages 315

WEB Messages

Invalid Session Management Configuration for non-distributable app [{0}] defaulting to memory: persistence-type = [{1}] / persistenceFrequency = [{2}] / persistenceScope = [{3}] Cause: TBD
Solution: TBD WEB0130

Enabling ha-based persistence for web module [{0}]s sessions: persistence-type = [{1}] / persistenceFrequency = [{2}] / persistenceScope = [{3}] Cause: TBD
Solution: TBD WEB0131

Enabling no persistence for web module [{0}]s sessions: persistence-type = [{1}] Cause: TBD
Solution: TBD WEB0132

Error creating javax.management.ObjectName from {0} Cause: TBD

Solution: TBD WEB0133

Failed to read attribute {0} from MBean {1} Cause: TBD

Solution: TBD WEB0134

Host names specified in allowRemoteHost property of virtual server [{0}] will not be matched because DNS lookups have been disabled Cause: TBD
Solution: TBD WEB0135
316 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WEB Messages

Host names specified in denyRemoteHost property of virtual server [{0}] will not be matched because DNS lookups have been disabled Cause: TBD
Solution: TBD WEB0136

Virtual server [{0}] has a property with missing name or value Cause: TBD
Solution: TBD WEB0137

Invalid redirect property value [{0}]: Contains more than one [{1}] element Cause: TBD
Solution: TBD WEB0138

Invalid redirect property value [{0}]: Missing from element Cause: TBD
Solution: TBD WEB0139

Invalid redirect property value [{0}]: Either url or url-prefix must be specified Cause: TBD
Solution: TBD WEB0140

Invalid redirect property value [{0}]: Contains both url and url-prefix elements Cause: TBD
Solution: TBD WEB0141

Chapter 32 WEB Error Messages

317

WEB Messages

Invalid redirect property value [{0}]: escape must be equal to yes or no Cause: TBD
Solution: TBD WEB0142

Invalid send-error property value [{0}]: Contains more than one [{1}] element Cause: TBD
Solution: TBD WEB0143

Invalid send-error property value [{0}]: Missing path element Cause: TBD
Solution: TBD WEB0144

Invalid redirect URL [{0}]: Impossible to URL encode Cause: TBD

Solution: TBD WEB0137

Schema updater error Cause: TBD

Solution: TBD WEB0200

Configuration error in web module [{0}] (while initializing virtual server [{1}]) Cause: TBD
Solution: TBD WEB0201

318

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WEB Messages

The web module [{0}] has been designated as the default web module for virtual server [{1}] Cause: TBD
Solution: TBD WEB0202

Error looking up the configuration information of virtual server [{0}] Cause: TBD
Solution: TBD WEB0203

Error looking up the configuration information of the default web module [{0}] of virtual server [{1}] Cause: TBD
Solution: TBD WEB0204

The default web module [{0}] is either disabled or does not specify virtual server [{1}] Cause: TBD
Solution: TBD WEB0205

Configuration error in applications module (while initializing virtual server [{1}]) Cause: TBD
Solution: TBD WEB0300

Creating VS {0} @docroot {1} Cause: TBD

Solution: TBD WEB0301
Chapter 32 WEB Error Messages 319

WEB Messages

Creating Listener @port {0} {1} Cause: TBD

Solution: TBD WEB0302

Starting Sun-Java-System/Application-Server. Cause: TBD

Solution: TBD WEB0303

Stopping Sun-Java-System/Application-Server. Cause: TBD

Solution: TBD WEB0304

Unsupported http-service property ({0}) is being ignored Cause: TBD

Solution: TBD WEB0305

HTTP listeners proxy port is not a numeric string Solution: Check to see if the value of the HTTP listener's server-name attribute contains a colon, and if so, make sure the name component following the colon is a numeric string.
WEB0306

Unable to parse redirect-port ({0}) attribute of http-listener {1}, using default: {2} Cause: TBD
Solution: TBD WEB0307

320

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WEB Messages

All SSL protocol variants disabled for http-listener {0}, using SSL implementation specific defaults Cause: TBD
Solution: TBD WEB0308

All SSL cipher suites disabled for http-listener {0}, using SSL implementation specific defaults Cause: TBD
Solution: TBD WEB0309

Unrecognized cipher: {0} Cause: TBD

Solution: TBD WEB0310

Unable to parse acceptor-threads attribute ({0}) of http-listener {1}, using default: {2} Cause: TBD
Solution: TBD WEB0311

default-virtual-server ({0}) referenced by HTTP listener {1} does not match virtual server ({2}) in whose http-listeners attribute the HTTP listener is listed Cause: TBD
Solution: TBD WEB0312

virtual server {0} does not have any docroot Cause: TBD
Solution: TBD WEB0313
Chapter 32 WEB Error Messages 321

WEB Messages

Unable to parse port number {0} of http-listener {1} Cause: TBD

Solution: TBD WEB0314

virtual server {0} has an invalid docroot {1} Cause: TBD

Solution: TBD WEB0315

Two or more virtual servers associated with the same HTTP listener share the same host name. Solution: Make sure that the sets of host names of all virtual servers associated with the same HTTP listener are disjunct.
WEB0316

Unable to convert timeout-in-seconds attribute value ({0}) of keep-alive element to int, using default: {1} Cause: TBD
Solution: TBD WEB0317

Unable to convert max-connections attribute value ({0}) of keep-alive element to int, using default: {1} Cause: TBD
Solution: TBD WEB0318

Unable to convert thread-count attribute value ({0}) of keep-alive element to int, using default: {1} Cause: TBD
Solution: TBD WEB0318
322 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WEB Messages

Invalid max-pending-count attribute value: ({0}). Using default {1}. Cause: TBD
Solution: TBD WEB0319

Invalid receive-buffer-size-in-bytes attribute value: ({0}). Using default {1}. Cause: TBD
Solution: TBD WEB0320

Invalid send-buffer-size-in-bytes attribute value: ({0}). Using default {1}. Cause: TBD
Solution: TBD WEB0321

http-file-cache element not supported Cause: TBD

Solution: TBD WEB0322

Unable to load ProxyHandler implementation class {0} Cause: TBD

Solution: TBD WEB0323

{0} not an instance of com.sun.appserv.ProxyHandler Cause: TBD

Solution: TBD WEB0324

Missing end delimiter in access log pattern: {0} Cause: TBD

Solution: TBD
Chapter 32 WEB Error Messages 323

WEB Messages

WEB0325

Invalid component: {0} in access log pattern: {1} Cause: TBD

Solution: TBD WEB0326

Access log buffer size ({0}) too small to hold single access log entry, doubling buffer capacity Cause: TBD
Solution: TBD WEB0327

Unsupported http-listener property ({0}) is being ignored Cause: TBD

Solution: TBD WEB0328

Invalid request-processing thread-count ({0}) is being ignored Cause: TBD

Solution: TBD WEB0329

Invalid request-processing initial-thread-count ({0}) is being ignored Cause: TBD

Solution: TBD WEB0330

Invalid request-processing request-timeout-in-seconds ({0}) is being ignored Cause: TBD

Solution: TBD WEB0331
324 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WEB Messages

Invalid request-processing thread-increment ({0}) is being ignored Cause: TBD

Solution: TBD WEB0332

Invalid request-processing header-buffer-length-in-bytes ({0}) is being ignored Cause: TBD

Solution: TBD WEB0333

Unable to rename access log file {0} to {1} Cause: TBD

Solution: TBD WEB0334

Invalid queue-size-in-bytes attribute value: ({0}). Using default {1}. Cause: TBD
Solution: TBD WEB0334

http-file-cache attribute hash-init-size not supported Cause: TBD

Solution: TBD WEB0335

http-listener attribute family not supported Cause: TBD

Solution: TBD WEB0336

http-listener attribute blocking-enabled not supported Cause: TBD

Solution: TBD
Chapter 32 WEB Error Messages 325

WEB Messages

WEB0337

http-listener attribute external-port not supported Cause: TBD

Solution: TBD WEB0338

http-protocol attribute ssl-enabled not supported Cause: TBD

Solution: TBD WEB0339

http-protocol attribute version not supported Cause: TBD

Solution: TBD WEB0400

Unable to set request encoding Cause: TBD

Solution: TBD WEB0401

Illegal session cookie name ({0}), using the standard {1} instead Cause: TBD
Solution: TBD WEB0402

POST data too large Cause: TBD

Solution: TBD WEB0500

326

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WEB Messages

default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead Cause: TBD
Solution: TBD WEB0501

Error processing request received on ad-hoc path {0} Cause: TBD

Solution: TBD WEB0502

No ad-hoc servlet configured to process ad-hoc path {0} Cause: TBD

Solution: TBD WEB0600

WebModule [{0}] failed to deploy and has been disabled: [{1}]. Cause: TBD
Solution: TBD WEB0601

Missing default web.xml, using application web.xml only Cause: TBD

Solution: TBD WEB0602

Missing default-web.xml, using application web.xml only Cause: TBD

Solution: TBD WEB0603

Chapter 32 WEB Error Messages

327

WEB Messages

Parse error in default-web.xml Cause: TBD

Solution: TBD WEB0604

Error closing default-web.xml Cause: TBD

Solution: TBD WEB0605

No Realm has been configured to authenticate against Cause: TBD

Solution: TBD WEB0606

Cannot load authenticators mapping list Cause: TBD

Solution: TBD WEB0607

Cannot configure an authenticator for method {0} Cause: TBD

Solution: TBD WEB0608

Cannot instantiate an authenticator of class {0} Cause: TBD

Solution: TBD WEB0609

Configured an authenticator for method {0} Cause: TBD

Solution: TBD
328 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WEB Messages

WEB0700

Error initializing socket factory Cause: TBD

Solution: TBD WEB0701

Error initializing endpoint Cause: TBD

Solution: TBD WEB0702

Error starting endpoint Cause: TBD

Solution: TBD WEB0703

Initializing Sun-Java-System/Application-Server HTTP/1.1 on {0} Cause: TBD

Solution: TBD WEB0704

Error reading request, ignored Cause: TBD

Solution: TBD WEB0705

IOException reading request Cause: TBD

Solution: TBD WEB0706

Chapter 32 WEB Error Messages

329

WEB Messages

IOException reading request, ignored Cause: TBD

Solution: TBD WEB0707

SocketException reading request Cause: TBD

Solution: TBD WEB0708

SocketException reading request, ignored Cause: TBD

Solution: TBD WEB0709

Attribute [{0}] Cause: TBD

Solution: TBD WEB0710

Attribute [{0}]: [{1}] Cause: TBD

Solution: TBD WEB07011

Error initializing socket factory Cause: TBD

Solution: TBD WEB0712

Starting Sun-Java-System/Application-Server HTTP/1.1 on {0} Cause: TBD

Solution: TBD
330 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WEB Messages

WEB0713

Stopping Sun-Java-System/Application-Server HTTP/1.1 on {0} Cause: TBD

Solution: TBD WEB0714

Pausing Sun-Java-System/Application-Server HTTP/1.1 on {0} Cause: TBD

Solution: TBD WEB0715

Error pausing endpoint Cause: TBD

Solution: TBD WEB0716

Resuming Sun-Java-System/Application-Server HTTP/1.1 on {0} Cause: TBD

Solution: TBD WEB0717

Error resuming endpoint Cause: TBD

Solution: TBD WEB0750

Invalid selectorTimeout value Cause: TBD

Solution: TBD WEB0751

Chapter 32 WEB Error Messages

331

WEB Messages

Invalid maxAcceptWorkerThread value Cause: TBD

Solution: TBD WEB0752

Invalid minWorkerThreads value Cause: TBD

Solution: TBD WEB0753

Invalid maxConnections value Cause: TBD

Solution: TBD WEB0754

Invalid maxReadWorkerThread value Cause: TBD

Solution: TBD WEB0755

Invalid pools.size number Cause: TBD

Solution: TBD WEB0756

Caught exception during HTTP processing. Cause: TBD

Solution: TBD WEB0757

Exception during enableChannelRegistration Cause: TBD

Solution: TBD
332 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WEB Messages

WEB0758

SSL Handshake exception Cause: TBD

Solution: TBD WEB0759

Http listener [{0}]: Maximum HTTP Connection reached. Increase maxConnections: [{1}] Cause: TBD
Solution: TBD WEB0760

Unable to close key Cause: TBD

Solution: TBD WEB0761

Caught exception trying to close socket. Cause: TBD

Solution: TBD WEB0762

Caught exception trying to unlock accept on Cause: TBD

Solution: TBD WEB0763

Null socket returned by accept Cause: TBD

Solution: TBD WEB0764
Chapter 32 WEB Error Messages 333

WEB Messages

Wrong socket permissions [{0}] [{1}] Cause: TBD

Solution: TBD WEB0765

http-listener {0} shutdown due to exception: {1} Cause: TBD

Solution: TBD WEB0766

Reinitializing ServerSocket Cause: TBD

Solution: TBD WEB0767

Restarting http-listener Cause: TBD

Solution: TBD WEB0768

http-listener {0} ignored exception: {1} Cause: TBD

Solution: TBD WEB0769

Exception when registering http-listener [{0}] mbeans Cause: TBD

Solution: TBD WEB0770

Exception when deregistering http-listener [{0}] mbeans Cause: TBD

Solution: TBD
334 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WEB Messages

WEB0771

Exception when initializing monitoring for http-listener [{0}] Cause: TBD

Solution: TBD WEB0772

Exception when handling HTTP connection Cause: TBD

Solution: TBD WEB0773

Invalid acceptor-thread value [{0}]. The acceptor-thread value must be greater than 1. Using the default value [{1}] Cause: TBD
Solution: TBD WEB0774

Error stopping http-listener [{0}] Cause: TBD

Solution: TBD WEB0775

Error processing HTTP request Cause: TBD

Solution: TBD WEB0776

Caught exception during NIO deregistration Cause: TBD

Solution: TBD WEB0777
Chapter 32 WEB Error Messages 335

WEB Messages

Unblocking keep-alive exception Cause: TBD

Solution: TBD WEB0778

Error creating internal request Cause: TBD

Solution: TBD WEB0779

Request keep-alibe timeout Cause: TBD

Solution: TBD WEB0780

HTTP Processing error Cause: TBD

Solution: TBD WEB0781

Error finishing request Cause: TBD

Solution: TBD WEB0782

Error finishing response Cause: TBD

Solution: TBD WEB0783

Error commiting response Cause: TBD

Solution: TBD
336 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WEB Messages

WEB0784

Exception getting SSL attributes Cause: TBD

Solution: TBD WEB0785

Exception getting SSL Cert Cause: TBD

Solution: TBD WEB0786

Unknown filter Cause: TBD

Solution: TBD WEB0787

Error intializing filter [{0}] Cause: TBD

Solution: TBD WEB0788

Error registering request Cause: TBD

Solution: TBD WEB0789

Error unregistering request Cause: TBD

Solution: TBD WEB0799

Chapter 32 WEB Error Messages

337

WEB Messages

HTTP processing exception Cause: TBD

Solution: TBD WEB1001

An illegal encoding was used to parse parameters Cause: TBD

Solution: TBD WEB1002

An IOException occurred while trying to read POST data Cause: TBD

Solution: TBD WEB2001

Web application service failed Cause: TBD

Solution: TBD WEB3004

The Application server could not initialize the native HTTP service. This could be cause by a misconfiguration, or a internal failure. Cause: It is also possible that the native library has been found missing.
Solution: Check that the HttpService configuration is valid. Examine the message reported by the native HTTP service for clues. Verify that the following needed libraries are present in the Application Servers's lib directory. If the problem persists, contact Sun with the complete error log message. WEB3005

The Application server could not start the native HTTP service. This could be cause by a misconfiguration, or a internal failure. Cause: It is also possible that the native library has been found missing.
Solution: Check that the HttpService configuration is valid. Examine the message reported by the native HTTP service for clues. Verify that the following needed libraries are present in the Application Servers's lib directory. If the problem persists, contact Sun with the complete error log message.
338 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WEB Messages

WEB3006

The file is missing. Solution: Check that the file is present in the Application Server's lib directory, or if enabled in the Library Path. Please contact Sun with the complete error log message.
WEB3007

This is an Unexpected Internal Error. Please contact Sun with the complete error log message. Solution: Please correct the format.
WEB5001

Exception in Authenticate() of RealmAdapter. Cause: TBD

Solution: TBD WEB5002

Exception in handleBeforeEvent. Cause: TBD

Solution: TBD WEB5003

Exception in handleAfterEvent. Cause: TBD

Solution: TBD WEB5004

Exception in preInvoke of WebContainerListener. Cause: TBD

Solution: TBD WEB5005

Exception in postInvoke of WebContainerListener. Cause: TBD

Solution: TBD
Chapter 32 WEB Error Messages 339

WEB Messages

WEB5006

Exception in SSLSocketFactory constructor [{0}] Cause: TBD

Solution: TBD WEB5007

Exception during handling of {0} event Cause: TBD

Solution: TBD WEB8074

Exception. Cause: TBD

Solution: TBD WEB8080

Unable to register {0} with monitoring registry Cause: TBD

Solution: TBD WEB3001

The Application Server was unable to instantiate the Acess Log Rotator Cause: TBD
Solution: TBD WEB3002

Received unexpected exception while adding certificates valve Cause: TBD

Solution: TBD WEB3003

340

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WEB Messages

Received unexpected exception while retrieving server config objects Cause: TBD
Solution: TBD WEB3008

Initializing httpservice monitoring Cause: TBD

Solution: TBD WEB3009

Initializing httpservice monitoring ... done Cause: TBD

Solution: TBD WEB3010

Restarting httpservice monitoring Cause: TBD

Solution: TBD WEB3011

Restarting httpservice monitoring ... done Cause: TBD

Solution: TBD WEB3012

HttpService monitoring could initialize stats unmarshaller Cause: TBD

Solution: TBD WEB3013

HttpService monitoring not initialized Cause: TBD

Solution: TBD
Chapter 32 WEB Error Messages 341

WEB Messages

WEB3014

Received exception while initializing httpservice monitoring Cause: TBD

Solution: TBD WEB3015

Received exception while updating httpservice statistics cache Cause: TBD

Solution: TBD WEB3016

Received exception while updating httpservice monitoring beans Cause: TBD

Solution: TBD WEB3017

Received exception while reconfiguring httpservice monitoring beans Cause: TBD

Solution: TBD WEB3018

Httpservice statistic unmarshaller found incosistent number of virtual servers Cause: TBD
Solution: TBD WEB3019

Httpservice statistics unmarshaller found inconsitencies on virtual server profiles Cause: TBD
Solution: TBD WEB3020
342 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WEB Messages

HttpSerice could not start access log rotation Cause: TBD

Solution: TBD WEB3021

HttpSerice could not stop access log rotation Cause: TBD

Solution: TBD WEB3022

HttpService Processor received exception Cause: TBD

Solution: TBD WEB3023

HttpService got bad cookie name [{0}] value [{1}] Cause: TBD
Solution: TBD WEB3024

HttpServiceWebContainer constructed Cause: TBD

Solution: TBD WEB3025

HttpService monitoring: parameter cache enable is invalid [{0}] Cause: TBD

Solution: TBD WEB3026

HttpService monitoring: setting cache enabled to true Cause: TBD

Solution: TBD
Chapter 32 WEB Error Messages 343

WEB Messages

WEB3027

HttpService monitoring: invalid cache refresh [{0}] Cause: TBD

Solution: TBD WEB3028

HttpService monitoring: disabling cache monitoring Cause: TBD

Solution: TBD WEB3029

HttpService config: current Virtual Server is [{0}] Cause: TBD

Solution: TBD WEB3030

HttpService config: adding new Virtual Server [{0}] Cause: TBD

Solution: TBD WEB3031

HttpService config: Invalid docroot [{1}] for virtual server [{0}] Cause: TBD
Solution: TBD WEB3032

HttpService config: Created virtual server [{0}] Cause: TBD

Solution: TBD WEB3033

344

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WEB Messages

Removing hosts from tomcat Cause: TBD

Solution: TBD WEB3034

Deleting Virtual Server [{0}] Cause: TBD

Solution: TBD WEB3035

HttpService received exception in destroy context [{0}] Cause: TBD

Solution: TBD WEB3036

HttpService: Context [{0}] undeployed from VS [{1}] Cause: TBD

Solution: TBD WEB3037

HttpService: Create new instance of HttpServiceWebContainer Cause: TBD

Solution: TBD WEB3038

HttpService: Starting HttpService instance Cause: TBD

Solution: TBD WEB3039

HttpService: Stopping HttpService instance Cause: TBD

Solution: TBD
Chapter 32 WEB Error Messages 345

WEB Messages

WEB3040

Initializing HttpService Cause: TBD

Solution: TBD WEB3041

Initializing HttpService ... done Cause: TBD

Solution: TBD WEB3042

Starting HttpService Cause: TBD

Solution: TBD WEB3043

Starting HttpService ... done Cause: TBD

Solution: TBD WEB3044

Reconfiguring HttpService Cause: TBD

Solution: TBD WEB3045

Reconfiguring HttpService ... done Cause: TBD

Solution: TBD WEB3046

346

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WEB Messages

Stopping HttpService Cause: TBD

Solution: TBD WEB3047

Stopping HttpService ... done Cause: TBD

Solution: TBD WEB3048

HttpService: Received exception while stoping HttpService Cause: TBD

Solution: TBD WEB3049

HttpService: Configured to skip NSS initialization Cause: TBD

Solution: TBD WEB03050

HttpService access log format is missing a percentage (%) Cause: TBD

Solution: TBD WEB3051

Unable to parse port number [{0}] of http-listener [{1}] Cause: TBD

Solution: TBD WEB3052

Chapter 32 WEB Error Messages

347

WEB Messages

Security-enabled on http-listener does not take effect without setting ssl-enabled on http-protocol Cause: TBD
Solution: TBD WEB3054

The acceptor-thread value [{0}] is too high for system resources, using value (10) Cause: TBD
Solution: TBD WEB3055

The acceptor-thread value [{0}] is being interpreted as [{1}] Cause: TBD

Solution: TBD WEB3056

Required attribute cert-nickname not set. Using default (s1as) cert-nickname Cause: TBD
Solution: TBD WEB3057

SSL2 Ciphers [{0}] Cause: TBD

Solution: TBD WEB3058

SSL3 Ciphers [{0}] Cause: TBD

Solution: TBD WEB3059

348

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WEB Messages

J2EE Native Connector is [{0}] Cause: TBD

Solution: TBD WEB3060

Processing property Name [{0}] Value [{1}] Cause: TBD

Solution: TBD WEB3061

HttpService: Unhandled pipeline exception Cause: TBD

Solution: TBD WEB3061

HttpService accesslog rotation: Rotation by size not supported Cause: TBD

Solution: TBD WEB3062

HttpService: Disabling accesslog rotation Cause: TBD

Solution: TBD WEB3063

HttpService: unknown accesslog rotation type [{0}] Cause: TBD

Solution: TBD WEB3064

HttpService: Setting interval rotation value to default Cause: TBD

Solution: TBD
Chapter 32 WEB Error Messages 349

WEB Messages

WEB3065

HttpService: accesslog rotation interval invalid [{0}] Cause: TBD

Solution: TBD WEB3066

HttpService: stats constructor got unexpected exception Cause: TBD

Solution: TBD WEB3067

HttpService: Registering stats objects Cause: TBD

Solution: TBD WEB3068

HttpService: Registering stats objects ... done Cause: TBD

Solution: TBD WEB3069

HttpService: Received exception while registering stats objects Cause: TBD

Solution: TBD WEB3070

HttpService: Received exception while unregistering stats objects Cause: TBD

Solution: TBD WEB3071

350

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WEB Messages

HttpService: Deleting ssl config Cause: TBD

Solution: TBD WEB3072

HttpService: Updating ssl config Cause: TBD

Solution: TBD WEB3073

HttpService: Creating ssl config Cause: TBD

Solution: TBD WEB3074

HttpService: Deleting HttpAccessLog Cause: TBD

Solution: TBD WEB3075

HttpService: Updating HttpAccessLog Cause: TBD

Solution: TBD WEB3076

HttpService: Creating HttpAccessLog Cause: TBD

Solution: TBD WEB3077

HttpService: Could not get domain Cause: TBD

Solution: TBD
Chapter 32 WEB Error Messages 351

WEB Messages

WEB3078

HttpService: Reconfig failed Cause: TBD

Solution: TBD WEB3079

HttpService: Could not obtain native accesslog rotator Cause: TBD

Solution: TBD WEB3080

HttpService: Could not obtain accesslog ration configuration Cause: TBD

Solution: TBD WEB3081

HttpService: Could not stop rotator Cause: TBD

Solution: TBD WEB3082

HttpService: Could not restart rotator Cause: TBD

Solution: TBD WEB3083

HttpService: Could not translate local address to a hostname. Returning IP address. Cause: TBD
Solution: TBD WEB3084
352 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WEB Messages

HttpService: Could not obtain location from default webmodule Cause: TBD
Solution: TBD WEB3085

Restart required. Use of system property before restart is not permitted. Dynamic reconfiguration did not happen Cause: TBD
Solution: TBD

Chapter 32 WEB Error Messages

353

354

C H A P T E R

WSS Error Messages

33

3 3

This chapter describes messages for errors with a WSS prefix.

WSS Messages
WSS0126

Unsupported algorithm type. Only RSA supported. Solution: Check that the signature algorithm is RSA.
WSS0129

Malformed message ds:Signature element missing from the wsse:Security header block. Solution: Check proper signature was generated while signing.
WSS0134

Unable to Initialize XMLCipher with the given Key. Solution: Check that the XMLCipher was initialized properly.
WSS0137

An appropriate JCE provider is not configured in the JRE. Solution: Look at root exception for more clues.
WSS0144

355

WSS Messages

Base64Decoding exception is the root cause. Solution: Check that the data is valid base64 encoded.
WSS0147

TransformationConfiguration exception while trying to use stylesheet to pretty print. Solution: Make sure style sheet is valid.
WSS0148

Exception while trying to pretty print using transform. Solution: Make sure the original SOAP Message and style sheet are both correct.
WSS0156

Error in certificate used for validation. Solution: Check that the token contains a valid Certificate.
WSS0165

XPath does not correspond to a DOM element. Solution: Check that the node represented by the XPath is a valid DOM element.
WSS0167

Invalid signature; verification failed. Solution: Make sure the signature was not tampered with in transit.
WSS0168

Unable to generate a random symmetric key. Solution: Verify that the KeyGenerator has been properly initialized.
WSS0169

Value of FilterParameterConstants.BINARY_SEC_TOKEN is not set. Solution: Check that direct referencestrategy is set before exporting the certificate.
WSS0181

Subject not authorized; validation failed. Solution: Check that the user is authorized.
WSS0182
356 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WSS Messages

FilterParameterConstants.REFERENCE_LIST parameter has a null value. Solution: The reference list that needs to be decrypted usually set by ImportEncryptedKeyFilter.
WSS0183

Could not locate a valid symmetric key needed for decryption. Solution: Value of symmetric key seems to be null. Check its value.
WSS0184

Could not retrieve security domain from the Securable SOAP message. Solution: Make sure the SecurityEnvironment factory has set the right security environment.
WSS0185

Could not find the certificate associated with the direct reference strategy. Solution: Check that the URI is valid and subjectkeyidentifier parameter is set in configuration.
WSS0189

Data decryption algorithm has to be either Triple-DES, AES128-CBC, AES256-CBC. Solution: Check that the encryption algorithm used is either 3DES, AES128_CBC, AES256_CBC.
WSS0190

The number of elements encrypted is less than required/allowed. Solution: Check that the data references for encryption (in message) match the requirements.
WSS0191

A SymmetricKey was not generated earlier that is set on the calling thread. KeyName specified could not locate a key in the security environment. Solution: Check that ExportEncryptedKeyFilter is called before. Check that a valid KeyStore URL is used to instantiate the SecurityEnvironment and it contains a matching SecretKey.
WSS0192

At least one target needs to be specified for encryption. Solution: Check that a non-null target list is used to instantiate the filter.
WSS0193
Chapter 33 WSS Error Messages 357

WSS Messages

Target specified does not correspond to a valid message part. Solution: Check that a valid XPath/QName/wsuId are specified.
WSS0194

SOAP-ENV:Header can not fully be encrypted. SOAP-ENV:Body can not fully be encrypted. Solution: Check that a valid XPath/QName/wsuId are specified complying to the spec.
WSS0195

ReferenceListBlock not set on the calling thread. Solution: Check that ExportEncryptedKeyFilter is called before. Check that ExportReferenceListFilter is called before.
WSS0196

An instance of SecurityEnvironment class for the operating environment was not set on SecurableSoapMessage. Solution: Check that SetSecurityEnvironmentFilter processed the message before.
WSS0198

Only RSA_SHA1 Signature algorithm is supported. Solution: Check that RSA_SHA1 signature algorithm is specified.
WSS0199

Timestamp creation time can not be null. Solution: Check that non-null creation time is used to instantiate the filter.
WSS0203

Header block corresponding to the desired requirement not found. Solution: Check that the message meets the security requirements.
WSS0204

Illegal security header block found in the security header. Solution: Check that the message is SOAP Security specification compliant.
WSS0205

358

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WSS Messages

Requirement for wsu:Timestamp has not been met. Solution: Check that the message meets the security requirements.
WSS0206

Not all receiver requirements for security have been met. Solution: Check that the message meets the security requirements.
WSS0208

Extra security than required by the receiver side policy found in the message. Solution: Check that the message strictly meets the security requirements.
WSS0209

The message filter is incorrectly configured to process an inbound message. Solution: Check that the filters are correctly configured to process inbound messages.
WSS0210

Only RSAv1.5 Key Encryption Algorithm is supported. Solution: Check that the Key Encryption Algorithm used in the inbound message is RSAv1.5.
WSS0212

Receiver requirement for digested password in UsernameToken not met. Solution: Check that the message meets the security requirements.
WSS0213

Receiver requirement for nonce in UsernameToken not met. Solution: Check that the message meets the security requirements.
WSS0215

handle() call for a PropertyCallback on the handler threw exception. Solution: Check the handler implementation.
WSS0216

handle() call on the handler threw exception. Solution: Check the handler implementation.
WSS0217
Chapter 33 WSS Error Messages 359

WSS Messages

handle() call on the handler threw exception. Solution: Check the handler implementation.
WSS0218

handle() call on the handler failed to set the Callback. Solution: Check the handler implementation for SignatureKeyCallback.DefaultPrivKeyCertRequest.
WSS0219

handle() call on the handler failed to set the Callback. Solution: Check the handler implementation for SignatureKeyCallback.DefaultPrivKeyCertRequest.
WSS0220

handle() call on the handler failed to set the Callback. Solution: Check the handler implementation for DecryptionKeyCallback.AliasSymmetricKeyRequest.
WSS0221

handle() call on the handler failed to set the Callback. Solution: Check the handler implementation for SignatureKeyCallback and/or EncryptionKeyCallback, check keystores and truststores.
WSS0222

handle() call on the handler failed to set the Callback. Solution: Check keystore path and ensure that the right keys are present.
WSS0301

Data malformed. Base 64 decoding error. Solution: Verify that data is base64 encoded.
WSS0302

Certificate parsing problem. Solution: Data stream used to create the x509 certificate maybe corrupted.
WSS0303
360 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WSS Messages

Certificate encoding exception. Solution: Check that the x509 data is valid. Could not extract raw bytes from it.
WSS0306

Invalid password type. Solution: Password type must match that specified by the WSS specification.
WSS0307

Nonce encoding namespace check failed. Solution: Nonce encoding type namespace seems invalid.
WSS0310

NoSuchAlgorithmException: Invalid algorithm. Solution: Check that the algorithm passed to SecureRandom is valid.
WSS0311

Password digest could not be created. Solution: Check that the algorithm passed to MessageDigest is valid.
WSS0316

BinarySecurity tokens Encoding type is invalid. Solution: Check that encoding value for BinarySecurity token is valid as per spec.
WSS0317

Could not find X.509 certificate. Solution: Ensure certificate path is not empty and certificate type is correct.
WSS0318

Error while parsing and creating the KeyInfo instance. Solution: Check values passed to KeyInfo constructor.
WSS0319

Could not add key name to KeyInfo Header block. Solution: Check KeyInfo and KeyName have been instantiated without exceptions.
WSS0320
Chapter 33 WSS Error Messages 361

WSS Messages

Could not get KeyName from KeyInfo. Solution: Make sure the KeyName exists in the KeyInfo.
WSS0321

Could not retrieve element from KeyInfo or could not import the node. Solution: Check the element to be converted to SOAPElement.
WSS0322

Exception while parsing and creating the Signature element. Solution: Check that a fully initialized XML Signature was passed.
WSS0323

Exception while trying to sign. Solution: Check the key used to sign.
WSS0324

Exception while adding a Reference with URI, transforms and Digest algorithm URI to SignedInfo. Solution: Verify the following:

Check getSignatureValue failure cause from underlying XML DSIG implementation. Check that the message signed using corresponding private key, and has not been tampered with. Check values passed to constructor of XMLSignature.addDocument passed to XML DSig implementation are correct.

WSS0327

Could not retrieve element from Signature or could not import the node. Solution: Check the element to be converted to SOAPElement.
WSS0328

Error parsing date. Solution: Check date format is in UTC. Check it is yyyy-MM-ddTHH:mm:ssZ or yyyy-MM-ddTHH:mm:ss.sssZ.
WSS0329

362

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WSS Messages

Expecting UsernameToken Element. Solution: Check that the next element is UsernameToken.
WSS0330

Username not first child of UsernameToken. Solution: Make sure first child of wsse:UsernameToken is Username in wsse namespace.
WSS0331

Element may not be a proper UsernameToken. Solution: Check that the UsernameToken matches the token schema.
WSS0332

Username was null. Solution: Check UsernameToken contains a valid Username.

WSS0333

Keystore URL is null. Solution: Check that the property javax.net.ssl.keyStore is set properly.
WSS0334

KeyIdentifier holds invalid ValueType. Solution: Check KeyIdentifier ValueType's value.

WSS0335

KeyReference type not supported. Solution: KeyReference type should be one of KeyIdentifier, Reference, X509Data.
WSS0336

Cant locate public key. Solution: Check public key retrieved should not be null.
WSS0337

Could not resolve URI. Solution: Check DirectReferences ValueType, it is not supported.
WSS0338
Chapter 33 WSS Error Messages 363

WSS Messages

Key Reference Mechanism not supported. Solution: Check reference is one of X509IssuerSerial, DirectReference, KeyIdentifier.
WSS0339

Support for processing information in the given ds:KeyInfo is not present. Solution: Check ds:KeyInfo matches schema.
WSS0340

Creation time cannot be ahead of current UTC time. Solution: Check system time and ensure it is correct.
WSS0341

Creation time is very old. Solution: Check system time and ensure it is correct.
WSS0342

BinarySecurity Tokens Value type is invalid. Solution: Check that valueType for BinarySecurity token is valid as per spec.
WSS0343

Error in creating the BST due to {0}. Solution: Check that all required values are set on the Binary Security Token, including TextNode value.
WSS0344

The binary data in the Security Token can not be decoded, expected Base64 encoding. Solution: Check to see that the encoding format of the Binary Security Token is Base64Binary.
WSS0345

Error creating SOAPElement for EncryptedDataHeaderBlock. Solution: If SOAPElement is used to create EncryptedData HeaderBlock, check to see that it is valid as per spec.
WSS0346
364 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WSS Messages

Invalid SOAPElement passed to EncryptedDataHeaderBlock constructor. Solution: Check that the SOAPElement passed to EncryptedDataHeaderBlock is valid as per spec.
WSS0347

SOAPElement used to initialize EncryptedType may not have CipherData element. CipherData may not have been set on the EncryptedType. Solution: Check to see SOAPElement used to initialize EncryptedType has CipherData. Check to see setCipherData() is called on the EncryptedType.
WSS0348

Error creating SOAPElement for EncryptedKeyHeaderBlock. Solution: If SOAPElement is used to create EncryptedKeyHeaderBlock, check to see that it is valid as per spec.
WSS0349

Invalid SOAPElement passed to EncryptedKeyHeaderBlock(). Solution: Check that the SOAPElement passed to EncryptedKeyHeaderBlock() is valid as per spec.
WSS0350

Error creating/updating CipherData SOAPElement (in EncryptedKeyHeaderBlock). Solution: Refer your SAAJ API Documentation.
WSS0351

Error creating EncryptionMethod SOAPElement. Solution: Refer your SAAJ API Documentation.
WSS0352

Error creating javax.xml.soap.Name for CipherValue. Solution: Refer your SAAJ API Documentation.
WSS0353

No CipherValue element(s) are present in CipherData. Solution: Check to see if setCipherValue() is called on EncryptedType.
WSS0354
Chapter 33 WSS Error Messages 365

WSS Messages

An error may have occurred creating javax.xml.soap.Name for EncryptionMethod. Cause: An error may have occurred creating javax.xml.soap.Name for KeyInfo. An error may have occurred creating javax.xml.soap.Name for CipherData. An error may have occurred creating javax.xml.soap.Name for EncryptionProperties.
Solution: Refer your SAAJ API Documentation. WSS0355

Error creating com.sun.org.apache.xml.security.keys.content.keyvalues.DSAKeyValue. Error creating com.sun.org.apache.xml.security.keys.content.keyvalues.RSAKeyValue. Error creating com.sun.org.apache.xml.security.keys.content.KeyValue. Solution: Check that a non-null SOAPElement is passed to addXXXKeyValue().
WSS0356

Error creating com.sun.org.apache.xml.security.keys.content.X509Data. Solution: Check that a non-null SOAPElement is passed to addX509Data().
WSS0357

Error getting KeyValue from KeyInfo for the given index. Solution: Check that the ds:KeyInfo element has ds:KeyValue elements. Check that the index (beginning with 0) used to refer the ds:KeyValue element is valid.
WSS0358

Error getting X509Data from KeyInfo for the given index. Solution: Check that the ds:KeyInfo element has ds:X509Data elements. Check that the index (beginning with 0) used to refer the ds:X509Data element is valid.
WSS0359

Error adding com.sun.org.apache.xml.security.keys.content.X509Data to KeyInfo. Solution: Check that a valid com.sun.org.apache.xml.security.keys.content.X509Data (as per specs.) is passed to addX509Data().
WSS0360

An error may have occurred creating javax.xml.soap.Name for ReferenceList. Solution: Refer your SAAJ API Documentation.
WSS0361
366 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WSS Messages

An error may have occurred creating org.w3c.dom.Element for ReferenceList. Cause: The org.w3c.dom.Document object passed ReferenceListHeaderBlock() may be null.
Solution: Check that the Namespace specified does not contain any illegal characters as per XML 1.0 specification. Check that the QName specified is not malformed (Refer to the J2SE Documentation for more information). Check that a non-Null Document is passed to the ReferenceListHeaderBlock(). WSS0362

Invalid SOAPElement passed to ReferenceListHeaderBlock(). Solution: Check that the SOAPElement passed to ReferenceListHeaderBlock() is valid as per spec.
WSS0363

Error creating javax.xml.soap.SOAPElement for xenc:DataReference. Cause: Error adding xenc:DataReference (SOAPElement) as child element of xenc:DataReference (SOAPElement). Error setting URI attribute on javax.xml.soap.SOAPElement for xenc:DataReference.
Solution: Refer your SAAJ API Documentation. WSS0365

Error creating javax.xml.soap.SOAPElement for namespace node. Solution: Refer your SAAJ API Documentation.
WSS0368

Error getting SOAPEnvelope from SOAPPart. Solution: Refer your SAAJ API Documentation.
WSS0369

Error getting SOAPHeader from SOAPEnvelope. Cause: Error creating SOAPHeader.

Solution: Refer to your SAAJ API Documentation. WSS0371

Chapter 33 WSS Error Messages

367

WSS Messages

Error in getting the SOAPBody from the SOAPMessage. Error in creating javax.xml.soap.Name for setting the fault on SOAPBody. Error in adding fault to SOAPBody. Solution: Refer your SAAJ API Documentation.
WSS0376

Error importing the SOAPElement representing the header block to the document corresponding to the SOAPMessage to which the header is being added. Solution: Check that the SecurityHeaderBlock can be transformed to a valid SOAPElement. Refer to the J2SE Documentation for more.
WSS0377

Error creating javax.xml.soap.SOAPElement for SecurityTokenReference. Solution: Refer your SAAJ API Documentation.
WSS0378

Error creating javax.xml.soap.SOAPElement for SecurityTokenReference. Solution: Check that the org.w3c.dom.Document object passed to SecurityTokenReference() is non-null. Refer your SAAJ API Documentation.
WSS0379

SOAPElement passed to SecurityTokenReference() is not a valid SecurityTokenReference element as per spec. Solution: Check that a valid SOAPElement as per spec. is passed to SecurityTokenReference().
WSS0380

The ds:Reference would already have been set using the constructors. Solution: Check that a SOAPElement with ds:Reference (child element) is not used to instantiate SecurityTokenReference.
WSS0381

Error in setting the passed ReferenceElement on SecurityTokenReference. Solution: Refer your SAAJ API Documentation.
WSS0382

368

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WSS Messages

Error appending ds:Object element to ds:Signature. Solution: Check that a valid ds:Object SOAPElement (as per spec.) is passed to appendObject(). Check that a non-null SOAPElement is passed to appendObject().
WSS0383

Owner document of ds:Signature SOAPElement is null. Solution: Check that the Document used to instantiate SignatureHeaderBlock() is not null.
WSS0384

Error creating javax.xml.soap.Name for Timestamp. Solution: Refer your SAAJ API Documentation.
WSS0385

The SOAPElement used to instantiate Timestamp() is not valid (as per specification). Solution: Check that the Localname and NamespaceURI of the SOAPElement used to create Timestamp() are correct as per spec.
WSS0386

Error creating javax.xml.soap.SOAPElement for Timestamp. Error adding child SOAPElements to the Timestamp element. Solution: Refer your SAAJ API Documentation.
WSS0387

Username is not set. Solution: Check that a Username has been passed through the configuration file or through the callback handler.
WSS0388

Error creating javax.xml.soap.SOAPElement for UsernameToken. Error adding child SOAPElements to the UsernameToken element. Solution: Refer your SAAJ API Documentation.
WSS0389

Chapter 33 WSS Error Messages

369

WSS Messages

Base64 nonce encoding type has not been specified. Solution: Check that the nonce encoding type used to create UsernameToken is Base64.
WSS0390

UTF-8 Charset is unsupported for byte-encoding (a string). Solution: Refer your J2SE Documentation.
WSS0391

Invalid Localname and NamespaceURI of the SOAPElement used for creating the token. Solution: Check that the Localname and NamespaceURI of the SOAPElement used to create X509SecurityToken are valid (as per specification).
WSS0393

The expiration time in Timestamp cannot be before current UTC time. Solution: Check system time and ensure it is correct.
WSS0394

Error parsing date. Solution: Check date format is in UTC. Check it is yyyy-MM-ddTHH:mm:ssZ or yyyy-MM-ddTHH:mm:ss.sssZ.
WSS0500

Classname not a recognized class name for a MessageFilter. Solution: Check that the class implements MessageFilter.
WSS0502

Element encountered does not match element expected. Solution: Check that the XML file follows schema for defining configuration.
WSS0503

Element encountered does not match valid element expected. Solution: Check that the XML file follows schema for defining configuration.
WSS0508

370

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WSS Messages

Default settings can not be specified after custom settings are specified. Solution: Check that no sender operations or receiver requirements are specified in a configuration. file. Check that no sender or receiver settings are programmatically added.
WSS0509

Custom settings can not be specified after default settings are specified. Solution: Check that no default settings are programmatically added.
WSS0511

Non-permissible boolean value string - valid strings are true and false. Solution: Check that the boolean value strings are either true or false.
WSS0512

Non-permissible attribute on a Security Configuration element. Solution: Check that the configuration file is consistent with the security configuration schema.
WSS0513

Non-permissible element on xwss:SecurityConfiguration. Solution: Check that the configuration file is consistent with the security configuration schema.
WSS0514

Non-permissible child element in a Security Configuration element. Solution: Check that the configuration file is consistent with the security configuration schema.
WSS0515

Impermissible value for key reference string. Solution: Check that the configuration file is consistent with the security configuration schema.
WSS0516

Non-permissible duplicate element on a Security Configuration Element. Solution: Check that the configuration file is consistent with the security configuration schema.
WSS0517
Chapter 33 WSS Error Messages 371

WSS Messages

Non-permissible duplicate element on a Security Configuration Element. Solution: Check that the configuration file is consistent with the security configuration schema.
WSS0519

Non-permissible/missing attribute value. Solution: Check that the configuration file is consistent with the security configuration schema.
WSS0520

xwss:SymmetricKey is not permitted along with xwss:X509Token. Solution: Check that the configuration file is consistent with the security configuration schema.
WSS0600

A Key can not be located in SecurityEnvironment for the Token Reference. Solution: Check that the certificate referred to is valid and present in the Keystores.
WSS0601

A Key can not be located in SecurityEnvironment for the KeyValue. Solution: Check that the certificate referred to is valid and present in the Keystores.
WSS0602

A Key can not be located in SecurityEnvironment for the X509Data. Solution: Check that the certificate referred to is valid and present in the Keystores.
WSS0603

XPathAPI TransformerException in finding element with matching wsu:Id/Id/SAMLAssertionID. Solution: Refer your XPathAPI documentation.
WSS0606

Input Node Set to STR Transform is empty. Solution: Check that the Referenced Node (to be STR transformed) in ds:SignedInfo is valid.
WSS0608
372 Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WSS Messages

The Reference Mechanism in the SecurityTokenReference is not supported. Solution: Check that the Reference Mechanism is either Direct/KeyIdentifier/X509IssuerSerial.
WSS0609

The referenced security token is neither an XML token nor a raw binary token. Solution: Check the referenced security token.
WSS0650

Username/Password data file not found. Solution: Check that the system property com.sun.xml.wss.usersFile is set.
WSS0654

Error creating javax.xml.soap.Name for wsu:Id. Solution: Try the following:

Refer your SAAJ API Documentation. Check that the Class object corresponds to the header block identified by the SOAPElement.

WSS0656

The Keystore URL is not specified/invalid in server.xml. A Keystore file does not exist in $user.home. Solution: Check that the keystoreFile attribute is specified on SSL Coyote HTTP/1.1 Connector element in server.xml and is valid. Check that a keystore file exists in $user.home.
WSS0700

An instance of SecurityEnvironment is not set on SecurableSoapMessage. Solution: Check that setSecurityEnvironment() is called on the SecurableSoapMessage. Check that SetSecurityEnvironmentFilter is applied on SecurableSoapMessage.
WSS0701

No X509v3 Certificate can be located for the alias in Keystore. Cause: If no alias has been specified for signing, no default certificate is available.
Solution: Check that a default certificate is available and/or a valid alias is used. WSS0702
Chapter 33 WSS Error Messages 373

WSS Messages

The X509v3 Certificate for the given alias does not contain a subject key identifier. Solution: Check that a valid X509v3 certificate is present in Keystores.
WSS0704

Agreement name: SESSION-KEY-VALUE, has not been set on the SecurityEnvironment instance. Solution: Check that the agreement name SESSION-KEY-VALUE is set on SecurityEnvironment using setAgreementProperty().
WSS0750

Error creating javax.xml.soap.SOAPElement. Solution: Refer your SAAJ API Documentation.

WSS0751

The localname of the SOAPElement passed is not Reference. The namespace URI of the SOAPElement passed does not conform to WSS Spec. Solution: Check that a SOAPElement conformant to spec. is passed.
WSS0752

The localname of the SOAPElement passed is not Embedded. The namespace URI of the SOAPElement passed does not conform to WSS Spec. Solution: Check that a SOAPElement conformant to spec. is passed.
WSS0753

An embedded token in wsse:Embedded element is missing. Solution: Check that the token element is conformant to the WSS specification.
WSS0754

Token on EmbeddedReference has already been set. Cause: A SOAPElement representation of EmbeddedReference containing the Token is used to create the EmbeddedReference instance.
WSS0756

374

Sun GlassFish Communications Server 2.0 Error Message Reference October 2009

WSS Messages

Error creating SOAPElement for wsse:KeyIdentifier. Solution: Check your SAAJ API Documentation.
WSS0757

Error adding KeyIdentifier value to wsse:KeyIdentifer. Solution: Check your SAAJ API Documentation.
WSS0758

Error creating javax.xml.soap.Name. Solution: Refer your SAAJ API Documentation.

WSS0759

An X509IssuerSerial instance can not be created. Solution: Check that the SOAPElement passed to the constructor is conformant to spec. (and has X509IssuerSerial child elements).
WSS0800

ds:KeyInfo in the message is not a valid one. Solution: Check if the ds:KeyInfo in the message is valid.

Chapter 33 WSS Error Messages

375

376