[JBoss JIRA] Created: (JBIDE-7347) jBPM process isn't deployed although successful deployment is reported
4:36 a.m.
jBPM process isn't deployed although successful deployment is reported
----------------------------------------------------------------------
Key: JBIDE-7347
URL: https://jira.jboss.org/browse/JBIDE-7347
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.2.0.Beta1
Environment: JBDS 4.0.0.beta1 #47, Linux 64, SOA-P 5.0.1.ga
Reporter: Jiri Peterka
Priority: Critical
Steps:
1. Create jbpm3 project with SOA-P 5.0.1.ga jbpm runtime
2. Open simple process, on deployment page, set gpd-deployer as sever deployer
3. Ping server OK
4. Deploy - OK
ERROR: When checked jBPM web Console, there is no process deployed
WORKAROUND: Save process archive in jbds and deploy it from jbpm web console
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:45 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-7347) jBPM process isn't deployed although successful deployment is reported
[
https://jira.jboss.org/browse/JBIDE-7347?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick updated JBIDE-7347:
-------------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Assignee: Koen Aers
Fix Version/s: 3.2.0.Beta2
jBPM process isn't deployed although successful deployment is
reported
----------------------------------------------------------------------
Key: JBIDE-7347
URL: https://jira.jboss.org/browse/JBIDE-7347
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.2.0.Beta1
Environment: JBDS 4.0.0.beta1 #47, Linux 64, SOA-P 5.0.1.ga
Reporter: Jiri Peterka
Assignee: Koen Aers
Priority: Critical
Fix For: 3.2.0.Beta2
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Steps:
1. Create jbpm3 project with SOA-P 5.0.1.ga jbpm runtime
2. Open simple process, on deployment page, set gpd-deployer as sever deployer
3. Ping server OK
4. Deploy - OK
ERROR: When checked jBPM web Console, there is no process deployed
WORKAROUND: Save process archive in jbds and deploy it from jbpm web console
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:45 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7347) jBPM process isn't deployed although successful deployment is reported
[
https://jira.jboss.org/browse/JBIDE-7347?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick commented on JBIDE-7347:
------------------------------------------
Koen, can you look into this?
jBPM process isn't deployed although successful deployment is
reported
----------------------------------------------------------------------
Key: JBIDE-7347
URL: https://jira.jboss.org/browse/JBIDE-7347
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.2.0.Beta1
Environment: JBDS 4.0.0.beta1 #47, Linux 64, SOA-P 5.0.1.ga
Reporter: Jiri Peterka
Assignee: Koen Aers
Priority: Critical
Fix For: 3.2.0.Beta2
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Steps:
1. Create jbpm3 project with SOA-P 5.0.1.ga jbpm runtime
2. Open simple process, on deployment page, set gpd-deployer as sever deployer
3. Ping server OK
4. Deploy - OK
ERROR: When checked jBPM web Console, there is no process deployed
WORKAROUND: Save process archive in jbds and deploy it from jbpm web console
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:06 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7347) jBPM process isn't deployed although successful deployment is reported
[
https://jira.jboss.org/browse/JBIDE-7347?page=com.atlassian.jira.plugin.s...
]
Koen Aers commented on JBIDE-7347:
----------------------------------
I can't reproduce this with the steps you describe. Is there something missing from
the description?
jBPM process isn't deployed although successful deployment is
reported
----------------------------------------------------------------------
Key: JBIDE-7347
URL: https://jira.jboss.org/browse/JBIDE-7347
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.2.0.Beta1
Environment: JBDS 4.0.0.beta1 #47, Linux 64, SOA-P 5.0.1.ga
Reporter: Jiri Peterka
Assignee: Koen Aers
Priority: Critical
Fix For: 3.2.0.Beta2
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Steps:
1. Create jbpm3 project with SOA-P 5.0.1.ga jbpm runtime
2. Open simple process, on deployment page, set gpd-deployer as sever deployer
3. Ping server OK
4. Deploy - OK
ERROR: When checked jBPM web Console, there is no process deployed
WORKAROUND: Save process archive in jbds and deploy it from jbpm web console
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:29 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7347) jBPM process isn't deployed although successful deployment is reported
[
https://jira.jboss.org/browse/JBIDE-7347?page=com.atlassian.jira.plugin.s...
]
Jiri Peterka commented on JBIDE-7347:
-------------------------------------
Koen, I don't think something is missing, process is just not deployed. If you're
asking how to verify deployed process archive in SOA-P, you can just open the browser with
running SOA-P-p platform (typically localhost:8080), switch to jBPM Console and you should
see deployed process there and that is not currently happening. Can you see deployed
process in jBPM Console?
jBPM process isn't deployed although successful deployment is
reported
----------------------------------------------------------------------
Key: JBIDE-7347
URL: https://jira.jboss.org/browse/JBIDE-7347
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.2.0.Beta1
Environment: JBDS 4.0.0.beta1 #47, Linux 64, SOA-P 5.0.1.ga
Reporter: Jiri Peterka
Assignee: Koen Aers
Priority: Critical
Fix For: 3.2.0.Beta2
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Steps:
1. Create jbpm3 project with SOA-P 5.0.1.ga jbpm runtime
2. Open simple process, on deployment page, set gpd-deployer as sever deployer
3. Ping server OK
4. Deploy - OK
ERROR: When checked jBPM web Console, there is no process deployed
WORKAROUND: Save process archive in jbds and deploy it from jbpm web console
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:52 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7347) jBPM process isn't deployed although successful deployment is reported
[
https://jira.jboss.org/browse/JBIDE-7347?page=com.atlassian.jira.plugin.s...
]
Koen Aers commented on JBIDE-7347:
----------------------------------
Yes, I actually see the deployed process. The only difference with your config is that
I'm on OSX but normally that shouldn't make any difference.
jBPM process isn't deployed although successful deployment is
reported
----------------------------------------------------------------------
Key: JBIDE-7347
URL: https://jira.jboss.org/browse/JBIDE-7347
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.2.0.Beta1
Environment: JBDS 4.0.0.beta1 #47, Linux 64, SOA-P 5.0.1.ga
Reporter: Jiri Peterka
Assignee: Koen Aers
Priority: Critical
Fix For: 3.2.0.Beta2
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Steps:
1. Create jbpm3 project with SOA-P 5.0.1.ga jbpm runtime
2. Open simple process, on deployment page, set gpd-deployer as sever deployer
3. Ping server OK
4. Deploy - OK
ERROR: When checked jBPM web Console, there is no process deployed
WORKAROUND: Save process archive in jbds and deploy it from jbpm web console
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:10 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7347) jBPM process isn't deployed although successful deployment is reported
[
https://jira.jboss.org/browse/JBIDE-7347?page=com.atlassian.jira.plugin.s...
]
Jiri Peterka commented on JBIDE-7347:
-------------------------------------
Koen, now it's clear what has happened. Issue is here when "gpd-deployer"
instead of "gpd-deployer/upload" is set as server deployer. jBPM tools somehow
thinks everything is all-right and reports successful deployment although is not true.
jBPM process isn't deployed although successful deployment is
reported
----------------------------------------------------------------------
Key: JBIDE-7347
URL: https://jira.jboss.org/browse/JBIDE-7347
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.2.0.Beta1
Environment: JBDS 4.0.0.beta1 #47, Linux 64, SOA-P 5.0.1.ga
Reporter: Jiri Peterka
Assignee: Koen Aers
Priority: Critical
Fix For: 3.2.0.Beta2
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Steps:
1. Create jbpm3 project with SOA-P 5.0.1.ga jbpm runtime
2. Open simple process, on deployment page, set gpd-deployer as sever deployer
3. Ping server OK
4. Deploy - OK
ERROR: When checked jBPM web Console, there is no process deployed
WORKAROUND: Save process archive in jbds and deploy it from jbpm web console
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:22 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-7347) jBPM process isn't deployed although successful deployment is reported
[
https://jira.jboss.org/browse/JBIDE-7347?page=com.atlassian.jira.plugin.s...
]
Koen Aers commented on JBIDE-7347:
----------------------------------
Aha, that makes a difference... I'll take a look at it!
jBPM process isn't deployed although successful deployment is
reported
----------------------------------------------------------------------
Key: JBIDE-7347
URL: https://jira.jboss.org/browse/JBIDE-7347
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.2.0.Beta1
Environment: JBDS 4.0.0.beta1 #47, Linux 64, SOA-P 5.0.1.ga
Reporter: Jiri Peterka
Assignee: Koen Aers
Priority: Critical
Fix For: 3.2.0.Beta2
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Steps:
1. Create jbpm3 project with SOA-P 5.0.1.ga jbpm runtime
2. Open simple process, on deployment page, set gpd-deployer as sever deployer
3. Ping server OK
4. Deploy - OK
ERROR: When checked jBPM web Console, there is no process deployed
WORKAROUND: Save process archive in jbds and deploy it from jbpm web console
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:50 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-7347) jBPM process isn't deployed although successful deployment is reported
[
https://jira.jboss.org/browse/JBIDE-7347?page=com.atlassian.jira.plugin.s...
]
Koen Aers updated JBIDE-7347:
-----------------------------
Attachment: JBIDE-7347.patch
jBPM process isn't deployed although successful deployment is
reported
----------------------------------------------------------------------
Key: JBIDE-7347
URL: https://jira.jboss.org/browse/JBIDE-7347
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.2.0.Beta1
Environment: JBDS 4.0.0.beta1 #47, Linux 64, SOA-P 5.0.1.ga
Reporter: Jiri Peterka
Assignee: Koen Aers
Priority: Critical
Fix For: 3.2.0.Beta2
Attachments: JBIDE-7347.patch
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Steps:
1. Create jbpm3 project with SOA-P 5.0.1.ga jbpm runtime
2. Open simple process, on deployment page, set gpd-deployer as sever deployer
3. Ping server OK
4. Deploy - OK
ERROR: When checked jBPM web Console, there is no process deployed
WORKAROUND: Save process archive in jbds and deploy it from jbpm web console
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:52 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-7347) jBPM process isn't deployed although successful deployment is reported
[
https://jira.jboss.org/browse/JBIDE-7347?page=com.atlassian.jira.plugin.s...
]
Koen Aers updated JBIDE-7347:
-----------------------------
Fix Version/s: 3.1.2
jBPM process isn't deployed although successful deployment is
reported
----------------------------------------------------------------------
Key: JBIDE-7347
URL: https://jira.jboss.org/browse/JBIDE-7347
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.2.0.Beta1
Environment: JBDS 4.0.0.beta1 #47, Linux 64, SOA-P 5.0.1.ga
Reporter: Jiri Peterka
Assignee: Koen Aers
Priority: Critical
Fix For: 3.1.2, 3.2.0.Beta2
Attachments: JBIDE-7347.patch
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Steps:
1. Create jbpm3 project with SOA-P 5.0.1.ga jbpm runtime
2. Open simple process, on deployment page, set gpd-deployer as sever deployer
3. Ping server OK
4. Deploy - OK
ERROR: When checked jBPM web Console, there is no process deployed
WORKAROUND: Save process archive in jbds and deploy it from jbpm web console
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:52 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-7347) jBPM process isn't deployed although successful deployment is reported
[
https://jira.jboss.org/browse/JBIDE-7347?page=com.atlassian.jira.plugin.s...
]
Koen Aers resolved JBIDE-7347.
------------------------------
Resolution: Done
jBPM process isn't deployed although successful deployment is
reported
----------------------------------------------------------------------
Key: JBIDE-7347
URL: https://jira.jboss.org/browse/JBIDE-7347
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.2.0.Beta1
Environment: JBDS 4.0.0.beta1 #47, Linux 64, SOA-P 5.0.1.ga
Reporter: Jiri Peterka
Assignee: Koen Aers
Priority: Critical
Fix For: 3.1.2, 3.2.0.Beta2
Attachments: JBIDE-7347.patch
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Steps:
1. Create jbpm3 project with SOA-P 5.0.1.ga jbpm runtime
2. Open simple process, on deployment page, set gpd-deployer as sever deployer
3. Ping server OK
4. Deploy - OK
ERROR: When checked jBPM web Console, there is no process deployed
WORKAROUND: Save process archive in jbds and deploy it from jbpm web console
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:27 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-7347) jBPM process isn't deployed although successful deployment is reported
[
https://jira.jboss.org/browse/JBIDE-7347?page=com.atlassian.jira.plugin.s...
]
Jiri Peterka closed JBIDE-7347.
-------------------------------
Verified in JBDS 4.0.0.beta2 H12, SOA-P 5.1 ER4, Fedora 14-64b
jBPM process isn't deployed although successful deployment is
reported
----------------------------------------------------------------------
Key: JBIDE-7347
URL: https://jira.jboss.org/browse/JBIDE-7347
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jbpm
Affects Versions: 3.2.0.Beta1
Environment: JBDS 4.0.0.beta1 #47, Linux 64, SOA-P 5.0.1.ga
Reporter: Jiri Peterka
Assignee: Koen Aers
Priority: Critical
Fix For: 3.1.2, 3.2.0.Beta2
Attachments: JBIDE-7347.patch
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Steps:
1. Create jbpm3 project with SOA-P 5.0.1.ga jbpm runtime
2. Open simple process, on deployment page, set gpd-deployer as sever deployer
3. Ping server OK
4. Deploy - OK
ERROR: When checked jBPM web Console, there is no process deployed
WORKAROUND: Save process archive in jbds and deploy it from jbpm web console
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5614
days inactive
5661
days old
jbosstools-issues@lists.jboss.org
11 comments
3 participants
participants (3)
-
Brian Fitzpatrick (JIRA) -
Jiri Peterka (JIRA)
-
Koen Aers (JIRA)