| Author |
Message
|
| mapa |
 Posted: Tue Oct 11, 2011 3:42 am Post subject: Yet another mqsicreatebar question - tracking errors |
 |
|
Master
Joined: 09 Aug 2001
Posts: 257
Location: Malmö, Sweden
|
There are quite a lot of topics for mqsicreatebar but after reading them (lost count after 10 or so posts) I didn't find an answer to my question.
Post is divided into the little longer background and the actual question:
Question
How can I find out more specific error details when the mqsicreatebar fails?
This doesn't tell me my problem:
Short error:
| Code: |
ERROR:
Processing file eCom_PartsInquiry.msgflow
Failed to add file eCom_PartsInquiry.msgflow to archive file
File 'eCom_PartsInquiry_Mapping.msgmap' contains error
|
My concern is for projects such as this that I can build in the toolkit but when using same source fails with mqsicreatebar.
Most projects work but some doesn't, and I haven't been able to tell any significant difference between them yet.
I know of and are using:
-trace
-skipWSErrorCheck (new for 7.0.0.3)
-.metadata/.log
Version: 7.0.0.3
Build id: 7.0.0.3-20110825_1025
Am I missing something or might I just go along and do a PMR?
Background
I've started to use mqsicreatebar as part of the release process in our V6.1 --> V7.0 migration project.
The projects are opened in WMBT7 and migrated. Changing only minor parts like adding svn:keywords.
Flows and messagesets are build in the toolkit and deployed to dev.
When this works the projects are committed and then tagged in Subversion.
The tag is exported (no .svn) and the needed wmb projects are then moved to the directory which will be specified in the -d flag to mqsicreatebar. Projects to be built are specified and then each project is scanned for project-references that are also added to the -p flag of the build, each project-reference .project is also scanned for more project-references (transient dependencies).
This works fine most of the time.
However for some projects I get an error on mqsicreatebar.
Projects that works fine to build if I open them in the Toolkit and import the same projects that is used for mqsicreatebar.
This command:
Command:
| Code: |
[INFO] { Try to compile again. }
[INFO] CommandProcessor: doCompile { doCompile }
[INFO] XSLTCompiler: canAddToBarFile { }
[INFO] AdapterCompiler: canAddToBarFile { }
[INFO] PHPCompiler: canAddToBarFile { }
[INFO] IDLCompiler: canAddToBarFile { }
[INFO] JarCompiler: canAddToBarFile { }
[INFO] AddToBARFileOperation: barGeneratorDelegate { }
[INFO] { addToBarFile: Delegate: com.ibm.etools.mft.flow.compiler.MessageFlowCo
mpiler fileToAdd: L/'PartsInquiry/'eCom_PartsInquiry.msgflow }
[ERROR] { Error adding to BAR Model. fileToAdd: L/'PartsInquiry/'e
Com_PartsInquiry.msgflow } - com.ibm.etools.mft.bar.model.BrokerArchiveExceptio
n
com.ibm.etools.mft.flow.compiler.PropertyCompilerException: File 'eCom_P
artsInquiry_Mapping.msgmap' contains error
at com.ibm.etools.mft.ibmnodes.compilers.MappingRootPropertyCompiler.com
pile(Unknown Source)
at com.ibm.etools.mft.flow.compiler.PropertyCompilerDelegate.compile(Unk
nown Source)
at com.ibm.etools.mft.flow.compiler.PropertyCompilerDelegate.compileAndS
tore(Unknown Source)
at com.ibm.etools.mft.flow.compiler.MessageFlowGenerator.addNestedFlow(U
nknown Source)
at com.ibm.etools.mft.flow.compiler.MessageFlowCompiler.addNodesAndTheir
ConfigurableProperties(Unknown Source)
at com.ibm.etools.mft.flow.compiler.MessageFlowCompiler.addAllNodes(Unkn
own Source)
at com.ibm.etools.mft.flow.compiler.MessageFlowCompiler.flattenOneLevel(
Unknown Source)
at com.ibm.etools.mft.flow.compiler.MessageFlowCompiler.flattenMessageFl
ow(Unknown Source)
at com.ibm.etools.mft.flow.compiler.MessageFlowCompiler.compile(Unknown
Source)
at com.ibm.etools.mft.flow.compiler.MessageFlowCompiler.addToBarFile(Unk
nown Source)
at com.ibm.etools.mft.bar.internal.model.AddToBARFileOperation.barGenera
torDelegate(Unknown Source)
at com.ibm.etools.mft.bar.internal.model.AddToBARFileOperation.processDe
ployables(Unknown Source)
at com.ibm.etools.mft.bar.internal.model.AddToBARFileOperation.execute(U
nknown Source)
at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(Unknown Source)
at org.eclipse.core.internal.resources.Workspace.run(Unknown Source)
at org.eclipse.ui.actions.WorkspaceModifyOperation.run(Unknown Source)
at com.ibm.etools.mft.bar.internal.model.BrokerArchiveIOFile.addEntry(Un
known Source)
at com.ibm.etools.mft.bar.cmdline.CommandProcessor.doCompile(Unknown Sou
rce)
at com.ibm.etools.mft.bar.cmdline.CommandProcessor.rebuild(Unknown Sourc
e)
at com.ibm.etools.mft.bar.cmdline.CommandProcessor.process(Unknown Sourc
e)
at com.ibm.etools.mft.bar.cmdline.CompilerLaunch.run(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithEx
ception(Unknown Source)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(Unknown Source)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runAppli
cation(Unknown Source)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Un
known Source)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Unknown Source)
at org.eclipse.equinox.launcher.Main.basicRun(Unknown Source)
at org.eclipse.equinox.launcher.Main.run(Unknown Source)
at org.eclipse.equinox.launcher.Main.main(Unknown Source)
ERROR:
Processing file eCom_PartsInquiry.msgflow
Failed to add file eCom_PartsInquiry.msgflow to archive file
File 'eCom_PartsInquiry_Mapping.msgmap' contains error
File 'eCom_PartsInquiry_Mapping.msgmap' contains error
[INFO] CommandProcessor: saveBar { saveBar }
BIP0988W Error occurred while completing mqsicreatebar command.
|
.metadata/.log
| Code: |
!SESSION 2011-10-11 12:52:55.796 -----------------------------------------------
eclipse.buildId=unknown
java.fullversion=JRE 1.6.0 IBM J9 2.4 Windows Server 2003 x86-32 jvmwi3260sr9-20110324_78506 (JIT enabled, AOT enabled)
J9VM - 20110324_078506
JIT - r9_20101028_17488ifx3
GC - 20101027_AA
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=sv_SE
Framework arguments: -noupdate -application com.ibm.etools.mft.bar.cmdline.mqsicreatebar -trace -skipWSErrorCheck -cleanBuild -b ecom124.bar -p baseline-errorhandler-rfh2-sub add-rfh2-with-PhysicalID-V2 LookupService remove-rfh2 SAPAdapter_toSAPMsgSet PartsInquiry -o PartsInquiryeCom_PartsInquiry.msgflow -wmbtData
Command-line arguments: -noupdate -os win32 -ws win32 -arch x86 -application com.ibm.etools.mft.bar.cmdline.mqsicreatebar -trace -skipWSErrorCheck -data . -cleanBuild -b ecom124.bar -p baseline-errorhandler-rfh2-sub add-rfh2-with-PhysicalID-V2 LookupService remove-rfh2 SAPAdapter_toSAPMsgSet PartsInquiry -o PartsInquiry/eCom_PartsInquiry.msgflow -wmbtData
!ENTRY org.eclipse.core.resources 2 10035 2011-10-11 12:52:57.937
!MESSAGE The workspace exited with unsaved changes in the previous session; refreshing workspace to recover changes.
!ENTRY org.eclipse.osgi 2 1 2011-10-11 12:53:19.531
!MESSAGE NLS missing message: WSDL_GatewayNonGatewayString in: com.ibm.etools.mft.ibmnodes.plugin.ibmnodesresources
!ENTRY org.eclipse.osgi 2 1 2011-10-11 12:53:19.531
!MESSAGE NLS missing message: tooltipFTETransferMode in: com.ibm.etools.mft.ibmnodes.plugin.ibmnodesresources
!ENTRY org.eclipse.osgi 2 1 2011-10-11 12:53:19.531
!MESSAGE NLS missing message: CICS_GROUP_HEADER_Node_ConnectionDetails in: com.ibm.etools.mft.ibmnodes.plugin.ibmnodesresources
!ENTRY org.eclipse.osgi 2 1 2011-10-11 12:53:19.531
!MESSAGE NLS missing message: CICS_GROUP_HEADER_Broker_ConnectionDetails in: com.ibm.etools.mft.ibmnodes.plugin.ibmnodesresources
!ENTRY org.eclipse.wst.server.core 4 0 2011-10-11 12:56:45.656
!MESSAGE Error during shutdown
!STACK 0
org.eclipse.core.runtime.AssertionFailedException: null argument:
at org.eclipse.core.runtime.Assert.isNotNull(Unknown Source)
at org.eclipse.core.runtime.Assert.isNotNull(Unknown Source)
at org.eclipse.core.internal.events.ResourceChangeListenerList.remove(Unknown Source)
at org.eclipse.core.internal.events.NotificationManager.removeListener(Unknown Source)
at org.eclipse.core.internal.resources.Workspace.removeResourceChangeListener(Unknown Source)
at org.eclipse.wst.server.core.internal.ResourceManager.shutdownImpl(Unknown Source)
at org.eclipse.wst.server.core.internal.ResourceManager.shutdown(Unknown Source)
at org.eclipse.wst.server.core.internal.ServerPlugin.stop(Unknown Source)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl$3.run(Unknown Source)
at java.security.AccessController.doPrivileged(Unknown Source)
at org.eclipse.osgi.framework.internal.core.BundleContextImpl.stop(Unknown Source)
at org.eclipse.osgi.framework.internal.core.BundleHost.stopWorker(Unknown Source)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.suspend(Unknown Source)
at org.eclipse.osgi.framework.internal.core.Framework.suspendBundle(Unknown Source)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.decFWSL(Unknown Source)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(Unknown Source)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.shutdown(Unknown Source)
at org.eclipse.osgi.framework.internal.core.SystemBundle.suspend(Unknown Source)
at org.eclipse.osgi.framework.internal.core.Framework.shutdown(Unknown Source)
at org.eclipse.osgi.framework.internal.core.Framework.close(Unknown Source)
at org.eclipse.osgi.framework.internal.core.OSGi.close(Unknown Source)
at org.eclipse.core.runtime.adaptor.EclipseStarter.shutdown(Unknown Source)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.eclipse.equinox.launcher.Main.invokeFramework(Unknown Source)
at org.eclipse.equinox.launcher.Main.basicRun(Unknown Source)
at org.eclipse.equinox.launcher.Main.run(Unknown Source)
at org.eclipse.equinox.launcher.Main.main(Unknown Source)
|
|
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Tue Oct 11, 2011 4:25 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Doesn't seem as through you sourced the MQSI profile before you invoked mqsicreatebar. Also, no projects in the workspace, even ones you dont reference, can contain any errors whatsoever.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Oct 11, 2011 5:06 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| lancelotlinc wrote: |
| Doesn't seem as through you sourced the MQSI profile before you invoked mqsicreatebar. Also, no projects in the workspace, even ones you dont reference, can contain any errors whatsoever. |
And I'm only writing to stress the second sentence.
The ENTIRE WORKSPACE PASSED TO MQSICREATEBAR must be error free. |
|
| Back to top |
|
|
| mapa |
| Posted: Tue Oct 11, 2011 11:20 am Post subject: |
|
|
Master
Joined: 09 Aug 2001
Posts: 257
Location: Malmö, Sweden
|
No, I didn't source the mqsiprofile, will add that.
However the question is how to get more detailed info about the specific error?
What you say about that no project can contain errors, is that still true if you specify the:
-skipWSErrorCheck
I delete the .metadata directory between builds and only add the projects needed, including transient dependencies, to the -p flag. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Oct 11, 2011 11:30 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| mapa wrote: |
No, I didn't source the mqsiprofile, will add that.
However the question is how to get more detailed info about the specific error?
What you say about that no project can contain errors, is that still true if you specify the:
-skipWSErrorCheck
I delete the .metadata directory between builds and only add the projects needed, including transient dependencies, to the -p flag. |
Apart from the profile sourcing the error is quite specific. One of the maps in the one of the project (transient dependencies?) is not error free.
| Quote: |
| File 'eCom_PartsInquiry_Mapping.msgmap' contains error |
Could that be due to a non referenced message set or a message set not in the expected place? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Oct 11, 2011 11:51 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Toolkit commands do not require the sourcing of mqsiprofile.
mqsicreatebar is a Toolkit command. |
|
| Back to top |
|
|
| mapa |
| Posted: Tue Oct 11, 2011 2:06 pm Post subject: |
|
|
Master
Joined: 09 Aug 2001
Posts: 257
Location: Malmö, Sweden
|
Yes, the server only have the toolkit installed and is not sourcing the mqsiprofile.
Works like a charm (except that it takes time).
There was a hard to spot typo in the buildscript that caused a referenced messageset to not be included in the -p after I added some validation checks.
Previous projects that didn't build does build successfully now.
Thanks fjb_saper for pointing me in the right direction.
I suspect the errors produced with -trace is sufficient after all... |
|
| Back to top |
|
|
|
|
