Author |
Message
|
kevinobyrne |
Posted: Wed Nov 26, 2008 6:15 am Post subject: Adding SAP msgsets to broker archive fails in toolkit |
|
|
 Voyager
Joined: 17 Jul 2007 Posts: 83 Location: Ireland
|
Hi,
I'm having a problem with my toolkit (6.1.0.2 ifix003),
I have used the sap adapter/msgset creation wizard to generate some Inbound/Outbound msgsets, for use with a sap request node and a sap input node.
But I'm having an issue when I try to add them to a bar, I receive the following error:
BIP0182E Message Set compile error.
A exception was thrown while compiling the Message Set. The cause of the error was an exception of type "class java.lang.NullPointerException", with message "null". The stack trace at the time of the error was:
"java.lang.NullPointerException
at com.ibm.etools.msg.dictionary.XSDZipGenerator.fixExternalReferencesInternal(Unknown Source)
at com.ibm.etools.msg.dictionary.XSDZipGenerator.fixExternalReferencesInternal(Unknown Source)
at com.ibm.etools.msg.dictionary.XSDZipGenerator.fixExternalReferencesInternal(Unknown Source)
at com.ibm.etools.msg.dictionary.XSDZipGenerator.fixExternalReferencesInternal(Unknown Source)
at com.ibm.etools.msg.dictionary.XSDZipGenerator.fixExternalReferencesInternal(Unknown Source)
at com.ibm.etools.msg.dictionary.XSDZipGenerator.fixExternalReferencesInternal(Unknown Source)
at com.ibm.etools.msg.dictionary.XSDZipGenerator.fixExternalReferencesInternal(Unknown Source)
at com.ibm.etools.msg.dictionary.XSDZipGenerator.fixExternalReferencesInternal(Unknown Source)
at com.ibm.etools.msg.dictionary.XSDZipGenerator.fixExternalReferencesInternal(Unknown Source)
at com.ibm.etools.msg.dictionary.XSDZipGenerator.fixExternalReferencesInternal(Unknown Source)
at com.ibm.etools.msg.dictionary.XSDZipGenerator.fixExternalReferences(Unknown Source)
at com.ibm.etools.msg.dictionary.XSDZipGenerator.extractSchema(Unknown Source)
at com.ibm.etools.msg.dictionary.DictionaryCompiler.addMultipleToBarFile(Unknown Source)
at com.ibm.etools.mft.bar.internal.model.AddToBARFileOperation.multipleBarGeneratorDelegate(Unknown Source)
at com.ibm.etools.mft.bar.internal.model.AddToBARFileOperation.execute(Unknown 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 org.eclipse.jface.operation.ModalContext$ModalContextThread.run(Unknown Source)
"
Retry the operation and contact your IBM support center.
Operation failed
BIP0841E The resource messageSet.mset could not be added to broker archive file IncColMsgSets.bar.
A colleague of mine has no problem building a bar with the same projects (which would point to my environment), but after uninstalling and reinstalling the toolkit I am still receiving the same error (which would point to the msgsets).
Has anyone experienced this or has any ideas?
Thanks. |
|
Back to top |
|
 |
kimbert |
Posted: Wed Nov 26, 2008 6:37 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
This has been reported before ( not on this forum ). It seems to be intermittent. First I would advise you to start eclipse with the -clean option.
If that fails, create a new workspace and import your message set project.
If that also fails, open a PMR. |
|
Back to top |
|
 |
kevinobyrne |
Posted: Wed Nov 26, 2008 8:19 am Post subject: |
|
|
 Voyager
Joined: 17 Jul 2007 Posts: 83 Location: Ireland
|
Thanks,
I tried each of those without success. I raised a PMR yesterday, time to chase them up on it. |
|
Back to top |
|
 |
kimbert |
Posted: Wed Nov 26, 2008 8:35 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
Please can you post the PMR number. so that I can
- follow this up internally if necessary.
- quote the iFix number if/when other users encounter this
Thanks |
|
Back to top |
|
 |
kevinobyrne |
Posted: Wed Nov 26, 2008 8:48 am Post subject: |
|
|
 Voyager
Joined: 17 Jul 2007 Posts: 83 Location: Ireland
|
|
Back to top |
|
 |
MikeyWMB |
Posted: Tue Apr 27, 2010 8:12 am Post subject: Same error in WMB 7.0 |
|
|
Newbie
Joined: 27 Apr 2010 Posts: 2
|
I'm using WMB Toolkit 7.0 and am experiencing the same issue. Did anyone ever find a fix for this? |
|
Back to top |
|
 |
kevinobyrne |
Posted: Tue Apr 27, 2010 8:34 am Post subject: |
|
|
 Voyager
Joined: 17 Jul 2007 Posts: 83 Location: Ireland
|
I think I may have done the usual, workspace -clean, or new workspace to get around the issue. |
|
Back to top |
|
 |
kimbert |
Posted: Tue Apr 27, 2010 9:18 am Post subject: |
|
|
 Jedi Council
Joined: 29 Jul 2003 Posts: 5542 Location: Southampton
|
See previous post by kevinobyrne - you need to request that fix.
If that doesn't solve it, open a PMR and quote this thread in your problem description. |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Apr 27, 2010 4:58 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
kimbert wrote: |
See previous post by kevinobyrne - you need to request that fix. |
Of course, in order to request that fix, you have to
kimbert wrote: |
open a PMR and quote this thread in your problem description. |
|
|
Back to top |
|
 |
MikeyWMB |
Posted: Fri Apr 30, 2010 1:58 am Post subject: Same error in WMB 7.0 |
|
|
Newbie
Joined: 27 Apr 2010 Posts: 2
|
The -clean option didn't resolve the issue. But I exported the Project Interface File and reimported into a new workspace which has resolved the issue. |
|
Back to top |
|
 |
|