| Author |
Message
|
| punky |
 Posted: Thu Oct 18, 2012 6:59 am Post subject: Error thrown while deploying the bar file in broker |
 |
|
Apprentice
Joined: 26 May 2011
Posts: 44
Location: India
|
Hi Masters,
I am struck up deploying a bar file in the Broker.
Whenever I am trying to deploy the bar file in the broker it throws the following two errors.
BIP4395E: Java exception: 'com.ibm.broker.schemadeploy.MbXSDInternalError'; thrown from class name: 'com.ibm.broker.schemadeploy.MbXSDDeployDirector', method name: 'compileMessageSetSchemas', file: 'MbXSDDeployDirector.java', line: '517' 
BIP4395E: Java exception: 'java.lang.OutOfMemoryError'; thrown from class name: 'sun.reflect.NativeMethodAccessorImpl', method name: 'invoke0', file: 'NativeMethodAccessorImpl.java', line: '-2'
I have tried deploying through command line using mqsideploy command as well as through the toolkit.
I have reimported the adapter configuration and tried but the result remains the same.
So require your help to guide me how should I analyse the case of this issue.
Regards,
Punky |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Thu Oct 18, 2012 7:25 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Sounds like your trying to migrate message flows from one version of Broker to another. Simply opening a bar file in the new toolkit is not sufficient.
Do you have a source code control system that stores the old source code?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| punky |
| Posted: Thu Oct 18, 2012 7:50 am Post subject: |
|
|
Apprentice
Joined: 26 May 2011
Posts: 44
Location: India
|
Hi lancelotlinc,
I am able to deploy the bar file for message flow, but unable to deploy the bar fle for message set.
I have tried previous source codes but the result is same even for old sources.
Appears like there is some memoryy problem.
Regards,
Punky |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Oct 18, 2012 7:51 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
You are avoiding the question: why are you doing this? Are you trying to migrate from one version of Broker to the other?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| punky |
| Posted: Thu Oct 18, 2012 8:01 am Post subject: |
|
|
Apprentice
Joined: 26 May 2011
Posts: 44
Location: India
|
lancelotlinc,
I am not doing the migration from one broker to other.
There was some structure change from SAP side.
So just reimported the adapter connection.
And now I am facing difficult deploy the message set.
I am using WMB 7.0 with a fix (MB7000_7002) maybe that is causing problem. The version of adapter which I am getting now is 7.0.3 which should be 7.0.2
Regards,
Punky |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Oct 18, 2012 8:11 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
WMB version number have four digits, not two or three. 7.0.0.1, 7.0.0.2, 7.0.0.3, 7.0.0.4, 7.0.0.5.
Its not clear from your post exactly which one you are using.
What is the 'effective level' of the WMB runtime you are trying to deploy to? From the commandline of the local box that is hosting the WMB runtime you are deploying to, run mqsireportbroker and post the 'effective level' back here on the forum.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| punky |
| Posted: Thu Oct 18, 2012 8:37 am Post subject: |
|
|
Apprentice
Joined: 26 May 2011
Posts: 44
Location: India
|
The MB version is 7.0.0.2
The runtime version is 7.0
Regards,
punky |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Oct 18, 2012 8:45 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| punky wrote: |
The MB version is 7.0.0.2
The runtime version is 7.0
Regards,
punky |
How can we help you if you will not follow instructions?
WHAT IS THE EFFECTIVE LEVEL OF YOUR RUNTIME?
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Oct 18, 2012 8:45 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Check for additional errors on the broker logs at the time of deploy. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Oct 18, 2012 8:53 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
There are forty-three SAP bug fixes in various WMB V7 fixpacks. If we don't know what version she is on, we cannot determine if applying a fixpack may help.
Since her SAP people are updating their connector code, I suspect she may need an up-to-date version of WMB. Even if she does not need an up-to-date version of WMB, if the effective level is still pristine, the error she is getting could possibly be due to the lack of knowledge or training about how to set the effective level.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| punky |
| Posted: Thu Oct 18, 2012 8:53 am Post subject: |
|
|
Apprentice
Joined: 26 May 2011
Posts: 44
Location: India
|
I am working as a developer so don't have access to run the command "mqsireportbroker". I will get bact to you with this information.
the entire error message is :
Begin running task [Deploying [MSP_CRM_BPPublishFromCRM.bar] to execution group [ESB_EG_02]]
BIP2087E: Broker RSTGBRKA was unable to process the internal configuration message.
The entire internal configuration message failed to be processed successfully.
Use the messages following this message to determine the reasons for the failure. If the problem cannot be resolved after reviewing these messages, contact your IBM Support center. Enabling service trace may help determine the cause of the failure.
BIP4041E: Execution group 'ESB_EG_02' received an invalid configuration message. See the following messages for details of the error.
The broker was asked to deploy a message flow which contained properties that were not recognized by the broker. This typically results from a message flow requiring a version or type of node that is not supported by the broker installation.
Check that the message flow is only using properties or nodes that are supported on the broker. Check that all necessary user-defined extensions are installed and that they are of a version that is compatible with the message flow.
BIP5024E: The creation and preprocessing of the XML schemas in message set 'MS_CRM_BPPublishFromCRM.xsdzip' has failed.
Review previous messages to find out why the error occurred.
BIP4395E: Java exception: 'java.lang.OutOfMemoryError'; thrown from class name: 'sun.reflect.NativeMethodAccessorImpl', method name: 'invoke0', file: 'NativeMethodAccessorImpl.java', line: '-2'
The message contains that data associated with a Java exception.
No user action required.
The task was unsuccessful: The deployment was unsuccessful. Check error messages above for explanation.
Regards,
Punky |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Oct 18, 2012 8:59 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Completely undeploy the existing adapter flows.
Create the bar file from scratch.
Try again.
check for relevant APARs in the list of fixes for 7.0.0.3 and 7.0.0.4 - make sure to run mqsichangebroker -f all after you apply the next FP. |
|
| Back to top |
|
|
| punky |
| Posted: Mon Jan 14, 2013 3:01 am Post subject: |
|
|
Apprentice
Joined: 26 May 2011
Posts: 44
Location: India
|
Hi Masters,
The version of :
WMB is 7.0.0.2
And the effective level of runtime is 7.0.0.1
The issue got resolved by creating a new execution group and making the deployment, but that still is a temperory solution. 
Best Regards,
Punky |
|
| Back to top |
|
|
|
|
