システム・メッセージ: LIBMFFカタログ1000-1099
|
![]() |
![]() |
1000 |
エラー: アプリケーションには最低でも2つのNameManagersが必要です。 | |
|
説明 |
NameManagerサービスの起動時にアプリケーション内で2つのNameManagerが構成されていない場合、NameManagerはスタートアップを終了してこのエラー・メッセージをユーザー・ログに書き込みます。アプリケーションの一部としてNameManagerサービスを実行するには、少なくとも2つのサーバーを構成する必要があります。この要件により、名前からIORへのマッピングの作業用コピーがいつでも使用可能になります。サーバーが複数のマシンにあり1台がクラッシュした場合、そのマシンおよびアプリケーションが再起動すると、新しいNameManagerは別のNameManagerからマッピングを取得します。 |
アクション |
| |
1001 |
エラー: アプリケーションにはマスターNameManagerが1つ必要です。 | |
|
説明 |
NameManagerはマスターまたはスレーブのどちらかとして指定でき、デフォルトはスレーブです。マスターNameManagerサービスがアプリケーションで構成されていない場合や実行されていない場合にスレーブNameManagerサービスが起動すると、起動中にサーバーが終了します。 |
アクション |
| |
1002 |
エラー: アプリケーションではマスターNameManagerを1つしか指定できません。 | |
|
説明 |
1つのアプリケーションで指定できるマスターNameManagerは1つのみです。複数のNameManagerサービスをマスターとして指定した場合、NameManagerはスタートアップを終了します。 |
アクション |
| |
1004 |
ERROR: CannotProceed Exception. NOTIFY Operations Staff! [IC=val] | |
|
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. | |
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. |
Action |
Follow the recovery procedures for the tperrno displayed. | |
1009 |
ERROR: Cannot subscribe to servicename, tperrno = tperrno. [IC=internalcode] | |
|
Description |
A NameManager server cannot subscribe to events posted by the System Event Broker. |
Action |
Follow the recovery procedures for the tperrno displayed. | |
1010 |
WARN: Cannot unsubscribe from servicename, tperrno = tperrno. [IC=internalcode] | |
|
Description |
A NameManager server cannot unsubscribe for events posted by the System Event Broker. |
Action |
Follow the recovery procedures for the tperrno displayed. | |
1011 |
エラー: ファクトリ・マッピングをリカバリできません。 | |
|
説明 |
1つのNameManagerが別のNameManagerから完全なファクトリ・マッピングを取得できませんでした。 |
アクション |
このメッセージを生成したNameManagerをシャットダウンして再起動してください。 | |
1012 |
エラー: アプリケーションは最初にTMSYSEVTを起動する必要があります。 | |
|
説明 |
NameManagerが起動する前に、システム・イベント・ブローカ |
アクション |
いずれかのNameManagerを起動する前に | |
1013 |
エラー: TMSYSEVTはアクティブである必要があります。 | |
|
説明 |
NameManagerが起動したとき、システム・イベント・ブローカ |
アクション |
NameManagerが起動する前に | |
1014 |
警告: 管理サービスを通知できませんでした | |
|
説明 |
|
アクション |
なし。 | |
関連項目 |
| |
1015 |
エラー: 無効なクラス指定です | |
|
説明 |
|
アクション |
少なくとも2つの | |
1016 |
エラー: マスターNameManagerより先にスレーブNameManagerが起動されました。 | |
|
説明 |
|
アクション |
| |
関連項目 |
| |
1017 |
エラー: NameManagerとFactoryFinderを一緒に構成できません。 | |
|
説明 |
NameManagerおよびFactoryFinderが、同じサーバー・プロセスを使用して構成されました。これは無効な組合せです。 |
アクション |
NameManagerとFactoryFinderを別々の2つのプロセスに分けてください。 | |
関連項目 |
| |
1018 |
警告: ポストが失敗しました。スレーブNameManagerが同期していない可能性があります。 | |
|
説明 |
マスターNameManagerが、 |
アクション |
まず、システム・イベント・ブローカが実行されていることを確認してください。次に、マスターNameManagerとの間に通信パスがあることを確認してください。最後に、スレーブNameManagerをシャットダウンして再起動してください。再起動時に、スレーブNameManagerはマスターNameManagerからファクトリ名マッピングの新しいコピーを取得します。 | |
1019 |
情報: メッセージの損失を検出しました。名前のマッピングを再同期化します。 | |
|
説明 |
マスターNameManagerから更新メッセージを受信する際に、スレーブNameManagerは、前の更新メッセージが受信されていなかったことを検出しました。スレーブは、マスターNameManagerからのファクトリ名マッピングのリフレッシュをリクエストします。 |
アクション |
なし。 | |
1020 |
ERROR: Initialization:unable to open factoryfinder initialization file val, opt_p | |
|
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, and that the name corresponds to the master Name Manager -f filename command line argument in the ubbconfig file. | |
1021 |
ERROR: Initialization:unable to process factoryfinder initialization file val, opt_p | |
|
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: Invalid factory Id: line = val | |
|
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: Invalid DomainId: line = val | |
|
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: Invalid RName: line = val | |
|
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. | |
1025 |
エラー: ファイルにドメイン・セクション・タイプがありません | |
|
説明 |
FactoryFinder初期化ファイルを処理しようとしましたが、エラーが発生しました。ファイル内にセクション・タイプ(DM_REMOTE_FACTORIESおよびDM_LOCAL_FACTORIES)がありませんでした。 |
アクション |
FactoryFinder初期化ファイルを編集してセクション・タイプを含めてください。 | |
1026 |
ERROR: FactoryFinder Invoke to TDomain val 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. | |
1027 |
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. | |
1028 |
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. | |
1029 |
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. | |
1030 |
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. | |
1031 |
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. | |
1032 |
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. | |
1033 |
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. | |
1034 |
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. | |
1035 |
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. | |
1036 |
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. | |
1037 |
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. | |
1038 |
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. | |
1039 |
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. | |
1040 |
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. | |
1041 |
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. | |
1042 |
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. | |
1043 |
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. | |
1044 |
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. | |
1045 |
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. | |
1046 |
ERROR: Cannot advertise servicename, tperrno = tperrno. [IC=internalcode] | |
|
Description |
A NameManager server cannot advertise a network service that was used to coordinate with other NameManager servers. |
Action |
Follow the recovery procedures for the tperrno displayed. | |
1047 |
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. |
Action |
Follow the recovery procedures for the tperrno displayed. | |
1048 |
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. |
Action |
Follow the recovery procedures for the tperrno displayed. | |
1049 |
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. |
Action |
Follow the recovery procedures for the tperrno displayed. | |
1050 |
ERROR: Cannot subscribe to servicename, tperrno = tperrno. [IC=internalcode] | |
|
Description |
A NameManager server cannot subscribe to events posted by the System Event Broker. |
Action |
Follow the recovery procedures for the tperrno displayed. | |
1051 |
WARN: Cannot unsubscribe from servicename, tperrno = tperrno. [IC=internalcode] | |
|
Description |
A NameManager server cannot unsubscribe for events posted by the System Event Broker. |
Action |
Follow the recovery procedures for the tperrno displayed. | |
1052 |
エラー: アプリケーションがNameManagerを構成しませんでした。 | |
|
説明 |
|
アクション |
少なくとも2つの | |
1053 |
ERROR: Invalid factory Id/Kind: line = val | |
|
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. | |
1054 |
ERROR: Invalid factory Id: line = val | |
|
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. | |
1055 |
ERROR: Invalid factory Id/Kind: line = val | |
|
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. | |
1056 |
ERROR: Invalid factory Id/Kind: line = val | |
|
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. | |
1057 |
ERROR: Invalid factory Id/Kind: line = val | |
|
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. | |
1058 |
ERROR: Invalid factory Id/Kind: line = val | |
|
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. | |
1059 |
ERROR: Invalid factory Id/Kind: line = val | |
|
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. | |
1060 |
ERROR: Invalid DomainId: line = val | |
|
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. | |
1061 |
ERROR: Invalid Domain Keyword: line = val | |
|
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. | |
1062 |
ERROR: Missing remote entry Kind value: line = val | |
|
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. | |
1063 |
ERROR: FactoryFinder Invoke to TDomain val failed: val | |
|
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. | |
1064 |
ERROR: Cannot access TMIB, tperrno = tperrno. | |
|
Description |
The NameManager or FactoryFinder service cannot access the TMIB. |
Action |
Follow the recovery procedures for the tperrno displayed. | |
1065 |
エラー: メモリー不足です。 | |
|
説明 |
NameManagerまたはFactoryFinder、あるいはその両方のサービスを実行するサーバーで、メモリー不足が発生しました。この状況は、登録されているファクトリの数が仮想メモリーの最大サイズに近づいた場合に、NameManagerを実行するサーバーで発生する傾向にあります。 |
アクション |
場合によっては、それぞれが独自に別個のNameManager機能を持つ複数のドメインに、アプリケーション・ファクトリを分割する必要があります。マシンのメモリー使用量を減らすか、メモリーを追加してください。 | |
1066 |
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. | |
1067 |
エラー: メモリー不足です。 | |
|
説明 |
NameManagerまたはFactoryFinder、あるいはその両方のサービスを実行するサーバーで、メモリー不足が発生しました。この状況は、登録されているファクトリの数が仮想メモリーの最大サイズに近づいた場合に、NameManagerを実行するサーバーで発生する傾向にあります。 |
アクション |
場合によっては、それぞれが独自に別個のNameManager機能を持つ複数のドメインに、アプリケーション・ファクトリを分割する必要があります。マシンのメモリー使用量を減らすか、メモリーを追加してください。 | |
1068 |
エラー: メモリー不足です。 | |
|
説明 |
NameManagerまたはFactoryFinder、あるいはその両方のサービスを実行するサーバーで、メモリー不足が発生しました。この状況は、登録されているファクトリの数が仮想メモリーの最大サイズに近づいた場合に、NameManagerを実行するサーバーで発生する傾向にあります。 |
アクション |
場合によっては、それぞれが独自に別個のNameManager機能を持つ複数のドメインに、アプリケーション・ファクトリを分割する必要があります。マシンのメモリー使用量を減らすか、メモリーを追加してください。 | |
1069 |
エラー: メモリー不足です。 | |
|
説明 |
NameManagerまたはFactoryFinder、あるいはその両方のサービスを実行するサーバーで、メモリー不足が発生しました。この状況は、登録されているファクトリの数が仮想メモリーの最大サイズに近づいた場合に、NameManagerを実行するサーバーで発生する傾向にあります。 |
アクション |
場合によっては、それぞれが独自に別個のNameManager機能を持つ複数のドメインに、アプリケーション・ファクトリを分割する必要があります。マシンのメモリー使用量を減らすか、メモリーを追加してください。 | |
1070 |
エラー: メモリー不足です。 | |
|
説明 |
NameManagerまたはFactoryFinder、あるいはその両方のサービスを実行するサーバーで、メモリー不足が発生しました。この状況は、登録されているファクトリの数が仮想メモリーの最大サイズに近づいた場合に、NameManagerを実行するサーバーで発生する傾向にあります。 |
アクション |
場合によっては、それぞれが独自に別個のNameManager機能を持つ複数のドメインに、アプリケーション・ファクトリを分割する必要があります。マシンのメモリー使用量を減らすか、メモリーを追加してください。 | |
1071 |
エラー: メモリー不足です。 | |
|
説明 |
NameManagerまたはFactoryFinder、あるいはその両方のサービスを実行するサーバーで、メモリー不足が発生しました。この状況は、登録されているファクトリの数が仮想メモリーの最大サイズに近づいた場合に、NameManagerを実行するサーバーで発生する傾向にあります。 |
アクション |
場合によっては、それぞれが独自に別個のNameManager機能を持つ複数のドメインに、アプリケーション・ファクトリを分割する必要があります。マシンのメモリー使用量を減らすか、メモリーを追加してください。 | |
1072 |
エラー: メモリー不足です。 | |
|
説明 |
NameManagerまたはFactoryFinder、あるいはその両方のサービスを実行するサーバーで、メモリー不足が発生しました。この状況は、登録されているファクトリの数が仮想メモリーの最大サイズに近づいた場合に、NameManagerを実行するサーバーで発生する傾向にあります。 |
アクション |
場合によっては、それぞれが独自に別個のNameManager機能を持つ複数のドメインに、アプリケーション・ファクトリを分割する必要があります。マシンのメモリー使用量を減らすか、メモリーを追加してください。 | |
1073 |
エラー: メモリー不足です。 | |
|
説明 |
NameManagerまたはFactoryFinder、あるいはその両方のサービスを実行するサーバーで、メモリー不足が発生しました。この状況は、登録されているファクトリの数が仮想メモリーの最大サイズに近づいた場合に、NameManagerを実行するサーバーで発生する傾向にあります。 |
アクション |
場合によっては、それぞれが独自に別個のNameManager機能を持つ複数のドメインに、アプリケーション・ファクトリを分割する必要があります。マシンのメモリー使用量を減らすか、メモリーを追加してください。 | |
1074 |
情報: アプリケーション・ファクトリが完全にシャットダウンしていると想定されます。 | |
|
説明 |
|
アクション |
なし。 | |
関連項目 |
| |
1075 |
ERROR: FactoryFinder Invoke to TDomain val 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. | |
1076 |
ERROR: FactoryFinder Invoke to TDomain val failed: ExceptionID | |
|
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. | |
1077 |
ERROR: FactoryFinder Invoke to TDomain val 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. | |
1078 |
ERROR: Invalid RName: line = val | |
|
Description |
The FactoryFinder initialization file contains an invalid |
Action |
Modify the RName value entered at line val. | |
See Also |
For more information about the | |
1079 |
ERROR: RegistrarNotAvailable Exception. NOTIFY Operations Staff! [IC=val] | |
|
Description |
Accompanying this message is an exception raised to an application object. The |
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. | |
1080 |
ERROR: RegistrarNotAvailable Exception. NOTIFY Operations Staff! [IC=val] | |
|
Description |
Accompanying this message is an exception raised to an application object. The |
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. | |
1081 |
ERROR: RegistrarNotAvailable Exception. NOTIFY Operations Staff! [IC=val] | |
|
Description |
Accompanying this message is an exception raised to an application object. The |
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. | |
1082 |
ERROR: RegistrarNotAvailable Exception. NOTIFY Operations Staff! [IC=val] | |
|
Description |
Accompanying this message is an exception raised to an application object. The |
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. | |
1083 |
ERROR: CannotProceed Exception. NOTIFY Operations Staff! [IC=val] | |
|
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. | |
1084 |
ERROR: CannotProceed Exception. NOTIFY Operations Staff! [IC=val] | |
|
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. | |
1085 |
ERROR: CannotProceed Exception. NOTIFY Operations Staff! [IC=val] | |
|
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. | |
1086 |
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. | |
1087 |
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. | |
1088 |
ERROR: Cannot subscribe to servicename, tperrno = tperrno. [IC=internalcode] | |
|
Description |
A NameManager server cannot subscribe to events posted by the System Event Broker. |
Action |
Follow the recovery procedures for the tperrno displayed. | |
1089 |
WARN: Cannot unsubscribe from servicename, tperrno = tperrno. [IC=internalcode] | |
|
Description |
A NameManager server cannot unsubscribe for events posted by the System Event Broker. |
Action |
Follow the recovery procedures for the tperrno displayed. | |
1090 |
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. |
Action |
Follow the recovery procedures for the tperrno displayed. | |
1091 |
ERROR: Local factory and remote factory cannot have the same identifier 'FactoryName'. | |
|
Description |
In a multiple domain environment, factories in different domains cannot have the same name. |
Action |
Change the name of one of the factories. | |
1092 |
ERROR: OBJ_ADAPTER Exception. FactoryFinder Invoke to TDomain val failed: ExceptionID | |
|
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. | |
1093 |
ERROR: Couldn't register TransactionFactory. Registrar service not available. Check status of FactoryFinder server(s). | |
|
Description |
The TransactionFactory could not be registered because the registration service was unavailable. |
Action |
Ensure that your application's FactoryFinder service is fully operational. | |
1094 |
ERROR: FFServer::registerTransactionFactory() cannot proceed due to unexpected problem with Registrar. Check status of FactoryFinder server(s). | |
|
Description |
The TransactionFactory could not be registered because of unexpected problems with the registration service. |
Action |
Ensure that your application's FactoryFinder service is fully operational. |
![]() |
![]() |
![]() |