Xi 3.0: Mail adapter fails with "exception in method process"

Hi.
I configured the dynamic address for mail adapter following the fantastic-as-always weblog from michalgh.
Althou everything seems to work fine (that is, i send correctly the email message) the A.F. returns an error with "exception in method process".
I tried both async and sync case with the same result. In the sync case, the response contains:

<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="PARSING">GENERAL</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: Exception in method process.</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Any idea???

Yes. There is also a response message in the imported structure.. it seems it should work as a kind of application ack with some info on the server that processed the mail.
Anyway, in my server i get a 404 for the link you suggested.
In the async case i don't get any error on the SXMB_MONI but only on the A.F.
I attach the audit log for the async case:
Audit Log for Message: ffb28585-3c53-0f4b-b366-7dd7a00513fc
Time Stamp Status Thread ID Sequence No. Description
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_45 1118608026046 The message was successfully received by the messaging system. Profile: XI URL: http://CAPELAB010:50000/MessagingSystem/receive/AFW/XI
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_45 1118608026062 Using connection AFW. Trying to put the message into the receive queue.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026093 The message was successfully retrieved from the receive queue.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026375 The message status set to DLNG.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026468 Delivering to channel: MAIL_RECV
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026468 Mail: message entering the adapter
2005-06-12 22:27:06 Error SAPEngine_Application_Thread[impl:3]_34 1118608026828 Exception caught by adapter framework: Failed to call the endpoint
2005-06-12 22:27:06 Error SAPEngine_Application_Thread[impl:3]_34 1118608026828 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026843 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:32:06 CEST 2005.
2005-06-12 22:27:06 Success SAPEngine_Application_Thread[impl:3]_34 1118608026859 The message status set to WAIT.
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327109 The message was successfully retrieved from the receive queue.
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327125 The message status set to DLNG.
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327156 Delivering to channel: MAIL_RECV
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327171 Mail: message entering the adapter
2005-06-12 22:32:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608327250 Exception caught by adapter framework: Failed to call the endpoint
2005-06-12 22:32:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608327250 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint .
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327281 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:37:07 CEST 2005.
2005-06-12 22:32:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608327296 The message status set to WAIT.
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627421 The message was successfully retrieved from the receive queue.
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627437 The message status set to DLNG.
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627546 Delivering to channel: MAIL_RECV
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627562 Mail: message entering the adapter
2005-06-12 22:37:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608627671 Exception caught by adapter framework: Failed to call the endpoint
2005-06-12 22:37:07 Error SAPEngine_Application_Thread[impl:3]_34 1118608627671 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint .
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627703 The asynchronous message was successfully scheduled to be delivered at Sun Jun 12 22:42:07 CEST 2005.
2005-06-12 22:37:07 Success SAPEngine_Application_Thread[impl:3]_34 1118608627734 The message status set to WAIT.
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927734 The message was successfully retrieved from the receive queue.
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927734 The message status set to DLNG.
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927750 Delivering to channel: MAIL_RECV
2005-06-12 22:42:07 Success SAPEngine_Application_Thread[impl:3]_40 1118608927750 Mail: message entering the adapter
2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927765 Exception caught by adapter framework: Failed to call the endpoint
2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927781 Delivery of the message to the application using connection AFW failed, due to: Failed to call the endpoint .
2005-06-12 22:42:07 Error SAPEngine_Application_Thread[impl:3]_40 1118608927796 The message status set to NDLV.
Total: 33 Entries 1020304050 messages displayed per page; this is page 1 of 1 page(s)

Similar Messages

Attempt to process file failed with Exception in XML Parser-format problem

Hi all,
Iam getting an unusual error in the J2EE stack in XI.
And the message is:
006-11-30 17:31:07 Error Attempt to process file failed with Exception in XML Parser (format problem?):'com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Invalid char #0xf(:main:, row:1, col:1044002)(:main:, row=1, col=1044002) -> com.sap.engine.lib.xml.parser.ParserException: Invalid char #0xf(:main:, row:1, col:1044002)' 2006-11-30 17:31:07 Error Exception caught by adapter framework: null 2006-11-30 17:31:07 Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
My scenerio iam posting IDOC to a flat file with content conversion in the receiver side,the mapping got executed successfully and in the audit log i found that the error was after the 'Start converting XML document content to plain text'.
This means that error occured during content conversion of XML to the prescribed file format.
Can anyone suggest any better approach using which we may trace the junk data in IDoc. Manual adhoc approach could take time and is error prone.
Thanks in advance...
karun

