cancel
Showing results for 
Search instead for 
Did you mean: 

Issue with BPM Consuming a lot of Time

Former Member
0 Kudos

Thanks guys for ur support:

I have the following issue: We have a working BPM scenario in Dev and it used to take 8 sec for processing now we moved objects to QA and with other issues of J2ee engine , BPM is taking too much time like 3 min around

We fixed all the outstanding basis issues like changing parameters etc but nothing improved this scenario.

I dont see any major issue as both dev and qa have identical config any ideas please?

and in some cases i get message saying :

com.sap.aii.af.ra.ms.api.MessageExpiredException: Message f5035300-a76a-11dc-ab84-0017a451bb4c(OUTBOUND) expired.

at com.sap.aii.af.ra.ms.impl.core.service.Call.execute(Call.java:199)

at com.sap.aii.af.ra.ms.impl.ServicesImpl.call(ServicesImpl.java:192)

at com.sap.aii.adapter.xi.ms.XIEventHandler.onCall(XIEventHandler.java:317)

at com.sap.aii.af.ra.ms.impl.ConnectionImpl.call(ConnectionImpl.java:336)

at com.sap.aii.af.mp.soap.ejb.AFCallerApplication.perform(AFCallerApplication.java:117)

at com.sap.aii.messaging.srt.ApplicationBubble.onMessage(ApplicationBubble.java:29)

at com.sap.aii.messaging.srt.ExtensionBubble.onMessage(ExtensionBubble.java:56)

at com.sap.aii.af.mp.soap.ejb.XISOAPAdapterBean.process(XISOAPAdapterBean.java:906)

at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_3.process(ModuleLocalLocalObjectImpl0_3.java:103)

at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:264)

at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103)

at com.sap.aii.af.mp.soap.web.MessageServlet.callModuleProcessor(MessageServlet.java:174)

at com.sap.aii.af.mp.soap.web.MessageServlet.doPost(MessageServlet.java:441)

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:160)

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)

Accepted Solutions (0)

Answers (1)

Answers (1)

VijayKonam
Active Contributor
0 Kudos

Hi Bujji,

Did you check the disk space available on both the machines? At database level did you compress the log files size? If it is taking much time means.. problem must be with the system resourses..!!

VJ