BPM Clustering on WLS

Does anyone have a decent cookbook for setting up a BPM cluster in WLS? We are deploying this configuration and have no problems on the WLS side but major problems with BPM. Unfortunately the documentation for this is rather thin and not too intuitive. Any help would be greatly appreciated.
TIA,
IGS

You need to increase the JTA timeout value in WLS to something higher (like 300). Some of the BPM engine transactions take longer than Weblogic's default.
Please refer to the following document in MetaLink for details:
Doc ID: 780946.1

Similar Messages

Oracle bpm clustering

Friends
I'm completely new to oracle bpm and would like to know how I can setup a bpm cluster.I'm planning to use bpm 10.3.1 for weblogic and weblogic 10.3.0.The deployment topology is planned as follows:
1.weblogic admin server on 1st machine
2.2 managed servers on 2nd machine
3.2 managed servers on 3rd machine
1 managed server on machine2 and 1managed server on machine 3 form a 1st cluster and we are planning to deploy papi-was onto this cluster
2nd managed server on machine2 and 2nd managed server on machine 3 form a 2nd cluster and we are planning to deploy bpm engine onto this cluster
I have the following queries
1.Where should we deploy the process admin web console on weblogic(this originally comes with tomcat but we don't want to use tomcat)
2.Are there any other components that are missing from above list and how to exactly deploy these.
Please let me know if any of you can walk through with the steps.I referred to the following documentation but it doesn't help much with clustering
http://download-llnw.oracle.com/docs/cd/E13154_01/bpm/docs65/config_guide/index.html
Thanks

In fact, this is the answer to my first question. Thank you.
But, how to see and detect the load balancing? how to see transactions between servers?
Thanks for help
Edited by: 857737 on 26 avr. 2012 14:54

Help with BPM Enterprise on WLS JDBC Errors

All,
We are seeing a consistent stream of errors when contacting external resources (Web Services, and Applications) during an exception handling flow and on the "happy path". The WLS logs do not show anything, the BPM engine logs continue to throw the error below:
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 30 seconds BEA1-0097C7E283E25C8E0272 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.JdbcInstanceExceptionPersMgr.getAllExceptions(JdbcInstanceExceptionPersMgr.java:304) at fuego.server.persistence.jdbc.JdbcInstanceExceptionPersMgr.getAllStack(JdbcInstanceExceptionPersMgr.java:392) at fuego.server.persistence.jdbc.JdbcInstanceExceptionPersMgr.create(JdbcInstanceExceptionPersMgr.java:58) at fuego.server.persistence.Persistence.createException(Persistence.java:677) at fuego.server.execution.microactivity.utils.ExceptionUtils.setExceptionToInstance(ExceptionUtils.java:130) at fuego.server.execution.microactivity.ComponentExecutionMicroActivity.handleUserDefine(ComponentExecutionMicroActivity.java:153) at fuego.server.execution.microactivity.ComponentExecutionMicroActivity.handleException(ComponentExecutionMicroActivity.java:138) at fuego.server.execution.microactivity.ComponentExecutionMicroActivity.execute(ComponentExecutionMicroActivity.java:97) at fuego.server.execution.microactivity.MicroActivityEngineExecutionHandler.executeActivity(MicroActivityEngineExecutionHandler.java:57) at fuego.server.execution.ImmediateActivity.execute(ImmediateActivity.java:42) at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304) at fuego.transaction.TransactionAction.startNestedTransaction(TransactionAction.java:527) at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:548) at fuego.transaction.TransactionAction.start(TransactionAction.java:212) at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123) at fuego.server.execution.DefaultEngineExecution.executeAutomaticWork(DefaultEngineExecution.java:62) at fuego.server.execution.EngineExecution.executeAutomaticWork(EngineExecution.java:42) at fuego.server.execution.ToDoItem.executeAutomaticWork(ToDoItem.java:251) at fuego.ejbengine.ItemExecutionBean$1.execute(ItemExecutionBean.java:212) 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) at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66) at fuego.ejbengine.ItemExecutionBean.processMessage(ItemExecutionBean.java:198) at fuego.ejbengine.ItemExecutionBean.onMessage(ItemExecutionBean.java:110) at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466) at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371) at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327) at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4547) at weblogic.jms.client.JMSSession.execute(JMSSession.java:4233) at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3709) at weblogic.jms.client.JMSSession.access$000(JMSSession.java:114) at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5058) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) fuego.transaction.DatabaseException: An error occurred while accesing the database. Detail:SQL statement: 'unknown' at fuego.server.persistence.jdbc.JdbcInstanceExceptionPersMgr.getAllExceptions(JdbcInstanceExceptionPersMgr.java:335) at fuego.server.persistence.jdbc.JdbcInstanceExceptionPersMgr.getAllStack(JdbcInstanceExceptionPersMgr.java:392) at fuego.server.persistence.jdbc.JdbcInstanceExceptionPersMgr.create(JdbcInstanceExceptionPersMgr.java:58) at fuego.server.persistence.Persistence.createException(Persistence.java:677) at fuego.server.execution.microactivity.utils.ExceptionUtils.setExceptionToInstance(ExceptionUtils.java:130) at fuego.server.execution.microactivity.ComponentExecutionMicroActivity.handleUserDefine(ComponentExecutionMicroActivity.java:153) at fuego.server.execution.microactivity.ComponentExecutionMicroActivity.handleException(ComponentExecutionMicroActivity.java:138) at fuego.server.execution.microactivity.ComponentExecutionMicroActivity.execute(ComponentExecutionMicroActivity.java:97) at fuego.server.execution.microactivity.MicroActivityEngineExecutionHandler.executeActivity(MicroActivityEngineExecutionHandler.java:57) at fuego.server.execution.ImmediateActivity.execute(ImmediateActivity.java:42) at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304) at fuego.transaction.TransactionAction.startNestedTransaction(TransactionAction.java:527) at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:548) at fuego.transaction.TransactionAction.start(TransactionAction.java:212) at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123) at fuego.server.execution.DefaultEngineExecution.executeAutomaticWork(DefaultEngineExecution.java:62) at fuego.server.execution.EngineExecution.executeAutomaticWork(EngineExecution.java:42) at fuego.server.execution.ToDoItem.executeAutomaticWork(ToDoItem.java:251) at fuego.ejbengine.ItemExecutionBean$1.execute(ItemExecutionBean.java:212) 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) at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66) at fuego.ejbengine.ItemExecutionBean.processMessage(ItemExecutionBean.java:198) at fuego.ejbengine.ItemExecutionBean.onMessage(ItemExecutionBean.java:110) at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466) at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371) at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327) at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4547) at weblogic.jms.client.JMSSession.execute(JMSSession.java:4233) at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3709) at weblogic.jms.client.JMSSession.access$000(JMSSession.java:114) at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5058) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) Caused by: java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: Transaction rolled back: Transaction timed out after 30 seconds BEA1-0097C7E283E25C8E0272 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.JdbcInstanceExceptionPersMgr.getAllExceptions(JdbcInstanceExceptionPersMgr.java:304) at fuego.server.persistence.jdbc.JdbcInstanceExceptionPersMgr.getAllStack(JdbcInstanceExceptionPersMgr.java:392) at fuego.server.persistence.jdbc.JdbcInstanceExceptionPersMgr.create(JdbcInstanceExceptionPersMgr.java:58) at fuego.server.persistence.Persistence.createException(Persistence.java:677) at fuego.server.execution.microactivity.utils.ExceptionUtils.setExceptionToInstance(ExceptionUtils.java:130) at fuego.server.execution.microactivity.ComponentExecutionMicroActivity.handleUserDefine(ComponentExecutionMicroActivity.java:153) at fuego.server.execution.microactivity.ComponentExecutionMicroActivity.handleException(ComponentExecutionMicroActivity.java:138) at fuego.server.execution.microactivity.ComponentExecutionMicroActivity.execute(ComponentExecutionMicroActivity.java:97) at fuego.server.execution.microactivity.MicroActivityEngineExecutionHandler.executeActivity(MicroActivityEngineExecutionHandler.java:57) at fuego.server.execution.ImmediateActivity.execute(ImmediateActivity.java:42) at fuego.server.execution.DefaultEngineExecution$AtomicExecutionTA.runTransaction(DefaultEngineExecution.java:304) at fuego.transaction.TransactionAction.startNestedTransaction(TransactionAction.java:527) at fuego.transaction.TransactionAction.startTransaction(TransactionAction.java:548) at fuego.transaction.TransactionAction.start(TransactionAction.java:212) at fuego.server.execution.DefaultEngineExecution.executeImmediate(DefaultEngineExecution.java:123) at fuego.server.execution.DefaultEngineExecution.executeAutomaticWork(DefaultEngineExecution.java:62) at fuego.server.execution.EngineExecution.executeAutomaticWork(EngineExecution.java:42) at fuego.server.execution.ToDoItem.executeAutomaticWork(ToDoItem.java:251) at fuego.ejbengine.ItemExecutionBean$1.execute(ItemExecutionBean.java:212) 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) at fuego.server.execution.EngineExecution.executeImmediate(EngineExecution.java:66) at fuego.ejbengine.ItemExecutionBean.processMessage(ItemExecutionBean.java:198) at fuego.ejbengine.ItemExecutionBean.onMessage(ItemExecutionBean.java:110) at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:466) at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371) at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327) at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4547) at weblogic.jms.client.JMSSession.execute(JMSSession.java:4233) at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3709) at weblogic.jms.client.JMSSession.access$000(JMSSession.java:114) at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5058) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1343) 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.JdbcInstanceExceptionPersMgr.getAllExceptions(JdbcInstanceExceptionPersMgr.java:304) ... 37 more
Any insight would be appreciated. The WLS and BPM configuration appears correct.
TIA,
IGS