Hi Bhavesh,
Thanks for the early reply. I checked the mapping and everything is fine and the output is also in valid XML format.
The audit log shows that the mapping got executed successfully and the error is after the step 'Start converting XML document content to plain text '. Is there any constraint in the file adapter regarding the message size for parsing.
2006-11-30 17:30:50 Success Transfer: "BIN" mode, size 2912595 bytes, character encoding -
2006-11-30 17:30:50 Success Start converting XML document content to plain text
2006-11-30 17:31:07 Error Attempt to process file failed with Exception in XML Parser (format problem?):'com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: Invalid char #0xf(:main:, row:1, col:1044002)(:main:, row=1, col=1044002) -> com.sap.engine.lib.xml.parser.ParserException: Invalid char #0xf(:main:, row:1, col:1044002)'
2006-11-30 17:31:07 Error Exception caught by adapter framework: null
2006-11-30 17:31:07 Error Delivery of the message to the application using connection AFW failed, due to: RecoverableException.
2006-11-30 17:31:07 Success The asynchronous message was successfully scheduled to be delivered at Thu Nov 30 17:36:07 GMT 2006.
2006-11-30 17:31:07 Success The message status set to WAIT.
2006-11-30 17:31:08 Success Acknowledgement creation triggered for type: SystemErrorAck
2006-11-30 17:31:08 Success Acknowledgement sent successfully for type: SystemErrorAck
2006-11-30 17:36:08 Success Retrying to deliver message to the application. Retry: 1

Approval task SP09: Evaluation of approvalid failed with Exception: while trying to invoke the method java.lang.String.length() of an object loaded from local variable 'aValue'

Hi everyone,
I just installed SP09 and i was testing the solution. And I found a problem with the approvals tasks.
I configured a simple ROLE approval task for validate add event. And when the runtime executes the task, the dispatcher log shows a error:
ERROR: Evaluation of approvalid failed with Exception: while trying to invoke the method java.lang.String.length() of an object loaded from local variable 'aValue'
And the notifications configured on approval task does not start either.
The approval goes to the ToDO tab of the approver, but when approved, also the ROLE stays in "Pending" State.
I downgraded the Runtime components to SP08 to test, and the approvals tasks works correctly.
Has anyone passed trough this situation in SP09?
I think there is an issue with the runtime components delivered with this initial package of SP09.
Suggestions?

Hi Kelvin,2016081
The issue is caused by a program error in the Dispatcher component. A fix will be provided in Identity Management SP9 Patch 2 for the Runtime component. I expect the patch will be delivered within a week or two.
For more info about the issue and the patch please refer to SAPNote 2016081.
@Michael Penn - I might be able to assist if you provide the ticket number
Cheers,
Kristiyan
IdM Development

Servlet failed with Exception

I have a servlet that read Swing Applet input stream. It works on my JBuilder6 with HTML very fine. But It can't work on browser(such as IE). I have error message: Please someone help me!
Mon May 19 10:00:28 EDT 2003:<E> <ServletContext-General> Servlet failed with Exception
java.net.SocketException: Connection aborted by peer: socket write error
at java.net.SocketOutputStream.socketWrite(Native Method)
at java.net.SocketOutputStream.write(SocketOutputStream.java:83)
at weblogic.servlet.internal.ChunkUtils.writeChunks(ChunkUtils.java:88)
at weblogic.servlet.internal.ServletOutputStreamImpl.flush(ServletOutputStreamImpl.java:121)
at weblogic.servlet.internal.ServletOutputStreamImpl.writeStream(ServletOutputStreamImpl.jav
a:444)
at weblogic.servlet.ClasspathServlet.sendResource(ClasspathServlet.java:114)
at weblogic.servlet.ClasspathServlet.doGet(ClasspathServlet.java:87)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:865)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:105)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:742)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:686)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:
247)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:361)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Mon May 19 10:00:28 EDT 2003:<E> <HTTP> Servlet request terminated with IOException:
java.net.ProtocolException: Didn't meet stated Content-Length, wrote: '4096' bytes instead of stated
: '16093' bytes.
at weblogic.servlet.internal.ServletOutputStreamImpl.finish(ServletOutputStreamImpl.java:372
at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:
249)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:361)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

