ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Mapping node code generation failure

Post new topic  Reply to topic
 Mapping node code generation failure « View previous topic :: View next topic » 
Author Message
coreybanks
PostPosted: Fri Sep 26, 2008 10:15 pm    Post subject: Mapping node code generation failure Reply with quote

Newbie

Joined: 26 Sep 2008
Posts: 2

Hi All,

Has anyone come accross an issue where the code behind a msgmap doesn't get generated in the bar file? I've got a flow that is simply doing a RCD, mapping from one MRM to another and then out the other side. No errors are reported anywhere in the toolkit, and the bar file build appears to work. When I deploy though it complains as follows:

Code:
BIP2087E: Broker V6BROKER was unable to process the internal configuration message.

The entire internal configuration message failed to be processed successfully.

The internal configuration message failed to be processed, use the messages following this message to determine the reasons for the failure.


Code:
BIP4041E: Execution group 'default' received an invalid configuration message. See the following messages for details of the error.

The message broker received an invalid configuration message and has not updated its configuration.  This can arise as a result of errors in the specification of either message flows or message sets which the configuration manager was unable to detect.  It can also result from a message flow requiring a type of node that is not supported by the broker installation, from the broker having become out of step with the configuration database or from other applications sending extraneous messages to the broker's configuration queues (SYSTEM.BROKER.ADMIN.QUEUE & SYSTEM.BROKER.EXECUTIONGROUP.QUEUE).

Check the relevant message flow and message set definitions, check that all necessary user-defined extensions are installed, perform a complete redeploy of the broker's configuration and ensure that no applications are writing to the broker's configuration queues.


Code:
BIP4001E: Syntax error in SQL statements in node 'NBI_PAS.NBI_FLE.Mapping.ComIbmCompute'.

The configuration failed due to errors in the SQL statement text. See the following messages for details of the error

The following error messages will give specific details of the location and nature of the error. Check and correct the syntax of the SQL statements and redeploy.


Code:
BIP2558E: (NBI_PAS.IBM_WBIMB_NBI_FLE_Mapping.MAIN, 3.6) : Undefined function 'NBI_PAS.NBI_PAS_Transform_FLEToU2'.

The program is attempting to call a function which is not defined or is not in the schema path.

Correct the syntax of your ESQL expression in node 'NBI_PAS.IBM_WBIMB_NBI_FLE_Mapping.MAIN', around line and column '3.6', then redeploy the message flow.



I'm on toolkit 6.0.2 iFix 015, and when I look inside the bar file the code is indeed not there. I don't see any errors in any log that I can think of (user log and service log in the bar, metadata .log in the workspace, windows event log) so what is stopping the code generation? Is there any other log somewhere, or a way of getting a build trace to see why the code isn't being generated. Other mapping nodes (similar but with a different outpput message format) work, and this used to work but has now stopped. It was working previously, so I guess I can roll back all my changes in CVS and re-do them but I'd rather know why it's actually failing if I can. The xml schema I'm mapping too has changed a little so I guess that might be my first step, but I don't really want to redo everything!

Any help or pointers would be greatly appreciated!

Regards,
Corey
Back to top
View user's profile Send private message
satya2481
PostPosted: Mon Nov 10, 2008 6:21 am    Post subject: Reply with quote

Disciple

Joined: 26 Apr 2007
Posts: 170
Location: Bengaluru

Hi,

Have a look at the below Link

http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg24020217

Hope this will help you to solve your problem, I am also facing similar kind of error and I am not sure whether by applying this fix pack my problem resolves or not.

Regards
S
_________________
IBM Certified Solution Developer WebSphere Message Broker V6.0
IBM Certified System Administrator WebSphere MQ V6.0
Back to top
View user's profile Send private message Send e-mail
coreybanks
PostPosted: Mon Nov 10, 2008 7:42 pm    Post subject: Reply with quote

Newbie

Joined: 26 Sep 2008
Posts: 2

Thanks Satya,

We will indeed be upgrading to broker 6.1 so hopefully this will be fixed as part of that upgrade. I've found that if I start a new workspace and re-get my project out of our CVS then it all works fine. Seems to be an eclipse/toolkit issue of some kind.

This might help you with your problem, but worth a shot to see if it's the same problem.

Regards,
Corey
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Mapping node code generation failure
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.