[JBoss JIRA] (WFLY-9404) [GSS](7.2.0) Unable to deploy clustered ejb in a mixed domain.
by Brad Maxwell (JIRA)
Brad Maxwell created WFLY-9404:
----------------------------------
Summary: [GSS](7.2.0) Unable to deploy clustered ejb in a mixed domain.
Key: WFLY-9404
URL: https://issues.jboss.org/browse/WFLY-9404
Project: WildFly
Issue Type: Bug
Components: Clustering, EJB
Affects Versions: 11.0.0.CR1
Reporter: Brad Maxwell
Assignee: Paul Ferraro
Attachments: Clusterejb-0.0.1.jar, domain_EAP7.xml, host_EAP7.xml, host_slave_EAP6.xml
Using a ha profile in a mixed domain( i.e EAP 7 as a domain controler and EAP 6.3 as a slave) it does not seem possible to deploy ejb successfully.
While deploying a simple @clustered ejb on EAP 6.3 server below exception was thrown. This issue is easily replicated.
{code:java}
19:12:11,886 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-16) JNDI bindings for session bean named CounterBean in deployment unit deployment "Clusterejb-0.0.1.jar" are as follows:
java:global/Clusterejb-0.0.1/CounterBean!com.test.Counter
java:app/Clusterejb-0.0.1/CounterBean!com.test.Counter
java:module/CounterBean!com.test.Counter
java:jboss/exported/Clusterejb-0.0.1/CounterBean!com.test.Counter
java:global/Clusterejb-0.0.1/CounterBean
java:app/Clusterejb-0.0.1/CounterBean
java:module/CounterBean
19:12:12,089 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS018559: Deployed "Clusterejb-0.0.1.jar" (runtime-name : "Clusterejb-0.0.1.jar")
19:12:12,090 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014775: New missing/unsatisfied dependencies:
service jboss.ejb.cache.cluster.simple (missing) dependents: [service jboss.ejb.cache.cluster]
19:12:12,093 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started (with errors) in 2654ms - Started 185 of 293 services (14 services failed or missing dependencies, 117 services are lazy, passive or on-demand)
{code}
I have attached the configuration files for both EAP 7 and EAP 6.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (WFLY-9403) Unable to deploy clustered ejb in a mixed domain.
by Brad Maxwell (JIRA)
[ https://issues.jboss.org/browse/WFLY-9403?page=com.atlassian.jira.plugin.... ]
Brad Maxwell moved JBEAP-13293 to WFLY-9403:
--------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-9403 (was: JBEAP-13293)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Clustering
EJB
(was: Clustering)
(was: EJB)
Affects Version/s: 11.0.0.CR1
(was: 7.0.7.GA)
> Unable to deploy clustered ejb in a mixed domain.
> -------------------------------------------------
>
> Key: WFLY-9403
> URL: https://issues.jboss.org/browse/WFLY-9403
> Project: WildFly
> Issue Type: Bug
> Components: Clustering, EJB
> Affects Versions: 11.0.0.CR1
> Reporter: Brad Maxwell
> Assignee: Paul Ferraro
> Attachments: Clusterejb-0.0.1.jar, domain_EAP7.xml, host_EAP7.xml, host_slave_EAP6.xml
>
>
> Using a ha profile in a mixed domain( i.e EAP 7 as a domain controler and EAP 6.3 as a slave) it does not seem possible to deploy ejb successfully.
> While deploying a simple @clustered ejb on EAP 6.3 server below exception was thrown. This issue is easily replicated.
> {code:java}
> 19:12:11,886 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-16) JNDI bindings for session bean named CounterBean in deployment unit deployment "Clusterejb-0.0.1.jar" are as follows:
> java:global/Clusterejb-0.0.1/CounterBean!com.test.Counter
> java:app/Clusterejb-0.0.1/CounterBean!com.test.Counter
> java:module/CounterBean!com.test.Counter
> java:jboss/exported/Clusterejb-0.0.1/CounterBean!com.test.Counter
> java:global/Clusterejb-0.0.1/CounterBean
> java:app/Clusterejb-0.0.1/CounterBean
> java:module/CounterBean
> 19:12:12,089 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS018559: Deployed "Clusterejb-0.0.1.jar" (runtime-name : "Clusterejb-0.0.1.jar")
> 19:12:12,090 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
> JBAS014775: New missing/unsatisfied dependencies:
> service jboss.ejb.cache.cluster.simple (missing) dependents: [service jboss.ejb.cache.cluster]
> 19:12:12,093 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started (with errors) in 2654ms - Started 185 of 293 services (14 services failed or missing dependencies, 117 services are lazy, passive or on-demand)
> {code}
> I have attached the configuration files for both EAP 7 and EAP 6.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (WFCORE-2951) Add JSON formatter resources to the logging subsystem
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2951?page=com.atlassian.jira.plugi... ]
James Perkins commented on WFCORE-2951:
---------------------------------------
Adding a logstash formatter would likely only be for convenience. Really it's just a {{json-formatter}} with the {{timestamp}} key replaced with {{@timestamp}} and a {{@version : 1}} key/value pair added to the output. This would be very easy to do with the {{json-formatter}} itself. In fact dropping the {{org.jboss.logmanager.formatters.LogstashFormatter}} is being considered.
> Add JSON formatter resources to the logging subsystem
> -----------------------------------------------------
>
> Key: WFCORE-2951
> URL: https://issues.jboss.org/browse/WFCORE-2951
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Logging
> Reporter: James Perkins
> Assignee: James Perkins
> Fix For: 4.0.0.Beta1
>
>
> The logging subsystem should include resources for a {{json-formatter}} -and probably a {{logstash-formatter}}. The {{logstash-formatter}} is likely just an extension of the {{json-formatter}} with some predefined attributes that logstash requires-.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (WFCORE-2951) Add JSON formatter resources to the logging subsystem
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2951?page=com.atlassian.jira.plugi... ]
James Perkins updated WFCORE-2951:
----------------------------------
Description: The logging subsystem should include resources for a {{json-formatter}} -and probably a {{logstash-formatter}}. The {{logstash-formatter}} is likely just an extension of the {{json-formatter}} with some predefined attributes that logstash requires-. (was: The logging subsystem should include resources for a {{json-formatter}} and probably a {{logstash-formatter}}. The {{logstash-formatter}} is likely just an extension of the {{json-formatter}} with some predefined attributes that logstash requires.)
> Add JSON formatter resources to the logging subsystem
> -----------------------------------------------------
>
> Key: WFCORE-2951
> URL: https://issues.jboss.org/browse/WFCORE-2951
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Logging
> Reporter: James Perkins
> Assignee: James Perkins
> Fix For: 4.0.0.Beta1
>
>
> The logging subsystem should include resources for a {{json-formatter}} -and probably a {{logstash-formatter}}. The {{logstash-formatter}} is likely just an extension of the {{json-formatter}} with some predefined attributes that logstash requires-.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (WFCORE-2951) Add JSON formatter resources to the logging subsystem
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/WFCORE-2951?page=com.atlassian.jira.plugi... ]
James Perkins updated WFCORE-2951:
----------------------------------
Summary: Add JSON formatter resources to the logging subsystem (was: Add JSON and Logstash formatter resources to the logging subsystem)
> Add JSON formatter resources to the logging subsystem
> -----------------------------------------------------
>
> Key: WFCORE-2951
> URL: https://issues.jboss.org/browse/WFCORE-2951
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Logging
> Reporter: James Perkins
> Assignee: James Perkins
> Fix For: 4.0.0.Beta1
>
>
> The logging subsystem should include resources for a {{json-formatter}} and probably a {{logstash-formatter}}. The {{logstash-formatter}} is likely just an extension of the {{json-formatter}} with some predefined attributes that logstash requires.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (LOGMGR-115) Writing the configuration file should handle properties with null values
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/LOGMGR-115?page=com.atlassian.jira.plugin... ]
James Perkins reassigned LOGMGR-115:
------------------------------------
Assignee: James Perkins
> Writing the configuration file should handle properties with null values
> ------------------------------------------------------------------------
>
> Key: LOGMGR-115
> URL: https://issues.jboss.org/browse/LOGMGR-115
> Project: JBoss Log Manager
> Issue Type: Enhancement
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Minor
> Fix For: 2.1.0.Alpha5
>
>
> Currently in the configuration API if a property is set to {{null}} an NPE occurs during the write and is swallowed. The idea was the {{removeProperty()}} should be used in the API. We should though check for {{null}} values and either not write the value or leave the value blank and have the reader for the configuration assume a value of 0 length is {{null}}.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (WFLY-9402) EJB timer state should be able to use a NoSQL store to persist its data
by Wolf-Dieter Fink (JIRA)
Wolf-Dieter Fink created WFLY-9402:
--------------------------------------
Summary: EJB timer state should be able to use a NoSQL store to persist its data
Key: WFLY-9402
URL: https://issues.jboss.org/browse/WFLY-9402
Project: WildFly
Issue Type: Feature Request
Components: EJB
Reporter: Wolf-Dieter Fink
As an ejb-timer persistence there are current only
- file; local not shared and no clustering possible
- database; shareable possible to use cluster features
But sometimes a project does not need a relational database but there are NoSQL storages available.
Because of this it would be a benefit to add the ability for such Object databases like MongoDb, AWS dynamo and Infinispan.
It would be a plus if there is no need to have an extra RDBMS to persist timers
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (WFCORE-3321) The jboss.dist system property is not used in testsuite/elytron module
by Yeray Borges (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3321?page=com.atlassian.jira.plugi... ]
Yeray Borges edited comment on WFCORE-3321 at 9/29/17 11:01 AM:
----------------------------------------------------------------
[~jcacek] I don't know if QE uses the same technique for wildfly-core. I've checked jboss.dist is not being used for Elytron tests on wildfly-core, please, let me know if you want this issue fixed in wildfly-core too, if not, you can simply close this one.
was (Author: yersan):
[~jcacek] I don't know if QE uses the same technique for wildfly-core. I've checked jboss.dist is not using for Elytron tests on wildfly-core, please, let me know if you want this issue fixed in wildfly-core too, if not, you can simply close this one.
> The jboss.dist system property is not used in testsuite/elytron module
> ----------------------------------------------------------------------
>
> Key: WFCORE-3321
> URL: https://issues.jboss.org/browse/WFCORE-3321
> Project: WildFly Core
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 3.0.3.Final
> Reporter: Yeray Borges
> Assignee: Yeray Borges
> Priority: Critical
>
> Elytron testsuite module doesn't work correctly with the {{jboss.dist}} system property.
> The {{jboss.dist}} system property is used by QE to run the AS testsuite against the correct bits (e.g. comming from PROD team). The {{testsuite/integration/elytron}} module seems not to be taking this property into account. It seems it always uses output of {{wildfly-server-provisioning-maven-plugin}} to test against.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (WFCORE-3321) The jboss.dist system property is not used in testsuite/elytron module
by Yeray Borges (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3321?page=com.atlassian.jira.plugi... ]
Yeray Borges updated WFCORE-3321:
---------------------------------
Summary: The jboss.dist system property is not used in testsuite/elytron module (was: The jboss.dist system property is not used in testsuite/integration/elytron module)
> The jboss.dist system property is not used in testsuite/elytron module
> ----------------------------------------------------------------------
>
> Key: WFCORE-3321
> URL: https://issues.jboss.org/browse/WFCORE-3321
> Project: WildFly Core
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 3.0.3.Final
> Reporter: Yeray Borges
> Assignee: Yeray Borges
> Priority: Critical
>
> Elytron testsuite module doesn't work correctly with the {{jboss.dist}} system property.
> The {{jboss.dist}} system property is used by QE to run the AS testsuite against the correct bits (e.g. comming from PROD team). The {{testsuite/integration/elytron}} module seems not to be taking this property into account. It seems it always uses output of {{wildfly-server-provisioning-maven-plugin}} to test against.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months