[jBPM] - New Installation of jBPM 5 using Existing Installation of JBoss 7 and Eclipse Indigo
by Patty Eilers
Patty Eilers [https://community.jboss.org/people/peilers64] created the discussion
"New Installation of jBPM 5 using Existing Installation of JBoss 7 and Eclipse Indigo"
To view the discussion, visit: https://community.jboss.org/message/649774#649774
--------------------------------------------------------------
I am trying to install jBPM 5 using my existing installations for JBoss7 and Eclipse Indigo. I have modified the build.properties file to point at my existing Eclipse installation and removed all mention of JBoss5.
In the installation documentation for jBPM the following instructions are presented:
h3. Installing
In the install dir, run installation script:
+ant install.guvnor.into.jboss+
+ant install.designer.into.jboss+
+ant install.jBPM-gwt-console.into.jboss+
+ant install.jBPM-eclipse.into.eclipse+
+ant install.drools-eclipse.into.eclipse+
The problem is that the last two tasks do not exist in the build.xml file. I have found a task called +install.droolsjbpm-eclipse.into.eclipse+ and another called +install.jBPM.runtime.+ I have run them both, as well as +install.demo.eclipse,+ but still neither the Guvnor or Console are accessible.
It would be great if someone could update the jBPM5 installer documentation. It seems that most people would already have both JBoss and Eclipse installed independently before they choose to install jBPM5. I have tried every flavor of JBPM5 installation--full/comprehensive and pieces parts--but I remain unsuccessful in getting access to the Guvnor and Console.
Ready to give up entirely on jBPM and head over to take a look at Intalio....
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/649774#649774]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
11 years, 12 months
[jBPM] - How can I set the size of designer
by amir rezei
amir rezei [https://community.jboss.org/people/a_rezaeinia] created the discussion
"How can I set the size of designer"
To view the discussion, visit: https://community.jboss.org/message/730717#730717
--------------------------------------------------------------
Hi ,
I used standalone designer , in my xhtml i used an ifram tag such as below :
<iframe id="myIframe"
src="localhost:8080/drools-guvnor/org.drools.guvnor.Guvnor/standaloneEditorServlet?assetsUUIDs="your-uuid-for-example"&client=oryx" domain="localhost" style="width: 100%; height: 580px" />
in this case there is no problem to open the designer into the iframe tag .
but my issue is the size of html that will be load in my iframe , I visited the HTML source code of the browser after loading page ,and saw that in my iframe , there is another iframe that has the size of (width = 1600px , height = 1000px) , so this cause to scroll my iFrame ,the desinger has its own scroll and my iFrame has scroll so it is a double-scroll problem
here is an image show the double-scroll problem
https://community.jboss.org/servlet/JiveServlet/showImage/2-730717-18420/... https://community.jboss.org/servlet/JiveServlet/downloadImage/2-730717-18...
this is a bug , because if you scroll down or srcoll right (according to the above picture) and click on canvas , the convas hope to the left-upper of iFrame to show the top and right menu.
i want to know is there any way to determine the size of internal iFrame ?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/730717#730717]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
11 years, 12 months
[jBPM] - ORA 00060 - Deadlock while using Oracle + JBPM 5.2
by Sukumaran Raghavan
Sukumaran Raghavan [https://community.jboss.org/people/suku_1983] created the discussion
"ORA 00060 - Deadlock while using Oracle + JBPM 5.2"
To view the discussion, visit: https://community.jboss.org/message/729707#729707
--------------------------------------------------------------
Hi,
I am using JBPM 5.2 for an application. I am facing issues when multiple threads complete work items parallely. These lead the process to completion and while completing, processInstanceInfo and a few other tables have DML statements executed. I use Oracle DB for the backend !
Exception trace below.
Hoping someone can help. Do let me know what options i have. Things i gave tried
- Increased INITRANS for the tables to 25 (default is 1) - This usually helps in ORA-0060 errors. However not this time :(
====================
16:17:54,389 INFO [stdout] (EJB default - 3) Hibernate: update SessionInfo set lastModificationDate=?, rulesByteArray=?, startDate=?, OPTLOCK=? where id=? and OPTLOCK=?
16:17:54,396 INFO [stdout] (EJB default - 4) Hibernate: insert into NodeInstanceLog (log_date, nodeId, nodeInstanceId, nodeName, processId, processInstanceId, type, id) values (?, ?, ?, ?, ?, ?, ?, ?)
16:17:54,462 INFO [stdout] (EJB default - 3) Hibernate: insert into NodeInstanceLog (log_date, nodeId, nodeInstanceId, nodeName, processId, processInstanceId, type, id) values (?, ?, ?, ?, ?, ?, ?, ?)
16:17:54,469 INFO [stdout] (EJB default - 4) Hibernate: insert into NodeInstanceLog (log_date, nodeId, nodeInstanceId, nodeName, processId, processInstanceId, type, id) values (?, ?, ?, ?, ?, ?, ?, ?)
16:17:54,535 INFO [stdout] (EJB default - 3) Hibernate: insert into NodeInstanceLog (log_date, nodeId, nodeInstanceId, nodeName, processId, processInstanceId, type, id) values (?, ?, ?, ?, ?, ?, ?, ?)
16:17:54,541 INFO [stdout] (EJB default - 4) Hibernate: insert into NodeInstanceLog (log_date, nodeId, nodeInstanceId, nodeName, processId, processInstanceId, type, id) values (?, ?, ?, ?, ?, ?, ?, ?)
16:17:54,612 INFO [stdout] (EJB default - 3) Hibernate: insert into NodeInstanceLog (log_date, nodeId, nodeInstanceId, nodeName, processId, processInstanceId, type, id) values (?, ?, ?, ?, ?, ?, ?, ?)
16:17:54,620 INFO [stdout] (EJB default - 4) Hibernate: update ProcessInstanceLog set end_date=?, processId=?, processInstanceId=?, start_date=? where id=?
16:17:54,684 INFO [stdout] (EJB default - 3) Hibernate: update ProcessInstanceLog set end_date=?, processId=?, processInstanceId=?, start_date=? where id=?
16:17:54,693 INFO [stdout] (EJB default - 4) Hibernate: delete from EventTypes where InstanceId=?
16:17:54,755 INFO [stdout] (EJB default - 3) Hibernate: delete from EventTypes where InstanceId=?
16:17:54,765 INFO [stdout] (EJB default - 4) Hibernate: delete from ProcessInstanceInfo where InstanceId=? and OPTLOCK=?
16:17:54,827 INFO [stdout] (EJB default - 3) Hibernate: delete from ProcessInstanceInfo where InstanceId=? and OPTLOCK=?
16:17:58,429 WARN [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (EJB default - 4) SQL Error: 60, SQLState: 61000
16:17:58,429 ERROR [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] (EJB default - 4) ORA-00060: deadlock detected while waiting for resource
16:17:58,431 WARN [com.arjuna.ats.arjuna] (EJB default - 4) ARJUNA012125: TwoPhaseCoordinator.beforeCompletion - failed for SynchronizationImple< 0:ffff11d11224:-5d726fdb:4f861b4f:1fd, org.hibernate.engine.transaction.synchronization.internal.RegisteredSynchronization@7c07a0c >: javax.persistence.PersistenceException: org.hibernate.exception.LockAcquisitionException: ORA-00060: deadlock detected while waiting for resource
at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1361) [hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Final]
at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1289) [hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Final]
at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1295) [hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Final]
at org.hibernate.ejb.AbstractEntityManagerImpl$CallbackExceptionMapperImpl.mapManagedFlushFailure(AbstractEntityManagerImpl.java:1481) [hibernate-entitymanager-4.0.1.Final.jar:4.0.1.Final]
at org.hibernate.engine.transaction.synchronization.internal.SynchronizationCallbackCoordinatorImpl.beforeCompletion(SynchronizationCallbackCoordinatorImpl.java:109) [hibernate-core-4.0.1.Final.jar:4.0.1.Final]
at org.hibernate.engine.transaction.synchronization.internal.RegisteredSynchronization.beforeCompletion(RegisteredSynchronization.java:53) [hibernate-core-4.0.1.Final.jar:4.0.1.Final]
at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.beforeCompletion(SynchronizationImple.java:76)
at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.beforeCompletion(TwoPhaseCoordinator.java:273)
at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:93)
at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:164)
at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1165)
at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:117)
at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:75)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.endTransaction(CMTTxInterceptor.java:92) [jboss-as-ejb3-7.1.0.Final.jar:7.1.0.Final]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:232) [jboss-as-ejb3-7.1.0.Final.jar:7.1.0.Final]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:304) [jboss-as-ejb3-7.1.0.Final.jar:7.1.0.Final]
at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:190) [jboss-as-ejb3-7.1.0.Final.jar:7.1.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) [jboss-as-ejb3-7.1.0.Final.jar:7.1.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) [jboss-as-ejb3-7.1.0.Final.jar:7.1.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) [jboss-as-ee-7.1.0.Final.jar:7.1.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ee.component.TCCLInterceptor.processInvocation(TCCLInterceptor.java:45) [jboss-as-ee-7.1.0.Final.jar:7.1.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:165) [jboss-as-ee-7.1.0.Final.jar:7.1.0.Final]
at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:173) [jboss-as-ee-7.1.0.Final.jar:7.1.0.Final]
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288) [jboss-invocation-1.1.1.Final.jar:1.1.1.Final]
at org.jboss.as.ejb3.component.interceptors.AsyncVoidInterceptorFactory$Task.run(AsyncVoidInterceptorFactory.java:75) [jboss-as-ejb3-7.1.0.Final.jar:7.1.0.Final]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_26]
at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_26]
at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Caused by: org.hibernate.exception.LockAcquisitionException: ORA-00060: deadlock detected while waiting for resource
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/729707#729707]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years
[Beginner's Corner] - JBOSS AS 7.0.2 : Exception in thread "Controller Boot Thread"
by Tan Mariani
Tan Mariani [https://community.jboss.org/people/mariani] created the discussion
"JBOSS AS 7.0.2 : Exception in thread "Controller Boot Thread""
To view the discussion, visit: https://community.jboss.org/message/732637#732637
--------------------------------------------------------------
I try to setup JBOSS AS.7.0.2.Final on Centos 6.2. I used java 1.6.31
When I try to run ./standalone.sh, I got this following error.
Can anyone help me? Do I do something wrong
=========================================================================
JBoss Bootstrap Environment
JBOSS_HOME: /opt/jboss-as-7.0.2.Final
JAVA: /usr/java/jdk1.6.0_31/bin/java
JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true
=========================================================================
16:47:56,514 INFO org.jboss.modules org.jboss.modules JBoss Modules version 1.0.2.GA
16:47:56,792 INFO org.jboss.msc org.jboss.msc JBoss MSC version 1.0.1.GA
16:47:56,848 INFO org.jboss.as org.jboss.as JBoss AS 7.0.2.Final "Arc" starting
16:47:57,079 ERROR https://community.jboss.org/message/732637#732637#732637/stderr JBOSS AS 7.0.2 : Exception in thread "Controller Boot Thread" Exception in thread "Controller Boot Thread" java.lang.RuntimeException: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to parse configuration
16:47:57,080 ERROR https://community.jboss.org/message/732637#732637#732637/stderr JBOSS AS 7.0.2 : Exception in thread "Controller Boot Thread" at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:89)
16:47:57,080 ERROR https://community.jboss.org/message/732637#732637#732637/stderr JBOSS AS 7.0.2 : Exception in thread "Controller Boot Thread" at java.lang.Thread.run(Thread.java:662)
16:47:57,080 ERROR https://community.jboss.org/message/732637#732637#732637/stderr JBOSS AS 7.0.2 : Exception in thread "Controller Boot Thread" Caused by: org.jboss.as.controller.persistence.ConfigurationPersistenceException: Failed to parse configuration
16:47:57,080 ERROR https://community.jboss.org/message/732637#732637#732637/stderr JBOSS AS 7.0.2 : Exception in thread "Controller Boot Thread" at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:115)
16:47:57,080 ERROR https://community.jboss.org/message/732637#732637#732637/stderr JBOSS AS 7.0.2 : Exception in thread "Controller Boot Thread" at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:104)
16:47:57,081 ERROR https://community.jboss.org/message/732637#732637#732637/stderr JBOSS AS 7.0.2 : Exception in thread "Controller Boot Thread" at org.jboss.as.server.ServerService.boot(ServerService.java:195)
16:47:57,081 ERROR https://community.jboss.org/message/732637#732637#732637/stderr JBOSS AS 7.0.2 : Exception in thread "Controller Boot Thread" at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:83)
16:47:57,081 ERROR https://community.jboss.org/message/732637#732637#732637/stderr JBOSS AS 7.0.2 : Exception in thread "Controller Boot Thread" ... 1 more
16:47:57,081 ERROR https://community.jboss.org/message/732637#732637#732637/stderr JBOSS AS 7.0.2 : Exception in thread "Controller Boot Thread" Caused by: java.lang.RuntimeException: Unable to determine a default name based on the local host name
16:47:57,081 ERROR https://community.jboss.org/message/732637#732637#732637/stderr JBOSS AS 7.0.2 : Exception in thread "Controller Boot Thread" at org.jboss.as.controller.parsing.CommonXml.getDefaultName(CommonXml.java:184)
16:47:57,081 ERROR https://community.jboss.org/message/732637#732637#732637/stderr JBOSS AS 7.0.2 : Exception in thread "Controller Boot Thread" at org.jboss.as.controller.parsing.StandaloneXml.readServerElement(StandaloneXml.java:137)
16:47:57,081 ERROR https://community.jboss.org/message/732637#732637#732637/stderr JBOSS AS 7.0.2 : Exception in thread "Controller Boot Thread" at org.jboss.as.controller.parsing.StandaloneXml.readElement(StandaloneXml.java:91)
16:47:57,082 ERROR https://community.jboss.org/message/732637#732637#732637/stderr JBOSS AS 7.0.2 : Exception in thread "Controller Boot Thread" at org.jboss.as.controller.parsing.StandaloneXml.readElement(StandaloneXml.java:79)
16:47:57,082 ERROR https://community.jboss.org/message/732637#732637#732637/stderr JBOSS AS 7.0.2 : Exception in thread "Controller Boot Thread" at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:100)
16:47:57,082 ERROR https://community.jboss.org/message/732637#732637#732637/stderr JBOSS AS 7.0.2 : Exception in thread "Controller Boot Thread" at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:59)
16:47:57,082 ERROR https://community.jboss.org/message/732637#732637#732637/stderr JBOSS AS 7.0.2 : Exception in thread "Controller Boot Thread" at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:107)
16:47:57,082 ERROR https://community.jboss.org/message/732637#732637#732637/stderr JBOSS AS 7.0.2 : Exception in thread "Controller Boot Thread" ... 4 more
16:47:57,082 ERROR https://community.jboss.org/message/732637#732637#732637/stderr JBOSS AS 7.0.2 : Exception in thread "Controller Boot Thread" Caused by: java.net.UnknownHostException: DEVK-TEST-3: DEVK-TEST-3
16:47:57,083 ERROR https://community.jboss.org/message/732637#732637#732637/stderr JBOSS AS 7.0.2 : Exception in thread "Controller Boot Thread" at java.net.InetAddress.getLocalHost(InetAddress.java:1360)
16:47:57,084 ERROR https://community.jboss.org/message/732637#732637#732637/stderr JBOSS AS 7.0.2 : Exception in thread "Controller Boot Thread" at org.jboss.as.controller.parsing.CommonXml.getDefaultName(CommonXml.java:182)
16:47:57,084 ERROR https://community.jboss.org/message/732637#732637#732637/stderr JBOSS AS 7.0.2 : Exception in thread "Controller Boot Thread" ... 10 more
Thanks before
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/732637#732637]
Start a new discussion in Beginner's Corner at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years
[jBPM] - A few jbpm5 architectural/design questions
by Kishore Jaladi
Kishore Jaladi [https://community.jboss.org/people/kishorejaladi] created the discussion
"A few jbpm5 architectural/design questions"
To view the discussion, visit: https://community.jboss.org/message/732732#732732
--------------------------------------------------------------
I am evaluating using JBPM5 for our work flows in e-commerce context. I did some reading online. Still got a few questions. Please help
* We use MongoDB as our database. I understand that JBPM5 supports JPA persistence. Is it safe to assume that with any ORM provider like Dataneucleaus that provides a JPA layer for MongoDB can used for Work Flow Engine persistence? ref: http://sasajovancic.blogspot.com/2011/06/use-jpa-with-mongodb-and-datanuc... http://sasajovancic.blogspot.com/2011/06/use-jpa-with-mongodb-and-datanuc...
* Is it possible to do on-demand process-instance or ksession persistence? If so, is there any sample code?
* I read that the work flow engine uses the single thread (the thread that starts the process/fires an event) to execute the entire process...no real multi-threading. What happens when the process instance and/or session is persisted at safe-points (or manually)?..does the thread end/return back to main program?
* If I have to start multiple (many) processes at the same time from the main program, do I have to start them all in different threads? do I have to model my own thread pool?
* I have a situation where, the main program receives a message on http and the http response thread have to be returned with status 200 OK after persisting the message. If I want the message persistence as a part of the process, how can I achieve this? I mean, I cannot return the main thread just after the first (persistence) node of the process, right?...how can make the rest of the process continue?
Thanks in advance
-Kishore
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/732732#732732]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years
[JBoss Tools] - Runtime Environment 7.1 Default Config 3.3M5
by Mark Rosenthal
Mark Rosenthal [https://community.jboss.org/people/mwr0707] created the discussion
"Runtime Environment 7.1 Default Config 3.3M5"
To view the discussion, visit: https://community.jboss.org/message/647007#647007
--------------------------------------------------------------
On 3.3M5, I've created a 7.1 runtime env and set the JRE to a Java 1.6 installation.
When creating a new Dynamic Web Project, the project configuration "Default JBoss 7.1 runtime configuration" insists on configuring a non-existent (in my case) 1.7 JRE by default.
The symptoms are deployable class files built at 1.7 which fail at deployment when a 1.7 JRE is not present.
This can be worked around by modifying the default configuration during project creation. After project creation, this can be worked around by changing the project Java Facet and Compiler Compliance Level.
The desired behavior is for the "Default JBoss 7.1 runtime configuration" during project creation to utilize the setting in the configured JBoss 7.1 Server runtime by default.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/647007#647007]
Start a new discussion in JBoss Tools at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years
[Datasource Configuration] - Maximum Database connection issue in JBoss 5.1
by Anil Mathew
Anil Mathew [https://community.jboss.org/people/amathewjboss1] created the discussion
"Maximum Database connection issue in JBoss 5.1"
To view the discussion, visit: https://community.jboss.org/message/731958#731958
--------------------------------------------------------------
Hi,
We have a big application which uses JBoss 5.1 and is running on Linux servers. Our production environments has 20 web servers (which runs on Apache/Tomcat) which talks to 4 app servers (which runs on JBoss 5.1 in one cluster) with a Oracle 9i database.
As far as the JBoss configuration is concerned, we are using pooledha invoker as our EJB calls are remote calls. Also <max-pool-size> in the oracle-ds.xml is set to 275. The ha-legacy-jboss-beans.xml has the following setup for the pooledInvokerHA:
<bean name="PooledInvokerHA"
class="org.jboss.invocation.pooled.server.PVOPooledInvokerHA">
<depends>jboss:service=TransactionManager</depends>
<depends>HAPartition</depends>
<annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss:service=invoker,type=pooledha", exposedInterface=org.jboss.invocation.pooled.server.PooledInvokerMBean.class, registerDirectly=true)</annotation>
<property name="numAcceptThreads">1</property>
<property name="maxPoolSize">800</property>
<property name="clientMaxPoolSize">300</property>
<property name="socketTimeout">150000</property>
<property name="serverBindAddress">
<value-factory bean="ServiceBindingManager" method="getStringBinding"
parameter="jboss:service=invoker,type=pooledha"/>
</property>
<property name="serverBindPort">
<value-factory bean="ServiceBindingManager" method="getIntBinding"
parameter="jboss:service=invoker,type=pooledha"/>
</property>
<property name="clientConnectAddress">${jboss.bind.address}</property>
<property name="clientConnectPort">0</property>
<property name="enableTcpNoDelay">false</property>
<property name="transactionManagerService">jboss:service=TransactionManager</property>
</bean>
The issue we are facing is that when we have an average/high load, we are reaching the "InUseConnectionCount" to 275 very quickly. When we look at the database side, we really don't have any traffic. So once we reached the maximum connection mark, the app servers started to get slow and then FULL GC and then it will crash. An interesting point is that during this situation just recycling the app servers doesn't kill the connections though.i.e we end up in recycling the complete web servers so that all the connections will be released. We spend many hours trying to figure out the issue, but no luck. So any thoughts on this issue will be appreciated.
Thanks
Anil Mathew
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/731958#731958]
Start a new discussion in Datasource Configuration at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
12 years
