Invalid url exception when calling webservice

Hi,
Im trying to create a LinkToURL component with a reference to a webservice which returns a document. When running the app it crashes with the message that the URL is invalid but when i input it into a browser, it works fine and opens the document. The url looks like:
http://nlvdhb300:10013/contract?D:\EAI\HR\Contracts\00300901-20061002113009.doc
Can anyone tell me why this doesnt work?
Much thanks..
Hugo Hendriks

Found the solution....The backslashes where the problem...replaced them with forward ones and it works now.
greetz
Hugo

Similar Messages

URL Escaping when calling Webservices API Changed?

Hello,
It seems that something has changed recently with the Adobe Connect Webservices API. In the past, when I would call 'principal-update' to create or update a user, I would sanitize all my strings using urlencode() in PHP, which takes any non-alphanumeric characters (or dashes and underscores) and "percent encodes" them. For example, a "@" character in an email address becomes "%40".
This is important especially in the case that a string contains an ampersand (&) or question mark (?) since those characters are used to pass the parameters themselves in the URL string.
This has always worked fine until I noticed a few days ago it was no longer working.
If I attempt to create a user with an email address formatted with the "%40", Connect now comes back with an error message saying it wasn't formatted properly. Removing the encoding fixes the problem.
However, this is NOT best practice. And especially for passwords, which could theoretically contain ampersands and question marks, you cannot simply pass the raw string in the URL as it will create a malformed URL.
Has anyone noticed this, and does Adobe know about it? Seems like a major problem, and means I will have to prevent users from using these special characters in their passwords until this is fixed.
-Jeff

Jeff,
Thanks for the posting. I suggest you should call this into Support as a bug. It's possible that they changed something that affected this without seeing the ramifications.

Error when call webservice on servlet

