[JBoss JIRA] (JGRP-1558) Discovery: don't suppress response when merging for non-merge triggered discovery requests
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-1558?page=com.atlassian.jira.plugin.... ]
Bela Ban commented on JGRP-1558:
--------------------------------
The functionality to only return the physical address / logical name for a specific (requested) member is redundant as return_entire_cache=true performs a similar task.
> Discovery: don't suppress response when merging for non-merge triggered discovery requests
> ------------------------------------------------------------------------------------------
>
> Key: JGRP-1558
> URL: https://issues.jboss.org/browse/JGRP-1558
> Project: JGroups
> Issue Type: Feature Request
> Reporter: Bela Ban
> Assignee: Bela Ban
> Fix For: 3.3
>
>
> In Discovery, when receiving a discovery request, we discard it if a merge is running (isMergeRunning()). The condition should be moved into the if-clause above (hdr.view_id != null), as it only applies to merge-triggered discoveries. When handling a regular discovery, e.g. at startup or when a physical address is looked up, a discovery response should be sent.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6141) JBoss Developer Framework README.md says there is an example-settings.xml, but there isn't.
by Michael Van Geertruy (JIRA)
[ https://issues.jboss.org/browse/AS7-6141?page=com.atlassian.jira.plugin.s... ]
Michael Van Geertruy edited comment on AS7-6141 at 12/27/12 7:09 AM:
---------------------------------------------------------------------
If you have a properly configured settings.xml file in your ~/.m2 directory, you should not need to use the example-settings.xml file. This file is present to show you how to configure Maven to use the examples. Skip this step if you have maven installed and running or if you are running the examples in an IDE that has a properly configured Maven plugin. If after skipping this step, the examples still don't work, please place a comment on this thread and paste the exception or error that you are getting. In the mean time I will research where this file has been placed.
was (Author: mikevan):
If you have a properly configured settings.xml file in your ~/.m2 directory, you should not need to use the example-settings.xml file. This file is present to show you how to configure Maven to use the examples. Skip this step if you have maven installed and running or if you are running the examples in an IDE that has a properly configured Maven plugin. If after skipping this step, the example don't work, please place a comment on this thread and paste the exception or error that you are getting. In the mean time I will research where this file has been placed.
> JBoss Developer Framework README.md says there is an example-settings.xml, but there isn't.
> -------------------------------------------------------------------------------------------
>
> Key: AS7-6141
> URL: https://issues.jboss.org/browse/AS7-6141
> Project: Application Server 7
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 7.1.1.Final
> Environment: JBoss Developer Framework site. http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/#introduction
> Reporter: Rick Wagner
> Priority: Critical
>
> The README.md describes an 'example-settings.xml' file that should be 'in the root of your quickstarts folder'. There does not seem to be such a file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6141) JBoss Developer Framework README.md says there is an example-settings.xml, but there isn't.
by Michael Van Geertruy (JIRA)
[ https://issues.jboss.org/browse/AS7-6141?page=com.atlassian.jira.plugin.s... ]
Michael Van Geertruy commented on AS7-6141:
-------------------------------------------
If you have a properly configured settings.xml file in your ~/.m2 directory, you should not need to use the example-settings.xml file. This file is present to show you how to configure Maven to use the examples. Skip this step if you have maven installed and running or if you are running the examples in an IDE that has a properly configured Maven plugin. If after skipping this step, the example don't work, please place a comment on this thread and paste the exception or error that you are getting. In the mean time I will research where this file has been placed.
> JBoss Developer Framework README.md says there is an example-settings.xml, but there isn't.
> -------------------------------------------------------------------------------------------
>
> Key: AS7-6141
> URL: https://issues.jboss.org/browse/AS7-6141
> Project: Application Server 7
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 7.1.1.Final
> Environment: JBoss Developer Framework site. http://www.jboss.org/jdf/quickstarts/jboss-as-quickstart/#introduction
> Reporter: Rick Wagner
> Priority: Critical
>
> The README.md describes an 'example-settings.xml' file that should be 'in the root of your quickstarts folder'. There does not seem to be such a file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6248) Missing file from Nexus preventing build of Arquillian TestNG Integration
by Michael Van Geertruy (JIRA)
[ https://issues.jboss.org/browse/AS7-6248?page=com.atlassian.jira.plugin.s... ]
Michael Van Geertruy edited comment on AS7-6248 at 12/27/12 5:39 AM:
---------------------------------------------------------------------
Patch file "0001-Moved-testng-integration-to-the-base-directory-and-m.patch" implements option 2 of this ticket. Released under ASF2.0 license.
was (Author: mikevan):
Implements option 2 of this ticket. Released under ASF2.0 license.
> Missing file from Nexus preventing build of Arquillian TestNG Integration
> -------------------------------------------------------------------------
>
> Key: AS7-6248
> URL: https://issues.jboss.org/browse/AS7-6248
> Project: Application Server 7
> Issue Type: Bug
> Components: Build System
> Affects Versions: 7.2.0.Alpha1
> Environment: CentOS 6.3, Intel X86-64
> Reporter: Michael Van Geertruy
> Assignee: Paul Gier
> Labels: Arquillian
> Attachments: 0001-Moved-testng-integration-to-the-base-directory-and-m.patch, AS7-6248-patch.txt
>
>
> After downloading the most recent codebase from git for jbossAS 7.2.0.SNAPSHOT, I recieved the following error:
> [INFO] ------------------------------------------------------------------------
> [INFO] Building JBoss Application Server: Arquillian TestNG Integration 7.2.0.Alpha1-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/as/jbos...
> Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/as/jbos...
> [WARNING] The POM for org.jboss.as:jboss-as-spec-api:pom:7.2.0.Alpha1-SNAPSHOT is missing, no dependency information available
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] JBoss Application Server: Arquillian .............. SUCCESS [3.091s]
> [INFO] JBoss Application Server: Arquillian TestEnricher MSC SUCCESS [7.331s]
> [INFO] JBoss Application Server: Arquillian Common ....... SUCCESS [7.461s]
> [INFO] JBoss Application Server: Arquillian Embedded Container SUCCESS [18.654s]
> [INFO] JBoss Application Server: Arquillian Protocol JMX . SUCCESS [3.766s]
> [INFO] JBoss Application Server: Arquillian Managed Container SUCCESS [19.634s]
> [INFO] JBoss Application Server: Arquillian Remote Container SUCCESS [2.147s]
> [INFO] JBoss Application Server: Arquillian TestNG Integration FAILURE [3.535s]
> [INFO] JBoss Application Server: Arquillian Common Domain SKIPPED
> [INFO] JBoss Application Server: Arquillian Remote Domain Container SKIPPED
> [INFO] JBoss Application Server: Arquillian Managed Domain Container SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 1:08.150s
> [INFO] Finished at: Sat Dec 22 23:43:21 PST 2012
> [INFO] Final Memory: 51M/317M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal on project jboss-as-arquillian-testng-integration: Could not resolve dependencies for project org.jboss.as:jboss-as-arquillian-testng-integration:jar:7.2.0.Alpha1-SNAPSHOT
> Indeed after looking at the jboss nexus repository I came across this link:
> https://repository.jboss.org/nexus/content/groups/public/org/jboss/as/jbo...
> There do not appear to be any entries for 7.2.0.Alpha1-SNAPSHOT.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6248) Missing file from Nexus preventing build of Arquillian TestNG Integration
by Michael Van Geertruy (JIRA)
[ https://issues.jboss.org/browse/AS7-6248?page=com.atlassian.jira.plugin.s... ]
Michael Van Geertruy updated AS7-6248:
--------------------------------------
Attachment: 0001-Moved-testng-integration-to-the-base-directory-and-m.patch
Implements option 2 of this ticket. Released under ASF2.0 license.
> Missing file from Nexus preventing build of Arquillian TestNG Integration
> -------------------------------------------------------------------------
>
> Key: AS7-6248
> URL: https://issues.jboss.org/browse/AS7-6248
> Project: Application Server 7
> Issue Type: Bug
> Components: Build System
> Affects Versions: 7.2.0.Alpha1
> Environment: CentOS 6.3, Intel X86-64
> Reporter: Michael Van Geertruy
> Assignee: Paul Gier
> Labels: Arquillian
> Attachments: 0001-Moved-testng-integration-to-the-base-directory-and-m.patch, AS7-6248-patch.txt
>
>
> After downloading the most recent codebase from git for jbossAS 7.2.0.SNAPSHOT, I recieved the following error:
> [INFO] ------------------------------------------------------------------------
> [INFO] Building JBoss Application Server: Arquillian TestNG Integration 7.2.0.Alpha1-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/as/jbos...
> Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/as/jbos...
> [WARNING] The POM for org.jboss.as:jboss-as-spec-api:pom:7.2.0.Alpha1-SNAPSHOT is missing, no dependency information available
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] JBoss Application Server: Arquillian .............. SUCCESS [3.091s]
> [INFO] JBoss Application Server: Arquillian TestEnricher MSC SUCCESS [7.331s]
> [INFO] JBoss Application Server: Arquillian Common ....... SUCCESS [7.461s]
> [INFO] JBoss Application Server: Arquillian Embedded Container SUCCESS [18.654s]
> [INFO] JBoss Application Server: Arquillian Protocol JMX . SUCCESS [3.766s]
> [INFO] JBoss Application Server: Arquillian Managed Container SUCCESS [19.634s]
> [INFO] JBoss Application Server: Arquillian Remote Container SUCCESS [2.147s]
> [INFO] JBoss Application Server: Arquillian TestNG Integration FAILURE [3.535s]
> [INFO] JBoss Application Server: Arquillian Common Domain SKIPPED
> [INFO] JBoss Application Server: Arquillian Remote Domain Container SKIPPED
> [INFO] JBoss Application Server: Arquillian Managed Domain Container SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 1:08.150s
> [INFO] Finished at: Sat Dec 22 23:43:21 PST 2012
> [INFO] Final Memory: 51M/317M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal on project jboss-as-arquillian-testng-integration: Could not resolve dependencies for project org.jboss.as:jboss-as-arquillian-testng-integration:jar:7.2.0.Alpha1-SNAPSHOT
> Indeed after looking at the jboss nexus repository I came across this link:
> https://repository.jboss.org/nexus/content/groups/public/org/jboss/as/jbo...
> There do not appear to be any entries for 7.2.0.Alpha1-SNAPSHOT.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6248) Missing file from Nexus preventing build of Arquillian TestNG Integration
by Michael Van Geertruy (JIRA)
[ https://issues.jboss.org/browse/AS7-6248?page=com.atlassian.jira.plugin.s... ]
Michael Van Geertruy edited comment on AS7-6248 at 12/27/12 3:57 AM:
---------------------------------------------------------------------
Please disregard the first patch. It did not capture the move of the module. I will submit a new patch that captures this change and submit it later on today.
was (Author: mikevan):
Patch for the second option moving testng-integration to be a peer to spec-api. This is released under the ASF2.0 license.
> Missing file from Nexus preventing build of Arquillian TestNG Integration
> -------------------------------------------------------------------------
>
> Key: AS7-6248
> URL: https://issues.jboss.org/browse/AS7-6248
> Project: Application Server 7
> Issue Type: Bug
> Components: Build System
> Affects Versions: 7.2.0.Alpha1
> Environment: CentOS 6.3, Intel X86-64
> Reporter: Michael Van Geertruy
> Assignee: Paul Gier
> Labels: Arquillian
> Attachments: AS7-6248-patch.txt
>
>
> After downloading the most recent codebase from git for jbossAS 7.2.0.SNAPSHOT, I recieved the following error:
> [INFO] ------------------------------------------------------------------------
> [INFO] Building JBoss Application Server: Arquillian TestNG Integration 7.2.0.Alpha1-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/as/jbos...
> Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/as/jbos...
> [WARNING] The POM for org.jboss.as:jboss-as-spec-api:pom:7.2.0.Alpha1-SNAPSHOT is missing, no dependency information available
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] JBoss Application Server: Arquillian .............. SUCCESS [3.091s]
> [INFO] JBoss Application Server: Arquillian TestEnricher MSC SUCCESS [7.331s]
> [INFO] JBoss Application Server: Arquillian Common ....... SUCCESS [7.461s]
> [INFO] JBoss Application Server: Arquillian Embedded Container SUCCESS [18.654s]
> [INFO] JBoss Application Server: Arquillian Protocol JMX . SUCCESS [3.766s]
> [INFO] JBoss Application Server: Arquillian Managed Container SUCCESS [19.634s]
> [INFO] JBoss Application Server: Arquillian Remote Container SUCCESS [2.147s]
> [INFO] JBoss Application Server: Arquillian TestNG Integration FAILURE [3.535s]
> [INFO] JBoss Application Server: Arquillian Common Domain SKIPPED
> [INFO] JBoss Application Server: Arquillian Remote Domain Container SKIPPED
> [INFO] JBoss Application Server: Arquillian Managed Domain Container SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 1:08.150s
> [INFO] Finished at: Sat Dec 22 23:43:21 PST 2012
> [INFO] Final Memory: 51M/317M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal on project jboss-as-arquillian-testng-integration: Could not resolve dependencies for project org.jboss.as:jboss-as-arquillian-testng-integration:jar:7.2.0.Alpha1-SNAPSHOT
> Indeed after looking at the jboss nexus repository I came across this link:
> https://repository.jboss.org/nexus/content/groups/public/org/jboss/as/jbo...
> There do not appear to be any entries for 7.2.0.Alpha1-SNAPSHOT.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBRULES-3108) problems with concurrent process executions, constraints, and multiple sessions
by J Xmith (JIRA)
[ https://issues.jboss.org/browse/JBRULES-3108?page=com.atlassian.jira.plug... ]
J Xmith commented on JBRULES-3108:
----------------------------------
I am using jbpm 5.3.0.Final, and I am facing the same problem:
I have a fairly simple business process with one rule-group (Guvnor TaskType=Business Rule). The rule-group does validations on process variables. To provide separation between facts from different requests, each processing request creates its own stateful knowledge session which in turns creates its own business process. Everything works well with one process execution (one request at a time).
When 2 almost concurrent requests are tried (each one running in its own thread), the first one reaching the rule-group leave an entry/record inside the EVENTTYPES table (containing the businessProcessId and the ruleflow group's name), and when the second business process reaches the rule-group it gets as event the one stored in the EVENTTYPES table. From that moment onwards, the second thread continues its execution on the first business process. The end result is, the first business process get executed twice.
Removing the rule-group makes the concurrent requests to work well.
I was thinking in a similar solution to the one proposed here by Jordi Alvarez (using the knowledge session Id as an extra identifier, etc), however I realised this Jira issue has been open for too long now, and not updates since then. What is the intended behaviour of the EVENTTYPES table, and why the knowledge session Id is not already used to distinguish between multiple concurrent requests?
> problems with concurrent process executions, constraints, and multiple sessions
> -------------------------------------------------------------------------------
>
> Key: JBRULES-3108
> URL: https://issues.jboss.org/browse/JBRULES-3108
> Project: JBRULES
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: drools-core (flow)
> Affects Versions: 5.1.1.FINAL, 5.2.0.Final
> Environment: Independent of OS, JVM, and Application Server. Reproduced in a windows development environment with a Sun JVM. Also reproduced in linux. Also database independent: reproduced with Oracle RDBMS and HSQLDB.
> Reporter: Jordi Alvarez
> Assignee: Kris Verlaenen
>
> The context is as follows:
> 1. We have drools flow configured with JPA and Hibernate, accessing an Oracle / HSQLDB database (depending on the environment).
> 2. We do have several concurrent stateful sessions in which different instances of the same kind of processes are running. These stateful sessions are persisted in the same database schema.
> 3. We do use wait states (also reproduced with rule nodes) that have constraints that wait for a fact to be inserted into the stateful session.
> 4. Whenever the fact that makes the constraint to satisfy is inserted for one process in a given stateful session; if there are other processes waiting in that wait state/constraint (in other different stateful sessions), the stateful session tries also to continue those process executions, even when they are not part of it.
> A solution has been implemented temporally over drools source code (in order to get our context working): the solution is briefly described in the forum url below. For completeness a summary is included here:
> - Adding a new attribute to org.drools.persistence.processinstance.ProcessInstanceInfo POJO identifying the stateful session to which the process instance corresponds (and the corresponding DB column).
> - modifying the ProcessInstancesWaitingForEvent query (in orm.xml) in order to take into account the session id as a (new) second parameter.
> - modify the class org.drools.persistence.processinstance.JPASignalManager in order to execute the query with both parameters.
> - as a quick way to have the session id, we have a threadlocal.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (AS7-6248) Missing file from Nexus preventing build of Arquillian TestNG Integration
by Michael Van Geertruy (JIRA)
[ https://issues.jboss.org/browse/AS7-6248?page=com.atlassian.jira.plugin.s... ]
Michael Van Geertruy updated AS7-6248:
--------------------------------------
Attachment: AS7-6248-patch.txt
Patch for the second option moving testng-integration to be a peer to spec-api. This is released under the ASF2.0 license.
> Missing file from Nexus preventing build of Arquillian TestNG Integration
> -------------------------------------------------------------------------
>
> Key: AS7-6248
> URL: https://issues.jboss.org/browse/AS7-6248
> Project: Application Server 7
> Issue Type: Bug
> Components: Build System
> Affects Versions: 7.2.0.Alpha1
> Environment: CentOS 6.3, Intel X86-64
> Reporter: Michael Van Geertruy
> Assignee: Paul Gier
> Labels: Arquillian
> Attachments: AS7-6248-patch.txt
>
>
> After downloading the most recent codebase from git for jbossAS 7.2.0.SNAPSHOT, I recieved the following error:
> [INFO] ------------------------------------------------------------------------
> [INFO] Building JBoss Application Server: Arquillian TestNG Integration 7.2.0.Alpha1-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/as/jbos...
> Downloading: http://repository.jboss.org/nexus/content/groups/public/org/jboss/as/jbos...
> [WARNING] The POM for org.jboss.as:jboss-as-spec-api:pom:7.2.0.Alpha1-SNAPSHOT is missing, no dependency information available
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] JBoss Application Server: Arquillian .............. SUCCESS [3.091s]
> [INFO] JBoss Application Server: Arquillian TestEnricher MSC SUCCESS [7.331s]
> [INFO] JBoss Application Server: Arquillian Common ....... SUCCESS [7.461s]
> [INFO] JBoss Application Server: Arquillian Embedded Container SUCCESS [18.654s]
> [INFO] JBoss Application Server: Arquillian Protocol JMX . SUCCESS [3.766s]
> [INFO] JBoss Application Server: Arquillian Managed Container SUCCESS [19.634s]
> [INFO] JBoss Application Server: Arquillian Remote Container SUCCESS [2.147s]
> [INFO] JBoss Application Server: Arquillian TestNG Integration FAILURE [3.535s]
> [INFO] JBoss Application Server: Arquillian Common Domain SKIPPED
> [INFO] JBoss Application Server: Arquillian Remote Domain Container SKIPPED
> [INFO] JBoss Application Server: Arquillian Managed Domain Container SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 1:08.150s
> [INFO] Finished at: Sat Dec 22 23:43:21 PST 2012
> [INFO] Final Memory: 51M/317M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal on project jboss-as-arquillian-testng-integration: Could not resolve dependencies for project org.jboss.as:jboss-as-arquillian-testng-integration:jar:7.2.0.Alpha1-SNAPSHOT
> Indeed after looking at the jboss nexus repository I came across this link:
> https://repository.jboss.org/nexus/content/groups/public/org/jboss/as/jbo...
> There do not appear to be any entries for 7.2.0.Alpha1-SNAPSHOT.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months