JSP Timeout in OBPM 10GR3

Hi all,
My JSP in OBPM 10GR3 is getting timed out quickly. How can I increase the timeout of my JSP?
Because it shows on the UI workspace that "The task cannot be resumed".
How can I increase the timeout of my JSP?

There is probably one more reason why this may be happening. Again, I don't have a running 10g instance to verify this, but may be you can. Once a user clicks on the work item (or left menu in the case of a Global Create) in the inbox, and the dialog opens up, if you do a browser refresh, the popup will close, but probably , behind the scene, the screen-flow is not closed. Now , if you click on your global create again, you may get a Task cannot be resumed.
Not sure, but try this, and the only way around may be to tell users not to refresh the screen when the popup is up, if they do and get a 'Task cannot be resumed' , they will have to log out and log back in.

Similar Messages

JSP problems in OBPM 10GR3

Hi all,
When I try to access a JSP from my Global creation in OBPM 10GR3, sometimes this message appears:-
[<W> 0830 15:19:41.296] Main (<5> [ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'): Error workspace-1314782980927
[ (cont) ] Main: The Task cannot be resumed
[ (cont) ] Main: Detail: The reason could be one of the following <ol> <li>You have already finished the task execution</li> <li>You have the autologin option enabled and the session for this execution has expired . </li></ol>
[ (cont) ] Main:
[ (cont) ] Main: fuego.web.exception.ItemAlreadyExecutedException: The Task cannot be resumed
[ (cont) ] Main: Detail: The reason could be one of the following <ol> <li>You have already finished the task execution</li> <li>You have the autologin option enabled and the session for this execution has expired . </li></ol>
[ (cont) ] Main:
[ (cont) ] Main: at fuego.web.papi.TaskExecutor.processRedirect(TaskExecutor.java:213)
[ (cont) ] Main: at fuego.web.papi.TaskExecutor.execute(TaskExecutor.java:104)
[ (cont) ] Main: at fuego.workspace.servlet.ExecutorServlet.doAction(ExecutorServlet.java:117)
[ (cont) ] Main: at fuego.workspace.servlet.BaseServlet.doPost(BaseServlet.java:229)
[ (cont) ] Main: at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
[ (cont) ] Main: at fuego.workspace.servlet.AuthenticatedServlet.service(AuthenticatedServlet.java:123)
[ (cont) ] Main: at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
[ (cont) ] Main: at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
[ (cont) ] Main: at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
[ (cont) ] Main: at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
[ (cont) ] Main: at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
[ (cont) ] Main: at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
[ (cont) ] Main: at fuego.web.filter.NoCacheNoStoreFilter.doFilter(NoCacheNoStoreFilter.java:39)
[ (cont) ] Main: at fuego.web.filter.BaseFilter.doFilter(BaseFilter.java:63)
[ (cont) ] Main: at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
[ (cont) ] Main: at fuego.web.filter.SingleThreadPerSessionFilter.doFilter(SingleThreadPerSessionFilter.java:64)
[ (cont) ] Main: at fuego.web.filter.BaseFilter.doFilter(BaseFilter.java:63)
[ (cont) ] Main: at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
[ (cont) ] Main: at fuego.web.filter.CharsetFilter.doFilter(CharsetFilter.java:48)
[ (cont) ] Main: at fuego.web.filter.BaseFilter.doFilter(BaseFilter.java:63)
[ (cont) ] Main: at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
[ (cont) ] Main: at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3496)
Any idea why?

There is probably one more reason why this may be happening. Again, I don't have a running 10g instance to verify this, but may be you can. Once a user clicks on the work item (or left menu in the case of a Global Create) in the inbox, and the dialog opens up, if you do a browser refresh, the popup will close, but probably , behind the scene, the screen-flow is not closed. Now , if you click on your global create again, you may get a Task cannot be resumed.
Not sure, but try this, and the only way around may be to tell users not to refresh the screen when the popup is up, if they do and get a 'Task cannot be resumed' , they will have to log out and log back in.

Using Assoc Arrays in OBPM 10GR3 for 25 million comparisons

Can we use Associative arrays in OBPM 10GR3 to do 25 million comparisons or even more than that?
I have two assoc arrays which I compare with each other 25 million times by looping them one inside the other.
For e.g.
for(int i = 0; i < 5000; i++)
for(j=0; j < 5000; j++)
if(i==j)
logMessage ("The value is equal");
when I try to do that, I get an error:-
Persistence Data error.
I get this error:-
Error while persisting the transaction data: 'An error occurred while accesing the database. Detail:SQL statement: 'unknown' ' Details: An error occurred while accesing the database. Detail:SQL statement: 'unknown' Caused by: Unexpected exception while enlisting XAConnection java.sql.SQLException: Transaction rolled back: Transaction timed out after 302 seconds BEA1-25BFB4A4F3934EFC9C00 at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1418) at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1330) at weblogic.jdbc.wrapper.JTAConnection.getXAConn(JTAConnection.java:189) at weblogic.jdbc.wrapper.JTAConnection.checkConnection(JTAConnection.java:64) at weblogic.jdbc.wrapper.Connection.preInvocationHandler(Connection.java:92) at weblogic.jdbc.wrapper.Connection.prepareStatement(Connection.java:482) at fuego.jdbc.FaultTolerantConnection.prepareStatement(FaultTolerantConnection.java:541) at fuego.server.persistence.jdbc.JdbcServerActivityPersMgr.insertInstanceEvent(JdbcServerActivityPersMgr.java:913) at fuego.server.persistence.Persistence.storeInstanceEvent(Persistence.java:944) at fuego.server.execution.EngineExecutionContext.persistEvents
So can we use such a big comparison on OBPM 10GR3. If yes, how?

