Google Webservice sample fails - "Service call exception"

I compiled the Best Practices - Google Search Functionality sample and deployed it to our new server. I started the application and after I entered a search term, it gave me the following error:
Service call exception; nested exception is: java.net.UnknownHostException: proxy
I'm stuck. Help, anyone?

Hi,
please visit on your portal (having the System Administrator role assigned to your user) System Administration->System Configuration->Service Configuration->Applications->com.sap.portal.ivs.httpservice->Services->Proxy (double click on proxy).
Either maintain proxy settings, or switch it off by editing field
HTTP - Enable Proxy setting
setting it to
FALSE
Regards,
Armin

Similar Messages

Service call Exception : webservices.jaxrpc.exceptions

Hi,
I have deployed my own enrichment adapter and while monitoring at following URL
http://xxxxxx:50000/webdynpro/dispatcher/sap.com/tcmdmenrichment~ui/MDM_EC
I am able to see an exception at
Adapter/application/services/service
Service call Exception; nested exception is:
com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException:
Invalid Response Code (401) Unauthorised. The requested URL was "http://localhost:50000/MDM_BUPA_WebSrvc/Config1?style=document"
Could somebody please help to come out of this issue...
Regards,
Manoj

Hello,
I'm facing the same problem.
Have you managed to resolv it?
Best regards,
Rui Romba

Error -32010 Service Call exception

Hi All,
I am getting the below mentioned error when I try to use BI Query Wizard in VC.
Error - 32010 Cannot Execute query. No result returned or XML returned in the result contains an error. Service call exception: nested exception is:
com.sap.engine.services.webservices.jaxrpc.ex
Invalid Response code: (404) Not found..
I have already checked the below mentioned post on the same error and have done the changes mentioned in the post, but still I am getting the same error.
Re: Error using VC BI Kit - Error -32010:
Request your suggestions as to how I could resolve the problem.
Regards
Anurag

Hi,
Can you please check the below OSS Note 797622 & 828313.
https://websmp103.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=012006153200001658542004
https://websmp103.sap-ag.de/~form/sapnet?_FRAME=CONTAINER&_OBJECT=012003146900000249742005
Thanks,
Ramakrishna
Message was edited by: Ramakrishna Prasad

Service call exception with Web service

Hello,
we changed tonight the interface of the web service I use in the web dynpro as model. So I deleted the old model and created a new model (under the same name) importing WSDL file.
The WSDL was created via XI which is the interface to a SAP R/3 system, calling in the end a RFC function module.
Now I get this error message:
Service call exception; nested exception is: com.sap.engine.services.webservices.jaxrpc.exceptions.XmlUnmarshalException: XML Deserialization Error. The content with schema type [http://trw.com/uta][/wsdl:definitions/wsdl:types/xsd:schema/xsd:complexType[1]/xsd:sequence/xsd:element[1]/xsd:complexType/xsd:sequence/xsd:element/xsd:complexType/xsd:sequence/xsd:element[9]/xsd:simpleType] is not valid.
The error occurs while executing wdContext.currentWebServiceElement().modelObject().execute(); command to get data from R/3 (via XI). What I can see in XI protocol is that the data comes back from the R/3 function module. But in web dynpro I get this error.
When no data are found there is no error executing command wdContext.currentWebServiceElement().modelObject().execute();
What to do in this case?
regards
Frank

Problem solved!
One of the fields in interface of the R/3 function module interface was changed from length 2 to 18. The adjustment in XI was missing and in the end the web dynpro runtime raised this error.
Nevertehless it is always very hard to find out the cause of such problems.

Service call exception; nested exception is: java.lang.IllegalMonitorStateE

Hi All,
when we try to run the Message Monitoring in our RWB then we get the following error:
Service call exception; nested exception is: java.lang.IllegalMonitorStateException
Has anybody of you an idea what this error occurs?
Thank you for the support..
Kind Regards
Markus

hi,
restarting the java stack would be enough. You can do that at SMICM. Before you should deregister all queues in SMQR so that incoming messages has to wait in the queue. Of coz all synchronous msgs would fail, as well messages going to your Java Inbound Adapters.
note:reward points if solution found helpfull.....
regards
chandrakanth.k

Service call exception?

Hi,
I Expose ABAP Functionality As WebService.
We Get WSDL URL in WSADMIN TCODE.
We Go To NWDS.And Develop WebDynpro Application Using Webservice Model.We Specify WSDL Under WSDL.
We Deploy the Application It's Successfully Deployed.
But We Give Import Values We Get Service Call Exception
"Service call exception:; nested exception is: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized. The requested URL was:"http://localhost:8000/sap/bc/srt/rfc/sap/ZFLIGHT?sap-client=800""
is it Require Any Configuration In ECC6.
Thanks
SubbaRao Chinta

Hi subbarao,
I also faced with the same issue last week. But i created a webservice out of a CAF .
The solution what i found is when you create a webservice it will ask for the authorization levels. There will be three options for setting the authorization levels
1)Basic SOAP
2)Simple SOAP
3)Secure SOAP
By default the option will be Basic SOAP .
My problem is solved by changing the option to simple SOAP.
You can try that once..

