Weblogi webservice exception

Hi,
What the reason for exception during webserice connection on client site?
I got exception during get connection:
FileExchangeServiceImplService service = new FileExchangeServiceImplService_Impl(Configuration.getUrl());
Dec 10, 2008 12:42:14 PM com.oracle.disconnected.syncmngr.syncclient.SyncManagerMain testMain
SEVERE: Failed to load weblogic client internal deployment descriptor. weblogic.descriptor.DescriptorException: Unmarshaller failed
Dec 10, 2008 12:42:14 PM com.oracle.disconnected.syncmngr.syncclient.SyncManagerMain testMain
SEVERE: weblogic.wsee.jaxrpc.ServiceImpl.throwServiceException(ServiceImpl.java:180)
Dec 10, 2008 12:42:14 PM com.oracle.disconnected.syncmngr.syncclient.SyncManagerMain testMain
SEVERE: weblogic.wsee.jaxrpc.ServiceImpl.loadWeblogicDD(ServiceImpl.java:455)
Dec 10, 2008 12:42:14 PM com.oracle.disconnected.syncmngr.syncclient.SyncManagerMain testMain
SEVERE: weblogic.wsee.jaxrpc.ServiceImpl.loadInternalDD(ServiceImpl.java:388)
Dec 10, 2008 12:42:14 PM com.oracle.disconnected.syncmngr.syncclient.SyncManagerMain testMain
SEVERE: weblogic.wsee.jaxrpc.ServiceImpl.<init>(ServiceImpl.java:123)
Thanks,
Dmitriy

From the error message, it looks like your client deployment is missing a Deployment Descriptor. I think it should have a name like 'SERVICE-NAME_internaldd.xml'. Where SERVICE-NAME is the name of your service. This should have been generated by the WebLogic 'clientgen' ant task. Can you re-run 'clientgen' and see if an XML file with a name like that gets generated in the output directory ?

Similar Messages

Where is the exception stacktrace - weblogic.webservice.core.handler.Invoke

Hi, I am debugging a Web Service. It sometimes throws an exception while deserializing the input. But when I look through the log all I see is:
####<Jul 27, 2010 9:20:43 AM EDT> <Info> <WebService> <myhost.net> <prodServer114> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1280236843573> <BEA-220024> <Handler weblogic.webservice.core.handler.InvokeHandler threw an exception from its handleRequest method. The exception was:
java.lang.NumberFormatException: For input string: "".>
How do I make weblogic spit out the exception stacktrace?
I am using Weblogic 9.2.
Thanks in advance!

Hi, I am debugging a Web Service. It sometimes throws an exception while deserializing the input. But when I look through the log all I see is:
####<Jul 27, 2010 9:20:43 AM EDT> <Info> <WebService> <myhost.net> <prodServer114> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1280236843573> <BEA-220024> <Handler weblogic.webservice.core.handler.InvokeHandler threw an exception from its handleRequest method. The exception was:
java.lang.NumberFormatException: For input string: "".>
How do I make weblogic spit out the exception stacktrace?
I am using Weblogic 9.2.
Thanks in advance!

How to resolve setPrefix() in SOAP(saaj API) with weblogic/webservices jar?

Hi,
I am facing a problem deploying a Web-Application in Weblogic containing SOAP related code.
My environment is as below:
1) Weblogic 8.1 SP2 server
2) Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
3) A method is exposed as web-service
4) A client program(which is a part of Action class of Webb-app) written with SOAP APIs containing the following section:
     MessageFactory mf = MessageFactory.newInstance();
     SOAPMessage sm = mf.createMessage();
     SOAPPart sp = sm.getSOAPPart();
     sp.setPrefix("soapenv");
     SOAPEnvelope se = sp.getEnvelope();
     se.addNamespaceDeclaration("soapenv","http://orion:7001");
giving the following error at runtime:
Exception in thread "main" java.lang.AbstractMethodError:
weblogic.were.soap.SOAPEnvelopeImpl.setPrefix(Ljava/lang/String;)V
at Client.main(Client.java:39)
I am able to compile without any error/warning all the time.
This is giving only when putting the saaj(jwsdp-1.4) jars along with weblogic/webservices jars in classpath.
I am able to run the same application(outside Web-application as a stand-alone java program) without
any error while not using weblogic/webservices jar in the classpath.
The saaj jars needed to run without any error are:
saaj-api.jar
saaj-impl.jar
mailapi.jar
activation.jar
xercesImpl.jar
xalan.jar
dom.jar
jdom.jar
I thinks this is a compatibility issue. Please suggest to resolve it.
Thanks in advance,
pal_sk