Hi All,
I'm having a problem when calling webservice inside the servlet on the WebLogic environment.
My code:
* Webservice:
package ws;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.PreparedStatement;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.util.Date;
import javax.jws.WebMethod;
import javax.jws.WebParam;
import javax.jws.WebService;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.sql.DataSource;
@WebService
public class getData {
public getData() {
super();
@WebMethod
public String getHello() {
return "HELLO HELLO";
private Connection getConn() throws NamingException, SQLException {
InitialContext ic = new InitialContext();
DataSource ds = (DataSource)ic.lookup("jdbc/hnxwebsite");
//System.out.println("POOL !!!!");
Connection con = ds.getConnection();
con.setAutoCommit(false);
return con;
@WebMethod
public String getIndexData(@WebParam(name="param") String param) {
StringBuffer sb = new StringBuffer();
String sql =
"Select * From idx_index_info iii where iii.index_code= ?";
Connection con = null;
PreparedStatement pstmt = null;
ResultSet rs = null;
try {
con = getConn();
pstmt = con.prepareStatement(sql);
pstmt.setString(1, param);
rs = pstmt.executeQuery();
int columnCount = rs.getMetaData().getColumnCount();
Object val;
while (rs.next()) {
for (int i = 1; i < columnCount; i++) {
//System.out.println(i);
val = rs.getObject(i);
if (val != null)
sb.append(val.toString() + "\n");
} catch (SQLException e) {
e.printStackTrace();
} catch (NamingException e) {
e.printStackTrace();
} finally {
try {
if (rs != null)
rs.close();
if (pstmt != null)
pstmt.close();
if (con != null)
con.close();
} catch (Exception e) {
e.printStackTrace();
String str = sb.toString();
int len = str.length();
//System.out.println("LENGTH >>>>"+len);
return str;
public static void main(String[] arg) {
Date date = new Date();
System.out.println(date.toGMTString());
getData gd = new getData();
System.out.println(date.toGMTString());
//System.out.println(gd.getIndexData("ACB"));
* WebClient:
package hnx;
import java.util.Date;
import java.util.Map;
import javax.xml.namespace.QName;
import javax.xml.soap.MessageFactory;
import javax.xml.soap.SOAPBody;
import javax.xml.soap.SOAPBodyElement;
import javax.xml.soap.SOAPElement;
import javax.xml.soap.SOAPMessage;
import javax.xml.ws.BindingProvider;
import javax.xml.ws.Dispatch;
import javax.xml.ws.Service;
import javax.xml.ws.WebServiceException;
import javax.xml.ws.soap.SOAPBinding;
public class wsClient {
public wsClient() {
super();
public String procWeb() {
String strmsg = null;
try {
QName serviceName = new QName("http://192.168.60.18:7001/","getDataService");
// QName for Port As defined in wsdl.
QName portName = new QName("http://192.168.60.18:7001/","getDataPort");
// //Endpoint Address
String endpointAddress = "http://192.168.60.18:7001/WsIndex/getDataPort?wsdl";
// Create a dynamic Service instance
Service service = Service.create(serviceName);
service.addPort(portName, SOAPBinding.SOAP11HTTP_BINDING,
endpointAddress);
// Create a dispatch instance
Dispatch<SOAPMessage> dispatch = service.createDispatch(portName,
SOAPMessage.class, Service.Mode.MESSAGE);
// Use Dispatch as BindingProvider
BindingProvider bp = (BindingProvider) dispatch;
// Optionally Configure RequestContext to send SOAPAction HTTP Header
Map<String, Object> rc = bp.getRequestContext();
rc.put(BindingProvider.SOAPACTION_USE_PROPERTY, Boolean.TRUE);
rc.put(BindingProvider.SOAPACTION_URI_PROPERTY, "http://ws/");
// Obtain a preconfigured SAAJ MessageFactory
MessageFactory factory = ((SOAPBinding) bp.getBinding())
.getMessageFactory();
// Create SOAPMessage Request
SOAPMessage request = factory.createMessage();
// Request Body
SOAPBody body = request.getSOAPBody();
// Compose the soap:Body payload
QName payloadName = new QName("http://ws/", "getIndexData","ns1");
SOAPBodyElement payload = body.addBodyElement(payloadName);
SOAPElement message = payload.addChildElement( "param");
message.addTextNode("HNX302");
request.saveChanges();
// Invoke the endpoint synchronously
System.out.println(message);
SOAPMessage reply = null;
try { // Invoke Endpoint Operation and read response
reply = dispatch.invoke(request);
} catch (WebServiceException wse) {
wse.printStackTrace();
// process the reply
SOAPBody bodyRes = reply.getSOAPBody();
SOAPBodyElement nextSoapBodyElement = (SOAPBodyElement) bodyRes
.getChildElements().next();
SOAPElement soapElement = (SOAPElement) nextSoapBodyElement
.getChildElements().next();
strmsg = soapElement.getValue();
System.out.println("AAA >>"+strmsg);
} catch (Exception wse) {
wse.printStackTrace();
return strmsg;
public static void main(String[] arg) {
wsClient ws = new wsClient();
Date date = new Date();
System.out.println(date.toGMTString());
System.out.println(ws.procWeb());
System.out.println(date.toGMTString());
* Servlet:
package hnx;
import java.io.IOException;
import java.io.PrintWriter;
import javax.servlet.*;
import javax.servlet.http.*;
import ws.GetData;
import ws.GetDataPortClient;
import ws.GetDataService;
public class getIndex extends HttpServlet {
private static final String CONTENT_TYPE = "text/html; charset=UTF-8";
public void init(ServletConfig config) throws ServletException {
super.init(config);
public void doPost(HttpServletRequest request,
HttpServletResponse response) throws ServletException,
IOException {
doGet(request, response);
public void doGet(HttpServletRequest request,
HttpServletResponse response) throws ServletException,
IOException {
response.reset();
response.flushBuffer();
response.setContentType(CONTENT_TYPE);
PrintWriter out = response.getWriter();
// GetDataService service = new GetDataService();
// GetData getData = service.getGetDataPort();
// String str = getData.getIndexData("HNX302");
// int length = str.length();
// response.setContentLength(length);
wsClient ws = new wsClient();
String str = ws.procWeb();
try {
out.println(str);
} catch (Exception e) {
e.printStackTrace();
out.close();
ERROR: >>>>>[Another instance of the application is running on the server. JDeveloper redeploy the application.]
[Application SClient stopped but not undeployed from Server Instance IntegratedWebLogicServer]
[Running application SClient on Server Instance IntegratedWebLogicServer...]
[03:41:48 PM] ---- Deployment started. ----
[03:41:48 PM] Target platform is (Weblogic 10.3).
[03:41:48 PM] Retrieving existing application information
[03:41:48 PM] Running dependency analysis...
[03:41:48 PM] Deploying 2 profiles...
[03:41:48 PM] Wrote Web Application Module to C:\Users\W7\AppData\Roaming\JDeveloper\system11.1.1.2.36.55.36\o.j2ee\drs\SClient\sgetDataWebApp.war
[03:41:48 PM] Wrote Enterprise Application Module to C:\Users\W7\AppData\Roaming\JDeveloper\system11.1.1.2.36.55.36\o.j2ee\drs\SClient
[03:41:49 PM] Redeploying Application...
[03:41:49 PM] Application Redeployed Successfully.
[03:41:49 PM] The following URL context root(s) were defined and can be used as a starting point to test your application:
[03:41:49 PM] http://192.168.9.100:7101/SClient
[03:41:49 PM] Elapsed time for deployment: 1 second
[03:41:49 PM] ---- Deployment finished. ----
Run startup time: 1380 ms.
[Application SClient deployed to Server Instance IntegratedWebLogicServer]
Target URL -- http://127.0.0.1:7101/SClient/getindex
[param: null]
javax.xml.ws.WebServiceException: com.ctc.wstx.exc.WstxIOException: Exceeding stated content length of 228
 at com.sun.xml.ws.encoding.StreamSOAPCodec.encode(StreamSOAPCodec.java:117)
 at com.sun.xml.ws.encoding.SOAPBindingCodec.encode(SOAPBindingCodec.java:258)
 at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:165)
 at com.sun.xml.ws.transport.http.client.HttpTransportPipe.processRequest(HttpTransportPipe.java:101)
 at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:604)
 at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:563)
 at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:548)
 at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:445)
 at com.sun.xml.ws.client.Stub.process(Stub.java:248)
 at com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:189)
 at com.sun.xml.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:215)
 at hnx.wsClient.procWeb(wsClient.java:75)
 at hnx.getIndex.doGet(getIndex.java:40)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 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:292)
 at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:326)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
 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:2202)
 at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
 at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: com.ctc.wstx.exc.WstxIOException: Exceeding stated content length of 228
 at com.ctc.wstx.sw.BaseStreamWriter.finishDocument(BaseStreamWriter.java:1687)
 at com.ctc.wstx.sw.BaseStreamWriter.writeEndDocument(BaseStreamWriter.java:585)
 at com.sun.xml.ws.message.saaj.SAAJMessage.writeTo(SAAJMessage.java:396)
 at com.sun.xml.ws.encoding.StreamSOAPCodec.encode(StreamSOAPCodec.java:114)
 ... 29 more
Caused by: java.net.ProtocolException: Exceeding stated content length of 228
 at weblogic.net.http.ContentLengthOutputStream.write(ContentLengthOutputStream.java:39)
 at com.ctc.wstx.io.UTF8Writer.flush(UTF8Writer.java:96)
 at com.ctc.wstx.sw.BufferingXmlWriter.flush(BufferingXmlWriter.java:214)
 at com.ctc.wstx.sw.BufferingXmlWriter.close(BufferingXmlWriter.java:194)
 at com.ctc.wstx.sw.BaseStreamWriter.finishDocument(BaseStreamWriter.java:1685)
 ... 32 more
java.lang.NullPointerException
 at hnx.wsClient.procWeb(wsClient.java:82)
 at hnx.getIndex.doGet(getIndex.java:40)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
 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:292)
 at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:326)
 at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
 at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
 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:2202)
 at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
 at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Can anyone help?
Thanks in advance.
LTThoi

I'm no webservices/servlet expert , but can you check the obvious out here -
javax.xml.ws.WebServiceException: com.ctc.wstx.exc.WstxIOException: Exceeding stated content length of 228
at ......
at hnx.wsClient.procWeb(wsClient.java:75)+ // check if you are passign something thats more than 228 chars
at hnx.getIndex.doGet(getIndex.java:40)

MSS - Business Event Details - Error Unexpected Exception when Calling RFC

Dear Experts,
Manager is getting the Error "Unexpected Exception when Calling RFC from Profile Application 'Business Event' when he tries to get the Training history of ONE employee in MSS. However, he is getting the details for the other employees of his department.
Any inputs on this?
Thank you.

I believe it is our custom iView that is incorrect.

When calling webservice Session event listener threw exception

Hi All,
I have Schdule the process to call webservice for 1 hour.
When it accessed It is throwing Exception But data send to Server and received response as true from webservice.
Exception details found in log file.
2007-12-04 01:00:36 StandardManager[npbpqa] Session event listener threw exception
java.lang.IllegalStateException: getAttribute: Session already invalidated
     at org.apache.catalina.session.StandardSession.getAttribute(StandardSession.java:925)
     at org.apache.catalina.session.StandardSessionFacade.getAttribute(StandardSessionFacade.java:124)
     at org.apache.axis.transport.http.AxisHTTPSessionListener.destroySession(AxisHTTPSessionListener.java:43)
     at org.apache.axis.transport.http.AxisHTTPSessionListener.sessionDestroyed(AxisHTTPSessionListener.java:72)
     at org.apache.catalina.session.StandardSession.expire(StandardSession.java:623)
     at org.apache.catalina.session.StandardSession.expire(StandardSession.java:572)
     at org.apache.catalina.session.StandardManager.processExpires(StandardManager.java:746)
     at org.apache.catalina.session.StandardManager.run(StandardManager.java:823)
     at java.lang.Thread.run(Thread.java:534)
Can any one help me urgently.
Thanks in advance.
Venkat K
Edited by: venkat2007 on Dec 4, 2007 2:44 PM

The service is working fine from a web page that my coworker did. I have not installed soap UI yet, but I used it at my last job. Since I posted this I have a new computer, have installed BizTalk Server 2013 R2 and Visual Studio 2013 Premium.
This is what I've done...
Created a new Host called BizTalkServerApplication64 with the '32-Bit only' unchecked.
Created a new host instance using the new host.
Created a new Send Handler for both Adapters 'WCF-BasicHttp' and 'WCF-Custom' using the new host.
configured both Send Ports (WCF-BasicHttp and WCF-Custom) to use the new send handler.
Have tried binding the logical port to both basic and the custom ports.
Now I get a different error which is:
Error Description: System.ServiceModel.CommunicationException: An error occurred while receiving the HTTP response to http://lbenson/MDSVC2/Service1.svc. This could be due to the service endpoint binding not using the HTTP protocol. This could also be due
to an HTTP request context being aborted by the server (possibly due to the service shutting down). See server logs for more details. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a receive. --->
System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host...
Any suggestions for this error? I'm not sure if this means I'm closer to getting it work or further.
Thanks for your help!
Jean
jRenae.s

Exception Message when calling WebService component

Hi,
We are using a Webservice component in our workflow. I want to know if there is a way to get the Exception message when an exception occurs in the Webservice call. We want to be able to handle the exception in the Livecycle layer and not the Flex layer.
When I draw a route from the Exception lightning bolt and select the type of Exception, it goes to the route when an exception occurs but I have not found a way to get the Exception message.
Does anyone know how to do that?
Thanks in Advance.
A

I'm using Linux in my server, and yes, my application is configured to run through an Http Proxy-server =)
When running the application on local, I included the Ip of my webservice in the proxy exceptions, so It wasn't blocked.
Maybe I have to remove the webService Ip from the exceptions, when running in the server.
I'll provide you with more details of my server as soon as the person in charge arrives.
But then, you think that exception is raised whenever the proxy or the application is blocking the webservice ip?
If that's so, I think I have a good track to keep searching.

Exception when calling SOAP Lookup-API async

Hello,
i'm calling a SOAP-Comunication Channel (Lookup-API) out of my MessageMapping. The WebService Called is asynchron because i just send some data and i don't care about the result. The WebService itselfs is implemented on our XI. In other words: we call us self.
In order to call my WebService asynchronous, i added &QualityOfService=ExactlyOnce at the end of the URL. The SOAP-Action is:
http://sap.com/xi/WebService/soap1.1
The problem is: the WebService works perfekt! But: in my mapping i get
nevertheless the following exception:
Errorcom.sap.aii.mapping.lookup.LookupException: Exception during processing the payload.Problem when calling an adapter by using communication channel SOAP_Receiver_SetIdocStatusAsync (Party: , Service: SetIdocStatus, Object ID: f6b1ce38e9fa332cba4eb1a6f0a3e17f) null com.sap.aii.mapping.lookup.LookupException: Problem when calling an adapter by using communication channel SOAP_Receiver_SetIdocStatusAsync (Party: , Service: SetIdocStatus, Object ID: f6b1ce38e9fa332cba4eb1a6f0a3e17f) null at com.sap.aii.ibrun.server.lookup.AdapterProxyLocal.process(AdapterProxyLocal.java:96) at com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.call(SystemAccessorInternal.java:47) at com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:141) at com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:74) at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169) at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:296) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:211) at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634) 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:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) 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) Root Cause: com.sap.aii.af.service.api.AFException at com.sap.aii.af.service.api.AdapterAccess.call(AdapterAccess.java:122) at com.sap.aii.ibrun.server.lookup.AdapterProxyLocal.process(AdapterProxyLocal.java:87) at com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.call(SystemAccessorInternal.java:47) at com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:141) at com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:74) at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169) at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:296) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:211) at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634) 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:401) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175) 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)

