we have recently experienced a strange behavior when trying to use web service with MTOM. When Webservice method is annotated #MTOM, application fails to deploy with strange message:
Certificate Alias not supplied
This happens only on Weblogic that has no access to internet, when we deploy the same application to Weblogic that has internet connection, everything is OK.
We managed to find a note in a forum, saying that this error happens when Weblogic is trying to unsuccessfully access remote resource (like xsd). This might be true because mtom.xml file (policy in weblogic) references remote xsd: http://schemas.xmlsoap.org/ws/2004/09/policy/optimizedmimeserialization/optimizedmimeserialization-policy.xsd
The webservices are created using standard J2EE 6 annotations (#WebService).
Has anyone experience similiar problem? We would appreciate any help.
MF & VH
Related
I have a web service, where I am required to make a contract change. The contract change is the easier part, and I was able to make the changes to service and deploy it on the WAS 8.5 application server.
When I triggered a sample request from SOAPUI to validate my changes, I saw that my request from SOAPUI could not be successfully parsed and that is when I noticed that *_Deser.class, *_ser.class and *_helper.class for my services objects are not created after the change. Due to this, the SOAPUI request could not be processed by the SAXParser.
Here is the technology stack that I am using:
Rational Application Developer : 8.5.5
Websphere Application Server: 8.5
Java: 1.6
Webservice Runtime: IBM Websphere JAX-RPC
Note: I have to stick to this runtime :(
Any idea, why these classes/java files to not be generated?
Thanks,
RS
Found the reason behind the issue after lot of research on internet :) . https://www.ibm.com/support/knowledgecenter/en/SS8PJ7_9.1.1/com.ibm.webservice.doc/topics/core/cruntimes.html
I'm trying to upgrade a legacy webservice from Axis1 to JaxWS. I've been trying out various tutorials to see if I can add a JaxWS Webservice to the existing WebSphere server we use. I'd like to use the WebService Wizard since that seems like the most likely way to get everything running smoothly, however I've encountered the following problem. When I change the Web Service Runtime from AXIS to WebSphere JAX-WS I get the message
The IBM WebSphere JAX-WS Web service runtime in WebSphere Application
Server V8.5 Liberty Profile does not support the service project <
jax-ws project name >
So far google has failed to find a solution or even an explanation of this error for me. Does anyone here understand what my error is?
Thanks,
I receive this error in running a Java program within JDeveloper and I have no idea what to do to fix the error:
javax.naming.CommunicationException: Could not obtain connection to any of these urls: 160.151.120.33:999
I know I can change the URL and port by changing the values in a jndi.properties file. I am quite new to Java, JDeveloper, EJB, and JBoss.
This is a desktop app that is failing to connect. Am I supposed to deploy the EJB to a JBoss server first? How does the EJB, JBoss and a desktop Java app work and communicate with each other?
If your application is trying to access an EJB then yes you first need to run/deploy the EJB and only then run the client.
I have several existing web-apps deployed as standalone war files in the app container (resin). Some use axis2 jar files and axis2-generated Stub files to make calls to external SOAP based web services. They were all working fine prior to this.
I recently deployed axis2.war to the same container in order to create web services (unrelated to the client code mentioned above).
As soon as I restart the app container, client calls to the external webservices seem to be "intercepted" by my newly deployed axis2.war.
Services appear temporarily in the "Available Services" page of the axis2 web-app, with what appears to be randomly generated name based on the original external webservice name.
These services disappear shortly after, but the result is that my client code fails with a 500 error, as the local Axis2.war doesnt know how to handle those requests.
I have been searching for 2 days and haven't found mention of anyone experiencing anything similar. I am not even sure how to explain what is going on, as my client code never references localhost to make those web service calls. I am assuming this has to do with some configuration in axis2.war?
If anyone has any idea or insight into what might be happening, I would really appreciate any information.
Thanks for your help
I have a java web application using axis2 stub to call a .net webservice that receieves a string parameter. When I run the web application using tomcat server, it works fine.
But when I use Oracle weblogic server I get the following error :
org.apache.axis2.AxisFault:
First Element must contain the local name, Envelope , but found html
What could be the cause to get this error? Please help me. I really need to fix this but I can't.
Follow the steps # http://axis.apache.org/axis2/java/core/docs/app_server.html for deploying axis2 onto weblogic