[JBoss JIRA] (DROOLS-1160) It is possible to create duplicate drools runtime
by Tomas David (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1160?page=com.atlassian.jira.plugi... ]
Tomas David updated DROOLS-1160:
--------------------------------
Affects Version/s: 6.4.0.Final
> It is possible to create duplicate drools runtime
> -------------------------------------------------
>
> Key: DROOLS-1160
> URL: https://issues.jboss.org/browse/DROOLS-1160
> Project: Drools
> Issue Type: Bug
> Components: eclipse plugin
> Affects Versions: 6.4.0.Final
> Reporter: Tomas David
> Assignee: Robert (Bob) Brodt
> Priority: Minor
> Labels: reported-by-qe
>
> It is possible to create drools runtime with a name of runtime which already exists. If the location or version text input is changed, the OK button is enabled. Only case when it is not possible to create duplicate runtime is when the name input is changed as the last input to the duplicate name.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (DROOLS-1160) It is possible to create duplicate drools runtime
by Tomas David (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1160?page=com.atlassian.jira.plugi... ]
Tomas David updated DROOLS-1160:
--------------------------------
Environment: (was: Drools plugin 6.4.1)
> It is possible to create duplicate drools runtime
> -------------------------------------------------
>
> Key: DROOLS-1160
> URL: https://issues.jboss.org/browse/DROOLS-1160
> Project: Drools
> Issue Type: Bug
> Components: eclipse plugin
> Affects Versions: 6.4.0.Final
> Reporter: Tomas David
> Assignee: Robert (Bob) Brodt
> Priority: Minor
> Labels: reported-by-qe
>
> It is possible to create drools runtime with a name of runtime which already exists. If the location or version text input is changed, the OK button is enabled. Only case when it is not possible to create duplicate runtime is when the name input is changed as the last input to the duplicate name.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (DROOLS-1151) Missing libraries in new jBPM project
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1151?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-1151:
--------------------------------
Fix Version/s: 6.4.0.Final
> Missing libraries in new jBPM project
> -------------------------------------
>
> Key: DROOLS-1151
> URL: https://issues.jboss.org/browse/DROOLS-1151
> Project: Drools
> Issue Type: Bug
> Components: eclipse plugin
> Affects Versions: 6.4.0.Final
> Environment: * JBDS 9.1.0.GA
> * drools-jbpm plugin 6.4.1.201604291802
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Fix For: 6.4.0.Final
>
>
> In project created via [1] are missing libraries. Specifically classes from packages [2] can not be found.
> [1]
> File -> New -> Other -> jBPM -> jBPM project -> project with example files -> build project using Java and jBPM classes
> [2]
> javax.persistence.*
> org.jbpm.test.*
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (DROOLS-1151) Missing libraries in new jBPM project
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1151?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-1151:
-------------------------------------
Verified on:
JBDS-IS 9.0.0.GA (with Drools 6.4.1.Final-v20160503-1355-B205)
> Missing libraries in new jBPM project
> -------------------------------------
>
> Key: DROOLS-1151
> URL: https://issues.jboss.org/browse/DROOLS-1151
> Project: Drools
> Issue Type: Bug
> Components: eclipse plugin
> Affects Versions: 6.4.0.Final
> Environment: * JBDS 9.1.0.GA
> * drools-jbpm plugin 6.4.1.201604291802
> Reporter: Jozef Marko
> Assignee: Jozef Marko
> Fix For: 6.4.0.Final
>
>
> In project created via [1] are missing libraries. Specifically classes from packages [2] can not be found.
> [1]
> File -> New -> Other -> jBPM -> jBPM project -> project with example files -> build project using Java and jBPM classes
> [2]
> javax.persistence.*
> org.jbpm.test.*
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (WFLY-6584) Upgrade Undertow to 1.3.22
by Mathieu Lachance (JIRA)
Mathieu Lachance created WFLY-6584:
--------------------------------------
Summary: Upgrade Undertow to 1.3.22
Key: WFLY-6584
URL: https://issues.jboss.org/browse/WFLY-6584
Project: WildFly
Issue Type: Component Upgrade
Components: Web (Undertow)
Affects Versions: 10.0.0.Final
Reporter: Mathieu Lachance
Assignee: Stuart Douglas
Fix For: 10.1.0.Final
If it's not too late for the Wildfly 10.1.0.Final release, I'd like to benefits from UNDERTOW-707 which is contained in Undertow 1.3.22.Final.
Thanks.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (WFLY-6405) Performance: WeldDeployment.getBeanDeploymentArchive method is synchronized
by Panos Grigoropoulos (JIRA)
[ https://issues.jboss.org/browse/WFLY-6405?page=com.atlassian.jira.plugin.... ]
Panos Grigoropoulos commented on WFLY-6405:
-------------------------------------------
Is this planned for the next release?
Also, on line 240 (containsKey) of the proposed solution, you should check if the specified key is not null otherwise NullPointerException...
> Performance: WeldDeployment.getBeanDeploymentArchive method is synchronized
> ---------------------------------------------------------------------------
>
> Key: WFLY-6405
> URL: https://issues.jboss.org/browse/WFLY-6405
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, Class Loading
> Affects Versions: 10.0.0.Final
> Reporter: Panos Grigoropoulos
> Assignee: Stuart Douglas
>
> (Wildfly 10.0.0.FINAL)
> During the performance test of my app (50 concurrent users with jmeter) I am running into the following issue:
> There are locked threads in the method WeldDeployment.getBeanDeploymentArchive(). Looking the code, this method is synchronized, so it makes sense. The question is, is this the expected behavior or this is a bug. In both cases is there any workaround to overcome this limitation?
> STACK TRACE:
> ....
> org.jboss.as.weld.WeldProvider$CdiImpl.getBeanManager():73
> org.jboss.as.weld.WeldProvider$CdiImpl.getBeanManager():93
> org.jboss.as.weld.deployment.WeldDeployment.getBeanDeploymentArchive():226
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years