The problem is: i don't know how to check for the HTTP-Header, because
my call
SOAPOutPayload = accessor.call(payload);
throws the mentioned exception, even though it works behind the scene.
Is it possible to check for the HTTP-Response-Code in the catch block?
We want to avoid an synchronous scenario because we don't need the result and the WebService is rather slow.

Exception during call webservice from Web Dyn Pro application

I receive exception when execute call to webservice. I found place where it fall, it is in stub classmdp\company\wd\_comp\src\packages\com\accenture\mdp\company\model\companybasic\proxies\Config1BindingStub.java
in method below, in line
this.transportBinding.call(this.stubConfiguration,this.globalProtocols,_getOperationProtocols("filterCompany"));
public com.accenture.mdp.company.model.companybasic.proxies.types.p4.FilterCompanyResponse filterCompany(com.accenture.mdp.company.model.companybasic.proxies.types.p4.FilterCompany parameters) throws java.rmi.RemoteException,com.accenture.mdp.company.model.companybasic.proxies.Exception,com.accenture.mdp.company.model.companybasic.proxies.MDPException {
 try {
 super._beginLogFrame();
 // Operation input params initialization
 this.inputParams = new ServiceParam[1];
 this.inputParams[0] = new ServiceParam();
 this.inputParams[0].isElement = true;
 this.inputParams[0].schemaName = new QName("urn:CompanyServiceVi","filterCompany");
 this.inputParams[0].name = "parameters";
 this.inputParams[0].contentClass = com.accenture.mdp.company.model.companybasic.proxies.types.p4.FilterCompany.class;
 this.inputParams[0].content = parameters;
 // Operation output params initialization
 this.outputParams = new ServiceParam[1];
 this.outputParams[0] = new ServiceParam();
 this.outputParams[0].isElement = true;
 this.outputParams[0].schemaName = new QName("urn:CompanyServiceVi","filterCompanyResponse");
 this.outputParams[0].name = "parameters";
 this.outputParams[0].contentClass = com.accenture.mdp.company.model.companybasic.proxies.types.p4.FilterCompanyResponse.class;
 // Operation faults initialization
 this.faultParams = new ServiceParam[2];
 this.faultParams[0] = new ServiceParam();
 this.faultParams[0].isElement = true;
 this.faultParams[0].schemaName = new QName("urn:CompanyServiceWsd/CompanyServiceVi","filterCompany_java.lang.Exception");
 this.faultParams[0].name = "errorPart";
 this.faultParams[0].contentClass = com.accenture.mdp.company.model.companybasic.proxies.Exception.class;
 this.faultParams[1] = new ServiceParam();
 this.faultParams[1].isElement = true;
 this.faultParams[1].schemaName = new QName("urn:CompanyServiceWsd/CompanyServiceVi","filterCompany_com.accenture.mdp.common.exceptions.MDPException");
 this.faultParams[1].name = "errorPart";
 this.faultParams[1].contentClass = com.accenture.mdp.company.model.companybasic.proxies.MDPException.class;
 com.accenture.mdp.company.model.companybasic.proxies.types.p4.FilterCompanyResponse parametersTemp;
 this.transportBinding.setTypeMappingRegistry(this.typeRegistry);
 this.transportBinding.startOperation(this.inputParams,this.outputParams,this.faultParams);
 // Binding Context initialization
 this.bindingConfiguration.clear();
 bindingConfiguration.setProperty("soapAction","");
 bindingConfiguration.setProperty("style","document");
 bindingConfiguration.setProperty("transport","http://schemas.xmlsoap.org/soap/http");
 PropertyContext bindingConfigurationX;
 bindingConfigurationX = bindingConfiguration.getSubContext("output");
 bindingConfigurationX.setProperty("operationName","filterCompany");
 bindingConfigurationX.setProperty("use","literal");
 bindingConfigurationX = bindingConfiguration.getSubContext("input");
 bindingConfigurationX.setProperty("operationName","filterCompany");
 bindingConfigurationX.setProperty("use","literal");
 bindingConfigurationX.setProperty("parts","parameters");
 super._fillEndpoint(bindingConfiguration);
 _buildOperationContext("filterCompany",this.transportBinding);
 this.transportBinding.call(this.stubConfiguration,this.globalProtocols,_getOperationProtocols("filterCompany"));
 _setEndpoint((String) bindingConfiguration.getProperty(com.sap.engine.services.webservices.jaxrpc.wsdl2java.ClientTransportBinding.ENDPOINT));
 if (this.faultParams[0].content != null) {
 throw (com.accenture.mdp.company.model.companybasic.proxies.Exception) this.faultParams[0].content;
 if (this.faultParams[1].content != null) {
 throw (com.accenture.mdp.company.model.companybasic.proxies.MDPException) this.faultParams[1].content;
 parametersTemp = (com.accenture.mdp.company.model.companybasic.proxies.types.p4.FilterCompanyResponse) this.outputParams[0].content;
 return parametersTemp;
 } catch (com.accenture.mdp.company.model.companybasic.proxies.Exception e) {
 throw e;
 } catch (com.accenture.mdp.company.model.companybasic.proxies.MDPException e) {
 throw e;
 } catch (javax.xml.rpc.soap.SOAPFaultException e) {
 throw e;
 } catch (java.lang.Exception e) {
 throw new RemoteException("Service call exception",e);
 } finally {
 super._endLogFrame("filterCompany");
I receive Service call exception; nested exception is: java.lang.NullPointerException
May be anybody could suggest me how can I get more information about of reason of this exceprion ?
How to repair it ?

Check the following path in your server:
If you are using NW04s: :\usr\sap\<InstanceName>\JC00\j2ee\cluster\server0\log\
If you are using CE: :\usr\sap\<InstanceName>\J00\j2ee\cluster\server0\log.
If you are using CE: [Log Viewing with the SAP MC|http://help.sap.com/saphelp_nwce10/helpdata/en/44/f71b59e38e2462e10000000a1553f7/content.htm]
Bala

Netweaver throwing following exception when calling the ProductionOrder WS

Hi,
when calling the ProductionOrder web service I get the following exception from the system:
nested exception is: com.sap.engine.services.ts.exceptions.BaseSystemException: Exception ( SAP J2EE Engine JTA Transaction : [0ffffffaa60fffffffe00103e] ) in rollback.
The system was migrated from Netweaver CE 7.1 SP4 to SP5 before the error started to occur.
Any ideas how to fix this? Start/Stopping ME didn't do the trick.
Kind Regards,
Christoph Mertins

Yes the stack trace is:
System exception
[EXCEPTION]
javax.ejb.EJBException: nested exception is: com.sap.engine.services.ts.exceptions.BaseSystemException: Exception ( SAP J2EE Engine JTA Transaction : [0ffffffaa60fffffffe0013ffffffb6] ) in rollback.
com.sap.engine.services.ts.exceptions.BaseSystemException: Exception ( SAP J2EE Engine JTA Transaction : [0ffffffaa60fffffffe0013ffffffb6] ) in rollback.
at com.sap.engine.services.ts.jta.impl.TransactionImpl.rollback(TransactionImpl.java:921)
at com.sap.engine.services.ts.jta.impl.TransactionManagerImpl.rollback(TransactionManagerImpl.java:486)
at com.sap.engine.services.ejb3.runtime.impl.TransactionAttributeHandler$Required.error(TransactionAttributeHandler.java:296)
at com.sap.engine.services.ejb3.runtime.impl.TransactionAttributeHandler$TransactionAttributeErrorsHandler.error(TransactionAttributeHandler.java:130)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.doWorkWithAttribute(Interceptors_Transaction.java:40)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Transaction.invoke(Interceptors_Transaction.java:22)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at $Proxy3782.create(Unknown Source)
at com.sap.me.productdefinition.wserpimpl.productionOrder.ProductionOrderPersister.createOrUpdate(ProductionOrderPersister.java:133)
at com.sap.me.productdefinition.wserpimpl.GenericVOServiceImpl.createOrUpdate(GenericVOServiceImpl.java:57)
at com.sap.me.productdefinition.wserpimpl.productionOrder.ProductionOrderServiceHandlerAdapter.updateProductionOrder(ProductionOrderServiceHandlerAdapter.java:51)
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:592)
at com.visiprise.frame.proxy.DefaultInterceptor.intercept(DefaultInterceptor.java:31)
at com.visiprise.frame.proxy.InterceptorChain.process(InterceptorChain.java:48)
at com.visiprise.frame.proxy.ProxyContext.process(ProxyContext.java:67)
at com.visiprise.frame.proxy.AdviceInterceptor.intercept(AdviceInterceptor.java:45)
at com.visiprise.frame.proxy.InterceptorChain.process(InterceptorChain.java:48)
at com.visiprise.frame.proxy.GenericSOProxy.invoke(GenericSOProxy.java:81)
at $Proxy3884.updateProductionOrder(Unknown Source)
at com.sap.me.production.ws.ProductionOrderService.updateProductionOrder(ProductionOrderService.java:53)
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:592)
at com.sap.engine.services.webservices.runtime.JavaClassImplementationContainer.invokeMethod(JavaClassImplementationContainer.java:96)
at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process0(RuntimeProcessingEnvironment.java:525)
at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.preProcess(RuntimeProcessingEnvironment.java:494)
at com.sap.engine.services.webservices.espbase.server.runtime.RuntimeProcessingEnvironment.process(RuntimeProcessingEnvironment.java:260)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWOLogging(ServletDispatcherImpl.java:178)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPostWithLogging(ServletDispatcherImpl.java:114)
at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:72)
at com.sap.engine.services.webservices.servlet.SOAPServletExt.doPost(SOAPServletExt.java:90)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.runServlet(FilterChainImpl.java:162)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:81)
at com.sap.me.webservice.ClearServiceContextFilter.doFilter(ClearServiceContextFilter.java:28)
at com.sap.engine.services.servlets_jsp.server.runtime.FilterChainImpl.doFilter(FilterChainImpl.java:73)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:461)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:397)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:83)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:243)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247)
at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327)
Caused by: com.sap.engine.services.dbpool.exceptions.BaseResourceException: SQLException is thrown by the pooled connection: com.sap.sql.log.OpenSQLException: Connection object com.sap.sql.jdbc.vendor.VendorConnectionHandle@aa1bf8e has already been closed.
at com.sap.engine.services.dbpool.spi.LocalTXManagedConnectionImpl.throwBaseResourceException(LocalTXManagedConnectionImpl.java:89)
at com.sap.engine.services.dbpool.spi.LocalTXManagedConnectionImpl.rollback(LocalTXManagedConnectionImpl.java:389)
at com.sap.engine.services.ts.jta.impl.TransactionImpl.rollback(TransactionImpl.java:813)
... 83 more
Caused by: com.sap.sql.log.OpenSQLException: Connection object com.sap.sql.jdbc.vendor.VendorConnectionHandle@aa1bf8e has already been closed.
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:83)
at com.sap.sql.log.Syslog.createAndLogOpenSQLException(Syslog.java:122)
at com.sap.sql.jdbc.vendor.VendorConnectionHandle.validate(VendorConnectionHandle.java:383)
at com.sap.sql.jdbc.vendor.VendorConnectionHandle.setAutoCommit(VendorConnectionHandle.java:38)
at com.sap.engine.services.dbpool.spi.LocalTXManagedConnectionImpl.rollback(LocalTXManagedConnectionImpl.java:386)
... 84 more