Service call exception java.lang. missing soap end tag..

Hi Experts,
I did the soap to rfc sync interface and Create the java deployble client proxy application in nwds. In Nwds i maintaine the PI parameters message server host,port and exectue the application. it is working fine. but i was deploying the another j2ee engine server messager server host name and port parameters I am getting the error. that is Service call exception java.lang. mising soap end tag.
Could you help me.
Thanks & Regards,
Veera

hi,
restarting the java stack would be enough. You can do that at SMICM. Before you should deregister all queues in SMQR so that incoming messages has to wait in the queue. Of coz all synchronous msgs would fail, as well messages going to your Java Inbound Adapters.
note:reward points if solution found helpfull.....
regards
chandrakanth.k

ADS does not work.(Service call exception)

Hi All,
According to SAP note 937697 "Usage of SAP NetWeaver BI Diagnostics & Support Desk Tools", when running the tool, it gives following error:
ADS does not work.(Service call exception; nested exception is: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized. The requested URL was:"http://sapbwd.ni.ad.newsint:50000/AdobeDocumentServices/Config?style=document")
I have been looking into system to find out how to solve the issue, but could not, is there anyone who can help me with exact instructions what I do need to do.
Thanks in advance
sahmad

Dear Sahmad,
I would suggest you to check notes 1004321 and 944221. The first one says that mostly of this kind of issues (and I have already seen several ones) is caused for bad passwords for user ADSUSER or this account expired. The second note is a troubleshoot note you can also do.
You can also follow this procedure to check that:
Please open the Visual Administrator and browse to Server -> Services -> Security Provider -> Policy Configurations
In the Components tab you will see the service.destinations policy. Click on this and then click on the AccessDestinations security Role. Modify this and add the J2EE_ADMIN/Administrator user to this role and save.
Maybe the password is not set correctly as well. I think it worths to be set it again. First you have to identify where your ADSUSER maintained.
Go to http(s)://<SERVER>:<PORT>/useradmin search for ADSUSER If Datasource:
- LDAP -> check psw of ADSUSER in LDAP and enter it in SM59
- UME data -> check psw of ADSUSER in Visual Admin and enter it in SM59
- ABAP -> check psw of ADSUSER the ABAP system in the following client:
Visual Admin->UME Provider->Properties->ume.r3.connection.master.client
If you want, also, you can change the ADS by the SAP Export Library, as per SAP Note 1112132. It is very simple to activate and will bypass ADS, doing every function ADS does.
I hope it helps.
Kind Regards,
Marcio

PDFObjectRuntimeException: Service call exception

Hi,
i'd like to use Adobe Interactive Forms to let a user to
fill in data and to merge this information with other generated information into a resulting pdf document.
When i go to the view (in a java web dynpro) i get the following exception:
com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
 com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (404) Not Found.
 at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:282)
 at com.sap.tc.webdynpro.pdfobject.core.PDFObject.createPDF(PDFObject.java:224)
 at com.sap.tc.webdynpro.clientserver.adobe.AdobeFormHelper.createPDFDocumentForUIElement(AdobeFormHelper.java:483)
 at com.sap.tc.webdynpro.clientserver.uielib.adobe.impl.InteractiveForm.afterHandleActionEvent(InteractiveForm.java:185)
 at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.afterHandleActionEvent(ClientApplication.java:1154)
 at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:402)
 at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:649)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
 at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:248)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)
