I do not get it either. jBPM retrieves all processdefinitions with the same
name (how many can that be, just several I think) and loops over that.
I again urge you to log additional things, you might e.g. have a problem with a
reverse dns lookup why things take long...
So I would not file a
saraswati.santanu wrote : Ajay,
|I did not get the first part of your question
|
| anonymous wrote : shouldn't the query actually be performed at the database
level !?!?
|
| The query will be performed at the db only.
|
| Do you mean a db procedure kind of thing? That
kukeltje wrote : I do not get it either. jBPM retrieves all
processdefinitions with the same name (how many can that be, just several I
think) and loops over that.
|
| I again urge you to log additional things, you might e.g. have a problem
with a reverse dns lookup why things take
ajaygautam wrote : saraswati.santanu wrote : Ajay,
| |I did not get the first part of your question
| |
| | anonymous wrote : shouldn't the query actually be performed at the
database level !?!?
| |
| | The query will be performed at the db only.
| |
| | Do
Sure. Here you go... The complete log leading upto this. The time lag occurs
between 9:33:57 to 9:35:43. This is when the deploy() runs.
PS: Could this be a timeout thing? Does deploy() go out to the internet, and
try to retrieve a DTD file or something like that? We are behind a proxy, so
jBPM afaik has the xsd's in a local resolver so should not need to go to the
internet. But it could be that (since the xsd changed in 4.2) this was
overlooked.
Regarding the logging Well, I (ofcourse ;-)) meant logging of what happens
DURING the deploy. So if it turns out not to be a
kukeltje wrote : jBPM afaik has the xsd's in a local resolver so should not
need to go to the internet. But it could be that (since the xsd changed in 4.2)
this was overlooked.
|
| Regarding the logging Well, I (ofcourse ;-)) meant logging of what
happens DURING the deploy. So if it
Is there any reason you cannot configure log4j (or jdk logging) to log in more
detail? Works fine here (and I'm serious, not joking or trying to make fun of
you or anything)
Now (besides the internet access) It's like saying: Hey, look at that car
driving by, it is going slow. Can you tell me
This statement takes all the time:
| ProcessDeployer.java line 134, method checkKey().
|
|
| ListProcessDefinition existingProcesses =
repositorySession.createProcessDefinitionQuery()
| .processDefinitionName(processDefinitionName)
| .list();
|
Then the code
Changing the database location from cross continent to local fixes the time
issue.
I think I should file this as a bug. Database developers should be frugal with
resources.
What do you think?
Ajay
View the original post :
Ajay,
I did not get the first part of your question
anonymous wrote : shouldn't the query actually be performed at the database
level !?!?
The query will be performed at the db only.
Do you mean a db procedure kind of thing? That will have other significant
disadvantages. So that query
Uhh I assume you have WAY more logging if so please post here. If not,
it is very, very hard for us to help.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4269773#4269773
Reply to the post :
12 matches
Mail list logo