Hi,
I am facing a problem deploying a Web-Application in Weblogic containing SOAP related code.
My environment is as below:
1) Weblogic 8.1 SP2 server
2) Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_04-b05)
3) A method is exposed as web-service
4) A client program(which is a part of Action class of Webb-app) written with SOAP APIs containing the following section:
     MessageFactory mf = MessageFactory.newInstance();
     SOAPMessage sm = mf.createMessage();
     SOAPPart sp = sm.getSOAPPart();
     sp.setPrefix("soapenv");
     SOAPEnvelope se = sp.getEnvelope();
     se.addNamespaceDeclaration("soapenv","http://orion:7001");
giving the following error at runtime:
Exception in thread "main" java.lang.AbstractMethodError:
weblogic.were.soap.SOAPEnvelopeImpl.setPrefix(Ljava/lang/String;)V
at Client.main(Client.java:39)
I am able to compile without any error/warning all the time.
This is giving only when putting the saaj(jwsdp-1.4) jars along with weblogic/webservices jars in classpath.
I am able to run the same application(outside Web-application as a stand-alone java program) without
any error while not using weblogic/webservices jar in the classpath.
The saaj jars needed to run without any error are:
saaj-api.jar
saaj-impl.jar
mailapi.jar
activation.jar
xercesImpl.jar
xalan.jar
dom.jar
jdom.jar
I thinks this is a compatibility issue. Please suggest to resolve it.
Thanks in advance,
pal_sk

Call Weblogic WebService in Delphi

