bea weblogic enterprise - oracle · the bea weblogic enterprise information set consists of the...

BEA WebLogic EnterpriseSystem Messages

B E A W e b L o g i c E n t e r p r i s e 4 . 2D o c u m e n t E d i t i o n 4 . 2

J u l y 1 9 9 9

Copyright

Copyright © 1999 BEA Systems, Inc. All Rights Reserved.

Restricted Rights Legend

This software and documentation is subject to and made available only pursuant to the terms of the BEA Systems License Agreement and may be used or copied only in accordance with the terms of that agreement. It is against the law to copy the software except as specifically allowed in the agreement. This document may not, in whole or in part, be copied, photocopied, reproduced, translated, or reduced to any electronic medium or machine-readable form without prior consent, in writing, from BEA Systems, Inc.

Use, duplication or disclosure by the U.S. Government is subject to restrictions set forth in the BEA Systems License Agreement and in subparagraph (c)(1) of the Commercial Computer Software-Restricted Rights Clause at FAR 52.227-19; subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013, subparagraph (d) of the Commercial Computer Software--Licensing clause at NASA FAR supplement 16-52.227-86; or their equivalent.

Information in this document is subject to change without notice and does not represent a commitment on the part of BEA Systems. THE SOFTWARE AND DOCUMENTATION ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. FURTHER, BEA Systems DOES NOT WARRANT, GUARANTEE, OR MAKE ANY REPRESENTATIONS REGARDING THE USE, OR THE RESULTS OF THE USE, OF THE SOFTWARE OR WRITTEN MATERIAL IN TERMS OF CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE.

Trademarks or Service Marks

BEA, ObjectBroker, TOP END, and TUXEDO are registered trademarks of BEA Systems, Inc. BEA Builder, BEA Connect, BEA Manager, BEA MessageQ, Jolt, M3, and WebLogic are trademarks of BEA Systems, Inc.

All other company names may be trademarks of the respective companies with which they are associated.

System Messages

Document Edition Date Software Version

4.2 July 1999 BEA WebLogic Enterprise 4.2

Contents

PrefacePurpose of This Document ....................................................................................v

How to Use This Document ................................................................................ vi

Related Documentation ....................................................................................... ix

Contact Information............................................................................................ xii

1. IntroductionSystem Message Catalogs and Prefixes ............................................................ 1-1

2. Multiple FactoryFinder MessagesMultiple FactoryFinder (MFF) Messages 1000-1019 ....................................... 2-1

3. C++ ORB MessagesC++ ORB Messages 1-164................................................................................ 3-1

4. Java ORB MessagesJava ORB Messages 1-44 .................................................................................. 4-1

5. ORB Command-line MessagesORB Command-line Messages 1-139 ............................................................... 5-1

6. IIOP Server Listener/Handler MessagesIIOP Server Listener/Handler Messages 1000-1099......................................... 6-1

IIOP Server Listener/Handler Messages 1100-1199....................................... 6-31

IIOP Server Listener/Handler Messages 1200-1399....................................... 6-61

IIOP Server Listener/Handler Messages 1400-1453..................................... 6-104

System Messages iii

7. Object Transaction Service MessagesObject Transaction Service (OTS) Messages 1000-1005.................................. 7-1

8. C++ TP Framework MessagesC++ TP Framework (TPFW) Messages 1-127.................................................. 8-1

9. Java TP Framework MessagesJava TP Framework Messages 1-66 .................................................................. 9-1

10. Interface Service Map MessagesInterface Service Map (ISM) Messages 4000-4030 ........................................ 10-1

11. Java XML Parser MessagesJava XML Parser Messages 1-81 .................................................................... 11-1

12. Java Server-side Infrastructure MessagesJava Server-Side Infrastructure Messages 1-119............................................. 12-1

13. Java Server Threading MessagesJava Server Threading Messages 1-10 ............................................................ 13-1

14. Minor Code Mapping

iv System Messages

iated

Preface

Purpose of This Document

This document describes the BEA WebLogic Enterprise (sometimes referred to as WLE) system messages. This document contains only the system messages that are unique to the WebLogic Enterprise software. For messages that are common to the WebLogic Enterprise software and the BEA TUXEDO system software, refer to the BEA TUXEDO System Messages.

Note: Effective February 1999, the BEA M3 product is renamed. The new name of the product is BEA WebLogic Enterprise (WLE).

Who Should Read This Document

This document is intended for programmers who encounter errors while developing or building applications using the WebLogic Enterprise software.

How This Document Is Organized

The System Messages document is organized as follows:

t Chapter 1, “Introduction,” lists the WLE system message catalogs and assocprefixes.

t Chapter 2, “Multiple FactoryFinder Messages,” describes the Multiple FactoryFinder system messages.

System Messages v

.

s.

ne

ver

m

rk

rk

ce

from

t Chapter 3, “C++ ORB Messages,” describes the C++ ORB system messages

t Chapter 4, “Java ORB Messages,” describes the Java ORB system message

t Chapter 5, “ORB Command-line Messages,” describes the ORB command-lisystem messages.

t Chapter 6, “IIOP Server Listener/Handler Messages,” describes the IIOP SerListener/Handler system messages.

t Chapter 7, “Object Transaction Service Messages,” describes the OTS systemessages.

t Chapter 8, “C++ TP Framework Messages,” describes the C++ TP Framewosystem messages.

t Chapter 9, “Java TP Framework Messages,” describes the Java TP Framewosystem messages.

t Chapter 10, “Interface Service Map Messages,” describes the Interface ServiMap system messages.

t Chapter 11, “Java XML Parser Messages,” describes the Java XML Parser system messages.

t Chapter 12, “Java Server-side Infrastructure Messages,” describes the Java Server-side Infrastructure system messages.

t Chapter 13, “Java Server Threading Messages,” describes the Java server application threading messages.

t Chapter 14, “Minor Code Mapping,” provides details about what action you need to take when you receive system exceptions with corresponding minor codes.

How to Use This Document

This document, System Messages, is designed primarily as an online, hypertext document. If you are reading this as a paper publication, note that to get full use this document you should access it as an online document via the Online Documentation CD for the BEA WebLogic Enterprise 4.2 release.

vi System Messages

The following sections explain how to view this document online, and how to print a copy of this document.

Opening the Document in a Web Browser

To access the online version of this document, open the following file:

\doc\wle\v42\index.htm

Note: The online documentation requires Netscape Communicator version 4.0 or later, or Microsoft Internet Explorer version 4.0 or later.

Printing from a Web Browser

You can print a copy of this document, one file at a time, from the Web browser. Before you print, make sure that the chapter or appendix you want is displayed and selected in your browser. To select a chapter or appendix, click anywhere inside the chapter or appendix you want to print.

The Online Documentation CD also includes Adobe Acrobat PDF files of all of the online documents. You can use the Adobe Acrobat Reader to print all or a portion of each document. On the CD Home Page, click the PDF Files button and scroll to the entry for the document you want to print.

Documentation Conventions

The following documentation conventions are used throughout this document.

Convention Item

boldface text Indicates terms defined in the glossary.

Ctrl+Tab Indicates that you must press two or more keys simultaneously.

italics Indicates emphasis or book titles.

System Messages vii

monospace text

Indicates code samples, commands and their options, data structures and their members, data types, directories, and file names and their extensions. Monospace text also indicates text that you must enter from the keyboard.

Examples:

#include <iostream.h> void main ( ) the pointer psz

chmod u+w *

.doc

BITMAP

float

monospace boldface text

Identifies significant words in code.

Example:

void commit ( )

monospace italic text

Identifies variables in code.

Example:

String expr

UPPERCASE TEXT

Indicates device names, environment variables, and logical operators.

Examples:

LPT1

SIGNON

OR

{ } Indicates a set of choices in a syntax line. The braces themselves should never be typed.

[ ] Indicates optional items in a syntax line. The brackets themselves should never be typed.

Example:

buildobjclient [-v] [-o name ] [-f file-list]... [-l file-list]...

| Separates mutually exclusive choices in a syntax line. The symbol itself should never be typed.

Convention Item

viii System Messages

Related Documentation

The following sections list the documentation provided with the BEA WebLogic Enterprise software, related BEA publications, and other publications related to the technology.

BEA WebLogic Enterprise Documentation

The BEA WebLogic Enterprise information set consists of the following documents:

Installation Guide

C++ Release Notes

Java Release Notes

Getting Started

Guide to the University Sample Applications

Guide to the Java Sample Applications

... Indicates one of the following in a command line:

t That an argument can be repeated several times in a command line

t That the statement omits additional optional arguments

t That you can enter additional parameters, values, or other information

The ellipsis itself should never be typed.

Example:

buildobjclient [-v] [-o name ] [-f file-list]... [-l file-list]...

.

.

.

Indicates the omission of items from a code example or from a syntax line. The vertical ellipsis itself should never be typed.

Convention Item

System Messages ix

Creating Client Applications

Creating C++ Server Applications

Creating Java Server Applications

Administration Guide

Using Server-to-Server Communication

C++ Programming Reference

Java Programming Reference

Java API Reference

JDBC Driver Programming Reference

System Messages (this document)

Glossary

Technical Articles

Note: The Online Documentation CD also includes Adobe Acrobat PDF files of all of the online documents. You can use the Adobe Acrobat Reader to print all or a portion of each document.

BEA Publications

Selected BEA TUXEDO 6.5 for BEA WebLogic Enterprise version 4.2 documents are available on the Online Documentation CD.

To access these documents:

1. Click the Other Reference button from the main menu.

2. Click the TUXEDO Documents option.

x System Messages

Other Publications

For more information about CORBA, Java, and related technologies, refer to the following books and specifications:

Cobb, E. 1997. The Impact of Object Technology on Commercial Transaction Processing. VLDB Journal, Volume 6. 173-190.

Edwards, J. with DeVoe, D. 1997. 3-Tier Client/Server At Work. Wiley Computer Publishing.

Edwards, J., Harkey, D., and Orfali, R. 1996. The Essential Client/Server Survival Guide. Wiley Computer Publishing.

Flanagan, David. May 1997. Java in a Nutshell, 2nd Edition. O’Reilly & Associates, Incorporated.

Flanagan, David. September 1997. Java Examples in a Nutshell. O’Reilly & Associates, Incorporated.

Fowler, M. with Scott, K. 1997. UML Distilled, Applying the Standard Object Modeling Language. Addison-Wesley.

Gamma, E., Helm, R., Johnson, R., and Vlissides, J. 1995. Design Patterns: Elements of Reusable Object-Oriented Software. Addison-Wesley Professional Computing Series.

Jacobson, I. 1994. Object-Oriented Software Engineering: A Use Case Driven Approach. Addison-Wesley.

Mowbray, Thomas J. and Malveau, Raphael C.(Contributor). 1997. CORBA Design Patterns, Paper Back and CD-ROM Edition. John Wiley & Sons, Inc.

Orfali, R., Harkey, D., and Edwards, J. 1997. Instant CORBA. Wiley Computer Publishing.

Orfali, R., Harkey, D. February 1998. Client/Server Programming with Java and CORBA, 2nd Edition. John Wiley & Sons, Inc.

Otte, R., Patrick, P., and Roy, M. 1996. Understanding CORBA. Prentice Hall PTR.

Rosen, M. and Curtis, D. 1998. Integrating CORBA and COM Applications. Wiley Computer Publishing.

System Messages xi

Rumbaugh, J., Blaha, M., Premerlani, W., Eddy, F., and Loresen, W. 1991. Object-Oriented Modeling and Design. Prentice Hall.

The Common Object Request Broker: Architecture and Specification. Revision 2.2, February 1998. Published by the Object Management Group (OMG).

CORBAservices: Common Object Services Specification. Revised Edition. Updated: November 1997. Published by the Object Management Group (OMG).

Contact Information

The following sections provide information about how to obtain support for the documentation and the software.

Documentation Support

If you have questions or comments on the documentation, you can contact the BEA Information Engineering Group by e-mail at [email protected]. (For information about how to contact Customer Support, refer to the following section.)

Customer Support

If you have any questions about this version of the BEA WebLogic Enterprise product, or if you have problems installing and running the BEA WebLogic Enterprise software, contact BEA Customer Support through BEA WebSupport at www.beasys.com. You can also contact Customer Support by using the contact information provided on the Customer Support Card, which is included in the product package.

When contacting Customer Support, be prepared to provide the following information:

t Your name, e-mail address, phone number, and fax number

t Your company name and company address

xii System Messages

t Your machine type and authorization codes

t The name and version of the product you are using

t A description of the problem and the content of pertinent error messages

System Messages xiii

xiv System Messages

CHAPTER

1 Introduction

This chapter lists the system message catalogs and associated prefixes.

System Message Catalogs and Prefixes

When system messages are generated, they are given a prefix and they are placed in the user log (ULOG). Table 1-1 lists the system message catalogs, their prefixes, and the chapter in this manual where the message is documented.

Table 1-1 Message Catalogs and Prefixes

Message Catalog Prefix See Chapter

Multiple FactoryFinder Messages LIBMFF_CAT 2

C++ ORB Messages LIBORB_CAT 3

Java ORB Messages IJORB_CAT 4

ORB Command-line Messages LIBORBCMD_CAT 5

IIOP Server Listener/Handler Messages

ISNAT_CAT 6

Object Transaction Service Messages

LIBOTS_CAT 7

C++ TP Framework Messages LIBTPFW_CAT 8

Java TP Framework Messages IJTPFW_CAT 9

Interface Service Map Messages LIBISM_CAT 10

System Messages 1-1

1 INTRODUCTION

Java XML Parser Messages IJXML_CAT 11

Java Server-side Infrastructure Messages

IJINFRA_CAT 12

Java Server Threading Messages IJTHREADS_CAT 13

Table 1-1 Message Catalogs and Prefixes (Continued)

Message Catalog Prefix See Chapter

1-2 System Messages

CHAPTER

2 Multiple FactoryFinder Messages

Multiple FactoryFinder (MFF) Messages 1000-1019

Note: When Multiple FactoryFinder messages are listed in the user log (ULOG), these messages have the prefix LIBMFF_CAT. For example, message 1000 is listed as LIBMFF_CAT:1000.

1000 ERROR: Application must contain at least two NameManagers.

Description If two NameManagers are not configured in the application when a NameManager service is booted, the NameManager quits its startup and writes this error message to the userlog. At least two servers must be configured to run the NameManager service as part of any application. This requirement ensures that a working copy of the name-to-IOR mapping is always available. If the servers are on different machines and one machine crashes, when the machine and application are restarted, the new NameManager obtains the mapping from the other NameManager.

Action Configure two NameManagers in the UBBCONFIG file.

System Messages 2-1

2 MULTIPLE FACTORYFINDER MESSAGES

1001 ERROR: Application must contain one Master NameManager.

Description NameManagers can be designated as either master or slave, the default being slave. If a master NameManager service is not configured in the application and is not running when a slave NameManager service starts, the server terminates itself during boot.

Action Configure one of the NameManagers as the master using the -M option in the UBBCONFIG file.

1002 ERROR: Application can only contain one Master NameManager.

Description Only one master NameManager can be specified in an application. If more than one NameManager service is designated as a master, the NameManager quits its startup.

Action Configure only one NameManager as the master in the UBBCONFIG file.

1003 ERROR: RegistrarNotAvailable Exception. NOTIFY Operations Staff!

Description Accompanying this message is an exception raised to an application object. The RegistrarNotAvailable exception is raised if the FactoryFinder service cannot locate the NameManager service. Possible situation that has occurred is that no NameManager servers are running.

Action Because there are no NameManagers active that contain the factory name-to-IOR mapping, all server applications must be shut down and restarted to reload the NameManagers.

2-2 System Messages

MULTIPLE FACTORYFINDER (MFF) MESSAGES 1000-1019

1004 ERROR: CannotProceed Exception. NOTIFY Operations Staff!

Description Accompanying this message is an exception raised to an application object. The CannotProceed exception is raised if the FactoryFinder or NameManager encounters an internal error during the search, and the error is written to the userlog. Depending on the severity of the internal error, the server running the FactoryFinder or NameManager services may have terminated.

Action If a FactoryFinder service has terminated, start a new FactoryFinder service. If a NameManager service has terminated and another NameManager service is running, start a new NameManager service. If there are no NameManager services running, all server applications must be shut down and restarted to reload the NameManagers.

1005 ERROR: Cannot access TMIB, tperrno = tperrno. [IC=internalcode].

Description The NameManager or FactoryFinder service cannot access the TMIB.

Action Follow the recovery procedures for the tperrno displayed.

1006 ERROR: Out of memory. [IC=internalcode].

Description A server running either the NameManager and/or FactoryFinder services has run out of memory. This situation is more likely to occur in a server running the NameManager if the number of factories registered has approached the maximum size of virtual memory.

Action The application factories may need to be divided into multiple domains where each domain has its own distinct NameManager capability. Either reduce the memory usage on the machine or add more memory.

System Messages 2-3


1007 ERROR: Cannot advertise servicename, tperrno = tperrno. [IC=internalcode]

Description A NameManager server cannot advertise a network service needed for coordination with other NameManager servers.

Action Follow the recovery procedures for the IIOP Server Listener displayed.

1008 WARN: Cannot unadvertise servicename, tperrno = tperrno. [IC=internalcode]

Description A NameManager server cannot unadvertise a network service that was used to coordinate with other NameManager servers.


1009 ERROR: Cannot subscribe to servicename, tperrno = tperrno. [IC=internalcode]

Description A NameManager server cannot subscribe to events posted by the System Event Broker.


1010 WARN: Cannot unsubscribe from servicename, tperrno = tperrno. [IC=internalcode]

Description A NameManager server cannot unsubscribe for events posted by the System Event Broker.


2-4 System Messages


1011 ERROR: Cannot recover factory mapping.

Description A NameManager was not able to obtain a complete factory mapping from another NameManager.

Action Shut down and restart the NameManager that generated the message.

1012 ERROR: Application must start TMSYSEVT first.

Description The System Event Broker, TMSYSEVT, was not started before the NameManagers were booted.

Action Start TMSYSEVT before starting any of the NameManagers.

1013 ERROR: TMSYSEVT must be active.

Description The System Event Broker, TMSYSEVT, was not active when the NameManagers were started.

Action Ensure that TMSYSEVT has been started before the NameManagers are started.

1014 INFO: Total application factory shutdown assumed.

Description A server application is attempting to unregister an application factory during Server::release(). The server detects a problem with the unregister operation at this time. Upon further investigation, the server discovers that the entire application is shutting down. As such, the unregister silently fails because the NameManagers also shut down.

Action None.

See Also Server::release(), tpsvrdone(3)

System Messages 2-5


1015 ERROR: Application did not configure any NameManagers.

Description No NameManagers were specified in the options for the TMFFNAME servers in the UBBCONFIG file.

Action Specify at least two TMFFNAME servers as NameManagers, with one being the master NameManager, and an additional TMFFNAME server as the FactoryFinder.

1016 ERROR: Slave NameManager started before Master NameManager.

Description In the UBBCONFIG file, a slave NameManager server was started before a master NameManager server. When the slave starts, it tries to communicate with a master and fails.

Action In the UBBCONFIG file, start the master NameManager before starting any slave NameManagers.

See Also For more information about the TMFFNAME server, see the Administration Guide.

1017 ERROR: Cannot configure both a NameManager and a FactoryFinder together.

Description The NameManager and the FactoryFinder were configured using the same server process. This is an invalid combination.

Action Separate the NameManager and FactoryFinder into two separate processes.

See Also For more information about the TMFFNAME server, see the Administration Guide

2-6 System Messages


there wn new

d. The er.

nd

1018 WARN: Posting failed; Slave NameManagers may become out of sync.

Description The master NameManager failed to post an update message to the System Event Broker, brought about by either a register_factory or an unregister_factory method. The System Event Broker then cannot notify any slave NameManagers. As a result, the slave’s factory name mapping may become out of sync with the master.

Action First check to ensure that the System Event Broker is running. Second, ensure that is a communications path between it and the master NameManager. Lastly, shut doand restart the slave NameManagers. On reboot, the slave NameManagers obtain acopy of the factory name mapping from the master NameManager.

1019 INFO: Detected message loss; resynchronizing name map.

Description A slave NameManager, upon receipt of an update message from the master NameManager, has discovered that a previous update message was never receiveslave requests a refresh of the factory name mapping from the master NameManag

Action None.

1020 ERROR: Initialization: Unable to open FactoryFinder initialization file

Description An error has occurred while attempting to open the FactoryFinder initialization file.

Action Ensure that the FactoryFinder initialization file is present, is in the correct location, athat the name corresponds to the master Name Manager -f filename command line argument in the ubbconfig file.

System Messages 2-7


1021 ERROR: Initialization: Unable to process FactoryFinder initialization file

Description An error has occurred while attempting to process the FactoryFinder initialization file.

Action Examine the initialization file for errors. This message is often displayed with one of the errors in the range of 1022 to 1025 in this catalog.

1022 ERROR: Text field error in factory id.kind values: line = line_number

Description A text error has been encountered in the factoryID.factoryKind values while attempting to process the FactoryFinder initialization file.

Action Correct the factoryID.factoryKind values in the FactoryFinder initialization file.

1023 ERROR: Text field error in Domain ID keyword or value: line = line_number

Description A text error has been encountered in the DOMAINID keyword or value while attempting to process the FactoryFinder initialization file.

Action Correct the DOMAINID keyword or value in the FactoryFinder initialization file.

1024 ERROR: Text field error in RName keyword or value: line = line_number

Description A text error has been encountered in the RNAME keyword or value while attempting to process the FactoryFinder initialization file.

Action Correct the RNAME keyword or value in the FactoryFinder initialization file.

2-8 System Messages


1025 ERROR: File contained no Section Types

Description An error has occurred while attempting to process the FactoryFinder initialization file. No Section Types (DM_REMOTE_FACTORIES and DM_LOCAL_FACTORIES) were found in the file.

Action Edit the FactoryFinder initialization file to include Section Types.

1026 ERROR: Invoke on FactoryFinder in TDomain: domain_name failed

Description An error has occurred while attempting to invoke the FactoryFinder in the specified domain.

Action Ensure that the FactoryFinder and domain name information was correctly specified.

System Messages 2-9


2-10 System Messages

CHAPTER

3 C++ ORB Messages

C++ ORB Messages 1-164

Note: When C++ ORB messages are listed in the user log (ULOG), the messages have the prefix LIBORB_CAT. For example, message 1 is listed as LIBORB_CAT:1.

1 INFO: Successful completion.

Description The operation was completed successfully.

Action None.

Exception None.

2 ERROR: Operation failed.

Description The operation failed.

Action A serious error has occurred that probably involves a programming function that is being performed. For additional information about the failure, refer to additional system messages, if provided.

Exception UNKNOWN

System Messages 3-1

3 C++ ORB MESSAGES

3 FATAL: Fatal error detected.

Description A fatal error was detected. Processing stops.

Action A serious error has occurred that probably involves a programming function that is being performed. For additional information about the failure, refer to additional system messages, if provided.

Exception UNKNOWN

4 ERROR: Item not found.

Description The specified item was not found. This message is commonly used by the WLE list routines.

Action For additional information about the failure, refer to additional system messages, if provided. If the information is insufficient and you are unable to resolve the problem, contact BEA Customer Support.

Exception UNKNOWN

5 ERROR: Bad list.

Description Attempted to use a WLE list with a WLE list routine when the list was not created by a WLE list routine.

Action None.

Exception BAD_PARAM

6 ERROR: Index out of range.

Description The specified index into a list is out of range; that is, it exceeds the list’s boundaries.

3-2 System Messages

C++ ORB MESSAGES 1-164

Action Verify the size of the list and the specified index.

Exception BAD_PARAM

6 ERROR: Index out of range.

7 FATAL: Insufficient memory.

Description There was not an adequate amount of virtual memory to complete the operation.

Action Verify memory usage or adjust process quotas and system configuration.

Exception NO_MEMORY

8 ERROR: Could not find file ‘ Filename’.

Description The specified file could not be found.

Action Verify the file name.

Exception UNKNOWN

9 ERROR: Insufficient privilege to access file ‘Filename’.

Description The user lacks sufficient privileges to access the file.

Action Verify the file privileges and the file specification.

Exception NO_PERMISSION

System Messages 3-3

3 C++ ORB MESSAGES

10 ERROR: File ‘Filename’ not available.

Description The specified file is not available (for example, the disk is unavailable or the network is unavailable).

Action Verify the availability of the file.

Exception UNKNOWN

11 ERROR: Bad file specification ‘Filename’.

Description The file specification is invalid (for example, too many characters, invalid characters, invalid form, and so on).


Exception UNKNOWN

12 ERROR: Buffer too small.

Description The buffer specified for a routine argument is too small to contain the result.

Action Enlarge the buffer.

Exception BAD_PARAM

3-4 System Messages


13 ERROR: Could not create file ‘Filename’.

Description The specified file could not be created. This problem could be caused by an invalid file specification, the existence of a file with the same file name (cannot overwrite), the unavailability of the specified disk or network, and so on.

Action Verify the file name and the output device.

Exception UNKNOWN

14 ERROR: Unrecognized status ‘status’ attempting to get a message.

Description The specified message could not be retrieved and an unrecognized status value was returned.

Action Contact BEA Technical Support.

Exception INTERNAL

15 ERROR: An internal error has occurred.

Description An unrecoverable internal processing error has occurred.


Exception INTERNAL

17 ERROR: A typecode internal error has occurred.



System Messages 3-5

3 C++ ORB MESSAGES

Exception INTERNAL

17 ERROR: A typecode internal error has occurred.

20 ERROR: Bad type specified for list.

Description An invalid list type was specified when a list was created or accessed.

Action Verify that the list and the list type specification are one of the WLE product supported lists.

Exception BAD_TYPECODE

23 ERROR: List element already exists.

Description A list element corresponding to an element being added already exists.

Action Verify the list and the element to be inserted.

Exception UNKNOWN

24 ERROR: Count specified for list is invalid.

Description The count specified for the list is invalid. The list count specified is not the actual list count.

Action Verify the list and the list count.

Exception BAD_PARAM

3-6 System Messages


25 ERROR: Invalid data type specified.

Description The value specified does not conform to the specified data type.

Action Correct the data type or value specified.


26 ERROR: Insufficient privilege to perform operation.

Description The user lacks sufficient privileges to perform the requested operation.

Action Verify the user’s privileges for the requested operation.


33 ERROR: Dynamic load of component ‘ComponentName’ for subsystem ‘Name’ failed.

Description The specified component of the subsystem could not be dynamically loaded.

Action Verify that the installation succeeded and that the subsystem file exists.

Exception INITIALIZE

34 ERROR: Could not open file ‘Filename’.

Description The specified file could not be opened.


Exception UNKNOWN

System Messages 3-7

3 C++ ORB MESSAGES

35 ERROR: Could not read file ‘Filename’.

Description The specified file could not be read.

Action Verify the file name and the protection.

Exception UNKNOWN

36 ERROR: The file ‘Filename’ is locked.

Description The specified file is currently locked.

Action Specify an alternate file, or attempt to access the file later.

Exception UNKNOWN

37 ERROR: Invalid operation.

Description An invalid or illegal operation was attempted.

Action Verify the operation.

Exception BAD_OPERATION

38 ERROR: Bad object for operation.

Description An invalid object was specified for the operation.

Action Verify that the correct object is being used for the operation.

Exception INV_OBJREF

3-8 System Messages


39 ERROR: Invalid parameter for operation.

Description An invalid parameter was specified for the operation.

Action Verify that the proper parameter was specified for the operation.

Exception BAD_PARAM

41 ERROR: Not yet implemented.

Description The specified feature is not yet implemented.

Action None

Exception NO_IMPLEMENT

42 ERROR: Unknown error: ‘ ErrorText’.

Description The error text corresponding to the unknown error.

Action Determine the appropriate action from the error text.

Exception UNKNOWN

43 ERROR: Bad Repository Id ‘RepID’.

Description An invalid repository identifier was specified.

Action Supply a valid repository identifier.

Exception BAD_PARAM

System Messages 3-9

3 C++ ORB MESSAGES

44 ERROR: GIOP Locate Forwarding loop detected.

Description While attempting to locate an ORB to which to send a given invoke request, a forwarding loop was detected.

Action Contact the system manager for the remote ORB to which you are trying to communicate and report that there is a forwarding loop between multiple servers (that is, each server is forwarding requests to the other).

Exception IMP_LIMIT

45 ERROR: There is no support for this function.

Description The operation attempted is not supported on this platform.

Action Review the product documentation to ensure the feature is available on this platform.

Exception UNKNOWN

46 ERROR: No Current implementation was found.

Description No current implementation was found for the operation.

Action None.

Exception UNKNOWN



48 ERROR: Current type was already registered.

Description A Current for this type has already been registered.

Action None.

Exception UNKNOWN

49 ERROR: MessageErrorMessage received.

Description A GIOP MessageErrorMessage was received and the ORB could not fall back to a previous version.

Action Check that the client and server support compatible GIOP versions.

Exception UNKNOWN

50 ERROR: Could not find the entry point ‘ EntryPoint’ in the dynamically loaded library ‘Name’.