Don't use ASSOC Arrays. Use SETs.
Also increase the JTA timeout in Weblogic to like say 600 seconds.

Error while deploying a project to the OBPM 10GR3 Server

Hi all,
I am trying to deploy my current project to the OBPM 10GR3 server and it gives me the following exception. I am not sure what is this exception.
The project compiles well in Studio 10GR3.
Cannot publish the project.
'close' is not a function. Caused by: 'close' is not a function.
Does anybody know what is the exception?

Got it..
I was using Fuego.Sql.DynamicSQL.close(Iterator)
For a an executeUpdate query which returns an int.
But I used it in a method and did not use that method inside my process or screenflow.
But it did not give me any error/exception while compiling it in Studio.
It gave me an exception while publishing in Enterprise.
This is strange.
It should have given me an error/exception while compiling itself rather than while publishing in Enterprise.

Problem while Introspecting a Web-Service in OBPM 10GR3 studio

I get the following problem while Introspecting a Web-Service in OBPM 10GR3 studio:-
Introspecting...
downloading /test-ws/testc?wsdl [Error] Instrospection exception: Web Service WSDL parse exception: HTTPS hostname wrong: should be <test-01.test.net>...
Any idea why?
It runs well in a browser, eclipse and SOAP UI?

have you create the destination?
do you use the wizard to generate code?
usually there is catch clause for this line of code
wdContext.currentRequest_SERVICE_MDM_LOOKUPElement().modelObject().execute();
Edited by: John Wu on Dec 16, 2010 11:51 PM

Return value for Direct OBPM SQL Query in OBPM 10GR3

Hi all,
I use a direct SQL Query provided by OBPM 10GR3 in my automatic activity to select certain elements from the db. The query is as follows:-
foreach (element in
SELECT id FROM TESTTABLE WHERE requestId = 732 and status = 1 )
// statements
logMessage("-- The id is-->" +element.id);
This only returns when the id is found in the db but returns nothing when not found in db?
How can I always get a return value? atleast a true or false, so that I can put IF statements?
Because if it returns nothing, the loop does not execute {}? So we cannot put something like:-
foreach (element in
SELECT id FROM TESTTABLE WHERE requestId = 732 and status = 1 )
logMessage("-- The id is-->" +element.id);
if(element.id == null)
logMessage("-- Id Not Found -->" );
else
logMessage("-- Id Found -->");
How can I always get a return value from my OBPM direct query ?
Remember , I am not using DynamicSQL in this case?

