| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| SAP Input adapter deployment error |
« View previous topic :: View next topic » |
| Author |
Message
|
| md.sadruddin |
 Posted: Thu Aug 27, 2009 8:57 am Post subject: SAP Input adapter deployment error |
 |
|
Novice
Joined: 27 Aug 2009
Posts: 12
|
Hi, I am using MB 6.1.0.2 on AIX. I am getting follwoing error while deploying a message flow with SAP Input node.
Strange thing is, when I deploy the adapter component and messageset (separately), it gets deployed; but not the mesageflow containing SAP Input node.
One more observation is, I could successfully deploy and test a messageflow containing SAP Request node.
I have set LD_LIBRARY_PATH, LIBPATH, LIB with both /usr/mqm/java/lib64 and /usr/mqm/java/lib separately. But it does not work.
Can you please advice?
| Quote: |
BIP3450E: An adapter error occurred during the processing of a message. The adapter error message is 'mqjbnd05 (A file or directory in the path name does not exist.) '.
This error was detected by the adapter. The following message describes the diagnostic information that is provided by the adapter 'mqjbnd05 (A file or directory in the path name does not exist.) '.
Inspect the diagnostic information that is provided by the adapter. Further diagnostic information might be written to user trace. Inspect user trace for further information.
|
 |
|
| Back to top |
|
 |