You need to increase the JTA timeout value in WLS to something higher (like 300). Some of the BPM engine transactions take longer than Weblogic's default.
Please refer to the following document in MetaLink for details:
Doc ID: 780946.1

Clustering problem WLS 5.1

Hi,
we have an environment with 2 clusters ( 1 JSP & 1 EJB)
both cluster consist each of 2 nodes, where 1 JSP and 1 EJB are running on a machine.
although both clusters seem to act correctly at runtime ( and are also visible
in the console as clusters), we get an exception at startup - only at th JSP tier
which is rather confusing:
Do Aug 08 06:11:15 CEST 2002:<E> <WebLogicServer> Unable to bind cluster MO as
"WebLogic" into JNDI tree
javax.naming.NameAlreadyBoundException; remaining name 'weblogic.cluster.WebLogic'
at weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.java:76)
at weblogic.jndi.toolkit.BasicWLContext_WLStub.bind(BasicWLContext_WLStub.java:1261)
at weblogic.jndi.toolkit.WLContextStub.bind(WLContextStub.java:484)
at weblogic.cluster.ClusterMain.start(ClusterMain.java:290)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:1447)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:869)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:140)
at weblogic.Server.main(Server.java:97)
at weblogic.Server.main(Server.java:58)
None of our clusters is named MO !
Does anybody have a clue ?!