Hi, I'm a newbie in WebService. I use Weblogic servicegen ant task wrap a stateless
EJB to webservice. The bean has a method with a string input parameter as follow:
String Test(String inputParam);
The WSDL generated by Weblogic WebService is like follow:
- <message name="Test">
<part name="string" xmlns:partns="http://www.w3.org/2001/XMLSchema" type="partns:string"
/>
I use Delphi as Webservice client. When I use Delphi's WSDL Import Wizard, it
renamed parameter "string" to "string_" because of "string" is a reserved word
in Delphi. So when I invoked the Webservice, an exception was thrown:
Found SOAPElement [<string_ xsi:type="xsd:string>test</string_>]. But was not
able to find Part that is registered with this Message which corresponds to this
SOAPElement
How can I solve this problem? On the another word, Can I control the parmater
name generate by Weblogic Webservice ant task?
thanks very much!

Please post web services issues in the webservices newsgroup.
Vimala wrote:
You can define the parameter name to the method and return parameter name with
a web-services.xml.
The link below should give a good start:
http://e-docs.bea.com/wls/docs70/webserv/dd.html#1057960
Vimala
"Dumack Wu" <[email protected]> wrote:
Hi, I'm a newbie in WebService. I use Weblogic servicegen ant task wrap
a stateless
EJB to webservice. The bean has a method with a string input parameter
as follow:
String Test(String inputParam);
The WSDL generated by Weblogic WebService is like follow:
- <message name="Test">
<part name="string" xmlns:partns="http://www.w3.org/2001/XMLSchema"
type="partns:string"
/>
I use Delphi as Webservice client. When I use Delphi's WSDL Import Wizard,
it
renamed parameter "string" to "string_" because of "string" is a reserved
word
in Delphi. So when I invoked the Webservice, an exception was thrown:
Found SOAPElement [<string_ xsi:type="xsd:string>test</string_>]. But
was not
able to find Part that is registered with this Message which corresponds
to this
SOAPElement
How can I solve this problem? On the another word, Can I control the
parmater
name generate by Weblogic Webservice ant task?
thanks very much!
Rajesh Mirchandani
Developer Relations Engineer
BEA Support

Wls 10.3 weblogic-webservices.xml transaction-timeout attribute not working

Hi, need some urgent need.
I have a stateless ejb webservice and I'm trying to set the transaction timeout for some of the methods. Right now my webservice transaction is timing out to the default of 30 secs. I've tried setting in the admin console the JTA transaction timeout option, didn't work (file a case with bea support #81233). And after days of researching and searching I came across that you can setup the weblogic webservice transaction-timeout thru the weblogic-webservices.xml deployment descriptor. Tried setting the transaction-timeout attribute to 120 secs. and that didn't work. Here is the snippet of the xml file.
<?xml version='1.0' encoding='UTF-8'?>
<weblogic-webservices xmlns="http://www.bea.com/ns/weblogic/weblogic-webservices" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/weblogic-webservices http://www.bea.com/ns/weblogic/weblogic-webservices/1.0/weblogic-webservices.xsd">
<webservice-description>
<webservice-description-name>com.starcomsoft.pp.system.jws.SystemWSImpl</webservice-description-name>
<webservice-type>JAXRPC</webservice-type>
<port-component>
<port-component-name>SystemWSSoapPort</port-component-name>
<service-endpoint-address>
<webservice-contextpath>starcomsoft_ws</webservice-contextpath>
<webservice-serviceuri>/SystemWSImpl</webservice-serviceuri>
</service-endpoint-address>
     <transaction-timeout>120</transaction-timeout>
     <reliability-config>
          <inactivity-timeout>P0DT600S</inactivity-timeout>
     </reliability-config>
</port-component>
</webservice-description>
</weblogic-webservice>
Does anybody have any clue to solve my urgent need.
Thanks in advance for your help or suggestion.

Unhandled exception
Type=Segmentation error vmState=0x00040000
J9Generic_Signal_Number=00000004 Signal_Number=0000000b Error_Value=00000000 Signal_Code=00000033
Handler1=F144C588 Handler2=F1446A9C
Module=/app/oracle/product/Middleware/wlserver_10.3/server/native/aix/ppc/libmuxer.so
Module_base_address=D8457000
Target=2_40_20091214_049398 (AIX 5.3)
CPU=ppc (4 logical CPUs) (0x600000000 RAM)
----------- Stack Backtrace -----------
(0xD696E748 [libj9vm24.so+0x48748])
(0xD8383EDC [libjclscar_24.so+0x10edc])
(0xD8384514 [libjclscar_24.so+0x11514])
(0xD6967718 [libj9vm24.so+0x41718])
(0xD6967158 [libj9vm24.so+0x41158])
(0xD69640D0 [libj9vm24.so+0x3e0d0])
(0xD6932C9C [libj9vm24.so+0xcc9c])
(0xD69BBA18 [libj9prt24.so+0x3a18])
(0xD6932BB8 [libj9vm24.so+0xcbb8])
(0xD69A77CC [libj9thr24.so+0x27cc])
pthreadbody+0x118 (0xD010D784 [libpthreads.a+0x3784])

Eclipse:package weblogic.webservice.tools.wsdlp does not exist

Hi, everyone! I got an error While I was Compiling the Entire MedRec Project application on Eclipse3.1 with ant. However, when I used setEnv.cmd and ant command(), it's all Ok! The error message shows as below:
banner:
[echo] #### S T A R T C O M M O N W E B A P P ####
[mkdir] Created dir: C:\medrec_tutorial\build\tmp
build:
[javac] Compiling 23 source files to C:\medrec_tutorial\build\tmp
[javac] C:\medrec_tutorial\src\common\web\com\bea\medrec\utils\MedRecWebAppUtils.java:319: package weblogic.webservice.tools.wsdlp does not exist
[javac] if (th instanceof weblogic.webservice.tools.wsdlp.WSDLParseException) {
[javac] ^
[javac] 1 error
BUILD FAILED
file:C:/medrec_tutorial/src/common/web/build.xml:29: Compile failed; see the compiler error output for details.

Bruce Stephens <[email protected]> wrote:
Hello,
This looks like a bug that has already been reported and resolved. If
you could provide your test case to our super support group [1], and
reference CR127344, they should be able to sort out this issue.
Thanks,Hi ,
I also got the same error.If u find the solution please email me
isuru [email protected]
Thanx
Bruce
[1]
http://support.bea.com
[email protected]
Franck wrote:
Hello,
when I try to build my webservice with a stateless bean and a complexdata type (byte[]), by using ANT and SERVICEGEN.
I have the following exception (with WL 8.1, but it works witout problemwith WL 7.0.4).
*** ERROR:
-package weblogic.xml.schema.binding does not exist
[servicegen] extends weblogic.xml.schema.binding.BeanCodecBase
What has changed between the both version.
can somebody help me
Tank you
Regards

Java.lang.ClassCastException: weblogic.webservice.core.soap.SOAPMessageImpl

Hello Gurus,
Can you please help me with following issue--
I have created a secured web service's client from netbeans 6.8.Then I made a jar file of it.Then I have integrated that jar in my ADF application's viewcontroller project .I have used the jar from backing bean of a jspx page.
If I create a main method in the bean and call the service from inside main method then everything works fine but if i remove the main method and call the service from a button click of the jspx page then i get the following error.
<Jan 7, 2012 11:01:34 AM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<ActionListenerImpl><processAction> java.lang.ClassCastException: weblogic.webservice.core.soap.SOAPMessageImpl cannot be cast to com.sun.xml.messaging.saaj.soap.MessageImpl
javax.faces.el.EvaluationException: java.lang.ClassCastException: weblogic.webservice.core.soap.SOAPMessageImpl cannot be cast to com.sun.xml.messaging.saaj.soap.MessageImpl
     at org.apache.myfaces.trinidad.component.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:51)
     at com.sun.faces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:102)
     at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:190)
     at javax.faces.component.UIViewRoot.broadcastEvents(UIViewRoot.java:475)
     at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:756)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._invokeApplication(LifecycleImpl.java:698)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:285)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:177)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.adf.share.http.ServletADFFilter.doFilter(ServletADFFilter.java:62)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:97)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
     at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:247)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:157)
     at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.ClassCastException: weblogic.webservice.core.soap.SOAPMessageImpl cannot be cast to com.sun.xml.messaging.saaj.soap.MessageImpl
     at com.sun.xml.rpc.client.StubBase._postSendingHook(StubBase.java:231)
     at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:324)
     at com.sahaj.billDetails.NotifySREIBilling_OB_Stub.notifySREIBilling_OB(NotifySREIBilling_OB_Stub.java:67)
     at com.sahaj.tester.Tester.getBillDetails(Tester.java:94)
     at Test.cb1_action(Test.java:19)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at com.sun.el.parser.AstValue.invoke(AstValue.java:157)
     at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:283)
     at org.apache.myfaces.trinidad.component.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:46)
     ... 36 more
