MQSeries.net :: View topic

nabanita

In the basic property of the databaseRetreive node there is datasource name feild there when I am providing the data source name then its creating problem while deployment but when I am selecting on of the database name from the drop down menu it is not giving deployment problem but giving a problem while testing.Where shall I provide the datasource name and database name can you kindly guide me.

The Deployment Problem is given below:-
BIP6253E: Error in node: Broker 'WBRK61_DEFAULT_BROKER'; Execution Group 'default'; Message Flow 'Database_retrieve_node_test'; Node 'DatabaseRetrieve'; Thread 'Thread[Thread-14,5,main]' . Could not locate JDBC Provider entry 'POC' in the broker registry, which was given for the data source name property for this node.

The node can not establish a connection with a database if the provided JDBC data source definition is not present as an entry in the registry associated with the broker.

Examine the data source name provided on the node and ensure the value given matches an existing JDBC Provider registry entry for the broker concerned.

BIP4041E: Execution group 'default' received an invalid configuration message. See the following messages for details of the error.

The message broker received an invalid configuration message and has not updated its configuration. This can arise as a result of errors in the specification of either message flows or message sets which the configuration manager was unable to detect. It can also result from a message flow requiring a type of node that is not supported by the broker installation, from the broker having become out of step with the configuration database or from other applications sending extraneous messages to the broker's configuration queues (SYSTEM.BROKER.ADMIN.QUEUE & SYSTEM.BROKER.EXECUTIONGROUP.QUEUE).

Check the relevant message flow and message set definitions, check that all necessary user-defined extensions are installed, perform a complete redeploy of the broker's configuration and ensure that no applications are writing to the broker's configuration queues.

BIP2087E: Broker WBRK61_DEFAULT_BROKER was unable to process the internal configuration message.

The entire internal configuration message failed to be processed successfully.

Use the messages following this message to determine the reasons for the failure. If the problem cannot be resolved after reviewing these messages, contact your IBM Support center. Enabling service trace may help determine the cause of the failure.

The testing problem is:-
Timestamps are formatted in local time, 330 minutes past GMT.
Trace written by version ; formatter version 6102

2009-01-16 18:30:31.790700 4120 UserTrace BIP4040I: The Execution Group ''default'' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2009-01-16 18:30:31.791305 4120 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' connected to queue manager ''WBRK61_DEFAULT_QUEUE_MANAGER''. The MQCC was '0' and the MQRC was '0'.
2009-01-16 18:30:31.791326 4120 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' on queue manager ''WBRK61_DEFAULT_QUEUE_MANAGER''.
2009-01-16 18:30:38.859722 4940 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'Database_retrieve_node_test.MQInput'.
2009-01-16 18:30:38.859973 4940 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'Database_retrieve_node_test.MQInput' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2009-01-16 18:30:38.860038 4940 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'Database_retrieve_node_test.MQInput' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2009-01-16 18:30:38.860118 4940 UserTrace BIP6061I: Parser type ''XMLNSC'' created on behalf of node 'Database_retrieve_node_test.MQInput' to handle portion of incoming message of length '31' bytes beginning at offset '364'. Parser type selected based on value ''XMLNSC'' from previous parser.
2009-01-16 18:30:42.842380 4940 UserTrace BIP3904I: Invoking the evaluate() method of node (class='ComIbmDatabaseRetrieveNode', name='Database_retrieve_node_test#FCMComposite_1_1').
About to pass a message to the evaluate() method of the specified node.
No user action required.
2009-01-16 18:31:12.312252 4940 Error BIP2628E: Exception condition detected on input node 'Database_retrieve_node_test.MQInput'.
The input node 'Database_retrieve_node_test.MQInput' detected an error whilst processing a message. The message flow has been rolled-back and, if the message was being processed in a unit of work, it will remain on the input queue to be processed again. Following messages will indicate the cause of this exception.
Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.
2009-01-16 18:31:12.312400 4940 RecoverableException BIP2230E: Error detected whilst processing a message in node 'Database_retrieve_node_test.DatabaseRetrieve'.
The message broker detected an error whilst processing a message in node 'Database_retrieve_node_test.DatabaseRetrieve'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2009-01-16 18:31:12.312421 4940 RecoverableException BIP6247E: Error in node: 'Broker 'WBRK61_DEFAULT_BROKER'; Execution Group 'default'; Message Flow 'Database_retrieve_node_test'; Node 'DatabaseRetrieve'; Thread 'Thread[Thread-18,5,main]' '. A problem was encountered evaluating general expression ''$InputRoot/XML/Emp/EmpNo'', which was given for the ''0'' element value in the query element table for this node.
The node evaluated the provided expression against the incoming message tree, but the result of the expression has returned an empty list containing no broker tree elements.
Examine the provided expression to confirm that it is correct.
2009-01-16 18:31:13.312968 4940 Error BIP2648E: Message backed out to a queue; node 'Database_retrieve_node_test.MQInput'.
Node 'Database_retrieve_node_test.MQInput' has received a message which has previously been backed out one or more times because of a processing error in the main path of the message flow. The failure terminal is not attached, so the message broker is putting the message directly to the requeue or dead letter backout queue associated with this node. The MQMD 'backoutCount' of the message now equals the 'backoutThreshold' defined for the WebSphere MQ input queue.
Examine previous messages and the message flow to determine why the message is being backed out. Correct this situation if possible. Perform any local error recovery processing required.
2009-01-16 18:31:13.313335 4940 UserTrace BIP2638I: The MQ output node 'Database_retrieve_node_test.MQInput' attempted to write a message to queue ''SYSTEM.DEAD.LETTER.QUEUE'' connected to queue manager ''WBRK61_DEFAULT_QUEUE_MANAGER''. The MQCC was '0' and the MQRC was '0'.
2009-01-16 18:31:13.313355 4940 UserTrace BIP2615I: The WebSphere MQ input node 'Database_retrieve_node_test.MQInput' has backed out the message to the backout requeue or the dead letter queue.
Message backout processing has been invoked, and the message has either been backed out by being written to the backout requeue or dead letter queue, as determined by the WebSphere MQ queue manager and queue configuration.
No user action required.
2009-01-16 18:32:31.974361 4120 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2009-01-16 18:32:31.974479 4120 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2009-01-16 18:32:31.974514 4120 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2009-01-16 18:32:31.974765 4120 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '244' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.

Threads encountered in this trace:
4120 4940