Description The given shared library does not contain the given entry point name.

Action Verify that the installation was successful.

Exception UNKNOWN

51 WARN: One or more unsupported kinds were encountered.

Description Not all TCKinds are currently supported.

Action Check the client for the use of unsupported kinds.

Exception MARSHAL

System Messages 3-11

3 C++ ORB MESSAGES

52 WARN: A UserException cannot be thrown from this function.

Description CORBA::UserException occurred in a function that does not support user exceptions.

Action Check the function to see whether a user exception was incorrectly thrown.

Exception IMP_LIMIT

53 ERROR: An error was detected in the configuration settings.

Description Invalid configuration settings were detected during initialization.

Action Determine whether the configuration settings passed to ORB_init are correct.

Exception INITIALIZE

55 ERROR: Specified object ‘ObjectName’ already exists.

Description The specified object already exists in the repository.

Action None.

Exception UNKNOWN



56 ERROR: Repository error in ‘ Filename’.

Description An error occurred in the repository.

Action For additional information about the failure, refer to additional system messages, if provided. If the information is insufficient and you are unable to resolve the problem, contact BEA Customer Support.

Exception INTF_REPOS

58 ERROR: Attribute ‘ AttributeName’ already exists.

Description The user attempted to redefine an attribute that already exists.

Action Verify the attribute specified and the object.

Exception UNKNOWN

59 ERROR: Bad object name ‘ObjectName’.

Description The specified object name is an invalid WLE object name (for example, illegal characters, too many characters, bad format, and so on).

Action Verify the name.

Exception INV_IDENT


3 C++ ORB MESSAGES

60 ERROR: Bad type ‘ObjectType’ for object ‘ObjectName’.

Description The specified object type is not one of the supported object types. Alternatively, the object may be of an incorrect type for the operation.

Action Verify the type.


62 ERROR: Object ‘Objectname’ not found.

Description The specified object was not found.

Action Verify the object name, whether the object exists, and that the correct repository was specified.

Exception UNKNOWN

64 ERROR: Attribute ‘ AttributeName’ not found.

Description The specified attribute was not found.

Action Verify attribute and object names, and that the correct repository was specified.

Exception UNKNOWN



65 ERROR: Value not found.

Description The specified value was not found.

Action Verify the value specification and object names and that the correct repository was specified.

Exception UNKNOWN

66 ERROR: File error for repository ‘ Filename’.

Description A file error occurred for the specified repository.

Action Verify the file name and the file.


67 ERROR: The repository ‘Filename’ is locked.

Description The specified repository is locked due to a write operation.

Action Exit the application that has the repository opened for write.


68 ERROR: Repository ‘Filename’ not found.

Description The specified repository was not found.

Action Verify the file specification and that the repository exists.



3 C++ ORB MESSAGES

69 ERROR: No repository specified.

Description The user attempted an operation on a repository (for example, open) without specifying the file name of the repository.

Action Specify a repository file specification.


71 ERROR: Repository ‘Filename’ is full.

Description The specified repository is full. No new definitions may be stored.

Action Remove unnecessary object definitions or use another repository.

Exception IMP_LIMIT

72 ERROR: Object is referenced by other objects.

Description For a delete object operation, the object is referenced by other objects and may not be deleted.

Action Remove the references, if possible.

Exception UNKNOWN



75 ERROR: Bad database version.

Description A repository created using an old version of WLE software was specified on an open repository operation.

Action Re-create the database using the latest WLE software version.


76 ERROR: No privilege for attempted operation on repository ‘Filename’.

Description The user attempted a database operation that he or she is not privileged to do.

Action Obtain the proper privilege to perform the operation.


77 ERROR: Database operation on repository ‘Filename’ timed out.

Description The attempted database operation timed out.

Action Try the operation again.


78 ERROR: File ‘Filename’ is not a valid ORB configuration file.

Description The WLE software attempted to open a database file and the database tag did not match. The specified database was not created by the WLE product.

Action Make sure the file is a valid WLE database file.



3 C++ ORB MESSAGES

79 ERROR: An internal error has occurred.



Exception INTERNAL

80 ERROR: File error: ‘ErrorText’.

Description The error text corresponding to the file error.

Action Determine the appropriate action from the error text.


81 Error: Invalid Object Reference.

Description The specified repository object reference was not one of the supported types. Alternatively, the types specified may be incorrect for the operation being performed.

Action Verify the object reference.

Exception BAD_PARAM

83 ERROR: Container ‘ObjectName’ Is Inherited By ‘ InheritedBy’.

Description A container could not be deleted because it is inherited by another container.

Action None.

Exception BAD_PARAM



84 ERROR: ‘ ObjectName’ Not Deleted.

Description A object could not be deleted. See secondary messages for specific reason.

Action None.

Exception BAD_PARAM

85 ERROR: Repository Corrupted.

Description An object within the repository has been corrupted.

Action Re-create the repository or recover from a previous version.

Exception BAD_PARAM

86 ERROR: Bad Repository Id ‘RepID’.

Description An invalid repository identifier was specified.

Action Specify a valid repository identifier.

Exception BAD_PARAM

87 ERROR: Invalid Container ‘ ObjectName’.

Description An attempt was made to create an object inside a container and the container type is not valid for this type of object.

Action Specify a valid container.

Exception BAD_PARAM


3 C++ ORB MESSAGES

89 ERROR: Bad Type ‘InternalType’.

Description The object reference is invalid or corrupted.


Exception BAD_PARAM

90 ERROR: Invalid Limit Type ‘ ObjectName’.

Description The limit type specified is not valid or is not valid in the context within which it is being used.

Action Specify a valid limit type value.

Exception BAD_PARAM

92 ERROR: Invalid constant value.

Description The user attempted to create a constant and the type of the value provided was not a string or the value of the string was NULL.

Action Verify the type and value of the constant.

Exception BAD_PARAM

93 ERROR: Bad Result Type.

Description The type of the result for the operation is invalid.


Exception BAD_PARAM



94 ERROR: Bad Attribute Type.

Description The type of the attribute is invalid.


Exception BAD_PARAM

95 ERROR: Bad TypeDef Type.

Description The type of the typedef is invalid.


Exception BAD_PARAM

96 ERROR: Bad Constant Type.

Description The type of the constant is invalid.


Exception BAD_PARAM

97 ERROR: Bad Exception Type.

Description The type of the exception is invalid.


Exception BAD_PARAM


3 C++ ORB MESSAGES

98 ERROR: Invalid TypeCode Id ‘RepID’.

Description The typecode points to an invalid typedef.


Exception BAD_PARAM

99 ERROR: Signature ‘ObjectName’ Not Fetched.

Description The signature for a method could not be fetched because an error occurred while the specified operation was being fetched.


Exception BAD_PARAM

100 ERROR: Bad Type Id ‘TypeId’ .

Description The object reference is invalid or corrupted.


Exception None.

103 ERROR: Transport error ‘ TransportError’.

Description A transport error has occurred.

Action Verify the operation of the transport.

Exception COMM_FAILURE



104 ERROR: Specified arguments do not match defined arguments.

Description The arguments for the operation invocation do not match the arguments defined for the operation (that is, too many arguments, too few arguments, inconsistent data type or direction, and so on).

Action Verify that the specified arguments match those defined for the operation.

Exception BAD_PARAM

105 ERROR: Specified method not found on implementation skeleton.

Description The specified method could not be called from the implementation invoke routine because the method was not found.

Action Verify that the method is defined for the implementation, and that the correct servant is used for invocation. Regenerate the implementation skeleton if necessary.

Exception NO_IMPLEMENT

108 ERROR: Unknown node ‘Node’ specified.

Description An unregistered node name was specified.

Action Make sure the node specified is registered.



3 C++ ORB MESSAGES

110 ERROR: The shared library ‘Name’ could not be dynamically loaded.

Description The ImagePath WLE registry parameter for a WLE loadable component or subsystem could not be dynamically loaded.

Action Verify that the dynamic library can be loaded. Check privileges, system constraints, and so on.

Exception UNKNOWN

112 ERROR: Bad dynamic library specification.

Description The name of the specified dynamic library is invalid.

Action Verify the name and path for the dynamic library.

Exception INV_IDENT

113 ERROR: The underlying transport could not be initialized.

Description The underlying transport (for example, TCP/IP) could not be initialized.

Action Verify the operation of the transport. Make sure that the appropriate software is installed and that it is running.

Exception None.



114 ERROR: An internal software error occurred.

Description An internal software error occurred. The operation was not completed.


Exception INTERNAL

115 ERROR: Bad object name ‘ObjectName’.

Description The specified object name is not a valid WLE object name (for example, illegal characters, bad format, too many characters, and so on).

Action Specify a valid object name.

Exception INV_IDENT

117 ERROR: Transport level communication failed.

Description Communication to a server has failed. This failure, in many cases, is due to a timeout while a method is being completed.

Action Check the server you are attempting to communicate with. In addition, verify the operation of the network. If the method is long running, try calling it asynchronously.



3 C++ ORB MESSAGES

118 ERROR: The requested server was not found or is not accessible on the network.

Description The WLE software could not locate the requested server on the network.

Action Verify that the server is running and is available on the network transport.

Exception UNKNOWN

119 ERROR: Exceeded marshalling buffer.

Description The marshalling buffer was exceeded.


Exception INTERNAL

120 ERROR: The transport message was not properly identified.

Description The message received on the transport was not identified as a WLE message.


Exception INTERNAL

121 ERROR: Invalid argument.

Description This message occurs when an invalid argument is specified.

Action Verify the arguments passed in.

Exception INV_OBJREF



122 ERROR: Specified result does not match defined result.

Description The result for the method invocation does not match the result defined for the method.

Action Verify that the specified result matches that defined for the operation.

Exception BAD_PARAM

123 ERROR: String length is greater than the bound.

Description The length of the string exceeds the bound specified for the type in the OMG IDL statements.

Action Verify the length. Either change the bound in the type definition in the OMG IDL statements or set the string to be of a length less than or equal to the bound.

Exception BAD_PARAM

124 ERROR: An invalid type was specified for an ANY argument.

Description An argument of type ANY was specified with an invalid type field.

Action Verify the ANY argument. Make sure that the argument type is a valid typecode.

Exception MARSHAL


3 C++ ORB MESSAGES

125 ERROR: Specified number of arguments do not match defined number of arguments.

Description The number of arguments for the invocation does not match the number of arguments defined for the operation.

Action Verify that the number of specified arguments matches those defined for the operation.

Exception BAD_PARAM

126 ERROR: Specified argument name ‘ArgumentName’ does not match defined argument name.

Description The name of the argument does not match the name of the argument defined for the operation.

Action Verify that the names of the specified arguments match those defined for the operation.

Exception BAD_PARAM

127 ERROR: Specified argument type does not match defined argument type for ‘ArgumentName’.

Description The type of the argument does not match the type of the argument defined for the operation.

Action Verify that the type of the specified argument matches that defined for the operation.

Exception BAD_PARAM



128 ERROR: TypeCode ID not found.

Description The TypeCode was not found in any of the TypeCode lookup routines. Without the TypeCode, the data cannot be marshaled or unmarshaled.

Action Verify that the id is from a type or an exception known to the client or the server. If you are using DII instead of stubs, ensure that the TypeCode lookup routine has been registered.


129 ERROR: Transport level send timeout.

Description Communication between server and client has failed. This failure is due to a timeout that occurs while the client is attempting to send an invoke request or the server is attempting to send a reply to an invoked request.

Action Check the client or server with which you are attempting to communicate. In addition, verify the operation of the network. If the method is long running, try invoking the method asynchronously.


130 ERROR: The object is constrained to be local.

Description An attempt was made to use an object that is constrained to be local in a context where nonlocal information is required.

Action Do not use a local object for an operation that may require going across the wire.

Exception MARSHAL


3 C++ ORB MESSAGES

132 INFO: No more items.

Description No keys or named values are available.

Action The enumeration of keys or named values has reached the end of the items.

Exception None.

147 ERROR: Registry ‘RegistryName’ not found.

Description The specified registry partition was not found.

Action Verify the registry partition name and that the registry partition exists.


149 ERROR: OA already exists.

Description Internal error only. An Object Adapter with the same name already exists.


Exception OBJ_ADAPTER

150 ERROR: OA does not exist.

Description Internal error only. An Object Adapter with the specified name does not exist.





152 ERROR: OA not active.

Description Internal error only. An Object Adapter is not active.



153 ERROR: OA is suspended.

Description Internal error only. An Object Adapter is suspended.



154 ERROR: OA queue is too large.

Description An Object Adapter has exceeded the size of the internal queue.



155 ERROR: OA object not found.

Description An Object Adapter object ID was not found.

Action Ensure that the Object is active in the server.

Exception OBJECT_NOT_EXIST


3 C++ ORB MESSAGES

156 ERROR: OA Servant not active.

Description Internal error only. An Object Adapter object servant was not active.



157 ERROR: OA Servant not unique.

Description Internal error. An Object Adapter object servant was not unique.



158 ERROR: Server Request discarded.

Description An Object Adapter discarded the server request and the request was not processed.

Action None.

Exception TRANSIENT

159 ERROR: Object is not a ServantActivator.

Description The servant manager is not a PortableServer::ServantActivator object.

Action Verify that a ServantActivator object is specified in the call to set_servant_manager.

Exception TRANSIENT



160 ERROR: Object is not a ServantLocator.

Description The servant manager is not a PortableServer::ServantLocator object.

Action Verify that a ServantLocator object is specified in the call to set_servant_manager.

Exception TRANSIENT

161 ERROR: Object is not a AdapterActivator.

Description The servant manager is not a PortableServer::AdapterActivator object.

Action Verify that an AdapterActivator object is specified in the call to the activator.

Exception TRANSIENT

163 ERROR: An error was returned by Tuxedo.

Description The BEA TUXEDO system returned an error. For more information, see the minor code and the user log (ULOG).

Action None

Exception UNKNOWN

164 ERROR: ‘ ObjectName’ is not an operation in the interface.

Description You specified an operation name that is defined in the interface, but is not an operation.

Action Ensure that the specified name is an operation in the interface.

Exception Marshal


3 C++ ORB MESSAGES


CHAPTER

4 Java ORB Messages

Java ORB Messages 1-44

Note: When Java ORB messages are listed in the user log (ULOG), the messages have the prefix IJORB_CAT. For example, message 1 is listed as IJORB_CAT:1.

1 "ERROR: Unexpected message type {0}"

Description The type of the incoming message is not GIOP. The type of the incoming message is indicated by {0}. The request is not processed.

Action Take corrective action so that the type of the incoming message is GIOP.

2 "ERROR: Could not resolve object key"

Description The ORB was unable to resolve the object key in the incoming request. The request is not processed and an appropriate exception is returned to the user.

Action Contact BEA Customer Support.

System Messages 4-1

4 JAVA ORB MESSAGES

3 "ERROR: Unexpected reply status: LOCATION_FORWARD"

Description The ORB received an unexpected reply status of LOCATION_FORWARD in response to an earlier request. The request is not processed and an appropriate exception is returned to the user.


4 "ERROR: Invalid reply status"

Description The ORB received an invalid reply status in response to an earlier request. The request is not processed and an appropriate exception is returned to the user.


5 "ERROR: Unable to unmarshal user exception"

Description An attempt by the ORB to unmarshal a user exception received in response to an earlier request failed. An appropriate exception is returned to the user.


6 "ERROR: Invalid profile in object reference"

Description The ORB detected an invalid profile in the object reference of the distributed object. If this occurred while processing an incoming message, the request is not processed and an appropriate exception is returned to the user.


4-2 System Messages

JAVA ORB MESSAGES 1-44

7 "ERROR: Attempt to write to output stream failed"

Description An IOException() was raised while the ORB was attempting to write to an internal output stream. The request is not processed and an appropriate exception is returned to the user.


8 "ERROR: Invalid completion status"

Description The ORB received an invalid completion status while processing the reply message in response to an earlier request. An appropriate exception is returned to the user.


9 "ERROR: Only M3 keys may be processed"

Description The ORB detected an object key whose type does not match with those supported by WLE. The request is not processed and an appropriate exception is returned to the user.

Action Make sure that only object keys supported and returned by the WLE system are used in the WLE Java environment.

System Messages 4-3

4 JAVA ORB MESSAGES

10 "ERROR: Only keys with major version number 1 and minor version number 1 may be processed"

Description The ORB detected an object key whose major version number and minor version number are not both 1. The request is not processed and an appropriate exception is returned to the user.

Action Make sure that only object keys supported and returned by the WLE system are used in the WLE Java environment.

11 "ERROR: Unable to encode object key"

Description The ORB received an exception while attempting to encode the object key. An appropriate exception is returned to the user.


13 "ERROR: Attempt to create POA with an invalid policy"

Description An invalid or inconsistent policy was specified while attempting to create the Portable Object Adapter (POA).

Action If this error message was received while the application attempted to create the POA, make sure that the correct policy was used. If the error message occurred while the system internally created a POA, contact BEA Customer Support.

15 "ERROR: POA contains invalid IdAssignmentPolicyValue Value"

Description An invalid or inconsistent value for IdAssignmentPolicy of the POA was specified while attempting to create an object reference.


4-4 System Messages


16 "ERROR: No information about interface {0}"

Description The ORB does not contain any information about the interface specified in {0}. Any attempt to create an object reference for that interface will fail.

Action Make sure the interface is specified in the corresponding XML file for that server.

17 "ERROR: No stub information about interface {0}"

Description The ORB does not contain any stub information about the interface specified in {0}. Any attempt to create an object reference for that interface will fail.

Action Make sure the stub of the interface is specified in the corresponding XML file for that server.

18 "ERROR: Stub creation failed with exception {0}"

Description The ORB received an exception while attempting to create the stub for an interface. The {0} value contains details of the exception received by the ORB.


19 "ERROR: No delegate implementation exists for {0}"

Description The ORB could not find a delegate implementation for the interface specified in {0}. An appropriate exception is returned to the user.


System Messages 4-5

4 JAVA ORB MESSAGES

20 "ERROR: Class {0} has no base class"

Description The ORB could not find the base class for the interface specified in {0}. An appropriate exception is returned to the user.


21 "ERROR: Class {0} is not a stub class"

Description The ORB expected the class name specified in {0} to be a stub class. An appropriate exception is returned to the user.


22 "ERROR: Class {0} has no Delegate constructor"

Description The ORB could not find a Delegate constructor for the class name specified in {0}. An appropriate exception is returned to the user.


23 "ERROR: Cannot create instance of class {0}, exception: {1}"

Description The ORB could not create an instance of the class name specified in {0}. An appropriate exception is returned to the user. The {1} value provides exception details.


4-6 System Messages


24 "ERROR: Class {0} contains no ids"

Description The ORB could not find any IDs for the class name specified in {0}. An appropriate exception is returned to the user.


25 "ERROR: Class {0} is not a skeleton class"

Description The ORB expected the class specified in {0} to be a skeleton class. An appropriate exception is returned to the user.


29 "ERROR: Class {0} has no _type_ids field, exception returned {1}"

Description The class name specified in {0} has no _type_ids field. The {1} value provides details of the exception returned to the ORB. An appropriate exception is returned to the user.


30 "ERROR: Class {0} cannot access _type_ids field, exception returned {1}"

Description The class name specified in {0} cannot access its _type_ids field. The {1} value provides details of the exception returned to the ORB. An appropriate exception is returned to the user.


System Messages 4-7

4 JAVA ORB MESSAGES

32 "ERROR: Class {0} has no default constructor, exception returned {1}"

Description The class name specified in {0} has no default constructor. The {1} value provides details of the exception returned to the ORB. An appropriate exception is returned to the user.


33 "ERROR: Failed to advertise interface {0}"

Description The ORB was unable to advertise the interface specified in {0}. An appropriate exception is returned to the user.


34 "ERROR: No information about interface {0}"

Description The ORB does not contain any information about the interface specified in {0}. Any attempt to create an object reference for that interface will fail.

Action Make sure the interface is specified in the corresponding XML file for that server. If the error persists, contact BEA Customer Support.

35 "ERROR: No stub information about interface {0}"

Description The ORB does not contain any stub information about the interface specified in {0}. Any attempt to create an object reference for that interface will fail.

Action Make sure the stub of the interface is specified in the corresponding XML file for that server.

4-8 System Messages


36 "ERROR: Unable to create stub, exception returned {0}"

Description The ORB was unable to create a stub for the interface. The {0} value provides details of the exception returned to the ORB.


37 "ERROR: Unable to find POA"

Description The ORB was unable to find its local Portable Object Adapter (POA) while processing the request. The request is not processed.


38 "ERROR: Missing string"

Description The ORB could not convert the stringified IOR to an object because the stringified IOR was empty.

Action Provide a nonempty stringified IOR to be converted into an object.

39 "ERROR: Stringified IOR does not start with IOR:"

Description The ORB could not convert the stringified IOR to an object because the stringified IOR does not start with IOR:.

Action Provide a proper stringified IOR to be converted into an object.

System Messages 4-9

4 JAVA ORB MESSAGES

40 "ERROR: Stringified IOR is not of even length"

Description The ORB could not convert the stringified IOR to an object because the stringified IOR was not of even length.


41 "ERROR: Stringified IOR contains non hexadecimal characters"

Description The ORB could not convert the stringified IOR to an object because the stringified IOR contained non-hexadecimal characters.


42 "ERROR: Object is not a ServantInfo"

Description The ORB expects the object to be an instance of the ServantInfo class.


43 "ERROR: Cannot get skeleton information {0}"

Description The ORB is unable to get the skeleton information of the interface specified in {0}.


44 "ERROR: Failed to advertise interfaces"



Description The ORB is unable to advertise the interfaces.



4 JAVA ORB MESSAGES


CHAPTER

5 ORB Command-line Messages

ORB Command-line Messages 1-139

Note: When ORB command-line messages are listed in the user log (ULOG), the messages have the prefix LIBORBCMD_CAT. For example, message 2 is listed as LIBORGCMD_CAT:2.

2 ERROR: Bad UUID ‘ UUID’.

Description The specified UUID is invalid (for example, has illegal characters, has too many characters, has an invalid format, and so on).

Action Verify the UUID.

3 ERROR: Bad object name: ‘ObjectName’.

Description The specified object name is not a valid WLE object name (for example, has illegal characters, is too long, has an invalid format, or does not exist).

Action Specify a valid WLE object name.

System Messages 5-1

5 ORB COMMAND-LINE MESSAGES

4 ERROR: Bad type ‘DataType’ for argument.

Description The data type specified for an argument is not a supported WLE argument data type.

Action Specify a valid WLE argument data type.

5 ERROR: Object not deleted.

Description For a DELETE REPOSITORY_OBJECT operation, the object was not deleted.

Action For more information, see any additional messages.

6 ERROR: Not yet implemented.

Description The specified operation is not yet implemented.

Action None.

7 ERROR: Object ‘ObjectName’ is damaged.

Description The specified object is damaged.

Action Verify the object and reload if necessary.

5-2 System Messages

ORB COMMAND-LINE MESSAGES 1-139

8 ERROR: Bad object type for object ‘ObjectName’ .

Description For a SHOW REPOSITORY operation, the object type for the specified object is invalid.

Action Reload the object definition.

9 ERROR: Object ‘ObjectName’ not found.

Description The specified object was not found.

Action Verify the object name and the repository specification.

10 FATAL: Definition file ‘ Filename’ contained one or more errors; object(s) not loaded.

Description The definition file for the LOAD operation contained errors.

Action Because this message is typically displayed immediately after one or more other messages, refer to the previous messages that are displayed to determine the nature of the problem.

11 FATAL: Fatal syntax error.

Description A syntax error occurred while the definition file was being parsed.

Action Verify the syntax at the designated point in the definition file.

System Messages 5-3


12 FATAL: Unsupported language ‘LanguageName’.

Description The specified programming language is not supported for the GENERATE IMPLEMENTATION or INTERFACE operation.

Action Specify a valid language name.

13 FATAL: Exceeded nesting limit for INCLUDE directive.

Description The limit of open files for LOAD or COMPILE operations was exceeded.

Action Reduce the number of #include directives.

14 FATAL: ‘ MethodServerName’ must be an implementation.

Description For the GENERATE IMPLEMENTATION operation, the object specified by MethodServerName must be an implementation.

Action Verify the object name. Specify a valid implementation.

15 FATAL: Bad or unsupported option.

Description UNIX systems only. An invalid option was specified on the WLE command line.

Action Verify that all options specified are valid for the command.

5-4 System Messages


16 FATAL: Too many arguments.

Description UNIX systems only. Too many arguments were specified on the WLE command line.

Action Verify the syntax of the specified command.

17 FATAL: Required arguments are not specified.

Description UNIX systems only. Not all required arguments were specified on the command line.

Action Verify the syntax of the specified command, and specify the required arguments.

18 FATAL: One or more specified options conflict.

Description UNIX systems only. Conflicting options were specified on the command line.

Action Verify that all options specified are supported for the specified form of the command.

19 FATAL: Encountered error token generated by SHOW command. Please verify definition file.

Description The &BAD& token generated by the SHOW command was encountered during a LOAD operation.

Action Verify the definition file, and replace the &BAD& markers with the correct syntax.

System Messages 5-5


20 FATAL: Unexpected EOF inside of comment.

Description During the parse of the definition file for a LOAD operation, an unclosed comment resulted in a premature EOF.

Action Verify the definition file; close the comment.

21 ERROR: Could not set symbol ‘Name’.

Description On a GET ARGUMENT operation, a value could not be set for the specified symbol.

Action Verify that the symbol name is valid; verify that the value is not too long.

22 ERROR: Unknown command.

Description For the UNIX interface, the specified command is unknown.

Action Verify the command.

23 INFO: Empty definition file ‘ Filename’; no object(s) found.

Description For the LOAD or COMPILE operation, the definition file did not contain any object definitions.

Action Define some objects.

5-6 System Messages


24 INFO: No proxies found.

Description No proxies were found matching the specified criteria.

Action Modify or eliminate the Remote Host, Remote User, or Local User fields.

25 FATAL: Input line is too long.

Description For LOAD or COMPILE commands, a line in the input definition file is too long.

Action Divide the line across multiple lines; use the concatenation character.

26 ERROR: Repository error.

Description The operation failed due to a repository error.

Action Refer to associated messages for additional information.

27 ERROR: An internal software error occurred.

Description An internal software error occurred. The operation was not completed.


28 FATAL: Exceeded scope limit.

Description The limit of nested scopes for COMPILE operations was exceeded.

Action Reduce the number of nested module and interface definitions.

System Messages 5-7


29 ERROR: ‘ Name’ already defined in this scope.

Description This definition conflicts with a previous definition of the same name in this scope.

Action Determine whether the two identifiers should have the same name.

30 ERROR: ‘Name’ not defined.

Description This identifier is not defined within the scope of this usage.

Action Define the identifier.

