[JBoss JIRA] (DROOLS-4497) "Finish" button on new column creation enabled
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-4497?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi updated DROOLS-4497:
-------------------------------------
Description:
# Created "Person" data object with three field [^Person.java] .
# Created "PersonGDT" guided decision table with wizard (hit policy "none", "Limited entry" type). [^PersonGDT.gdst]
# Trying to insert new column: ""Unexpected error" when click "Finish" button without selecting a column type in the box
# The popup error appear.
I think user should "guided" through UI to and it should not possible for him to execute "illegal" action. In that situation, the issue is that the user *must* select a type *before* clicking finish; but if the user does not knows the tool, seeing the "Finish" button enabled, expects that clicking such button would lead to column creation; so the "error" is that the button should be disable until the user select a column type
was:
# Created "Person" data object with three field [^Person.java] .
# Created "PersonGDT" guided decision table with wizard (hit policy "none", "Limited entry" type). [^PersonGDT.gdst]
# Trying to insert new column: ""Unexpected error" when click "Finish" button.
# Can not proceed further.
> "Finish" button on new column creation enabled
> ----------------------------------------------
>
> Key: DROOLS-4497
> URL: https://issues.jboss.org/browse/DROOLS-4497
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor
> Environment: jbpm-server-distribution-7.26.0.Final-dist
> Reporter: Gabriele Cardosi
> Assignee: Toni Rikkola
> Priority: Major
> Attachments: Person.java, PersonGDT.gdst
>
>
> # Created "Person" data object with three field [^Person.java] .
> # Created "PersonGDT" guided decision table with wizard (hit policy "none", "Limited entry" type). [^PersonGDT.gdst]
> # Trying to insert new column: ""Unexpected error" when click "Finish" button without selecting a column type in the box
> # The popup error appear.
> I think user should "guided" through UI to and it should not possible for him to execute "illegal" action. In that situation, the issue is that the user *must* select a type *before* clicking finish; but if the user does not knows the tool, seeing the "Finish" button enabled, expects that clicking such button would lead to column creation; so the "error" is that the button should be disable until the user select a column type
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (DROOLS-4497) "Finish" button on new column creation enabled
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-4497?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi updated DROOLS-4497:
-------------------------------------
Summary: "Finish" button on new column creation enabled (was: Failed to create new column inside Guided Decision Table)
> "Finish" button on new column creation enabled
> ----------------------------------------------
>
> Key: DROOLS-4497
> URL: https://issues.jboss.org/browse/DROOLS-4497
> Project: Drools
> Issue Type: Bug
> Components: Guided Decision Table Editor
> Environment: jbpm-server-distribution-7.26.0.Final-dist
> Reporter: Gabriele Cardosi
> Assignee: Toni Rikkola
> Priority: Major
> Attachments: Person.java, PersonGDT.gdst
>
>
> # Created "Person" data object with three field [^Person.java] .
> # Created "PersonGDT" guided decision table with wizard (hit policy "none", "Limited entry" type). [^PersonGDT.gdst]
> # Trying to insert new column: ""Unexpected error" when click "Finish" button.
> # Can not proceed further.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (WFLY-12462) Incompatible conflicting binding Exception and EJB naming
by Jaikiran Pai (Jira)
[ https://issues.jboss.org/browse/WFLY-12462?page=com.atlassian.jira.plugin... ]
Jaikiran Pai commented on WFLY-12462:
-------------------------------------
[~usharik], I haven't yet been able to reproduce this, even with the sample application that you shared. So a few questions:
1. Does your WildFly (standalone) configuration have any changes than the one that's shipped by default? Can you attach the one you are using?
2. How are you deploying the application? Is any IDE involved?
> Incompatible conflicting binding Exception and EJB naming
> ---------------------------------------------------------
>
> Key: WFLY-12462
> URL: https://issues.jboss.org/browse/WFLY-12462
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, EJB
> Affects Versions: 17.0.1.Final
> Environment: MacOS High Sierra
> Reporter: Alexey Usharovski
> Assignee: Cheng Fang
> Priority: Minor
> Attachments: server.log.zip, simplewebapp-lesson-6-ejb.zip, war-content.txt.zip
>
>
> Wired exception for very simple EJB with @Remote annotated interface in time of deploy to WildFly 17.0.1.Final
> {code:java}
> @Stateless
> public class UserServiceImpl implements UserServiceRemote {
> @Override
> public List<UserRepr> getAllUsers() {
> return null;
> }
> }
> @Remote
> public interface UserServiceRemote {
> List<UserRepr> getAllUsers();
> }
> {code}
> The exception is
> {code}
> Caused by: java.lang.IllegalArgumentException: WFLYEE0047: Incompatible conflicting binding at java:jboss/exported/simple-webapp/UserServiceImpl!ru.geekbrains.jsf.UserServiceRemote
> source: org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor$2@6aba1c4b"},
> "WFLYCTL0412: Required services that are not installed:" => [ "jboss.deployment.unit.\"simple-webapp.war\".beanmanager", "jboss.deployment.unit.\"simple-webapp.war\".WeldStartService" ],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => [ "jboss.deployment.unit.\"simple-webapp.war\".batch.artifact.factory is missing [jboss.deployment.unit.\"simple-webapp.war\".beanmanager]",
> "jboss.deployment.unit.\"simple-webapp.war\".weld.weldClassIntrospector is missing [jboss.deployment.unit.\"simple-webapp.war\".beanmanager, jboss.deployment.unit.\"simple-webapp.war\".WeldStartService]" ] }
> {code}
> Notice that problem could be resolved by undeploy and Wildfly server restart. May be something wrong with JNDI content?
> I've tried to look through the web console but found nothing interesting.
> Full application code on GitHub https://github.com/usharik/simplewebapp/tree/lesson-6-ejb
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (WFLY-12446) Memory leak in StatelessSessionComponent
by Jaikiran Pai (Jira)
[ https://issues.jboss.org/browse/WFLY-12446?page=com.atlassian.jira.plugin... ]
Jaikiran Pai commented on WFLY-12446:
-------------------------------------
[~jbaesner], would you be able to enable TRACE level logging for "org.jboss.as.ejb3" package and then attach the generated logs to this issue? If you have access to the generated heap dump file, attaching that too will help. I would have tried your reproducer, but it requires SOAP UI, which I don't have access to and I'm being lazy to set it up.
> Memory leak in StatelessSessionComponent
> ----------------------------------------
>
> Key: WFLY-12446
> URL: https://issues.jboss.org/browse/WFLY-12446
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 17.0.1.Final
> Reporter: Joerg Baesner
> Assignee: Cheng Fang
> Priority: Major
> Attachments: playground-jee8.zip
>
>
> When running the attached reproducer application and doing a memory analysis afterwards, it looks like a memory leak, e. g.
> {code}
> One instance of "org.jboss.as.ejb3.component.stateless.StatelessSessionComponent" loaded by "org.jboss.modules.ModuleClassLoader @ 0x5e0fbc2e0" occupies 936,593,520 (96.13%) bytes. The memory is accumulated in one instance of "java.util.concurrent.ConcurrentLinkedQueue$Node" loaded by "<system class loader>".
> {code}
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (AG-117) Expose configuration option for ConnectionWrapper.trackStatements
by Luis Barreiro (Jira)
[ https://issues.jboss.org/browse/AG-117?page=com.atlassian.jira.plugin.sys... ]
Luis Barreiro resolved AG-117.
------------------------------
Fix Version/s: 1.6
Resolution: Done
> Expose configuration option for ConnectionWrapper.trackStatements
> -----------------------------------------------------------------
>
> Key: AG-117
> URL: https://issues.jboss.org/browse/AG-117
> Project: Agroal
> Issue Type: Bug
> Components: pool
> Affects Versions: 1.5
> Reporter: John O'Hara
> Assignee: Luis Barreiro
> Priority: Major
> Fix For: 1.6
>
>
> Please can we expose a configuration option for io.agroal.pool.wrapper.ConnectionWrapper.trackStatements?
> At present, the default behaviour is to track prepared statements and close all statements when a connection is returned to the connection pool. There are instances when we do not wish to close prepared statements, when we wish to reuse prepared statements
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months
[JBoss JIRA] (WFCORE-4646) Include core-security-realms in Galleon layer set used in -Dts.layers tests
by Brian Stansberry (Jira)
Brian Stansberry created WFCORE-4646:
----------------------------------------
Summary: Include core-security-realms in Galleon layer set used in -Dts.layers tests
Key: WFCORE-4646
URL: https://issues.jboss.org/browse/WFCORE-4646
Project: WildFly Core
Issue Type: Task
Components: Test Suite
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Follow-on to WFCORE-4642. The configs we expect to promote on OpenShift will include core-security-realms because this is what allows an auto-generated TLS certificate to be used for simple OOTB HTTPS. So, include that in the config of the installations that -Dts.layers users.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 8 months