Caused by: java.rmi.RemoteException: Service call exception; nested exception is:
 com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (404) Not Found.
 at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:85)
 at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:95)
 at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:279)
 ... 27 more
Caused by: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (404) Not Found.
 at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.handleResponseMessage(MimeHttpBinding.java:834)
 at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1238)
 at com.sap.tc.webdynpro.adsproxy.ConfigBindingStub.rpData(ConfigBindingStub.java:78)
 ... 29 more
The mode property of the AIF is set to updateDataInPdf (the same exception occurs using the createPdf mode).
Product info:
Server:
Web Dynpro Runtime Vendor: SAP, Build ID: 6.4014.00.0000.20060719132130.0000 (release=NW04_14_REL, buildtime=2006-07-19:23:04:47[UTC], changelist=19247, host=PWDFM087)
J2EE Engine 6.40 patchlevel 100381.311
Java VM Java HotSpot(TM) Server VM, version:1.4.2_07-b05, vendor: Sun Microsystems Inc.
Operating system Windows 2003, version: 5.2, architecture: x86
Web Dynpro Code Generation Infos
SapDictionaryGenerationCore 6.4014.00.0000.20050818151336.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:08:16[UTC], changelist=363802, host=PWDFM026.wdf.sap.corp)
SapDictionaryGenerationTemplates (unknown)
SapGenerationFrameworkCore 6.4014.00.0000.20050818152155.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:01:32[UTC], changelist=363812, host=PWDFM026.wdf.sap.corp)
SapIdeWebDynproCheckLayer 6.4014.00.0000.20050818152737.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:15:40[UTC], changelist=363825, host=PWDFM026.wdf.sap.corp)
SapMetamodelCommon 6.4014.00.0000.20050818152303.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:02:26[UTC], changelist=363816, host=PWDFM026.wdf.sap.corp)
SapMetamodelCore 6.4014.00.0000.20050818152303.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:02:18[UTC], changelist=363816, host=PWDFM026.wdf.sap.corp)
SapMetamodelDictionary 6.4014.00.0000.20050606171352.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:05:38[UTC], changelist=351719, host=PWDFM026.wdf.sap.corp)
SapMetamodelWebDynpro 6.4014.00.0000.20050818152356.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:11:31[UTC], changelist=363818, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationCTemplates 6.4014.00.0000.20050905165427.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:26:31[UTC], changelist=366934, host=PWDFM026)
SapWebDynproGenerationCore 6.4014.00.0000.20050818152737.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:16:08[UTC], changelist=363825, host=PWDFM026.wdf.sap.corp)
SapWebDynproGenerationTemplates 6.4014.00.0000.20050905165427.0000 (release=630_VAL_REL, buildtime=2005-09-09:20:26:31[UTC], changelist=366934, host=PWDFM026)
sap.com/tcwddispwda
No information available
sap.com/tcwdcorecomp
No information available
Adobe Document Server version is NW04 SPS 14
Any comments are appreciated.
regards
 Dirk

Apparently the ADS was not configured.
One can check this using the following URL as
template:
http://<server>:<port>/AdobeDocumentServices/Config
See also the thread Re: ADS Error for interactive forms
regards
 Dirk

XI rwb: service call exception

I cann't do the monitoring via message mornitoring of runtime workbench,
when I click the 'start', the error message will display as below:
'Service call exception; nested exception is: java.lang.IllegalMonitorStateException'
I've never seen this error message before.

Hi man or woman without a name,
restarting the java stack would be enough. You can do that at SMICM. Before you should deregister all queues in SMQR so that incoming messages has to wait in the queue. Of coz all synchronous msgs would fail, as well messages going to your Java Inbound Adapters.
Before restarting open a OSS call with priority very high, it is a production system and not your fault. They should help you immediatly.
Regards,
Udo

Service call Exception : ClassNotFoundException XMLTokenReader

Hi All,
I am trying to call a webservice using a StandAloneProxy generated by Netweaver. The call works fine when called from a POJO. But when deployed and called from a jsp page, it returns the following error. I've included sapxmltoolkit.jar that holds XMLTokenReader class but to no avail.
java.rmi.RemoteException: Service call exception; nested exception is:
 java.lang.ClassNotFoundException: com.sap.engine.lib.xml.parser.tokenizer.XMLTokenReader
