One of my pals saw this exception earlier today: -
An error has occurred.
The error message returned was: "Error in method displayData_InputPage_NextAction. Error in method displayData_ShowResults. Error in method getDataViaWSDL.invoke. Error in method getDataViaWSDL.invokeInternal. java.net.ConnectException: HTTP ( 404 ) Not Found address : http://wpx7.uk.ibm.com:10039/WPF0001/servlet/AxisServlet".
Please refer to the logs folder in your deployed application for additional error information.
Click here for a detailed error message.
when attempting to execute a simple model that consumes a Web Service - in his case, this was a WSDL-based service that he had created with another model that consumed DB2 UDB using JDBC.
In addition to the above exception shown in the browser when he ran the model, we also saw: -
Caused by: com.bowstreet.util.WrappedException: The AXIS engine could not find a target service to invoke! targetService is null [Root exception is javax.xml.ws.soap.SOAPFaultException: The AXIS engine could not find a target service to invoke! targetService is null]
javax.xml.ws.soap.SOAPFaultException: The AXIS engine could not find a target service to invoke! targetService is null
in the SystemOut.log file of the underlying WebSphere Portal 7 instance.
I reproduced the same problem on my own lashup, so dug a little further.
I regenerated the models a number of times, and also published and republished my project, but to no avail.
In the end, thinking laterally, I wondered whether WPF v7 had introduced any new options when creating projects - I know that the dev. team were talking about providing more options for project creation in order to reduce the default size of a generated WAR file.
Sure enough, when I looked at the Project Properties ( select the project and click the right-hand mouse button ), under WebSphere Portlet Factory -> Feature Info, I saw that there are now new options for Axis 1 Extensions and Web Service Enablement Extensions.
From trial and error, I can tell you that you need BOTH options.
Geeking in technology since 1985, with IBM Development, focused upon Docker and Kubernetes on the IBM Z LinuxONE platform In the words of Dr Cathy Ryan, "If you don't write it down, it never happened". To paraphrase one of my clients, "Every day is a school day". I do, I learn, I share. The postings on this site are my own and don’t necessarily represent IBM’s positions, strategies or opinions. Remember, YMMV https://infosec.exchange/@davehay
Subscribe to:
Post Comments (Atom)
Note to self - use kubectl to query images in a pod or deployment
In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...
-
Why oh why do I forget this ? Running this command : - ldapsearch -h ad2012.uk.ibm.com -p 389 -D CN=bpmbind,CN=Users,DC=uk,DC=ibm,DC=com -w...
-
Error "ldap_sasl_interactive_bind_s: Unknown authentication method (-6)" on a LDAPSearch command ...Whilst building my mega Connections / Domino / Portal / Quickr / Sametime / WCM environment recently, I was using the LDAPSearch command tha...
-
Whilst building a new "vanilla" Kubernetes 1.25.4 cluster, I'd started the kubelet service via: - systemctl start kubelet.se...
6 comments:
I got the same problem and after following your tips, the problem went away... Many-many thanks to you...
@Hans - no problems, glad to be of help
thanx budy i have also same issue but i went through ur suggestion ...
that a great trick...
@SPG, no worries, glad to help
Great. It worked for me.
thanks.
@Sooraj, excellent news, thanks for letting me know.
Post a Comment