Fault getting XML node when calling webservice

Please assist, I'm calling a webservice from SAP using a generated proxy and not going via XI. The webservice has 4 methods. Three of which make a successful call to the websrvice. When calling one of the methods, I get a SOAP fault. It does not say what the fault is.
On debugging I traced the fault to class CL_SOAP_MESSAGE_NEW method DESERIALIZE_HEADER_ NEW, at point " 4.1- ... and get method ". A method call is made to return the next XML node. This method executes a kernel module coded as "method IF_SXML_READER~NEXT_NODE
by kernel module fxkmsrd_next_node fail", and the method name returned is "FAULT", which then triggers a SOAP FAULT exception.
I do not know how to access this kernel module to trace the error. I need assitance in identifying why I'm getting a fault back. Please assist. Points will be awarded.
Maggie

Thanks for this hint, Amar. But this points directly to my next problem: How can I set this parameter. I know how to set flat parameters (e.g. of type long, boolean, etc.). But how can I set a parameter of a complex type?
For example I can call
wdContext.currentSaveElement().setIdFather(long id)
in order to set the parameter idFather of type long for the WebService-method save(). But there is no method
wdContext.currentSaveElement().setIdFather(SoftwareKomponenteDTO aKomp)
Could you please help me on more time?
Kind regards,
Christoph

