| Author |
Message
|
| whiting |
 Posted: Thu Sep 20, 2012 5:31 am Post subject: finding mqsicreatebar errors |
 |
|
Acolyte
Joined: 26 Mar 2002
Posts: 64
Location: Greenville, SC
|
Is there a way to find errors in a message flow or workspace when mqsireadbar fails to build?
I know that I can open the workspace in a toolkit, but I'm looking for an easier solution for our build server. Most developers will not be able to collect the files from the build server and copy them back to their local desktop to troubleshoot.
Is problem data stored somewhere by eclipse?
//Bill |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Thu Sep 20, 2012 5:36 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Yes, its stored in the .metadata directory in the log file.
Your developers should be using the same Ant script to invoke mqsicreatebar as the build server does. Developers should never build bars manually.
Therefore, the build server shouldn't have any errors that the developers don't have in the local.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| whiting |
| Posted: Thu Sep 20, 2012 5:50 am Post subject: .log didn't help |
|
|
Acolyte
Joined: 26 Mar 2002
Posts: 64
Location: Greenville, SC
|
In the latest instance, the problem was that the .project file did not get checked in, so a needed project was not referenced.
Neither the output from mqsireadbar nor the .metadata/.log files provided a clue as to the root cause ("could not locate sub-flow", in this case).
Thanks for the feedback
//Bill |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Sep 20, 2012 6:20 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Again, developers should never rely on their local to close out activities. The person checking in the code should not be the one conducting the code review. The code reviewer should "update view", use the Ant script to build the bar, and perform the functional test of the activity.
It all comes down to having a consistent, repeatable build process before you mark an activity 'Ready For Build' (ie. before it gets to the build server). This implies at least two if not more builds apart from the developer's local before it ever gets to the build server.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER
Last edited by lancelotlinc on Thu Sep 20, 2012 7:24 am; edited 1 time in total |
|
| Back to top |
|
|
| whiting |
| Posted: Thu Sep 20, 2012 6:37 am Post subject: build process |
|
|
Acolyte
Joined: 26 Mar 2002
Posts: 64
Location: Greenville, SC
|
Unfortunately I'm stuck w/ CA Harvest. It is extremely arcane.
Having a good process helps to prevent the need to troubleshoot a failed build. However, if the build fails in mqsicreatebar, there isn't much help to determine the cause.
//Bill |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Sep 20, 2012 7:02 am Post subject: Re: build process |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| whiting wrote: |
| if the build fails in mqsicreatebar, there isn't much help to determine the cause. |
Why would a developer check in a failed build? Wouldn't you require your developers to check in code that works?
Hence the requirement for developers to avoid building bars manually: they must certify by the act of checking in code that their code can be built successfully by the scripts.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Sep 20, 2012 7:04 am Post subject: Re: build process |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| whiting wrote: |
| Unfortunately I'm stuck w/ CA Harvest. It is extremely arcane. |
Harvest can invoke Ant just as easily as it can mqsicreatebar. Write an Ant script and invoke Ant from Harvest rather than mqsicreatebar directly. Then require your developers to build their bars with the same Ant script.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Sep 20, 2012 6:36 pm Post subject: Re: build process |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| whiting wrote: |
Unfortunately I'm stuck w/ CA Harvest. It is extremely arcane.
Having a good process helps to prevent the need to troubleshoot a failed build. However, if the build fails in mqsicreatebar, there isn't much help to determine the cause.
//Bill |
You need to run mqsicreatebar in verbose mode. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mapa |
| Posted: Thu Sep 20, 2012 11:23 pm Post subject: |
|
|
Master
Joined: 09 Aug 2001
Posts: 257
Location: Malmö, Sweden
|
Agree with the verbose mode.
However that flag is not documented in the Info Center, nor on the command itself so here it is "-trace". |
|
| Back to top |
|
|
| whiting |
| Posted: Mon Sep 24, 2012 6:40 am Post subject: -trace helped |
|
|
Acolyte
Joined: 26 Mar 2002
Posts: 64
Location: Greenville, SC
|
Thanks for the tip on -trace.
In this case the final error was "errors in workspace", but that was more helpful than what I was getting before.
//Bill |
|
| Back to top |
|
|
| mapa |
| Posted: Mon Sep 24, 2012 6:52 am Post subject: |
|
|
Master
Joined: 09 Aug 2001
Posts: 257
Location: Malmö, Sweden
|
I see now that it is actually a documented flag on the command in WMBT8.
You may also sometimes use the "-skipWSErrorCheck" flag as well.
Also not documented in WMBT7 FP3.
| Code: |
'-skipWSErrorCheck' to ignore the workspace error that is not related to the
required content to be put in the archive file (optional)
|
I prefer to clean up the project references instead normally, but sometimes they are transient. I actually use this flag by default on our 7.0.0.3 builds. |
|
| Back to top |
|
|
|
|
