| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| No logs written in WMB log |
« View previous topic :: View next topic » |
| Author |
Message
|
| RaviKrG |
 Posted: Mon Jan 26, 2009 12:19 am Post subject: No logs written in WMB log |
 |
|
Master
Joined: 07 Sep 2008
Posts: 240
|
Hi, My Env is
WMB6 toolkit on Windows XP
Broker on Solaris
Configuration manager on Solaris
Broker/Configuration Manager uses same queue manager
The Queue manager is on solaris
Now I am able to deply the flow to the broker through the toolkit also tested by sending messages and receiving at other ends.
Now I am trying to see the logs in the broker log in path /var/adm/messages but there are no logs written for the deployement part, also if there is any problem and the message is backed out then also there is nothing updated in this file.
But if I give any command on solaris to stop/start broker and i encounter any problem then it logs the entries in /var/adm/messages
Can anybody shed come light on this. |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Jan 26, 2009 12:56 am Post subject: Re: No logs written in WMB log |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Is this connected to this thread?
| RaviKrG wrote: |
| Now I am trying to see the logs in the broker log in path /var/adm/messages but there are no logs written for the deployement part, |
Deployment messages are reported to the config mgr, and are visible through the event viewer.
| RaviKrG wrote: |
| also if there is any problem and the message is backed out then also there is nothing updated in this file. |
Do you mean a deployment message or a data message passing through a flow? The first is as above, the second isn't logged by the broker because there's nothing wrong with the broker - functioning as designed!
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| RaviKrG |
| Posted: Tue Jan 27, 2009 7:47 pm Post subject: |
|
|
Master
Joined: 07 Sep 2008
Posts: 240
|
Vitor,
Is this connected to this thread? - Not exactly
Deployment messages are reported to the config mgr, and are visible through the event viewer. - this is right but the config mgr is on solaris and only the toolkit is on windows also the event viewer(win on which toolkit is installed) does not have any log info related to wmb.
Do you mean a deployment message or a data message passing through a flow?
when the flow is deplyed I think the broker should have some info that the flow has been deployed (Please correct me if I am wrong) something like this
Deployed Message Received from the ConfigMgr - processing UOW : Broker_Name.agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 963: ImbAdminAgent::readAdministrationMessages: :
Deployed message for Execution Group tag sent to - Executiongroup :Broker_Name.agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 7454: ImbAdminAgent::SendMessage: :
Deployed messages for Execution Groups - committed UOW, awaiting Execution Group response :Broker_Name .agent: /build/S500_P/src/AdminAgent/ImbAdminAgent.cpp: 1761: ImbAdminAgent::receiveCMRequest:
Also for data message if the broker encounters any problem then should it not give some info as below (before when there was any problem i was getting error something like)
Exception condition detected on input node 'io.FileInput'. : Broker_Name.763d62ed-1e01-0000-0080-808c3fd1e0b8: /build/S610_P/src/Dat
aFlowEngine/TemplateNodes/ImbCallableTemplateNode.cpp: 1511: ImbCallableTemplateNode::processMessage: ComIbmFileInputNode: io
#FCMComposite_1_6
Error detected whilst processing a message in node 'io.Compute'. : Broker_Name.763d62ed-1e01-0000-0080-808c3fd1e0b8: /build/S610_P/s
rc/DataFlowEngine/ImbComputeNode.cpp: 464: ImbComputeNode::evaluate: ComIbmComputeNode: io#FCMComposite_1_3 |
|
| Back to top |
|
|
| RaviKrG |
| Posted: Tue Jan 27, 2009 7:53 pm Post subject: |
|
|
Master
Joined: 07 Sep 2008
Posts: 240
|
To add to my previous post :
I have a flow as MQINPUT NODE --> COMPUTE NODE --> ROUTE TO LABEL
LABEL --> COMPUTE --> MQOUTPUT NODE
Flow was developed on win(only toolkit is there) and deployed to teh broker(broker, ConfigMGR and the queue manager for Broker and ConfigMGR) is on solaris.
I have sent one message
<FILE><FILENAME>ABC</FILENAME></FILE>
but I got this error on broker as
Exception condition detected on input node 'FileTransfer.TEST.INPUT.FILE.QUEUE'. : Broker.6e368d02-1f01-0000-0080-cfca6a06785d: /build/S610_P/src/DataFlowEngine/ImbCommonInputNode.cpp: 1585: ImbCommonInputNode::run: ComIbmMQInputNode: FileTransfer#FCMComposite_1_1
Error detected whilst processing a message in node 'FileTransfer.RouteToFileName'. : Broker.6e368d02-1f01-0000-0080-cfca6a06785d: /build/S610_P/src/DataFlowEngine/BasicNodes/ImbRouterNode.cpp: 318: ImbRouterNode::evaluate: ComIbmRouteToLabelNode: FileTransfer#FCMComposite_1_3
RouteToLabel node 'FileTransfer.RouteToFileName' unable to locate Label node ''. : Broker.6e368d02-1f01-0000-0080-cfca6a06785d: /build/S610_P/src/DataFlowEngine/BasicNodes/ImbRouterNode.cpp: 294: ImbRouterNode::evaluate: ComIbmRouteToLabelNode: FileTransfer#FCMComposite_1_3 |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Jan 27, 2009 11:58 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Broker is reporting to the system event log problems it has encountered.
This behaviour is the same on all platforms. Successful operations like deploys are not reported to system event logs.
In the example you just provided shows this.
'FileTransfer.RouteToFileName' unable to locate Label node ''.
FileTransfer = the name of your flow
RouteToFileName = name of the node where the problem was detected.
'unable to locate label node' = the nature of the problem.
To put it plainly, the flow passed bad data to the route to label node.
The previous two messages indicated that an exception occurred. Get used to this and look for the final message in the group. That will give you the detail.
If I encountered the above problem, I would do the following
1) Insert a trace node between the Comput Node and the Route to Label node.
2) configure the trace to output the part of the message tree that holds the value of the label you are trying to route to.
But I would also check that I had configured the properties of the compute node correctly first.
As a final hint, I would also make sure that I had some proper exceptionlist handling code in the flow so that I could capture all the relevant information about the exception. This is a vital component to any serious MB developers toolbox.
_________________
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 |
|
|
|
|
|
| |
|
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
|
|
|
|
