ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » error log files

Post new topic  Reply to topic
 error log files « View previous topic :: View next topic » 
Author Message
kirran
PostPosted: Fri Mar 11, 2016 12:15 am    Post subject: error log files Reply with quote

Novice

Joined: 29 Feb 2016
Posts: 18

hii,
iam new to message broker 7, iam using the flow like

(MQInputNode----ComputeNode-----MQOutputnode) iam getting exception and it go back to mqinputnode,but where can i see the error msg in error log are some were.i did not connect catch or failure terminal what will happen
Back to top
View user's profile Send private message
timber
PostPosted: Fri Mar 11, 2016 1:16 am    Post subject: Reply with quote

Grand Master

Joined: 25 Aug 2015
Posts: 1292

Errors are not written to a file on the filesystem unless you take specific action to make that happen.

You can see the ExceptionList tree in the message flow debugger.
You can capture the ExceptionList tree and write it to a file using the Trace node ( set the Pattern to ${ExceptionList} )

On Windows, uncaught exceptions are written to Windows Event Viewer ( Application log ).
On Unix/Linux they are written to the syslog ( normally /var/log/messages )
Back to top
View user's profile Send private message
smdavies99
PostPosted: Fri Mar 11, 2016 2:18 am    Post subject: Re: error log files Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

kirran wrote:
hii,
iam new to message broker 7, iam using the flow like

(MQInputNode----ComputeNode-----MQOutputnode) iam getting exception and it go back to mqinputnode,but where can i see the error msg in error log are some were.i did not connect catch or failure terminal what will happen


Message Broker 7 went out of support last year so it would be advisable to move to a newer version, say IIB 9 or IIB10

you could get a detailed description of your error by...
1) Adding a trace node to toyr flow
2) wire the trace node up to the Failure terminal of the MQInput Node
3) Set the Trace node pattern to be

${ExceptionList}

4) set the trace node output type TO FILE and the nadd a valid path and filename to the node.

Save, rebuild the bar file and run it again.

give it a go and see what happens.
_________________
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
View user's profile Send private message
kirran
PostPosted: Fri Mar 11, 2016 2:49 am    Post subject: Reply with quote

Novice

Joined: 29 Feb 2016
Posts: 18

thankyou.....i will try
Back to top
View user's profile Send private message
kirran
PostPosted: Fri Mar 11, 2016 3:25 am    Post subject: Reply with quote

Novice

Joined: 29 Feb 2016
Posts: 18

i have given pattern and file path in trace node ,i didnot got any exception list, the input msg as arrived to that path only.
Back to top
View user's profile Send private message
smdavies99
PostPosted: Fri Mar 11, 2016 3:37 am    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

I hate to say this but youy really do need one of the following

1) To attend a proper training course on the product. This Broker/IIB thing is very complicated.
2) To work with someone in your office who can see what you are doing and guide you towards the correct solution.

Even if you do 2) I would say that you still need to do 1).
_________________
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
View user's profile Send private message
kirran
PostPosted: Sat Mar 12, 2016 8:28 am    Post subject: Reply with quote

Novice

Joined: 29 Feb 2016
Posts: 18

mq inpute node-------compute----mqoutput node

in my flow exception has raised in compute node and is rolledback to firstnode i.e,mq inputnode,but i did not connect any failure or catch terminal for mqinput node .where this exception will go in mqinput node..................i used backout queue for thershold purpose givinen for 3 times ......after that i didnot find the msg may be it lost i think,,,,,,,,,,,,,can u give any answer and right flow to execute it .....
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Sat Mar 12, 2016 1:05 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

Well if the message is not in the backout queue, have you looked at the dead letter queue?
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
kirran
PostPosted: Sun Mar 13, 2016 12:36 am    Post subject: Reply with quote

Novice

Joined: 29 Feb 2016
Posts: 18

if deadlater queue is filled its capacityi i.e, we shold set an alert for that,where did it the msg goes.........can u plz provide solution
Back to top
View user's profile Send private message
smdavies99
PostPosted: Sun Mar 13, 2016 5:12 am    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

The first thing you should do is to look at the reasons why the messages ended up on the DLQ.
The RFHutil application (Support Pack IH03) is very useful for finding out the reason why messages were sent to the DLQ.
Then fix the problem.

As a longer term solution, adding a BOQ to the Queue used for the MQ INput Node is one way that many of us here handle that.

But as we have said, you really do need some proper training to give you a foundation upon which you can work.

I came to this product after 3+ years of MQ (Application Development and Admin) and I felt like a fish out of water until I'd attended a training course. This was back in 2002 and the product was a lot simpler then.
_________________
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
View user's profile Send private message
Gralgrathor
PostPosted: Sun Mar 13, 2016 5:29 am    Post subject: Reply with quote

Master

Joined: 23 Jul 2009
Posts: 297

smdavies99 wrote:
I came to this product after 3+ years of MQ (Application Development and Admin) and I felt like a fish out of water until I'd attended a training course.

I just looked up my first posts. Ouch.
_________________
A measure of wheat for a penny, and three measures of barley for a penny; and see thou hurt not the oil and the wine.
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » error log files
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.