Scripting API: Com exception when calling Session.Record

Hi,
I'm communicating with SAP Scripting API Com-Object from my Net application.
When the Scripting events are disable in server side (by setting sapgui/user_scripting_disable_recording=TRUE in the server profile see Note 692245) ans i try to set the GuiSession.Record property to true i recieve a COM exception.
System.Runtime.InteropServices.COMException (0x80010105): The server threw an exception. (Exception from HRESULT: 0x80010105 (RPC_E_SERVERFAULT))
at System.RuntimeType.ForwardCallToInvokeMember(String memberName, BindingFlags flags, Object target, Int32[] aWrapperTypes, MessageData& msgData)
at SAPFEWSELib.ISapSessionTarget.set_Record(Boolean )
My question is - is this is the expected behavior? (I wouldn't expect exception when mode is disabled).
Thanks,
Dror.

The problem is: i don't know how to check for the HTTP-Header, because
my call
SOAPOutPayload = accessor.call(payload);
throws the mentioned exception, even though it works behind the scene.
Is it possible to check for the HTTP-Response-Code in the catch block?
We want to avoid an synchronous scenario because we don't need the result and the WebService is rather slow.

NO_PERMISSION Exception when calling secured EJB-methods

In WL6.1, I have an Ejb with secured methods. The (Swing) client application accesses the Ejb through rmi-iiop using the JDK1.3.1 Orb.
Unfortunately, it seems that the caller identity (which was supplied in the InitialContext lookup) is not propagated
to the server: any call to a secured method
fails with a CORBA NO_PERMISSION Exception.
Non secured methods work fine.
Using the t3 protocol the program also works fine, but that would require
the 25Mb weblogic.jar on all clients,
which is unattainable for us.
Any ideas how this situation can be corrected?
-Allard Siemelink

I am still getting the NO_PERMISSION Exception when using "weblogic.jndi.WLInitialContextFactory".
We use Sun's JRE, version 1.3.1_01.
Am I forgetting something?
My code is as follows:
InitialContext context = null;
try {
Hashtable ht = new Hashtable();
ht.put(InitialContext.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory");
ht.put(InitialContext.PROVIDER_URL, "iiop://localhost:80");
ht.put(InitialContext.SECURITY_PRINCIPAL, "system");
ht.put(InitialContext.SECURITY_CREDENTIALS, "system_password");
context = new InitialContext(ht);
Object objHome = context.lookup(EJB_NAME);
MyHome myHome = (MyHome)PortableRemoteObject.narrow(objHome, MyHome.class);
MyRemote myRemote = myHome.create();
//NEXT LINE Crashes when method is secured:
myRemote.securedMethod();
finally {
if (context!=null) context.close();
Andy Piper <[email protected]> wrote:
Allard Siemelink <[email protected]> writes:
In WL6.1, I have an Ejb with secured methods. The (Swing) client applicationaccesses the Ejb through rmi-iiop using the JDK1.3.1 Orb.
Unfortunately, it seems that the caller identity (which was suppliedin the InitialContext lookup) is not propagated
to the server: any call to a secured method
fails with a CORBA NO_PERMISSION Exception.Make sure you are using WLInitialContextFactory and not
CNCtxFactory. Only the former will give you security.
andy

Invalid URL Exception while opening a file using external window in webdynp

I am trying open an URL ythru external window on click of button in my webdynpro.
This is the URl I am trying to open
File://mww/Documents/Attachments/2008/10/56254/{FD803B0D-157F-47F9-A5A8-C687E1DC6B96}_break.JPG
if I try to open from a from the browser it works fine but thru webdynpro it is throwing the error.
mww is another system where the file is residing.
But I am using the same techniue in other component where I am able to open file from an external window.
File://mww/Documents/Attachments/2008/10/56254/some.jpg
The only difference in the URL is {FD803B0D-157F-47F9-A5A8-C687E1DC6B96}Since this URL is generated by another system I do not have any other aletrnative but I have live with this URL.
can some body please give some idea how to fix this
if I use java.net.URLEncoder.encode() then I am not getting any error , buit file is not opening in the browser( external window)
below is the error stack I am getting.
com.sap.tc.webdynpro.services.exceptions.InvalidUrlRuntimeException: Invalid URL=File://mww/Documents/Attachments/2008/10/56254/{FD803B0D-157F-47F9-A5A8-C687E1DC6B96}_break.JPG
at com.sap.tc.webdynpro.serverimpl.core.url.AbstractURLGenerator.checkURL(AbstractURLGenerator.java:699)
at com.sap.tc.webdynpro.services.sal.url.core.URLGeneratorInternal.checkURL(URLGeneratorInternal.java:390)
at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.createNonModalExternalWindow(ClientComponent.java:1037)
at com.gis.dcww.findsrch.AttachmentView.onActionOpen_Attachement(AttachmentView.java:179)
at com.gis.dcww.findsrch.wdp.InternalAttachmentView.wdInvokeEventHandler(InternalAttachmentView.java:203)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:321)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
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:401)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)
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:102)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
thanks
PK

