Thanks, I'll forward this to some people so they can shed a light on this.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4250258#4250258
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4250258
anonymous wrote : Are 1,2 and 3 valid for all DBMS you use? Would be great if
you could confirm that.
Definitely Oracle and Sybase, don't have much experience with MSSql yet.
anonymous wrote : And maybe also what the default locking mechanisms are on
specific database.
Defaults:
Oracle - Row
Are 1,2 and 3 valid for all DBMS you use? Would be great if you could confirm
that. And maybe also what the default locking mechanisms are on specific
database.
Surprises me that there is no slowdown btw. And I'm also curious what
additional indexes you created that are not already on jBPM. Sin
kukeltje:
anonymous wrote : - Would be great if you could elaborate a little on the way
creating the indexes impacted performance more than just the delete (thankfully
it was not the coroner you had to call ;-))
(1) When we start up the jBPM java app, we load information about all the
running
bestage:
anonymous wrote : How do you re-use the jBPM component in multiple
applications? Are you distributing a jar and use a central jbpm db for the
tables? This is what I am planning to do in one of my projects. But I was also
thinking about the possible deadlock issues.
Yes, this is the tr
This is a very interesting discussion to follow.
@michaelholtzmann: as I see you are using jBPM3.x.x here. I wonder if locking
issues also take place with jbpm4. I hope not or to a smaller extent, since the
db schema design has been improved considerably.
How do you re-use the jBPM component i
Hmm... I wrote a long response to this, but it strangely disappeared. I'll
summarize:
- Would be great if you could elaborate a little on the way creating the
indexes impacted performance more than just the delete (thankfully it was not
the coroner you had to call ;-))
- If you have some errors
Well, to make things even more fun we support three db platforms: Sybase,
Oracle, and SqlServer.
First off, almost all of the deadlock problems were cured after indexing the
JBPM tables on all the foreign key columns. (We almost had to call the
paramedics for the DBA when we told him we were ad
Nice hearing it is used so extensively. Not nice to hear there are persistency
errors.
Ok , first, my experience is that diagnosing deadlocks etc is indeed hard, not
only with jBPM, but in general. In most cases we used a dba to do find the
deadlocks in combination java/db expert that uses thr
Yes, I have already written a number of these one-trick ponies to solve
specific problems. We're more interested in diagnosing database issues.
We are pushing jBPM very hard, running multiple processing threads within a
java app as well as multiple distributed java apps. (We have a client that
1: If there are, they were not mentioned here. Easiest thing to do is write a
small application that uses hiberenate to find all processinstances with or
beyond a certain end date and do a delete via hibernate. That will cascadingly
remove all things
2: Hmm... I never had a 'data integrity cons
11 matches
Mail list logo