Hi, did you get any solution for the protocol exception? I have the same problem too....
Thanks
Suresh

Servlet failed with Exception java.lang.LinkageError: Class javax/servlet/ServletConfig

          Hi
          I registered a web app with Weblogic 5.1 in the weblogic.properties file. I try
          to run the web app from my browser typing http://localhost:7001/xxx(Webapp name)
          and a jsp page. Following is the error I get. It would be helpful if some one
          could point me to a fix for this problem
          Tue May 01 13:56:41 CDT 2001:<I> <ServletContext-omxclient> Generated java file:
          D:\weblogic\myserver\omxclient\_tmp_war\jsp_servlet\_omx\_login.java
          Tue May 01 13:56:43 CDT 2001:<E> <ServletContext-omxclient> Servlet failed with
          Exception
          java.lang.LinkageError: Class javax/servlet/ServletConfig violates loader constr
          aints
          at jsp_servlet._omx._login._jspService(_login.java:59)
          at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
          at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
          pl.java:105)
          at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
          pl.java:123)
          at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletCon
          textImpl.java:742)
          at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletCon
          textImpl.java:686)
          at weblogic.servlet.internal.ServletContextManager.invokeServlet(Servlet
          ContextManager.java:247)
          at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
          a:361)
          at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)


          Sorry, I didn't look very closely - the exception is for
          javax.servlet.ServletConfig - should be in weblogicaux.jar.
          Is there anything wrong with it? What service pack are you
          using? Could be a problem with weblogic.policy.
          mike
          >>java.lang.LinkageError: Class javax/servlet/ServletConfig
          "KC" <[email protected]> wrote:
          >
          >Hi Mike
          >The login.jsp page just contains a javascript function and two text boxes
          >in it.
          >Will try making changing it. If that is not the issue could you let me
          >know of
          >any other issues.
          >
          >"mreiche" <[email protected]> wrote:
          >>
          >>I would guess that login.jsp is a very large JSP and that
          >>the generated service method is too large for the classloader's
          >>liking. Try making it smaller.
          >>
          >>Mike
          >>
          >>
          >>"KC" <[email protected]> wrote:
          >>>
          >>>Hi
          >>>I registered a web app with Weblogic 5.1 in the weblogic.properties
          >>file.
          >>>I try
          >>>to run the web app from my browser typing http://localhost:7001/xxx(Webapp
          >>>name)
          >>>and a jsp page. Following is the error I get. It would be helpful if
          >>>some one
          >>>could point me to a fix for this problem
          >>>
          >>>Tue May 01 13:56:41 CDT 2001:<I> <ServletContext-omxclient> Generated
          >>>java file:
          >>> D:\weblogic\myserver\omxclient\_tmp_war\jsp_servlet\_omx\_login.java
          >>>Tue May 01 13:56:43 CDT 2001:<E> <ServletContext-omxclient> Servlet
          >>failed
          >>>with
          >>>Exception
          >>>java.lang.LinkageError: Class javax/servlet/ServletConfig violates
          >loader
          >>>constr
          >>>aints
          >>> at jsp_servlet._omx._login._jspService(_login.java:59)
          >>> at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
          >>> at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
          >>>pl.java:105)
          >>> at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
          >>>pl.java:123)
          >>> at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletCon
          >>>textImpl.java:742)
          >>> at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletCon
          >>>textImpl.java:686)
          >>> at weblogic.servlet.internal.ServletContextManager.invokeServlet(Servlet
          >>>ContextManager.java:247)
          >>> at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.jav
          >>>a:361)
          >>> at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:261)
          >>>
          >>> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >>>
          >>>
          >>
          >

Servlet failed with Exception java.lang.IllegalStateException: Response already committed