Hi,
Set a Boolean flag value to False before the SQL query.
Some thing like:
boolean flag = false;
foreach (element in
SELECT id FROM TESTTABLE WHERE requestId = 732 and status = 1 )
logMessage("-- The id is-->" +element.id);
flag = true;
if(flag) {
logMessage("-- Id Found -->" );
else
logMessage("-- Id Not Found -->");
Hope the above logic would work fine.
Bibhu
Edited by: Bibhuti Bhusan on Sep 2, 2011 11:48 AM

Text File opened in Wordpad cannot be parsed on OBPM 10GR3

Hi all,
Text File opened in Wordpad cannot be parsed on OBPM 10GR3
Why is that?
I use the following code to parse a file:-
textFile = TextFile();
textFile.open(name : "C:\testFile.txt");
logMessage("---Does file exist?--> " + textFile.exists);
foreach (line in textFile.lines) {
logMessage("-- The LINE is-->" + line);
pinBlockProcessing.linesCount = pinBlockProcessing.linesCount + 1;
pinBlockProcessing.deviceIdentifierArray[] = line;
textFile.close();

Hi all,
I also used other two methods to parse such a file which can be opened in Wordpad but not in Notepad.
1) I used Java.Util.Scanner
2) I also created and compiled a program/package/class which gets a file and parses it using Java.Util.Scanner using Java in Eclipse.
I created a JAR out of it and tried to use this JAR in my process by introspecting it and then passing the file to be parsed to the methods in this JAR file.
But this did not work either. Although the program does work in plain Java in Eclipse. It compiles and parses a a file which can be opened in Wordpad but not in Notepad.
My program for both these methods was :-
import java.io.FileReader;
import java.io.FileWriter;
import java.io.IOException;
import java.util.Scanner;
public class Test{
public static void main(String args[]) throws IOException {
FileReader fin = new FileReader("./testFile.txt");
Scanner src = new Scanner(fin);
src.useDelimiter("\n");
while (src.hasNext()) {
System.out.println(src.next());
fin.close();
This does not work either.
All programs and methods work when a text file can be opened in NotePad.
What could be possible solution in OBPM 10GR3?
It is something to do with Carriage Return and generating a file in UNIX which when opened in Notepad shows one straight horizontal line and when opened in Wordpad shows vertical lines.

View Items in OBPM 10GR3

Does anybody know how to bring the last initiated process instance to be seen first in the worklist views in OBPM 10GR3?
By default, the last initiated worklist item is posted at the end and one has to scroll down all the way to the last initiated item.
How can we bring that to the front?

Enter in the Workspace Administrator, go to the presentations option, take the presentation associated to your inbox, typically default_instances take the column "received" and put to sort by this column choosing descending.
HTH

Aborting an Automatic Activity from OBPM 10GR3 workspace

Hi all,
I can abort Interactive Activities from the OBPM 10GR3 workspace just by selecting that instance, the selecting the action as ABORT from the BULK ACTIONS on the right hand side and the entire instance is aborted.
But how do I abort Automatic Activities from the OBPM 10GR3 workspace?
When my instance arrives at an automatic activity, I am unable to abort it from the BPM workspace.
There is no option when you right click an Automatic Activity and select RUNTIME , which says, "If enabled, the instance can be aborted by the user".
So how do we do that ( from the OBPM 10GR3 Workspace)?

The "If enabled, the instance can be aborted by the user" needs to be selected when you abort via PAPI...
Since aotumatic activitys do not appear in the workspace you cannot abort them from there.
You can connect via PAPI, find the instance and abort it from another instance.
Even though must automatic activitys are built so they finish before you can even go and abort them.
I think its a strange design to have an aotumatic activity that is up long enough for you to cancel it but as i said above...
1) Select abortable on the activity.
2) Find the instance and abort
Fuego.Papi.InstanceFilter ifilter = new InstanceFilter();
ProcessService.connectTo(url : Fuego.Server.directoryURL, user :<username>, password : <password>);
ifilter.create(processService : ProcessService);
ifilter.searchScope = new SearchScope(participantScope : ParticipantScope.ALL , statusScope : StatusScope.ONLY_INPROCESS);
//Notice i write public variable and not instance variable
ifilter.addAttributeTo(variable : <public variable (such as description or one of your own)>, comparator : Comparison.<the one that fits you>, value : <value>);
Fuego.Papi.Instance[] cInstances = ProcessService.getInstancesByFilter(filter : ifilter);
foreach (instance in cInstances)
//Second type of filtering (checking current activity and process), you can check just the activity name if its a unique name
if (instance.activityName == <aotumatic activity name> && instance.processId.contains(regexp : '/<process name>/'))
instance.abort();
I use a similer code snippet to remove Interactive activities.
Just notice that you filter only the instances you really want to take down.

How to install a plugin in OBPM 10GR3

How do we install a plugin in OBPM 10GR3. Any steps that you guys know of?
I want to install a plugin which actually needs to be installed for eclipse but since OBPM 10GR3 is built on top of eclipse, I think I can install it in OBPM 10GR3..
Please guide through the process.?

BPM Studio (10g) is just a plugin for eclipse. To install other plugins, just use the Help - Software Updates - Find and Install
HTH,
-Kevin

Internet Explorer CLOSE Button for OBPM 10GR3 Presentations

Hi all,
I am using OBPM 10GR3 presentations with a POPUP window.
I already have a close button to close the presentation. This is a Global Interactive Activity which displays the dashboards.
The Global Interactive Activity contains a screenflow and inside the screenflow I have a Interactive Component Call to call the presentation.
Now the presentation opens smoothly and everything is displayed.. When we hit the CLOSE button everything goes away and when we open it again it again comes back to the previous Interactive Component Call and restarts.
BUT
When we Close the window itself instead of using the CLOSE button of the presentations, and we re-open, we get the previous data.
This is because we do not hit the CLOSE button of the presentation instead hit the IE WINDOW CLOSE button on the top right hand corner besides the minimize maximize button.
Therefore the call is still inside the screenflow inside the Global Interactive Activity and therefore it waits for the user to hit the CLOSE button of the presentations otherwise does not close.
How can we resolve this issue?
How can we make sure, that if the user closes the IE WINDOW itself using the CLOSE button, it closes the presentation itself and when re-opened displays the previous presentation?

Hi,
First of all this is a training issue with the user. It is not advisable not to press the close button of the IE.
Nevertheles you can disable to close button of the presentaion.
You can remove the x from dialogs by doing this. Open the executionDialog.xhtml file in the <OraBPMEnterpriseHomeDirectory>\webapps\workspace\jsf\common directory (both Studio and Enterprise have this file).
Change the text on line 81 from this:
<oc:Dialog verticalAlign="top" offsetY="40" backColor="#D4E1EB" borderColor="#517B9E"
borderStyle="solid" borderWidth="1px" id="executionDialog#{componentBean.id}"
title="#{fn:getMsg('EXECUTION')}" broadcastName="executionDialog#{componentBean.id}"
maximized="#{componentBean.executionDialogMaximized}" width="#{componentBean.executionDialogWidth}"
height="#{componentBean.executionDialogHeight}" titleBarCssClass="bpmWorkspaceDialogHeader"
displayMaximizeButton="true"
modal="false" jsObjectName="executionDialog#{componentBean.id}">
to this:
<oc:Dialog verticalAlign="top" offsetY="0" backColor="#FFFFFF" borderColor="#FFFFFF"
borderStyle="solid" borderWidth="1px" id="executionDialog#{componentBean.id}"
title="#{fn:getMsg('EXECUTION')}" broadcastName="executionDialog#{componentBean.id}"
maximized="#{componentBean.executionDialogMaximized}" width="#{componentBean.executionDialogWidth}"
height="#{componentBean.executionDialogHeight}" titleBarCssClass="bpmWorkspaceDialogHeader"
displayMaximizeButton="true"
displayCloseButton="false" modal="false" jsObjectName="executionDialog#{componentBean.id}">
This change does a couple things. The addition of the text "displayCloseButton="false"" removes the x button that is causing the undesired results you're getting and setting the colors to #FFFFFF changes the light blue border around dialog boxes to white.
Bibhu

Best Practice for using JSP in OBPM 10gr3

Hi Guys,
We are using JSP for UI in our project. We are new to the OBPM. wants to clarify some things.
1. is it good to have jsp in screenflows or if we can manage it outside BPM also with same effect
2. How is the BPM database structured. Is the PAPI API's avaialble to get all the desired information from it.
3. Is notes/attachments/audits managed in BPM database or if we can manage it in external db also.. how to access these from java if it can be managed in BPM db.
4. What are the pro's and cons of PAPI vs JMS
Thanks in Advance!!!!

1. is it good to have jsp in screenflows or if we can manage it outside BPM also with same effectOthers will probably disagree, but I always say to use Screenflows and to use the out of the box Workspace. They are built in as part of the product and you'll be facing a ton of work trying to duplicate this functionality outside.
2. How is the BPM database structured. Is the PAPI API's avaialble to get all the desired information from it.Unless it's a project variable or a variable that is marked as "Separated", the instance variables are stored in a single blob in a row in the Engine's database. PAPI can retrieve the instance variable information (I posted something on how to do this a while back on this forum and can find it if you need it).
3. Is notes/attachments/audits managed in BPM database or if we can manage it in external db also.. how to access these from java if it can be managed in BPM db.The out of the box notes and attachments are also stored as part of the blob. On the project I'm currently on, the customer wanted the attachments stored separately in an external database so we did not use the out of the box attachments. They wanted what they call "tasks" stored in a separate database. These tasks were for ad hoc queries to send a question to any department / user and then store the history of responses and routing.
4. What are the pro's and cons of PAPI vs JMSSorry - you lost me here. Sure someone else will pick up on the comparison between the API Oracle BPM uses and JMS, but I'm not getting it.
Dan

Database locks in OBPM 10gR3

Environment:
Oracle BPM 10gR3 Version: 10.3.1.0.0 Build: #99954
WebLogic Server 10.0 MP1 Clustered domain
JDBC Driver - WebLogic Type 4 XA ( weblogic.jdbcx.oracle.OracleDataSource )
We have a BPM project deployed on the WLS 10.0 MP1 Cluster,which was running fine for the last 18 months. But all of a sudden we are experiencing the database locks errors for the last few days, when we try to restart the BPM Engine.
WebLogic JTA Timeout = 30 seconds
Database Distributed_Lock_Timeout = 60 seconds
WebLogic Datasources for Directory and Engine XA Connection Timeout = 30 seconds
Error
Process '/Test#Default-1.0' could not be started. Details:\nProcess execution engine execution error.
Caused by: Exception [java.sql.SQLException: [BEA][Oracle JDBC Driver][Oracle]ORA-02049: timeout: distributed transaction waiting for lock ].
Caused by: [BEA][Oracle JDBC Driver][Oracle]ORA-02049: timeout: distributed transaction waiting for lock
fuego.papi.impl.EngineExecutionException: Process execution engine execution error.
 at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:139)
 at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:79)
 at fuego.server.execution.DefaultEngineExecution.executeWithoutComponentImmediate(DefaultEngineExecution.java:185)
 at fuego.server.execution.EngineExecution.executeWithoutComponentImmediate(EngineExecution.java:86)
 at fuego.ejbengine.service.EJBActiveProcessService.startProcess(EJBActiveProcessService.java:92)
 at fuego.server.service.ActiveProcessService.runProcessesLoader(ActiveProcessService.java:118)
 at fuego.server.service.ActiveProcessService.activateProcesses(ActiveProcessService.java:88)
 at fuego.ejbengine.service.EJBActiveProcessService.doActivateProcesses(EJBActiveProcessService.java:63)
 at fuego.ejbengine.cluster.DistributedEJBActiveProcessService.initialize(DistributedEJBActiveProcessService.java:37)
 at fuego.ejbengine.cluster.ClusterObjectFactory.initializeActiveProcessService(ClusterObjectFactory.java:33)
 at fuego.ejbengine.Engine.startServices(Engine.java:448)
 at fuego.ejbengine.Engine.start(Engine.java:129)
 at fuego.ejbengine.servlet.AbstractSchedulerServlet.init(AbstractSchedulerServlet.java:91)
 at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
 at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
 at weblogic.security.service.SecurityManager.runAs(Unknown Source)
 at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
 at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
 at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
 at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:507)
 at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1853)
 at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1830)
 at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1750)
 at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2909)
 at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:973)
 at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:361)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
 at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
 at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
 at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
 at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
 at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
 at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
 at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
 at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
 at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
 at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
 at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:182)
 at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:359)
 at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
 at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
 at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
 at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
 at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
 at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
 at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
 at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
 at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
