[JBoss JIRA] (JGRP-2246) Internal thread pool not created if default thread pool is injected
by Paul Ferraro (JIRA)
Paul Ferraro created JGRP-2246:
----------------------------------
Summary: Internal thread pool not created if default thread pool is injected
Key: JGRP-2246
URL: https://issues.jboss.org/browse/JGRP-2246
Project: JGroups
Issue Type: Bug
Affects Versions: 4.0.9
Reporter: Paul Ferraro
Assignee: Bela Ban
WildFly injects a custom thread pool into its JGroups transports. However, in JGroups 4.0.x, only the default thread pool exposes a setThreadPool(...) method. The internal thread pool does not. However, the logic within TP.init() will not create an internal thread pool if the default thread pool already exists (and is not shutdown), which is the case in WildFly.
Can we restore the TP.setInternalThreadPool(...) method?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFLY-9708) Wildfly 11.0.0.Final JSF 1.2 configuration error
by Martin Kouba (JIRA)
[ https://issues.jboss.org/browse/WFLY-9708?page=com.atlassian.jira.plugin.... ]
Martin Kouba commented on WFLY-9708:
------------------------------------
Thanks [~fjuma]. Then it seems the only way to run JSF 1.2 app on WildFly 11.0.0.Final is to bundle the JSF impl?
> Wildfly 11.0.0.Final JSF 1.2 configuration error
> ------------------------------------------------
>
> Key: WFLY-9708
> URL: https://issues.jboss.org/browse/WFLY-9708
> Project: WildFly
> Issue Type: Bug
> Components: CDI / Weld, JSF
> Affects Versions: 11.0.0.Final
> Reporter: Luis Canales
> Assignee: Martin Kouba
> Priority: Optional
> Attachments: log.txt
>
>
> Since WFLY-8815, the class WeldApplication extends ApplicationWrapper. The class "ApplicationWrapper" was created in JSF2.0, so when I try to build JSF1.2 modules (see https://developer.jboss.org/wiki/StepsToAddAnyNewJSFImplementationOrVersi...) and deploy a JSF1.2 application, I get this error:
> _java.lang.NoClassDefFoundError: Failed to link org/jboss/as/jsf/injection/weld/WeldApplication (Module "org.jboss.as.jsf-injection:mojarra-1.2_15" from local module loader @3aa9e816 (finder: local module finder @17d99928 (roots: C:\Java\wildfly-11.0.0.Final.gts\modules,C:\Java\wildfly-11.0.0.Final.gts\modules\system\layers\base))): javax/faces/application/ApplicationWrapper_
> If I change WeldApplication extends to ForwardingApplication and rebuild modules, the application runs OK.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (DROOLS-2256) [DMN Designer] Scrollbars in full screen mode
by Jozef Marko (JIRA)
Jozef Marko created DROOLS-2256:
-----------------------------------
Summary: [DMN Designer] Scrollbars in full screen mode
Key: DROOLS-2256
URL: https://issues.jboss.org/browse/DROOLS-2256
Project: Drools
Issue Type: Bug
Components: DMN Editor
Affects Versions: 7.6.0.Final
Reporter: Jozef Marko
Assignee: Michael Anstis
Attachments: Screenshot from 2018-01-19 13-39-20.png, Screenshot from 2018-01-19 13-39-52.png
The scroll bars doesn't work in some cases during full screen mode is in action.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (WFCORE-3512) ClassReflectionIndexUtil does not return default methods from findMethod
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3512?page=com.atlassian.jira.plugi... ]
Tomaz Cerar commented on WFCORE-3512:
-------------------------------------
Next version is 12, which should be released soon.
Currently there is no plan for 11.1.
> ClassReflectionIndexUtil does not return default methods from findMethod
> ------------------------------------------------------------------------
>
> Key: WFCORE-3512
> URL: https://issues.jboss.org/browse/WFCORE-3512
> Project: WildFly Core
> Issue Type: Bug
> Components: Server
> Reporter: Daniel Bildhauer
> Assignee: Stuart Douglas
> Fix For: 4.0.0.Alpha6
>
> Attachments: ejb-in-ear.zip, wildfly-ejb-in-ear-ear.ear
>
>
> This problem is in Wildfly Core, but manifests as an issue with EJB's in WildFly full.
> Given the following class/interface inheritance structure, the interface method doMagic could not be called from a remote view, even if there is a default implementation as given in the mixin interface. A local call works, but the remote call fails with a message like
> {code}
> org.jboss.invocation.CannotProceedException: INV000002: Invocation cannot proceed (end of interceptor chain has been hit)
> {code}
> Example code:
> {code}
> @Remote
> interface MyEJBInterface {
> void doMagic();
> }
> interface MyEJBMixin extends MyEJBInterface {
> default void doMagic() { .... }
> }
> @Stateless
> class MyEJBBean extends MyEJBMixin {
> }
> {code}
> The problem is inside the fix for WFLY-4354 bug, which checks only for the default method implementation in the interface declaring the method the first time but not in other interfaces.
> A example is attached and I will submitt a pull request with a fix.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (ELY-1481) Coverity, Explicit null dereferenced in FileSystemSecurityRealm
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/ELY-1481?page=com.atlassian.jira.plugin.s... ]
Ilia Vassilev reassigned ELY-1481:
----------------------------------
Assignee: Ilia Vassilev
> Coverity, Explicit null dereferenced in FileSystemSecurityRealm
> ---------------------------------------------------------------
>
> Key: ELY-1481
> URL: https://issues.jboss.org/browse/ELY-1481
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Authentication Client
> Affects Versions: 1.2.0.Beta11
> Reporter: Martin Choma
> Assignee: Ilia Vassilev
>
> There are 2 occurences of call to PasswordFactory.getInstance(algorithm) in FileSystemSecurityRealm where algorithm can be null, because algorithm is optional in wildfly-config.xml
> {code:xml|title=elytron-1_0_1.xsd}
> <xsd:complexType name="credential-type">
> <xsd:simpleContent>
> <xsd:extension base="xsd:string">
> <xsd:attribute name="algorithm" type="xsd:string" use="optional"/>
> <xsd:attribute name="format" type="xsd:string" use="optional"/>
> </xsd:extension>
> </xsd:simpleContent>
> </xsd:complexType>
> <xsd:complexType name="otp-credential-type">
> <xsd:simpleContent>
> <xsd:extension base="xsd:string">
> <xsd:attribute name="algorithm" type="xsd:string" use="optional"/>
> <xsd:attribute name="hash" type="xsd:string" use="optional"/>
> <xsd:attribute name="seed" type="xsd:string" use="optional"/>
> <xsd:attribute name="sequence" type="xsd:string" use="optional"/>
> </xsd:extension>
> </xsd:simpleContent>
> </xsd:complexType>
> {code}
> Algorithm is dereferenced in PasswordFactory.getInstance(algorithm) down in
> {code:java|title=java.security.Provider$ServiceKey.java}
> private ServiceKey(String type, String algorithm, boolean intern) {
> this.type = type;
> this.originalAlgorithm = algorithm;
> algorithm = algorithm.toUpperCase(ENGLISH);
> this.algorithm = intern ? algorithm.intern() : algorithm;
> }
> {code}
> [1] https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=44847...
> [2] https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=44847...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (DROOLS-2250) Align Engine hints in Decision Table column wizard with BAPL-708
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2250?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2250:
--------------------------------
Description:
Due to the BAPL-708 and the [doc|https://docs.google.com/spreadsheets/d/1kmK92hY3JJp7gZTvLzd0CawaZzvI2...] with new product terminology, we should update the Engine hint shown in the attached screenshots. We should use *decision engine* or *process / engine* instad of *inference engine*, *rules engine* etc.
[edited]
Also the Data Object designer affected, see the role hint.
!Screenshot from 2018-01-19 14-35-50.png|thumbnail!
was:
Due to the BAPL-708 and the [doc|https://docs.google.com/spreadsheets/d/1kmK92hY3JJp7gZTvLzd0CawaZzvI2...] with new product terminology, we should update the Engine hint shown in the attached screenshots. We should use *decision engine* or *process / engine* instad of *inference engine*, *rules engine* etc.
[edited]
Also the Data Object designer affected, see the role hint. !Screenshot from 2018-01-19 14-35-50.png|thumbnail!
> Align Engine hints in Decision Table column wizard with BAPL-708
> ----------------------------------------------------------------
>
> Key: DROOLS-2250
> URL: https://issues.jboss.org/browse/DROOLS-2250
> Project: Drools
> Issue Type: Task
> Components: Guided Decision Table Editor
> Affects Versions: 7.6.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Attachments: Screenshot from 2018-01-17 13-49-51.png, Screenshot from 2018-01-17 13-50-37.png, Screenshot from 2018-01-19 14-35-50.png
>
>
> Due to the BAPL-708 and the [doc|https://docs.google.com/spreadsheets/d/1kmK92hY3JJp7gZTvLzd0CawaZzvI2...] with new product terminology, we should update the Engine hint shown in the attached screenshots. We should use *decision engine* or *process / engine* instad of *inference engine*, *rules engine* etc.
> [edited]
> Also the Data Object designer affected, see the role hint.
> !Screenshot from 2018-01-19 14-35-50.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (DROOLS-2250) Align Engine hints in Decision Table column wizard with BAPL-708
by Jozef Marko (JIRA)
[ https://issues.jboss.org/browse/DROOLS-2250?page=com.atlassian.jira.plugi... ]
Jozef Marko updated DROOLS-2250:
--------------------------------
Description:
Due to the BAPL-708 and the [doc|https://docs.google.com/spreadsheets/d/1kmK92hY3JJp7gZTvLzd0CawaZzvI2...] with new product terminology, we should update the Engine hint shown in the attached screenshots. We should use *decision engine* or *process / engine* instad of *inference engine*, *rules engine* etc.
[edited]
Also the Data Object designer affected, see the role hint. !Screenshot from 2018-01-19 14-35-50.png|thumbnail!
was:Due to the BAPL-708 and the [doc|https://docs.google.com/spreadsheets/d/1kmK92hY3JJp7gZTvLzd0CawaZzvI2...] with new product terminology, we should update the Engine hint shown in the attached screenshots. We should use *decision engine* or *process / engine* instad of *inference engine*, *rules engine* etc.
> Align Engine hints in Decision Table column wizard with BAPL-708
> ----------------------------------------------------------------
>
> Key: DROOLS-2250
> URL: https://issues.jboss.org/browse/DROOLS-2250
> Project: Drools
> Issue Type: Task
> Components: Guided Decision Table Editor
> Affects Versions: 7.6.0.Final
> Reporter: Jozef Marko
> Assignee: Michael Anstis
> Attachments: Screenshot from 2018-01-17 13-49-51.png, Screenshot from 2018-01-17 13-50-37.png, Screenshot from 2018-01-19 14-35-50.png
>
>
> Due to the BAPL-708 and the [doc|https://docs.google.com/spreadsheets/d/1kmK92hY3JJp7gZTvLzd0CawaZzvI2...] with new product terminology, we should update the Engine hint shown in the attached screenshots. We should use *decision engine* or *process / engine* instad of *inference engine*, *rules engine* etc.
> [edited]
> Also the Data Object designer affected, see the role hint. !Screenshot from 2018-01-19 14-35-50.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months