[JBoss JIRA] (WFLY-9516) JPA deployer adding cross sub deployment dependencies when multiple persistence units deployed
by Scott Marlow (JIRA)
[ https://issues.jboss.org/browse/WFLY-9516?page=com.atlassian.jira.plugin.... ]
Scott Marlow commented on WFLY-9516:
------------------------------------
Next step will be recreating failure in a WildFly unit test.
> JPA deployer adding cross sub deployment dependencies when multiple persistence units deployed
> ----------------------------------------------------------------------------------------------
>
> Key: WFLY-9516
> URL: https://issues.jboss.org/browse/WFLY-9516
> Project: WildFly
> Issue Type: Bug
> Components: JPA / Hibernate
> Affects Versions: 11.0.0.Final
> Reporter: Brad Maxwell
> Assignee: Scott Marlow
>
> If an ear contains two EJB sub deployments which each contain a Persistence Unit and a Stateless EJB which injects the PU that is in its jar using @PersistenceContext. There is a dependency being added where in the Stateless EJB from one deployment depends on the PU from the other jar. It appears this is happening after this bug fix WFLY-1531
> {code}
> app.ear
> - ejb-with-pu1.jar
> - ejb-with-pu2.jar
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (DROOLS-2129) Lock the rule validation button
by Edson Tirelli (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2129?page=com.atlassian.jira.plugi... ]
Edson Tirelli reassigned DROOLS-2129:
-------------------------------------
Assignee: Toni Rikkola (was: Edson Tirelli)
> Lock the rule validation button
> -------------------------------
>
> Key: DROOLS-2129
> URL: https://issues.jboss.org/browse/DROOLS-2129
> Project: Drools
> Issue Type: Bug
> Components: kie server
> Affects Versions: 6.5.0.Final
> Reporter: Petr Farmakovsky
> Assignee: Toni Rikkola
>
> Our business users often use rules with a large number of lines. After saving, they validate the rules. Due to large size of rules, the validation process takes a lot of time. The validation button in the Drools interface is not blocked, so users have time to press it 5-10 times before receiving a response. In this case, the server does not manage to process such a large number of requests due to lack of resources.
> We learned how to diagnose a lack of resources and tried to restart the server. However, the javascript that performs the validation continues to load the server after the restart. Therefore, the only way that helps us with a lack of resources is to stop the tomcat server, and start it in a few minutes.
> Can you make a lock the rule validation button when it is in process?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months