Hi,
can someone help with this issue. I've been getting this error in my logs since for the past 3 days and I don't know how to resolve it.
os-aix-64 bit
wls:10.3
####<Aug 25, 2014 11:36:18 AM GMT+05:30> <Error> <HTTP> <XXX-XXXXXX-XX> <examplesServer> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1408946778196> <BEA-101020> <[weblogic.servlet.internal.WebAppServletContext@2ee12ee1 - appName: 'consoleapp', name: 'console', context-path: '/console', spec-version: '2.5'] Servlet failed with Exception
java.lang.IllegalStateException: Response already committed
        at weblogic.servlet.internal.ServletResponseImpl.objectIfCommitted(ServletResponseImpl.java:1553)
        at weblogic.servlet.internal.ServletResponseImpl.sendRedirect(ServletResponseImpl.java:838)
        at javax.servlet.http.HttpServletResponseWrapper.sendRedirect(HttpServletResponseWrapper.java:136)
        at com.bea.netuix.nf.HttpServletResponseWrapper.sendRedirect(HttpServletResponseWrapper.java:50)
        at com.bea.netuix.servlets.controls.content.NetuiContent.handleRedirect(NetuiContent.java:234)
        at com.bea.netuix.servlets.controls.content.NetuiContent.handlePreRenderResponseState(NetuiContent.java:630)
        at com.bea.netuix.servlets.controls.content.StrutsContent.handlePreRenderResponseState(StrutsContent.java:224)
        at com.bea.netuix.servlets.controls.content.NetuiContent.preRender(NetuiContent.java:310)
        at com.bea.netuix.nf.ControlLifecycle$6.visit(ControlLifecycle.java:428)
        at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:727)
        at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
        at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
        at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
        at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
        at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
        at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
        at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
        at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
        at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
        at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
        at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
        at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
        at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
        at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
        at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
        at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
        at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
        at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
        at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:146)
        at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
        at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
        at com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:208)
        at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:162)
        at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:388)
        at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258)
        at com.bea.netuix.servlets.manager.UIServlet.doGet(UIServlet.java:211)
        at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:196)
        at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:251)
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
        at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.service(MBeanUtilsInitSingleFileServlet.java:54)
        at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:130)
        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:42)
        at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
        at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3496)
        at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
        at weblogic.security.service.SecurityManager.runAs(Unknown Source)
        at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
        at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
        at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
        at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
        at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
TIA,
Vamsi

Can someone please help me with this issue.

Add-on 9000005 failed with exception; Event Type: 1

Hi Experts,
I am woking on a project which uses DI API and creates AP Invoice by reading an excel file.
I used all the invoice in one sap transaction.
I read excel line by line and create one AP Invoice per line. It works when excel is having less then 500 records. But if there are more then 500 records or more then 600 records, it give following error to me
Add-on 9000005 failed with exception; Event Type: 1
Can anyone help me in it?
Thanks!!
Ritu

Hi,
I'm sure there is a limit to the number of rows you can add to an Invoice but I think it's probably limited on memory rather than a fixed limit on the number of rows. This might be an out of memory error that's causing the exception. Have you tried putting a try/catch around your code to see what the exact details are of the exception? Also, if you are filling in any text fields on the invoice (remarks), they are limited to 30K.
David

Add-on 9000035 failed with exception; Event Type: 32

In loadscreen function i have load the XML form but it shows the error like
"Add-on 9000035 failed with exception; Event Type: 32"
But i will connect to some other db means its working .
Share your ideas for what is the problem to load the screen in particular DB
Thanks,
Helen. S

Hi,
You may check this: Add-on 9000002 failed with exception; Event Type: 32
Thanks,
Gordon

Addon 9000000X failed with exception; Event type X

Hi SDK experts,
We had a problem with occurrence intermittent, something that we identified with relation on wait of response of event.
The problem is:
My addon need to submit XML files to some webservices. In some cases this files will be send on batches, what causes the response time to events on addon is to much large.
In this cases, when the response time is much large, the B1 overthrow the addon.
In compiled mode the message is not shown. This evidence was achieved on debug time.
The error message is "Addon 90000002 failed with exception; Event type 6"
The paleative solution was implement a thread to release the event. But threads on addons can be a problem.
What the opinions?
We need a solutions. Our addon is a market product for process accounting and fiscal.
regards.
Daniel Weissmann

Hi,
You may check this thread first:
Addon Crashes
Thanks,
Gordon

Servlet failed with Exception java.lang.OutOfMemoryError: PermGen space