My bean class looks as follows--
public class Test {
public Test() {
*public String cb1_action() {//does not work*
HashMap billDetails = new Tester().getBillDetails("212078438");
System.out.println(billDetails.size());
return null;
*public static void main(String[] args) {//works*
HashMap billDetails = new Tester().getBillDetails("212078438");
System.out.println(billDetails.size());
}

Hi Mike,
Support for SAAJ was added in WLS 8.1, see:
http://edocs.bea.com/wls/docs81/webserv/interceptors.html#1058444
Can you try your code on the latest release?
Thanks,
Bruce
Mike Reiche wrote:
>
What do I need to fix this?
WLS 7.0 sp2
- Mike
java.lang.Error: NYI
at
weblogic.webservice.core.soap.SOAPMessageImpl.saveRequired(SOAPMessageImpl.j
ava:360)
at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOAPConnec
tion.java:228)
at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedPost.run
(HttpSOAPConnection.java:156)
at java.security.AccessController.doPrivileged(Native Method)
at
com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOAPConnec
tion.java:126)

Where is the stack trace weblogic.webservice.core.handler.InvokeHandler

Hi, I am debugging a Web Service. It sometimes throws an exception while deserializing the input. But when I look through the log all I see is:
####<Jul 27, 2010 9:20:43 AM EDT> <Info> <WebService> <myhost.net> <prodServer114> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <1280236843573> <BEA-220024> <Handler weblogic.webservice.core.handler.InvokeHandler threw an exception from its handleRequest method. The exception was:
java.lang.NumberFormatException: For input string: "".>
How do I make weblogic spit out the exception stacktrace?
I am using Weblogic 9.2.
Thanks in advance!

Hi, I am debugging a Web Service. It sometimes throws an exception while deserializing the input. But when I look through the log all I see is:
####<Jul 27, 2010 9:20:43 AM EDT> <Info> <WebService> <myhost.net> <prodServer114> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <1280236843573> <BEA-220024> <Handler weblogic.webservice.core.handler.InvokeHandler threw an exception from its handleRequest method. The exception was:
java.lang.NumberFormatException: For input string: "".>
How do I make weblogic spit out the exception stacktrace?
I am using Weblogic 9.2.
Thanks in advance!

NoSuchMethodError: weblogic.webservice.core.rpc.ServiceImpl

I developed webservices and jsp client on my local copy of weblogic - everything works perfectly fine.. I moved the webservices and jspclient to work's developement weblogic server.. Webservices works fine but the jspclient is throwing an exception as sooon as i try to get the service.
Webservices Local Machine & Client Local -> Works.
Webservices DevServer & Client Local --> Works
Webservices DevServer & Client DevServer --> Client throws exception!!
Throwing following exception on this line: MyWebServices service = new MyWebServices_Impl();
Error 500--Internal Server Error
java.lang.NoSuchMethodError: weblogic.webservice.core.rpc.ServiceImpl.(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)V
     at jspclient.MyWebServices_Impl.(MyWebServices_Impl.java:22)
     at jspclient.MyWebServices_Impl.(MyWebServices_Impl.java:16)
     at jsp_servlet.__Mydb._jspService(__Mydb.java:128)
     at weblogic.servlet.jsp.JspBase.service(JspBase.java:33)
     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:971)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:402)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:305)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:6350)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3635)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2585)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