Caused by: fuego.directory.DirectoryRuntimeException: Exception [java.sql.SQLException: [BEA][Oracle JDBC Driver][Oracle]ORA-02049: timeout: distributed transaction waiting for lock ].
 at fuego.directory.DirectoryRuntimeException.wrapException(DirectoryRuntimeException.java:85)
 at fuego.directory.provider.jdbc.oracle.OraclePersistenceManager.mapSQLException(OraclePersistenceManager.java:183)
 at fuego.directory.provider.jdbc.datadirect.oracle.DataDirectOraclePersistenceManager.mapSQLException(DataDirectOraclePersistenceManager.java:50)
 at fuego.directory.provider.jdbc.JDBCServiceAccessor.mapSQLException(JDBCServiceAccessor.java:78)
 at fuego.directory.provider.jdbc.JDBCProcessAccessor.updateDeployedProcess(JDBCProcessAccessor.java:1330)
 at sun.reflect.GeneratedMethodAccessor92.invoke(Unknown Source)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
 at $Proxy57.updateDeployedProcess(Unknown Source)
 at fuego.directory.DirDeployedProcess.update(DirDeployedProcess.java:1022)
 at fuego.server.ActiveProcessManager.handleProcess(ActiveProcessManager.java:496)
 at fuego.server.service.ActiveProcessService.startProcess(ActiveProcessService.java:136)
 at fuego.ejbengine.service.EJBActiveProcessService.startProcessImpl(EJBActiveProcessService.java:107)
 at fuego.ejbengine.service.EJBActiveProcessService.access$100(EJBActiveProcessService.java:32)
 at fuego.ejbengine.service.EJBActiveProcessService$2.execute(EJBActiveProcessService.java:95)
 at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304)
 at fuego.transaction.TransactionAction.startBaseTransaction(TransactionAction.java:470)
 at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:551)
 at fuego.transaction.TransactionAction.start(TransactionAction.java:212)
 at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123)
 ... 52 more
