on 10-02-2007 3:46 PM
Hi all,
running some tests checking some Xi interfaces we have the following problem :
going to Runtime Workbench --> Component Monitoring --> Adapter Engine e clicking on the Tab "Test Message" we insert Service, Interface, Namespace, Quality of Service, user and password
On "send message to" we insert the string:
http://apl06gjbx:8031/XISOAPAdapter/MessageServlet?channel=:BSY_CDFS_CRISP_DX8:CC_SOAP_IF_KE_02_In
Executing "Send Message", we get the following error :
"error while sending message : 501 not implemented"
Any suggestion ?
thanks in advance
Hi,
>>The Error- 501
The server does not support the functionality required to fulfill the request. This is the appropriate response when the server does not recognize the request method and is not capable of supporting it for any resource.
Regards
Agasthuri Doss
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
your help was very appreciated
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi dear all,
problem solved with J2EE port 53100, XML in SOAP format and QoS Exactly Once
thanks a lot everybody !
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Peter,
yes the channel monitoring is green.
I send the message to the following address ( I tried also with the IP address)
http://apl06gjbx:53100/XISOAPAdapter/MessageServlet?channel=:BSY_CDFS_CRISP_DX8:CC_SOAP_IF_KE_02_In
thanks a lot.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi all,
using a 53100 port and xml code in payload it seems better but we get the following error:
com.sap.engine.services.servlets_jsp.server.exceptions.WebServletException: Error in dispatching request to servlet [/sub/componentmonitoringpageprocessor].
Display Stack Trace
com.sap.engine.services.servlets_jsp.server.exceptions.WebServletException: Error in dispatching request to servlet [/sub/componentmonitoringpageprocessor].
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:328)
at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
at jsp_FC_Secure1185456171353._jspService(jsp_FC_Secure1185456171353.java:24)
at com.sap.engine.services.servlets_jsp.server.jsp.JspBase.service(JspBase.java:112)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:544)
at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:186)
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(AccessController.java:215)
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.NullPointerException
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmDynPage.doProcessAfterInput(CmDynPage.java:60)
at com.sapportals.htmlb.page.PageProcessor.handleRequest(PageProcessor.java:101)
at com.sapportals.htmlb.page.PageProcessorServlet.handleRequest(PageProcessorServlet.java:62)
at com.sapportals.htmlb.page.PageProcessorServlet.doPost(PageProcessorServlet.java:22)
at com.sap.aii.rwb.web.componentmonitoring.viewcontroller.CmPageProcessor.doPost(CmPageProcessor.java:35)
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.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
... 20 more
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
can you see any message in SXMB_MONI for the outbound interface ?
if not I think its is not even calling the outbound interface.
how did you create the WSDL file for the outbound interface(cos SOAP sender) and make sure you dont use the default URL the system gives there,use the URL you have given in the prevoius message but with J2EE port.
and also we need to make sure we are sending appropriate request(sensible payload).
check the QOS = BE(Sync integration)
Check ,the parameters are exact in the URL and in your developed object in IR & ID.
Do you also put XML message to be sent into the textarea box? The Payload box..
Since you're using SOAP adapter, it MUST be of course in SOAP format.
Stupid question, but you didn't describe it.. Maybe this is the problem..
Peter
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you are using sender SOAP adapter use J2EE port not HTTP port.
it should be ok now.try with J2EE port.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
76 | |
9 | |
8 | |
7 | |
6 | |
5 | |
5 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.