Hello,
I recently installed BI Apps 11.1.1.7.1 on Oracle Linux 64.
while i am trying to run the full load i.e. SDE, SILOS and PLP and sometimes while trying to access BIA Configuration Manager..I get below error. while i tried to increase the heap size to 2gb in SetOBIDomain.sh for both bi_server1 and odi_sever1.sh, it is not really affected i.e. i dont see the updated arguments while trying to re start these managed servers. i tried to restart the box and it still did not work...Any idea on where exactly to change/update the parameters to increase the heap size and any other known issues cauing out of memory issues.
<Sep 30, 2013 11:55:44 AM EDT> <Error> <HTTP> <BEA-101020> <[ServletContext@263264514[app:oracle.biacm module:biacm path:/biacm spec-version:2.5 version:11.1.1.7.1]] Servlet failed with Exception
java.lang.OutOfMemoryError: PermGen space
Thank You in advance
Rakesh

Hi Fabian,
It seems that you have got out of memory due to PermGen space, hence increase the MaxPermGen space
java.lang.OutOfMemoryError: PermGen space
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632)
at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
Also you can go through the below posts to get more details about JVM architecture and more details about Out of memory
Topic: Parts Of JVM And JVM Architecture Diagram?
http://middlewaremagic.com/weblogic/?p=4456
Topic: OutOfMemory Causes and First Aid Steps?
http://middlewaremagic.com/weblogic/?p=4464
Regards,
Ravish Mody
http://middlewaremagic.com/weblogic/
Come, Join Us and Experience The Magic…

Getting error Servlet failed with Exception java.lang.IllegalStateException

Hi
I am getting this error throughout the server when i am trying to download a pdf from that page.
Im attaching the error console
2011 5:10:26 PM CEST> <Error> <HTTP> <aczocc08x.vfcz.dc-ratingen.de> <ShopSrv1_1_pre> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1306163426535> <BEA-101020> <[weblogic.servlet.internal.WebAppServletContext@172d19e - appName: 'OCC', name: '/shop', context-path: '/shop'] Servlet failed with Exception
java.lang.IllegalStateException: Cannot resize buffer - 76438 bytes have already been written (Servlet 2.3, sec. 5.1)
     at weblogic.servlet.internal.ServletResponseImpl.setBufferSize(ServletResponseImpl.java:338)
     at weblogic.servlet.jsp.PageContextImpl.initialize(PageContextImpl.java:74)
     at weblogic.servlet.jsp.PageContextImpl.<init>(PageContextImpl.java:110)
     at weblogic.servlet.jsp.JspFactoryImpl.getPageContext(JspFactoryImpl.java:40)
     at jsp_servlet._checkout._order.__cart_thank_45_you._jspService(__cart_thank_45_you.java:644)
     at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:226)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:124)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:283)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
     at vodafone.servlet.security.HttpsEnforcingFilter.doFilter(HttpsEnforcingFilter.java:39)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
     at atg.servlet.pipeline.TailPipelineServlet.service(TailPipelineServlet.java:90)
     at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:116)
     at atg.servlet.pipeline.DispatcherPipelineServletImpl.service(DispatcherPipelineServletImpl.java:202)
     at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:116)
     at atg.servlet.pipeline.PipelineableServletImpl.service(PipelineableServletImpl.java:279)
     at vodafone.dynamo.servlet.LocaleRedirector.service(LocaleRedirector.java:75)
     at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:116)
     at atg.servlet.pipeline.PipelineableServletImpl.service(PipelineableServletImpl.java:279)
     at atg.servlet.dafpipeline.RecordingServlet.service(RecordingServlet.java:280)
     at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:116)
     at atg.servlet.http.CookieBufferServlet.service(CookieBufferServlet.java:97)
     at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:116)
     at atg.userprofiling.ExpiredPasswordServlet.service(ExpiredPasswordServlet.java:356)
     at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:116)
     at atg.servlet.pipeline.MimeTyperPipelineServlet.service(MimeTyperPipelineServlet.java:206)
     at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:116)
     at atg.droplet.DropletEventServlet.service(DropletEventServlet.java:565)
     at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:116)
     at atg.servlet.sessionsaver.SessionSaverServlet.service(SessionSaverServlet.java:2442)
     at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:116)
     at atg.commerce.order.CommerceCommandServlet.service(CommerceCommandServlet.java:128)
     at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:116)
     at atg.commerce.promotion.PromotionServlet.service(PromotionServlet.java:191)
     at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:116)
     at atg.userprofiling.AccessControlServlet.service(AccessControlServlet.java:602)
     at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:116)
     at atg.userprofiling.PageEventTriggerPipelineServlet.service(PageEventTriggerPipelineServlet.java:169)
     at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:116)
     at atg.userprofiling.SessionEventTrigger.service(SessionEventTrigger.java:461)
     at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:116)
     at vodafone.servlets.ServletHelper.service(ServletHelper.java:34)
     at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:116)
     at vodafone.dynamo.servlet.DefaultCatalogFixer.service(DefaultCatalogFixer.java:54)
     at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:116)
     at atg.commerce.profile.VodafoneSSOProfileRequestServlet.service(VodafoneSSOProfileRequestServlet.java:231)
     at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:116)
     at atg.userprofiling.ProfileRequestServlet.service(ProfileRequestServlet.java:480)
     at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:116)
     at vodafone.session.SessionSynchronizationServlet.service(SessionSynchronizationServlet.java:38)
     at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:116)
     at atg.servlet.pipeline.DynamoPipelineServlet.service(DynamoPipelineServlet.java:469)
     at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:116)
     at atg.servlet.pipeline.PathAuthenticationPipelineServlet.service(PathAuthenticationPipelineServlet.java:370)
     at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:116)
     at atg.userprofiling.sso.PassportServlet.service(PassportServlet.java:561)
     at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:116)
     at atg.servlet.security.ThreadUserBinderServlet.service(ThreadUserBinderServlet.java:91)
     at atg.servlet.pipeline.PipelineableServletImpl.passRequest(PipelineableServletImpl.java:116)
     at atg.servlet.pipeline.HeadPipelineServlet.passRequest(HeadPipelineServlet.java:1100)
     at atg.servlet.pipeline.HeadPipelineServlet.service(HeadPipelineServlet.java:782)
     at atg.servlet.pipeline.PipelineableServletImpl.service(PipelineableServletImpl.java:231)
     at atg.filter.dspjsp.PageFilter.doFilter(Unknown Source)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3393)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2140)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2046)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1366)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