Caused by: java.sql.SQLException: [BEA][Oracle JDBC Driver][Oracle]ORA-02049: timeout: distributed transaction waiting for lock
 at weblogic.jdbc.base.BaseExceptions.createException(Unknown Source)
 at weblogic.jdbc.base.BaseExceptions.getException(Unknown Source)
 at weblogic.jdbc.oracle.OracleImplStatement.execute(Unknown Source)
 at weblogic.jdbc.base.BaseStatement.commonExecute(Unknown Source)
 at weblogic.jdbc.base.BaseStatement.executeUpdateInternal(Unknown Source)
 at weblogic.jdbc.base.BasePreparedStatement.executeUpdate(Unknown Source)
 at weblogic.jdbcx.base.BasePreparedStatementWrapper.executeUpdate(Unknown Source)
 at weblogic.jdbc.wrapper.PreparedStatement.executeUpdate(PreparedStatement.java:125)
 at fuego.jdbc.FaultTolerantPreparedStatement.executeUpdate(FaultTolerantPreparedStatement.java:623)
 at fuego.directory.provider.jdbc.JDBCPersistenceManager.update(JDBCPersistenceManager.java:946)
 at fuego.directory.provider.jdbc.JDBCProcessAccessor.updateDeployedProcess(JDBCProcessAccessor.java:1327)
 ... 68 more

