| Author |
Message
|
| Sanjayy |
 Posted: Sun Jan 31, 2016 7:12 pm Post subject: Application Errors in Event viewer |
 |
|
Novice
Joined: 06 Oct 2015
Posts: 12
|
Hi All,
Could you please provide me the solution for how to change the severity level from error to warnings in event viewer application errors from MQ side?
thanks in advance. |
|
| Back to top |
|
 |
| Sanjayy |
| Posted: Sun Jan 31, 2016 7:31 pm Post subject: |
|
|
Novice
Joined: 06 Oct 2015
Posts: 12
|
Channel 'CHNL.SVRCONN' to host 'host name (host ip)' ended abnormally.
this is the error message I got |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Jan 31, 2016 9:59 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Sanjayy wrote: |
Channel 'CHNL.SVRCONN' to host 'host name (host ip)' ended abnormally.
this is the error message I got |
Adjust the idle timeout to match on both ends to the channel and be less than the firewall timeout 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Sanjayy |
| Posted: Mon Feb 01, 2016 1:32 am Post subject: |
|
|
Novice
Joined: 06 Oct 2015
Posts: 12
|
Thank you fjp_saper
| Quote: |
| Adjust the idle timeout to match on both ends to the channel and be less than the firewall timeout |
Can you please tell me where can I adjust these things? and one more thing is I need to change the severity level of this Alert ERROR to WARNING in event viewer application logs. Could you please help me  |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Feb 01, 2016 5:30 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| Sanjayy wrote: |
Channel 'CHNL.SVRCONN' to host 'host name (host ip)' ended abnormally.
this is the error message I got |
What was the error message ID of this error? Errors logged to MQ error logs usually have AMQxxxx message IDs. Plesase post here the complete error.
What event viewer? The Windows operating system event viewer? If so, it is likely that TCPIP is the cause of the error. What is the error logged in the event viewer? Please include the complete error.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Feb 01, 2016 5:45 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Sanjayy wrote: |
Thank you fjp_saper
| Quote: |
| Adjust the idle timeout to match on both ends to the channel and be less than the firewall timeout |
Can you please tell me where can I adjust these things? |
In the channel configuration at both ends as my worthy associate points out.
| Sanjayy wrote: |
| I need to change the severity level of this Alert ERROR to WARNING in event viewer application logs. |
a) you can't
b) why would you want to? that's like taking the battery out of a smoke alarm because it keeps going off. While it's an effective solution in that it stops the alarm repeatedly sounding, the better solution is to find out where the smoke is coming from and stop that..... 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Feb 01, 2016 6:41 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
If you are monitoring the event viewer/windows application event log with some tool, you should very easily be able to configure that tool to respond to this particular ERROR as a warning instead.
"ended abnormally" is not the full error message. You should get some additional information in the message to help you actually prevent the error from happening again.
Unless it's because of bad networking between the client application and the queue manager.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| Sanjayy |
| Posted: Tue Feb 02, 2016 7:07 pm Post subject: |
|
|
Novice
Joined: 06 Oct 2015
Posts: 12
|
Thanks all,
it is windows event viewer log. I am getting the error is:
1/20/2016 09:29:41 - Process(6464.371549) User(username) Program(.exe) Host(hostname) Installation(Installation1) VRMF(7.5.0.3) QMgr(Qmgr)
Channel 'CHNL.SVRCONN' to host 'hostname (hostIP)' ended abnormally.
The channel program running under process ID 6464(3348) for channel 'CHNL.SVRCONN' ended abnormally. The host name is 'hostname (hostIP)'; in some cases the host name cannot be determined and so is shown as '????'.
Look at previous error messages for the channel program in the error logs to determine the cause of the failure. Note that this message can be excluded completely or suppressed by tuning the "ExcludeMessage" or "SuppressMessage" attributes under the "QMErrorLog" stanza in qm.ini. Further information can be found in the System Administration Guide.
thanks |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Feb 02, 2016 8:10 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
What is the error written to the errors folder/directory in the MQ installation filesystem?
...\qmgrs\yourqmgrname\errors\...
That error should provide an AMQnnnn kind of error, and a bit more of an explanation.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| manoj5007 |
| Posted: Wed Feb 03, 2016 12:10 am Post subject: |
|
|
Acolyte
Joined: 15 May 2013
Posts: 64
|
What you are trying to change is the event logging the application. The application has been laredy configured the level to be logged for each event and changing this is changing the applicaitons behaviour which is nethier possibel nor recommeneded.
The best way to implement will be configuring the tool monitoring the MQ logs. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Feb 03, 2016 5:07 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| manoj5007 wrote: |
What you are trying to change is the event logging the application. The application has been laredy configured the level to be logged for each event and changing this is changing the applicaitons behaviour which is nethier possibel nor recommeneded.
The best way to implement will be configuring the tool monitoring the MQ logs. |
Well, actually, the best way is to fix the underlying cause of the problem - not the symptom.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Feb 03, 2016 5:35 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bruce2359 wrote: |
| manoj5007 wrote: |
What you are trying to change is the event logging the application. The application has been laredy configured the level to be logged for each event and changing this is changing the applicaitons behaviour which is nethier possibel nor recommeneded.
The best way to implement will be configuring the tool monitoring the MQ logs. |
Well, actually, the best way is to fix the underlying cause of the problem - not the symptom. |
As I said above.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
