| Author |
Message
|
| svemula1 |
 Posted: Thu Mar 08, 2012 6:24 pm Post subject: unknown receiving type evaluate(MbMessageAssembly) |
 |
|
Newbie
Joined: 14 Feb 2012
Posts: 7
|
Hi,
I am reading the messages from JMS Queue with Java compute node.
I am able to read the messages and my JCP has two output nodes(out,alternate).out node is connected to compute node and alternate is also connected to compute nodte.While propagating to out terminal I am getting some esceptions.
out.propagate(outAssembly);
Exceptions :
<unknown receiving type>(CommonComponents_ReadQ_WriteQ).evaluate(MbMessageAssembly) line: 134
<unknown receiving type>(CommonComponents_ReadQ_WriteQ).evaluate(MbMessageAssembly) line: 134
<unknown receiving type>(MbRuntimeJavaComputeNode).evaluate(MbMessageAssembly, MbInputTerminal) line: 180
<unknown receiving type>(MbNode).evaluate(long, String, long) line: 1476
Please help me in this regard.
I really appreciate your quick response. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Fri Mar 09, 2012 2:31 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Those exceptions point to lines of your own code, which you have not posted. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Mar 09, 2012 5:53 am Post subject: Re: unknown receiving type evaluate(MbMessageAssembly) |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| svemula1 wrote: |
| I am reading the messages from JMS Queue with Java compute node. |
Why are you reading a queue with custom code rather than with the WMB node provided for this purpose? It's a very bad idea and can lead to all sorts of problems.
Not least it sounds like you're using WMB like it's WAS which can only end in trouble.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Mar 09, 2012 5:54 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Moved to WMB section
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| svemula1 |
| Posted: Fri Mar 09, 2012 12:04 pm Post subject: Re: unknown receiving type evaluate(MbMessageAssembly) |
|
|
Newbie
Joined: 14 Feb 2012
Posts: 7
|
| Vitor wrote: |
| svemula1 wrote: |
| I am reading the messages from JMS Queue with Java compute node. |
Why are you reading a queue with custom code rather than with the WMB node provided for this purpose? It's a very bad idea and can lead to all sorts of problems.
Not least it sounds like you're using WMB like it's WAS which can only end in trouble. |
My Requirement is something like this.
WMB receives a soap request.i need to capture some info from request and need to construct sendq and destination queue.These queue name will be present in property file(In future they might add few more queues).
The whole part is done.I am able to connect to Queue and and able to read the message and when i propagate to out terminal am getting the exception.
Do we have to set any compute node properties to resolve this issue.
Setting are
Transaction : Automatic
COmpuet Node : LocalENvironment and Message
Exception details :
Error detected whilst processing a message in node 'Caught exception and rethrowing'.
The message broker detected an error whilst processing a message in node 'Caught exception and rethrowing'. An exception has been thrown to cut short the processing of the message.
See the following messages for details of the error. : Caught exception and rethrowing
Exception message: Unable to resolve message: Source: Java
Please advise the right aproach if its not. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Mar 09, 2012 12:07 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
It is the wrong approach.
You should not use Properties files.
You should not use JMS directly from a JCN, when you can instead use JMSOutput nodes and JMSRequest nodes.
You still have not posted information about your actual code. It is your actual code that is throwing the exceptions you are seeing. It is not anything in the flow you have configured. It is not anything in the properties of any of your nodes.
IT IS YOUR CODE THAT IS BROKEN. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Mar 09, 2012 12:47 pm Post subject: Re: unknown receiving type evaluate(MbMessageAssembly) |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| svemula1 wrote: |
| Please advise the right aproach if its not. |
It's not.
There is no requirement to use custom Java to capture information from a SOAP node. There is no requirement (and no excuse) to access queues from inside Java, especially if it's an output queue name you're building. There is no requirement to read anything from a property file.
Your aproach (sic) is wrong, your design is flawed and your code is broken. At best this is wasting the license fee you're paying for WMB, at worst this is going to tie you in knots and create a maintenance nightmare. This was all covered in your earlier thread.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| svemula1 |
| Posted: Fri Mar 09, 2012 1:48 pm Post subject: Re: unknown receiving type evaluate(MbMessageAssembly) |
|
|
Newbie
Joined: 14 Feb 2012
Posts: 7
|
| Vitor wrote: |
| svemula1 wrote: |
| Please advise the right aproach if its not. |
It's not.
There is no requirement to use custom Java to capture information from a SOAP node. There is no requirement (and no excuse) to access queues from inside Java, especially if it's an output queue name you're building. There is no requirement to read anything from a property file.
Your aproach (sic) is wrong, your design is flawed and your code is broken. At best this is wasting the license fee you're paying for WMB, at worst this is going to tie you in knots and create a maintenance nightmare. This was all covered in your earlier thread. |
If i dont use property file where do i put my destination queues.
Here is my code.
Message message = null;
while ( (message = queueReceiver.receive(5000)) != null ){
textMessage = (TextMessage)message;
if(textMessage != null){
MbElement outRoot = outMessage.getRootElement();
MbElement mqrfh2 = outRoot.createElementAsLastChild("MQRFH2");
MbElement outrfh2 = mqrfh2.createElementAsLastChild(MbElement.TYPE_NAME_VALUE, "usr", null);
for (Enumeration e = textMessage.getPropertyNames(); e.hasMoreElements()  {
propertyName = new String((String) e.nextElement());
MbElement outrfh1 = outrfh2.createElementAsLastChild(MbElement.TYPE_NAME_VALUE, propertyName, textMessage.getObjectProperty(propertyName));
}
MbElement outParser = outRoot.createElementAsLastChild(MbBLOB.PARSER_NAME);
MbElement outBodyEl2 = outParser.createElementAsLastChild(MbElement.TYPE_NAME_VALUE, "BLOB", textMessage.getText().getBytes());
out.propagate(outAssembly);
outMessage = new MbMessage();
outAssembly = new MbMessageAssembly(contact admin,outMessage);
}
} |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Fri Mar 09, 2012 1:55 pm Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Mar 09, 2012 1:57 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The exception you posted originally had line numbers. The code you have posted does not have line numbers. You should read the line numbers in the original exception you posted, and match this to the relevant lines of code.
I can almost see through your design to what you are trying to do, and I can almost see that it's not the worst idea.
You seem, maybe, to be using a SOAP Service to cause a set of messages on a remote queue manager to move into a local queue manager, as part of a security or scheduling type of task.
There does not exist a JMSRead node or JMSGet node so you can't fetch JMS messages in the middle of a flow. You are talking to a remote queue manager, so you can't use an MQGet node.
You still SHOULD NOT use a properties file, you should use User Defined Properties on your Message Flow. You then access those from your JCN and populate the right things. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Mar 09, 2012 3:32 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
I can almost see through your design to what you are trying to do, and I can almost see that it's not the worst idea.
You seem, maybe, to be using a SOAP Service to cause a set of messages on a remote queue manager to move into a local queue manager, as part of a security or scheduling type of task. |
Given that it's reasonable to do this, I stand by my assertion that it's at best a waste to use WMB for this and at worst a disaster waiting to happen. If you've decided to write custom Java that reads an XML property file and is exposed as a web service, there are better containers for such things.
This was discussed on the OP's first attempt at this question here.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