Hi,
we have an environment with 2 clusters ( 1 JSP & 1 EJB)
both cluster consist each of 2 nodes, where 1 JSP and 1 EJB are running on a machine.
although both clusters seem to act correctly at runtime ( and are also visible
in the console as clusters), we get an exception at startup - only at th JSP tier
which is rather confusing:
Do Aug 08 06:11:15 CEST 2002:<E> <WebLogicServer> Unable to bind cluster MO as
"WebLogic" into JNDI tree
javax.naming.NameAlreadyBoundException; remaining name 'weblogic.cluster.WebLogic'
at weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.java:76)
at weblogic.jndi.toolkit.BasicWLContext_WLStub.bind(BasicWLContext_WLStub.java:1261)
at weblogic.jndi.toolkit.WLContextStub.bind(WLContextStub.java:484)
at weblogic.cluster.ClusterMain.start(ClusterMain.java:290)
at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:1447)
at weblogic.t3.srvr.T3Srvr.main(T3Srvr.java:869)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.Server.startServerDynamically(Server.java:140)
at weblogic.Server.main(Server.java:97)
at weblogic.Server.main(Server.java:58)
None of our clusters is named MO !
Does anybody have a clue ?!

Clustering 5 wls

Hello,
          I set up a cluster of 5 wls (451) with the default values, on
          a LAN, on 5 computers, same config.
          They joined the cluster together without any problem.
          But, when calling mulitple methods on a Stateless session bean,
          the time between calls were really slow: 4 to 10 seconds.
          I tested with 2 Wls only in a cluster. It does work, really fast.
          1. What did I miss?
          2. How to configure wls so that it does not renew contacts to
          other wls too often?
          Thierry


The short answer to #1 is to set the following tuneables on the client
          side:
          java -Dweblogic.system.executeThreadCount=10
          -Dweblogic.system.percentSocketReaders=50 <your client program>
          The default settings are 5 and 33. Thus the number of socket reading
          threads on the client was restricted to a maximum of 2 (33% of 5). As
          you discovered, this can cause problems when there are > 3 servers in
          the cluster.
          This has been documented in the tuning guide which is part of the WL5.1
          docs.
          Srikant, [email protected], http://www.weblogic.com/, etc.
          Thierry Janaudy wrote:
          > Hello,
          >
          > I set up a cluster of 5 wls (451) with the default values, on
          > a LAN, on 5 computers, same config.
          >
          > They joined the cluster together without any problem.
          >
          > But, when calling mulitple methods on a Stateless session bean,
          > the time between calls were really slow: 4 to 10 seconds.
          >
          > I tested with 2 Wls only in a cluster. It does work, really fast.
          >
          > 1. What did I miss?
          >
          > 2. How to configure wls so that it does not renew contacts to
          > other wls too often?
          >
          > Thierry

Error connecting to Directory in BPM Enterprise on WLS