Found in negative cache
Loader Info -
ClassLoader name: [rim.com/eSellingWebAppFS]
Parent loader name: [Frame ClassLoader]
References:
 common:service:http;service:servlet_jsp
 service:ejb
 common:service:iiop;service:naming;service:p4;service:ts
 service:jmsconnector
 library:jsse
 library:servlet
 common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl
 library:ejb20
 library:j2eeca
 library:jms
 library:opensql
.........
Error causing code:
 Z_ES_CUSTOMER_SEARCHResponse custSearchResponse = new Z_ES_CUSTOMER_SEARCHResponse();
 Z_ES_CUSTOMER_SEARCHServiceImpl serviceImpl = new Z_ES_CUSTOMER_SEARCHServiceImpl();
 Z_ES_CUSTOMER_SEARCHPortType servicePort = serviceImpl.getLogicalPort();
 ((Stub)servicePort)._setProperty(javax.xml.rpc.Stub.USERNAME_PROPERTY,authUsername);
 ((Stub)servicePort)._setProperty(javax.xml.rpc.Stub.PASSWORD_PROPERTY,authPassword);
 Z_ES_CUSTOMER_SEARCH params = new Z_ES_CUSTOMER_SEARCH();
 ZESCRITERIA zescriteriaArr[] = new ZESCRITERIA[criteriaList.size()];
 Iterator criteriaIter = criteriaList.iterator();
 int index = 0;
 while(criteriaIter.hasNext()) {
 SearchCriteria criteria = (SearchCriteria)criteriaIter.next();
 ZESCRITERIA zescriteria = new ZESCRITERIA();
 zescriteria.setOBJECT(SearchCriteria.CUSTOMER_OBJECT);
 zescriteria.setOPERATION(criteria.getSearchOperation());
 zescriteria.setSEARCH_NAME(criteria.getSearchName());
 zescriteria.setHIGH(criteria.getHighValue());
 zescriteria.setLOW(criteria.getLowValue());
 zescriteriaArr[index++] = zescriteria;
 params.setSEARCH_CRITERIA(zescriteriaArr);
 params.setRESULT_SET(new ZESKUNNRHITS[0]);
 params.setRETURN(new BAPIRET2[0]);
 params.setSEARCH_OBJECT(SearchCriteria.CUSTOMER_OBJECT);
 Z_ES_CUSTOMER_SEARCHResponse response = servicePort.z_ES_CUSTOMER_SEARCH(params); <<---- ERROR

We have come across exactly the same problem, but with a "deployable proxy". We are using stack 16.
We are calling a web service exposed by BW, and the response seems to generate this documented error.
(please see error info below)
Has anyone else come across this problem, and more importantly, the solution?
If you need more technical specs, I can provide it.
Thanks in advance !
HTTP/1.1 500 Internal Server Error
Connection: close
Server: SAP J2EE Engine/6.40
Content-Type: text/xml; charset=UTF-8
Date: Thu, 04 May 2006 15:36:26 GMT
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" ><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode>SOAP-ENV:Client</faultcode><faultstring>Erreur lors de l'appel du proxy BW
java.rmi.RemoteException: Service call exception; nested exception is:
 java.lang.ClassNotFoundException: com.sap.engine.lib.xml.parser.tokenizer.XMLTokenReader
Found in negative cache
Loader Info -
ClassLoader name: [sap.com/TestBWProxy]
Parent loader name: [Frame ClassLoader]
References:
 common:service:http;service:servlet_jsp
 service:ejb
 common:service:iiop;service:naming;service:p4;service:ts
 service:jmsconnector
 library:jsse
 library:servlet
 common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl
 library:ejb20
 library:j2eeca
 library:jms
 library:opensql
 common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore
 interface:resourcecontext_api
 interface:webservices
 interface:cross
 interface:ejbserialization
Resources:
 /usr/sap/DA1/DVEBMGS91/j2ee/cluster/server0/apps/sap.com/TestBWProxy/webservices_container/wsClients/ws_cl_0/jars/com.hydroquebec.test.bw.proxy.BWProxy.jar
 /usr/sap/DA1/DVEBMGS91/j2ee/cluster/server0/apps/sap.com/TestBWProxy/webservices_container/wsClients/app_jars/TestBWProxy.jar
Loading model: {parent,references,local}
 at com.hydroquebec.test.bw.proxy.Z_RRW3_GET_QUERY_VIEW_DATASoapBindingStub.RRW3_GET_QUERY_VIEW_DATA(Z_RRW3_GET_QUERY_VIEW_DATASoapBindingStub.java:98)
 at com.hydroquebec.test.bw.ejb.TestBWBean.getQueryData3(TestBWBean.java:93)
 at com.hydroquebec.test.bw.ejb.TestBWLocalLocalObjectImpl0.getQueryData3(TestBWLocalLocalObjectImpl0.java:177)
 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:324)
 at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)
 at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)
 at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)
 at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)
 at SoapServlet.doPost(SoapServlet.java:51)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.ClassNotFoundException: com.sap.engine.lib.xml.parser.tokenizer.XMLTokenReader
