| Author |
Message
|
| bindu s |
 Posted: Mon Jul 29, 2013 8:30 am Post subject: issue with wsrr |
 |
|
Apprentice
Joined: 27 Jun 2013
Posts: 27
|
wen we r trying to retrieve service from wsrr using EndpointLookup node, it was showing error like
Text:CHARACTER:Unhandled exception in plugin method
Insert
Type:INTEGER:5
Text:CHARACTER:java.lang.NullPointerException
Insert
Type:INTEGER:5
Text:CHARACTER:com.ibm.broker.plugin.MbService
Insert
Type:INTEGER:5
Text:CHARACTER:getLogMessages
Insert
Type:INTEGER:5
Text:CHARACTER:MbService.java
Insert
Type:INTEGER:2
Text:CHARACTER:452
can anyone help me out? |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Mon Jul 29, 2013 8:53 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Jul 29, 2013 11:37 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Where I come from, the use of
| Code: |
| catch (Exception e) { ... |
is viewed with deep suspicion until the author can prove that it really is the correct solution.
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Jul 30, 2013 3:16 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| kimbert wrote: |
Where I come from, the use of
| Code: |
| catch (Exception e) { ... |
is viewed with deep suspicion until the author can prove that it really is the correct solution. |
Sarcasm and tongue-in-cheek are not readily visible with ASCII characters. Motivation to read is sometimes a far off goal.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| dogorsy |
| Posted: Tue Jul 30, 2013 3:31 am Post subject: |
|
|
Knight
Joined: 13 Mar 2013
Posts: 553
Location: Home Office
|
| lancelotlinc wrote: |
| Motivation to read is sometimes a far off goal. |
you are making a big assumption here.... |
|
| Back to top |
|
|
| akkypaul |
| Posted: Mon Oct 17, 2016 7:09 am Post subject: Any resolution to this problem? |
|
|
Apprentice
Joined: 30 Jun 2014
Posts: 44
Location: India
|
I see you guys are enjoying your wise wits but, is there any solution that you can provide?
IBM has recognized this issue and has given a solution i.e. to check whether the WSRR certificate added to TrustStore file has X 509 format and that the type of file should be .JKS though I fulfilled both the criteria and restarted my broker, I am still facing the same error:-
| Code: |
| Node throwing exception : sample.soap.flow.SampleMessageFlow.Endpoint Lookup Unhandled exception in plugin method : evaluate Endpoint Lookup <com.ibm.broker.plugin.MbRecoverableException class:EndpointLookup(SRRetrieveITServiceNode) method:evaluate source:com.ibm.ws.webservices.multiprotocol.discovery.ServiceProviderManager (initialization failure) key:com.ibm.ws.webservices.multiprotocol.discovery.ServiceProviderManager (initialization failure) message: Unable to resolve message: Source: com.ibm.ws.webservices.multiprotocol.discovery.ServiceProviderManager (initialization failure)Key: com.ibm.ws.webservices.multiprotocol.discovery.ServiceProviderManager (initialization failure) > Unhandled exception in plugin method : com.ibm.broker.plugin.MbRecoverableException EndpointLookup(SRRetrieveITServiceNode) evaluate Undefined -1 Throwable occurred when persisting entities from the query result com.ibm.ws.webservices.multiprotocol.discovery.ServiceProviderManager (initialization failure) com.ibm.ws.webservices.multiprotocol.discovery.ServiceProviderManager (initialization failure) : Flow (sample.soap.flow.SampleMessageFlow) Node (Endpoint Lookup) |
|
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Oct 17, 2016 7:15 am Post subject: Re: Any resolution to this problem? |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| akkypaul wrote: |
| I am still facing the same error |
No you're not. This thread is 3 years old and, as you say, IBM have provided some patches between now and then and obviously all the software versions are different.
I would strongly suggest that you start a new thread (referencing this one if you want) that describes your problem, the scenarios where you see it, the software levels you are using and what you've done to try and resolve this.
One of the wits on this thread (who demonstrated at least half of them on this forum) is no longer with us, so you should find a greater focus.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