Has anyone seen this before?:
fuego.directory.exception.DirectoryNotAvailableException: Unable to connect to the Directory Service. If the problem persists, contact your system administrator.
     at fuego.directory.exception.DirectoryNotAvailableException.wrapDNAException(DirectoryNotAvailableException.java:33)
     at fuego.directory.jdbc.JDBCConnectionProvider.getEntry(JDBCConnectionProvider.java:81)
     at fuego.directory.jdbc.JDBCConnectionProvider.getEntry(JDBCConnectionProvider.java:34)
     at fuego.directory.provider.jdbc.JDBCPersistenceManager.getConnection(JDBCPersistenceManager.java:437)
     at fuego.directory.provider.jdbc.JDBCPersistenceManager.getPreparedStatement(JDBCPersistenceManager.java:566)
     at fuego.directory.provider.jdbc.JDBCObjectPropertiesAccessor.getPreparedStatementForFetchBinaryDirectoryProperty(JDBCObjectPropertiesAccessor.java:1052)
     at fuego.directory.provider.jdbc.JDBCObjectPropertiesAccessor.fetchAllDirectoryProperties(JDBCObjectPropertiesAccessor.java:393)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
     at $Proxy57.fetchAllDirectoryProperties(Unknown Source)
     at fuego.directory.provider.jdbc.JDBCDirectoryPreferencesAccessor.loadPreferences(JDBCDirectoryPreferencesAccessor.java:38)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at fuego.directory.provider.DirectorySessionImpl$AccessorProxy.invoke(DirectorySessionImpl.java:756)
     at $Proxy59.loadPreferences(Unknown Source)
     at fuego.directory.provider.DirectorySessionImpl.getDirectoryPreferences(DirectorySessionImpl.java:619)
     at fuego.directory.hybrid.ldap.LDAPDirectoryPreferences.createFromSession(LDAPDirectoryPreferences.java:35)
     at fuego.directory.hybrid.msad.MSADRepository.buildRepository(MSADRepository.java:55)
     at fuego.directory.hybrid.msad.MSADHybridFactory.createRepository(MSADHybridFactory.java:37)
     at fuego.directory.hybrid.ldap.DefaultLDAPHybridFactory.createOrganizationAccessor(DefaultLDAPHybridFactory.java:65)
     at fuego.directory.provider.DirectorySessionImpl.<init>(DirectorySessionImpl.java:103)
     at fuego.directory.provider.Factory.buildSession(Factory.java:239)
     at fuego.directory.hybrid.HybridFactory.buildSession(HybridFactory.java:51)
     at fuego.directory.provider.Factory.startSession(Factory.java:403)
     at fuego.directory.Directory.startAnonymousSession(Directory.java:214)
     at fuego.papi.impl.ProcessServiceFactoryImpl.obtainSchemaId(ProcessServiceFactoryImpl.java:193)
     at fuego.papi.impl.ProcessServiceFactoryImpl.create(ProcessServiceFactoryImpl.java:75)
     at fuego.papi.impl.ProcessServiceFactoryImpl.create(ProcessServiceFactoryImpl.java:63)
     at fuego.papi.ProcessService.create(ProcessService.java:335)
     at fuego.workspace.WorkspaceEnvironment.initPAPI(WorkspaceEnvironment.java:462)
     at fuego.workspace.WorkspaceEnvironment.initialize(WorkspaceEnvironment.java:138)
     at fuego.workspace.WorkspaceEnvironment.<init>(WorkspaceEnvironment.java:94)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
     at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
     at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
     at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
     at fuego.web.WebEnvironment.initialize(WebEnvironment.java:81)
     at fuego.workspace.context.WorkspaceContextListener.contextInitialized(WorkspaceContextListener.java:51)
     at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:465)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:175)
     at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1784)
     at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2999)
     at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1371)
     at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:468)
     at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     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:37)
     at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
     at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
     at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
     at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
     at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:16)
     at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:162)
     at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
     at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
     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.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: fuego.connector.ConnectorException: Connector [fuego:SQL:REMOTE_JDBC] caused an exception when getting a resource of type [0].
Detail:Connector [fuego:SQL:REMOTE_JDBC] caused an exception when getting a resource of type [0].
     at fuego.connector.ConnectorException.exceptionOnGetResource(ConnectorException.java:95)
     at fuego.connector.ConnectorTransaction.getResource(ConnectorTransaction.java:324)
     at fuego.connector.ConnectorTransaction.getResource(ConnectorTransaction.java:298)
     at fuego.directory.jdbc.JDBCConnectionProvider.getEntry(JDBCConnectionProvider.java:75)
     ... 78 more
Caused by: java.sql.SQLException: Unable to resolve 'XAFDIDS'. Resolved ''
     at fuego.connector.impl.RemoteJDBCConnector.getConnection(RemoteJDBCConnector.java:83)
     at fuego.connector.impl.RemoteJDBCConnector.getConnection(RemoteJDBCConnector.java:64)
     at fuego.connector.impl.RemoteJDBCConnector.getResource(RemoteJDBCConnector.java:147)
     at fuego.connector.ConnectorTransaction.getResource(ConnectorTransaction.java:319)
     ... 80 more
This is the first time I've seen this and the connection to the directory was fine up until seeing this error. No schema or naming changes have been made. All system user accounts are the same. Any help would be appreciated.
TIA,
IGS

Hi,
we are experimenting the same issue, a DirectoryNotAvailableException.
It happens randomly at runtime, and then the application is completely freezed and engine must be restarted.
We are completely puzzled here, as DB is fine, we increased connections on the connection pool and verified custom code.
Like in the initial post, we also have two binaries installation of ALBPM on the same server.
Do you think it's possible the two instances overwrites at runtime some properties (e.g. under /tmp) so that the directory configuration is messed up?
Did anyone experimente the same issue?
Thanks a lot

Technical Articles on Oracle BPM you might find useful

A friend pointed me to http://www.oracle.com/technology/products/bpm/obpm_articles.html on OTN. It currently has these articles:
Tuning Oracle BPM Directory Services
Oracle BPM Clustering Tips and Tricks
Oracle BPM Engine Troubleshooting Tips and Tricks
Oracle BPM PAPI Instance Cache Explained
Oracle BPM Single Sign On Configuration
Oracle BPM & Web Services Integration
Oracle BPM Enterprise Setups explained
Migrating ALBPM 5.7 to OBPM 10gR3