Found in negative cache
Loader Info -
ClassLoader name: [sap.com/TestBWProxy]
Parent loader name: [Frame ClassLoader]
References:
 common:service:http;service:servlet_jsp
 service:ejb
 common:service:iiop;service:naming;service:p4;service:ts
 service:jmsconnector
 library:jsse
 library:servlet
 common:library:IAIKSecurity;library:activation;library:mail;library:tcsecssl
 library:ejb20
 library:j2eeca
 library:jms
 library:opensql
 common:library:com.sap.security.api.sda;library:com.sap.security.core.sda;library:security.class;library:webservices_lib;service:adminadapter;service:basicadmin;service:com.sap.security.core.ume.service;service:configuration;service:connector;service:dbpool;service:deploy;service:jmx;service:jmx_notification;service:keystore;service:security;service:userstore
 interface:resourcecontext_api
 interface:webservices
 interface:cross
 interface:ejbserialization
Resources:
 /usr/sap/DA1/DVEBMGS91/j2ee/cluster/server0/apps/sap.com/TestBWProxy/webservices_container/wsClients/ws_cl_0/jars/com.hydroquebec.test.bw.proxy.BWProxy.jar
 /usr/sap/DA1/DVEBMGS91/j2ee/cluster/server0/apps/sap.com/TestBWProxy/webservices_container/wsClients/app_jars/TestBWProxy.jar
Loading model: {parent,references,local}
 at com.sap.engine.frame.core.load.ReferencedLoader.loadClass(ReferencedLoader.java:348)
 at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302)
 at com.sap.engine.services.webservices.jaxrpc.encoding.SimpleValidator.checkMaxLengthString(SimpleValidator.java:77)
 at com.hydroquebec.test.bw.proxy.types.Char22.deserialize(Char22.java:36)
 at com.sap.engine.services.webservices.jaxrpc.encoding.InstanceBuilder.readElement(InstanceBuilder.java:603)
 at com.sap.engine.services.webservices.jaxrpc.encoding.InstanceBuilder.readSequence(InstanceBuilder.java:829)
 at com.sap.engine.services.webservices.jaxrpc.encoding.InstanceBuilder.readContent(InstanceBuilder.java:955)
 at com.sap.engine.services.webservices.jaxrpc.encoding.GeneratedComplexType.deserialize(GeneratedComplexType.java:1723)
 at com.sap.engine.services.webservices.jaxrpc.encoding.DocumentArrayBuilder.readContent(DocumentArrayBuilder.java:82)
 at com.sap.engine.services.webservices.jaxrpc.encoding.GeneratedComplexType.deserialize(GeneratedComplexType.java:1656)
 at com.sap.engine.services.webservices.jaxrpc.encoding.InstanceBuilder.readElement(InstanceBuilder.java:603)
 at com.sap.engine.services.webservices.jaxrpc.encoding.InstanceBuilder.readSequence(InstanceBuilder.java:829)
 at com.sap.engine.services.webservices.jaxrpc.encoding.InstanceBuilder.readContent(InstanceBuilder.java:955)
 at com.sap.engine.services.webservices.jaxrpc.encoding.GeneratedComplexType.deserialize(GeneratedComplexType.java:1723)
 at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.getResponseDocument(MimeHttpBinding.java:1104)
 at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1432)
 at com.hydroquebec.test.bw.proxy.Z_RRW3_GET_QUERY_VIEW_DATASoapBindingStub.RRW3_GET_QUERY_VIEW_DATA(Z_RRW3_GET_QUERY_VIEW_DATASoapBindingStub.java:86)
 ... 27 more