Hi Armin, Josue
Thanks for the reply
Please note I am able to open an external window( browser ) thru my code with "File" protocol.
I have no issue opening an external window or using File protocol.
I am able to open an image/doc with a normal URL as follows
File://mww/documents/image.jpg
or
File://mww/document/temp.csv
But My URL has some system( thru Other applications ) generated charaters in it , I need get the path from DB( which I have done ) and pass this URL to the ExternalNonModalWindow as paramter.
MY code is opening successfully the external window for any URL .
but for URL which has these character { } is throwing the invalid URL error
for the below URL, I am getting the error
File://mww/Documents/Attachments/2008/10/56254/{FD803B0D-157F-47F9-A5A8-C687E1DC6B96}_break.JPG
thanks
PK
because of the flower bracket it is throwing the error.
thansk
PK

Invalid URL error when displaying Work Item Attached URL Object in UWL

Hi,
After upgraded from EP6 to EP7 the user can no longer display the attached URL object of work items in the UWL Inbox. It works fine in the SAPGUI Inbox so the URL should be okay. We found below error messages in UWL log file:
#1.5#0003BA5D298B001E0000030300003A280004314BFE992222#1180102370599#/uwl/ui#sap.com/tcwddispwda#com.sap.netweaver.bc.uwl.ui.control.UWLActionControl#C004049#43497#####SAPEngine_Application_Thread[impl:3]_0##0#0#Warning#1#com.sap.netweaver.bc.uwl.ui.control.UWLActionControl#Plain###com.sap.tc.webdynpro.services.exceptions.InvalidUrlRuntimeException: Invalid URL=HTTP://apinvoice.d51.lilly.com
gbip
gbip.asp?po=invoice=TC630400360USERID=USC076601#
#1.5#0003BA5D298B001E0000030400003A280004314BFE9986AB#1180102370625#/uwl/ui#sap.com/tcwddispwda#com.sap.netweaver.bc.uwl.ui.control.UWLActionControl#C004049#43497#####SAPEngine_Application_Thread[impl:3]_0##0#0#Warning#1#com.sap.netweaver.bc.uwl.ui.control.UWLActionControl#Plain###com.sap.netweaver.bc.uwl.UWLException: Fri May 25 10:12:50 EDT 2007
(Portal) :com.sap.tc.webdynpro.services.exceptions.InvalidUrlRuntimeException:Invalid URL=HTTP://apinvoice.d51.lilly.com
gbip
gbip.asp?po=invoice=TC630400360USERID=USC076601#
Looks like the error is related to the back slashes in the URL but it was working fine in EP6. We are going to change the back slashes to forward slashes to see it will work. We would like to know if any SDNers can provide some more detail on why this is happening and if there is other solution. Any hint will be very appreciated.
Regards,
Jiannan Che

Use link attachment or add button action to UWL as possible workaround. It appears that work item text can only be displayed as-is.

Invalid URL screen when accessing Facebook

When I am in Facebook, and go to another screen, or just trying to access it in general, I will regularly get the following"
Invalid URL
The requested URL "/", is invalid.
Reference #9.5efd4317.1351252290.10b247da
Or that I am going to an Untrusted Connection.
Sometimes I have to reboot 3 or 4 times, even after clearing out the history, cache, etc...
Why is this happening?

Launch Terminal from your Utilities folder. Copy/Paste the following:
sudo killall -HUP mDNSResponder
Hit enter, you'll be asked for your Admin password, it will not appear on the screen as you type it.

Invalid url exception when calling webservice

Similar Messages

Maybe you are looking for