ADDM is just a sophisticated software module.
It does not use any hard-to-understand, magical and mathematical tricks but sticks to collected information(AWR) and some proven best practices.
So, i think it's no harm for you to consult ADDM report.
Every best practice has weakness, it can't deal every aspect of your DBMS things.
But, it's good start point and does not make stupid mistakes unlike human beings always do.
Another thing to note is that ADDM is a very large module and connected with AWR, Tuning Avisors, wait events, Advisories, blah blah blah~
You're not using ADDM correctly if you have no good concepts and experiences on these.

Accesing the clustered components ...load balancing!!!

          Friends ... here is my problem scenario. If any body has ideas, pl.share them.
          I have Webservices exposed on weblogic server. UI (in .NET ) accesses the webservices
          API on WLS.(bunch of EJBs are deployed on the WLS)
          Now I thought of converting the WLS to a clustered environment. So I created 2
          manged servers (on the same machine ..just to try initially). I have assigned
          unique port numbers to them.I tried mutlcast test .looks like the intra-cluster
          communication is okay.
          How can I do load balancing in this situation ? I could individually ping(look
          up) each of the manged server address. But how do i look up the cluster as a whole
          and not individual managed servers.(I mean load balancing ) I tried to access
          using the cluster address.It does not work .
          Do we need to have a plug-in /proxy to do the load balancing or is there any load
          balancing mechanism build in to WLS, so that I dont have to work with plug-ins
          and other stuff.
          precisely how do i access the individual components on different managed servers
          with a single address (which should then redistribute to individual managed servers
          in the cluster)
          Thanks for your help .


          Thanks Bijan. That was very useful information.
          I have one more question.
          While configuring the iis ,Which kind of forwarding should i use ? path forwarding/file
          forwarding ?(may not be relevant )
          (what should i give as end point in the web.config xml file? )
          When I had only one instance of WLS I used to give
          "http://localhost:7001/CCWebModule/services/XCWebServiceSoap"
          Right now I have two managed servers in cluster running on port 8001 and 9001.(while
          7001 is the admin server )
          I know i need to put this addresses in the iisproxy.ini as "WeblogicCluster".
          In this case what seem appropriate for "WLForward=" in the iisproxy.ini file
          Thanks
          Prasanth
          "Bijan Mohanty" <[email protected]> wrote:
          >
          >Prashanth,
          >
          >If you have deployed some webservices on WLS and later used clustering
          >of WLS,
          >you have essentialy multiple WSDLs. When you use a client to talk to
          >this webservice,
          >you have to loadbalance between the webservices on the managed server.
          >
          >When you use RMI to talk to a EJB deployed on clustered WLS, the replica
          >aware
          >stub has the clustering info. So the client's call to EJB is loadbalanced
          >by weblogic
          >automatically.
          >
          >In case of webservices, there is no such luck. You can use any of the
          >following
          >tricks.
          >1. Create webservice stubs in the client for each webservice in the managedserver
          >and laodbalance it in the client.
          >2. Use a proxy (Apache or IIS or Iplanet) that can loadbalance betwen
          >the webservices
          >and use that from the client.
          >3. Use a hardware loadbalancer for loadbalancing.
          >
          >4. Or use HttpClusterServlet. I had lots of problems using this in the
          >past and
          >don't recommend that.
          >
          >My suggestion will be to use the first option in the development and
          >use a combination
          >of 2 and 3 for production env. In the second option, although you get
          >the loadbalancing,
          >you have a single point of failure(i.e the proxy plugin). That's why,
          >the combination
          >of 2 and 3 works best.
          >
          >BTW the webservices are implemented as a webapp. When a call reaches
          >that servlet
          >the call stays in that app server instance, even if the EJBs are clustered.
          >That's
          >because weblogic optimizes the calls to reduce the marshalling/unmarshalling.
          >
          >Hope this helps.
          >
          >Bijan
          >
          >"prasanthbk" <[email protected]> wrote:
          >>
          >>Friends ... here is my problem scenario. If any body has ideas, pl.share
          >>them.
          >>
          >>I have Webservices exposed on weblogic server. UI (in .NET ) accesses
          >>the webservices
          >>API on WLS.(bunch of EJBs are deployed on the WLS)
          >>
          >>Now I thought of converting the WLS to a clustered environment. So I
          >>created 2
          >>manged servers (on the same machine ..just to try initially). I have
          >>assigned
          >>unique port numbers to them.I tried mutlcast test .looks like the intra-cluster
          >>communication is okay.
          >>
          >>How can I do load balancing in this situation ? I could individually
          >>ping(look
          >>up) each of the manged server address. But how do i look up the cluster
          >>as a whole
          >> and not individual managed servers.(I mean load balancing ) I tried
          >>to access
          >>using the cluster address.It does not work .
          >>
          >>Do we need to have a plug-in /proxy to do the load balancing or is there
          >>any load
          >>balancing mechanism build in to WLS, so that I dont have to work with
          >>plug-ins
          >>and other stuff.
          >>
          >>precisely how do i access the individual components on different managed
          >>servers
          >>with a single address (which should then redistribute to individual
          >managed
          >>servers
          >>in the cluster)
          >>
          >>
          >>Thanks for your help .
          >