</faultstring><detail><ns1:getQueryData3_com.hydroquebec.sap.integration.infra.ExceptionTransactionSAP xmlns:ns1='urn:TestBWWsd/TestBWVi'></ns1:getQueryData3_com.hydroquebec.sap.integration.infra.ExceptionTransactionSAP></detail></SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>

Monitoring the Enrichment Controller- Service call Exception

Hi,
I have configured my enrichment controller but while monitoring the Enrichment Controller System, I found following error under Adapters\Application\Services\testport\Availability.
Service call Exception; Nested Exception is: java.net.UnknownHostException
iltlvt33.tlv.sap.com
I also get the following exception while invoking the simulation adapter
"Unknown enrichment service: Serviceport"
Could anybody suggest something to solve this issue, because I am stuck here...
Thanks in advance,
Manoj
Edited by: Manoj Kumar Nanda on Aug 28, 2008 7:26 AM
Edited by: Manoj Kumar Nanda on Aug 28, 2008 7:26 AM

Hi Swarna,
the identical port code is the one that you have specified in the config.xml
outbound port is Manual and
Inbound port is automatic processing
BTW do you have any experience on this...Will it solve my issue?
please visit on your portal (having the System Administrator role assigned to your user) System Administration->System Configuration->Service Configuration->Applications->com.sap.portal.ivs.httpservice->Services->Proxy (double click on proxy). Check if the proxy server equals u201Ciltlvt33.tlv.sap.corpu201D.
Either maintain proxy settings, or switch it off by editing field
HTTP - Enable Proxy setting
setting it to FALSE
( Taken from the sdn : /thread/78976 [original link is broken])
Regards,
Manoj
Edited by: Manoj Kumar Nanda on Aug 28, 2008 1:32 PM

Google Webservice API - failed

Hi all,
I am exeperimenting with creating a Portal Service
from a WSDL. And I am following the example of
GoogleSearch given in PDK.
I've created everything according to the documentation
and also registered and used the Key for Google API.
The error as you can see from the log below is stating
: Deserializer not found or not supported.
what could be the problem?
I am using EP6.0 Sneak Preview.
regs
Anoop C M
Sep 30, 2004 1:02:28 PM # SAPEngine_Applica... Fatal           Exception ID:01:02_30/09/04_0045
com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
Component : pcd:portal_content/TST_FLDR/com.mycomp.anoop/iViewGoogleWS
Component class : com.mycom.wsdl2service.MyGooglePage
User : test1
     at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:864)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:313)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:137)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:185)
     at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:209)
     at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:604)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:303)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:137)
     at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:185)
     at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:669)
     at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:232)
     at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:532)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:415)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:153)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:377)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:257)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:322)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:300)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:699)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:224)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:147)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:140)
Caused by: com.sapportals.portal.prt.component.PortalComponentException: Exception during PageProcessorComponent.doContent()
     at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:139)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
     at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
     at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:303)
     ... 29 more
Caused by: java.lang.reflect.InvocationTargetException
     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:324)
     at com.sapportals.htmlb.page.DynPage.doProcessCurrentEvent(DynPage.java:172)
     at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:101)
     at com.sapportals.portal.htmlb.page.PageProcessorComponent.doContent(PageProcessorComponent.java:135)
     ... 32 more
