OBPM Workspace Cascade StyleSheet (CSS) Loading Page Stuck

Question

Hi there, I´m facing a serious problem !
We have implemented ALBPM workspace to end users on my customer ! The main problem is regarding a weird behavior.
When users are working through ALBPM Workspace (deployed into ALBPM for WebLogic Server) sometimes they got stuck due to workspace problems, they select an instance or try to submit a instance to validation, they got stuck in "LOADING PAGE" and nothing happens then! They must close their browsers and re-open again to get the work done!
This is impacting roughly end users performances! My customer is complaining and we don´t have any idea what´s going on.
This is my loadingstatus.xhtml file output :
<div xmlns="http://www.w3.org/1999/xhtml"
xmlns:ui="http://java.sun.com/jsf/facelets"
xmlns:f="http://java.sun.com/jsf/core"
xmlns:html="http://fuego.com/jsf/html"
xmlns:fn="http://bea.com/bpmWorkspace/functionsLibrary">
<html:div rendered="#{not componentBean.minimizedViewSize}">
<f:verbatim>
<div id="loadingMsg#{componentBean.id}" class="bpmWorkspaceLoadingContainer" style="display:none">
<div class="bpmWorkspaceLoadingMsg">#{fn:getMsg('LOADING')}</div>
</div>
<script type="text/javascript">
function showLoadingMsg_#{componentBean.id}() {
var elem = document.getElementById('loadingMsg#{componentBean.id}');
if (elem) elem.style.display = '';
</script>
</f:verbatim>
</html:div>
</div>
Does anybody has a similiar behavior ? We are not using WEBLOGIC PORTAL !
I´d appreciate any help !
Thanks in advance
Edson

Answer 1

Thanks for your help, but I´m not using WebLogic Portal.
I´m using BPM Workspace instead of it.
End users access through BPM WORKSPACE,like I said, BPM Worskpace has been deployed into WebLogic Server and NOT WebLogic Portal. I had some issues like that on WebLogic Portal, another customer, I resolved changed the TYPE LAYOUT to Two Column Layout instead of FLOW LAYOUT.
But here, customer is using only BPM WORKSPACE, so there´s no WEBLOGIC PORTAL !
I´m facing these problems occasionally, end users must close their browsers and open a new one and finish their jobs.
I appreciate your help and attention.
Thanks
Edson - Brazil