Clustering rmi objects

Hi all,
I am looking for some information about clustering RMI objects. I have read as much
as I can find about it, not much seems to be in the wl docs.
I have read that if the server that bound the rmi object into jndi goes down, the
rmi server will no longer work. When I tested this out, the server seemed to continue
working and using the node in the cluster that was still running.
I am wondering what the difference between declaring the RMI object to be clusterable
and setting the WLContext.REPLICATE_BINDINGS flag to false when creating the context
to bind the RMI objects, and binding a seperate RMI object into the tree, one for
each node in the cluster.
is there some docs I can read about this? Thanks for any information you can give
me about this.
-chris

bwit <[email protected]> wrote:
In article <[email protected]>, [email protected]
says...
Hi all,Hi Chris.
I am looking for some information about clustering RMI objects. I haveread as much
as I can find about it, not much seems to be in the wl docs.
I have read that if the server that bound the rmi object into jndi goesdown, the
rmi server will no longer work. When I tested this out, the server seemedto continue
working and using the node in the cluster that was still running.If a server offering an RMI object via JNDI goes down the binding to
that object is removed from JNDI in all the other servers in the
cluster. Other replicas of that object may be available and will
continue to be used as you discovered.
I am wondering what the difference between declaring the RMI object tobe clusterable
and setting the WLContext.REPLICATE_BINDINGS flag to false when creatingthe context
to bind the RMI objects, and binding a seperate RMI object into the tree,one for
each node in the cluster.Marking the RMI object as clusterable causes WLS to generate a replica
aware stub for it. This stub is aware of all the replicas of the object
within the cluster and provides load balancing and failover. When you
bind a RMI object on multiple servers with REPLICATE_BINDINGS set to
false you have a bunch of individual, unrelated objects. Your clients
must contact the particular server running the objects and there will be
no load balancing or failover, all client calls will be serviced by the
object on the server which supplied the stub.
is there some docs I can read about this? Thanks for any informationyou can give
me about this.I thought the WLS RMI Programmer's Guide was pretty clear about how this
worked.
Well, you are right, the docs are clear on what they talk about, but as I mentioned,
when I marked the objects with REPLICATE_BINDINGS set to false, the client still
sent a comma delimited list of servers to create the InitialContext, and we still
observed load balancing, and what looked like failover. This is why we were confused,
we expected to see only one server do all the work (the first in the comma delimited
list), and for failures when that server was brought down. I will take a look at
our configuration and make sure we didnt make a mistake someplace in here.
Regards,
Bob
-chris

Apache 1.3.12 running with Raven SSL Proxy

          Hi All,
          I am currently having an issue clustering 2 WLS 5.1 sp8 app servers using Apache
          1.3.12 with the Raven SSL 1.4.3 plugin. (All on Solaris 7)
          Here is my scenario:
          The cluster "seems" to work. A session is processed fine on it's primary server,
          while the session information is replicated to the secondary server.
          Yet when we crash the primary server to test failover, all of the sessions on the
          primary server are lost and NOT processed by the secondary server. It is almost
          like the cookie was not updated to reflect that the primary had gone down, so the
          secondary server does not know it is now the primary.
          Any ideas?.. As long as the primary does not fail the system works fine.. so I know
          the sessions are being directed to the correct server the rest of the time, just
          not during failover.
          NOTE: I have had no problems with failover using Apache Stronghold using the mod_wl_ssl.so
          proxy, this problem only seems to occur with the Apache using Raven SSL and the mod_wl_ssl_raven.so
          proxy. Is there a bug with this proxy?
          Thank you for any ideas.
          -Nick


The Web server plug-ins do not natively support outbound SSL connections
yet(i.e. SSL from the plug-in to WebLogic). This is a feature for version
6.0. You can use SSL from the browser to Apache or from the browser to
WebLogic directly.
The majority of our customers use strict firewall rules to protect the
traffic between Apache and WebLogic. If they are paranoid, they use an SSL
proxy or a VPN product.
Thanks,
Michael
Michael Girdley
BEA Systems Inc
"Josh Kwan" <[email protected]> wrote in message
news:39d4e8a5$[email protected]..
>
Hello,
I want to know how to connect Apache 1.3.12 with mod_ssl to BEA WebLogic5.1.0 on Solaris via HTTPS. I have heard that this can only work over t3...
is that true? If so, how can it be done securely? If that isn't the case,
how can httpd.conf/weblogic.conf be configured on the Apache server to talk
to the WebLogic server on port 7002? Both of the machines I am using are
running Solaris 7 with necessary patches. I have installed SP5 for WebLogic
and I have copied mod_wl.so and mod_wl_ssl.o to the Apache server for
inclusion as modules.
>
The two servers communicate correctly over HTTP, but I want to be able toserve some JSPs via HTTPS from the WebLogic server through the Apache web
server. I have generated all the required CA and server certificates for
each server, and they both individually answer HTTPS requests, but do not
work when an HTTPS request is sent to the Apache server for a JSP that is
served from the WebLogic server. I read somewhere in the documentation for
5.1.0 that WebLogic will communicate via HTTPS to various web and proxy
servers.
>
Any help would be greatly appreciated... thanks!
Regards,
Josh Kwan
Sr. Systems Engineer
iXL

