|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Native method not found error |
« View previous topic :: View next topic » |
Author |
Message
|
mqseries123 |
Posted: Sun Jul 15, 2007 8:28 pm Post subject: Native method not found error |
|
|
Apprentice
Joined: 04 Jan 2006 Posts: 26
|
Hi,
During the deployment of the ear file in WPS (6.0.1) on Windows XP server, the following error is encountered:
WMSG0031E: Exception processing JMS Message for MDB export.SendMessageExportEIS, JMSDestination MQConn/SendMessageExport_MQ_RECEIVE_D : com.ibm.websphere.sca.ServiceRuntimeException: No native method found on export SendMessageExport
In the application, the MQ-JMS export binding is configured for getting messages from the queue.
Please do let me know is there any other configuration that needs to be taken care of.
Regards |
|
Back to top |
|
 |
mymq |
Posted: Thu Feb 04, 2010 4:50 am Post subject: |
|
|
Centurion
Joined: 01 Mar 2007 Posts: 101 Location: US-Greenwille
|
Hi,
Did u get any update on the same?
regards
Srikant _________________ --SRK-- |
|
Back to top |
|
 |
doreen |
Posted: Wed Mar 03, 2010 1:12 pm Post subject: Native method not found error |
|
|
Newbie
Joined: 05 Feb 2010 Posts: 4
|
Do you have in the Method Bindings property the Native method set? |
|
Back to top |
|
 |
wooda |
Posted: Tue Mar 09, 2010 3:00 am Post subject: |
|
|
 Master
Joined: 21 Nov 2003 Posts: 265 Location: UK
|
This error indicates a failure to find a valid operation to invoke for this message.
The Export has a configurable function selector class which gets access to the inbound message and returns a corresponding "native method" name to invoke for that message.
Now the user can choose which function selector class they wish to use, each has a different way of selecting the "native method" , also you can write and use your own function selector.
The "native method" string returned from the FS must match a "native method" found on one of the method bindings in the MQ JMS export binding.
Each method binding essentially maps each opertation in the interface to a "native method" string. The "native method" string is configurable.
So...
a.) Check which function selector you are using. Waht does it expect to find in the message to determine the "native method" ?
b.) Check the "native method" value it will return for this message matches one set on one of your method bindings in the MQ JMS export binding config.
FYI: The default function selector on a MQ JMS export will be looking for a JMS property called "TargetFunctionName" and returning the value of this as the native method value. |
|
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
|
|
|
|