31 ERROR: `Name' not defined in scope.

Description This identifier is not defined within the specified scope.

Action Define the identifier in the specified scope.

32 ERROR: ‘Name’ has incorrect type for qualifier.

Description This identifier cannot be used as a qualifier in a scoped name because it is not a type that can contain other objects.

Action Correct the scoped name.

33 RROR: ‘Name’ is not a valid type specification.

Description This specified identifier cannot be used as a type specification.

Action Correct the type specification.

5-8 System Messages


34 ERROR: Not a simple type, use a type name instead.

Description A struct, union, or enum has been used where a simple type is required.

Action Use a type name instead of a struct, union, or enum.

35 ERROR: Size must be an integer constant.

Description The size of a bounded string, bounded sequence, or array must be an integer constant.

Action Enter an integer for the size.

36 ERROR: Size must be a positive value.

Description The size of a bounded string, bounded sequence, or array must be a positive integer constant.

Action Enter an positive integer for the size.

37 ERROR: Case label has wrong type.

Description The type of the constant expression in the case label does not match the type specified in the switch statement.

Action Enter an expression of the correct type.

System Messages 5-9


38 ERROR: Case label has invalid value.

Description The value of the constant expression in the case label is invalid for the data type specified in the switch statement. The value may be too large or too small for the data type, or negative for an unsigned data type.

Action Enter an expression of the correct value.

39 ERROR: Expression has wrong type.

Description The value of the expression does not match the defined type.

Action Enter an expression of the correct type.

40 ERROR: Expression value out of range.

Description The value of the expression is not within the range of the defined data type.

Action Enter an expression within the range of the data type.

41 ERROR: String is too long.

Description The length of the string expression exceeds the size of the defined bounded string.

Action Increase the size of the string.

42 ERROR: Cyclic type reference must be in a Sequence.

Description A cyclic reference to a type must be contained within a sequence.

Action Move the cyclic type reference into a sequence.



43 ERROR: Constant has no value.

Description A reference has been made to a constant definition that has no defined value.

Action Define a value for the constant.

44 ERROR: ‘ Name’ is not a valid switch type.

Description The specified type is not a valid type for a switch statement. Valid types are long, short, unsigned long, unsigned short, char, boolean, or enum.

Action Enter one of the valid types.

45 ERROR: Only one default label allowed.

Description Only one default label is allowed in a switch statement.

Action Remove the duplicate default label.

46 ERROR: Duplicate label value.

Description More than one case label contains the same value. Label values must be unique.

Action Remove the duplicate case label value.



47 ERROR: Structure is empty.

Description The structure definition contains no members. A structure must contain at least one member.

Action Add at least one member to the structure.

48 ERROR: No full interface definition found for ‘ Name’.

Description The full interface definition for the specified forward reference is not found.

Action Remove the forward reference or add an interface definition.

49 ERROR: ‘Name’ must be an exception.

Description The identifier specified in the raises statement is not an exception.

Action Correct the name to specify an exception.

50 ERROR: ‘Name’ is a malformed context property.

Description This context property is not correctly specified. A context property is a sequence of alphanumeric, ’.’, ’_’, and ’*’ characters. The first character must be an alphabetic character. An asterisk may be used only as the last character of the string.

Action Correct the context property.



51 ERROR: ‘ Name’ is not a valid constant type.

Description The specified type is not a valid type for a constant statement. Valid types are long, short, unsigned long, unsigned short, char, boolean, float, or double, plus any previously defined name of these types.

Action Enter a valid type.

52 ERROR: ‘DataType’ and ‘Name’ types cannot be mixed in expression.

Description The specified expression contains mixed types (for example, integers mixed with floats). A mixed-type expression is illegal.

Action Eliminate the use of mixed types in the expression.

53 ERROR: Division by zero.

Description An expression attempts to divide by zero.

Action Correct the expression to remove the division by zero.

54 ERROR: Shift value out of range.

Description The right operand in the shift operator is invalid. It must be in the range 0 <= right operand < 32.

Action Correct the right operand.



55 ERROR: Operator only applies to integers.

Description The specified operator applies only to operands of type integer.

Action Specify an integer operand.

56 ERROR: Operator not applicable to values of type ‘DataType’ .

Description The specified operator does not apply to operands of the specified type.

Action Specify an operand of the correct type.

57 ERROR: Unary operator ‘Name’ not allowed with operand of type ‘DataType’.

Description The specified unary operand does not support an operand of the specified type.

Action Correct the unary operand.

58 ERROR: Interface ‘Name’ not fully defined yet.

Description The specified interface has not been fully defined.

Action Move the definition of the interface so that the definition is completed before this reference.



59 ERROR: ‘ Name’ is not an interface.

Description An interface can only inherit from interfaces. The specified item is not an interface.

Action Correct the inheritance statement to specify only interfaces.

60 ERROR: Inheritance conflict: ‘Name’ inherited from both ‘ Base1’ and ‘Base2’.

Description An inheritance conflict has occurred. The specified element is inherited from two different base interfaces. References to base interface elements must be unambiguous.

Action Resolve the ambiguity by qualifying the element name with its interface name.

61 ERROR: Pointer types are not allowed.

Description Pointer types are not allowed in definitions.

Action Utilize a construct such as sequence.

62 ERROR: Union body is empty.

Description The union body contains no statements. It must contain at least one case.

Action Add a case to the body of the union statement.



63 ERROR: Missing case label.

Description A case label is required for each element in the union statement.

Action Add a case label to the union statement.

64 ERROR: Enum is empty.

Description The enum statement contains no identifiers. An enum statement must contain at least one identifier.

Action Add an identifier to the enum statement.

65 FATAL: Unexpected end of file.

Description During the parse of the definition file, the end of the file was reached before parsing was completed. This problem indicates an error in the definition file.

Action Correct the error and retry.

66 ERROR: Character literal is empty.

Description The character literal does not contain a character.

Action Add a character to the literal.



67 ERROR: Bad identifier name ‘Name’.

Description The specified identifier name is invalid (for example, illegal characters, starts with _, and so on). An identifier name consists of alphanumeric and underscore (_) characters. The first character must be an alphabetic character.

Action Verify the identifier name.

68 FATAL: Unexpected end of file inside of literal.

Description During the parse of the definition file, an unclosed literal resulted in a premature end of file.

Action Verify the definition file; close the literal.

69 FATAL: Unexpected end of line inside of literal.

Description During the parse of the definition file, an unclosed literal was found.

Action Verify the definition file; close the literal.

70 WARN: Identifier ‘ Name’ already referenced in this scope.

Description The specified identifier has already been referenced in this scope of the definition.

Action Verify the definition.



71 WARN: Identifier should be spelled ‘Name’.

Description An identifier for a definition must be spelled consistently (with respect to case) throughout a specification.

Action Correct the identifier spelling.

72 WARN: Module declarations are not allowed inside interfaces.

Description Module declarations are not allowed inside interface definitions. Module declarations are allowed only at the top level or inside other module definitions.

Action Move the module declaration.

73 WARN: Module is empty.

Description The module definition is empty. Modules usually contain other definitions, such as interfaces, typedefs, and so on.

Action Add definitions to the module.

74 WARN: Interface declarations are not allowed inside interfaces.

Description Interface declarations are not allowed inside other interface definitions. Interface declarations are allowed only at the top level or inside module definitions.

Action Move the interface declaration.



75 WARN: Operation declarations are only allowed inside interfaces.

Description Operation declarations are allowed only inside interfaces.

Action Move the operation declaration inside an interface definition.

87 ERROR: “Keyword should be spelled as ‘Name’ .

Description The OMG IDL file contains keywords that have the wrong case.

Action Find the keyword with the wrong case and correct it.

88 WARN: The float literal is invalid.

Description The specified literal is not a valid float literal.

Action Verify the definition file and correct the literal.

89 WARN: Unterminated character literal.

Description The specified character literal is not terminated by a closing quote.

Action Verify the definition file and close the character literal.

91 WARN: No argument found.

Description The specified keyword requires an argument, but none has been included.

Action Add the appropriate argument for this keyword or remove the keyword.



93 INFO: Duplicate definition of ‘ Name’ ignored.

Description The named definition occurs more than once.

Action Remove the duplicate definition.

94 WARN: Implementation declarations are not allowed inside implementations.

Description Implementation declarations are not allowed inside other implementation definitions. Implementation declarations are allowed only at the top level or inside module definitions.

Action Move the implementation declaration.

95 ERROR: ‘Name’ is not an implementation.

Description An implementation can inherit only from implementations. The specified item is not an implementation.

Action Correct the inheritance statement to specify only implementations.

96 WARN: Duplicate base implementation ‘Name’.

Description A base implementation is specified more than once in the inheritance list.

Action Remove the duplicate base implementation from the inheritance list.



97 ERROR: ‘ Name’ must be an interface.

Description The identifier specified in the interface list is not an interface.

Action Specify an interface.

98 ERROR: Bad argument type for argument ‘ArgumentName’ in operation ‘Name’.

Description For operations that generate client stubs, the argument type for the specified operation is not a supported WLE argument data type.

Action Specify a valid argument data type.

99 ERROR: Bad argument type for result in operation ‘Name’.

Description For GENERATE INTERFACE or IMPLEMENTATION, the return type for the specified operation or method is not a supported WLE return data type.

Action Specify a valid return data type.

100 ERROR: No interfaces found.

Description On a COMPILE operation, no interfaces were found for generating the specified files.

Action Include an interface in the definition file.



101 ERROR: Missing conditional expression.

Description In the definition file, a #if clause is not followed by a conditional expression.

Action Add a conditional expression to the #if clause.

102 ERROR: Missing right parenthesis.

Description A closing parethesis is missing from a conditional expression, an actual parameter list, or a parameter list.

Action Add a closing parenthesis.

103 ERROR: Syntax error in constant expression.

Description A constant expression contains a syntax error.

Action Verify the syntax of the expression.

104 ERROR: Missing colon for conditional expression.

Description A colon is missing from a conditional expression.

Action Add the colon between the arguments.



105 ERROR: Vertical whitespace within preprocessor directive.

Description A preprocessor directive contains vertical whitespace character(s).

Action Remove the vertical whitespace character(s).

106 ERROR: Constant value too large.

Description A constant value is too large.

Action Verify the value of the constant and adjust the value.

107 FATAL: Unexpected end of file before finish of preprocessor directive.

Description During the preprocessing on the definition file, the end of file was encountered before the preprocessor directive was finished.

Action Verify the definition file; finish the preprocessor directive.

108 ERROR: Illegal token on preprocessor directive line.

Description An illegal token was found on a preprocessor directive line.

Action Verify the preprocessor directive; remove the token.



109 ERROR: Missing parentheses for macro argument list.

Description The parentheses required for the macro argument list are missing from a macro definition.

Action Add parentheses to the argument list.

110 ERROR: Too few actual parameters in macro call.

Description A macro call contains too few actual parameters.

Action Add the parameters to the macro call.

111 ERROR: Too many actual parameters in macro call.

Description A macro call contains too many actual parameters.

Action Remove the additional parameters from the macro call.

112 ERROR: Argument is not an identifier.

Description A preprocessor directive or macro formal argument is not an identifier, or the argument is missing.

Action Verify the argument and correct it.



113 ERROR: Out of place directive ignored.

Description A preprocessor directive is out of place and has been ignored.

Action Remove the preprocessor directive.

114 ERROR: Missing argument in preprocessor directive.

Description An argument is missing from a preprocessor directive.

Action Add an argument to the directive.

115 ERROR: Unrecognized preprocessing directive.

Description An unrecognized preprocessor directive was specified.

Action Remove the preprocessor directive.

116 ERROR: Missing #endif directive.

Description An #endif directive was not found before the end of file.

Action Add the missing #endif directive.

117 ERROR: File does not end in unescaped newline.

Description A file must end in an unescaped newline.

Action Add the newline.



118 ERROR: Illegal header name.

Description A header name is illegally terminated, has an illegal form, or contains characters after the name.

Action Verify the header name and correct it.

119 ERROR: Missing macro name identifier.

Description The macro name identifier argument is missing from a define directive.

Action Add the macro name identifier.

120 ERROR: Macro name cannot be redefined or undefined.

Description System and predefined macros such as defined cannot be redefined or undefined by the user.

Action Choose a different macro name.

121 ERROR: Missing operand.

Description The WLE IDL preprocessor encountered a missing operand to the # or ## operators in a macro definition.

Action Add an operand.



122 ERROR: Non ANSI line directive.

Description This form of the line directive is not supported by the ANSI standard.

Action Correct the line directive.

123 ERROR: User defined error text: ‘ErrorText’.

Description This is the error text from a #error directive.

Action Verify the #error directive.

124 ERROR: Too many tokens in macro expansion.

Description There are too many tokens in the macro expansion.

Action Verify the macro.

125 ERROR: Formal parameter definition is not unique.

Description The definition of the formal parameter is not unique.

Action Change the name of the formal parameter.

126 INFO: The macro has been redefined. The redefinition is now in effect.

Description A macro has been redefined. The new definition will be used instead of the original definition.

Action Remove the original definition of the macro.



127 ERROR: Invalid proxy wildcard.

Description This combination of Remote User, Remote Host, and Local Username is not supported.

Action Remove the wildcard specification for the Remote Host or Local Username.

128 ERROR: No typecode repository id.

Description The typecode is an anonymous type and contains no repository ID. This is an internal error only.


130 INFO: Object ‘ObjectName’ is not in the IDL file. Please remove the #pragma from the IDL file.

Description A UUID was found for an object that does not exist.

Action Remove the #pragma from the OMG IDL file.

131 INFO: ‘Name’ is a non-standard context property.

Description This context property is not a standard CORBA context. A standard context property is a sequence of alphanumeric, ’.’, ’_’, and ’*’ characters. The first character must be an alphabetic character. An asterisk may be used only as the last character of the string. WLE context property names can contain the additional ’&’, ’-’, ’@’, ’:’ characters. In addition, the first character does not have to be alphabetic.

Action Correct the context property if standard CORBA context property names are desired.



132 INFO: ‘Name’ cannot be both a module and an interface; compilation errors will occur.

Description A module name and an interface name are the same. Compilation errors will occur in the C++ stubs.

Action This is an informational message; no action is necessary.

133 INFO: ‘Name’ cannot be the same as its container; compilation errors will occur.

Description A type name and its container name are the same. Compilation errors will occur in the C++ stubs.


134 ERROR: ‘DataType’ data type not yet supported in this context.

Description The data type specified is not supported by the WLE product in this context.

Action Specify a supported WLE data type.

135 INFO: The long name option or qualifier was ignored.

Description C++ does not require the use of options or qualifiers to handle long names. There is no ANSI standard for routine name length in C++, so this option was ignored, and the long name was generated. The limit for the length is restricted only by the compiler.




136 ERROR: Invalid Protocol Type Name.

Description The protocol type specified is invalid.

Action Specify a valid protocol type value.

137 ERROR: An error occurred while creating a TypeCode.

Description The TypeCode could not be created due to an error.

Action See any associated error messages.

138 ERROR: This statement requires the IOP protocol.

Description This statement requires that the IOP protocol be specified when OMG IDL files are loaded or compiled.

Action Ensure that you have specified the IOP protocol option or qualifier when loading the repository or compiling OMG IDL files.

139 WARNING: The transaction policy for ‘ interface’ is inconsistent with its inheritance.

Description The transaction policy inherited by the interface is inconsistent with the transaction policy specified for the implementation in the ICF file. This can occur when an interface inherits from the interface CosTransactions::TransactionalObject, but is implemented with a transaction policy of ignore or never.

Action Determine whether the interface is transactional, and modify the ICF file associated with the OMG IDL file to appropriately update the transaction policy of its implementation. Alternatively, define an alternate, nontransactional inheritance for the interface.

Note that the stubs and skeletons generated from the OMG IDL and ICF files will support nontransactional requests; however, because of the transaction policy of ignore or never, errors could occur if transactional requests are attempted.


CHAPTER

6 IIOP Server Listener/Handler Messages

IIOP Server Listener/Handler Messages 1000-1099

Note: When IIOP Listener/Handler messages are listed in the user log (ULOG), the messages have the prefix ISNAT_CAT. For example, message 1101 is listed as ISNAT_CAT:1101.

1001 ERROR: Unused arguments passed to buildish.

Description The command-line option passed to the buildish command is not recognized as a valid option. An extra hyphen (-) in the command line also might cause this error.

Action Examine the command line that calls buildish and remove the extra option.

System Messages 6-1

6 IIOP SERVER LISTENER/HANDLER MESSAGES

1002 ERROR: Unable to execute the command command_string.

Description While the C compilation system was being invoked to build a new IIOP Server Handler, an error was detected.

This error could happen for one of the following reasons:

t The C compilation system command was not found.

t The CC command returned an error while linking the new IIOP Server Handler.

t The $CC environmental variable was not set correctly.

t The $CFLAGS environmental variable has invalid options.

Action Make sure the C compilation system is present on your machine. Make sure there is enough disk space available for the new IIOP Server Handler. The amount of disk space should be roughly the same as the existing IIOP Server Handler and the added object files. Examine the $CC and $CFLAGS variables and, if these variables are set, make sure the options are correct for your C compilation environment.

1003 ERROR: Could not find buffer type type_val: subtype subtype_val information.

Description This error occurs when the IIOP Server Handler receives a message from either a server application or a client application, and it cannot find the buffer type information for the buffer type of the message.

Action The error indicates an internal problem with the IIOP Server Handler. Contact BEA Customer Support.

6-2 System Messages

IIOP SERVER LISTENER/HANDLER MESSAGES 1000-1099

1004 ERROR: Memory allocation failure.

Description An attempt to allocate memory dynamically from the operating system using malloc failed.

Action Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine. Increase the space on the swap device.

See Also See the malloc function.

For UNIX systems, see the malloc(3) manual page.

For Microsoft Windows NT systems, see the Microsoft Visual C++ online help.

1008 ERROR: Could not establish listening address on network string.

Description This error occurs if the IIOP Server Listener cannot advertise its listening address on the network.

This error could happen for one of the following reasons:

t The format of the address supplied to the IIOP Server Listener is incorrect. If the address format is incorrect, the network provider will be unable to advertise the address and the request fails.

t The address used in the -n command-line option to the IIOP Server Listener is already in use by another process. For TCP/IP, this condition can be verified by using the netstat command.

t A previously used address has not completed the close sequence. This condition occurs if either the IIOP Server Listener or the IIOP Server Handler were killed in an abortive manner, such as kill-9. Some transports (among them, TCP/IP) keep the connection open for an implementation-dependent amount of time to flush the existing data on the buffered network connection.

System Messages 6-3


Action To correct the problem, match one of the following solutions with the previous problem descriptions:

t Check the address format. For TCP/IP, the address must be specified in either of the following two formats:

//hostname:port_number""//#.#.#.#:port_number"

The #.#.#.# is in dotted decimal format. In dotted decimal format, each # should be a number from 0 to 255.

t See whether other processes are using the requested network address. For TCP/IP, use the netstat command and, if the address is already in use, select a different address.

t If the system is out of network addresses, ask the system administrator to increase the number of addresses.

t If the connection is not closed yet, wait a few minutes and try again.




1009 ERROR: Cannot decode header of the received message.

Description Either the IIOP Server Handler or the IIOP Server Listener read the data from the network. Each message has a header at the top of the message. If the message is corrupted or is smaller that the expected header, this error occurs.


6-4 System Messages


1010 ERROR: Couldn’t convert buffer to current release format.

Description This error occurs if an WLE remote client application and the native UNIX system machine have different WLE releases and the message is from an older release. The error can also occur if the message received by either the IIOP Server Handler or the IIOP Server Listener is corrupted.


1011 ERROR: Couldn’t convert buffer to native site format.

Description The IIOP Server Handler cannot convert a message from a client application format to the native format. This indicates that the buffer type is unknown to the IIOP Server Handler .

Action Check the user log for a message indicating the nature of the failure (in particular, the type and subtype of the buffer that could not be converted).

1012 ERROR: Received message with an unknown internal type index indexval.

Description While processing a message from the client application, the system indicates that the internal buffer type is unknown.

Action Because the buffer type is set during the conversion to the native format, this error should not occur. Contact BEA Technical Support.

System Messages 6-5


1013 ERROR: Received message of unknown type ’typeval’ subtype ‘subtypeval’.

Description While processing a message from the client application, the system indicates that the application buffer type and subtype are unknown.

Action Because the buffer type is set during conversion to the native format, this error should not occur. Contact BEA Technical Support.

1014 ERROR: Received message of unknown type ‘type’.

Description While processing a message from the client application, the system indicates that the application buffer type is unknown.

Action Because the buffer type is set during conversion to the native format, this error should rarely occur. Contact BEA Technical Support.

1015 ERROR: Message decode failure.

Description Decoding of the message received from the client application by the encdec function for the buffer type failed.

Action Check the user log for additional messages that indicate why the decoding failed. Contact BEA Technical Support.

See Also The typesw(5) command. For information about the typesw(5) command, see the BEA TUXEDO Reference Manual.

6-6 System Messages


1016 ERROR: Post receive operation on message failed.

Description Postprocessing of the message received from the client application by the postsend function for the buffer type failed.

Action Check the user log for additional messages that indicate why the postprocessing failed. Contact BEA Technical Support.


1017 ERROR: Message presend routine failed.

Description Preprocessing of the message being sent to the client application by the presend function for the buffer type failed.

Action Check the user log for additional messages that indicate why the preprocessing failed. Contact BEA Technical Support.


1018 ERROR: Invalid data length of 0, data not self describing.

Description Preprocessing of the message being sent to the client application by the presend function for the buffer type returned 0. This error indicates that a message length of 0 was presented by the application and that the buffer type is not self-describing, such that the presend function cannot infer the desired transfer length.

Action The application must provide a length for sending messages of the particular buffer type.

See Also The TUXEDO typesw(5) command. For information about the typesw(5) command, see the BEA TUXEDO Reference Manual.

System Messages 6-7


1019 ERROR: Message conversion to client format failed.

Description The IIOP Server Handler cannot convert a message from native format to client application format.

Action This error should not occur. Contact BEA Technical Support.

1023 WARN: No client context space available in handler.

Description While setting up a connection for a new client application, the IIOP Server Handler ran out of space to keep context for client applications.

Action This error should occur rarely because the IIOP Server Listener transfers control of client application connections to IIOP Server Handler programs based on their current degree of multiplexing. Contact BEA Technical Support.

See Also For information about the ISL command, see the Administration Guide and, in particular, the discussion of the CLOPT parameter.







6-8 System Messages


1025 ERROR: Expected numeric argument to -x option.

Description An invalid argument was passed to the ISL command-line option. The argument to the -x option, the degree of multiplexing, needs to be numeric. This error causes the IIOP Server Listener not to be booted.

Action Make sure the argument to the -x option is numeric.

See Also The ISL command. For information about the ISL command, see the Administration Guide.

1026 ERROR: Handler received unexpected message.

Description The IIOP Server Handler received a message without a client application context (that is, a message intended for the IIOP Server Handler) that is not in the correct format. It is not a WLE message.

Action The message is ignored. Contact BEA Technical Support.

1027 ERROR: Handler received unexpected opcode 0xcode.

Description The IIOP Server Handler received a message without a client application context (that is, a message intended for the IIOP Server Handler) that has an unrecognized operation code. This message is normally a shutdown message from the IIOP Server Listener.

Action The message is ignored. Contact BEA Technical Support.

System Messages 6-9


1028 WARN: Couldn’t change to client context context_number, continuing.

Description The IIOP Server Handler encountered an error while it was switching to the context of a client application when the IIOP Server Handler was dropping all connections during shutdown.

Action The connection is ignored. Contact BEA Technical Support.

1029 ERROR: Sending of reply message to client failed.

Description While a reply message was being sent to a client application, the operation failed.

Action Check the user log for messages that indicate the nature of the failure. This warning may indicate that the client application is no longer accessible (that is, either the network or the machine has failed). Contact BEA Technical Support.

1030 INFO: IIOP Handler joining application.

Description The IIOP Server Listener started an IIOP Server Handler process based on the command-line options for the listener and the current demand by clients.

Action None.

See Also For information about ISL command, see the Administration Guide and, in particular, the discussion of the CLOPT parameter.



1031 ERROR: Invalid command line argument ‘arg’ ignored.

Description An illegal command-line option was found in the command-line options for the IIOP Server Handler.

This error is rare because the IIOP Server Listener, not the system administrator, starts the IIOP Server Handler.

















1034 ERROR: Failed to attach to shared memory for listener table, errno = errno_val.

Description The IIOP Server Handler failed to attach a shared memory segment.

Action This is an operating system error. Check the value of errno_val for an indication of the problem. Contact BEA Technical Support.

1035 ERROR: Handler table entry already occupied by pid.

Description The IIOP Server Listener started an IIOP Server Handler and assigned it a slot that is already occupied by another IIOP Server Handler process that has the process identifier pid.


See Also For information about the ISL command, see the Administration Guide and, in particular, the discussion of the CLOPT parameter.



1036 ERROR: Network provider returns a zero length network address, can’t establish network address.

Description The length of the network address that the IIOP Server Handler is using to establish a connection is 0. This is invalid (and should not occur).


1037 ERROR: Can’t synchronize with IIOP listener... continuing.

Description The forked IIOP Server Handler process lost the connection between the IIOP Server Listener and the IIOP Server Handler that it is executing. The pipe with IIOP Server Listener may have been lost because the IIOP Server Listener process is being stopped.

Action No action is required. However, the cause of the IIOP Server Listener disconnection should be investigated if the cause is not known.


1038 WARN: Couldn’t change to client context index, continuing.

Description The IIOP Server Handler encountered an error while it was switching to the context of a client application when the IIOP Server Handler was dropping all connections during shutdown.




1039 WARN: Can’t use TPGETANY flag with tpcall().

Description The client application called tpcall() with the TPGETANY option. This option is not valid, and TPEINVAL is returned to the application.

Action This error should not occur. Contact BEA Technical Support.

1040 WARN: tpsprio() call failed, tperrno = tperrno_val.

Description A call to tpsprio in the IIOP Server Handler on behalf of the client application failed with tperrno set to tperrno_val.

Action None.

See Also The tpsprio(3c) command. For information about the tpsprio(3c) command, see the BEA TUXEDO Reference Manual.









1042 ERROR: tpcall() call failed, tperrno = tperrno_val.

Description A call to tpcall in the IIOP Server Handler on behalf of the client application failed with tperrno set to tperrno_val.

Action None.

See Also The tpcall(3c) command. For information about the tpcall(3c) command, see the BEA TUXEDO Reference Manual.

1043 ERROR: tpacall() call failed, tperrno = tperrno_val.

Description A call to tpacall in the IIOP Server Handler on behalf of the client application failed with tperrno set to tperrno_val.

Action None.

See Also The tpacall(3c) command. For information about the tpacall(3c) command, see the BEA TUXEDO Reference Manual.

1044 ERROR: tpgprio() call failed, tperrno = tperrno_val.

Description A call to tpgprio in the IIOP Server Handler on behalf of the client application failed with tperrno set to tperrno_val.

Action None.

See Also The buildish(1) command. For information about the buildish(1) command, see the BEA TUXEDO Reference Manual.



1045 ERROR: Sending of reply to tpacall() call to client failed.

Description An attempt to send an acknowledgment of a tpacall request to the WLE remote client application failed.

This failure indicates a problem with the network, with the IIOP Server Listener/Handler, or with the WLE remote client application process.


1046 ERROR: Sending of reply to tpinit() call to client failed.

Description An attempt to send an acknowledgment of a tpinit request to the WLE remote client application failed.



1047 ERROR: Sending of reply to tpterm() call to client failed.

Description An attempt to send an acknowledgment of a tpterm request to the WLE remote client application failed.





1048 ERROR: Sending of error reply to call client failed.

Description An attempt to send an acknowledgment message to the WLE remote client application has failed.



1049 ERROR: Couldn’t create buffer for receiving messages.

Description An attempt to create a buffer with tpalloc failed. This buffer is used to receive messages.

This error indicates either a resource problem or an internal problem with the IIOP Server Handler.

Action If there is insufficient memory to allocate buffers, the IIOP Server Handler process cannot operate. Contact BEA Technical Support.

If machine resources are sufficient, there is an internal problem with the IIOP Server Handler. In this case, contact BEA Technical Support.

1050 ERROR: Error switching to the handler’s context.

Description The IIOP Server Handler was attempting to switch from a client application context to the IIOP Server Handler context when it experienced an error.

Action The error indicates an internal problem with the IIOP Server Handler. Contact BEA Technical Support.



1052 ERROR: Failed to process network event.

Description The IIOP Server Handler was unable to process a network event using tmnwevent.

Action The error indicates an internal problem with the IIOP Server Handler software. Contact BEA Technical Support.

1053 ERROR: Error polling network connections.

Description The IIOP Server Handler encountered an error polling a network connection using tmnwcpoll.

Action The error indicates a network error. Check that the network connection to the WLE remote client application has not gone down. If the network connection has gone down, the WLE remote client application has to rejoin the application. Contact BEA Technical Support.

1054 ERROR: Error generating network event list.

Description The IIOP Server Handler encountered an error when polling a network connection using tmnwcpoll.

Action The error indicates a network error. Check that the network connection to the WLE remote client application has not gone down. If the network connection has gone down, the WLE remote client application has to rejoin the application. Contact BEA Technical Support.



1055 ERROR: Connection to unassigned ISH rejected.

Description The connection for the client application was timed out.

Action This situation may occur if the system or the network is very busy, or if the network has gone down. The client application should try again to join the application.

1056 WARN: Couldn’t change to client context index, continuing.

Description The IIOP Server Handler encountered an error when switching to the context of a client application to do a tpterm.

Action This error indicates an internal problem. Contact BEA Technical Support.

1057 ERROR: Error processing message received from network.

Description The IIOP Server Handler encountered an error when receiving a message from the network.

Action This error could indicate a network problem or an internal BEA problem. Contact BEA Technical Support.

1058 ERROR: Received message with opcode other than init for non-existent context.

Description The IIOP Server Handler has received a message from a process that has not joined the application.

Action This message indicates an internal problem in communication between the IIOP Server Handler and the WLE remote client application. Contact BEA Technical Support.



1059 ERROR: Received network message with unknown context.

Description The IIOP Server Handler has received a message from an unknown process.


1060 ERROR: Received message with context associated with a different connection.

Description The IIOP Server Handler, working on behalf of one client application context, has received a message intended for a different client application context.


1061 ERROR: Received a reply message from a client.

Description The IIOP Server Handler has received from an WLE remote client application a message that contains the reply protocol.

Action A WLE remote client application should never send a message with this protocol. This situation indicates an internal problem in communication between the IIOP Server Handler and the WLE remote client application. Contact BEA Technical Support.



1062 ERROR: Sending of reply to tpbegin() call to client failed.

Description An attempt to send an acknowledgment of a tpbegin request to the WLE remote client application has failed.

Action This is an internal message. This failure indicates a problem with the network, with the IIOP Server Listener/Handler, or with the WLE remote client application process. Contact BEA Technical Support.

1063 ERROR: No more IIOP handlers available.

Description An attempt to start a new IIOP Server Handler process has failed because the maximum limit of IIOP Server Handlers has already been reached.

Action The maximum number of IIOP Server Handlers specified in the configuration file have been started. To increase this number, the CLOPT -M maxh value must be changed. This can be done in one of two ways:

t Shut down the application, change the configuration file, and reboot the application.

t Change the value dynamically with tmconfig (1), and shut down and reboot only the IIOP Server Listener.

1064 ERROR: Error formatting command line options for handler.

Description An error was encountered while the argument string needed for booting an IIOP Server Handler was being formatted.

Action This message occurs if there are more than 256 characters in the CLOPT string in the configuration file.

See Also ISL command and servopts(5). For information about the ISL command, see the Administration Guide and, in particular, the discussion of the CLOPT parameter. For information about servopts(5), see the BEA TUXEDO Reference Manual.



1065 ERROR: Error retrieving machine table entry of the listener.

Description An error was encountered while an IIOP Server Handler was trying to get internal machine information during an IIOP Server Handler boot process.


1066 ERROR: IIOP Handler died, attempting restart.

Description If an IIOP Server Handler process has died and the number of IIOP Server Handler processes booted is below the minimum number specified in the configuration file, the BEA WLE system attempts to boot a new IIOP Server Handler.

Action IIOP Server Handlers should not die. If IIOP Server Handlers do die, it could indicate an internal problem that requires attention. Additional IIOP Server Handlers may need to be booted, if the system is very busy.

1067 ERROR: IIOP Handler died, cleaning up.

Description An IIOP Server Handler process has died and the number of IIOP Server Handler processes booted is below the minimum number specified in the configuration file. An attempt to boot a new IIOP Server Handler has failed.

Action This could either be an operating system error or an internal WLE error. In the former case, contact your system administrator. In the latter case, contact BEA Technical Support.



1068 ERROR: Invalid command line argument ‘arg’ ignored.

Description An illegal command-line option was found in the CLOPT string.

Action Examine the command line and remove the invalid option.

See Also ISL command and servopts(5). For information about the ISL command, see the Administration Guide and, in particular, the discussion of the CLOPT parameter. For information about servopts(5), see the BEA TUXEDO Reference Manual.

1069 ERROR: Sending of reply to tpbroadcast() or tpnotify() call to client failed.

Description An attempt to send an acknowledgment of a tpbroadcast or tpnotify request to the WLE remote client application has failed.


1070 ERROR: Cannot boot ISL with MAXWSCLIENTS for machine set to 0.

Description The IIOP Server Listener process has failed to boot because the MAXWSCLIENTS parameter was not specified in the configuration file.

Action The MAXWSCLIENTS parameter must be specified either in the RESOURCES section or in the MACHINES section of the configuration file.




Description The IIOP Server Listener failed to create a buffer for storing IIOP Server Handler information.






Description The IIOP Server Listener failed to create a buffer for storing a device name.






Description The IIOP Server Listener failed to create a buffer for storing an IIOP Server Handler’s name.








Description The IIOP Server Listener failed to create a buffer for storing a network address.





1075 ERROR: Can’t get machine entry for listener.

Description The IIOP Server Listener encountered an error when attempting to read the MACHINES entry from the configuration file.

Action Make sure the TUXCONFIG file has not been removed or corrupted. If the TUXCONFIG file is all right, contact BEA Technical Support.



1076 ERROR: Failed to create to shared memory for listener table, errno = errno_val.

Description The IIOP Server Listener failed to create a shared memory segment.


See Also The Uunix_err(3c) command. For information about the Uunix_err(3c) command, see the BEA TUXEDO Reference Manual.

1077 ERROR: Failed to update server table entry, tperrno = tperrno_val.

Description The IIOP Server Listener failed to update the Bulletin Board.

Action Check that the shared memory segment that contains the Bulletin Board has not been removed. If this segment has been removed, the application needs to be rebooted. Otherwise, this error indicates an internal error and you should contact BEA Technical Support.

See Also The tperrno(5) command. For information about the tperrno(5) command, see the BEA TUXEDO Reference Manual.

1078 ERROR: Failed to attach to shared memory for listener table, errno = errno_val.

Description The IIOP Server Listener failed to attach a shared memory segment.





1079 ERROR: Error starting minimum number of handlers.

Description The IIOP Server Listener encountered an error when attempting to boot the minimum number of IIOP Server Handlers.

Action This could be an operating system error. Perhaps there are too many processes running. This could also be an internal error. Check the log file for other messages relating to this message. Contact BEA Technical Support.

1080 ERROR: Error polling network connections.

Description The IIOP Server Listener encountered an error when polling a network connection.

Action This error indicates a network error. Check with your system administrator to see whether the network is down. If the network is all right, contact BEA Technical Support.

1082 ERROR: Error adding connection request to event list.

Description The IIOP Server Listener was unable to allocate space on the event list.

Action This error indicates a resource problem. If there is insufficient memory to allocate buffers, the IIOP Server Listener process cannot operate. Contact BEA Technical Support.

1083 ERROR: Error assigning connection request, can’t create any more handlers.



Description The IIOP Server Listener was unable to start a new Handler.

Action The most likely problem is that the maximum number of IIOP Server Handlers specified in the configuration file have been started. To increase this number, the CLOPT -M maxh value must be changed. This can be done in one of two ways:

t Shut down the application, change the configuration file, and reboot the application.

t Change the value dynamically with tmconfig(1), and shut down and reboot only the IIOP Server Listener.

Another source of the problem could be that the number of processes allowable by a user (ulimit) has been reached. If the ulimit has been reached, consult with your system administrator to increase this limit.

1086 ERROR: Message conversion to release rel format failed.

Description The IIOP Server Listener/Handler was unable to change the release structure to 4.2.


1088 ERROR: tpinit() failed, tperrno = tperrno_val.

Description The tpinit(3c) function call used to connect a client application to a WLE server application has failed. Further information about the cause of the failure is provided by the value of tperrno. By examining the <atmi.h> header file, this numeric tperrno value may be converted to a symbolic value. Potential causes of each such symbolic value are listed for the tpinit(3c) command.

Action For causes of the specific tperrno value that was reported to the application, see the tpinit(3c) command in the BEA TUXEDO Reference Manual. Eliminate the potential causes of such an error and retry the failed operation. Contact BEA Technical Support.

See Also The tpinit(3c) and tperrno(5) commands. For information about these commands, see the BEA TUXEDO Reference Manual.



1089 ERROR: tpscmt() failed, tperrno = tperrno_val.

Description While attempting to commit a transaction on behalf of a client application, the IIOP Server Handler process was unable to set the transaction commit control characteristic for the transaction to TP_CMT_LOGGED. For this reason, the attempt to commit the transaction failed. For further information about the transaction commit control characteristic, refer to the tpscmt (3c) command in the BEA TUXEDO Reference Manual.

Action Because the transaction cannot be committed, the user must abort the transaction. The value of tperrno and immediately preceding messages in the user log may provide further information as to the cause of the error.

See Also The tpabort (3c), tpcommit (3c), tpscmt (3c), and tperrno (5) commands. For information about these commands, see the BEA TUXEDO Reference Manual.

1090 ERROR: tpscmt() failed, tperrno = tperrno_val.

Description While attempting to commit a transaction on behalf of a client application, the IIOP Server Handler process was unable to set the transaction commit control characteristic for the transaction to TP_CMT_COMPLETE. For this reason, the attempt to commit the transaction failed. For further information about the transaction commit control characteristic, refer to the tpscmt(3c) command in the BEA TUXEDO Reference Manual.

Action Because the transaction cannot be committed, the user must abort the transaction. The value of tperrno and immediately preceding messages in the user log may provide further information as to the cause of the error.

See Also The tpabort (3c), tpcommit (3c), tpscmt (3c), and tperrno (5) commands. For information about these commands, see the BEA TUXEDO Reference Manual.



1096 ERROR: Sending of reply to tpcommit() call to client failed.

Description An attempt to send an acknowledgment of a tpcommit request to the WLE remote client application has failed.


1097 ERROR: Sending of reply to tpabort() call to client failed.

Description An attempt to send an acknowledgment of a tpabort request to the WLE remote client application has failed.


1099 ERROR: Could not find correct number of active handlers, found num1, expected num2.

Description While being restarted after the death of a previous IIOP Server Listener process, the IIOP Server Listener found an inconsistency in the existing specific shared memory regarding the number of IIOP Server Handler processes. The IIOP Server Listener attempts to shut down any associated IIOP Server Handler processes that it knows about, removes the inconsistent shared memory, and exits.

Action The system administrator should check for any stray IIOP Server Handler processes associated with this particular IIOP Server Listener, and see that they are manually terminated. The system administrator may then reboot the IIOP Server Listener process.




Note: When IIOP Server Listener/Handler messages are listed in the user log (ULOG), the messages have the prefix ISNAT_CAT. For example, message 1100 is listed as ISNAT_CAT:1100

1100 ERROR: -n option is required.

Description The IIOP Server Listener process was invoked without the -n option. This parameter contains the well-known network address used by the IIOP Server Listener, and is required. The IIOP Server Listener process is exiting due to the absence of a required option.

Action Examine the configuration file and determine the change that needs to be made to the CLOPT argument for the IIOP Server Listener process. The -n option must occur, must have an appropriate option argument, and must be located after the double dash (--) that separates WLE options from ISL specific options. The options for a server may be updated while the system is running through use of the tmconfig (1) command, or while the system is shut down by reloading the configuration file through use of tmloadcf (1).

See Also The tmconfig (1) and tmloadcf (1) commands and the ISL command.

For information about the tmconfig (1) and tmloadcf (1) commands, see the BEA TUXEDO Reference Manual.

For information about the ISL command, see the Administration Guide.

1103 ERROR: Bad -m option.



Description The IIOP Server Listener process was invoked with an -m option that specified an option argument outside the allowed range. The -m option specifies the minimum number of handlers that should be available at any given time in conjunction with this IIOP Server Listener. The legal range is between 0 and 255. The IIOP Server Listener process is exiting due to an error in its arguments.

Action Change the value for the ISL command -m option so that it is within the legal range. The options for a server may be updated while the system is running through use of the tmconfig (1) command, or while the system is shut down by reloading the configuration file through use of tmloadcf (1).

See Also The tmconfig (1), tmloadcf (1), and ubbconfig (5) commands and the ISL command.

For information about the tmconfig (1), tmloadcf (1), and ubbconfig (5) commands, see the BEA TUXEDO Reference Manual.


1104 ERROR: Bad -x option.

Description The IIOP Server Listener process was invoked with an -x option that specified an option argument outside the allowed range. The -x option specifies the degree of multiplexing desired within each IIOP Server Handler. The legal range is between 1 and 32767. The IIOP Server Listener process is exiting due to an error in its arguments.

Action Change the value for the ISL command -x option so that it is within the legal range. The options for a server may be updated while the system is running through use of the tmconfig (1) command, or while the system is shut down by reloading the configuration file through use of tmloadcf (1).



See Also The tmconfig (1), tmloadcf (1), and ubbconfig (5) commands and the ISL command.



1105 ERROR: Bad -M option.

Description The IIOP Server Listener process was invoked with an ISL command -M option that specified an option argument outside the allowed range. The -M option specifies the maximum number of handlers that should be available at any given time in conjunction with this IIOP Server Listener. The legal range is between 1 and 32767. The IIOP Server Listener process is exiting due to an error in its arguments.

Action Change the value for the ISL command -M option so that it is within the legal range. The options for a server may be updated while the system is running through use of the tmconfig (1) command, or while the system is shut down by reloading the configuration file through use of tmloadcf (1).

See Also The tmconfig (1), tmloadcf (1), and ubbconfig (5) commands and the command.



1106 ERROR: Error receiving unsolicited message, tperrno = tperrno_val.

Description The IIOP Server Handler process experienced an error while receiving an unsolicited message. The numeric value of tperrno is also printed; this value can aid in determining the exact cause of the problem. You can convert a numeric value of tperrno to a symbolic value by looking in the <atmi.h> header file. In most cases, there is also a preceding message in the user log that gives further information as to the cause of the error.



Action Examine the user log for any immediately preceding messages giving further information as to the cause of the error. Also examine the user log on the site that sent the failed unsolicited message for further clues as to the cause of the error. Contact BEA Technical Support.


1107 ERROR: Error receiving messages, tperrno = TPEOS, Uunixerr = UMSGRCV.

Description The UNIX system msgrcv system call returned an error to the IIOP Server Handler process. A prior message in the user log provides more information as to the cause of the error.

Action Examine the prior message in the user log to determine the specific UNIX system error associated with this msgrcv failure. If the failure is not transient and the IIOP Server Handler is still active, the IIOP Server Listener may need to restart this particular IIOP Server Handler. Contact BEA Technical Support.

See Also The tperrno (5) and Uunix_err (3c) commands. For information about these commands, see the BEA TUXEDO Reference Manual.

1108 ERROR: Handler received unexpected unsolicited opcode opcode_value.

Description The IIOP Server Handler process received an unsolicited message that contained an unexpected internal opcode. The opcode value is printed as part of the error message.


1109 ERROR: Failed to process broadcast message.



Description The IIOP Server Handler process received a broadcast message to be forwarded to the appropriate client application(s). However, it was unable to process this message for forwarding to the client application(s).

Action A previous message in the user log may indicate a more precise cause of the error and may indicate a corrective action. The client applications associated with this IIOP Server Handler did not receive the broadcast message sent to them. Depending on the particular situation, these client applications may need to be informed of the broadcast in another way. Contact BEA Technical Support.

1110 ERROR: Couldn’t change to client context context_number, continuing.

Description The IIOP Server Handler encountered an error when switching to the context of a client application when dropping all connections during shutdown.


1111 ERROR: Sending of broadcast message to client failed.

Description The IIOP Server Handler process received a broadcast message to be forwarded to the appropriate client application(s). However, it was unable to process this message for forwarding to one of the client applications. Often, this error is due to a network error.

Action Use network management utilities to determine whether any networking problems exist between the machine on which the IIOP Server Handler process is running and its associated client application. Also, examine the user log to see whether any immediately preceding entries give a more detailed explanation for the error. Contact BEA Technical Support.



1112 ERROR: Failed to process notification message.

Description The IIOP Server Handler process received a notification message to be forwarded to a client application. However, it was unable to process this message for forwarding to the client application.

Action If a prior message in the user log provides further explanation for the cause of the problem, follow the recommendations listed for that message. Otherwise, contact BEA Technical Support.

1113 ERROR: Couldn’t change to client context context_number, continuing.

Description The IIOP Server Handler encountered an error switching to the context of a client application when dropping all connections during shutdown.


1114 ERROR: Sending of notification message to client failed.

Description The IIOP Server Handler process received a notification message to be forwarded to a client application. However, it was unable to process this message for forwarding to the client application. Often, this error is due to a network error.

Action Use network management utilities to determine whether any networking problems exist between the machine on which the IIOP Server Handler process is running and its associated client application. Also, examine the user log to see whether any immediately preceding entries give a more detailed explanation for the error. Contact BEA Technical Support.



ify t d,

1120 ERROR: tpchkauth() failed, tperrno = tperrno_val.

Description As part of its startup processing, the IIOP Server Handler process attempted to determine whether application authentication is required by this application configuration, but encountered an error while trying to obtain this information. A numeric value of tperrno is printed as part of the error message; you can convert this value to a symbolic value by examining <atmi.h>.

Action Examine the user log for a prior message indicating a more exact cause of the error. Contact BEA Technical Support.

See Also The tperrno (5) command. For information about this command, see the BEA TUXEDO Reference Manual.

1121 ERROR: Couldn’t get administrative key for decrypting client messages.

Description The process was unable to access the encoded form of the password used to create the encryption/decryption schedule employed between the IIOP Server Handler and client applications.

Action Verify that the process is running under the system administrator’s ID. Also, verthat the file $APPDIR/.adm/.keydb has not been accidentally removed and thathe TUXCONFIG file has not been corrupted. If either of these two files is corrupteyou need to reload the TUXCONFIG file. Contact BEA Technical Support.

1122 ERROR: Restoring message to original condition after sending failed.



Description Either the IIOP Server Listener or the IIOP Server Handler process sent an encrypted message to a client application. After the send, the IIOP Server Listener or IIOP Server Handler tried to restore the message to its original unencrypted state, but the operation failed.


1124 ERROR: Broadcast message received with unknown type ‘type_name’ subtype ‘ subtype_name’.

Description The IIOP Server Handler process received a notification or broadcast message from a node with an unknown type.


1131 ERROR: tpbroadcast() or tpnotify() failed on send, tperrno = tperrno.

Description The IIOP Server Handler that performs the tpbroadcast or tpbroadcast call on behalf of the client applications failed to forward the broadcast message to the (D)BBL administrative server. The message is to be sent to the DBBL administrative server in MP mode and to the BBL administrative server in SHM mode, which, in turn, takes care of broadcasting the unsolicited message to the target client applications.

Action Check the error number, tperrno, and determine why the IIOP Server Handler was not able to send the message. Most likely the (D)BBL administrative server queue is full. In this case, change the operating system tunable parameters to increase the maximum queue size. If tperrno is set to TPESYSTEM or TPEOS, check the user log for other error messages that may indicate the exact nature of the problem and the reason for this failure. Contact BEA Technical Support.



See Also The tpbroadcast (3c), tperrno (5), and ubbconfig (5) commands. For information about these commands, see the BEA TUXEDO Reference Manual.

1132 ERROR: Received message of type ‘type’ to tpinit() call.

Description The IIOP Server Handler that performs the tpinit call on behalf of client applications received a request to join a client application to the WLE server application. However, the message it received in conjunction with the request was not a TPINIT buffer, but of type type. The IIOP Server Handler, therefore, removes the client application context from the IIOP Server Handler and returns an error.


1133 ERROR: TPINIT information must be passed to tpinit() call in secure application.

Description Prior to performing a tpinit on behalf of a client application, the IIOP Server Handler must make sure a TPINIT structure is passed if the application requires client application authentication. This error indicates that the TPINIT information was not passed, even though client application authentication is required. The IIOP Server Handler, therefore, unregisters the client application from the Bulletin Board, removes the client application context from the IIOP Server Handler, and returns an error. An error message, with tperrno set to TPEPERM, is sent back to the client application.




1134 ERROR: Sending of reply to ticket protocol failed.

Description The IIOP Server Handler failed to send the ticket reply back to the client application. The IIOP Server Handler, therefore, unregisters the client application from the Bulletin Board, removes the client application context from the IIOP Server Handler, and returns an error.

Action Check the user log for other error messages that may indicate the exact nature of the problem and the reason for this failure. Contact BEA Technical Support.

1135 ERROR: Invalid client name given ‘cltname’.

Description While a client application’s request to join the application was being processed, an invalid client application name, cltname, was found in the TPINIT buffer. The value sysclient is reserved by the system for the cltname field.


1136 WARN: Invalid notification option given 0xoption, reset to TPU_IGN.

Description While a client application’s request to join the application was being processed, an invalid notification option option was found in the TPINIT buffer flags field. For client application notification, the possible values for flags are as follows: TPU_SIG, TPU_DIP, or TPU_IGN.




1137 ERROR: Invalid length for TPINIT structure given.

Description While a client’s request to join the application was being processed, an invalid data length was found in the TPINIT buffer datalen field. The length must be greater than or equal to zero.


1138 ERROR: Failed to update registry table information.

Description The IIOP Server Handler failed to update the client application information in the Bulletin Board’s registry table. The IIOP Server Handler, therefore, unregisters the client application from the Bulletin Board, removes the client application context from the IIOP Server Handler, and returns an error.


1139 ERROR: Failed to send message to authentication server, tperrno = tperrno_val.

Description The IIOP Server Handler failed to send the TPINIT information to the authentication server. The call to tpacall failed with tperrno set to tperrno_val. This failure causes the IIOP Server Handler to return an error to the client application with tperrno set to TPEPERM.



Action Check the error number, tperrno_val, and determine why the call to the authentication server failed. Most likely, the authentication server is not booted. In this case, boot the authentication server. If tperrno_val is set to TPESYSTEM or TPEOS, check the user log for other error messages that may indicate the exact nature of the problem and the reason for this failure. Contact BEA Technical Support.

See Also The tpinit (3c), tpacall, and tperrno (5) commands. For information about these commands, see the BEA TUXEDO Reference Manual.

1140 WARN: tpbroadcast() or tpnotify() encountered blocking condition.

Description The IIOP Server Handler failed to send an unsolicited message due to a blocking condition. The IIOP Server Handler is responsible for sending to the (D)BBL administrative server a request to forward unsolicited messages on behalf of the client application. The request was not sent because of an existing blocking condition on the (D)BBL administrative server queue.

Action Most likely a system limit has been reached. You may want to change the operating system tunable parameters related to the maximum size of a queue.

See Also The tpbroadcast (3c) command. For information about this command, see the BEA TUXEDO Reference Manual.

1141 ERROR: Unable to assign connection request, can’t create any more handlers.



Description The IIOP Server Listener failed to start a new IIOP Server Handler. This error may be due to no more IIOP Server Handlers being available, an error in the formatting of the command line for the IIOP Server Handler, an error in retrieving the machine table entry for the IIOP Server Listener in the Bulletin Board, or an error executing the IIOP Server Handler.


1142 ERROR: For a secure application, the two-phase challenge/response protocol must be followed.

Description The IIOP Server Handler received a message over the network from a client application. No context exists for this client application. When a secure application is running, the only message that can be accepted by the IIOP Server Handler from a client application with no context is a two-phase challenge/response message. This error indicates that this requirement has not been adhered to. The two-phase challenge/response protocol must be followed in a secure application. An error message, with tperrno set to TPEPERM, is sent back to the client application.


1143 ERROR: Failed to create encryption/decryption schedule.



Description The IIOP Server Handler failed to create an encryption/decryption schedule. The function used to create the encryption/decryption schedule is called _tpcryptinit. This function is part of an internal interface that is designed to support various methods of data encryption.

Action This error probably indicates a WLE system or operating system error. Check the user log for other error messages that may indicate the exact nature of the problem and the reason for this failure. The _tpcryptinit function may also fail because an invalid argument was given. In this case, contact BEA Technical Support.

See Also The encryption(3i) command. For information about this command, see the BEA TUXEDO Reference Manual.

1144 ERROR: _tprandkey() failed tperrno = tperrno_val, could not generate random encryption key.

Description The IIOP Server Handler failed to create a random key conforming to the restrictions of the encryption subsystem in use. The function used to create the random key is _tprandkey. This function is part of an internal interface that is designed to support various methods of data encryption.

Action Check the error number and determine why _tprandkey failed. This error probably indicates a WLE software or operating system error. Check the user log for other error messages that may indicate the exact nature of the problem and the reason for this failure. The _tprandkey function may also fail because an invalid argument was given. In this case, contact BEA Technical Support.




1145 ERROR: tpalloc() failed, tperrno = tperrno_val.

Description An attempt to allocate a buffer in the IIOP Server Handler dynamically failed. The call to tpalloc failed with tperrno set to tperrno_val.

Action Check the error number and determine why tpalloc failed. Most likely, a system limit has been reached. Change the operating system tunables to increase the amount of space a process is allowed to allocate dynamically.

See Also The tpalloc and tperrno(5) commands. For information about these commands, see the BEA TUXEDO Reference Manual.

1146 ERROR: Sending of reply to challenge call to client failed.

Description The IIOP Server Handler failed to send the challenge reply back to the client application. The IIOP Server Handler, therefore, unregisters the client application from the Bulletin Board, removes the client application context from the IIOP Server Handler, and returns an error.

Action Check the user log for other error messages that may indicate the exact nature of the problem and the reason for this failure.



1147 ERROR: Protocol error, can’t process tpinit() request before performing security protocol.

Description The IIOP Server Handler in a secure application received a request to perform a tpinit on behalf of a client application before performing the security protocol. The IIOP Server Handler, therefore, unregisters the client application from the Bulletin Board, removes the client application context from the IIOP Server Handler, and returns an error.


See Also The tpinit(3c) command. For information about tpinit(3c), see the BEA TUXEDO Reference Manual.

1148 ERROR: Processing of message to be sent to client failed.

Description The IIOP Server Handler failed to send a message to the client application. The failure occurred in a low-level routine that performs all manipulations for the message send. This includes presend, encoding, and postsend work. The message being sent from the IIOP Server Handler to the client application had to do with the client application trying to join the application. During this phase, all messages are encrypted when they are sent across the network. The messages may also be encoded if the machines are not of the same type. The IIOP Server Handler failed to encrypt the message.




1149 ERROR: Validation of TPINIT information failed.

Description The IIOP Server Handler failed to validate the TPINIT structure identifying the connecting client application against an uninterpreted ticket structure identifying the security agent’s opinion of the client application. This validation determines whether the connecting client application should be granted access to the application. The function used to perform the validation is _tpvalidate(3i). This function is part of an internal interface that is designed to support various methods of application authentication.

Action This error probably indicates that the security ticket and tpinit information do not match, and the user should not be allowed to join the application. This error may also indicate a WLE software or operating system error. Check the user log for other error messages that may indicate the exact nature of the problem and the reason for this failure. The _tpvalidate function may also fail because an invalid argument was given. In this case, contact BEA Technical Support.

See Also The security(3i) command. For information about this command, see the BEA TUXEDO Reference Manual.

1150 ERROR: Incorrect timestamp value sent by client.

Description The IIOP Server Handler failed to validate the ticket information passed to it by a client application. The ticket information passed from the client application to the IIOP Server Handler does not match the time-stamping information stored in the IIOP Server Handler.





Description An attempt to dynamically allocate memory from the operating system using malloc failed while the ticket information passed to the IIOP Server Handler by the client application was being validated.

Action Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.

1153 ERROR: Could not obtain session key from ticket.

Description The IIOP Server Handler failed to retrieve a session key from a ticket in a secure application while trying to validate the ticket information passed to it by a client application. The function used to retrieve the session key is _tpsessionkey. This function is part of an internal interface that is designed to support various methods of authentication.

Action This probably means a WLE or operating system error. Check the user log for other error messages that may indicate the exact nature of the problem and the reason for this failure. The _tpsessionkey function may also fail because an invalid argument was given or the ticket could not be processed because the client application was denied permission for an implementation-specific reason. In this case, contact BEA Technical Support.

See Also The security(3i) command. For information about this command, see the BEA TUXEDO Reference Manual.



1154 ERROR: Failed to encrypt ticket information.

Description The IIOP Server Handler failed to encrypt data according to a schedule while accepting a challenge and time-stamping value that is to be used to verify that the request is valid. The function used to encrypt data is _tpcrypt. This function is part of an internal interface that is designed to support various methods of encryption.

Action This error probably means a WLE software or operating system error. Check the user log for other error messages that may indicate the exact nature of the problem and the reason for this failure. The _tpcrypt function may also fail because an invalid argument was given. In this case, contact BEA Technical Support.


1155 ERROR: Couldn’t process message for client.

Description The IIOP Server Handler failed to receive a message from the client application. The failure occurred in a low-level routine that performs all manipulations on a message after the message has been received. This includes decoding and postreceive work. The message received has an invalid data size field in the message header.


1156 ERROR: Decryption of challenge request failed.

Description While a client application was attempting to join the application, the challenge request message could not be decrypted.




1157 ERROR: Encryption of challenge request failed.

Description While a client application was attempting to join the application, the challenge request message could not be decrypted.


1158 ERROR: Couldn’t create encryption/decryption schedule.

Description While a client application was attempting to join the application, the encryption or decryption schedule could not be created.


1159 ERROR: Failed to encode/decode establish connection request message.

Description While a client application was attempting to join the application, the establish connection request message could not be encoded or decoded.


1160 ERROR: Decryption of challenge reply failed.

Description While a client application was attempting to join the application, the challenge reply message could not be decrypted.




1161 ERROR: Encryption of challenge reply failed.

Description While a client application was attempting to join the application, the challenge reply message could not be decrypted.


1162 ERROR: Encoding/decoding of ticket request failed.

Description While a client application was attempting to join the application, the ticket request message could not be encoded or decoded.





1164 ERROR: Decryption of TPINIT buffer failed.

Description While a client application was attempting to join the application, the TPINIT message could not be decrypted.




1165 ERROR: Encoding/decoding of TPINIT buffer failed.

Description While a client application was attempting to join the application, the TPINIT message could not be encoded or decoded.


1166 ERROR: Encryption of TPINIT buffer failed.

Description While a client application was attempting to join the application, the TPINIT message could not be encrypted.


1167 ERROR: Unknown client message to process.

Description While a client application was attempting to join the application, an unknown message type was encountered for processing.


1168 ERROR: Tried to process unexpected message opcode 0xcode.

Description While a client application was attempting to join the application, an unknown message type was encountered for processing.




1169 ERROR: Expected numeric argument to -D option.

Description An invalid argument was passed to the IIOP Server Listener command-line option. The argument to the ISL command -D option needs to be numeric. This error causes the IIOP Server Listener not to be booted.

Action Make sure the argument to the ISL command -D option is numeric.


1170 ERROR: Expected numeric argument to -M option.

Description An invalid argument was passed to the IIOP Server Listener command-line option. The argument to the ISL command -M option needs to be numeric. This error causes the IIOP Server Listener not to be booted.

Action Make sure the argument to the ISL command -M option is numeric.


1171 ERROR: Expected numeric argument to -m option.

Description An invalid argument was passed to the IIOP Server Listener command-line option. The argument to the -m option needs to be numeric. This error causes the IIOP Server Listener not to be booted.

Action Make sure the argument to the -m option is numeric.




1174 WARN: Disconnecting listener connection to client, connection timed out.

Description The IIOP Server Listener scans its handler table and times out any connections that are overdue, restarts any dead handlers, and allocates any blocked connection requests to a handler that is available. When scanning this table, the IIOP Server Listener found a handler that was waiting for a connection that had timed out. The IIOP Server Listener proceeded and forced the connection closed.


1175 WARN: Disconnecting listener connection to client, request timed out.

Description The IIOP Server Listener scans its handler table and times out any connections that are overdue, restarts any dead handlers, and allocates any blocked connection requests to a handler that is available. When scanning this table, the IIOP Server Listener found a blocked connection request that had not been passed to an available handler. Because the time to assign a handler expired, the IIOP Server Listener proceeded and forced the connection to close.

Action This error probably indicates that the number of client applications that need to join the application cannot be supported by the existing configuration. The command-line options for the ISL command should be modified to support a larger number of client applications. The ISL command -m, -M, and -x options should be used to that effect.


1176 ERROR: Sending of reply to tpconnect() call to client failed.

Description An attempt to send an acknowledgment of a tpconnect request to the client application has failed.

Action This is an internal message. This failure indicates a problem with the network or with the client application process. Contact BEA Technical Support.



1177 ERROR: Sending of reply to tpdiscon() call to client failed.

Description An attempt to send an acknowledgment of a tpdiscon request to the client application has failed.


1178 ERROR: Sending of reply to tpsend() call to client failed.

Description An attempt to send an acknowledgment of a tpbroadcast request to the client application has failed.


1179 ERROR: Unrecognized opcode: opcode.

Description A message was received in the IIOP Server Handler requesting an unknown operation.

Action This is an internal message. This failure indicates a problem with the network or with the client application process. This failure could indicate the use of newer client application software with an older IIOP Server Handler. Contact BEA Technical Support.



1180 ERROR: Sending of reply to tpconnect() call to client failed.

Description An attempt to send an acknowledgment of a tpconnect request to the client application has failed.


1182 ERROR: Invalid -T option = num.

Description The -T command-line option for the ISL command had an invalid argument. The value must be greater than or equal to 0 and less than 70409299.

Action Reconfigure the CLOPT parameter for the ISL command and reboot the process. For information about the ISL command , see the Administration Guide.

1183 ERROR: Expected numeric argument to -T option.

Description The -T command-line option for the ISL command had a nonnumeric argument.

Action Reconfigure the CLOPT parameter for the ISL command and reboot the process. For information about the ISL command, see the Administration Guide.

1185 INFO: Userid: [user], Clientid: [client] timed out due to inactivity.



Description A client application attached to the application has been invalid for longer than the configured timeout value, specified via the -T command-line option of the ISL command. The associated user name and client application name are printed.

Action None.

1186 ERROR: Cannot convert message with unknown protocol num.

Description The IIOP Server Handler received a message from a client application with an unknown protocol number, num.


1187 ERROR: Cannot convert message from protocol num1 to num2.

Description The IIOP Server Handler received a message to or from a client application with a protocol version that cannot be converted.


1188 ERROR: Unrecognized message format, release num.

Description The IIOP Server Listener received a connection message from a client application with an unknown protocol number, num.


1189 ERROR: Received message of unknown type ‘type’ subtype ‘subtype’.



Description The IIOP Server Handler received a typed buffer from a client application with an unknown type or subtype, or both, indicated in the message.


1190 INFO: Reestablished network address string.

Description A previously suspended IIOP Server Listener process has been unsuspended and has reestablished its network address.

Action Informational message, no action required.

See Also The MIB(5) and WS_MIB(5) commands. For information about these commands, see the BEA TUXEDO Reference Manual.

1191 INFO: Network address disabled.

Description An IIOP Server Listener process has been suspended and has disabled its listening network address to disallow further incoming connections.


See Also The MIB(5) and WS_MIB(5) commands. For information about these commands, see the BEA TUXEDO Reference Manual.

1192 INFO: Abortively disconnecting client user[usr], client[clt].



Description An IIOP Server Handler is disconnecting the virtual circuit associated with a particular client application (<usr>/<clt>) because of an administrative request to set the client application state to DEAD.


1195 WARN: Failed to reestablish network address string.

Description A previously suspended IIOP Server Listener server was administratively unsuspended but could not reestablish its network address.

Action Failure to reestablish the network address is usually caused either by a failure of the network drivers on the machine to clear the previously held network address or by another process claiming the network address while the listener was suspended. In the former case, the network address eventually is released by the system and the IIOP Server Listener reestablishes its network address through its periodic retry mechanism; therefore, no action is required in this case. In the latter case, local commands may be used to determine what processes and users are occupying the network address; these processes and users should be asked to relinquish the address.

See Also The UNIX netstat command, the Microsoft Windows NT NetStatisticsGet command, and the MIB(5) and WS_MIB(5) commands.

For information about the netstat command, see the UNIX manual page.

For information about the NetStatisticsGet command, see Microsoft Visual C++ online help.

For information about the MIB(5) and WS_MIB(5) commands, see the BEA TUXEDO Reference Manual.

1196 INFO: Terminating handlers in preparation for shutdown.



Description The IIOP Server Listener is shutting down and in preparation is about to terminate its associated IIOP Server Handler processes.


See Also The MIB(5), tmshutdown(1), and WS_MIB(5) commands. For information about these commands, see the BEA TUXEDO Reference Manual.

1197 INFO: Exiting system.

Description The IIOP Server Listener has completed its shutdown and is exiting the system.



1199 WARN: .SysClientDied: User usrname on LMID clientname client died.

Description This message indicates that the specified client application exited the application without ending the session. The client applications should call either the PrincipalAuthenticator::logoff() function or the Tobj_Bootstrap::destroy_current() function before exiting the application.

Action This is an informational message. No action is required.

See Also The PrincipalAuthenticator::logoff() and the Tobj_Bootstrap::destroy_current() functions. For information about these functions, see the BEA WLE C++ Programming Reference.




Note: When IIOP Server Listener/Handler messages are listed in the user log (ULOG), the messages have the prefix ISNAT_CAT. For example, message 1100 is listed as ISNAT_CAT:1100

1200 INFO: .SysClientState: User usrname on LMID state change to state.

Description This message indicates that the specified client application changed to a new state. A complete listing of the current attributes of the client application is sent in the posted buffer.

Action This is an informational message.

See Also The EVENT_MIB(5) and TM_MIB(5) commands. For information about these commands, see the BEA TUXEDO Reference Manual.

1201 WARN: .SysClientSecurity: User usrname on LMID authentication failure.

Description This message indicates that the specified client application failed security validation when trying to join the application. A complete listing of the current attributes of the client application is sent in the posted buffer.

Action Make sure that a hacker is not trying to gain access to your application data.

See Also The EVENT_MIB(5) and TM_MIB(5) commands. For information about these commands, see the BEA TUXEDO Reference Manual.



1204 ERROR: Memory allocation failure error_info.

Description An attempt to allocate memory dynamically from the operating system failed while a client application message was being decoded. Additional information about the problem is printed as part of the message.

Action Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine.


Description An attempt to allocate memory dynamically from the operating system failed while a client application message was being decompressed. Additional information about the problem is printed as part of the message.



Description An attempt to allocate memory dynamically from the operating system failed while a message was being compressed. Additional information about the problem is printed as part of the message.





Description An attempt to allocate memory dynamically from the operating system failed while a client application message for _tmpostrecv() was being processed. Additional information about the problem is printed as part of the message.


1213 ERROR: Type switch uninitialization failure.

Description While processing a client application buffer, the buffer uninitialization function, _tmuninitbuf(), returned an error.

Action Check the buffer type switch to see that it is correctly set up (that is, that the right uninitialization function is associated with the correct buffer type). If the buffer type is application defined, check the uninitialization function to see that it is coded correctly.

See Also The buffer (3c) and typesw (5) commands. For information about these commands, see the BEA TUXEDO Reference Manual.

1229 WARN: A client failed encryption negotiation.

Description A client application attempted to log in to the system, but could not negotiate an acceptable encryption level.

Action When client applications log into the system, they negotiate an encryption strength with the IIOP Server Listener. If the client application and listener cannot agree on the level of encryption (for example, if the IIOP Server Listener demands 128-bit encryption and the client application can only speak 40-bits encryption) this message is displayed. The system administrator can change the encryption policy either of the IIOP Server Listener or client application.



1230 ERROR: Invalid security protocol.

Description An invalid opcode was attempted while the IIOP Server Listener was insecure.

Action Monitor your network for malicious use. Contact BEA Technical Support.

1231 ERROR: Memory allocation error.

Description While negotiating the Diffie-Hellman parameters, the IIOP Server Listener ran out of memory.

Action Make sure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine.

1232 ERROR: Encryption negotiation protocol error.



1233 ERROR: Unable to get encryption handle.

Description While negotiating the Diffie-Hellman parameters and attempting to get an encryption handle, the IIOP Server Listener experienced an error.

Action Make sure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine.



1234 ERROR: Unable to establish negotiation parameters.



1235 ERROR: Unable to send negotiation parameters.

Description While attempting to send the Diffie-Hellman parameters to the client application, the IIOP Server Listener experienced an error.

Action The network may have experienced an error, or the client application waiting for the security packet may have been killed. If neither of these events has occurred, contact BEA Technical Support.

1236 ERROR: Unable to begin encryption.

Description After the shared key was established, an error occurred while encryption was starting.


1237 ERROR: tpnotify(TPACK) failed to reply, tperrno = tperrno.

Description The IIOP Server Handler sent an acknowledged unsolicited message to a client application. However, that client application never acknowledged the message.

Action The network may have experienced an error, or the client application waiting for the notification may have been killed. The tperrno process may provide clues as to the cause of this failure. If neither of these events has occurred, contact BEA Technical Support.



1238 ERROR: Invalid security parameters.

Description The encryption level of the IIOP Server Listener is greater than zero bits, but the link level encryption package is not installed on this machine.

Action The MIB may have changed the minimum encryption bits for this IIOP Server Handler. If the new value of the minimum encryption bits is greater than zero and the link level encryption package is not installed, no client applications is able to log into the IIOP Server Handler. Change the minimum encryption value via the -z option to the IIOP Server Listener, or through the MIB with the TA_MINENCRYPTBITS member of the T_WSL class.

1239 ERROR: Invalid security parameters.

Description The encryption level of the IIOP Server Listener is greater than forty bits, but only the 40-bit link level encryption package is installed on this machine.

Action The MIB may have changed the minimum encryption bits for this IIOP Server Handler. If the new value of the minimum encryption bits is greater than forty, no client applications is able to log into the IIOP Server Handler. Change the minimum encryption value via the -z option to the IIOP Server Listener, or through the MIB with the TA_MINENCRYPTBITS member of the T_WSL class.

1240 ERROR: Failed to read server table entry, tperrno = tperrno.

Description The IIOP Server Listener was rebooting after a failure and could not read the server table.

Action The Bulletin Board may be corrupted. The tperrno process may provide clues as to the cause of this failure. Contact BEA Technical Support.



1241 ERROR: Sending of reply to tpbroadcast() or tpnotify() call to client failed.

Description The IIOP Server Handler received an acknowledgment from a client application but was unable to forward the acknowledgment of the tpnotify to the sender.

Action The originator of the tpnotify may have been killed. If the originator of the notify has not been killed, contact BEA Technical Support.

1242 ERROR: Bad Internet type of listening address provided: address.

Description The address is not a valid Internet address.

Action Any address that starts with // must be a valid Internet address. The following formats are recognized by the system: //hostname:port_number and //#.#.#.#:port_number. Other formats may be recognized. Change address to comply with the known formats. If you believe that your address is in the proper format, contact BEA Technical Support.

1249 ERROR: -H and -n have different length of network address.

Description If you are using an external address, that address must have the same format as the -n option.

Action Change the -H option to have the same format as the -n option.





Action Make sure the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used be a process. Either reduce the memory usage on the machine or increase the amount of physical memory on the machine.

1254 ERROR: Bad conversational sequence number.

Description Conversations are sequenced to provide protection. One of the conversational messages arrived out of order. The conversation has been disconnected, and if a transaction was active, it has been set to the ABORTONLY state.

Action Look at the user log to determine whether the BRIDGE has given up sending any messages to the message queue for the IIOP Server Handler. If it has given up, the operating system may need to be tuned to handle a high volume of messages properly. This problem may also be alleviated by using compression. This error may also occur when the BRIDGE is failing over to a new network link or failing back to a high priority link.

1276 ERROR: Received message with unknown release number value.

Description The IIOP Server Handler received a packet with an unknown release number value. The network may be having difficulty. If link-level encryption is in use, this error may indicate that an attack is in progress.

Action If this error happens consistently, contact BEA Technical Support.




Description An attempt to allocate memory dynamically from the operating system using malloc() failed while the IIOP Server Listener or the IIOP Server Handler was being initialized.


1278 ERROR: Address conversion error.

Description The IIOP Server Handler had a problem converting an address from a binary format to a text format.

Action If this error happens consistently, contact BEA Technical Support.

1279 ERROR: descriptor allocation error.

Description The IIOP Server Handler was unable to allocate a network resource for the listening end point.




1280 ERROR: Could not initialize network (error).

Description The IIOP Server Handler or IIOP Server Listener could not initialize its network.

Action Ensure that the network is viable on the machine. If the network is viable, contact BEA Technical Support.

1281 ERROR: Could not initialize global information (error).



1283 ERROR: Network error (error) servicing network event.

Description The IIOP Server Listener encountered a severe error while handling network events.


1284 ERROR: Failed to allocate a network resource (error).

Description The IIOP Server Handler or IIOP Server Listener could not allocate a network descriptor for a remote connection.




1286 ERROR: -K argument must be client, handler, both, or none.

Description The -K option for the ISL command requires an argument of client application, handler, both, or none.

Action Ensure that the -K option of the ISL command is client application, handler, both, or none. Check your spelling.

1287 WARN: Forced shutdown of client; user name ‘name’; client name ‘name’ client address ‘xxx.xxx.xxx.xxx’ did not call tpterm().

Description This error may result from an IIOP Server Handler being shut down when client applications are connected, a client application connection has timed out, the IIOP Server Handler was unable to send a network message to the client application, or an incorrect APP_PW (application password) was rejected during tpinit().

Action If APP_PW is turned on, see your UBBCONFIG file and ubbconfig(5), and then check with your system administrator to verify that you are using the correct application password for your WLE application.

1288 WARN: setsockopt() for SO_KEEPALIVE failed.

Description The KEEPALIVE handler-side networking option was configured for a IIOP Server Listener/Handler pair, but could not be enabled.

Action This error is ignored and IIOP Server Handler processing continues normally. However, network errors may not be reported, or may be reported less promptly. Consider enabling the inactive client application timeout (ISL command -T option) to reclaim resources associated with dead network connections.




1289 WARN: KEEPALIVE option requested but not available on this platform.

Description The KEEPALIVE handler-side networking option is configured for a IIOP Server Listener/Handler pair, but cannot be enabled because it is not available on this platform.

Action This error is ignored and IIOP Server Handler processing continues normally. However network errors may not be reported, or may be reported less promptly. Consider enabling the inactive client application timeout (ISL command -T option) to reclaim resources associated with dead network connections.


1290 ERROR: Can’t parse the address address.

Description While the networking software was attempting to resolve address, an error occurred.

Action Any address that starts with // must be a valid Internet address. The following formats are recognized by the system: //hostname:port_number and //#.#.#.#:port_number. Other formats may be recognized. Make sure that DNS is working properly in your network, and that the host name and port number portion of address can be located by your server.

1291 ERROR: Can’t resolve host name in address address.

Description While the networking software was attempting to resolve the host name portion of address, an error occurred.

Action Any address that starts with // must be a valid Internet address. The following formats are recognized by the system: //hostname:port_number and //#.#.#.#:port_number. Other formats may be recognized. Make sure that DNS is working properly in your network, and that the host name portion of address can be located by your DNS server.



1292 ERROR: Unknown address type: address.

Description The given address does not correspond to a type known by the system.

Action The WLE software understands several types of address format. Addresses that start with // must be Internet addresses. Other formats may or may not be understood by the WLE software.

1293 ERROR: Can’t resolve port number in address address.

Description While the networking software was attempting to resolve the port number portion of address, an error occurred.

Action Any address that starts with // must be a valid Internet address. The following formats are recognized by the system: //hostname:port_number and //#.#.#.#:port_number. Other formats may be recognized. Make sure that DNS is working properly in your network, and that the port number portion of address can be located by your server.

1294 ERROR: Can’t convert the address address to binary format.

Description While the WLE software was trying to convert an address to an internal binary representation, an error occurred.


1295 ERROR: Illegal character in the address address.

Description There is an illegal character in the port portion of address. Ports may only have alphanumeric characters.

Action Remove the illegal character from the port portion of the address.



1296 ERROR: Missing port number in the address address.

Description The address must have a port number portion.

Action Supply a port number portion in the given address. Otherwise, the IIOP Server Listener or IIOP Server Handler cannot determine its listening end point properly.

1297 ERROR: Port number can’t be bigger than value in the address address.

Description The port number portion of address is larger than the largest allowable port number of value.

Action Change the port number to be within the specified range.

1304 ERROR: Invalid argument to -C option:.

Description The -C option for the ISL command requires an argument of detect, warn, or none.

Action Ensure that the -C option of the ISL command is detect, warn, or none. Check your spelling.



1305 WARN: Unofficial connection from client (network address is unknown).

Description An unofficial connection was established from a client application with an unknown network address. The official way for a CORBA client application to connect to the IIOP Server Listener/Handler is via a Bootstrap object. An unofficial connection is established directly from an IOR. The use of unofficial connections can cause problems for remote client applications that use transactions.

Action Check that the host name specified in the Tobj_Bootstrap() constructor or in the TOBJADDR environment variable exactly matches the host name specified in the -n option of the ISL command. The names must match exactly in both spelling and case.


1306 WARN: Unofficial connection from client at ‘address’.

Description An unofficial connection was established from a client application at the network address address. The official way for a CORBA client application to connect to the IIOP Server Listener/Handler is via a Bootstrap object. An unofficial connection is established directly from an IOR. The use of unofficial connections can cause problem for remote client applications that use transactions.

Action Check that the host name specified in the Tobj_Bootstrap() constructor or in the TOBJADDR environment variable exactly matches the host name specified in the -n option of the ISL command. The names must match exactly in both spelling and case.




1307 ERROR: Unofficial connection from client (network address is unknown).

Description An unofficial connection was established from a client application with an unknown network address. The official way for a CORBA client application to connect to the IIOP Server Listener/Handler is via a Bootstrap object. An unofficial connection is established directly from an IOR. The use of unofficial connections can cause problems for remote client applications that use transactions.

Action Check that the host name specified in the Tobj_Bootstrap() constructor or in the TOBJADDR environment variable exactly matches the host name specified in the -n option of the ISL command. The names must match exactly in both spelling and case. Also check that the client application connects to the IIOP Server Listener via a Bootstrap object only.


1308 ERROR: Unofficial connection from client at ‘address’.

Description An unofficial connection was established from a client application at the network address address. The official way for a CORBA client application to connect to the IIOP Server Listener/Handler is via a Bootstrap object. An unofficial connection is established directly from an IOR. The use of unofficial connections can cause problems for remote client applications that use transactions.

Action Check that the host name specified in the Tobj_Bootstrap() constructor or in the TOBJADDR environment variable exactly matches the host name specified in the -n option of the ISL command. The names must match exactly in both spelling and case. Also check that the client application connects to the IIOP Server Listener via a Bootstrap object only.




1309 ERROR: Unable to open TUXCONFIG file to Resources section.

Description While attempting to read the application password, the IIOP Server Listener or the IIOP Server Handler had a problem opening the RESOURCES section of the TUXCONFIG file.

Action Ensure that the TUXCONFIG environment variable points to the appropriate configuration file. If the configuration file does not exist, you can create it from the UBBCONFIG file using tmloadcf. If it does exist, the file may be corrupted, or may have been a file generated by an older release of the WLE software. Shut down the system, remove the file, and recreate it with tmloadcf.

1310 ERROR: Unable to open Resources section of TUXCONFIG file.

Description While attempting to read the application password, the IIOP Server Listener or the IIOP Server Handler had a problem reading the RESOURCES section of the TUXCONFIG file.

Action Ensure that the TUXCONFIG environment variable points to the appropriate configuration file. If the configuration file does not exist, you can create it from the UBBCONFIG file using tmloadcf. If it does exist, the file may be corrupted, or may have been a file generated by an older release of the WLE software. Shut down the system, remove the file, and recreate it with the tmloadcf command.

1311 ERROR: Possibly corrupted key in database.

Description While the IIOP Server Handler or the IIOP Server Listener was reading the TUXCONFIG file, an invalid password was detected.




1312 ERROR: Error while decrypting password.

Description While the IIOP Server Handler or IIOP Server Listener was reading the TUXCONFIG file, an invalid password was detected.


1313 ERROR: Invalid password in TUXCONFIG file.

Description While the IIOP Server Handler or IIOP Server Listener was reading the TUXCONFIG file, an invalid password was detected.


1314 ERROR: Invalid parameter.

Description An error occurred while the application password was being encrypted.





Description While an encryption schedule was being created, the system ran out of memory.

Action Check the memory on the system where the process was running.


Description An error occurred while the application password was being encrypted.



Description An error occurred while the application password was being manipulated.



Description While a key was being created, the system ran out of memory.





Description An error occurred while a session key being retrieved.



Description While a session key was being created, the system ran out of memory.





1322 ERROR: Received message of unknown type ‘type’ subtype ‘subtype’.

Description The IIOP Server Handler received a typed buffer from a client application with an unknown type or subtype, indicated in the message.




1323 ERROR: Couldn’t convert buffer to current release format.

Description This error occurs if an WLE remote client application and the native UNIX system machine are of different WLE software releases and the message is from an older release. The error can also occur if the message received by the IIOP Server Handler or IIOP Server Listener is corrupted.


1324 ERROR: Couldn’t convert buffer to native site format.

Description The IIOP Server Handler was unable to convert a message from a WLE client application format to the native format. This error indicates that the buffer type is unknown to the IIOP Server Handler.

Action Check the user log for a message indicating the nature of the failure (in particular, the type and subtype of the buffer that could not be converted). It may be necessary to rebuild the IIOP Server Handler to include additional application buffer types.

1325 ERROR: Received message with an unknown internal type index indexval.

Description While processing a message from the client application, the IIOP Server Handler received an unknown internal buffer type.

Action Because the IIOP Server Handler sets the buffer type when it converts the message to the native format, this error should not occur. Contact BEA Technical Support.

1326 ERROR: Received message of unknown type ‘typeval’ subtype ‘subtypeval’.



Description While processing a message from the client application, the IIOP Server Handler received an unknown buffer type and subtype.


1327 ERROR: Received message of unknown type ‘type’.

Description While processing a message from the client application, the IIOP Server Handler received an unknown application buffer type.


1328 ERROR: Failed to update registry table information.

Description The IIOP Server Handler failed to update the client application information in the Bulletin Board’s registry table. The IIOP Server Handler therefore unregisters the client application from the Bulletin Board, removes the client application context from the IIOP Server Handler, and returns an error.

Action Check the user log for other error messages that may indicate the exact nature of the problem and reason for this failure.



1329 ERROR: Error assigning connection request, can’t create any more handlers.

Description The IIOP Server Listener was unable to start a new Handler.

Action The most likely problem is that the maximum number of IIOP Server Handlers specified in the configuration file have been started. To increase this number, the CLOPT -M maxh value must be changed. This can be done in two ways: first, shut the application down and change the configuration file and reboot the application, or second, change the value dynamically with tmconfig(1), and shut down and reboot only the IIOP Server Listener server.

Another possible source of the problem could be that the number of processes allowable by a user (ulimit) has been reached. If the ulimit has been reached, consult with your system administrator to increase this limit.

1330 ERROR: Failed to initialize network protocol information (error).



1331 ERROR: Failed to encode/decode establish connection request message.

Description While a client application was attempting to join the application, the establish connection request message could not be encoded or decoded.




1335 ERROR: Memory allocation failure error_info

Description An attempt dynamically to allocate memory from the operating system failed. Additional information about the problem is printed as part of the message.


1336 ERROR: Memory allocation failure error_info

Description An attempt dynamically to allocate memory from the operating system failed. Additional information about the problem is printed as part of the message.


1337 ERROR: Cannot send system exception

Description The IIOP Server Listener/Handler attempted to return a CORBA system exception to the client application, but could not write the message to the network.

Action The client application cannot be reached on the network, which probably means that the client application process disconnected.



1338 ERROR: Cannot send error message

Description The IIOP Server Listener/Handler attempted to send a GIOP error message to the client application, but could not write the message to the network.


1339 ERROR: Cannot send close connection message

Description The IIOP Server Listener/Handler attempted to send a GIOP close-connection message to the client application, but could not write the message to the network.


1340 ERROR: Received unexpected GIOP message type (type)

Description The IIOP Server Listener/Handler received a GIOP message with an unknown or unexpected message type. This probably indicates that the client application is not GIOP 1.0 compliant. The IIOP Server Listener/Handler returns a GIOP error message to the client application.

Action Make sure that the client is GIOP 1.0 compliant.



1341 ERROR: Cannot decode locate request

Description The IIOP Server Listener/Handler received a GIOP locate request message that could not be decoded. This probably indicates that the client application is not GIOP 1.0 compliant. The IIOP Server Listener/Handler returns a GIOP error message to the client application.

Action Make sure the client application is GIOP 1.0 compliant.

1342 ERROR: Cannot encode locate reply

Description The IIOP Server Listener/Handler failed to encode a GIOP locate reply message. This should not happen. The IIOP Server Listener/Handler returns a GIOP error message to the client application.


1343 ERROR: Cannot send locate reply

Description The IIOP Server Listener/Handler attempted to send a GIOP locate reply message to the client application, but could not write the message to the network.




1344 ERROR: Cannot decode request header

Description The IIOP Server Listener/Handler received a GIOP request message that could not be decoded. This probably indicates that the client application is not GIOP 1.0 compliant The IIOP Server Listener/Handler returns a GIOP error message to the client application.

Action Make sure the client application is GIOP 1.0 compliant.

1345 ERROR: Received invalid object key

Description The IIOP Server Listener/Handler received a GIOP request message which contains a non-WLE object key. This could happen if a client application reuses an old CORBA Interoperable Object Reference (IOR) that was created for another CORBA Object Request Broker using the same network address as the IIOP Server Listener/Handler.

Action Make sure the offending IOR was received from a WLE server.

1346 ERROR: Received unexpected type type object key

Description The IIOP Server Listener/Handler received a GIOP request message that contains a WLE object that is not recognized. This should not happen.


1347 ERROR: Invalid internal buffer: error_info

Description An internal buffer is corrupted. Additional information about the problem is printed as part of the message.





Description The IIOP Server Listener/Handler failed to allocate memory for an internal network buffer. Additional information is printed as part of the message.


1349 ERROR: Cannot allocate call buffer: error_info

Description The IIOP Server Listener/Handler failed to allocate memory for an internal WLE buffer. Additional information is printed as part of the message.


1350 ERROR: Cannot reallocate call buffer: error_info

Description The IIOP Server Listener/Handler failed to increase the size of an internal WLE buffer. Additional information is printed as part of the message.




1351 ERROR: Cannot set TGIOP host and port: error_info

Description An internal error occurred in IIOP Server Listener/Handler.










1354 ERROR: Cannot allocate reply buffer: error_info

Description The IIOP Server Listener/Handler failed to allocate memory for an internal WLE buffer. Additional information is printed as part of the message.


1355 ERROR: Cannot decode reply message header

Description The IIOP Server Listener/Handler failed to decode the header of a TGIOP message received from a WLE server.


1356 ERROR: Cannot decode reply header

Description The IIOP Server Listener/Handler failed to decode the header of a TGIOP reply message received from a WLE server.


1357 ERROR: Cannot decode locate reply header

Description The IIOP Server Listener/Handler failed to decode the header of a TGIOP locate reply message received from a WLE server.








Description In internal buffer is corrupted. Additional information about the problem is printed as part of the message.







1361 ERROR: Cannot encode IIOP profile

Description The IIOP Server Listener/Handler failed to allocate memory for an internal IIOP buffer.


1362 ERROR: Cannot encode IOR



1363 ERROR: Cannot allocate memory for IOR string





1364 ERROR: Cannot encode IOR



1365 ERROR: Cannot allocate memory for IOR string



1366 ERROR: No protocol machine registered in protocol group

Description The IIOP Server Listener/Handler did not initialize properly.


1367 ERROR: Invalid protocol machine discriminator return

Description An internal error occurred in the IIOP Server Listener/Handler.




1368 ERROR: Error allocating protocol group table

Description The IIOP Server Listener/Handler failed to allocate memory for an internal structure.


1369 ERROR: Invalid protocol group

Description An internal error occurred in the IIOP Server Listener/Handler during initialization.


1370 ERROR: Missing group discriminator

Description An internal error occurred in the IIOP Server Listener/Handler during initialization.




1371 ERROR: Error allocating global protocol machine table



1372 ERROR: Error allocating local protocol machine table



1373 ERROR: Cannot allocate protocol machine context





1374 ERROR: Unexpected object key number

Description The IIOP Server Listener/Handler received a valid WLE object key for an unknown or unexpected internal interface.



Description An internal buffer in the IIOP Server Listener/Handler is corrupted. Additional information about the problem is printed as part of the message.


1376 ERROR: Memory allocation error: error_info



1377 ERROR: Cannot open named pipe file_name

Description Solaris only. The IIOP Server Listener failed to open the named pipe file_name to communicate with an IIOP Server Handler.

Action Shut the IIOP Server Listener down, remove file_name from the APPDIR directory and reboot the IIOP Server Listener/Handler. If the problem persists, contact BEA Customer Support.



1378 ERROR: Named pipe file_name is not a streams pipe

Description Solaris only. The IIOP Server Listener/Handler expects file_name to be a named pipe. There is an existing file by that name that is not named pipe.


1379 ERROR: Cannot find timod on connection fd

Description Solaris only. The IIOP Server Listener/Handler expects the network connection descriptor to use TLI. The connection is not TLI based.


1380 ERROR: Cannot pass connection to handler

Description Solaris only. The IIOP Server Listener uses a named pipe to pass a newly received connection to its handler. If this error occurs, the selected handler is probably dead.

Action Wait a few seconds and try again (that is, restart the client application). If the problem persists, contact BEA Customer Support.

1381 ERROR: Invalid handler index

Description HP-UX, AIX and Tru64 UNIX only. An internal table is corrupted in the IIOP Server Listener.




1382 ERROR: Cannot create UNIX socket, errno = error_number

Description HP-UX, AIX, and Tru64 UNIX only. The IIOP Server Listener failed to create a UNIX socket to communicate with an IIOP Server Handler. Error_number is the UNIX error number.

Action Make sure the operating system parameters are set correctly to handle UNIX sockets.

1383 ERROR: Cannot connect to handler socket file_name, errno = error_number (error_message)

Description HP-UX, AIX, and Tru64 UNIX. The IIOP Server Listener failed to connect the UNIX socket name to an IIOP Server Handler. Error_number is the UNIX error number, and error_message is a string description of error_number.


1384 ERROR: Cannot callocate control





1385 ERROR: Cannot pass connection to handler

Description HP-UX, AIX and Tru64 UNIX. The IIOP Server Listener uses a named pipe to pass a newly received connection to its handler. If this error occurs, the selected handler is probably dead.

Action Wait a few seconds and try again (that is, restart the client application). If the problem persists, contact BEA Customer Support.

1386 ERROR: Cannot open handler process: error_info

Description Windows NT only. The IIOP Server Listener is trying to access an IIOP handler to pass a connection. The handler process cannot be reached. Error_info provides more information.

Action Make sure the handler process is still alive. Wait a few seconds and try again (i.e. restart the client application). In case of failure, make sure that the number of handles used by all the processes on the machine is not too large. Make sure enough handles are available on the system for WLE software to operate normally.

1387 ERROR: Cannot duplicate connection handle: error_info

Description Windows NT only. The IIOP Server Listener is trying to duplicate a connection handle in order to pass the connection to an IIOP Server Handler. The handle cannot be duplicated. Error_info provides more information.

Action Make sure that the number of handles used by all the processes on the machine is not too large. Make sure enough handles are available on the system for WLE software to operate normally.



1388 ERROR: Cannot find timod on connection fd

Description Solaris only. The IIOP Server Handler expects the network connection descriptor received from the IIOP Server Listener to use TLI. The connection is not TLI based.


1389 ERROR: Cannot accept connection on UNIX socket

Description HP-UX, AIX and Tru64 UNIX only. The IIOP Server Handler encountered an error when accepting a UNIX socket connection from the IIOP Server Listener. This UNIX socket connection between listener and handler is used to pass a network connection from a client application.


1390 ERROR: Cannot allocate control





, all .

1391 ERROR: Cannot receive fd

Description HP-UX, AIX and Tru64 UNIX only. The IIOP Server Handler encountered an error when trying to receive a network connection file descriptor from the listener.

Action Make sure the number of file descriptors available per process is large enough to accommodate all the client application connections on the handler plus a few control file descriptors, such as the UNIX socket connection between listener and handler. Make sure the number of file descriptors available on the machine is large enough to accommodate all the client application’s connections on the machinethe control file descriptors, and all the other processes running on the machine

1392 ERROR: Missing protocol machine information











1395 ERROR: No : separator in network address

Description The IIOP Server Handler process was invoked with a -n option that specified an incorrect network address. The network address argument to option -n of the IIOP Server Handler must be in one of the following formats:

“//hostname:port_number”

“//#.#.#.#:port_number”

The colon is missing in the argument.

Action This is an internal error. Contact BEA Customer Support.

1396 ERROR: No memory for host variable



1397 ERROR: Cannot register WSH protocols

Description While initializing the IIOP Server Handler, an internal error occurred.





Note: When IIOP Listener/Handler messages are listed in the user log (ULOG), the messages have the prefix ISNAT_CAT. For example, message 1100 is listed as ISNAT_CAT:1100

1398 ERROR: Cannot allocate memory for named pipe name

Description Solaris, HP-UX, AIX, and Tru64 UNIX only. The IIOP Server Listener/Handler failed to allocate memory for an internal structure.


1399 ERROR: Cannot create named pipe file

Description Solaris only. The IIOP Server Handler creates a named pipe to communicate with an IIOP Server Listener. The file for the named pipe cannot be created.

Action Shut the IIOP Server Listener down, remove all files with names that begin with ISH.pipe from the APPDIR directory and reboot the IIOP Server Listener/Handler. If the problem persists, contact BEA Customer Support.



1400 ERROR: Cannot create pipe for listener

Description Solaris only. The IIOP Server Handler creates a pipe to communicate with an IIOP Server Listener. The pipe cannot be created.

Action Make sure the operating system has enough resources to create pipes.

1401 ERROR: Cannot setup pipe for listener

Description Solaris only. The IIOP Server Handler sets up a pipe to communicate with an IIOP Server Listener. The setup operation failed.


1402 ERROR: Cannot attach to pipe for listener

Description Solaris only. The IIOP Server Handler attaches a named pipe to a normal pipe to communicate with an IIOP Server Handler. The attach operation failed.


1403 ERROR: Cannot create UNIX socket

Description HP-UX, AIX, and Tru64 UNIX only. The IIOP Server Listener failed to create a UNIX socket to communicate with an IIOP Server Handler.




1404 ERROR: Cannot bind to UNIX socket

Description HP-UX, AIX, and Tru64 UNIX only. The IIOP Server Handler creates a UNIX socket to communicate with an IIOP Server Listener. The file for the UNIX socket cannot be created.

Action Shut the listener down, remove all files with names that begin with ISH.pipe from the APPDIR directory and reboot the IIOP Server Listener/Handler. If the problem persists, contact BEA Customer Support.

1405 ERROR: Cannot listen on UNIX socket

Description HP-UX, AIX, and Tru64 UNIX only. The IIOP Server Handler creates a UNIX socket to communicate with an IIOP Server Listener. The IIOP Server Listener/Handler cannot set up the length of the listen queue.












SEE ALSO Contact BEA Customer Support.




1410 ERROR: No : separator in network address

Description The IIOP Server Handler process was invoked with an ISL command that specified an incorrect network address. The ISL command network address (netaddr) argument to the -n option must be of the form //host:port. This error indicates that the colon is missing in the argument.

Action Fix the application configuration for the IIOP Server Listener/Handler and make sure the network address has the appropriate syntax.

1411 ERROR: No memory for host variable





1412 ERROR: Cannot register protocols

Description While initializing the IIOP Server Listener (ISL), an internal error occurred.


1413 ERROR: Hex address type not supported

Description The network address argument to option -n of the IIOP Server Listener/Handler uses the WLE hexadecimal format 0x0002. The IIOP Server Listener/Handler expects the network address argument to be of the form //host:port.

Action Fix the application configuration for the IIOP Server Listener/Handler and make sure the network address has the appropriate format.






1415 WARN: Received a non-GIOP message

Description The IIOP Server Listener/Handler received a non-GIOP message. This can occur when a client application other than an WLE remote client application attempts to connect to the IIOP Server Listener/Handler; for example, a JOLT client application, an ATMI client application, or an http client application. After this message is written to the user log, the IIOP Server Listener/Handler closes the connection with the client application.

Action Make sure that only WLE remote client applications connect to the IIOP Server Listener/Handler.

1420 ERROR: Expected numeric argument to -s option

Description An invalid argument was passed to the ISL command-line option. The argument to the -s option, the server timeout, needs to be numeric. This error causes the IIOP Server Listener not to be booted.

Action Make sure the argument to the -s option is numeric.


1421 ERROR: Expected numeric argument to -u option

Description An invalid argument was passed to the ISL command-line option. The argument to the -u option, the number of outbound IIOP users, needs to be numeric. This error causes the IIOP Server Listener not to be booted.

Action Make sure the argument to the -u option is numeric.




1422 ERROR: Bad -u option

Description The IIOP Server Listener process was invoked with a -u option that specified an option argument outside the allowed range. The -u option specifies the number of outbound IIOP users (native clients or servers) that can be supported simultaneously by each outbound IIOP connection. This option must be greater than 0 but not more than 1024.

Action Make sure the argument to the -u option is between 1 and 1024.


1423 ERROR: Expected numeric argument to -o option

Description An invalid argument was passed to the ISL command-line option. The argument to the -o option, the maximum number of outbound connections, needs to be numeric. This error causes the IIOP Server Listener not to be booted.

Action Make sure the argument to the -o option is numeric.


1424 INFO: host = host_name, port = port_number

Description The IIOP Server Listener is listening on this host and port.

Action None.



1425 ERROR: Bad -o option

Description The IIOP Server Listener process was invoked with an -o option that specified an option argument outside the allowed range. The -o option specifies the maximum number of outbound connections that each ISH may have. This option must be greater than zero but not more than 4096. In addition, the -o option times the maximum number of handlers must be less than 32767.

Action Make sure the argument to the -o option is between 1 and 4096, and that the -M option multiplied by the -o option is less than 32767.


1426 ERROR: -O option must be specified if -o, -s, or -u specified

Description The IIOP Server Listener process was not invoked with the -O option, enable outbound IIOP, when the -o, -s, or -u options were specified. Since the -O option requires a small amount of extra resources, outbound IIOP is not enabled by default.

Action Add the -O option to the ISL command.


1427 ERROR: Error initializing OCM table

Description The IIOP Server Listener could not initialize the data structures used for asymmetric outbound IIOP.

Action The error indicates an internal problem with the IIOP Server Listener. Contact BEA WLE Technical Support.



1428 WARN: No space in ISL shared memory for additional OCM entries

Description The maximum number of outbound IIOP connections, determined by the ISL -o option multiplied by the -M option, has been reached.

Action Raise the maximum number of outbound IIOP connections or add IIOP Server Listeners.


1429 ERROR: Cannot advertise service_name, tperrno = errno

Description The IIOP Server Listener could not advertise the service used for asymmetric outbound IIOP.


1430 ERROR: Cannot unadvertise service_name, tperrno = errno

Description The IIOP Server Listener could not unadvertise the service used for asymmetric outbound IIOP.


1431 ERROR: Invalid arguments, field id field_id not passed

Description Invalid arguments were passed to the IIOP Server Listener.




1432 ERROR: Invalid connection id id

Description An invalid connection id was passed to the IIOP Server Listener.


1433 ERROR: Error binding outbound connection request, can’t create any more handlers

Description The IIOP Server Listener could not start another IIOP Server Handler to process the outbound request.

Action Raise the maximum number of IIOP Server Handlers (ISL -M option).

1434 ERROR: OCM entry could not be added

Description The outbound IIOP connection could not be added to the outbound connection map because the IIOP Server Listener could not start another IIOP Server Handler.

Action Raise the maximum number of IIOP Server Handlers (ISL -M option).

1435 INFO: external host = host_name, port = port_number

Description The IIOP Server Listener stores this host and port in any object references returned to the client. The host and port are determined by the -H option.

Action None.



1436 ERROR: Could not timeout OCM entry

Description An error occurred while timing out an outbound IIOP connection.

Action The error indicates an internal problem with the IIOP Server Listener. Contact BEA Technical Support.

1437 INFO: Host: host_name, Port: port_number connection timed out due to inactivity

Description The IIOP Server Listener has determined that the outbound connection has not been used within the server timeout period (ISL -s option). The connection will be torn down by the IIOP Server Handler.

Action None. If a subsequent request is received for this connection, the connection will be restablished.

1438 ERROR: Sending of request message to server failed

Description While a request message was being sent to a remote server application, the operation failed.

Action Check the user log for messages indicating the nature of the failure. This warning may indicate that the remote server application is no longer accessible (that is, either the network or machine has failed). Contact BEA Technical Support.

1439 ERROR: Missing outbound connection

Description The IIOP Server Handler does not have the necessary outbound connection information to send the request.




1440 ERROR: Could not connect to host/port host_port_address

Description The IIOP Server Handler could not connect to the host and port contained within the object reference.

Action Determine if the remote machine has failed.

1441 INFO: No outstanding request to send reply

Description A reply has been received from the remote server application. There is no corresponding entry on the outstanding request queue. The remote server may have exceeded the timeout period for the request and the entry has already been removed from the queue.

Action Determine if the remote server is processing invocations within the timeout period. Determine if the timeout period is appropriate for your application (BLOCKTIME multiplied by SCANUNIT).

1442 ERROR: Could not add message to blocked queue

Description The IIOP Server Handler could not add the reply from the remote server application on the queue of blocked messages.

Action Examine the userlog for any immediately preceding messages giving further information about the cause of the error. Contact BEA Technical Support.

1443 ERROR: Cannot send reply to caller: error_text

Description The IIOP Server Handler could not send the reply from the remote server application back to the caller (native client or server).

Action Examine the userlog for any immediately preceding messages giving further information about the cause of the error. Contact BEA Technical Support.



1444 ERROR: Invalid outbound IIOP request

Description The IIOP Server Handler received a message without the necessary request information.


1445 INFO: Outbound connection index timed out due to inactivity

Description The outbound connection was not used within the server timeout period (ISL -s option). The connection has been torn down.

Action None. If a subsequent request is received for this connection, the connection will be reestablished.

1446 ERROR: Cannot send oneway reply

Description The IIOP Server Handler could not send a oneway reply to the remote server application.

Action This warning may indicate that the remote server application is no longer accessible (that is, either the network or machine has failed). Contact BEA Technical Support.

1447 ERROR: Cannot decode fragment header

Description The IIOP Server Handler could not decode a fragment header.




1448 ERROR: Cannot copy msg to call buffer: error

Description The IIOP Server Handler could not copy a message to an internal buffer.


1449 ERROR: Cannot send one-way request, one-way method not executed

Description The IIOP Server Handler failed to send a request to the remote server. Since this request is a GIOP 1.0 oneway request, no error can be returned to the caller; instead, the error is logged.

Action Determine why the request could not be sent to the remote server.

1450 ERROR: Error switching to the client’s context

Description The IIOP Server Handler could not switch to the client context.


1451 ERROR: Invalid socket index index

Description The IIOP Server Handler received a message with an invalid socket index.




1452 ERROR: Invalid -s option = value

Description The IIOP Server Listener process was invoked with an -s option that specified an option argument outside the allowed range. The -s option specifies the server timeout in minutes. This option must be greater than 0.

Action Make sure the argument to the -s option is greater than 0.


1453 INFO: Attempting to forward bind to another ISL

Description If the maximum number of outbound IIOP connections, determined by the -o option multiplied by the -M option, is reached, the IIOP Server Listener attempts to forward the request to a different IIOP Server Listener.

Action If the forward is successful, no action is required. If the forward fails, either raise the maximum number of outbound IIOP connections or add IIOP Server Listeners.


CHAPTER

7 Object Transaction Service Messages

Object Transaction Service (OTS) Messages 1000-1005

Note: When Object Tranaction Service messages are listed in the user log (ULOG), the messages have the prefix LIBOTS_CAT. For example, message 1000 is listed as LIBOTS_CAT:1000.

1000 "WARNING: xa_start() failed in pre-prepare phase with error = internalcode."

Description Attempts to call xa_start with the flags value of TMRESUME or TMNOFLAGS failed in the preprepare phase of the transaction life cycle. The transaction will be rolled back.

Action Verify configuration of openinfo for the associated resource manager. Consult error codes described for X/Open CAE Specification.

System Messages 7-1

7 OBJECT TRANSACTION SERVICE MESSAGES

1001 "WARNING: xa_end() failed in pre-prepare phase with error = internalcode."

Description Attempts to call xa_end with the flags value of TMFAIL failed in the preprepare phase of the transaction life cycle. The transaction will be rolled back.

Action Verify configuration of openinfo for the associated resource manager. Consult error codes described for X/Open CAE Specification.

1002 "ERROR: Unable to attach BB ."

Description This message occurs in the server process if the server process was configured in the PROTECTED SYSTEM_ACCESS mode and the process is unable to attach itself to the Bulletin Board.


1003 "ERROR: Unable to lock BB and detach previous BB ."

Description This message occurs in the server process if the server process was configured in the PROTECTED SYSTEM_ACCESS mode and the process is unable to lock and later detach itself from the Bulletin Board.


1004 "ERROR: Unable to lock BB ."

Description This message occurs in the server process if the server process is unable to lock the Bulletin Board.


7-2 System Messages

OBJECT TRANSACTION SERVICE (OTS) MESSAGES 1000-1005

1005 "ERROR: Unable to detach BB ."

Description This message occurs in the server process if server process was configured in the PROTECTED SYSTEM_ACCESS mode and the process is unable to detach itself from the Bulletin Board.


System Messages 7-3

7 OBJECT TRANSACTION SERVICE MESSAGES

7-4 System Messages

CHAPTER

8 C++ TP Framework Messages

C++ TP Framework (TPFW) Messages 1-127

Note: When C++ TP Framework messages are listed in the user log (ULOG), the messages have the prefix LIBTPFW_CAT. For example, message 1 is listed as LIBTPFW_CAT:1.

Note: Messages in the range 1-99 are errors or warnings raised because of user processing. The messages generally indicate a problem in application processing that should be directed to the programmer.

Note: Messages in the range 100 and higher are errors or warnings raised because of system processing.

1 "ERROR: Exception in Server::initialize(): exception id. Reason = reason."

Description Either application code raised an exception in Server::initialize() or application code did not catch an exception raised during processing in Server::initialize(). The exception id is printed with a reason. If the application raised TobjS::InitializeFailed and included a reason string, it is printed here. The server startup processing is halted.

Action Notify the programmer.

System Messages 8-1

8 C++ TP FRAMEWORK MESSAGES

2 "WARN: Exception in Server::release():exception id. Reason = reason."

Description Either application code raised an exception in Server::release() or application code did not catch an exception raised during processing in Server::release(). The exception id is printed with a reason. If the application raised TobjS::ReleaseFailed and included a reason string, it is printed here. Server shutdown processing continues.


3 "INFO: Default Server::initialize() used."

Description The programmer either did not implement Server::initialize(), or called ServerInternal::initialize() explicitly. The default initialization tries to open the default XA resource manager.

Action None

4 "INFO: Default Server::release() used."

Description The programmer did not implement Server::release(), or called ServerInternal::release() explicitly. The default release tries to close the default XA resource manager.

Action None

8-2 System Messages

C++ TP FRAMEWORK (TPFW) MESSAGES 1-127

5 "WARN: TP::deactivateEnable() called in illegal context. Called in Server::initialize() or Server::release()."

Description The application called TP::deactivateEnable outside the context of a CORBA method invocation. This is an illegal call. Processing continues.

Action Notify the programmer. Call to TP::deactivateEnable should be removed from Server::initialize and/or Server::release.

6 "WARN: TP::deactivateEnable() called illegally - object has transaction activation policy."

Description The application called TP::deactivateEnable inside a CORBA method invocation on an object with the transaction activation policy. This is an illegal call. Processing continues.


7 "ERROR: Invoking request - interface not advertised: interfaceName."

Description The object reference invoked by a client is for an interface that is unknown to the system.

Possible reasons are:

t No server is available that can service the interface.

t The server may not have been started yet, or may have been shut down or abnormally terminated.

The factory that created the object reference specified an invalid interface name. The interface name specified in the call to TP::create_object_reference must correspond exactly to the interface name specified in the OMG IDL file for the CORBA object. This interface name is usually the OMG interface repository ID.

Action Check the status of the interface. It may be suspended. If you cannot find the interface in the system, notify the programmer.

System Messages 8-3


8 "WARN: Application didn’t catch TobjS exception. TP Framework throwing CORBA::BAD_OPERATION."

Description The system caught an exception defined in the TobjS idl module after invoking a method of a CORBA object.

This warning indicates that either:

t The application raised an exception defined in TobjS idl within the method invocation, which is not allowed because the exceptions defined in this module are for use by servers only and should not be returned to clients.

t The application did not handle an exception defined in TobjS.idl that was thrown by a system call.

In either case, the system converts the exception to CORBA::BAD_OPERATION before returning the exception to the client.


9 "WARN: Application called TP::deactivateEnable() illegally and didn’t catch TobjS exception."

Description The system caught a TobjS::IllegalOperation exception after a method invocation.

The possible reasons are:

t The application raised a TobjS::IllegalOperation exception, which is not allowed because this exception is reserved for use by the WLE software.

t The application called TP::deactivateEnable() illegally (most likely in an object with transaction activation policy) and did not handle the exception.


8-4 System Messages


11 "ERROR: Non-transactional invocation on CORBA object infected with a transaction."

Description An invocation was made without an active transaction on an object that is participating in a global transaction. This error can occur if a client sends a request to a CORBA object that is participating in a transaction started for another client. It can also occur if a call is made immediately after a transaction has been marked for rollback only. There is a small delay while the transaction-termination processing is completed by the transaction manager when the transaction is still active. This error is generally detected in a for loop that invokes the same object repeatedly for different transactions.

Action If many such messages are seen, notify the programmer. If loop processing is being done, sleep() for a short time between invocations.

12 "ERROR: Invalid gtrid when invoking {active|inactive}{transaction|method|process} - bound CORBA object infected with a transaction."

Description A client tried to invoke a CORBA object already infected by a transaction with a different transaction ID than the one it was originally processing. This error can occur if a client sends a request to a CORBA object that is participating in a transaction started for another client. It can also occur if a call is made immediately after a transaction has been marked for rollback only. There is a small delay while the transaction termination processing is completed by the transaction manager when the transaction is still active. This error is generally detected in a for loop that invokes the same object repeatedly for different transactions.


System Messages 8-5


21 "ERROR: Illegal recursive call on CORBA Object. Interface = interfaceName, OID = object ID."

Description A recursive call was made on a CORBA object. This error occurs if, for example, a client calls object A, which calls object B, which uses an object reference to object A to invoke a method of object A. The second call to object A causes this error message to be printed to the user log and a CORBA::OBJ_ADAPTER exception to be returned to the calling client (in this case, object B).


22 "ERROR: Activating object - application raised TobjS::OutOfMemory. Interface = interfaceName, OID = object ID."

Description The system caught TobjS::OutOfMemory raised by either Server::create_servant or Tobj_ServantBase::activate_object. This error may have occurred because the application did not catch this exception when it was thrown either by a WLE system call or by application code.

Action This error may indicate that all available memory for the process has been exhausted. Ensure that operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.

23 "ERROR: Activating object - application raised TobjS::CreateServantFailed. Reason = reason. Interface = interfaceName, OID = object ID."

Description The application raised TobjS:CreateServantFailed with the reason string supplied.

Action Application dependent. Notify your company’s technical support or the application programmer.

8-6 System Messages


n

n

24 "ERROR: Activating object - application raised TobjS::ActivateObjectFailed. Reason = servicename. Interface = interfaceName, OID = object ID."

Description The system caught TobjS::ActivateObjectFailed raised by either Server::create_servant or Tobj_ServantBase::activate_object. The application raised TobjS::ActivateObjectFailed with the reason string supplied.


25 "ERROR: Activating object - CORBA Exception not handled by application. Exception ID = exception ID. Interface = InterfaceName, OID = object ID."

Description The system caught a CORBA exception raised by either Server::create_servant or Tobj_ServantBase::activate_object.

Action Application dependent. Notify your company’s technical support or the applicatioprogrammer.

26 "ERROR: Activating object - Unknown exception not handled by application Interface = InterfaceName, OID = object ID. "

Description The system caught an unknown exception raised by either Server::create_servant or Tobj_ServantBase::activate_object.


System Messages 8-7


n

n

27 "ERROR: De-activating object - application raised TobjS::DeactivateObjectFailed. Reason = reason Interface = interfaceName, OID = object ID."

Description The system caught a TobjS::DeactivateObjectFailed exception raised in Tobj_ServantBase::deactivate_object.


28 "ERROR: De-activating object - CORBA Exception not handled by application. Exception ID = exception ID. Interface = InterfaceName, OID = object ID."

Description The system caught a CORBA exception raised in Tobj_ServantBase::deactivate_object.


29 "ERROR: De-activating object - Unknown exception not handled by application Interface = InterfaceName, OID = object ID."

Description The system caught an unknown exception raised in Tobj_ServantBase::deactivate_object.


8-8 System Messages


100 "ERROR: Couldn’t open XA resource manager in default Server::initialize(). tperrno = internalcode."

Description The default implementation of Server::initialize() failed to open the default XA resource manager for the server group. The tperrno function specifies the error returned.

Action Verify configuration of openinfo for the associated resource manager. Consult error codes described for tx_open(3).

See Also tx_open(3).

101 "ERROR: Couldn’t close XA resource manager in default Server::release(). tperrno = internalcode."

Description The default implementation of Server::release() failed to close the default XA resource manager for the server group. The tperrno function specifies the error returned.

Action Consult error codes described for tx_close(3).

See Also tx_close(3).

102 "ERROR: TP::create_object_reference() couldn’t create object reference for: Interface = servicename OID = servicename."

Description An internal exception was raised when an object reference for the specified interface and object ID was created.


System Messages 8-9


103 "ERROR: TP::[register | unregister]_factory() couldn’t register factory. Registrar service not available. Check status of FactoryFinder server(s)."

Description The register or unregister factory operation failed because the FactoryFinder server or an associated server was not available.

Action Verify that the FactoryFinder and all associated servers are available.

See Also Administration Guide online document.

104 "ERROR: TP::servicename_factory() cannot proceed due to unexpected problem with Registrar. Check status of FactoryFinder server(s)."

Description An internal exception was raised when a factory was being registered or unregistered.


See Also Administration Guide online document.

106 "ERROR: Invoking request - couldn’t get: resource."

Description An internal problem was encountered when the specified resource was being retrieved.


107 "ERROR: Invoking request - no context."

Description An internal problem was encountered.




108 "ERROR: Invoking request - unexpected exception."



109 "ERROR: After invoking request - couldn’t get: resource. "

Description An internal problem was encountered when the specified resource was being retrieved.


110 "ERROR: After invoking request - no context."



111 "ERROR: After invoking request - interface not advertised: interfaceName."





112 "ERROR: After invoking request - unexpected exception."



113 "ERROR: Activating object - out of memory. Interface = interfaceName, OID = Object ID."

Description The system could not obtain sufficient memory to activate the specified object.


116 "ERROR: Activating object - Internal map error. Interface = servicename, OID = servicename."



118 "ERROR: No local gtrid or local gtrid doesn’t match global gtrid."





119 "ERROR: Invoking process-bound object - transaction table inconsistency."



120 "ERROR: Invalid activation policy."



121 "ERROR: Couldn’t set tran sync."



122 "ERROR: Couldn’t set gtrid."



123 "ERROR: Couldn’t set deref."





124 "ERROR: Couldn’t set tran sync ..."



125 "ERROR: Couldn’t set gtrid ..."



126 "ERROR: Couldn’t set deref ..."



127 "ERROR: Context stack out of memory. System throws TobjS::OutOfMemory exception."

Description The system could not obtain sufficient memory to manage an internal stack.




178 "WARN: TP::create_active_object_reference() called illegally - object does not have process activation policy."

Description TP::create_active_object_reference was called on an interface that does not have process activation policy.

Action Change the interface to have process activation policy.

179 "WARN: TP::deactivateEnable() called illegally - object does not have process activation policy."

Description TP::deactivateEnable was called on an object that does not have process activation policy.

Action Change the interface of the object to have process activation policy.

180 "ERROR: TP::create_object_reference() couldn’t create object reference for: Interface = %s OID = %.256s"

Description An exception occurred while calling TP::create_object_reference. The object reference could not be created.

Action Check the user log for messages indicating the nature of the failure. Contact BEA Technical Support.


CHAPTER

9 Java TP Framework Messages

Java TP Framework Messages 1-66

Note: When Java TP Framework messages are listed in the user log (ULOG), the messages have the prefix IJTPFW_CAT. For example, message 1 is listed as IJTPFW_CAT:1.

1 "ERROR: Missing ORB argument to Tobj_Bootstrap"

Description An attempt to create the Tobj_Bootstrap object failed because the orb argument passed to the Tobj_Bootstrap constructor was empty.

Action Make sure that the orb argument that was passed to the Tobj_Bootstrap constructor is not empty.

2 "ERROR: Cannot find class {0}"

Description An attempt to create the Tobj_Bootstrap object failed because the class name in {0} could not be found.

Action Make sure that the corresponding WLE Java .jar file is included in the class path.

System Messages 9-1

9 JAVA TP FRAMEWORK MESSAGES

3 "ERROR: Cannot instantiate delegate bootstrap"

Description An attempt to create the Tobj_Bootstrap object failed while attempting to invoke its constructor.


4 "ERROR: Cannot execute delegate bootstrap constructor"

Description An attempt to create the Tobj_Bootstrap object failed while attempting to execute its constructor.


5 "ERROR: Cannot access delegate bootstrap constructor"

Description An attempt to create the Tobj_Bootstrap object failed while attempting to access its constructor.


6 "ERROR: No cached reference to FactoryFinder found"

Description An attempt to call resolve_initial_references("FactoryFinder") failed because the Bootstrap object could not locate any cached references to the FactoryFinder object.


9-2 System Messages

JAVA TP FRAMEWORK MESSAGES 1-66

7 "ERROR: No cached reference to InterfaceRepository found"

Description An attempt to call resolve_initial_references("InterfaceRepository") failed because the Bootstrap object could not locate any cached references to the InterfaceRepository object.


8 "ERROR: Underlying ORB unable to resolve a reference to FactoryFinder "

Description An attempt to call resolve_initial_references("FactoryFinder") failed because the underlying ORB was unable to internally resolve a reference to the FactoryFinder object.


9 "ERROR: Underlying ORB unable to resolve a reference to InterfaceRepository "

Description An attempt to call resolve_initial_references("InterfaceRepository") failed because the underlying ORB was unable to internally resolve a reference to the InterfaceRepository object.


10 "ERROR: Invalid data exchange between application and infrastructure threads"

Description The underlying ORB was unable to exchange data between the application and the infrastructure threads while attempting to boot or process incoming requests.


System Messages 9-3


13 "ERROR: Calling infrastructure from other thread in single-threaded mode"

Description In a single-threaded environment, an attempt was made to call the infrastructure thread from a separate thread.


15 "ERROR: Cannot call infrastructure when no call is active"

Description An attempt was made to call the infrastructure thread, when the infrastructure thread was not in a state expecting any incoming calls.


16 "INFO: Threading level is Single-Threaded (level 0)"

Description This is an informational message to the user indicating that the threading level in the booted server process is single-threaded.

Action None.

17 "INFO: Threading level is Multi-Threaded/Serialized outgoing requests (level 1)"

Description This is an informational message to the user indicating that the threading level in the booted server process is multithreaded/serialized outgoing requests.

Action None.

9-4 System Messages


18 "WARN: Invalid threading level {0}. Defaulting to level 0"

Description This is a warning to the user that an attempt was made to boot the server process with a threading level indicated in {0}. However, the system overrides this threading level so that the server process boots in a single-thread environment.

Action None.

19 "ERROR: Cannot load libij, exception:{0}"

Description An attempt to load the library libij by the Java Virtual Machine failed. The {0} value contains details of the exception returned to the Java Virtual Machine.

Action Try to resolve the problem based on the exception returned to the Java Virtual Machine. Otherwise, contact BEA Customer Support.

20 "ERROR: Invalid empty argument list"

Description An attempt was made to boot the server process with an invalid empty argument list.

Action Make sure that the UBBCONFIG file has the appropriate arguments corresponding to the server process entry.

21 "ERROR: Missing argument after -M option"

Description An attempt was made to boot the server process with an empty argument after the -M option.


System Messages 9-5


22 "ERROR: Invalid option:{0}"

Description An attempt was made to boot the server process with an invalid option specified in {0}.


23 "ERROR: Missing .jar file"

Description An attempt was made to boot the server process with a missing .jar file in the argument list.


24 "ERROR: Invalid thread level:{0}"

Description An attempt was made to boot the server process with an invalid value corresponding to the thread level argument.


25 "INFO: Loading {0}"

Description This is an informational message indicating that the Java Virtual Machine is now loading the .jar file specified in {0}.

Action None.

9-6 System Messages


26 "ERROR: Invalid M3 file {0} : missing {1}"

Description An attempt was made to boot the server process with an invalid file specified in {0}. The {1}value indicates the file that was missing that prevented a successful boot.

Action Make sure that the corresponding XML file for the server process has the appropriate values.

27 "ERROR: No M3-Server entry in {0}"

Description An attempt was made to boot the server process with no M3-server entry existing in the file specified in {0}.

Action Make sure that the corresponding XML file for the server process has the appropriate values.

28 "ERROR: server_init failed"

Description An attempt to boot the server process failed due to an internal error in the ORB.


29 "ERROR: ServerMain.init received exception:{0}"

Description An attempt to boot the server process failed due to an internal error in the ORB. The {0} value provides details of the exception returned.


System Messages 9-7


30 "ERROR: ServerMain.service received exception:{0}"

Description An attempt to process an incoming request failed due to an internal error in the ORB. The {0} value provides details of the exception returned.


31 "ERROR: ServerMain.release received exception:{0}"

Description An attempt to shut down the server process failed due to an internal error in the ORB. The {0} value provides details of the exception returned.


32 "ERROR: Out of memory"

Description An attempt to allocate space for internal data structures failed because the server process ran out of memory.


9-8 System Messages


34 "INFO: Total application factory shutdown assumed."

Description A server application is attempting to unregister an application factory during Server.release(). The server detects a problem with the unregister operation at this time. Upon further investigation, the server discovers that the entire application is shutting down. As a result, the unregister attempt silently fails because the NameManagers also shut down.

Action None.

35 "WARN: Posting failed; Slave NameManagers may become out of sync."

Description The master NameManager failed to post an update message to the SystemEventBroker, brought about by either a register_factory or an unregister_factory method. Therefore, the SystemEventBroker cannot notify any slave NameManagers. As a result, the slave’s factory name mapping may lose synchronization with the master.

Action First check to ensure that the SystemEventBroker is running. Second, ensure that there is a communications path between the SystemEventBroker and the master NameManager. Lastly, shut down and restart the slave NameManagers. On reboot, the slave NameManagers obtain a new copy of the factory name mapping from the master NameManager.

36 "ERROR: Could not open XA resource manager in default Server.initialize(). error = {0}"

Description An attempt to open the XA resource manager in the default Server.initialize() failed. The {0} value provides details of the error value returned.

Action Take corrective action based on the error value returned.

System Messages 9-9


37 "ERROR: Could not close XA resource manager in default Server.release(). error = {0}"

Description An attempt to close the XA resource manager in the default Server.release() failed. The {0} value provides details of the error value returned.

Action Take corrective action based on the error value returned.

38 "ERROR: TP.create_object_reference() could not create object reference for: Interface = {0} OID = {1}"

Description An internal exception was raised when an object reference for the specified interface and object ID was created. The {0} and {1} values provide details about the interface and the OID, respectively.


39 "ERROR: TP.{0}_factory() could not register factory. Registrar service not available. Check status of FactoryFinder server(s)."

Description The register_factory() or unregister_factory() method failed because the FactoryFinder server or an associated server was not available. The {0} value provides details about whether the call to register or unregister the factory was made.




40 "ERROR: TP.{0}_factory() cannot proceed due to unexpected problem with Registrar. Check status of FactoryFinder server(s)."

Description An internal exception was raised when a factory was being registered or unregistered. The {0} value provides details about whether the call to register or unregister the factory was made.


41 "WARN: TP.deactivateEnable() called in illegal context. Called in Server.initialize() or Server.release()."

Description The application called TP.deactivateEnable() outside the context of a CORBA method invocation. This is an illegal call. Processing continues.

Action Notify the programmer. The call to TP.deactivateEnable should be removed from Server.initialize() and/or Server.release().

42 "WARN: TP.deactivateEnable() called illegally - object has transaction activation policy."

Description The application called TP.deactivateEnable() inside a CORBA method invocation on an object with the activation policy set to transaction. This is an illegal call. Processing continues.


43 "ERROR: ORB init failed, exception returned:{0}"

Description An attempt to initialize the ORB during server boot time failed. The {0} value provides details of the exception returned.




44 "ERROR: Could not find root POA, exception returned:{0}"

Description An attempt to initialize the ORB during server boot time failed because the root Portable Object Adapter (POA) could not be found. The {0} value provides details of the exception returned.


45 "ERROR: Could not create child POA, exception returned:{0}"

Description An attempt to initialize the ORB during server boot time failed because the child Portable Object Adapter (POA) could not be created. The {0} value provides details of the exception returned.


46 "ERROR: Cannot set default servant, exception returned:{0}"

Description An attempt to initialize the ORB during server boot time failed because the default servant could not be set for the Portable Object Adapter (POA). The {0} value provides details of the exception returned.


47 "ERROR: Exception in Server.initialize(): {0}. Reason = {1}"

Description During server boot time, an exception was thrown in Server.initialize(). The {0} and {1} values provide details of the exception returned.

Action Take corrective action based on the exception returned.



48 "ERROR: Exception in Server.initialize(): {0}. Reason = unknown"

Description During server boot time, an exception was thrown in Server.initialize(). The {0} value provides details of the exception returned.

Action Take corrective action based on the exception returned. Otherwise, contact BEA Customer Support.

49 "WARN: Exception in Server.release(): {0}. Reason = {1}"

Description During server shutdown, an exception was thrown in Server.release(). The {0} and {1} values provide details of the exception returned. Processing continues.


50 "WARN: Exception in Server.release(): {0}. Reason = unknown"

Description During server shutdown, an exception was thrown in Server.release(). The {0} value provides details of the exception returned. Processing continues.


51 "INFO: Default Server.initialize() used."

Description The programmer either did not implement Server.initialize(), or called ServerInternal.initialize() explicitly. The default initialization tries to open the default XA resource manager.

Action None.



52 "INFO: Default Server.release() used."

Description The programmer either did not implement Server.release(), or called ServerInternal.release() explicitly. The default release tries to close the default XA resource manager.

Action None.

53 "ERROR: Illegal recursive call on CORBA Object. Interface = {0} OID = {1}"

Description A recursive call was made on a CORBA object. This error occurs if, for example, a client calls object A, which calls object B, which uses an object reference to object A to invoke a method of object A. The second call to object A causes this error message to be printed to the user log and a CORBA.OBJ_ADAPTER exception to be returned to the calling client (in this case, object B). The {0} and {1} values provide details of the interface and OID, respectively.


54 "ERROR: Cannot find activation policy of interface"

Description The TP Framework was not able to find the activation policy of an interface on which an incoming request was made.




55 "ERROR: Non-transactional invocation on CORBA object infected with a transaction"

Description An invocation was made without an active transaction on an object that is participating in a global transaction. This error can occur if a client sends a request to a CORBA object that is participating in a transaction started for another client. It can also occur if a call is made immediately after a transaction has been marked for rollback only. There is a small delay while the transaction-termination processing is completed by the transaction manager when the transaction is still active. This error is generally detected in a for loop that invokes the same object repeatedly for different transactions.


56 "ERROR: Invoking request - unexpected exception"



57 "ERROR: Activating object - application raised TobjS.CreateServantFailed. Reason = {0} Interface = {1} OID = {2}"

Description The application raised TobjS.CreateServantFailed with the reason string supplied. The {0}, {1}, and {2} values provide details of the reason code, the interface, and the OID, respectively.

Action Application dependent.



58 "ERROR: Activating object - Exception not handled by application. Interface = {0} OID = {1}"

Description The system caught an exception while activating the object that was not handled by the application. The {0} and {1} values provide details of the interface and the OID, respectively.

Action Application dependent. Notify the user.

59 "ERROR: Activating object - application raised TobjS.OutOfMemory. Interface = {0} OID = {1}"

Description The system caught TobjS.OutOfMemory while activating the object. This error may have occurred because the application did not catch this exception when it was thrown either by a WLE system call or by application code. The {0} and {1} values provide details of the interface and the OID, respectively.

Action This error may indicate that all available memory for the process has been exhausted. Ensure that the operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine or increase the amount of physical memory on the machine.

60 "ERROR: Activating object - application raised TobjS.ActivateObjectFailed. Interface = {0} OID = {1}"

Description The system caught TobjS.ActivateObjectFailed exception raised while activating the object. The {0} and {1} values provide details of the interface and the OID, respectively.

Action Application dependent.



61 "ERROR: Activating object - exception not handled by application. Interface = {0} OID = {1}"

Description The system caught an exception while activating the object that was not handled by the application. The {0} and {1} values provide details of the interface and the OID, respectively.


62 "ERROR: De-activating object - application raised TobjS.DeactivateObjectFailed. Interface = {0} OID = {1} Reason = {2}"

Description The system caught a TobjS.DeactivateObjectFailed exception raised while deactivating the object. The {0} and {1} values provide details of the interface and OID, and reason code, respectively.


63 "ERROR: De-activating object - Exception not handled by application. Interface = {0} OID = {1}"

Description The system caught an exception while deactivating the object that was not handled by the application. The {0} and {1} values provide details of the interface and OID, respectively.


64 "ERROR: Invoking request - could not get: InterfaceID"

Description An internal problem occurred in the ORB while trying to access the interface.




65 "ERROR: Invoking request - could not get: OID"

Description An internal problem occurred in the ORB while trying to access the OID.


66 "ERROR: Activating object - Internal map error. Interface = {0}, OID = {1}"

Description An internal problem was encountered in the ORB while activating the object. The {0} and {1} values provide details of the interface and the OID, respectively.



CHAPTER

10 Interface Service Map Messages

Interface Service Map (ISM) Messages 4000-4030

Note: When Interface Service Map messages are listed in the user log (ULOG), the messages have the prefix LIBISM_CAT. For example, message 4000 is listed as LIBISM_CAT:4000.

4000 "WARN: duplicate interface servicename passed in to be advertised..."

Description An interface having the same Interface ID has already been registered with the WLE infrastructure.

Action Check the application server code for any interface being specified more than once.


10 INTERFACE SERVICE MAP MESSAGES

4001 "WARN: interface ID servicename longer than max length allowed, truncating to number bytes..."

Description The specified interface has an Interface ID longer than the allowed limit.

Action Shorten the Interface ID length to allowed length.

4002 "WARN: Implementation ID servicename of interface servicename longer than max length allowed, truncating to number bytes..."

Description The specified interface has an Implementation ID longer than the allowed limit.

Action Shorten the Implementation ID length to allowed length.

4003 "ERROR: Memory allocation failure"

Description The server process could not allocate virtual memory.

Action Either reduce the memory usage on the machine or add more memory. Try increasing space on the swap device.

4004 "ERROR: Internal error, could not determine address of default ORB function."

Description The server has encountered an internal error while registering it’s interfaces with the WLE infrastructure. Contact BEA Customer Support.



INTERFACE SERVICE MAP (ISM) MESSAGES 4000-4030

4005 "ERROR: Internal error, could not set TMPROC values."

Description The server has encountered an internal error while registering its interfaces with the WLE infrastructure.


4006 "ERROR: Internal error, could not get parameters for interface servicename"



4008 "ERROR: Internal error, could not advertise interfaces..."



4009 "ERROR: Interface servicename’s policies not consistent across Group Group, could not advertise interfaces..."

Description The specified interface is being offered by another server in the specified group with different deactivation or transaction policies. This is not allowed.

Action Make sure all instances of the interface across all servers in the group have the same activation and transaction policies.



4010 "ERROR: Bulletin Board limit reached, could not advertise interfaces..."

Description Maximum number of interfaces in the application (as specified by the MAXINTERFACES parameter in the RESOURCES section of the UBBCONFIG file) has been reached. No more interfaces can be offered.

Action Increase this parameter to a higher value. This can be done at run time using the TMIB API or tmconfig. For more information, see the BEA TUXEDO System Reference Manual and Administration Guide.

4011 "ERROR: [NULL interface name used to get interface information]"






4016 "ERROR: Interface parameter error in internal routine"





4017 "ERROR: Invalid interface information passed to internal routine"



4018 "ERROR: Memory allocation failure."



4020 "ERROR: tmrsvrs() returned multiple servers."



4023 "ERROR: Invalid interface information passed to internal routine"

Description The server has encountered an internal error while unregistering interfaces with the WLE infrastructure.




4024 "ERROR: invalid service name found"

Description The server has encountered an internal error while reading the WLE Bulletin Board.


4026 "ERROR: Internal error, could not set policies for interface servicename"



4027 "ERROR: [Memory allocation failure.]"



4028 "ERROR: Memory allocation failure."








4030 "WARN: Interface servicename’s transaction policy setting of \"IGNORE\" or \"NEVER\" conflicts with \"AUTOTRAN=Y\" setting in UBBCONFIG file, turning off AUTOTRAN setting..."

Description An interface has its transaction policy set to either IGNORE or NEVER, but its entry in the UBBCONFIG file has AUTOTRAN set to Y, which is contradictory. This AUTOTRAN flag is turned off internally.

Action Change either the setting in the UBBCONFIG file or the policy setting in the ICF file so that they both match.


CHAPTER

11 Java XML Parser Messages

Java XML Parser Messages 1-81

Note: When Java XML parser messages are listed in the user log (ULOG), the messages have the prefix IJXML_CAT. For example, message 1 is listed as IJXML_CAT:1.

1 "INFO: 1 warning"

Description There was one warning during the execution of buildjavaserver. The warning was reported in a previous message.

Action None.

2 "INFO: {1} warnings"

Description There were multiple warnings during the execution of buildjavaserver. The warnings were reported in previous messages. The {1} value is replaced with the number of warnings.

Action None.


11 JAVA XML PARSER MESSAGES

3 "INFO: 1 error"

Description There was one error during the execution of buildjavaserver. The error was reported in a previous message. No output files were generated.

Action Fix the error and execute buildjavaserver again.

4 "INFO: 1 error, 1 warning"

Description There was one error and one warning during the execution of buildjavaserver. The error and the warning were reported in a previous message. No output files were generated.


5 "INFO: 1 error, {1} warnings"

Description There was one error and multiple warnings during the execution of buildjavaserver. The error and the warnings were reported in a previous message. No output files were generated. The {1} value is replaced with the number of warnings.


6 "INFO: {0} errors"

Description There were multiple errors during the execution of buildjavaserver. The errors were reported in a previous message. No output files were generated. The {0} value is replaced by the number of errors.

Action Fix the errors and execute buildjavaserver again.


JAVA XML PARSER MESSAGES 1-81

7 "INFO: {0} errors, 1 warning"

Description There were multiple errors and one warning during the execution of buildjavaserver. The errors and the warning were reported in a previous message. No output files were generated. The {0} value is replaced with the number of errors.


8 "INFO: {0} errors, {1} warnings"

Description There were multiple errors and multiple warnings during the execution of buildjavaserver. The errors and the warnings were reported in a previous message. No output files were generated. The {0} value is replaced with the number of errors. The {1} value is replaced with the number of warnings.


9 "ERROR: Missing argument to -s option"

Description The -s option to buildjavaserver must be followed by a search path similar to a Java class path. This argument was not specified on the command line.

Action Add the search path argument to the command line and run buildjavaserver again.

10 "ERROR: Invalid option {0}"

Description An invalid option was passed to buildjavaserver.

Action See the Java Programming Reference for the list of valid options to buildjavaserver, fix the command line, and run the command again.



11 "ERROR: Missing input file argument"

Description The last command line argument to buildjavaserver must be the name of an XML input file. That name is missing.

Action Add the input file name argument to the command line and run buildjavaserver again.

12 "ERROR: Cannot open {0}"

Description The XML input file {0} could not be opened for reading. No output file will be generated.

Action Make sure the input file {0} exists and is readable.

13 "ERROR: Unexpected EOF"

Description The XML parser reached the end of file unexpectedly. No output file will be generated.

Action Fix the XML syntax of the input file.

14 "ERROR: Unexpected {0}"

Description The XML parser found an unexpected token in the source. The {0} value is replaced by the token. Depending on the situation, parsing will continue after reporting the error or will stop immediately. In any case, no output file will be generated.



15 "ERROR: I/O Error"

Description An I/O error occurred reading the XML input file. This is a fatal error. No more processing is attempted. No output file will be generated.

Action Check the XML input file for read access, bad blocks, locks, and so forth.

16 "WARNING: Illegal -- in comment"

Description It is illegal to have a double dash (--) in an XML comment, except to introduce the end of comment -->.

Action This is a warning. However, the comment should be fixed, because other XML parsers could reject the input.

17 "ERROR: End of file in comment"

Description The end of file was reached in a comment.

Action Look for any nonterminated comments in the input file.

18 "ERROR: Invalid character sequence <!-{0}"

Description The character {0} is not valid after <!-. The XML parser for buildjavaserver only supports <!-- to start comments.


19 "ERROR: Unexpected character {0} after <!{1}"

Description A non-white-space character is present after <!{1}. The {1} value can be either ENTITY or DOCTYPE.


20 "ERROR: Unsupported keyword {0}"

Description A <! is followed by a keyword that was neither ENTITY nor DOCTYPE. The {0} value is replaced with the offending keyword.


21 "ERROR: Unsupported processing instruction {0}"

Description A <? can be followed only by xml. The {0} value is replaced with the three characters at the beginning of the offending word.


22 "ERROR: Unexpected {0} after </"

Description An invalid character (such as a white-space character) follows </.


23 "ERROR: Unexpected {0} after </{1}"

Description An element closing tag must end with >. An invalid character (such as a white-space character) follows </{1}. The {1} value is replaced with the keyword in the closing tag.




24 "ERROR: Unexpected </{0}> closing tag"

Description The {0} value is an unknown element tag.


25 "ERROR: Unexpected {0} after <"

Description An invalid character (such as a white-space character) follows a <. The {0} value is replaced with the offending character.


26 "ERROR: Unexpected <{0}> element"

Description The {0} value is an unknown element tag.


27 "ERROR: Unexpected {0} after ?"

Description The {0} value is an invalid character after the question mark character (?). Only > can follow a ?.


28 "ERROR: Unexpected {0} after /"

Description The {0} value is an invalid character after /. Only > can follow a /, except in an element closing tag.




29 "ERROR: Missing XML declaration"

Description Every XML document must begin with an XML declaration<?xml version="1.0"?>.


30 "ERROR: Unexpected {0} in XML declaration"

Description Only the version declaration is valid in the XML declaration. The {0} value is replaced with the offending declaration keyword.


31 "ERROR: Missing = after version in XML declaration"

Description The version declaration must be followed by the = sign in the XML declaration.


32 "ERROR: Only supported version of XML is 1.0"

Description The only version recognized by the XML parser is 1.0.


33 "ERROR: Missing end of XML declaration"

Description The ?> is missing at the end of the XML declaration.




34 "ERROR: Invalid value {0} for {1}"

Description Value {0} is invalid for attribute or entity {1}.


35 "ERROR: Cannot load class {0}"

Description buildjavaserver failed to load class {0}.

Action Make sure class {0} can be reached from the CLASSPATH or from the search path specified with the -s option to buildjavaserver.

36 "ERROR: Unexpected ENTITY definition {0}"

Description The only two entities that can be redefined in the internal subset are transaction_policy and activation_policy. The {0} value is replaced with the unexpected ENTITY name.


37 "ERROR: Unexpected {0} in internal subset"

Description Only entities can be redefined in the internal subset. The {0} value is the start of a nonentity definition.


38 "WARNING: Missing DOCTYPE. Assuming M3-SERVER"

Description No <!DOCTYPE declaration was specified in the XML file. buildjavaserver assumes that the document is of type M3-SERVER.

Action None.



39 "ERROR: Only supported document type is M3-SERVER"

Description When specifying a DOCTYPE declaration in the XML file, the document type must be M3-SERVER.


40 "ERROR: Expected SYSTEM after M3-SERVER"

Description The M3-SERVER DTD has no URL. The DOCTYPE declaration must always use the SYSTEM identifier.


41 "ERROR: Expected "m3.dtd" after SYSTEM"

Description The string after SYSTEM in the DOCTYPE must be "m3.dtd".


42 "ERROR: Unexpected {0} at end of DOCTYPE"

Description The DOCTYPE declaration must end with >. The {0} value is replaced with the offending character.


43 "ERROR: Expected <M3-SERVER> tag instead of {0}"

Description The document tag must be M3-SERVER. The {0} value is replaced with the name of the offending tag.




44 "ERROR: Cannot find directory for {0}"

Description The absolute pathname for file. The {0} value cannot be retrieved.

Action Make sure there are no access restrictions for the current user on the directory.

45 "ERROR: Invalid attribute {0} in <{1}>"

Description The attribute name {0} is invalid for element {1}.


46 "ERROR: Unexpected {0} in <{1}>"

Description The token {0} is unexpected in element {1}.


47 "ERROR: The <ARCHIVE> tag must appear last in <M3-SERVER>"

Description If the <ARCHIVE> element is specified in an XML input file, the element must be the last one inside an <M3-SERVER> element.

Action Move the archive element to the end of the <M3-SERVER> element.

48 "ERROR: Only one <ARCHIVE> tag allowed in <M3-SERVER>"

Description Only one archive element is allowed inside an <M3-SERVER> element.

Action Remove the duplicate archive element.



49 "ERROR: Unexpected {0} in <M3-SERVER>"

Description The element {0} is invalid in an <M3-SERVER> element.


50 "WARNING: No server-implementation in <M3-SERVER>. Defaulting to ’com.beasys.Tobj.Server’"

Description If no server-implementation attribute is present in the <M3-SERVER> element, buildjavaserver defaults to com.beasys.Tobj.Server.

Action None.

51 "WARNING: No server-descriptor-name in <M3-SERVER>. Defaulting to Server.ser"

Description If no server-descriptor-name attribute is present in the <M3-SERVER> element, buildjavaserver defaults to Server.ser.

Action None.

52 "ERROR: Cannot create file {0}"

Description The file {0} cannot be created. The file is either the server descriptor or a temporary file created when preparing the archive.

Action Make sure there is no permission problem that may inhibit the creation of the file (such as an existing read-only file already in the same directory), and that the file system is not out of resources.

53 "ERROR: Multiple occurrences of {0} in <{1}>"

Description There is more than one occurrence of attribute {0} in element {1}.



Action Remove extra occurrence(s).

55 "ERROR: Missing attribute {0} in <{1}>"

Description There is no occurrence of the required attribute {0} in element {1}.

Action Add the missing attribute.

56 "ERROR: Redefinition of {0}"

Description The {0} value is being redefined as a different object. For instance, it was initially defined as a module, and it is now defined as in implementation, and vice versa.

Action Remove the extraneous definition.

57 "WARNING: <MODULE> {0} is empty"

Description Module {0} does not contain any implementations and could be removed from the XML file.

Action None.

58 "ERROR: Unexpected {0} at end of <{1}>"

Description This message is generated if a module or an archive definition does not end with the matching closing tag (for example, </ARCHIVE> for an archive). This message is also generated if an implementation element definition that does not end with /> (that is, as an empty tag) is not followed immediately with an implementation closing tag </IMPLEMENTATION>.




60 "WARNING: File {0} already in archive {1} as {2}. Ignoring duplicate"

Description The file {0} is already in the archive {1}, coming from {2}, where {2} is either a full path name or a name inside a ZIP or JAR archive. The redefinition is ignored.

Action None.

61 "ERROR: Cannot find class file for {0}"

Description The class file for class {0} cannot be found on the search path.

Action Make sure the search path is correct. Check that the class name is correct.

62 "ERROR: Directory {0} not found"

Description The directory {0} cannot be found. The {0} value is created by the concatenation of a prefix and a name in a <DIRECTORY> element.

Action Make sure there are no access restrictions for the current user on the directory and that the name is spelled correctly.

63 "ERROR: {0} is not a directory"

Description The {0} value is not a directory. The {0} value is created by the concatenation of a prefix and a name in a <DIRECTORY> element.

Action Make sure the name is spelled correctly.



64 "ERROR: File {0} not found"

Description The file {0} cannot be found. The {0} value is created by the concatenation of a prefix and a name in a <FILE> element.

Action Make sure there are no access restrictions for the current user on the file and that the file name is spelled correctly.

65 "ERROR: {0} is not a regular file"

Description The {0} value is not a regular file. The {0} value is created by the concatenation of a prefix and a name in a <FILE> element.

Action Make sure the file name is spelled correctly.

66 "ERROR: Package {0} not found"

Description No class files could be found in Java package {0}. The {0} value comes from a <PACKAGE> or a <PACKAGE-RECURSIVE> element.

Action Make sure the class files for the packages can be found on the search path and that the package name is spelled correctly.

67 "ERROR: No classes in anonymous package"

Description No class files could be found for the anonymous package (that is, classes whose source file does not include a package statement). This message is generated when processing the <PACKAGE-ANONYMOUS> element.

Action Make sure the class files can be found on the search path.



68 "ERROR: Directory ’’{0}’’ exists already"

Description The directory {0} should be used to prepare the creation of the archive, but the name already exists in the file system.

Action The existing directory must be removed or renamed. Alternatively, buildjavaserver can be executed from another directory that does not contain an entry by that name.

69 "ERROR: Cannot create directory {0}"

Description The {0} value is the name of a directory that is created when preparing the creation of the archive. The directory cannot be created.

Action Make sure there are no access restrictions on the directory for the current user and that the file system is not out of resources.

70 "ERROR: {0} exists and is not a directory"

Description The directory {0} is created when preparing the creation of the archive. Another file by that name has already been created, and the directory cannot be created.

Action Check the directory and the file name.

71 "ERROR: Cannot copy {0} to {1}"

Description The file {0} cannot be copied to {1} when preparing the creation of the archive. The {0} value is either an absolute file name or an entry in a ZIP or JAR archive.

Action Make sure there are no access restrictions on {0}and that the file system is not out of resources.



72 "ERROR: Cannot change to directory {0}"

Description buildjavaserver cannot set the current directory to {0}.

Action Check that there are no permission problems on the directory. Also make sure that the umask is not too restrictive when creating directories.

73 "ERROR: Cannot create archive {0}"

Description The execution of the jar command failed.The messages issued by the jar command provide more information.

Action Depends on the information given by the jar command. For information on the jar command, refer to the online documentation included with JDK 1.2 and the Java Programming Reference.

74 "WARNING: Cannot remove {0}"

Description The temporary file {0} cannot be removed.

Action Remove the leftover files after the buildjavaserver command completes.

75 "ERROR: Cannot write {0}"

Description There is an I/O error when the system attempts to write to temporary file {0}.

Action Check that there are sufficient resources in the file system.

76 "ERROR: Cannot open {0}"

Description The file {0} cannot be opened for reading.

Action Make sure the current user has read permission on the file.



77 "ERROR: Empty value for attribute {0}"

Description The value for attribute {0} is an empty string.

Action Add a valid value for the attribute.

78 "ERROR: Invalid value {0} for attribute {1}"

Description The value {0} is not valid for attribute {1}. Typically, the attribute should contain a Java class or a package name, and the name is not a valid dot-separated Java identifier.

Action Make sure the value is valid for the attribute.

79 "ERROR: Class {0} in server-implementation does not extend com.beasys.Tobj.Server"

Description The class whose name is specified in the server-implementation attribute of the <M3-SERVER> element must either derive from com.beasys.Tobj.Server or be the com.beasys.Tobj.Server class itself.

Action Check that the class name for the server-implementation attribute is correct. Make sure that the specified class extends com.beasys.Tobj.Server.

80 "ERROR: Class {0} in name is not a servant implementation"

Description The class {0} found in an implementation element does not derive from a skeleton generated by the m3idltojava compiler.

Action Make sure the base class for {0} is a valid skeleton.



81 "ERROR: ’’implements’’ value {0} does not match servant id {1}"

Description The implements attribute value {0} does not match the interface repository ID found in the implementation class being processed. The interface repository ID is actually part of the skeleton class used as the base class for the implementation class.

Action Make sure the interface repository ID is correct. Alternatively, the implements attribute can be omitted completely, in which case the value found in the implementation class will be used.


CHAPTER

12 Java Server-side Infrastructure Messages

Java Server-Side Infrastructure Messages 1-119

Note: When Java server-side messages are listed in the user log (ULOG), the messages have the prefix IJINFRA_CAT. For example, message 1 is listed as IJINFRA_CAT:1.

1 "ERROR: Cannot allocate request buffer"




12 JAVA SERVER-SIDE INFRASTRUCTURE MESSAGES

2 "INFO: Starting JVM"

Description This is an informational message indicating that the server process is starting the Java Virtual Machine.

Action None.

3 "ERROR: Cannot create FML buffer for TMIB request"



4 "ERROR: Cannot call .TMIB: errnum"

Description The server process was unable to call the TMIB. Details about the error that was returned are indicated by errnum.

Action Take corrective action based on the returned value of errnum. If the problem persists, contact BEA Customer Support.

5 "ERROR: Cannot find default constructor for ServerInfo"

Description The server process was unable to find the default constructor for the ServerInfo class.

Action Make sure the CLASSPATH is appropriately set. If the problem persists, contact BEA Customer Support.


JAVA SERVER-SIDE INFRASTRUCTURE MESSAGES 1-119

6 "ERROR: Cannot create ServerInfo object"



7 "WARN: No server group info"

Description The server process was unable to get any information about the server group.

Action None. This may result in a more serious error, and a corresponding error message would be written to the user log.

8 "ERROR: Cannot find m_srvgp field in ServerInfo"

Description The server process was unable to find the m_srvgp field in the ServerInfo class.


9 "ERROR: Cannot find m_srvid field in ServerInfo"

Description The server process was unable to find the m_srvid field in the ServerInfo class.




10 "WARN: No server ID info"

Description The server process was unable to get any information about the server ID.


11 "ERROR: Cannot find m_grpno field in ServerInfo"

Description The server process was unable to find the m_grpno field in the ServerInfo class.


12 "WARN: No group number info"

Description The server process was unable to get any information about the group number.


13 "WARN: No CLOPT info"

Description The server process could not find any command line option information.




14 "ERROR: Cannot find m_clopt field in ServerInfo"

Description The server process was unable to find the m_cltop field in the ServerInfo class.


15 "ERROR: Request failed with error: errnum"

Description An attempt by the process to make a request failed. errnum provides details of the error returned by the system.

Action Take corrective action based on the value of errnum returned. If the problem persists, contact BEA Customer Support.

16 "ERROR: Cannot allocate reply buffer"



17 "ERROR: Reply failed with error: errnum"

Description An attempt by the process to receive a reply failed. errnum provides details of the error returned by the system.




18 "ERROR: Reply length is zero"

Description An attempt by the process to receive a reply failed because the length of the receiving buffer was zero.


19 "ERROR: Out of memory. Cannot allocate space for internal data structure"



20 "ERROR: Unable to resolve in process or out process method invocation"

Description The process was unable to determine if a particular request was an in process or an out process invocation. The request fails.


21 "ERROR: Out of memory\n"





22 "ERROR: Interface interfaceName not found: errnum"

Description The system was not able to get information about the interface specified by interfaceName. Details of the error returned are provided in errnum.


23 "ERROR: Cannot find org.omg.CORBA.INTERNAL class"

Description The server process was unable to find the org.omg.CORBA.INTERNAL class.


24 "ERROR: Cannot find com.beasys.CORBA.tgiop.tmintfinfo class"

Description The server process was unable to find the com.beasys.CORBA.tgiop.tmintfinfo class.


25 "ERROR: Cannot find default constructor for tmintfinfo"

Description The server process was unable to find the default constructor for com.beasys.CORBA.tgiop.tmintfinfo class.




26 "ERROR: Cannot create tmintfinfo object"



27 "ERROR: Cannot find intf_id field"

Description The server process was unable to find the intf_id field in the com.beasys.CORBA.tgiop.tmintfinfo class.


28 "ERROR: Cannot find impl_id field"

Description The server process was unable to find the impl_id field in the com.beasys.CORBA.tgiop.tmintfinfo class.


29 "ERROR: Cannot find deact_policy field"

Description The server process was unable to find the deact_policy field in the com.beasys.CORBA.tgiop.tmintfinfo class.




30 "ERROR: Cannot find tx_policy field"

Description The server process was unable to find the tx_policy field in the com.beasys.CORBA.tgiop.tmintfinfo class.


31 "ERROR: Cannot find state_policy field"

Description The server process was unable to find the state_policy field in the com.beasys.CORBA.tgiop.tmintfinfo class.


32 "ERROR: Cannot find svc_nm field"

Description The server process was unable to find the svc_num field in the com.beasys.CORBA.tgiop.tmintfinfo class.


33 "ERROR: Cannot allocate FML buffer for TMIB call"





34 "ERROR: Cannot access TMIB: errnum"

Description The server process was unable to access the TMIB. Details about the error that was returned is indicated by errnum.

Action Take corrective action based on the returned value of errnum. If the problem persists, contact BEA Customer Support.

35 "ERROR: Unable to attach BB"

Description This message occurs in the server process if the server process was configured in the PROTECTED SYSTEM_ACCESS mode, and the process is unable to attach itself to the Bulletin Board.


36 "ERROR: Unable to lock BB and detach previous BB"

Description This message occurs in the server process if the server process was configured in the PROTECTED SYSTEM_ACCESS mode, and the process is unable to lock and later detach itself from the Bulletin Board.


37 "ERROR: Unable to lock BB"

Description This message occurs in the server process if the server process was unable to lock the Bulletin Board.




38 "ERROR: Unable to detach BB"

Description This message occurs in the server process if the server process was configured in the PROTECTED SYSTEM_ACCESS mode, and the process is unable to detach itself from the Bulletin Board.


39 "Usage: buildXAJS [-E envlabel] [-v] -r rmname [-o outfile]\n\t Also make sure JAVA_HOME is set in the environment\n"

Description This message shows the proper usage of the buildXAJS command.

Action Re-execute the buildXAJS command with the proper parameters or environmental variables.

40 "ERROR: Cannot execute prog_name\n"

Description The buildXAJS command was unable to execute the buildserver command. The name of the command being executed is given as part of the error message.

Action If you are compiling executables to run on the same machine type, as is normally the case, verify that the TUXDIR shell variable is properly set, that the program ${TUXDIR}/bin/buildserver exists, is accessible and executable, and that the shell variable XCBINDIR is not set. If you are compiling executables for a different machine type, verify that the shell variable XCBINDIR is set and exported, and that the program ${XCBINIDIR}/buildserver exists and is accessible and executable.



41 "Usage: JavaServer [JVM specific options] file.jar [application options]"

Description This message shows the proper usage of the JavaServer command in the UBBCONFIG file.

Action Make the appropriate modifications to the UBBCONFIG file so that the JavaServer command is executed with the proper parameters.

42 "ERROR: Missing argument to -M option"

Description The server process will not boot because no argument has been passed on the command line to the -M option.

Action Make the appropriate changes in the UBBCONFIG file and reboot.

43 "ERROR: Missing argument to -classpath option"

Description The server process will not boot because no argument has been passed on the command line to the -classpath option.

Action Make the appropriate changes in the UBBCONFIG file and reboot.

44 "ERROR: Cannot create debugging pipe: errnum"

Description The server process will not boot because it could not create a debugging pipe. Details about the error that was returned is specified by errnum.

Action Take corrective action based on the value of errnum. If the problem persists, contact BEA Customer Support.



45 "ERROR: Cannot reopen stdout for debugging info: errnum"

Description The server process will not boot because it cannot reopen stdout for debugging information. Details about the error that was returned is specified by errnum.

Action Take corrective action based on the value of errnum. If the problem persists, contact BEA Customer Support.

46 "ERROR: Cannot create Java VM"

Description The server process will not boot because it could not create the Java Virtual Machine.


47 "ERROR: No agent password info"

Description The server process will not boot because it could not retrieve the agent password information.


48 "INFO: Debug password buffer: buf"

Description This is an informational message with the debug password buffer specified in buf.

Action None.



49 "ERROR: Cannot find com.beasys.Tobj.infrastructure.ServerMain class"

Description The server process was unable to find the com.beasys.Tobj.infrastructure.ServerMain class.


50 "ERROR: Cannot find com.beasys.Tobj.ObjectManager class"

Description The server process was unable to find the com.beasys.Tobj.Objectmanager class.


51 "ERROR: Cannot find com.beasys.Tobj.OrbMain class"

Description The server process was unable to find the com.beasys.Tobj.OrbMain class.


52 "ERROR: Cannot find ServerMain.init"

Description The server process was unable to find the init(…) method in the com.beasys.Tobj.infrastructure.ServerMain class.




54 "ERROR: Cannot find ObjectManager.handleTransactionEnd"

Description The server process was unable to find the handleTransactionEnd(…) method in the com.beasys.Tobj.ObjectManager class.


55 "ERROR: Cannot find OrbMain.objectManager"

Description The server process was unable to find the objectManager(…) method in the com.beasys.Tobj.OrbMain class.


56 "ERROR: Cannot find ObjectManager.txInInvocation"

Description The server process was unable to find the txInInvocation(…) method in the com.beasys.Tobj.ObjectManager class.


57 "ERROR: Cannot find ServerMain.release"

Description The server process was unable to find the release(…) method in the com.beasys.Tobj.infrastructure.ServerMain class.


58 "ERROR: Cannot create Java VM"

Description Execution of buildjavaserver failed because the process was unable to create the Java Virtual Machine.




59 "ERROR: Cannot find <classname>\n"

Description While executing buildjavaserver, the process was unable to find the class specified in <classname>.


60 "ERROR: Cannot find buildjavaserver.main\n"

Description While executing buildjavaserver, the process was unable to find the main(…) method in the class com.beasys.Tobj.xml.buildjavaserver .


64 "ERROR: Cannot obtain ObjectManager from OrbMain"

Description The server process will not boot because critical information that it needs is missing.


65 "INFO: Server initialized"

Description This is an informational message indicating that the server process has successfully initialized and is now ready to process incoming requests.

Action None.

66 "ERROR: Server intialization failed"

Description The server process initialization has failed because of an internal error.




67 "ERROR: Cannot allocate request array"



68 "ERROR: service returned null"

Description The processing of an incoming request to the server process failed because of an internal error in the server process.


69 "ERROR: Cannot allocate return buffer"



70 "INFO: Shutting down JVM"

Description This is an informational message indicating that the server process is shutting down the Java Virtual Machine.




71 "ERROR: You do not have a valid BEA WLE Java server license"

Description The server process will not boot because you do not have a valid BEA WLE Java server license.

Action Contact BEA Customer Support to acquire an appropriate license.

72 "ERROR: Your license for BEA WLE Java server has expired"

Description This server process will not boot because your license for the BEA WLE Java server has expired.

Action Contact BEA Customer Support to acquire a new license.

73 "WARN: <pattern> not found in <file>\n"

Description This is a warning message that is output while executing m3idttojava if an expected pattern (specified by <pattern>) is not found in the file (specified by <file>).

Action None. This may result in a more serious error and a corresponding error message being written to the user log.

74 "INFO: <command>: PostProcessing: writing file <file>\n"

Description This is an informational message that is output while executing the command specified by <command>. <file> gives the name of the file being written to during the postprocessing phase.

Action None.



75 "ERROR: Cannot open <file>: <error>\n"

Description While executing m3idttojava, the process was unable to open the file specified by <file>. <error> indicates the error returned by the system while attempting to open that file.

Action Take corrective action based on the error returned.

76 "ERROR: Cannot create temp file: <error> \n"

Description While executing m3idttojava, the process was unable to create a temporary file. <error> indicates the error returned by the system while attempting to create that file.


77 "ERROR: Invalid ImplBase file <file>\n"

Description While executing m3idttojava, an invalid ImplBase file was specified. The name of that file is specified by <file>.


78 "ERROR: Cannot create new <file>: <error>\n"

Description While executing m3idttojava, the process was unable to create a new file specified by <file>. <error> indicates the error returned by the system while attempting to create that file.




79 "ERROR: <command>: idltojava option <option> not supported\n"

Description This error message is output while executing the command (specified by <command>) if an unsupported idltojava option is specified. <option> gives details of the option specified.

Action Do not use the corresponding option. It is not supported.

80 "ERROR: <command>: Out of memory\n"

Description An attempt to allocate space for internal data structures failed because the process ran out of memory while executing the command (specified by <command>).


81 "ERROR: <command>: Cannot execute <sub-command>: <error>\n"

Description While executing the command (specified by <command>), the process was unable to execute a sub-command (specified by <sub-command>). <error> gives details of the error returned by the system.


82 "ERROR: Cannot access file <file> in APPDIR <appdir>"

Description The server process will not boot because it cannot access the jar file specified by <file> in the APPDIR specified by <appdir>.

Action Make sure the jar file exists in APPDIR and that the file can be accessed.



83 "ERROR: Cannot copy request message"

Description The request cannot be processed by the server because the request message cannot be copied.

Action Notify BEA Technical Support.



Action This error may indicate that all available memory for the process has been exhausted. Ensure that operating system parameters are set correctly for the amount of memory on the machine and the amount of memory that can be used by a process. Reduce the memory usage on the machine, or increase the amount of physical memory on the machine.

85 "ERROR: No more available contexts"

Description The request cannot be processed by the server because no more server contexts are available.

Action This error indicates that all available server contexts have been exhausted. Increase the value of the threading level parameter in the UBBCONFIG file, or reduce the number of concurrent client requests.









88 "WARN: Blocking condition reached on outcall. Request will be resent."

Description A blocking condition was reached when the server attempted to invoke another server. The request will be queued internally and will be resent later.

Action None. This condition may be reached when the queue of the server to which the request is being made is full, or when another blocking condition arises. The failed request will be queued to be resent. If subsequent resend operations fail, a corresponding error message is written to the user log.

89 "INFO: Total application factory shutdown assumed."

Description A server application is attempting to unregister an application factory during execution of the release method on the Server object. The server application detects a problem with the unregister operation at this time. Upon further investigation, the server application discovers that the entire application is shutting down. The unregister method then fails (without sending a message) because the NameManagers also shut down.

Action None.



90 "ERROR: Request failed with error: errnum"

Description An attempt by the process to make a request failed. The number represented by errnum provides a reference to the details of the error returned by the system.

Action Take corrective action based on the value of the error number returned. If the problem persists, notify BEA Technical Support.

91 "ERROR: Cannot create registry table entry for context"

Description An attempt to create a registry table entry for the new context failed.

Action Either increase the value of the MAXACCESSERS parameter in the UBBCONFIG file, or reduce the number of concurrent client requests. In the WLE Server Threading architecture, each outstanding request is associated with its own BEA TUXEDO context, which in turns requires its own registry table entry. The MAXACCESSERS parameter in the UBBCONFIG file tells the BEA TUXEDO system how many registry table entries to be reserved. If the problem persists, notify BEA Technical Support.

92 "ERROR: Context initialization failed"

Description An attempt to initialize the server context failed.

Action This could be due to no more server contexts being available, insufficient memory, or a problem creating a registry table entry for the server contexts. A detailed error message should be written to the user log. Take corrective action based on the error message. If the problem persists, notify BEA Technical Support.



93 "ERROR: Failed to allocate context"

Description An attempt to allocate the server context failed.

Action This could be due to no more server contexts being available, insufficient memory, or a problem creating a registry table entry for the server contexts. A detailed error message should be written to the user log. Take corrective action based on the error message. If the problem persists, notify BEA Technical Support.

94 "ERROR: Cannot find com.beasys.Tobj.threading.ThreadMonitor class"

Description An attempt to find the com.beasys.Tobj.threading.ThreadMonitor class failed.

Action Make sure that the corresponding WLE Java JAR file is included in the class path.

95 "ERROR: Cannot find com.beasys.Tobj.threading.ThreadMonitor.allThreadsBusy"

Description An attempt to find the com.beasys.Tobj.threading.ThreadMonitor.allThreadsBusy method failed.


96 "ERROR: Cannot find com.beasys.Tobj.infrastructure.ServerMain.drainInfraQueue"

Description An attempt to find the com.beasys.Tobj.infrastructure.ServerMain.drainInfraQueue method failed.




97 "ERROR: Cannot find com.beasys.Tobj.infrastructure.ServerMain.sendMethodReply"

Description An attempt to find the com.beasys.Tobj.infrastructure.ServerMain.sendMethodReply method failed.


98 "ERROR: Cannot find com.beasys.Tobj.threading.ExchangeQueue class"

Description An attempt to find the com.beasys.Tobj.threading.ExchangeQueue class failed.


99 "ERROR: Cannot find com.beasys.Tobj.threading.ExchangeQueue.setKillLock"

Description An attempt to find the com.beasys.Tobj.threading.ExchangeQueue.setKillLock method failed.


100 "ERROR: Cannot find com.beasys.Tobj.threading.ApplicationThread class"

Description An attempt to find the com.beasys.Tobj.threading.ApplicationThread class failed.




101 "ERROR: Cannot find com.beasys.Tobj.threading.ApplicationThread.infrastructure_queue field"

Description An attempt to find the com.beasys.Tobj.threading.ApplicationThread.infrastructure_queue class field failed.


102 "ERROR: Cannot find com.beasys.Tobj.threading.ApplicationThread.infrastructure_queue"

Description An attempt to find the com.beasys.Tobj.threading.ApplicationThread.infrastructure_queue class field failed.


103 "ERROR: Cannot find com.beasys.Tobj.infrastructure.Debug class"

Description An attempt to find the com.beasys.Tobj.infrastructure.Debug class failed.


104 "ERROR: Cannot find com.beasys.Tobj.infrastructure.Debug.setLevel"

Description An attempt to find the com.beasys.Tobj.infrastructure.Debug.setLevel method failed.




105 "ERROR: tpcommit reported err in reply processing"

Description An attempt to call the tpcommit() function failed during reply processing. The detailed error is provided in the error string err.


106 "WARN: transaction processing failure in reply processing"

Description A transaction processing failure has been encountered during the processing of a reply.

Action None. This may result in a more severe problem that will be logged as an error.

107 "WARN: _tmfmsg_copy_tcm fails"

Description A call to the _tmfmsg_copy_tcm() function to copy the message has failed.

Action None. This may result in a more severe problem that will be logged as an error.

108 "ERROR: Failed to send reply: err"

Description An attempt to send a reply has failed. The detailed error is provided in the error message err.


109 "WARN: Number of worker threads specified is too high. Resetting to 500."

Description The number of the worker threads specified in the UBBCONFIG file exceeds the upper limit of 500. It is being reset to 500.

Action None.



110 "ERROR: Cannot find com.beasys.Tobj.infrastructure.ServerMain.sendTransactionReply"

Description An attempt to find the com.beasys.Tobj.infrastructure.ServerMain.sendTransactionReply method failed.


111 "ERROR: Cannot find com.beasys.Tobj.threading.ThreadMonitor.initThreadPool"

Description An attempt to find the com.beasys.Tobj.threading.ThreadMonitor.initThreadPool method failed.


112 "ERROR: Cannot open internal temporary file"

Description The program could not create or open an internal temporary file in this directory.

Action Make sure that permissions have been set so that this program can open, read, and write internal temporary files.


Description An attempt to allocate space for internal data structures failed as the server process ran out of memory.




114 "ERROR: Cannot write to internal temporary file"

Description The program could not create or open an internal temporary file in this directory.

Action Make sure that permissions have been set so that this program can open, read, and write internal temporary files.

115 "ERROR: Cannot advertise admin service"

Description An attempt to advertise the administration service for server threads administration failed.


116 "ERROR: Cannot unadvertise admin service"

Description An attempt to unadvertise the administration service for server threads administration failed.


117 "ERROR: Cannot find com.beasys.Tobj.threading.ThreadMonitor.getIdle"

Description An attempt to find the com.beasys.Tobj.threading.ThreadMonitor.getIdle method failed.




118 "ERROR: Cannot find com.beasys.Tobj.threading.ThreadMonitor.getStarted"

Description An attempt to find the com.beasys.Tobj.threading.ThreadMonitor.getStarted method failed.


119 "ERROR: Server initialization failed"

Description The initialization of the JavaServer failed.

Action Check the ULOG for additional error information and take appropiate corrective actions.


CHAPTER

13 Java Server Threading Messages

Java Server Threading Messages 1-10

Note: When Java server threading messages are listed in the user log (ULOG), the messages have the prefix IJTHREADS_CAT. For example, message 1 is listed as IJTHREADS_CAT:1.

1 "INFO: Thread {0} started"

Description A new thread with a thread ID specified by {0} is started.

Action None.

2 "ERROR: Illegal recursive call"

Description A recursive call was made. This error occurs if, for example, a server thread that is currently executing a method of object A invokes object B, which in turns invokes object A again. The second invocation to object A causes this error message to be printed to the user log.



13 JAVA SERVER THREADING MESSAGES

3 "INFO: Thread {0} is being terminated"

Description A new thread with thread ID specified by {0} is being terminated.

Action None.

4 "ERROR: Cannot invoke ORB functions from non-Server threads"

Description Invocations to the ORB functions are allowed only from WLE Java server threads.

Action Notify the programmer. Make sure that no attempt to invoke ORB functions is made from application-created threads.








JAVA SERVER THREADING MESSAGES 1-10







9 "ERROR: Cannot invoke infrastructure from non-Server threads"

Description Invocations to the infrastructure are only allowed from WLE Java server threads.

Action Notify the programmer. Made sure that no attempt to invoke infrastructure functions is made from application-created threads.

10 "ERROR: Request Table out of bounds"

Description An attempt is made to access an invalid entry in the WLE Java threading infrastructure’s request table.



13 JAVA SERVER THREADING MESSAGES


14 Minor Code Mapping

The following table provides details about what action you need to take when you receive system exceptions with corresponding minor codes. If the problem persists after the application programmer has taken the specified corrective measures, notify BEA Customer Support and for faster problem resolution provide the appropriate minor code value.

The following minor code values are the last four digits in the minor code, as displayed in decimal.

Minor Code Value

Description of Error Condition and Action to Be Taken

7705 Refer to the description/corrective action for message number 1 in the message catalog IJTPFW_CAT.properties.





7712 The Bootstrap object is unable to resolve the host machine and the port to connect to the WLE system. Make sure the address string passed to the Bootstrap object (either programmatically or through environment variables) is correct.


14 MINOR CODE MAPPING

7713 The Bootstrap object is unable to resolve the host machine and the port to connect to the WLE system. Make sure the address string passed to the Bootstrap object (either programmatically or through environment variables) is not null.






7719 The Bootstrap object is unable to resolve the host machine and the port to connect to the WLE system. Make sure the address string passed to the Bootstrap object (either programmatically or through environment variables) does not have a null host or port value.

7720 The Bootstrap object is unable to resolve the host machine and the port to connect to the WLE system. Make sure the address string passed to the Bootstrap object (either programmatically or through environment variables) has an integral port number.

7721 or 7722

Notify BEA Technical Support and provide this minor code value.

7723 Make sure that another Bootstrap object in the client does not own the TransactionCurrent object.

7724 Make sure that another Bootstrap object in the client does not own the SecurityCurrent object.

7725 Make sure that another Bootstrap object in the client does not own the Current objects.

7726 Make sure the address string passed to the Bootstrap object is empty or null.

7727 Make sure the address string passed to the Bootstrap object is null.

7728 Make sure that another Bootstrap object in the client does not own the TransactionCurrent object.


7729 Make sure that another Bootstrap object in the client does not own the SecurityCurrent object.

7730 The current version of this product does not support the SecurityCurrent object for native clients.

7731 Make sure that another Bootstrap object in the client does not own the Current objects.

7732 to 7744


7745 Unable to get POACurrent. Notify BEA Technical Support and provide this minor code value.

7746 Unable to resolve POACurrent. Notify BEA Technical Support and provide this minor code value.

7747 Notify BEA Technical Support and provide this minor code value.




7751 An object infected with one transaction may not be invoked from within a different transaction at the same time. Also, a nontransactional invocation may not be made on an object that is already infected with a transaction.

7752 An object infected with one transaction may not be invoked from within a different transaction at the same time. Also, a nontransactional invocation may not be made on an object that is already infected with a transaction.



7755 to 7757


7758 The invocation on the object failed. Scan the userlog to get the appropriate error message and take the corresponding corrective action.

7759 or 7760




7761 to 7764

Make sure that when an invocation is made on an object, the entering and exiting transaction contexts match. The entering transaction context is defined as the transaction context at the time just before invoking the object (if the activate_object method is invoked on the object, it is the context before the activate_object method is invoked). The exiting transaction context is defined as the transaction context at the time just after the invoked method completes (if the deactivate_object method is invoked on the object, it is the context after the deactivate_object method is invoked).

7765 to 7780






7785 to 7788

Make sure a previous destroy_current method has not been invoked on the current Bootstrap object.

7789 Make sure that the user_name provided to the logon method is not empty or too long.

7790 Make sure that the client_name provided to the logon method is not empty or too long.

7791 Make sure that only one of user_password or user_data is provided to the logon method.

7792 Make sure that the system_password provided to the logon method is not empty or too long.


7794 Make sure a previous destroy_current method has not been invoked on the current Bootstrap object.

7795 Make sure the client is currently logged on before an invocation to the logoff method is issued.


7797 or 7798



7799 to 7804



7806 to 7824


7825 or 7826


7827 or 7828



7830 to 7834


7835 Make sure that the current thread is not inside a transaction context at the time of issuing an invocation to the close_xa_rm method.


7905 The default POA returned by the WLE system is null. Notify BEA Technical Support and provide this minor code value.

7906 to 7909


7910 Refer to the description/corrective action for message number 2 in the message catalog IJORB_CAT.properties.




7914 to 7936








7941 Make sure the interface string passed as a parameter to the offending call is not empty or null.

7942 Make sure the oid passed as a parameter to the offending call is not empty or null.



7945 to

7950








7957 to 7961







7966 to 7972



7974 or 7975