This problem was due to the fact that my local machine had weblogic 8.1SP3 installed and dev server had SP2 installed.
I moved to a server with SP3 and everything worked smoothly.
Thanks.

Reliable SOAP messaging problems - weblogic.webservice.saf.StoreForwardException

Hi Guys,
I'm playing with the new SOAP reliable message transport in WL 8.1 SP 1.
I have configured a simple web service, with void return, configured for
reliable messaging. I deploy the client to the same server as the server
hosting the webservice, and it uses the async invocation etc.
It wasn't obvious how to throw the exception in the backend implementation.
I simply grab the usertransaction
and call ut.setRollbackOnly(). Hope that's correct..
Whenever I invoke the operation, I get this:
weblogic.webservice.saf.StoreForwardException: Could not find MessageData
header in aknowledgement
I have a JMS file store setup, and I have it assigned to the server via the
services/webservice tab, and I do see some activity in the file store.
My client looks like this:
AsyncInfo asyncInfo = new AsyncInfo();
asyncInfo.setReliableDelivery(true);
FutureResult fr = port.startReliableOperation("hello World", asyncInfo);
System.err.println("Client: Made invocation, invoking async end now");
port.endReliableOperation(fr);
Any ideas?
Regards,
Jon
PS. [As an aside, aknowledgement needs a 'c']
Client: port.StartReliableOperation()
--S:In reliable TX operation
--S:Going to roll back
--S: Set setRolbackOnly()
--S: Finished Reliable operation
Client: Made invocation, invoking async end now
<26-Aug-2003 18:39:31 o'clock BST> <Info> <WebService> <BEA-220025> <Handler
web
logic.webservice.saf.SAFHandler threw an exception from its handleResponse
metho
d. The exception was:
javax.xml.rpc.JAXRPCException: Failed to handle the response.>
myserver:Info:Handler weblogic.webservice.saf.SAFHandler threw an exception
from
its handleResponse method. The exception was:
javax.xml.rpc.JAXRPCException: Failed to handle the response.
<26-Aug-2003 18:39:31 o'clock BST> <Info> <WebService> <BEA-220047> <A
exception
was thrown from callReceive in the Client Dispatcher.>
myserver:Info:A exception was thrown from callReceive in the Client
Dispatcher.
<26-Aug-2003 18:39:31 o'clock BST> <Info> <WebService> <BEA-220034> <A stack
tra
ce associated with message 220047 follows:
javax.xml.rpc.soap.SOAPFaultException: Exception during processing:
weblogic.web
service.saf.StoreForwardException: Could not find MessageData header in
aknowled
gement. (see Fault Detail for stacktrace)
at
weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.ja
va:285)
at
weblogic.webservice.core.ClientDispatcher.callReceive(ClientDispatche
r.java:119)
at
weblogic.webservice.saf.ConversationAssembler.getResponse(Conversatio
nAssembler.java:302)
at
weblogic.webservice.saf.ConversationAssembler.execute(ConversationAss
embler.java:536)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>