JNDI tree replicated to an external global naming service

Hi!
Is it possible to have a JNDI tree replicated to an external
global naming service? For instance, to merge two clusters
of WLS 5.1 servers from two different network zones?
Thanking you in advance,
Guillaume Bedard

Yes, you can use federation do achieve this but remember federation is
just putting a refence that points to the original JNDI provider and
doesn't really give you replication of the entire JNDI namespace.
Guillaume Bedard wrote:
Hi!
Can you elaborate as to what makes it impossible?
What if we "federate" the two clusters, which have their
own autonomous naming systems, by binding a reference to
these naming systems in another naming service?
Thanks,
Guillaume
"Raja Mukherjee" <[email protected]> wrote:
No
..raja
"Guillaume Bedard" <[email protected]> wrote in message
news:3cab4a00$[email protected]..
More specifically, I would like be able to join two clusters
(each having their own cluster-wide replicated naming tree)
by replicating their bindings into a global naming tree,
possibly hosted by a dedicated "jndi" server.
Guillaume
"Raja Mukherjee" <[email protected]> wrote:
My immediate response would be 'No', but I am confused as to what
are
you
trying to achieve?
..raja
"Guillaume Bedard" <[email protected]> wrote in message
news:3ca9cd9c$[email protected]..
Hi!
Is it possible to have a JNDI tree replicated to an external
global naming service? For instance, to merge two clusters
of WLS 5.1 servers from two different network zones?
Thanking you in advance,
Guillaume Bedard

Replicated jndi tree

We are running multiple WL servers (vers. 2.5.1 non-clustered)
registered to
different ports and would like to have the component names of one server
known to the other. Is there a way of doing this w/o having to
hard-code
that component A lives on machineX : port 999 or buying the clustering
option?

Yes, you can use federation do achieve this but remember federation is
just putting a refence that points to the original JNDI provider and
doesn't really give you replication of the entire JNDI namespace.
Guillaume Bedard wrote:
Hi!
Can you elaborate as to what makes it impossible?
What if we "federate" the two clusters, which have their
own autonomous naming systems, by binding a reference to
these naming systems in another naming service?
Thanks,
Guillaume
"Raja Mukherjee" <[email protected]> wrote:
No
..raja
"Guillaume Bedard" <[email protected]> wrote in message
news:3cab4a00$[email protected]..
More specifically, I would like be able to join two clusters
(each having their own cluster-wide replicated naming tree)
by replicating their bindings into a global naming tree,
possibly hosted by a dedicated "jndi" server.
Guillaume
"Raja Mukherjee" <[email protected]> wrote:
My immediate response would be 'No', but I am confused as to what
are
you
trying to achieve?
..raja
"Guillaume Bedard" <[email protected]> wrote in message
news:3ca9cd9c$[email protected]..
Hi!
Is it possible to have a JNDI tree replicated to an external
global naming service? For instance, to merge two clusters
of WLS 5.1 servers from two different network zones?
Thanking you in advance,
Guillaume Bedard

Conflict Error Handler Exception in Cluster

          Hi
          We bind some objects using rebind method to the JNDI in our weblogic servers.
          If we run one instance of weblogic server no problem but if we start another one
          server in the cluster it throughs conflict error handler exception. More over
          if we refresh one object instance in one server (by rebind) the new changes in
          the object doesn't reflect in other servers.


If you bind non clusterable objects in the jndi from two servers then you
          will run into conflicts.
          Basically in a cluster, two servers cannot provide the same service unless
          it is clusterable.
          WLS assumes that everything you bind into jndi is a service.
          -- Prasad
          "BSIL" <[email protected]> wrote in message
          news:3b94f93a$[email protected]..
          >
          > Hi
          > We bind some objects using rebind method to the JNDI in our weblogic
          servers.
          > If we run one instance of weblogic server no problem but if we start
          another one
          > server in the cluster it throughs conflict error handler exception. More
          over
          > if we refresh one object instance in one server (by rebind) the new
          changes in
          > the object doesn't reflect in other servers.

JMS Cluster error

Hi,
          We have clustered two WLS 6.1 instances which has two JMS servers one deployed on each server instance. There are two destinations(Queues) with same JNDI name but deployed under different JMS servers. We are getting this following error while starting the servers. We have seen messages going to both the destinations. What could be the problem here ?
          Thanks.
          Bijan
          <Cluster> <Conflict start: You tried to bind an object under the name obs.queue.OBSMSMQueueError in the JNDI tree. The object you have bound from 172.26.136.113 is non clusterable and you have tried to bind more than once from two or more servers. Such objects can only deployed from one server.>