| kimbert |
| Posted: Thu Aug 27, 2009 9:54 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Have you tried doing this yet?
| Quote: |
| Further diagnostic information might be written to user trace. Inspect user trace for further information. |
|
|
| Back to top |
|
|
| md.sadruddin |
| Posted: Thu Aug 27, 2009 10:00 am Post subject: |
|
|
Novice
Joined: 27 Aug 2009
Posts: 12
|
Please find the detail below.
| Quote: |
Aug 27 13:51:28 mwd1 user:info WebSphere Broker v6102[2851010]: (DBK)[1]BIP8099I: Deployed Message Received from the ConfigMgr: processing UOW - : DBK.agent: /build/S610_P/src/AdminAgent/ImbAdminAgent.cpp: 1149: ImbAdminAgent::readAdministrationMessages: :
Aug 27 13:51:29 mwd1 user:info WebSphere Broker v6102[2851010]: (DBK)[1]BIP8099I: Deployed message for Execution Group sent to : WBI6POC - : DBK.agent: /build/S610_P/src/AdminAgent/ImbAdminAgent.cpp: 10132: ImbAdminAgent::SendMessage: :
Aug 27 13:51:29 mwd1 user:info WebSphere Broker v6102[2851010]: (DBK)[1]BIP8099I: Deployed messages to Execution Groups : committed UOW, awaiting Execution Group response - : DBK.agent: /build/S610_P/src/AdminAgent/ImbAdminAgent.cpp: 2072: ImbAdminAgent::receiveCMRequest: :
Aug 27 13:51:31 mwd1 user:err|error WebSphere Broker v6102[1437928]: (DBK.WBI6POC)[8225]BIP4041E: Execution group 'WBI6POC' received an invalid configuration message. See the following messages for details of the error. : DBK.38dfecb8-1b01-0000-0080-de835b681204: /build/S610_P/src/DataFlowEngine/ImbConfigurationNode.cpp: 396: ImbConfigurationNode::evaluate: ComIbmConfigurationNode: ConfigurationNode
Aug 27 13:51:31 mwd1 user:info WebSphere Broker v6102[1437928]: (DBK.WBI6POC)[8225]BIP3450E: An adapter error occurred during the processing of a message. The adapter error message is 'mqjbnd05 (A file or directory in the path name does not exist.): DBK.38dfecb8-1b01-0000-0080-de835b681204: MbErrorHandler.java: 242: throwableToMbException: :
Aug 27 13:51:31 mwd1 user:info WebSphere Broker v6102[2851010]: (DBK)[1]BIP8099I: Retrieved message for Execution Group: WBI6POC - : DBK.agent: /build/S610_P/src/AdminAgent/ImbAdminAgent.cpp: 2491: ImbAdminAgent::receiveEGResponse: :
Aug 27 13:51:31 mwd1 user:info WebSphere Broker v6102[2851010]: (DBK)[1]BIP8099I: Deploy Message Response sent to : ConfigMgr - : DBK.agent: /build/S610_P/src/AdminAgent/ImbAdminAgent.cpp: 2932: ImbAdminAgent::receiveEGResponse: :
|
|
|
| Back to top |
|
|
| smdavies99 |
| Posted: Thu Aug 27, 2009 10:50 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| Quote: |
The adapter error message is 'mqjbnd05 (A file or directory in the path name does not exist.):
|
If you do a search on this forum for mqjbnd05 you will see quite a few references to this issue. Have you by any chance looked at these?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| md.sadruddin |
| Posted: Thu Aug 27, 2009 11:23 pm Post subject: |
|
|
Novice
Joined: 27 Aug 2009
Posts: 12
|
yes, I have done all the possible things that has been said here in this forum and also all possible activities I got through googling ..
|
|
| Back to top |
|
|
| md.sadruddin |
| Posted: Fri Aug 28, 2009 1:29 am Post subject: |
|
|
Novice
Joined: 27 Aug 2009
Posts: 12
|
added the user trace .. does it give any idea?
| Quote: |
Timestamps are formatted in local time, 240 minutes before GMT.
Trace written by version 6102; formatter version 6102
2009-05-22 22:43:08.005547 7454 UserTrace BIP4149E: User-defined extension input parameter failed debug validation check.
Input parameter 2 passed into function ''cpiElementType'' is a NULL pointer.
Correct user-defined extension implementation accordingly.
2009-05-22 22:43:08.005592 7454 UserTrace BIP4149E: User-defined extension input parameter failed debug validation check.
Input parameter 2 passed into function ''cpiSetElementType'' is a NULL pointer.
Correct user-defined extension implementation accordingly.
2009-05-22 22:43:08.005599 7454 UserTrace BIP4149E: User-defined extension input parameter failed debug validation check.
Input parameter 2 passed into function ''cpiElementType'' is a NULL pointer.
Correct user-defined extension implementation accordingly.
2009-05-22 22:43:08.005604 7454 UserTrace BIP4149E: User-defined extension input parameter failed debug validation check.
Input parameter 2 passed into function ''cpiSetElementType'' is a NULL pointer.
Correct user-defined extension implementation accordingly.
2009-08-28 04:53:39.971744 8225 UserTrace BIP4040I: The Execution Group ''WBI6POC'' 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-08-28 04:53:39.972044 8225 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' connected to queue manager ''DQM''. The MQCC was '0' and the MQRC was '0'.
2009-08-28 04:53:39.972056 8225 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' on queue manager ''DQM''.
2009-08-28 04:54:23.249140 8225 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2009-08-28 04:54:23.249268 8225 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-08-28 04:54:23.249296 8225 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-08-28 04:54:23.249406 8225 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '17441' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.
2009-08-28 04:54:24.175746 8225 Warning BIP4041E: Execution group ''WBI6POC'' 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.
2009-08-28 04:54:24.175762 8225 RecoverableException BIP3522E: The adapter was unable to locate a required Java library.
The most likely cause of this exception is that the client libraries for the Enterprise Information System (EIS) are missing from the system. The EIS client libraries are not supplied with the message broker product and have to be obtained separately from the EIS provider. If the EIS client libraries have been installed and the broker has been configured to use them then make sure they have the correct permissions and that configurable service points to the correct location. The missing resource which caused this problem was: '{1}'. If the problem persists then it might be due to an internal problem with the product.
Obtain the missing client libraries from the EIS vendor and configure the broker to have access to these files using mqsichangeproperties command. Consult the documentation for the exact details (topic an09140). If this is not the cause of the missing class exception then contact IBM support.
2009-08-28 04:54:24.176104 8225 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' connected to queue manager ''DQM''. The MQCC was '0' and the MQRC was '0'.
2009-08-28 04:54:24.176130 8225 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' on queue manager ''DQM''.
2009-08-28 05:02:26.359290 8225 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2009-08-28 05:02:26.359406 8225 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-08-28 05:02:26.359430 8225 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-08-28 05:02:26.359498 8225 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '170' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.
2009-08-28 05:02:26.893994 8225 UserTrace BIP7080I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node with Subscription Point '''' has received a message of type 'Publish'.
The Publication Node with Subscription Point '''' has started processing a message.
No user action required.
2009-08-28 05:02:26.904702 8225 UserTrace BIP7081I: The Publication Node has matched '1' subscriptions to topic ''$SYS/Broker/DBK/Status/ExecutionGroup/WBI6POC'' for subscription point ''''.
The Publication Node has matched subscriptions for the current publication and topic.
No user action required.
2009-08-28 05:02:26.904752 8225 UserTrace BIP7082I: Node 'PubSubControlMsgFlow.MatchingNode': Publishing to destination 'PBD1NTD1:SYSTEM.BROKER.ADMIN.REPLY:4366674d677253756233' for user 'mqmnt'.
A publication destination is being added to the list of destinations to 'PBD1NTD1:SYSTEM.BROKER.ADMIN.REPLY:4366674d677253756233' for user 'mqmnt'.
No user action required.
2009-08-28 05:02:26.904784 8225 UserTrace BIP7085I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node has propagated a message to its output terminal for subscription point ''''.
The Publication Node has propagated the current message to its output terminal.
No user action required.
2009-08-28 05:02:26.905140 8225 UserTrace BIP2638I: The MQ output node 'PubSubControlMsgFlow.ListOutputNoSyncNode' attempted to write a message to queue ''SYSTEM.BROKER.ADMIN.REPLY'' connected to queue manager ''PBD1NTD1''. The MQCC was '0' and the MQRC was '0'.
2009-08-28 05:02:26.905176 8225 UserTrace BIP2622I: Message successfully output by output node 'PubSubControlMsgFlow.ListOutputNoSyncNode' to queue ''SYSTEM.BROKER.ADMIN.REPLY'' on queue manager ''PBD1NTD1''.
2009-08-28 05:02:26.905302 8225 UserTrace BIP4040I: The Execution Group ''WBI6POC'' 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-08-28 05:02:32.617012 1 UserTrace BIP2233I: Invoking user-defined extension 'onReset'('N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
About to invoke the specified user-defined extension with the specified parameters.
No user action required.
2009-08-28 05:02:32.617248 1 UserTrace BIP2234I: Returned from user-defined extension 'onReset' with result: 'N/A'.
The execution of the specified user-defined extension has been completed with the specified result.
No user action required.
2009-08-28 05:02:33.617980 1 UserTrace BIP2233I: Invoking user-defined extension 'onDelete'('N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
About to invoke the specified user-defined extension with the specified parameters.
No user action required.
2009-08-28 05:02:33.618308 1 UserTrace BIP2234I: Returned from user-defined extension 'onDelete' with result: 'N/A'.
The execution of the specified user-defined extension has been completed with the specified result.
No user action required.
2009-08-28 05:02:35.620244 1 UserTrace BIP2233I: Invoking user-defined extension 'onDelete'('N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
About to invoke the specified user-defined extension with the specified parameters.
No user action required.
2009-08-28 05:02:35.620564 1 UserTrace BIP2234I: Returned from user-defined extension 'onDelete' with result: 'N/A'.
The execution of the specified user-defined extension has been completed with the specified result.
No user action required.
2009-08-28 05:02:35.621892 1 UserTrace BIP2233I: Invoking user-defined extension 'DeleteNodeContext'(33b88a60, 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
About to invoke the specified user-defined extension with the specified parameters.
No user action required.
2009-08-28 05:02:35.621912 1 UserTrace BIP2234I: Returned from user-defined extension 'DeleteNodeContext' with result: 'N/A'.
The execution of the specified user-defined extension has been completed with the specified result.
No user action required.
2009-08-28 05:02:35.622260 1 UserTrace BIP2233I: Invoking user-defined extension 'DeleteNodeContext'(33bbf710, 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
About to invoke the specified user-defined extension with the specified parameters.
No user action required.
2009-08-28 05:02:35.622276 1 UserTrace BIP2234I: Returned from user-defined extension 'DeleteNodeContext' with result: 'N/A'.
The execution of the specified user-defined extension has been completed with the specified result.
No user action required.
2009-08-28 05:02:35.623164 1 UserTrace BIP2233I: Invoking user-defined extension 'DeleteNodeContext'(33ebde60, 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
About to invoke the specified user-defined extension with the specified parameters.
No user action required.
2009-08-28 05:02:35.623192 1 UserTrace BIP2234I: Returned from user-defined extension 'DeleteNodeContext' with result: 'N/A'.
The execution of the specified user-defined extension has been completed with the specified result.
No user action required.
2009-08-28 05:02:35.623540 1 UserTrace BIP2233I: Invoking user-defined extension 'DeleteNodeContext'(33ef4b10, 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
About to invoke the specified user-defined extension with the specified parameters.
No user action required.
2009-08-28 05:02:35.623556 1 UserTrace BIP2234I: Returned from user-defined extension 'DeleteNodeContext' with result: 'N/A'.
The execution of the specified user-defined extension has been completed with the specified result.
No user action required.
2009-08-28 05:02:35.623640 1 UserTrace BIP2233I: Invoking user-defined extension 'onDelete'('N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
About to invoke the specified user-defined extension with the specified parameters.
No user action required.
2009-08-28 05:02:35.623900 1 UserTrace BIP2234I: Returned from user-defined extension 'onDelete' with result: 'N/A'.
The execution of the specified user-defined extension has been completed with the specified result.
No user action required.
2009-08-28 05:02:35.625084 1 UserTrace BIP2233I: Invoking user-defined extension 'onDelete'('N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
About to invoke the specified user-defined extension with the specified parameters.
No user action required.
2009-08-28 05:02:35.625284 1 UserTrace BIP2234I: Returned from user-defined extension 'onDelete' with result: 'N/A'.
The execution of the specified user-defined extension has been completed with the specified result.
No user action required.
2009-08-28 05:02:35.627632 1 UserTrace BIP2233I: Invoking user-defined extension 'onDelete'('N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
About to invoke the specified user-defined extension with the specified parameters.
No user action required.
2009-08-28 05:02:35.627828 1 UserTrace BIP2234I: Returned from user-defined extension 'onDelete' with result: 'N/A'.
The execution of the specified user-defined extension has been completed with the specified result.
No user action required.
2009-08-28 05:02:37.852628 1 UserTrace BIP2233I: Invoking user-defined extension 'onDelete'('N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
About to invoke the specified user-defined extension with the specified parameters.
No user action required.
2009-08-28 05:02:37.852916 1 UserTrace BIP2234I: Returned from user-defined extension 'onDelete' with result: 'N/A'.
The execution of the specified user-defined extension has been completed with the specified result.
No user action required.
2009-08-28 05:02:37.854292 1 UserTrace BIP2233I: Invoking user-defined extension 'DeleteNodeContext'(34c727f0, 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
About to invoke the specified user-defined extension with the specified parameters.
No user action required.
2009-08-28 05:02:37.854312 1 UserTrace BIP2234I: Returned from user-defined extension 'DeleteNodeContext' with result: 'N/A'.
The execution of the specified user-defined extension has been completed with the specified result.
No user action required.
2009-08-28 05:02:37.854700 1 UserTrace BIP2233I: Invoking user-defined extension 'DeleteNodeContext'(34d15b70, 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
About to invoke the specified user-defined extension with the specified parameters.
No user action required.
2009-08-28 05:02:37.854716 1 UserTrace BIP2234I: Returned from user-defined extension 'DeleteNodeContext' with result: 'N/A'.
The execution of the specified user-defined extension has been completed with the specified result.
No user action required.
2009-08-28 05:02:37.855652 1 UserTrace BIP2233I: Invoking user-defined extension 'DeleteNodeContext'(34db45d0, 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
About to invoke the specified user-defined extension with the specified parameters.
No user action required.
2009-08-28 05:02:37.855668 1 UserTrace BIP2234I: Returned from user-defined extension 'DeleteNodeContext' with result: 'N/A'.
The execution of the specified user-defined extension has been completed with the specified result.
No user action required.
2009-08-28 05:02:37.856020 1 UserTrace BIP2233I: Invoking user-defined extension 'DeleteNodeContext'(339a1d50, 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
About to invoke the specified user-defined extension with the specified parameters.
No user action required.
2009-08-28 05:02:37.856048 1 UserTrace BIP2234I: Returned from user-defined extension 'DeleteNodeContext' with result: 'N/A'.
The execution of the specified user-defined extension has been completed with the specified result.
No user action required.
2009-08-28 05:02:37.856136 1 UserTrace BIP2233I: Invoking user-defined extension 'onDelete'('N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
About to invoke the specified user-defined extension with the specified parameters.
No user action required.
2009-08-28 05:02:37.856348 1 UserTrace BIP2234I: Returned from user-defined extension 'onDelete' with result: 'N/A'.
The execution of the specified user-defined extension has been completed with the specified result.
No user action required.
2009-08-28 05:02:37.857508 1 UserTrace BIP2233I: Invoking user-defined extension 'onDelete'('N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
About to invoke the specified user-defined extension with the specified parameters.
No user action required.
2009-08-28 05:02:37.857708 1 UserTrace BIP2234I: Returned from user-defined extension 'onDelete' with result: 'N/A'.
The execution of the specified user-defined extension has been completed with the specified result.
No user action required.
2009-08-28 05:02:37.859992 1 UserTrace BIP2233I: Invoking user-defined extension 'onDelete'('N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
About to invoke the specified user-defined extension with the specified parameters.
No user action required.
2009-08-28 05:02:37.860196 1 UserTrace BIP2234I: Returned from user-defined extension 'onDelete' with result: 'N/A'.
The execution of the specified user-defined extension has been completed with the specified result.
No user action required.
2009-08-28 05:02:44.195876 1 Information BIP2204I: Execution group using process '1765556' thread '1' stopped.
The execution group using process '1765556' and thread '1' has stopped. This may be because it has been instructed to do so or because it has encountered a problem.
No user action required. The execution group will be restarted automatically if need be.
2009-08-28 05:04:54.694160 1 Information BIP3501I: The execution group ''WBI6POC'' on broker ''DBK'' has SAP adapter components deployed to it which are being used in at least one message flow.
This execution group is running WebSphere Adapter SAP nodes.
None
2009-08-28 05:05:51.579328 8225 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2009-08-28 05:05:51.579648 8225 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-08-28 05:05:51.579668 8225 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-08-28 05:05:51.579736 8225 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '172' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.
2009-08-28 05:05:51.772760 8225 UserTrace BIP7080I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node with Subscription Point '''' has received a message of type 'Publish'.
The Publication Node with Subscription Point '''' has started processing a message.
No user action required.
2009-08-28 05:05:51.779356 8225 UserTrace BIP7081I: The Publication Node has matched '1' subscriptions to topic ''$SYS/Broker/DBK/Status/ExecutionGroup/WBI6POC'' for subscription point ''''.
The Publication Node has matched subscriptions for the current publication and topic.
No user action required.
2009-08-28 05:05:51.779420 8225 UserTrace BIP7082I: Node 'PubSubControlMsgFlow.MatchingNode': Publishing to destination 'PBD1NTD1:SYSTEM.BROKER.ADMIN.REPLY:4366674d677253756233' for user 'mqmnt'.
A publication destination is being added to the list of destinations to 'PBD1NTD1:SYSTEM.BROKER.ADMIN.REPLY:4366674d677253756233' for user 'mqmnt'.
No user action required.
2009-08-28 05:05:51.779444 8225 UserTrace BIP7085I: Node 'PubSubControlMsgFlow.MatchingNode': The Publication Node has propagated a message to its output terminal for subscription point ''''.
The Publication Node has propagated the current message to its output terminal.
No user action required.
2009-08-28 05:05:51.780648 8225 UserTrace BIP2638I: The MQ output node 'PubSubControlMsgFlow.ListOutputNoSyncNode' attempted to write a message to queue ''SYSTEM.BROKER.ADMIN.REPLY'' connected to queue manager ''PBD1NTD1''. The MQCC was '0' and the MQRC was '0'.
2009-08-28 05:05:51.780676 8225 UserTrace BIP2622I: Message successfully output by output node 'PubSubControlMsgFlow.ListOutputNoSyncNode' to queue ''SYSTEM.BROKER.ADMIN.REPLY'' on queue manager ''PBD1NTD1''.
2009-08-28 05:05:51.780956 8225 UserTrace BIP4040I: The Execution Group ''WBI6POC'' 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-08-28 05:05:51.781548 8225 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' connected to queue manager ''DQM''. The MQCC was '0' and the MQRC was '0'.
2009-08-28 05:05:51.781564 8225 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' on queue manager ''DQM''.
2009-08-28 05:06:17.196938 8225 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2009-08-28 05:06:17.197064 8225 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-08-28 05:06:17.197092 8225 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-08-28 05:06:17.197256 8225 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '17441' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.
2009-08-28 05:06:19.149974 8225 Warning BIP4041E: Execution group ''WBI6POC'' 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.
2009-08-28 05:06:19.149994 8225 RecoverableException BIP3450E: An adapter error occurred during the processing of a message. The adapter error message is ''mqjbnd05 (A file or directory in the path name does not exist.)
''.
This error was detected by the adapter. The following message describes the diagnostic information that is provided by the adapter ''mqjbnd05 (A file or directory in the path name does not exist.)
''.
Inspect the diagnostic information that is provided by the adapter. Further diagnostic information might be written to user trace. Inspect user trace for further information.
2009-08-28 05:06:19.150544 8225 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' connected to queue manager ''DQM''. The MQCC was '0' and the MQRC was '0'.
2009-08-28 05:06:19.150552 8225 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' on queue manager ''DQM''.
2009-08-28 05:14:55.566872 8225 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2009-08-28 05:14:55.566988 8225 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-08-28 05:14:55.567016 8225 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-08-28 05:14:55.567088 8225 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '208' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.
2009-08-28 05:20:59.580372 8225 UserTrace BIP4040I: The Execution Group ''WBI6POC'' 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-08-28 05:20:59.580700 8225 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' connected to queue manager ''DQM''. The MQCC was '0' and the MQRC was '0'.
2009-08-28 05:20:59.580712 8225 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' on queue manager ''DQM''.
2009-08-28 05:21:55.137464 8225 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
2009-08-28 05:21:55.137588 8225 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-08-28 05:21:55.137616 8225 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-08-28 05:21:55.137848 8225 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node 'ConfigurationMessageFlow.InputNode' to handle portion of incoming message of length '17441' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.
2009-08-28 05:21:57.051012 8225 Warning BIP4041E: Execution group ''WBI6POC'' 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.
2009-08-28 05:21:57.051032 8225 RecoverableException BIP3450E: An adapter error occurred during the processing of a message. The adapter error message is ''mqjbnd05 (A file or directory in the path name does not exist.)
''.
This error was detected by the adapter. The following message describes the diagnostic information that is provided by the adapter ''mqjbnd05 (A file or directory in the path name does not exist.)
''.
Inspect the diagnostic information that is provided by the adapter. Further diagnostic information might be written to user trace. Inspect user trace for further information.
2009-08-28 05:21:57.051424 8225 UserTrace BIP2638I: The MQ output node 'ConfigurationMessageFlow.outputNode' attempted to write a message to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' connected to queue manager ''DQM''. The MQCC was '0' and the MQRC was '0'.
2009-08-28 05:21:57.051444 8225 UserTrace BIP2622I: Message successfully output by output node 'ConfigurationMessageFlow.outputNode' to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' on queue manager ''DQM''.
Threads encountered in this trace:
1 7454 8225
|
|
|
| Back to top |
|
|
| Gaya3 |
| Posted: Fri Aug 28, 2009 1:44 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
|
| Back to top |
|
|
| md.sadruddin |
| Posted: Fri Aug 28, 2009 2:01 am Post subject: |
|
|
Novice
Joined: 27 Aug 2009
Posts: 12
|
Thanks fr reply -- i am using proper uid/pwd.
Strange thing is - Msgflow with SAP Request node gets deployed properly. Had there been a problem with library path, it should have thrown it for the SAP request message flow deployment as well.
Also, the SAP Input node related adapter gets deployed when i deploy it alone; but not the message flow. |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Fri Aug 28, 2009 2:28 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
| md.sadruddin wrote: |
| Also, the SAP Input node related adapter gets deployed when i deploy it alone; but not the message flow. |
i dont get you the statement,
i guess, when you deployed only the sap input node its deploying properly, when you attach the sap input node with some other nodes its not deploying isnt it.
hope sapjco, dll libraries have given properly for this sapinput adapter component
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| md.sadruddin |
| Posted: Fri Aug 28, 2009 2:42 am Post subject: |
|
|
Novice
Joined: 27 Aug 2009
Posts: 12
|
Thanks for reply..
I meant to say - if i deploy justthe adapter component, it gets deployed, but if i deploy a msgflow with just the SAPInput node .. it gives problem ..
I have created the adapter component by giving the library paths properly to the CONNECTOR project.
Can you please tell me if there is version compatibility that has to be matched between the SAP Adapter component and the libraries?
I have set the path of librfccm.o, sapjco.jar and libsapjcorfc.so in environment.
I am using 2.1.8 version of Jco Library |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Fri Aug 28, 2009 3:18 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
SAP Version also makes issues,
You have to give proper version while retrieving the SAP Business Objects
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| jbanoop |
| Posted: Fri Aug 28, 2009 5:54 am Post subject: |
|
|
Chevalier
Joined: 17 Sep 2005
Posts: 401
Location: SC
|
| Quote: |
-08-28 04:54:24.175762 8225 RecoverableException BIP3522E: The adapter was unable to locate a required Java library.
The most likely cause of this exception is that the client libraries for the Enterprise Information System (EIS) are missing from the system. The EIS client libraries are not supplied with the message broker product and have to be obtained separately from the EIS provider. If the EIS client libraries have been installed and the broker has been configured to use them then make sure they have the correct permissions and that configurable service points to the correct location. The missing resource which caused this problem was: '{1}'. If the problem persists then it might be due to an internal problem with the product.
Obtain the missing client libraries from the EIS vendor and configure the broker to have access to these files using mqsichangeproperties command. Consult the documentation for the exact details (topic an09140). If this is not the cause of the missing class exception then contact IBM support.
|
Have you completed the below steps ?
To set up the sapjco.jar file required to connect to SAP system
mqsichangeproperties B1 -c EISProviders -o SAP -n jarsURL -v <jarfile_location>
To set up native library files required for SAP
mqsichangeproperties B1 -c EISProviders -o SAP -n nativeLibs -v <nativelib_location>
To report the properties
mqsireportproperties B1 -c EISProviders -o SAP -r
This is required by the broker runtime. |
|
| Back to top |
|
|
| md.sadruddin |
| Posted: Mon Aug 31, 2009 12:22 am Post subject: |
|
|
Novice
Joined: 27 Aug 2009
Posts: 12
|
| yes, i have done these... mqsireportpropeties gives the result properly |
|
| Back to top |
|
|
| md.sadruddin |
| Posted: Tue Sep 15, 2009 5:18 am Post subject: The issue is Resolved |
|
|
Novice
Joined: 27 Aug 2009
Posts: 12
|
| we had to add '/usr/mqm/java/lib' in MQSI_LIBPATH32 (ours is 32 bit execution group) |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