Caused by: java.lang.Exception: Deserializer not found or not supported
     at com.sap.portal.prt.service.soap.serializers.GoogleSearchResultSer.deserializeXMLElement(GoogleSearchResultSer.java:207)
     at com.sap.portal.prt.service.soap.serializers.GoogleSearchResultSer.unmarshall(GoogleSearchResultSer.java:83)
     at com.sapportals.portal.prt.service.soap.ParamsProcessor.getSOAPParameter(ParamsProcessor.java:148)
     at com.sapportals.portal.prt.service.soap.element.PRTSOAPBodyElement.constructSOAPParam(PRTSOAPBodyElement.java:579)
     at com.sapportals.portal.prt.service.soap.element.PRTSOAPBodyElement.processParams(PRTSOAPBodyElement.java:564)
     at com.sapportals.portal.prt.service.soap.element.PRTSOAPBodyElement.init(PRTSOAPBodyElement.java:192)
     at com.sapportals.portal.prt.service.soap.element.PRTSOAPBodyElement.(PRTSOAPBodyElement.java:55)
     at com.sapportals.portal.prt.service.soap.element.PRTSOAPBody.init(PRTSOAPBody.java:94)
     at com.sapportals.portal.prt.service.soap.element.PRTSOAPBody.(PRTSOAPBody.java:36)
     at com.sapportals.portal.prt.service.soap.element.PRTSOAPEnvelope.init(PRTSOAPEnvelope.java:113)
     at com.sapportals.portal.prt.service.soap.element.PRTSOAPEnvelope.(PRTSOAPEnvelope.java:54)
     at com.sapportals.portal.prt.service.soap.element.PRTSOAPMessage.processSOAPMessage(PRTSOAPMessage.java:58)
     at com.sapportals.portal.prt.service.soap.element.PRTSOAPMessage.(PRTSOAPMessage.java:40)
     at com.sapportals.portal.prt.service.soap.SOAPService.call(SOAPService.java:177)
     at com.sapportals.portal.prt.service.soap.PRTSOAPCall.invokeMethod(PRTSOAPCall.java:208)
     at com.mycomp.wsdl2service.MyGoogleSearch.doGoogleSearch(MyGoogleSearch.java:169)
     at com.mycomp.wsdl2service.MyGooglePage$MyGooglePageDynPage.onSearchButtonClicked(MyGooglePage.java:83)
     ... 39 more
[email protected]4a #

HI Karsten,
   Thanks but I've reffered that post already. It refers to issue with studio 1.3.1 and j2ee 25.
Since mine is dev studio 2.0.5 and J2ee 30 it seems
to be a different problem.
   Well, I guess the problem lies in deserializng the resultset.
I have not applied any patches to EP6 SP4 Sneak Preview
and to the devstudio. Do i need to apply some?
After some analysis of the code that the plugin generated
i feel the err msg is generated from tge following code excerpt. Any idea on what could be wrong?
if (qparam != null){
                         SOAPDeserializer dser = reg.getDeserializer(qparam, ISOAPParamConstants.NS_URI_SOAP_ENC);
                         if ( dser == null)
                              throw new PRTFaultSerializator(
                              "The Deserializer for "qparam.getLocalPart()" not found or not supported by the soap service!.",
                              (Object)this, new Exception("Deserializer not found or not supported"));
regs
Anoop

Com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call

Hi experts,
I just installed and configured ADS in NW04-Java SP20 and tested the URL http://host:portal/AdobeDocumentServices/Config. it shows the version information in the response.
When I try to run the Java-Webdynpro interactive form I am getting below messages. I also tried SDN sample project, I got the same message.
I installed ACF for NW04, it shows in the control panel, but not in the IE add-ons list.
Error Message:
com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
     java.net.ConnectException: Connection refused: connect
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:282)
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.createPDF(PDFObject.java:224)
com.sap.tc.webdynpro.pdfobject.core.PDFObjectRuntimeException: Service call exception; nested exception is:
     java.net.ConnectException: Connection refused: connect
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.doSoapCall(PDFObject.java:282)
     at com.sap.tc.webdynpro.pdfobject.core.PDFObject.createPDF(PDFObject.java:224)
Caused by: java.net.ConnectException: Connection refused: connect
     at java.net.PlainSocketImpl.socketConnect(Native Method)
     at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
     at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
     at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
Could you please tell me is any thing missing???
Thanks in advance,
Ramana.

