We're also seeing this error, not out of state transfer, just randomly once in
awhile on a busy day. We've noticed that setting eventQueueSize=40 (for
example) doesnt help, we still get the error at 20. We've tried adjusting
down the minTimeToLiveSeconds now, from one day, to one
[EMAIL PROTECTED] wrote : Do you see any issues with the replication? E.g.,
if you turn off the cache loader - or even use a different cache loader - does
this work?
|
Hello again, and thanks for the followup. We tried the cache without a loader
today, and got the same result.
View
I've now logged this as a formal JIRA case:
https://jira.jboss.org/jira/browse/JBCACHE-1432
Thanks again!
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4187786#4187786
Reply to the post :
Ah, yes. Very fair question. :-) When it was apparant to me that the error
lies in readInt() and readShort(), I didn't think about the rest. Clearly
thats where the problem is, but this is the form we see without a loader
enabled:
30 [ERROR] RequestCorrelator.receiveMessage(): - failed
genman wrote : You're getting an EOF, meaning somebody in your cluster is
cutting the connection to your system. It might just be a network connectivity
issue. Look at the logs on the other machines (TRACE) and see what's triggering
the disconnect, if it indeed is within the cache.
Thanks for
I'm still hoping to get a confirmation. We feel certain that anyone else
attempting to blend 64bit windows in with other architectures in a cluster will
experience the same result, though.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4187843#4187843
Reply
Just a followup here, as mentioned. When using 64bit java for windows (1.6
latest), we do see the same result.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4184256#4184256
Reply to the post :
[EMAIL PROTECTED] wrote : I doubt this is an OS problem, but just to prove
it, do you see this issue if you had 1 windows and 1 linux machine in the
cluster, and the other linux machine were to join?
Thanks for the reply. We see this problem immediately after the 64bit machine
put()s or
Hello. We've run into some trouble in attempting to bring a 64bit windows
machine into an existing cluster. The cluster has (had) two 64bit linux
members and was running fine when we attempted to merge a 64bit windows machine
into the group. Anytime the windows machine wrote on a node, the
Small addendum, we're running the latest 2.2.0GA release. Thanks again.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4181964#4181964
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4181964
Hi,
I'm trying to determine if remoting might be a suitable replacement for an
older RMI implementation I'm using. This implementation has a built-in jxta
layer which provides functionality similar to multiplex sockets. Jxta also
provides a notion of a relay server, which can provide
Right. You're not getting the identity bits you need to run the demo. This
note:
[url]http://wiki.jboss.org/wiki/Wiki.jsp?page=UseHibernateToCreateJbpmDB
[/url]
should get you going.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4047113#4047113
Reply to
Looks like you need to set the appropriate dialect property in your mysql
config.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4047011#4047011
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4047011
lethrech wrote : think you for your response,
|
| some tables are absent (JBPM_ID_USER, JBPM_ID_GROUPE, JBPM_ID_MEMBERSHIP,
JBPM_ID_PERMISSIONS,JBPM_ID_JOB)
Some of those tables are a part of the identity implementation, which is not
referenced in the basic database initialization.
Your
You only need to use createSchema() once to setup the db.It automatically
drops and recreates all tables each time you invoke it. I'm not sure what your
code looks like, but you would likely want to comment that call and proceed
with the assumption that the database now exists.
View the
HLQ wrote : Everytime I startup Tomcat, it will automatically re-create the
database, and the database becomes empty. anybody knows how to avoid this?
Sounds like you're executing the createSchema() call every time you start up?
View the original post :
estaub wrote : Re where to get GPD:
| Be aware that Red Hat is planning to change the GPD from LGPL license to
GPL license. I don't know when.
|
Can someone point me to more details regarding this transition?
How will it affect the jbpm-console? Will process definitions created with GPD
kukeltje wrote : wjm wrote : estaub wrote : Re where to get GPD:
| | | Be aware that Red Hat is planning to change the GPD from LGPL
license to GPL license. I don't know when.
| | |
| |
| | Can someone point me to more details regarding this transition?
| |
| Sorry
MGarl10024 wrote :
|
| Section 11.11 from the Reference Manual stating jBPM includes an optional
identity component that can be easily replaced by a company's own identity data
store is just not working out like planned.
| - If you remove it, other things break.
|
| MG
The
pjodev wrote :
| Now it looks like it attempts to build the entire configuration from the
default.jbpm.cfg.xml file which is giving me that Message.hbm.xml error What
the hell is Message.hbm.xml? WHERE DO I USE IT? (see my other post!!!)
|
It appears the Message, TextMessage, and some
[EMAIL PROTECTED] wrote :
| You can find the current dependencies on Eclipse in the
dependencies.properties file which is in the org.jbpm.gd.jpdl.build project
Thanks Koen. I'll try upgrading to eclipse 3.2.1 along with the rest of the
dependencies you mentioned. I suspect that this
If you mean that you'd like to create the database automatically that's easy.
You can tell hibernate to do the job for you. See
http://wiki.jboss.org/wiki/Wiki.jsp?page=UseHibernateToCreateJbpmDB
for details on how to do that. Otoh, if you want to update your existing
database to reflect
[EMAIL PROTECTED] wrote :
| I did not yet try to do a build of the designer after I merged the two
plugins. How did you build it exactly?
|
I've tried both ant and the direct method using eclipse. The same anomalies
show up in either case.
anonymous wrote :
| Of course you need to
Hello. I'm trying to follow the latest changes to the designer. The
3.1.0.alpha3 version is being built now out of CVS head, but there appear to be
incompatibilities with the EMF/GEF versions which are distributed as default
with the 3.1.13 designer which is shipped with GA.
Can someone
Just to clarify, the 3.0.13.1 version is shipping with jBPM 3.2GA, while the
3.1.0.alpha3 version of the designer is building on cvs HEAD. (But the 3.2GA
target still contains 3.0.13.1, so there's no confusion for end users, only us
wannabees)
View the original post :
[EMAIL PROTECTED] wrote : To work on the head of the designer you should
checkout the org.jbpm.gd.jpdl project in the module jbpm.3/designer/jpdl. The
build script of jpdl 3.2 fetches the already built designer (3.0.13.1)from the
repository.
|
| Regards,
| Koen
Thanks alot for taking
anonymous wrote :
| What I'd want is the node Wait for Approval stay in a wait state untill
other entity signals it. But it's just executing it and continuing the flow.
| What have I missed?
|
Assuming Wait for Approval is a task-node, you have several options for
making it sit on its
kukeltje wrote : ... but still one issue remains. populating the identity
tables
The solution using hibernate which I proposed above does populate the identity
tables with the sesame street users using an included identity.xml called
(sesamestreet.xml).
Shameless link whoring:
kukeltje wrote : (and sorry for not reading it first, shame on me)
Trust me, it's not the first time. If anyone can find a better (less verbose)
way to present the solution on the wiki page, I would welcome edits.
Bill
View the original post :
hipchic wrote : Thanks for your replies,
| It don't think so , it's a user database configuration, i use the tomcat
context for doing these and it's works well...
|
The websale process archive as uploaded from the designer does seem to have
dependencies upon the jbpm-style UserRealm. You
hipchic wrote : Please remove in the hibernate.cfg.xml the line
|
| mapping resource=org/jbpm/taskinstance/CustomTaskInstance.hbm.xml
|
| [...]
| thks, but it's work great also
Thanks for the feedback, I've fixed the error in the hibernate config file, and
will look again at the
Running a checksum against the respective jarfiles in both locations shows them
to be identical. I dont think this is a problem, although the link on the
jboss pages could be set to include the GA bits. Hopefully we'll see a final
3.2 soon though.
View the original post :
Looks like somebody enabled ehcache in hibernate.cfg.xml without the necessary
setup. Try changing to the following in your hibernate.cfg.xml
property
name=hibernate.cache.provider_classorg.hibernate.cache.HashtableCacheProvider/property
|
|
and see if it helps. Note that
As a final note on this topic I'd like to point out that the easiest way to
create the jbpm database, for any given database server, is to let hibernate do
the job, and not rely on SQL at all as the solution proposes. This includes
creation of the Identity components (which were the primary
perrylucas wrote : Ok - you should be able to find a mini tutorial here now:
http://wiki.jboss.org/wiki/Wiki.jsp?page=CustomTasks
|
| (Linked from the jbpm home wiki page under jbpm 3)
Thanks for doing that, it looks like a good start.
I'm wondering if it makes sense to mention something
jpdl-3.2.xsd doesn't specify definition as an allowed attribute on Node, even
though, like name, definition is member variable of the GraphElement class
(node superclass).
Is there a good reason why this is the case? I'd like to be able to specify a
definition for a given node (or any of its
Additionally, it appears that among two (2) of the three (3) copies of
jpdl-3.2.xsd which are in the un-built distribution, description is allowed
as an element, but not an attribute, on some instances of node (decision,
start_state and end_state), but not others.
Given that description is
It appears I've referred to definition during this topic, which I should have
been referencing description. I hope that hasn't confused the issue too
terribly to make it impossible to reply to this.
To restate, only a few of the node instances in jpdl-3.2.xsd allow for a
description
kukeltje wrote : If you would have searched the jira for 'know' or solved
issues, you would have found that it is already solved in cvs.
|
| If I find a bug in any kind of library, the first thing I do is search the
jira and the forums. Saves me a lot of time.
I'm using HEAD, afaik.
39 matches
Mail list logo