Hello -
Following is the Oracle recommendation for BPM timeouts. Now you can try this.
Increase the timeout:
-in the Oracle Weblogic console go to Services -> JTA -> Timeout Seconds . Set the value to 300.
also the DISTRIBUTED_LOCK_TIMEOUT value for BPM should follow the following formula:
DISTRIBUTED_LOCK_TIMEOUT >= XA Transaction Timeout >= WebLogic Server JTA timeout
This means that the configured "DISTRIBUTED_LOCK_TIMEOUT" value should be equal to or
larger than the "XA Transaction Timeout" value which in turn should be equal to or larger than the "WebLogic Server JTA timeout".
Note : Check your previous BPM Engine logs, you can see the timeout warning.
BR,
Justin.

JSP Timeout after 300 seconds

"Hi all,
 Need your help. My JSP always got timeout after 300 seconds. I already set the Timeout Secs (in web app descriptor) to 600 seconds and Invalidation Interval Secs to 180 seconds. Where this 300 secs setting come from ? Below is the error message. Thanks.
 Transaction Rolledback.; nested exception is:
 weblogic.transaction.internal.TimedOutException: Transaction timed out after 303 seconds
 Name=[EJB EJB.AccountPortfolioBean.mtdAccount(EJB.Engine.Message)]
 Start server side stack trace:
 java.rmi.RemoteException: Transaction Rolledback.; nested exception is:
 weblogic.transaction.internal.TimedOutException: Transaction timed out after 303 seconds
 Name=[EJB EJB.AccountPortfolioBean.mtdAccount(EJB.Engine.Message)]
 weblogic.transaction.internal.TimedOutException: Transaction timed out after 303 seconds
 Name=[EJB EJB.AccountPortfolioBean.mtdAccount(EJB.Engine.Message)]
 at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1124)
 at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:466)
 at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1604)
 at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:429)
 at weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManagerImpl.java:1570)
 at java.lang.Thread.run(Thread.java:484)
 End serve


 Hi Hendry,
 Get in to weblogic console
 Click JTA from your left pane
 JTA and increase the timeout seconds there.
 Hope this helps you.
 Arul
 Rob Woollen <[email protected]> wrote:
 >That's the transaction timing out. What version of WLS are you using?
 >
 >In < 6.0, the default tx timeout is 300 seconds. In >= 6.0, the default
 >
 >tx timeout is 30 seconds.
 >
 >What are you doing in a transaction that takes more than 5 minutes?
 >
 >-- Rob
 >
 >Hendry Janto wrote:
 >> "Hi all,
 >>
 >>
 >> Need your help. My JSP always got timeout after 300 seconds. I already
 >set the Timeout Secs (in web app descriptor) to 600 seconds and Invalidation
 >Interval Secs to 180 seconds. Where this 300 secs setting come from
 >? Below is the error message. Thanks.
 >>
 >> Transaction Rolledback.; nested exception is:
 >> weblogic.transaction.internal.TimedOutException: Transaction timed
 >out after 303 seconds
 >> Name=[EJB EJB.AccountPortfolioBean.mtdAccount(EJB.Engine.Message)]
 >>
 >> Start server side stack trace:
 >> java.rmi.RemoteException: Transaction Rolledback.; nested exception
 >is:
 >> weblogic.transaction.internal.TimedOutException: Transaction timed
 >out after 303 seconds
 >> Name=[EJB EJB.AccountPortfolioBean.mtdAccount(EJB.Engine.Message)]
 >> weblogic.transaction.internal.TimedOutException: Transaction timed
 >out after 303 seconds
 >> Name=[EJB EJB.AccountPortfolioBean.mtdAccount(EJB.Engine.Message)]
 >> at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1124)
 >> at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:466)
 >> at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1604)
 >> at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:429)
 >> at weblogic.transaction.internal.TransactionManagerImpl$1.run(TransactionManagerImpl.java:1570)
 >> at java.lang.Thread.run(Thread.java:484)
 >> End serve
 >