Hi Jon,
I've asked our WS RM guru to comment on your question, but I believe the
answer is going to be that you can explicitly roll back the transaction,
however only from the EJB application method, using the
EJBContext.setRollbackOnly() method.
Regards,
Bruce
Jon Mountjoy wrote:
>
Hi Bruce,
I looked at the example you pointed to, and it does what it says it does.
However, it doesn't attempt to rollback a transaction, which is what I am
doing.
The docs for reliable messaging say:
" If you want to roll back the transaction from the Java method, use the
Java Transaction API (JTA) to get the transaction object and then explicitly
roll back the transaction. "
They also indicate that the receiver executes in the context of a
transaction, which you may rollback.
For example, when the server is down, the transaction doesn't commit. This
behaviour is tested by your example, and it works.
However, when I modify your example to roll back the transaction in the web
service operation backend implementation,
then it doesn't. It yields the same exception that mine does.
For example, I modified your MarketService.java as indicated below to grab
the initial context and then during the operation grab the usertransaction
and call setRollbackOnly(). This causes WebLogic to throw a
weblogic.webservice.saf.StoreForwardException.
Any ideas?
Regards,
Jon
public final class MarketService {
private static boolean mustThrow = true;
InitialContext ctx = null;
public MarketService() {
try {
ctx = new InitialContext();
System.err.println("---InitialContext is set");
} catch (Exception e) {
System.err.println("---InitialContext is not set: " + e);
public void placeOrder(OrderInfo o) {
System.out.println("[MarketService] placing order: " + o);
mustThrow = !mustThrow;
if (mustThrow) {
System.out.println("--S:Going to roll back");
UserTransaction ut = null;
try {
ut = (UserTransaction) ctx.lookup(
"javax.transaction.UserTransaction");
System.out.println("--S: Set setRolbackOnly()");
ut.setRollbackOnly();
// <------------------------------------------
} catch (Exception e) {
System.err.println("--S: UT transaction error:" + e);
} else {
System.out.println("--S: -Not rolling back");
--S:In reliable TX operation
--S:Going to roll back
--S: Set setRolbackOnly()
--S: Finished Reliable operation
<29-Aug-2003 15:48:24 o'clock BST> <Info> <WebService> <BEA-220025> <Handler
weblogic.webservice.saf.SAFHandler threw an
exception from its handleResponse method. The exception was:
javax.xml.rpc.JAXRPCException: Failed to handle the response.>
myserver:Info:Handler weblogic.webservice.saf.SAFHandler threw an exception
from its handleResponse method. The exceptio
n was:
javax.xml.rpc.JAXRPCException: Failed to handle the response.
<29-Aug-2003 15:48:25 o'clock BST> <Info> <WebService> <BEA-220047> <A
exception was thrown from callReceive in the Clie
nt Dispatcher.>
myserver:Info:A exception was thrown from callReceive in the Client
Dispatcher.
<29-Aug-2003 15:48:25 o'clock BST> <Info> <WebService> <BEA-220034> <A stack
trace associated with message 220047 follow
s:
javax.xml.rpc.soap.SOAPFaultException: Exception during processing:
weblogic.webservice.saf.StoreForwardException: Could
not find MessageData header in aknowledgement. (see Fault Detail for
stacktrace)
at
weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:285)
at
weblogic.webservice.core.ClientDispatcher.callReceive(ClientDispatcher.java:
119)
at
weblogic.webservice.saf.ConversationAssembler.getResponse(ConversationAssemb
ler.java:302)
at
weblogic.webservice.saf.ConversationAssembler.execute(ConversationAssembler.
java:536)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
myserver:Info:A stack trace associated with message 220047 follows:

Com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException

Hello Team,
We have a scenario where we have a PI web service and we are importing the WSDL into our WD Java application.
While running the test scenario we are getting the below 2 exceptions in the stack trace.
20111222:Exception trace: com.sap.tc.webdynpro.model.webservice.api.WDWSModelExecuteException: Exception on execution of web service on destination 'WS_CUST_**' for operation 'GetCustomer*' in interface 'GetCustomer**'
Caused by: java.rmi.RemoteException: Cannot created typed model object. Factory for typed model class '$002fWsdlDefinitions$002fWsdlTypes$002fXsdSchema$005b1$005d$002fXsdComplexType$005b1$005d$002fXsdSequence$002fXsdElement$005b1$005d$002fXsdComplexType' has not been registered.; nested exception is:
com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Cannot created typed model object. Factory for typed model class '$002fWsdlDefinitions$002fWsdlTypes$002fXsdSchema$005b1$005d$002fXsdComplexType$005b1$005d$002fXsdSequence$002fXsdElement$005b1$005d$002fXsdComplexType' has not been registered.
Caused by: com.sap.tc.webdynpro.model.webservice.exception.WSModelRuntimeException: Cannot created typed model object. Factory for typed model class '$002fWsdlDefinitions$002fWsdlTypes$002fXsdSchema$005b1$005d$002fXsdComplexType$005b1$005d$002fXsdSequence$002fXsdElement$005b1$005d$002fXsdComplexType' has not been registered.
By running through few posts on SDN a probable solution for this was proposed as: blank the "designtimeWsdlUrl" properties of the model in NWDS and re-deploy the application
Any help on this would be great.
Regards,
Shailesh

Dear Shailesh,
Did you try to check the blank the "designtimeWsdlUrl" properties of the model in NWDS and re-deploy the application? please try to check and test.
Also try to import fresh in new DC and check whether it is working or not.
Best Regards
Arun Jaiswal

Ignoring Http basic authentication header in wls 7.0.sp2 web service servlet (weblogic.webservice.server.servlet.WebServiceServlet)

Hi!
We need to implement authentication using our own methods, and the authentication
information is provided to the web service implementation in a basic authentication
header. The problem is, that the servlet
weblogic.webservice.server.servlet.WebServiceServlet, which handles web services
in
wls 7.0.sp2, always attempts to perform authentication, if the header is present.
Is there any way to circumvent this, because we want to implement authentication
on our own?
I already know two workarounds:
The best would of course be to implement a custom security realm for our own
authentication system. This is not an option, implementing an own security
realm is overkill for this specific web service.
The other way would be to route the requests by way of a custom servlet, which
would
remove the basic authentication header, and put the authentication info in custom
headers, such as x-auth: <user:password>, or smthng similar, and after successful
authentication, make a call to bea's servlet weblogic.webservice.server.servlet.WebServiceServlet.
But still, I'd like to know if there is any way to tell bea's servlet to ignore
the basic
authentication header?
Oh yeah, by the way, this is URGENT, as always. (really!! ;)
Toni Nykanen

Currently there is no option to turn off security check.
I think you can use a servlet filter mapped to the URL
of your service, instead of a proxy servlet?
Regards,
-manoj
http://manojc.com
"Toni Nykanen" <[email protected]> wrote in message
news:3ef1577b$[email protected]..
>
Hi!
We need to implement authentication using our own methods, and theauthentication
information is provided to the web service implementation in a basicauthentication
header. The problem is, that the servlet
weblogic.webservice.server.servlet.WebServiceServlet, which handles webservices
in
wls 7.0.sp2, always attempts to perform authentication, if the header ispresent.
Is there any way to circumvent this, because we want to implementauthentication
on our own?
I already know two workarounds:
The best would of course be to implement a custom security realm for ourown
authentication system. This is not an option, implementing an own security
realm is overkill for this specific web service.
The other way would be to route the requests by way of a custom servlet,which
would
remove the basic authentication header, and put the authentication info incustom
headers, such as x-auth: <user:password>, or smthng similar, and aftersuccessful
authentication, make a call to bea's servletweblogic.webservice.server.servlet.WebServiceServlet.
>
But still, I'd like to know if there is any way to tell bea's servlet toignore
the basic
authentication header?
Oh yeah, by the way, this is URGENT, as always. (really!! ;)
Toni Nykanen

Error in Weblogic Webservice

I was using SAAJ 1.3 initially in WEBINF/lib and my code erred with
java.lang.NoSuchMethodError: newInstance at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection
Error Location:
SOAPConnectionFactory factory = SOAPConnectionFactory.newInstance();
SOAPConnection connection = factory.createConnection();
It erred on the above highlighted line. After some searching, I found that it could be because of Weblogic Server 9.2 not compatible with SAAJ 1.3. So I used SAAJ 1.2 and this error got solved. Now I am stuck up with the following error.
java.lang.UnsupportedOperationException: This class does not support SAAJ 1.1
at weblogic.webservice.core.soap.SOAPMessageImpl.getSOAPBody(SOAPMessageImpl.java:634)
Error Location:
SOAPElement attachmentElement = (SOAPElement)message.getSOAPBody().getElementsByTagNameNS(ws, "Attachment").item(0);
I am using SAAJ 1.2 but it says the class does not support SAAJ 1.1.
Again after some googling, I found that the error is due to some bug in Weblogic 9.2 when it is used with SAAJ 1.2. It was mentioned that following steps can be used to overcome this error.
1. Set classpath to latest saaj-impl.jar in startweblogic.cmd
2. Set the below 2 system properties in code.
System.setProperty("javax.xml.soap.MessageFactory","com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl");
System.setProperty("javax.xml.soap.SOAPConnectionFactory","weblogic.wsee.saaj.SOAPConnectionFactoryImpl");
I tried this too but it didnt work.
How can i get rid of this error? Also if i m going to set the classpath to SAAJ 1.3 in startweblogic.cmd, will it not result in the first error i got i.e java.lang.NoSuchMethodError: newInstance at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.
If my question is not very clear, please bear with me. I am pretty new to Webservice.
Can someone tell me how can i overcome this problem.

Have you included the IP addresses of the managed servers into the cluster address like for eg 192.127.1.2,192.127.1.2 in the cluster address field in the administration console? include it if not included that will fix the issue.
Regards,
Dinesh

Webservice Exception from Webdynpro

Hi,
We are on 7.1 SP04 Patch 1. We have created a webservice with http and None Authentication and deployed on EP 7.0 server. We have set a constant User Name and Password in Visual Admin.
We are able to execute this webservice successfully from Webservice navigator.
We have developed a Webdynpro appln with this webservice. We are getting an exception when the webservice is getting executed from Webdynpro appln.
"Exception on execution of webservice with WSDL url '<wsdl url>' with operation 'webservice name' in interface"
We checked in the trace file and got the following message
com.sap.mdm.logging.MdmLogger warning
WARNING: PingServerCommand failed
Have any one faced this issue?
Thanks,
Arun prabhu

Hi Walter,
The webservices are developed using MDM Webservice generator. The webdnpro application has to access MDM Data using MDM Webservices / MDM Java APIs.
This was working fine with MDM 7.1 SP03. Now we have upgraded to MDM 7.1 SP04.
When I try to access MDM Data from webdynpro using MDM Java API commands, I am getting an exception at AuthenticateUserSession Command. While access using MDM Webservices, I am getting an webservice exception and an entry in trace file.
Thanks,
Arun prabhu S

Weblogic-webservices-policy.xml

hi,
iam getting the following error in weblogic-webservices-policy.xml
Referenced file (weblogic-webservices-policy.xml) contains errors (http://www.bea.com/ns/weblogic/webservice-policy-ref/1.0/webservice-policy-ref.xsd).
weblogic-webservices-policy.xml containts the following lines of code:
<?xml version='1.0' encoding='UTF-8'?>
<webservice-policy-ref xmlns="http://www.bea.com/ns/weblogic/webservice-policy-ref" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/webservice-policy-ref http://www.bea.com/ns/weblogic/webservice-policy-ref/1.0/webservice-policy-ref.xsd"></webservice-policy-ref>
can anybody suggest how to fix this error?
thanks
john

Hi!
I was looking for some information regarding the weblogic-webservices-policy.xml file and founf your post. Did you success to solve the problem with it?
Greatly appreciate any inputs
Sincerely
J.

Weblogi webservice exception

Similar Messages

Maybe you are looking for