[EJB3] - JBoss 6, EJB and Web Application dependency
by Paata Lominadze
Paata Lominadze [https://community.jboss.org/people/paata] created the discussion
"JBoss 6, EJB and Web Application dependency"
To view the discussion, visit: https://community.jboss.org/message/822409#822409
--------------------------------------------------------------
Hello team,
I have 2 application on jboss 6 :
1. EJB application which has multiple ejb components and entity beans.
2. Web application which use GWT. I want to call ejb components from GWT Servlets.
I want to deploy both of them into jboss 6 server (standalone mode).
EJB jar deployment has no any problem. it works fine.
Now I want to deploy War file.
if I put EJB jar file into WAR-PROJECT/WEB-INF/lib. it throws an error. EJB Components trying to deploy on next time, But without this library I got an ClassNotFoundException.
I want EJB application to be as a library for Web Application.
How I can do it ?
Also I don't want to make EAR Project for some reasons.
I want this 2 application separately into one jboss application sever.
Thant In Advance,
Paata.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/822409#822409]
Start a new discussion in EJB3 at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 11 months
[Beginner's Corner] - implicit modules in development
by jsm3031
jsm3031 [https://community.jboss.org/people/jsm3031] created the discussion
"implicit modules in development"
To view the discussion, visit: https://community.jboss.org/message/822098#822098
--------------------------------------------------------------
Hi,
I am used to eclipse doing a lot for me, so I'm trying to learn more about app servers, deployment, etc. I also switched to Intellij for a trial.
So, I have read up as much as I can, don't have enough time these days and appreciate help. I read the stuff on implicit dependencies in jboss, so for example if I use the @PersistenceUnit the dependencies will be added, but this doesn't work in development in the IDE, and in Intellij I have to use Maven dependency in the pom file or get intellij to download the jars into the projects lib folder or else the IDE can't resolve anything and it won't compile. These are easy enough solutions, but what i don't get is, it seems like the inclusion of these implicit modules by jboss is a deploy time thing (I also read you specify them in the manifest file) but if you have to use maven or download and add them to your lib directory to be able to develop then what's the difference between using tomcat and doing that then deploying them together or using jboss or other java ee compliant server (which i read that the benifit of using them is they come with all that stuff included)? Either way you have to get the dependencies into your project manually to develop. The only thing using the full featured ee compliant server seems to get you is not having to actually include them in the lib folder of the deployment artifact.
At least that's what I have observed. I like figuring out these details but I just don't have the time these days and I'm quite curious about this.
Thanks
jon
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/822098#822098]
Start a new discussion in Beginner's Corner at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 11 months
[EJB3] - Job manager/dispatcher pattern
by Bernard Labno
Bernard Labno [https://community.jboss.org/people/blabno] created the discussion
"Job manager/dispatcher pattern"
To view the discussion, visit: https://community.jboss.org/message/822316#822316
--------------------------------------------------------------
Hello
In my app there are some long running tasks that can be started from web front-end. Admin should see progress of those tasks in the same front-end.
What is the best approach to implement this?
Right now I have 1 ApplicationScoped JobManager and ~20 task executors running on separate JVM's (simple standalone apps). Those executors periodically (fast) pool JobManager for jobs through JAX-RS.
JobManager must know which job is executed by which executor so that it's not done twice. Also that information must be persistent (in case of JobManager crash/restart).
{code:lang=java}
public String assignJob(String executorId) {
Job job = get1stUnassignedJobFromDB();
job.setExecutorId(executorId);
saveJobInDB(job);
return job.getId();
}{code}
The problem is that sometimes executor 1 gets job A, the transaction doesn't get commited yet and the executor 2 also get's the same job.
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/822316#822316]
Start a new discussion in EJB3 at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 11 months
[jBPM] - Can't find persistence unit org.jbpm.domain in jbpm-console.war while setting up jBPM 6.0 Beta2 to use MySQL
by Samuele Mezzasalma
Samuele Mezzasalma [https://community.jboss.org/people/samuele_m] created the discussion
"Can't find persistence unit org.jbpm.domain in jbpm-console.war while setting up jBPM 6.0 Beta2 to use MySQL"
To view the discussion, visit: https://community.jboss.org/message/822294#822294
--------------------------------------------------------------
Hi everybody.
I'm a complete newbie for what concern business processes and jBPM so I ask for help.
I installed jBPM 6.0 Beta2 full installer but it's almost two weeks that I'm trying to set up jBPM 6.0 Beta2 to use MySQL and I haven't come up with anything.
I followed this 5.4 guide https://community.jboss.org/docs/DOC-48374 Set up jBPM 5.4 Final Installer to use MySQL - or how to run section 3.7 of the User Guide but it didn't seem to work for me.
I closely followed these four steps:
h5. 1)Set up MySQL
mysql> CREATE SCHEMA IF NOT EXISTS jbpm5;
mysql> CREATE USER 'jbmp5'@'localhost' IDENTIFIED BY 'jbpm5';
mysql> GRANT ALL PRIVILEGES ON jbpm5.* TO 'jbpm5'@'localhost';
mysql> CREATE SCHEMA IF NOT EXISTS task;
mysql> CREATE USER 'task'@'localhost' IDENTIFIED BY 'task';
mysql> GRANT ALL PRIVILEGES ON task.* TO 'task'@'localhost;
h5. 2)Set up jBPM
h6. build.properties
# data base related properties
db.driver.jar=${install.home}/db/driver/${db.driver.jar.name}
db.driver.module.dir=${jboss.home}/modules/${db.driver.module.prefix}/main/
# default is H2
# db.name=h2
# db.driver.jar.name=${db.name}.jar
# db.driver.download.url=http://repo1.maven.org/maven2/com/h2database/h2/${...
#other options are mysql
db.name=mysql
db.driver.module.prefix=com/mysql
db.driver.jar.name=${db.name}-connector-java.jar
db.driver.download.url=https://repository.jboss.org/nexus/service/local/r....
h6. build.xml
<!-- Start Demo (DB) -->
<target name="start.demo.db" depends="start.jboss, start.eclipse" />
<!-- Start Demo (DB, No Eclipse) -->
<target name="start.demo.db.noeclipse" depends="start.jboss" />
<!-- Stop Demo (DB)-->
<target name="stop.demo.db" depends="stop.jboss" />
h6. db/jbpm-persistence-JPA2.xml
<property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect" />
h6. db/task-persistence-JPA2.xml
<property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect"/>
h6. standalone.xml
<datasource jndi-name="java:jboss/datasources/ExampleDS" pool-name="ExampleDS" enabled="true" use-java-context="true">
<connection-url>jdbc:mysql://localhost:3306/task</connection-url>
<driver>mysql</driver>
<security>
<user-name>task</user-name>
<password>task</password>
</security>
</datasource>
<datasource jta="true" jndi-name="java:jboss/datasources/jbpmDS" pool-name="H2DS" enabled="true" use-java-context="true" use-ccm="true">
<connection-url>jdbc:mysql://localhost:3306/jbpm6</connection-url>
<driver>mysql</driver>
<pool>
<min-pool-size>1</min-pool-size>
<max-pool-size>4</max-pool-size>
<prefill>false</prefill>
<use-strict-min>false</use-strict-min>
<flush-strategy>FailingConnectionOnly</flush-strategy>
</pool>
<security>
<user-name>jbpm6</user-name>
<password>jbpm6</password>
</security>
<validation>
<check-valid-connection-sql>SELECT 1</check-valid-connection-sql>
<validate-on-match>false</validate-on-match>
<background-validation>false</background-validation>
</validation>
</datasource>
<datasource jta="true" jndi-name="java:jboss/datasources/BamAppDS" pool-name="BamAppDS" enabled="true" use-java-context="true" use-ccm="true">
<connection-url>jdbc:mysql://localhost:3306/jbpm6</connection-url>
<driver>mysql</driver>
<pool>
<min-pool-size>1</min-pool-size>
<max-pool-size>4</max-pool-size>
<prefill>false</prefill>
<use-strict-min>false</use-strict-min>
<flush-strategy>FailingConnectionOnly</flush-strategy>
</pool>
<security>
<user-name>jbpm6</user-name>
<password>jbpm6</password>
</security>
<validation>
<check-valid-connection-sql>SELECT 1</check-valid-connection-sql>
<validate-on-match>false</validate-on-match>
<background-validation>false</background-validation>
</validation>
</datasource>
<drivers>
<driver name="mysql" module="com.mysql">
<xa-datasource-class>com.mysql.jdbc.jdbc2.optional.MysqlXADataSource</xa-datasource-class>
</driver>
</drivers>
h6. task-service/resources/META-INF/persistence.xml
<property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect"/>
<property name="hibernate.connection.driver_class" value="org.jdbc.Driver"/>
<property name="hibernate.connection.url" value="jdbc:mysql:://localhost:3306/task" />
<property name="hibernate.connection.username" value="task"/>
<property name="hibernate.connection.password" value="task"/>
<property name="hibernate.connection.autocommit" value="false" />
<property name="hibernate.max_fetch_depth" value="3"/>
<property name="hibernate.hbm2ddl.auto" value="create" />
<property name="hibernate.show_sql" value="false" />
h6. lib/jbpm-console-6.0.0.Beta2.war/WEB-INF/classes/META-INF/persistence.xml
<property name="hibernate.dialect" value="org.hibernate.dialect.MySQLialect" />
<property name="hibernate.max_fetch_depth" value="3" />
<property name="hibernate.hbm2ddl.auto" value="update" />
<property name="hibernate.show_sql" value="false" />
<!-- BZ 841786: AS7/EAP 6/Hib 4 uses new (sequence) generators which seem to cause problems -->
<property name="hibernate.id.new_generator_mappings" value="false" />
<property name="hibernate.transaction.jta.platform" value="org.hibernate.service.jta.platform.internal.JBossAppServerJtaPlatform" />
</properties>
h5. 3)Install jBPM
ant install.demo.noeclipse
h5. 4)Run the demo
ant start.demo.db.noeclipse
I attach to this post all modified files, server.log and jbpm-console.war log.
h6. jbpm-console.war.failed
{"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"jbpm-console.war\".WeldService" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"jbpm-console.war\".WeldService: org.jboss.weld.exceptions.DeploymentException: Exception List with 1 exceptions:
Exception 0 :
java.lang.IllegalArgumentException: JBAS016069: Error injecting persistence unit into CDI managed bean. Can't find a persistence unit named org.jbpm.domain in deployment jbpm-console.war
at org.jboss.as.weld.services.bootstrap.WeldJpaInjectionServices.getScopedPUName(WeldJpaInjectionServices.java:96)
at org.jboss.as.weld.services.bootstrap.WeldJpaInjectionServices.resolvePersistenceUnit(WeldJpaInjectionServices.java:78)
at org.jboss.weld.util.Beans.injectEEFields(Beans.java:631)
at org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget$1$1.proceed(ManagedBean.java:160)
at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48)
at org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget$1.work(ManagedBean.java:157)
at org.jboss.weld.bean.ManagedBean$FixInjectionPoint.run(ManagedBean.java:131)
at org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget.inject(ManagedBean.java:153)
at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:290)
at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:107)
at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:616)
at org.jboss.weld.bean.AbstractReceiverBean.getReceiver(AbstractReceiverBean.java:73)
at org.jboss.weld.bean.ProducerMethod$1.produce(ProducerMethod.java:131)
at org.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:299)
at org.jboss.weld.context.unbound.DependentContextImpl.get(DependentContextImpl.java:61)
at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:616)
at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:681)
at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:118)
at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:703)
at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:712)
at org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget$1$1.proceed(ManagedBean.java:161)
at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48)
at org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget$1.work(ManagedBean.java:157)
at org.jboss.weld.bean.ManagedBean$FixInjectionPoint.run(ManagedBean.java:131)
at org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget.inject(ManagedBean.java:153)
at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:290)
at org.jboss.weld.context.unbound.DependentContextImpl.get(DependentContextImpl.java:61)
at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:616)
at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:681)
at org.jboss.weld.injection.FieldInjectionPoint.inject(FieldInjectionPoint.java:118)
at org.jboss.weld.util.Beans.injectBoundFields(Beans.java:703)
at org.jboss.weld.util.Beans.injectFieldsAndInitializers(Beans.java:712)
at org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget$1$1.proceed(ManagedBean.java:161)
at org.jboss.weld.injection.InjectionContextImpl.run(InjectionContextImpl.java:48)
at org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget$1.work(ManagedBean.java:157)
at org.jboss.weld.bean.ManagedBean$FixInjectionPoint.run(ManagedBean.java:131)
at org.jboss.weld.bean.ManagedBean$ManagedBeanInjectionTarget.inject(ManagedBean.java:153)
at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:290)
at org.jboss.weld.context.AbstractContext.get(AbstractContext.java:107)
at org.jboss.weld.bean.proxy.ContextBeanInstance.getInstance(ContextBeanInstance.java:90)
at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:79)
at org.jbpm.services.task.impl.TaskDeadlinesServiceImpl$Proxy$_$$_WeldClientProxy.toString(TaskDeadlinesServiceImpl$Proxy$_$$_WeldClientProxy.java)
at org.kie.commons.services.cdi.StartupBeanExtension.runPostConstruct(StartupBeanExtension.java:81)
at org.kie.commons.services.cdi.StartupBeanExtension.afterDeploymentValidation(StartupBeanExtension.java:69)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:264)
at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:52)
at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:137)
at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:260)
at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:170)
at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:51)
at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:154)
at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:241)
at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:229)
at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:207)
at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:75)
at org.jboss.weld.bootstrap.events.AbstractDeploymentContainerEvent.fire(AbstractDeploymentContainerEvent.java:46)
at org.jboss.weld.bootstrap.events.AfterDeploymentValidationImpl.fire(AfterDeploymentValidationImpl.java:31)
at org.jboss.weld.bootstrap.WeldBootstrap.validateBeans(WeldBootstrap.java:369)
at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:83)
at org.jboss.as.weld.services.WeldService.start(WeldService.java:76)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
"},"JBAS014771: Services with missing/unavailable dependencies" => ["jboss.web.deployment.default-host./jbpm-console.realmjboss.security.security-domain.jbpm-console-ngMissing[jboss.web.deployment.default-host./jbpm-console.realmjboss.security.security-domain.jbpm-console-ng]"]}}}
Anyone has any thought on this?
Any help will be appreciated.
Regards
Samuele Mezzasalma
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/822294#822294]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 11 months
[jBPM] - jBPM 5.1 without HumanTask Service
by Massimiliano Izzo
Massimiliano Izzo [https://community.jboss.org/people/amizzo] created the discussion
"jBPM 5.1 without HumanTask Service"
To view the discussion, visit: https://community.jboss.org/message/821059#821059
--------------------------------------------------------------
Hi,
I am using the jBPM 5.1.
I am using this version because I have JBoss AS5 on a production environment, and I tested the jBPM 5.1 final as the only version fully compatible with AS5, in terms of
jBPM console server
drools-guvnor
designer
The problem is that the ant start.demo script launches also the human task service, but I don't want/need the human task service. How to disable this service without receiving the following error?
2013-06-03 18:31:48,967 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/gwt-console-server].[Resteasy]] (http-0.0.0.0-8080-2) Servlet.service() for servlet Resteasy threw exception
org.jboss.resteasy.spi.UnhandledException: java.lang.IllegalArgumentException: Could not connect task client
at org.jboss.resteasy.core.SynchronousDispatcher.handleApplicationException(SynchronousDispatcher.java:319)
at org.jboss.resteasy.core.SynchronousDispatcher.handleException(SynchronousDispatcher.java:230)
at org.jboss.resteasy.core.SynchronousDispatcher.handleInvokerException(SynchronousDispatcher.java:206)
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:360)
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:173)
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:93)
at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:68)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.bpm.console.server.util.GWTJsonFilter.doFilter(GWTJsonFilter.java:59)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:235)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:95)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:330)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:829)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:598)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:451)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.IllegalArgumentException: Could not connect task client
at org.jbpm.integration.console.TaskManagement.connect(TaskManagement.java:66)
at org.jbpm.integration.console.TaskManagement.getAssignedTasks(TaskManagement.java:179)
at org.jboss.bpm.console.server.TaskListFacade.getTasksForIdRef(TaskListFacade.java:99)
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 org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:117)
at org.jboss.resteasy.core.ResourceMethod.invokeOnTarget(ResourceMethod.java:260)
at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:232)
at org.jboss.resteasy.core.ResourceMethod.invoke(ResourceMethod.java:166)
at org.jboss.resteasy.core.DispatcherUtilities.getJaxrsResponse(DispatcherUtilities.java:142)
at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:356)
... 28 more
Basically, I need only my WorkItemHandler registered with the jBPM Console, and I don't need the Human Tasks persistence.
Thanks in advance
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/821059#821059]
Start a new discussion in jBPM at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 11 months
[Performance Tuning] - JBoss 5.1.0 tuning on AWS for large number of concurrent users
by jbossbuddy
jbossbuddy [https://community.jboss.org/people/jbossbuddy] created the discussion
"JBoss 5.1.0 tuning on AWS for large number of concurrent users"
To view the discussion, visit: https://community.jboss.org/message/822201#822201
--------------------------------------------------------------
Performance Testing Environment
--------------------------------
Web Server
CPU: 4 Core processor
RAM: 14984 MB
OS: AMI(amazon linux) --64 bit
App Server
CPU: 4 Core processor
RAM: 14985 MB
OS: AMI(amazon linux) --64 bit
DB Server
CPU: 4 Core processor
RAM: 14985 MB
OS: AMI(amazon linux) --64 bit
Deployment Information
-----------------------------------
Web Server (Apache) : Serving static files, images, javascripts, CSS etc.
App. Server (Jboss GA 5.1.0) : An eCommerce application
Database Server (mysql Ver 14.14 Distrib 5.5.28) : The DB schema for the e-Commerce application.
Background on site usage
--------------------------------------
The site currently supports 700 Active users (per Google Analytics) and CPU utilization stayed at 40 % when that many users were active in the site. The 'maxThreads' configuration in server.xml file is set at 700, and ConnnectionPool size has also been set at a value matching the demand. JVM tuning had been done subseqent to the results obtained as a result of load testing the application iteratively.
The above usage case has been supported by running a single instance of Jboss.
Other info : Jboss has been slimmed as per the recommendations in the web site
Questions
------------------
I. In anticipation of a higher demand, 2000 Active users at peak, we are considering the following strategies
a. Increase the parameters like 'maxThreads', max-min connection pool sizes, and achieve the capacity to address that many users.
b. Have another instance of Jboss running in the same box, and cluster that with the former, and have the configuration parameters stated in #I.a. to support 1000 users on each of those Jboss instances.
Which among the above will be a better option? - The CPU utilization on the App Server machine can go up to 70 %.
Are there other candidate strategies that provide better value for the investment already done?
II. Are there any Jboss/ Operating System configuration tuning specific to AWS cloud deployments?
--------------------------------------------------------------
Reply to this message by going to Community
[https://community.jboss.org/message/822201#822201]
Start a new discussion in Performance Tuning at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&con...]
10 years, 11 months