| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| XML Validator Node - Support Pac IA9A (SOLVED) |
« View previous topic :: View next topic » |
| Author |
Message
|
| javaforvivek |
 Posted: Mon Aug 22, 2005 3:58 am Post subject: XML Validator Node - Support Pac IA9A (SOLVED) |
 |
|
Master
Joined: 14 Jun 2002
Posts: 282
Location: Pune,India
|
Hi,
I am working on WBIMB v5 CSD6.
Today I downloaded supportpac IA09:
http://www-1.ibm.com/support/docview.wss?rs=849&context=SSKM8N&dc=D400&uid=swg24010092&loc=en_US&cs=UTF-8&lang=en
It all went well till the installation of this node.
But, while running the sample message flow, it gave me error of major-minor version :
BIP2628E: Exception condition detected on input node 'ValidateAccordingToMsg.XMLVALID.MSG.IN'.
The input node 'ValidateAccordingToMsg.XMLVALID.MSG.IN' detected an error whilst processing a message. The message flow has been rolled-back and, if the message was being processed in a unit of work, it will remain on the input queue to be processed again. Following messages will indicate the cause of this exception.
Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.
2005-08-22 16:09:05.392817 3536 RecoverableException BIP2230E: Error detected whilst processing a message in node 'ValidateAccordingToMsg.Validate According to Msg'.
The message broker detected an error whilst processing a message in node 'ValidateAccordingToMsg.Validate According to Msg'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error.
2005-08-22 16:09:05.392858 3536 RecoverableException BIP4367E: The method 'evaluate' in Java node 'Validate According to Msg' has thrown the following exception: java.lang.UnsupportedClassVersionError: org/xml/sax/SAXException (Unsupported major.minor version 48.0).
The method 'evaluate' of the Java plug-in node has thrown an exception. Examine previous error messages for details of the cause of the problem.
Contact the node provider for further details.
2005-08-22 16:09:05.392918 3536 RecoverableException BIP4395E: Java exception: 'java.lang.UnsupportedClassVersionError'; thrown from class name: 'java.lang.ClassLoader', method name: 'defineClass', file: 'ClassLoader.java', line: '703'
The message contains that data associated with a Java exception.
No user action required.
2005-08-22 16:09:06.415728 3536 UserTrace BIP2631I: Backed out message being propagated to failure terminal; node 'ValidateAccordingToMsg.XMLVALID.MSG.IN'.
Node 'ValidateAccordingToMsg.XMLVALID.MSG.IN' has received a message which has previously been backed out because of a processing error in the message flow. The MQMD 'backoutCount' of the message exceeds (or equals) the 'backoutThreshold' defined for the WebSphere Business Integration input queue. The message broker is propagating the message to the failure terminal of the node.
Examine the other messages and the message flow to determine why the message is being backed out. Correct this situation if possible. Perform any local error recovery processing required.
I have tried this with either of the following JREs (Toolkit - Windows- Preferences - Java - Installed JREs):
E:\WBIMB\eclipse\jre
C:\j2sdk1.4.2_02\jre
What is the problem?
_________________
Vivek
------------------------------------------------------
...when you have eliminated the impossible, whatever remains, however improbable, must be the truth.
Last edited by javaforvivek on Thu Sep 01, 2005 1:19 am; edited 2 times in total |
|
| Back to top |
|
 |
| sigormley |
| Posted: Wed Aug 31, 2005 5:57 am Post subject: |
|
|
Newbie
Joined: 24 Feb 2004
Posts: 6
|
Hi,
The SupportPac was tested on CSD4, however, the classpath for Java plug-in nodes has changed since then, and it is now necessary for the required Xerces jar files to be included in the broker classpath, e.g. for Windows, place the following in the System classpath:
c:\progra~1\ibm\websph~2\classes\xerces.jar;
c:\progra~1\ibm\websph~2\classes\xml-apis.jar
(for the default broker install location - these will be different depending on how the broker was installed)
The broker will also need a restart.
This may not resolve your problem, but will need to be done to allow the node to work on CSD6. You could also try recompiling the runtime part of node using the installed JDK. |
|
| Back to top |
|
|
| javaforvivek |
| Posted: Thu Sep 01, 2005 1:18 am Post subject: |
|
|
Master
Joined: 14 Jun 2002
Posts: 282
Location: Pune,India
|
Hi sigormley,
I got it working at last..
The problem was that, my JRE was set to "1.4.2_06", at the same time, I had also set my classpath to the xerces.jar and xml-apis.jar as you have suggested.
Now both J2SE rt.jar and xerces.jar contain org.apache.sax packages. they are not compatible with each other. whereas J2SE 1.3 and xerces.jar combination went well.
I did this:
Changed my classpath from
| Code: |
CLASSPATH = %CLASSPATH%;C:\J2SDK1.4.2\jre\lib\rt.jar
to
CLASSPATH = %CLASSPATH%;C:\J2SDK1.3.1\jre\lib\rt.jar |
and then appended the two xerces jar files.
Its working fine now. thanks for the reply.
_________________
Vivek
------------------------------------------------------
...when you have eliminated the impossible, whatever remains, however improbable, must be the truth. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