On 12 Dec 2002 16:41:13 -0800, Bijan <[email protected]> wrote:
          The error says it all. The JNDI name of any "non-clustered" object
          within the cluster must be unique - queues, applications, etc.
          I suspect you are attempting to "distribute" the queue. Either
          upgrade to 6.1 or check out the "emulating distributed destinations
          in 6.1" section of the "JMS Performance white-paper" - available at
          dev2dev.bea.com.
          Tom, BEA
          >Hi,
          >
          >We have clustered two WLS 6.1 instances which has two JMS servers one deployed on each server instance. There are two destinations(Queues) with same JNDI name but deployed under different JMS servers. We are getting this following error while starting the servers. We have seen messages going to both the destinations. What could be the problem here ?
          >
          >Thanks.
          >
          >Bijan
          >
          >-----------------------------
          ><Cluster> <Conflict start: You tried to bind an object under the name obs.queue.OBSMSMQueueError in the JNDI tree. The object you have bound from 172.26.136.113 is non clusterable and you have tried to bind more than once from two or more servers. Such objects can only deployed from one server.>

NullPointerException when doing in-memory-replication

I am clustering two WLS instance sitting behind a WLS NSAPI proxy on one
          multi-home NT box, but when I tried to use in memory replication with adding
          the the following three properties:
          weblogic.httpd.clustering.enable=true
          weblogic.httpd.session.persistence=true
          weblogic.httpd.session.persistentStoreType=replicated
          I got the exception below. if I removed the session.persistence and
          session.persistentStoreType properties, the request will go through and both
          instance can serve request, but I lost the session information in fail over.
          Any hints will be appreciated!
          Qingxiang
          java.lang.NullPointerException
          at
          weblogic.servlet.internal.session.ReplicatedSession.setMaxInactiveInterval(R
          eplicatedSession.java:339)
          at
          weblogic.servlet.internal.session.SessionContext.getNewSessionInstance(Sessi
          onContext.java:322)
          at
          weblogic.servlet.internal.ServletRequestImpl.getNewSession(ServletRequestImp
          l.java:1104)
          at
          weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.j
          ava:1007)
          at
          weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.j
          ava:981)
          at
          weblogic.servlet.jsp.PageContextImpl.initialize(PageContextImpl.java:47)
          at
          weblogic.servlet.jsp.PageContextImpl.<init>(PageContextImpl.java:64)
          at
          weblogic.servlet.jsp.JspFactoryImpl.getPageContext(JspFactoryImpl.java:31)
          at jsp_servlet.index._jspService(index.java:105)
          at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
          at
          weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          :123)
          at
          weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          :141)
          at
          weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
          l.java:744)
          at
          weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
          l.java:692)
          at
          weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
          Manager.java:251)
          at
          weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:363)
          at
          weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:263)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)


I forgot to add that I am running WLS5.1 with sp3.
          "Qingxiang Ke" <[email protected]> wrote in message
          news:[email protected]...
          > I am clustering two WLS instance sitting behind a WLS NSAPI proxy on one
          > multi-home NT box, but when I tried to use in memory replication with
          adding
          > the the following three properties:
          >
          > weblogic.httpd.clustering.enable=true
          > weblogic.httpd.session.persistence=true
          > weblogic.httpd.session.persistentStoreType=replicated
          >
          > I got the exception below. if I removed the session.persistence and
          > session.persistentStoreType properties, the request will go through and
          both
          > instance can serve request, but I lost the session information in fail
          over.
          >
          > Any hints will be appreciated!
          >
          > Qingxiang
          >
          > java.lang.NullPointerException
          > at
          >
          weblogic.servlet.internal.session.ReplicatedSession.setMaxInactiveInterval(R
          > eplicatedSession.java:339)
          > at
          >
          weblogic.servlet.internal.session.SessionContext.getNewSessionInstance(Sessi
          > onContext.java:322)
          > at
          >
          weblogic.servlet.internal.ServletRequestImpl.getNewSession(ServletRequestImp
          > l.java:1104)
          > at
          >
          weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.j
          > ava:1007)
          > at
          >
          weblogic.servlet.internal.ServletRequestImpl.getSession(ServletRequestImpl.j
          > ava:981)
          > at
          > weblogic.servlet.jsp.PageContextImpl.initialize(PageContextImpl.java:47)
          > at
          > weblogic.servlet.jsp.PageContextImpl.<init>(PageContextImpl.java:64)
          > at
          > weblogic.servlet.jsp.JspFactoryImpl.getPageContext(JspFactoryImpl.java:31)
          > at jsp_servlet.index._jspService(index.java:105)
          > at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
          > at
          >
          weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          > :123)
          > at
          >
          weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java
          > :141)
          > at
          >
          weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
          > l.java:744)
          > at
          >
          weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImp
          > l.java:692)
          > at
          >
          weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContext
          > Manager.java:251)
          >
          > at
          >
          weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:363)
          > at
          > weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:263)
          > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >
          >
          >

BPM Clustering on WLS

Similar Messages

Maybe you are looking for