BIP11001 - BIP11513

BIP11001
Message flow <insert_1> is about to make an outbound request for method <insert_3>.
Severity
0 : Information
Explanation
The message flow <insert_1> includes a <insert_2> request node. The node is about to make a request to call method <insert_3> on the EIS system.

BIP11002
The call to method <insert_3> was successful.
Severity
0 : Information
Explanation
The message flow <insert_1> includes a <insert_2> request node. The request to call method <insert_3> was successful.

BIP11003
The call to method <insert_3> failed and the following error was received: <insert_4>.
Severity
20 : Error
Explanation
The message flow <insert_1> includes a <insert_2> request node. The request to call method <insert_3> failed because of error <insert_4>.

BIP11004
A <insert_1> Adapter has received a message, which will be processed by message flow <insert_3>.
Severity
0 : Information
Explanation
A <insert_1> WebSphere Adapter named <insert_2> received an inbound message. The business method name was <insert_5>. The message will be processed by the node <insert_4> in flow <insert_3>. The node has secondary adapters configured as <insert_6> and the details for the method were found in the adapter <insert_7>.

BIP11005
Adapter <insert_1> is about to send a synchronous reply message back to the calling EIS System.
Severity
0 : Information
Explanation
A <insert_2> WebSphere Adapter named <insert_1> received an inbound message which required a reply. This reply will be sent back to the <insert_2> system via the reply node <insert_4> in flow <insert_3>.

BIP11006
Connected to <insert_1>.
Severity
0 : Information
Explanation
The WebSphere Adapter <insert_2> has established a new connection to the <insert_1> EIS system. The connection identifier is <insert_3>.

BIP11007
Disconnected from the <insert_1> system.
Severity
0 : Information
Explanation
The Adapter <insert_2> has closed the connection to the <insert_1> system. This may be because the adapter is being undeployed, the broker is stopping or the idle timeout for the connection has been reached.

BIP11008
Adapter <insert_1> has closed an idle connection.
Severity
0 : Information
Explanation
A WebSphere Adapter named <insert_1> maintains connections to an EIS system. The idle timeout on the connection was set to <insert_2> and that timeout has expired without the connection being reused. The connection has therefore been closed.

BIP11009
Failure in <insert_1> connection.
Severity
20 : Error
Explanation
The connection between Adapter <insert_2> and the <insert_1> system has been lost. The reason provided by the adapter is: <insert_3>.

BIP11101
Put data into map <insert_1>
Severity
0 : Information
Explanation
The message flow has successfully put data into map <insert_1>, in cache <insert_2>, using key <insert_3>.

BIP11102
Cleared all data from map <insert_1>
Severity
0 : Information
Explanation
The message flow has successfully cleared all data from map <insert_1>, in cache <insert_2>.

BIP11103
Got data from map <insert_1>
Severity
0 : Information
Explanation
The message flow has successfully got data from map <insert_1>, in cache <insert_2>, using key <insert_3>.

BIP11104
Updated data in map <insert_1>
Severity
0 : Information
Explanation
The message flow has successfully updated data in map <insert_1>, in cache <insert_2>, using key <insert_3>.

BIP11105
Inserted data into map <insert_1>
Severity
0 : Information
Explanation
The message flow has successfully inserted data into map <insert_1>, in cache <insert_2>, using key <insert_3>.

BIP11106
Removed data from map <insert_1>
Severity
0 : Information
Explanation
The message flow has successfully removed data from map <insert_1>, in cache <insert_2>, using key <insert_3>.

BIP11107
Checked whether key exists in map <insert_1>
Severity
0 : Information
Explanation
The message flow has checked whether map <insert_1> in cache <insert_2> contains key <insert_3>.

BIP11108
Failed to complete action on map <insert_1>
Severity
20 : Error
Explanation
The message flow has failed to complete an action on map <insert_1> in cache <insert_2>. Details of the exception are: <insert_3>.

BIP11109
Connected to cache <insert_1>
Severity
0 : Information
Explanation
The execution group has successfully connected to cache <insert_1>.

BIP11110
Failed to connect to cache <insert_1>
Severity
20 : Error
Explanation
The execution group has failed to connect to cache <insert_1>. Details of the exception are: <insert_2>.

BIP11111
Started catalog server
Severity
0 : Information
Explanation
The catalog server <insert_1> has successfully started.

BIP11112
Retrying start of cache components
Severity
10 : Warning
Explanation
The WebSphere eXtreme Scale server <insert_1> has not started. The start will continue retrying in the background.

BIP11113
Failed to start catalog server
Severity
20 : Error
Explanation
The catalog server <insert_1> has failed to start. Details of the exception are: <insert_2>.

BIP11114
Started container server
Severity
0 : Information
Explanation
The container server <insert_1> has successfully started.

BIP11115
Failed to start container server
Severity
20 : Error
Explanation
The container server <insert_1> has failed to start. Details of the exception are: <insert_2>.

BIP11501
Received data from input node <insert_1>.
Severity
0 : Information
Explanation
The input node <insert_1> has received data and has propagated it to the message flow <insert_2>.

BIP11502
Received a message from input node <insert_1> that is the last message in a message group.
Severity
0 : Information
Explanation
The input node <insert_1> has been configured to use message groups, and has received the last message in that message group. It has propagated the message to message flow <insert_2>.

BIP11503
Received a message from input node <insert_1> that forms part of a message group.
Severity
0 : Information
Explanation
The Input node <insert_1> has been configured to use message groups, and has received a message as part of that message group. It has propagated the message to message flow <insert_2>.

BIP11504
Waiting for data from input node <insert_1>.
Severity
0 : Information
Explanation
A thread is waiting for data from input node <insert_1> in flow <insert_2>.

BIP11505
Started a global transaction.
Severity
0 : Information
Explanation
A global transaction has been started to coordinate work for the message flow thread.

BIP11506
Committed a local transaction.
Severity
0 : Information
Explanation
A local transaction has been committed for work done on the message flow thread.

BIP11507
Rolled back a local transaction.
Severity
10 : Warning
Explanation
A local transaction has been rolled back for work done on the message flow thread.

BIP11508
Committed a global transaction successfully.
Severity
0 : Information
Explanation
A global transaction has been successfully committed for work on the message flow thread.

BIP11509
Failed to commit a global transaction.
Severity
20 : Error
Explanation
A global transaction failed to commit successfully.

BIP11510
Rolled back a global transaction.
Severity
10 : Warning
Explanation
A global transaction has been rolled back for work performed on the message flow thread.

BIP11511
Failed to parse input data.
Severity
10 : Warning
Explanation
The input data produced a warning. The data might be corrupt or truncated. For further information, examine the relevant transport and the system event log.

BIP11512
Failed to read input data
Severity
20 : Error
Explanation
Data arriving at the input node has caused a failure. If the flow is processing a message group, that group will be rolled back. Otherwise, this request will fail, but previous work in the batch will be committed.

BIP11513
Flow reconfiguration or redeployment is in progress; the flow is not waiting for data from input node <insert_1>.
Severity
10 : Warning
Explanation
The flow <insert_2> is being reconfigured or redeployed, therefore this input node is not currently polling or waiting for data.