>
Anyone has any idea or faced this issue before please guide me what is the cause, i have got a feeling that this may be because server has run out of memory.

i havn't written anything before calling set buiffer sizeSo why does the exception message say the opposite?
I can see that error may be because of a jsp named cart_thank-you.jspSo can I. So have a look at it. It is writing something before the other thing is calling setBufferSize().
you can see that in erro logSo can you.

Add-on 9000034 failed with exception; in blocking expire date batch in GR

Hi all ,
I try to set mandotory in expire date field in batch setup of good receipt. My code is like this
If (pVal.FormTypeEx = "41") Then
            oForm = SBO_Application.Forms.Item(FormUID)
            If (pVal.Before_Action = True) Then
                            Else
                If pVal.ItemUID = "3" Then
                    mat = oForm.Items.Item("3").Specific
                    currow = pVal.Row
                    currCol = pVal.ColUID
                    If (pVal.ColUID = "10" And pVal.EventType = SAPbouiCOM.BoEventTypes.et_KEY_DOWN And pVal.CharPressed = 9) Or (pVal.ItemUID = "1" And pVal.EventType = SAPbouiCOM.BoEventTypes.et_ITEM_PRESSED) Then
                        Try
                            Dim expdate As SAPbouiCOM.EditText
                            expdate = mat.Columns.Item(10).Cells.Item(currow).Specific
                            tgl = expdate.Value
                            Try
                                If expdate = "" Then
                                    SBO_Application.MessageBox("Expired Date empty is not allowed")
                                End If
                                Exit Sub
                            Catch ex As Exception
                                Debug.Print(ex.Message)
                                Debug.Print(ex.ToString)
                            End Try
                        Catch ex As Exception
                            Debug.Print(ex.Message)
                            Debug.Print(ex.ToString)
                        End Try
                    End If
                End If
            End If
        Else
            If pVal.ItemUID = "41" And pVal.EventType = SAPbouiCOM.BoEventTypes.et_FORM_CLOSE Then
                Exit Sub
            End If
        End If