OBPM 10gR3 Dynamic Role Assignment at user login

Hi,
For all the great integration with LDAP in 10gR3, unfortunately, the system is unable to deal with dynamically-defined LDAP groups.
Our goal is to apply a BPM Role to ALL humans defined in our LDAP.
All humans happen to already be defined by a dynamically-defined LDAP group called 'AllPeople'.
It would have been perfect if we could simply assign our BPM Role, 'Employee', to the LDAP group, 'AllPeople'. Sadly you can't (one for the next release pls).
So as a workaround, what we want to do instead is assign the BPM Role 'Employee' to each individual user dynamically when they first login.
Since the FDI library is useless outside of a BPM context (you'll find that some of the familiar methods of RoleAssignment are missing), We opted to create an actual BPM process to conduct role assignments, and we would then trigger it via PAPI.
The question then was, where/when do we invoke the process such that it does the role assignment quickly and soon enough for the appropriate views and applications to appear in their workspace straight after login?
We opted for a customised implementation of the SSOWorkspaceLoginInterface class.
However, we tried making the invocation in the setupAuthenticatedSession() and the processRequest() methods but, although the role assignment was successfully done in either case, sadly the user's session was loaded without the new changes - perhaps loaded quicker than the role assignment could be fed back through the directory.
Therefore, we dumped the invocation in the actual constuctor - and this seems to work for the most part. Yet on the odd ocassion, the role assignment is not quick enough to be realised in the user's workspace session - the user has to logout and back in before the changes are realised.
We've even tried to get the execution to sleep for a second or two, while the PAPI thread goes about doing the role assignment - again not much success.
So I really have 2 questions:
1. Where during login can we make a PAPI call to do a role assignment so that it should be picked up by the time the session is created? perhaps we already are doing it in the right place.
2. How could we refresh/request a new session cookie without explicitly logging out and back in again? Note, page refresh is not enough.
Thanks for reading.

Sorry for the belated response - I don't get notified of replies.
The code for my custom SSOLoginModule class is:-
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import java.io.FileInputStream;
import java.io.IOException;
import java.util.Properties;
import fuego.workspace.security.SSOWorkspaceLoginInterface;
import fuego.papi.Arguments;
import fuego.papi.CommunicationException;
import fuego.papi.InstanceInfo;
import fuego.papi.OperationException;
import fuego.papi.ProcessService;
import fuego.papi.ProcessServiceSession;
import fuego.sso.SSOLoginException;
import fuego.sso.SSOUserLogin;
import fuego.jsfcomponents.Util;
import fuego.workspace.model.common.WorkspaceApplicationBean;
public class CustomSSOWorkspaceLogin extends SSOUserLogin implements SSOWorkspaceLoginInterface {
private ProcessService pService;
private ProcessServiceSession pServiceSession;
private Properties properties;
public SSOWorkspaceDBLogin() {
//Do the role assignment here because it works, and does not work in the ideal location of setupAuthenticatedSession method
pService = createProcessService();
pServiceSession = createProcessServiceSession();
assignDefaultRole(Util.getHttpServletRequest().getRemoteUser());
private ProcessService createProcessService() {
return WorkspaceApplicationBean.getCurrent().getProcessService();
private ProcessServiceSession createProcessServiceSession() {
return pService.createSession("yourdirectoryusername","yourdirectorypassword",null);
//This method is used to remotely invoke a BPM process to do the role assignment - no external API to do this directly!
private void assignDefaultRole(String email) {
try {
String processId = "myRoleAssignmentProcessId";
String argumentName = "argumentName"; //the name of the input argument to feed in the participant
String argumentValue = email;
Arguments arguments = Arguments.create();
arguments.putArgument(argumentName, argumentValue);
InstanceInfo instance = pServiceSession.processCreateInstance(processId, arguments);
Long waitTime = new Long(1000);
Long timeLimit = new Long(5000);
boolean roleAssigned = false;
boolean timeLimitExceeded = false;
Long startTime = System.currentTimeMillis();
//Allow role assignment thread to complete
while (!roleAssigned && !timeLimitExceeded) {
try {
Thread.sleep(waitTime);
if (pServiceSession.processGetInstance(instance.getId()).isCompleted()) {
roleAssigned = true;
if (System.currentTimeMillis() - startTime > timeLimit) {
timeLimitExceeded = true;
} catch (InterruptedException e) {
e.printStackTrace();
//close process service session
pServiceSession.close();
//Do not close the service itself as it is shared with the Workspace itself!
//pService.close();
} catch (Exception e) {
e.printStackTrace();
public void setupAuthenticatedSession(HttpServletRequest httpservletrequest, HttpServletResponse httpservletresponse) throws SSOLoginException {
//Unfortunately, the below does not work here because the role assignment is not fast enough
//The result is that the user logs in but cannot see any applications because the role assignment has not been made in time.
//Therefore, we run the below statements from the constructor - ugly but functions.
//pService = createProcessService();
//pServiceSession = createProcessServiceSession();
//assignDefaultRole(httpservletrequest.getRemoteUser());
public void processRequest(HttpServletRequest httpservletrequest, HttpServletResponse httpservletresponse) throws SSOLoginException {
}

JSP Timeout in OBPM 10GR3

Similar Messages

Maybe you are looking for