| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Internal Exception Arised: FmcAssertionException |
« View previous topic :: View next topic » |
| Author |
Message
|
| Ratan |
 Posted: Fri Jan 16, 2004 11:32 am Post subject: |
 |
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
I have this problem but on WF 332. I was never been able to find a correct solution to this problem.
My work around was for whatever structure WF arises that exception, I isolate that data structure and import it. It is a time cosuming process though.
_________________
-Ratan |
|
| Back to top |
|
 |
| dsbailey |
| Posted: Fri Jan 16, 2004 12:19 pm Post subject: |
|
|
Novice
Joined: 20 May 2002
Posts: 24
|
| ....just a comment based on one of your earlier appends. You mentioned that you were using MQ 5.2 with MQWF 3.4. Please note that MQ 5.2 is no longer supported and is not supported with MQ Workflow 3.4. You will want to upgrade your MQ level. By the way, this has nothing to do with the problem you are seeing because buildtime or fmcibie do NOT use the MQ interface. |
|
| Back to top |
|
|
| smyers |
| Posted: Tue Jan 20, 2004 10:39 am Post subject: |
|
|
Novice
Joined: 18 Jul 2002
Posts: 17
|
Ok, Guys, here is the data structure that occurs BEFORE the offending line where the import usually throws the error:
STRUCTURE 'XXXX_xxXxxXxxXxxxxxxx'
DESCRIPTION "XXXX XX xxxxxxxx xxxxxx xxxxxx xxxx xx Xxxxxxxx."
'STRProcessInstanceKey': 'XXXX_strucProcessInstanceKey';
'ClassService': STRING;
'DueDate': STRING;
'ErrorCount': LONG;
'ErrorMsg': STRING;
'ManualRole': STRING;
'PriorityInd': LONG;
'ResolveTime': LONG;
'ServiceOrderNumber': STRING;
'WorkflowActivity': STRING;
END 'XXXX_xxXxxXxxXxxxxxxx'
Here is a sample of one structure that the import did not like, and which occurs AFTER the above data structure:
STRUCTURE 'XXXX_xxXxxxXxxXxxx'
DESCRIPTION "Xxxxx xx xx XXXX XX xxxxx xxxx xxx xxxx."
'STRProcessInstanceKey': 'XXXX_strucProcessInstanceKey';
'ClassService': STRING;
'DueDate': STRING;
'ErrorCount': LONG;
'ErrorMsg': STRING;
'ManualRole': STRING;
'PriorityInd': LONG;
'ResolveTime': LONG;
'ServiceOrderNumber': STRING;
'WorkflowActivity': STRING;
'CalcDueDate': LONG;
END 'XXXX_xxXxxxXxxXxxx'
No matter how many I remove (as suggested by Ratan), another error seems to occur somewhere below the first .fdl structure which I have listed above. I have tried removing them as they come, but as we have MANY data structures it would take a very long time. I have also tried placing UPDATE in front of the structure names (i.e. UPDATE STRUCTURE "x") but that didn't work either. I have tried conversions for white space and extraneous characters, and have also tried changing FM_RELEASE V3R3 0 to FM_RELEASE V3R4 0. I also just upgraded my MQ Client to v5.3. *Note that "X" denotes a capitilization, small "x" denotes a small char, all chars are equivalent to the words in behind so nothing has changed in regards to NUMBER of chars. |
|
| Back to top |
|
|
| Ratan |
| Posted: Tue Jan 20, 2004 10:42 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
Open a PMR with IBM. I cant reproduce the error, so I cant open a PMR.
_________________
-Ratan |
|
| Back to top |
|
|
| kriersd |
| Posted: Wed Jan 21, 2004 7:13 pm Post subject: |
|
|
Master
Joined: 22 Jul 2002
Posts: 209
Location: IA, USA
|
I have the EXACT same problem..
The work around is to turn on tracing. I just started a level 99 trace and limited the size of the trace file to 1 mb. IBM is still trying to find the long term solution.
dk.
_________________
Dave Krier
IBM WebSphere MQ Workflow V3.4 Solution Designer |
|
| Back to top |
|
|
| smyers |
| Posted: Thu Jan 22, 2004 12:48 pm Post subject: |
|
|
Novice
Joined: 18 Jul 2002
Posts: 17
|
Hi Guys,
Well, I broke down and stepped through my data structure .fdl (as Ratan had mentioned earlier, and which I was previously hesitant to attempt due to time issues). I just kept trying to import it, removing each data structure that it didn't like, and placing the "offending" data structures in their own separate file. I removed approximately 26 Data Structures out of a possible 309, and the import eventually worked. I then moved on to the "offending" .fdl file and proceeded to break THOSE data structures down, and tried to import them. The first import attempt did not work, but when I separated the the data structures into "groups", they would then import correctly.
Now that I had all the correct data inserted into wf3.4, I then proceeded to do an export of my entire .fdl in wf3.4 (data structures, programs, process models, etc.) to check and see if I could now import the data structures correctly. When I attempted the import, I then got the same error over again! Very strange! We then thought it may have something to do with the length of the .fdl file itself, so I exported only my data structures and tried to import them again, gradually decreasing the length of the file. Unfortunately, that did not work either.
So, we are at a point now where we do indeed have all our data structures transferred correctly into wf 3.4 from wf3.3, but if we try to do any updates or reimports we are still running into the same issue. I am going to try the tracing workaround which kriesd has mentioned and see if that helps. Hopefully IBM will post a solution soon! |
|
| Back to top |
|
|
| smyers |
| Posted: Thu Jan 22, 2004 2:24 pm Post subject: |
|
|
Novice
Joined: 18 Jul 2002
Posts: 17
|
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