When i try to close the batch setup and return to Good receipt form there is an error message
Add-on 9000034 failed with exception; Event Type : 17
Does any one know what the error message means ?
Does I miss something ?
Thanks in advance
Regards
Jia Shun

Hello,
for sorting batch codes by GR time sort from high to low after finding the codes from the date(s) you want (since the batch codes are created in numeric order the lower number will be the older batch codes)
perhaps I did not understand...

Add-On [X] failed with exception; Event Type:16

Hi,
I'm currently trying to create a SAP B1 Add-On using C# (Framework 3.5/VS 2008). I've done several VB.Net Add-Ons in the past but this is the first one I try to create one in C#.
Using the SDK code examples, I've managed to create an Add-On that correctly connects to UI and DI (I can create a sub-menu, set event filters and add some usertables and userfields). My sub-menu opens an XML based form in SAP B1. The first time I click on the sub-menu, my form is correctly shown. But immediately after, I get the following error in the message bar at the bottom :
Add-On [X] failed with exception; Event Type:16, in which [X] is a number (like 90003), incrementing each time I stop the Add-On in Visual Studio and restart it.
After this message occurs, I cannot display another instance of the window using the sub-menu. In fact, it seems that all Add-On activity (button click, event trapping) is disabled or ineffective. The Add-On still is running in the process tree, but no response. Only the "X" is working on the created form to close it.
I've run some tests on the code and I realized that this is happening on XML based forms (using the LoadBatchActions command to load the form) and the FormCreationParams class to create a simple form. If I put the form creation line code in comments, my Add-On still runs (I can trap events on the sub-menu click) ; I can click multiple times on the menu without a problem But as soon as I create a form, it stops responding.
It also seems that as soon as I click on another menu to open a system form, the same error occurs. If I comment the form creation line code, again I can click as often as I want without getting this error message
Can anyone help me on this one ? I can post some code depending of what you may need to check this.
Thanks !

Sorry, I've just found the problem ; it was caused by an unhanded exception !
Thanks !

Clear package failed with exception CX_SY_COMPRESSION_ERROR ?

Hi Experts,
When i ran a clear package it got failed with exception CX_SY_COMPRESSION_ERROR .
Hint : i ran light optimize package before running clear package and it got succeeded.
Thanks,
Siva

Hi,
Do you find any short dump in ST22?
It may be because of memory issue as explained in 1734382 - Process ends with CX_SY_COMPRESSION_ERROR when export transaction data to application server.
Regards,
Raju

SOAP Adapter: Exception in method process

Hello Experts,
We are getting from time to time on the Receiver SOAP Communication Channels the folowing error:
Delivery of the message to the application using connection AFW failed, due to: Exception in method process.
We are getting this error on both types of messages - sync and async.
I did a search on SDN and Notes, but didn't found any description or solution for this error.
Can someone please help with this error?
Thanks in advance!

Here are some details extracted from the log:
Date : 07/30/2008
Time : 8:44:15:783
Message : Error during processing local bean: localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
Severity : Error
Category :
Location : com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(String , ModuleData)
Application : sap.com/com.sap.aii.af.app
Thread : output
Datasource : 1217412862462:/usr/sap/xxx/xxx/j2ee/cluster/server1/log/defaultTrace.trc
Message ID : 001CC4B7988E00A5000268B100000CB3000453381549AFAE
Source Name : com.sap.aii.af.mp.ejb.ModuleProcessorBean
Argument Objs :
Arguments :
Dsr Component : xxx
Dsr Transaction : 989219405e0211ddc88b001cc4b7988e
Dsr User : Guest
Indent : 0
Level : 0
Message Code :
Message Type : 0
Relatives :
Resource Bundlename :
Session : 0
Source : com.sap.aii.af.mp.ejb.ModuleProcessorBean
ThreadObject : output
Transaction : SAP J2EE Engine JTA Transaction : [2dffffff91ffffffbdffffffe3040ffffffb0]
User : J2EE_GUEST
Hope this will help somebody to get the clue what is causing this error.

Xi 3.0: Mail adapter fails with "exception in method process"

Similar Messages

Maybe you are looking for