[JBoss JIRA] (WFLY-11034) Integration with grpc (high performance, open-source universal RPC framework)
by Brad Maxwell (Jira)
[ https://issues.redhat.com/browse/WFLY-11034?page=com.atlassian.jira.plugi... ]
Brad Maxwell commented on WFLY-11034:
-------------------------------------
[~rogerio.ferreira1] I created WFLY-13530 for the REST use case in particular. REST Engrs have been discussing it, so you can monitor WFLY-13530
> Integration with grpc (high performance, open-source universal RPC framework)
> -----------------------------------------------------------------------------
>
> Key: WFLY-11034
> URL: https://issues.redhat.com/browse/WFLY-11034
> Project: WildFly
> Issue Type: Feature Request
> Components: Remoting
> Affects Versions: 14.0.0.Final
> Reporter: Brad Maxwell
> Priority: Major
>
> https://grpc.io/
> grpc should be seamlessly integrated into Wildfly as grpc support for EJB's and other EE components would make it very easy for microservices written in other languages to interact with Wildfly.
> grpc might be a good replacement candidate for corba (binary marshalling, efficiency, good community and support, modern, http/2, streaming, strong contract).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 10 months
[JBoss JIRA] (WFLY-13457) Generic JMS RA leaks memory when using JMS 2.0 API with TIBCO EMS
by Ilia Vassilev (Jira)
[ https://issues.redhat.com/browse/WFLY-13457?page=com.atlassian.jira.plugi... ]
Ilia Vassilev updated WFLY-13457:
---------------------------------
Labels: downstream_dependency (was: )
> Generic JMS RA leaks memory when using JMS 2.0 API with TIBCO EMS
> -----------------------------------------------------------------
>
> Key: WFLY-13457
> URL: https://issues.redhat.com/browse/WFLY-13457
> Project: WildFly
> Issue Type: Bug
> Components: JCA, JMS
> Reporter: Emmanuel Hugonnet
> Assignee: Emmanuel Hugonnet
> Priority: Major
> Labels: downstream_dependency
> Fix For: 20.0.0.Final
>
>
> There is a memory leak when using JBoss EAP Generic JMS Resource Adapter with TIBCO EMS JMS 2.0 API. This is due to the way TIBCO decided to implement their JMS 2.0 API.
> When using JMSContext JMSProducers are only closed when JMSContext is closed which never happens in a life time of an application since that would negates any benefits of having JCA pool.
> This could be easily observed when examining memory dump. It is possible to see a large accumulation of JMSProducer objects in memory.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 10 months
[JBoss JIRA] (WFLY-11999) Wildfly creates to many instances of all web service classes
by Parul Sharma (Jira)
[ https://issues.redhat.com/browse/WFLY-11999?page=com.atlassian.jira.plugi... ]
Parul Sharma edited comment on WFLY-11999 at 5/28/20 1:02 PM:
--------------------------------------------------------------
[~jim.ma] [~s.frings74] Can you please let me know what is the purpose of using @ApplicationScoped and @webservice both?
*@Application* is responsible for initializing CDI/weld that's why multiple instances are creating.
One is creating for web services and another for CDI/Weld. You didn't face this issue in apache because it doesn't have CDI/weld.
was (Author: parsharma):
[~jim.ma] [~s.frings74] Can you please let me know what is the purpose of using @ApplicationScoped and @webservice both?
*@Application *is responsible for initializing CDI/weld that's why multiple instances are creating.
One is creating for web services and another for CDI/Weld. You didn't face this issue in apache because it doesn't have CDI/weld.
> Wildfly creates to many instances of all web service classes
> ------------------------------------------------------------
>
> Key: WFLY-11999
> URL: https://issues.redhat.com/browse/WFLY-11999
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 8.0.0.Final, 16.0.0.Final, 19.0.0.Final
> Environment: Ubuntu 18.10 64bit, Open JDK 8 or Open JDK 11
> Reporter: Stefan Frings
> Assignee: Parul Sharma
> Priority: Minor
> Attachments: Test-1.0-SNAPSHOT.war, Test.zip, standalone.xml
>
>
> 1) My @Webservice classes are all constructed multiple times (3x - 4x) but I expected only one instance.
> 2) Only the second instance receives a call to the observer method for initialization. I expect that this method is called in each instance.
> The issue can be reproduced with the attached minimum project on Wildfly 8 with JDK 8 as well as Wildfly 16 with JDK 11.
> Complete source code of the whole application:
> {code}
> package com.mvneco.test;
> import javax.enterprise.context.ApplicationScoped;
> import javax.enterprise.context.Initialized;
> import javax.enterprise.event.Observes;
> import javax.jws.WebMethod;
> import javax.jws.WebService;
> import org.apache.commons.logging.Log;
> import org.apache.commons.logging.LogFactory;
> @ApplicationScoped
> @WebService
> public class SoapService
> {
> private Log log = LogFactory.getLog(SoapService.class);
> public SoapService()
> {
> log.debug("Init SoapService 1");
> }
> @WebMethod(exclude = true)
> public void init(@Observes @Initialized(ApplicationScoped.class) Object init)
> {
> log.debug("Init SoapService 2");
> }
> @WebMethod
> public String test(String payload)
> {
> log.debug("Start test(). payload="+payload);
> return "OK";
> }
> }
> {code}
> Extract from Log messages that show the issue (the complete log is in the attached ZIP):
> {code}
> 2019-04-17 13:12:21,399 DEBUG [com.mvneco.test.SoapService] (MSC service thread 1-2) Init SoapService 1
> 2019-04-17 13:12:23,068 DEBUG [com.mvneco.test.SoapService] (ServerService Thread Pool -- 74) Init SoapService 1
> 2019-04-17 13:12:23,070 DEBUG [com.mvneco.test.SoapService] (ServerService Thread Pool -- 74) Init SoapService 2
> 2019-04-17 13:12:23,475 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) started in 10514ms - Started 510 of 699 services (337 services are lazy, passive or on-demand)
> 2019-04-17 13:12:28,920 INFO [org.apache.cxf.services.SoapService.REQ_IN] (default task-1) REQ_IN
> Address: http://localhost:8080/Test-1.0-SNAPSHOT/SoapService
> ...
> 2019-04-17 13:12:28,932 DEBUG [com.mvneco.test.SoapService] (default task-1) Init SoapService 1
> 2019-04-17 13:12:28,937 DEBUG [com.mvneco.test.SoapService] (default task-1) Init SoapService 1
> 2019-04-17 13:12:28,937 DEBUG [com.mvneco.test.SoapService] (default task-1) Start test(). payload=?
> 2019-04-17 13:12:28,969 INFO [org.apache.cxf.services.SoapService.RESP_OUT] (default task-1) RESP_OUT
> Content-Type: text/xml
> ...
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 10 months
[JBoss JIRA] (WFLY-11999) Wildfly creates to many instances of all web service classes
by Parul Sharma (Jira)
[ https://issues.redhat.com/browse/WFLY-11999?page=com.atlassian.jira.plugi... ]
Parul Sharma edited comment on WFLY-11999 at 5/28/20 1:02 PM:
--------------------------------------------------------------
[~jim.ma] [~s.frings74] Can you please let me know what is the purpose of using @ApplicationScoped and @webservice both?
*@Application* is responsible for initializing CDI/weld that's why multiple instances are creating.
One is creating for web services and another for CDI/Weld. You didn't face this issue in (multiple instances) apache because it doesn't have CDI/weld.
was (Author: parsharma):
[~jim.ma] [~s.frings74] Can you please let me know what is the purpose of using @ApplicationScoped and @webservice both?
*@Application* is responsible for initializing CDI/weld that's why multiple instances are creating.
One is creating for web services and another for CDI/Weld. You didn't face this issue in apache because it doesn't have CDI/weld.
> Wildfly creates to many instances of all web service classes
> ------------------------------------------------------------
>
> Key: WFLY-11999
> URL: https://issues.redhat.com/browse/WFLY-11999
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 8.0.0.Final, 16.0.0.Final, 19.0.0.Final
> Environment: Ubuntu 18.10 64bit, Open JDK 8 or Open JDK 11
> Reporter: Stefan Frings
> Assignee: Parul Sharma
> Priority: Minor
> Attachments: Test-1.0-SNAPSHOT.war, Test.zip, standalone.xml
>
>
> 1) My @Webservice classes are all constructed multiple times (3x - 4x) but I expected only one instance.
> 2) Only the second instance receives a call to the observer method for initialization. I expect that this method is called in each instance.
> The issue can be reproduced with the attached minimum project on Wildfly 8 with JDK 8 as well as Wildfly 16 with JDK 11.
> Complete source code of the whole application:
> {code}
> package com.mvneco.test;
> import javax.enterprise.context.ApplicationScoped;
> import javax.enterprise.context.Initialized;
> import javax.enterprise.event.Observes;
> import javax.jws.WebMethod;
> import javax.jws.WebService;
> import org.apache.commons.logging.Log;
> import org.apache.commons.logging.LogFactory;
> @ApplicationScoped
> @WebService
> public class SoapService
> {
> private Log log = LogFactory.getLog(SoapService.class);
> public SoapService()
> {
> log.debug("Init SoapService 1");
> }
> @WebMethod(exclude = true)
> public void init(@Observes @Initialized(ApplicationScoped.class) Object init)
> {
> log.debug("Init SoapService 2");
> }
> @WebMethod
> public String test(String payload)
> {
> log.debug("Start test(). payload="+payload);
> return "OK";
> }
> }
> {code}
> Extract from Log messages that show the issue (the complete log is in the attached ZIP):
> {code}
> 2019-04-17 13:12:21,399 DEBUG [com.mvneco.test.SoapService] (MSC service thread 1-2) Init SoapService 1
> 2019-04-17 13:12:23,068 DEBUG [com.mvneco.test.SoapService] (ServerService Thread Pool -- 74) Init SoapService 1
> 2019-04-17 13:12:23,070 DEBUG [com.mvneco.test.SoapService] (ServerService Thread Pool -- 74) Init SoapService 2
> 2019-04-17 13:12:23,475 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) started in 10514ms - Started 510 of 699 services (337 services are lazy, passive or on-demand)
> 2019-04-17 13:12:28,920 INFO [org.apache.cxf.services.SoapService.REQ_IN] (default task-1) REQ_IN
> Address: http://localhost:8080/Test-1.0-SNAPSHOT/SoapService
> ...
> 2019-04-17 13:12:28,932 DEBUG [com.mvneco.test.SoapService] (default task-1) Init SoapService 1
> 2019-04-17 13:12:28,937 DEBUG [com.mvneco.test.SoapService] (default task-1) Init SoapService 1
> 2019-04-17 13:12:28,937 DEBUG [com.mvneco.test.SoapService] (default task-1) Start test(). payload=?
> 2019-04-17 13:12:28,969 INFO [org.apache.cxf.services.SoapService.RESP_OUT] (default task-1) RESP_OUT
> Content-Type: text/xml
> ...
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 10 months
[JBoss JIRA] (WFLY-11999) Wildfly creates to many instances of all web service classes
by Parul Sharma (Jira)
[ https://issues.redhat.com/browse/WFLY-11999?page=com.atlassian.jira.plugi... ]
Parul Sharma edited comment on WFLY-11999 at 5/28/20 1:01 PM:
--------------------------------------------------------------
[~jim.ma] [~s.frings74] Can you please let me know what is the purpose of using @ApplicationScoped and @webservice both?
*@Application *is responsible for initializing CDI/weld that's why multiple instances are creating.
One is creating for web services and another for CDI/Weld. You didn't face this issue in apache because it doesn't have CDI/weld.
was (Author: parsharma):
[~jim.ma] [~s.frings74] Can you please let me know what is the purpose of using @ApplicationScoped and @webservice both?
> Wildfly creates to many instances of all web service classes
> ------------------------------------------------------------
>
> Key: WFLY-11999
> URL: https://issues.redhat.com/browse/WFLY-11999
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 8.0.0.Final, 16.0.0.Final, 19.0.0.Final
> Environment: Ubuntu 18.10 64bit, Open JDK 8 or Open JDK 11
> Reporter: Stefan Frings
> Assignee: Parul Sharma
> Priority: Minor
> Attachments: Test-1.0-SNAPSHOT.war, Test.zip, standalone.xml
>
>
> 1) My @Webservice classes are all constructed multiple times (3x - 4x) but I expected only one instance.
> 2) Only the second instance receives a call to the observer method for initialization. I expect that this method is called in each instance.
> The issue can be reproduced with the attached minimum project on Wildfly 8 with JDK 8 as well as Wildfly 16 with JDK 11.
> Complete source code of the whole application:
> {code}
> package com.mvneco.test;
> import javax.enterprise.context.ApplicationScoped;
> import javax.enterprise.context.Initialized;
> import javax.enterprise.event.Observes;
> import javax.jws.WebMethod;
> import javax.jws.WebService;
> import org.apache.commons.logging.Log;
> import org.apache.commons.logging.LogFactory;
> @ApplicationScoped
> @WebService
> public class SoapService
> {
> private Log log = LogFactory.getLog(SoapService.class);
> public SoapService()
> {
> log.debug("Init SoapService 1");
> }
> @WebMethod(exclude = true)
> public void init(@Observes @Initialized(ApplicationScoped.class) Object init)
> {
> log.debug("Init SoapService 2");
> }
> @WebMethod
> public String test(String payload)
> {
> log.debug("Start test(). payload="+payload);
> return "OK";
> }
> }
> {code}
> Extract from Log messages that show the issue (the complete log is in the attached ZIP):
> {code}
> 2019-04-17 13:12:21,399 DEBUG [com.mvneco.test.SoapService] (MSC service thread 1-2) Init SoapService 1
> 2019-04-17 13:12:23,068 DEBUG [com.mvneco.test.SoapService] (ServerService Thread Pool -- 74) Init SoapService 1
> 2019-04-17 13:12:23,070 DEBUG [com.mvneco.test.SoapService] (ServerService Thread Pool -- 74) Init SoapService 2
> 2019-04-17 13:12:23,475 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 16.0.0.Final (WildFly Core 8.0.0.Final) started in 10514ms - Started 510 of 699 services (337 services are lazy, passive or on-demand)
> 2019-04-17 13:12:28,920 INFO [org.apache.cxf.services.SoapService.REQ_IN] (default task-1) REQ_IN
> Address: http://localhost:8080/Test-1.0-SNAPSHOT/SoapService
> ...
> 2019-04-17 13:12:28,932 DEBUG [com.mvneco.test.SoapService] (default task-1) Init SoapService 1
> 2019-04-17 13:12:28,937 DEBUG [com.mvneco.test.SoapService] (default task-1) Init SoapService 1
> 2019-04-17 13:12:28,937 DEBUG [com.mvneco.test.SoapService] (default task-1) Start test(). payload=?
> 2019-04-17 13:12:28,969 INFO [org.apache.cxf.services.SoapService.RESP_OUT] (default task-1) RESP_OUT
> Content-Type: text/xml
> ...
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 10 months
[JBoss JIRA] (WFLY-13457) Generic JMS RA leaks memory when using JMS 2.0 API with TIBCO EMS
by Emmanuel Hugonnet (Jira)
[ https://issues.redhat.com/browse/WFLY-13457?page=com.atlassian.jira.plugi... ]
Emmanuel Hugonnet resolved WFLY-13457.
--------------------------------------
Fix Version/s: 20.0.0.Final
Resolution: Done
> Generic JMS RA leaks memory when using JMS 2.0 API with TIBCO EMS
> -----------------------------------------------------------------
>
> Key: WFLY-13457
> URL: https://issues.redhat.com/browse/WFLY-13457
> Project: WildFly
> Issue Type: Bug
> Components: JCA, JMS
> Reporter: Emmanuel Hugonnet
> Assignee: Emmanuel Hugonnet
> Priority: Major
> Fix For: 20.0.0.Final
>
>
> There is a memory leak when using JBoss EAP Generic JMS Resource Adapter with TIBCO EMS JMS 2.0 API. This is due to the way TIBCO decided to implement their JMS 2.0 API.
> When using JMSContext JMSProducers are only closed when JMSContext is closed which never happens in a life time of an application since that would negates any benefits of having JCA pool.
> This could be easily observed when examining memory dump. It is possible to see a large accumulation of JMSProducer objects in memory.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 10 months
[JBoss JIRA] (DROOLS-5331) Support for Enums in Rule Test Scenario
by Yeser Amer (Jira)
[ https://issues.redhat.com/browse/DROOLS-5331?page=com.atlassian.jira.plug... ]
Yeser Amer commented on DROOLS-5331:
------------------------------------
Added _EnumTest.java_ and _Customer.java_ , Data Objects to be used as a test case.
> Support for Enums in Rule Test Scenario
> ---------------------------------------
>
> Key: DROOLS-5331
> URL: https://issues.redhat.com/browse/DROOLS-5331
> Project: Drools
> Issue Type: Feature Request
> Reporter: Yeser Amer
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
> Attachments: Customer.java, EnumTest.java
>
>
> Currently, Test Scenario doesn't support an attribute of Enumeration type.
> In case of RULE Scenario:
> Loading a Data Object with such attribute, will result in Complex Type properties with a nested simple property "declaringClass" of "java.lang.Class" type.
> The expected result should be a Simple property of Enum type (in this case: category [java.lang.Enum] )
> In case of DMN Scenario:
> Currently no impacts
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 10 months
[JBoss JIRA] (DROOLS-5331) Support for Enums in Rule Test Scenario
by Yeser Amer (Jira)
[ https://issues.redhat.com/browse/DROOLS-5331?page=com.atlassian.jira.plug... ]
Yeser Amer updated DROOLS-5331:
-------------------------------
Attachment: EnumTest.java
> Support for Enums in Rule Test Scenario
> ---------------------------------------
>
> Key: DROOLS-5331
> URL: https://issues.redhat.com/browse/DROOLS-5331
> Project: Drools
> Issue Type: Feature Request
> Reporter: Yeser Amer
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
> Attachments: Customer.java, EnumTest.java
>
>
> Currently, Test Scenario doesn't support an attribute of Enumeration type.
> In case of RULE Scenario:
> Loading a Data Object with such attribute, will result in Complex Type properties with a nested simple property "declaringClass" of "java.lang.Class" type.
> The expected result should be a Simple property of Enum type (in this case: category [java.lang.Enum] )
> In case of DMN Scenario:
> Currently no impacts
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 10 months
[JBoss JIRA] (DROOLS-5331) Support for Enums in Rule Test Scenario
by Yeser Amer (Jira)
[ https://issues.redhat.com/browse/DROOLS-5331?page=com.atlassian.jira.plug... ]
Yeser Amer updated DROOLS-5331:
-------------------------------
Attachment: Customer.java
> Support for Enums in Rule Test Scenario
> ---------------------------------------
>
> Key: DROOLS-5331
> URL: https://issues.redhat.com/browse/DROOLS-5331
> Project: Drools
> Issue Type: Feature Request
> Reporter: Yeser Amer
> Assignee: Yeser Amer
> Priority: Major
> Labels: drools-tools
> Attachments: Customer.java, EnumTest.java
>
>
> Currently, Test Scenario doesn't support an attribute of Enumeration type.
> In case of RULE Scenario:
> Loading a Data Object with such attribute, will result in Complex Type properties with a nested simple property "declaringClass" of "java.lang.Class" type.
> The expected result should be a Simple property of Enum type (in this case: category [java.lang.Enum] )
> In case of DMN Scenario:
> Currently no impacts
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
3 years, 10 months