[Design of Clustering on JBoss (Clusters/JBoss)] - JBAS-3864 Discussion Thread
by bstansberry＠jboss.com
Discussions related to http://jira.jboss.com/jira/browse/JBAS-3864.
Re: where things like # retry attempts should be configured:
"Tomohisha Igarishi" wrote :
| "Brian Stansberry" wrote :
| | I'd like to move away from configuring this via the Tomcat5MBean. Rather I'd like to configure it via jboss-web.xml.
| |
| oh, I found JBAS-3460. but you won't backport that to branch 4.2?
| I think replication retry settings should be same layer as UseJK or Snapshot settings.
|
I added a subtask to backport that.
I agree with you about consistency. In 4.2 the config of default snapshot mode/interval may not be removed from the Tomcat SAR in order to maintain compatibility in a minor release. But IMHO they don't really belong in the Tomcat SAR.
Right now I'm thinking that:
1) Everything that can be varied per webapp should be configurable per webapp (i.e. in jboss-web.xml).
2) The ability to set an overall default in the Tomcat SAR is useful, but it adds clutter to the SAR config. If you read the SAR's -service.xml, you'll see what I mean. So, we should only offer the ability to set the default if:
a) it's a value people are likely to change
b) the change is something they want applied to multiple webapps
Of the UseJK, snapshot and retry configurations, IMHO only useJK meets these criteria.
Opinions on this are most welcome; on JBAS-3460 I mentioned I wanted a forum discussion about this general issue, so no reason this can't be that discussion. :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992242#3992242
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992242
18 years, 1 month
[Design of JBoss jBPM] - Exception while trying to instance process definition
by anu123suya
My processdefintion xml file got successfully deployed into the server. Could see an entry for this process in processdefinition table also.
When i try to run the sample application which tries to create an instance of the process, I am getting an Hibernate exception.
below is the code sample and exception . Can anyone help me to resolve this issue.
Thanks
JbpmConfiguration jbpmConfiguration = JbpmConfiguration.getInstance();
JbpmContext jbpmContext = jbpmConfiguration.createJbpmContext();
try
{
GraphSession graphSession = jbpmContext.getGraphSession();
ProcessDefinition processDefinition = graphSession.findLatestProcessDefinition("LeaveApproval");
ProcessInstance processInstance = new ProcessInstance(processDefinition);
Token token = processInstance.getRootToken();
token.signal();
jbpmContext.save(processInstance);
}
finally
{
jbpmContext.close();
}
Exception trace is:
------------------------------
2006-12-08 18:33:39,593 DEBUG [org.hibernate.persister.collection.AbstractCollectionPersister] Inserting collection: [org.jbpm.graph.exe.ProcessInstance.instances#22]
2006-12-08 18:33:39,593 DEBUG [org.hibernate.persister.collection.AbstractCollectionPersister] collection was empty
2006-12-08 18:33:39,593 DEBUG [org.hibernate.transaction.JDBCTransaction] re-enabling autocommit
2006-12-08 18:33:39,593 DEBUG [org.hibernate.transaction.JDBCTransaction] committed JDBC Connection
2006-12-08 18:33:39,593 DEBUG [org.hibernate.jdbc.ConnectionManager] aggressively releasing JDBC connection
2006-12-08 18:33:39,593 DEBUG [org.hibernate.jdbc.ConnectionManager] closing JDBC connection [ (open PreparedStatements: 0, globally: 0) (open ResultSets: 0, globally: 0)]
2006-12-08 18:33:39,593 DEBUG [org.jbpm.persistence.db.DbPersistenceService] closing hibernate session
2006-12-08 18:33:39,593 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/test].[jsp]] Servlet.service() for servlet jsp threw exception
org.hibernate.HibernateException: null index column for collection: org.jbpm.graph.def.ProcessDefinition.definitions
at org.hibernate.persister.collection.AbstractCollectionPersister.readIndex(AbstractCollectionPersister.java:652)
at org.hibernate.collection.PersistentMap.readFrom(PersistentMap.java:222)
at org.hibernate.loader.Loader.readCollectionElement(Loader.java:994)
at org.hibernate.loader.Loader.readCollectionElements(Loader.java:635)
at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:579)
at org.hibernate.loader.Loader.doQuery(Loader.java:689)
at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:223)
at org.hibernate.loader.Loader.loadCollection(Loader.java:1916)
at org.hibernate.loader.collection.CollectionLoader.initialize(CollectionLoader.java:71)
at org.hibernate.persister.collection.AbstractCollectionPersister.initialize(AbstractCollectionPersister.java:520)
at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:60)
at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1593)
at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:344)
at org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:86)
at org.hibernate.collection.PersistentMap.values(PersistentMap.java:198)
at org.jbpm.graph.exe.ProcessInstance.(ProcessInstance.java:103)
at org.apache.jsp.InvokeProcess_jsp._jspService(InvokeProcess_jsp.java:66)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332)
at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:175)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:74)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:534)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992234#3992234
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992234
18 years, 1 month
[Design of JBoss jBPM] - Brainstorming BA requirements
by bazoo
Here are a few requirements which have come up on a recent BPM project I've been the BA for, using a different BPM suite but the concepts are the same:
The ability to step back in a process if a mistake has been made. So rather than an "administrator" editing process variables, a process actor could reject a task and send it back to the previous actor.
| In a similar vein, it would be great if you (an administrator) could click on the process map in the web app to restart at the location you clicked.
| The ability to define task overrun points, which would trigger remedial procedures. For example, if a process actor hasn't completed a task within 24 hours then assign to someone else.
| To differentiate between primary users of the system, who "live and breathe" in their task list, and secondary users, who would perhaps get an email with a link which they can click to go in and complete a task every so often.
| The ability to embed task-specific "help" information in the process map which gets pulled through to the web app and displayed in context on the task page.
| The ability to easily get an overview of all the data associated to a particular process job, and to make changes to that data where it won't affect the integrity of the process.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992221#3992221
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992221
18 years, 1 month
[Design of JBoss jBPM] - Modelling notation - a Business Analyst perspective
by bazoo
Hello all,
I'm a business analyst and I've been playing with JBPM for a month or two now. I understand that there is some controversy within the project about which modelling notation to use, and I wanted to share my perspective.
To me, the current JBPM notation language is almost perfect. I think that BPMN is far too technical and I much prefer the simple approach of boxes and arrows. The question I ask myself is: "could my business sponsor understand the model enough to be able to sign off on it?". With a BPMN model, the answer is surely no, they couldn't.
I'm sure BPMN offers much more flexibility and is far more descriptive, but BPMN diagrams are complicated, and hence they put up unnecessary barriers to communication. If the model can't represent the business process in a form the business can relate to, then there is a breakdown in communication on a fundamental level. Anything which starts to resemble a circuit board diagram is simply not going to work for the business, and hence nor will it work for a BA. If the business can't sign off a model as meeting their requirements, then what are we building anyway?
For me, I much prefer the JBPM approach. Perhaps the only element I would add would be visual swimlaning - part of what my sponsor is signing off is the definition of who does what.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992214#3992214
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992214
18 years, 1 month
[Design of Persistence on JBoss] - Error when using TreeCacheProvider in JBoss 5
by thejavafreak
Hi all,
I hit against this error when running EJB3, in JBoss5, running the 'all' configuration, and use TreeCacheProvider provider as caching provider.
17:18:57,277 ERROR [AbstractKernelController] Error installing to Start: name=pe
| rsistence.units:jar=ejb3.jar,unitName=department state=Create
| java.lang.NoClassDefFoundError: org/jboss/cache/PropertyConfigurator
| at org.hibernate.cache.TreeCacheProvider.start(TreeCacheProvider.java:68
| )
| at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:
| 183)
| at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.jav
| a:1291)
| at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Con
| figuration.java:691)
| at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFa
| ctory(HibernatePersistence.java:127)
| at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnit
| Deployment.java:237)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
| java:39)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
| sorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:589)
| at org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(Reflec
| tionUtils.java:55)
| at org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(
| ReflectMethodInfoImpl.java:108)
| at org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethod
| JoinPoint.java:66)
| at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dis
| patchJoinPoint(KernelControllerContextAction.java:71)
| at org.jboss.kernel.plugins.dependency.LifecycleAction.installAction(Lif
| ecycleAction.java:147)
| at org.jboss.kernel.plugins.dependency.KernelControllerContextAction.ins
| tall(KernelControllerContextAction.java:96)
| at org.jboss.dependency.plugins.AbstractControllerContextActions.install
| (AbstractControllerContextActions.java:51)
| at org.jboss.dependency.plugins.AbstractControllerContext.install(Abstra
| ctControllerContext.java:226)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractContr
| oller.java:709)
| at org.jboss.dependency.plugins.AbstractController.incrementState(Abstra
| ctController.java:429)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr
| actController.java:538)
| at org.jboss.dependency.plugins.AbstractController.resolveContexts(Abstr
| actController.java:472)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractContr
| oller.java:274)
| at org.jboss.dependency.plugins.AbstractController.install(AbstractContr
| oller.java:177)
| at org.jboss.kernel.plugins.dependency.AbstractKernelController.install(
| AbstractKernelController.java:83)
| at org.jboss.kernel.plugins.dependency.AbstractKernelController.install(
| AbstractKernelController.java:77)
| at org.jboss.ejb3.MCKernelAbstraction.install(MCKernelAbstraction.java:1
| 41)
| at org.jboss.ejb3.Ejb3Deployment.startPersistenceUnits(Ejb3Deployment.ja
| va:473)
| at org.jboss.ejb3.Ejb3Deployment.start(Ejb3Deployment.java:324)
| at org.jboss.ejb3.deployers.EJBStage2Deployer.deploy(EJBStage2Deployer.j
| ava:48)
| at org.jboss.deployers.plugins.deployer.AbstractSimpleDeployer.commitDep
| loy(AbstractSimpleDeployer.java:52)
| at org.jboss.deployers.plugins.deployer.DeployerWrapper.commitDeploy(Dep
| loyerWrapper.java:145)
| at org.jboss.deployers.plugins.deployment.MainDeployerImpl.commitDeploy(
| MainDeployerImpl.java:440)
| at org.jboss.deployers.plugins.deployment.MainDeployerImpl.process(MainD
| eployerImpl.java:381)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadPr
| ofile(ProfileServiceBootstrap.java:366)
| at org.jboss.system.server.profileservice.ProfileServiceBootstrap.bootst
| rap(ProfileServiceBootstrap.java:246)
| at org.jboss.kernel.plugins.bootstrap.AbstractBootstrap.run(AbstractBoot
| strap.java:89)
| at org.jboss.system.server.profileservice.ServerImpl.doStart(ServerImpl.
| java:401)
| at org.jboss.system.server.profileservice.ServerImpl.start(ServerImpl.ja
| va:340)
| at org.jboss.Main.boot(Main.java:210)
| at org.jboss.Main$1.run(Main.java:508)
| at java.lang.Thread.run(Thread.java:619)
Could this be because of the not updated library between JBoss cache and Hibernate 3.2.1?
Can I call this as a bug? Or is there a workaround for this?
Thanks in advance
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3992208#3992208
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3992208
18 years, 1 month