| Author |
Message
|
| indra |
 Posted: Sun Jun 19, 2011 6:05 am Post subject: DatabaseInput Node Message Flow Deployment Issue |
 |
|
Newbie
Joined: 23 Apr 2009
Posts: 4
|
I created a message flow that react quickly to changes to application data held in database.and retrieves updated data directly from the database.
and generates the xml and puts into the MQ Queue.
DatabaseInputNode--->Mapping NOde-->MQOutputNode
Version: 7002
But When I deploy the message flow with xsdzip files I am getting the following Error.
DatabaseInput Node Message Flow Deployment Issue
Begin running task [Deploying [DatabaseInputSample.bar] to execution group [test]]
BIP2087E: Broker MB7BROKER 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 'test' 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.
BIP3430E: The creation of a resource based on message set 'DatabaseInput Database Message.xsdzip' failed.
Review the following exception messages to find out the cause.
None
BIP3450E: An adapter error occurred during the processing of a message. The adapter error message is 'java.lang.IllegalArgumentException
at org.apache.tuscany.sdo.helper.XSDHelperImpl.define(XSDHelper... (data of len 813 truncated)'.
This error was detected by the adapter. The following message describes the diagnostic information that is provided by the adapter 'java.lang.IllegalArgumentException
at org.apache.tuscany.sdo.helper.XSDHelperImpl.define(XSDHelper... (data of len 813 truncated)'.
Inspect the diagnostic information that is provided by the adapter. Further diagnostic information might be written to user trace. Inspect user trace for further information.
The task was unsuccessful: The deployment was unsuccessful. Check error messages above for explanation. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Sun Jun 19, 2011 2:08 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| it sounds like you upgraded your Toolkit to 7.0.0.2 but not your runtime? |
|
| Back to top |
|
|
| indra |
| Posted: Mon Jun 20, 2011 12:37 am Post subject: |
|
|
Newbie
Joined: 23 Apr 2009
Posts: 4
|
| I already upgraded Toolkit and Runtime also but still the error continues. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Jun 20, 2011 1:52 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
I don't mean to sound disagreeable here, but the error message strongly suggests that the Runtime is *not* at 7.0.0.2.
There's also other information there that suggests that the runtime is upgraded, and the adapter is trying to start but it is having problems because of something.
Can you stop and start the broker, and then review all of the errors that mention the databaseinput node? There maybe data that is missing from what you've shown already. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Jun 20, 2011 4:22 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
Did you upgrade the runtime functionality to 7.0.0.2?
Do a 'mqsireportproperties' on the broker to find out.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jun 20, 2011 12:20 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| indra wrote: |
| I already upgraded Toolkit and Runtime also but still the error continues. |
You say you upgraded ... but did you make the level effective @7.0.0.2 or is it still running at a prior level of functionality...?? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Jun 20, 2011 1:09 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| fjb_saper wrote: |
| indra wrote: |
| I already upgraded Toolkit and Runtime also but still the error continues. |
You say you upgraded ... but did you make the level effective @7.0.0.2 or is it still running at a prior level of functionality...?? |
Hmmm. Isn't that what I said in the previous post? 
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jun 20, 2011 8:15 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| smdavies99 wrote: |
| Hmmm. Isn't that what I said in the previous post? |
I gotta stop posting 2 mins before the next emergency and read ALL the answers... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