Hi Ramana,
If you are on NW '04 SP11 or lower, try upgrading to a later version. SP 12 (and higher) contains a newer version of Adobe document services that renders much faster.
By default the Web service client socket timeout is set to 60. Try changing this parameter in the Visual Administrator: Server -> Services -> Web Services Container on the Settings tab.
In online scenarios with large context performance issues are seen. It may make more sense to create smaller PDFs with a stricter data selection.
Also refer to this note:
[Note 811342 - Time Out exception when rendering to Adobe document service|https://websmp230.sap-ag.de/sap/support/notes/811342]
Hope this helps!!
Cheers,
Arafat

Using Web Dynpro authentication for a Web Service call

Hi all,
I want to develop a Web Dynpro that calls a Web Service running on the same Web AS (7.0). The Web Dynpro will be integrated in a Portal. The web service that has to be called is automatically generated when we create a guided procedure :
http://help.sap.com/saphelp_nw2004s/helpdata/en/44/44c59fd7c72e84e10000000a155369/frameset.htm
In my Web Dynpro, I imported the WSDL of this WS and created a model.
The first time I tried to call the WS in my Web Dynpro I got an authentication error :
Service call exception; nested exception is: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (401) Unauthorized. The requested URL was:"http://<myHostName>:50100/GPRuntimeFacadeWS/GPProcessExposing?style=document&pid=CA544E9B629A11DB91480017A48D672A&pver=0.5"
So I hard-coded an HTTP authentication :
 model._setUser("myWASuser");
 model._setPassword("myPassword");
And the Web Service call now works.
Now the next step is that the WS call is made by the user that runs the Web Dynpro. So I found this documentation :
http://help.sap.com/saphelp_nw04/helpdata/en/59/e8e95d1eba48dfa86ae91ad8816f5d/frameset.htm
It would resolve my authentication problem, AND the transport issue : at the moment the Web Service URL is stored in the Logical Port of the WD model, and at transport time, a rebuild of the WD project will be needed.
So I applied what is said in the doc : from the point of view of the Web Service consumer, I just had to add :
 model._setHTTPDestinationName("STARTGP");
(where STARTGP is the name of the destination I created in the Visual Administrator with a "Logon Ticket" authentication.)
before the execute(), and I removed my hardcoded authentication.
Unfortunately, nothing changes... I still get a 401 authentication error.
Does anyone have an idea about this ? Or maybe a workaround ?
Thanks in advance for any suggestion.
Regards,
Julien

Hello Julien,
I have a scenario similar to yours. A client webdynpro application accessing a EJB methods exposed as web service. Those EJB's methods calls R3 RFC's. The client requirements' was to allow SSO through all the layers (Webdynpro -> EJB WS -> RFC). The Webdynpro and EJB's are deployed on the same WAS.
Solution:
1 - Create a RFC Destination on Visual Administration provide the R3 connection parameters and set the Authentication for "Current User (Logon Ticket)". Save your Destination;
2 - In your EJB Project open your Web Service Configuration, on the Security page, set:
 Authentication Mechanism: HTTP Authentication
 Basic (username/password)
 Use SAP Logon Ticket
3 - In your EJB, implement the following code to create JCO Client for the RFC invocations:
Object obj = ctx.lookup(DestinationService.JNDI_KEY);
 DestinationService dstService = (DestinationService) obj;
 RFCDestination dst = (RFCDestination) dstService.getDestination("RFC", "<YOUR_RFC_DESTINATION_NAME>");
 Properties jcoProperties = dst.getJCoProperties();
 JCO.Client jcoClient = JCO.createClient(jcoProperties);
4 - In your EAR Project, open your "application-j2ee-engine.xml" and add the References:
 "tc/sec/destinations/service" as Service
 "tc/sec/destinations/interface" as Interface.
5 - Create your EAR File and Deploy;
6 - Check if the web service now requires Authentication: go to http://<host>:<port>/index.html and click on Web Services Navigator. Test your Web Service. Your Web Service should requiere you to log in before execute the test;
7 - Go back to your Visual Administrator and create a HTTP Destination. Provide your WS URL (should be something like "http://<host>:<port>/<WS_NAME>/Config1?style=document"). Choose Authentication: Logon Ticket. Save your Destination;
8 - Go to your webdynpro project, import your WS Model. (If you have already created it, you have to delete it and import it again, refer to this blog on how to reimport WS Models: /people/bertram.ganz/blog/2005/10/10/how-to-reimport-web-service-models-in-web-dynpro-for-java How To Reimport Web Service Models in Web Dynpro for Java );
9 - Open your model's Logical Ports node, go to the Security tab, and choose "Use SAP Logon Ticket";
10 - In your webdynpro code, before you call the ws invocation (should be something like that: <YOUR_NODE_DEFINITION>.modelObject().execute();), include the following line:
<YOUR_NODE_DEFINITION>.modelObject()._setHTTPDestinationName("<YOUR_HTTP_DESTINATION_NAME>");
11 - Save All Metadata and deploy your Webdynpro App. Test your results.
I hope it helps you, as the documentation on how to implement this scenario is scattered through the SDN and all the SAP help portal.
Best regards,
Paulo.

Google Webservice sample fails - "Service call exception"

Similar Messages

Maybe you are looking for