[JBoss JIRA] (WFLY-9954) Too many services and dependencies created for EJBs
by Tomasz Adamski (Jira)
[ https://issues.jboss.org/browse/WFLY-9954?page=com.atlassian.jira.plugin.... ]
Tomasz Adamski reassigned WFLY-9954:
------------------------------------
Assignee: Richard Opalka (was: Romain Pelisse)
> Too many services and dependencies created for EJBs
> ---------------------------------------------------
>
> Key: WFLY-9954
> URL: https://issues.jboss.org/browse/WFLY-9954
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: David Lloyd
> Assignee: Richard Opalka
> Priority: Critical
>
> If a deployment contains more than 2730 EJBs, the deployment's INSTALL phase will get a stack trace like this:
> {noformat}
> 2018-03-25 08:22:34,115 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC000001: Failed to start service jboss.deployment.unit."example.jar".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."example.jar".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "example.jar"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:154)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.IllegalArgumentException: Too many dependencies specified (max is 16383) .......... (*1)
> at org.jboss.msc.service.ServiceBuilderImpl.doAddDependency(ServiceBuilderImpl.java:216)
> at org.jboss.msc.service.ServiceBuilderImpl.addDependenciesNoCheck(ServiceBuilderImpl.java:158)
> at org.jboss.msc.service.ServiceBuilderImpl.addDependencies(ServiceBuilderImpl.java:152)
> at org.jboss.msc.service.ServiceBuilderImpl.addDependencies(ServiceBuilderImpl.java:142)
> at org.jboss.as.naming.deployment.JndiNamingDependencyProcessor.deploy(JndiNamingDependencyProcessor.java:59)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
> ... 5 more
> {noformat}
> The reason is that the INSTALL phase has six additional dependencies per EJB:
> * service jboss.naming.context.java.comp.example.example.<class-name>.InAppClientContainer
> * service jboss.naming.context.java.comp.example.example.<class-name>.InstanceName
> * service jboss.deployment.unit."example.jar".component.<class-name>.JndiBindingsService
> * service jboss.naming.context.java.comp.example.example.<class-name>.UserTransaction
> * service jboss.naming.context.java.comp.example.example.<class-name>.TransactionSynchronizationRegistry
> * service jboss.naming.context.java.comp.example.example.<class-name>.BeanManager
> We probably should not be creating N dependencies per deployment object since all the services of a given kind are always started together. They could be grouped at a deployment level instead.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (WFLY-4621) RESTEasy SMIME doesn't work with WildFly current module setup
by Ron Sigal (Jira)
[ https://issues.jboss.org/browse/WFLY-4621?page=com.atlassian.jira.plugin.... ]
Ron Sigal resolved WFLY-4621.
-----------------------------
Resolution: Done
> RESTEasy SMIME doesn't work with WildFly current module setup
> -------------------------------------------------------------
>
> Key: WFLY-4621
> URL: https://issues.jboss.org/browse/WFLY-4621
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 9.0.0.CR1
> Reporter: Weinan Li
> Assignee: Weinan Li
> Priority: Major
> Fix For: 10.0.0.Final
>
> Attachments: patch_WFLY-4621_all, patch_WFLY-4621_new
>
>
> RESTEasy provides the functions of SMIME encryption and here is an example that can be deployed into WildFly:
> https://github.com/liweinan/digital-signatures/tree/master/smime
> And currently resteasy-crypto module doesn't work properly in WildFly unless applied the following patch:
> {code:diff}
> power:modules weinanli$ git diff
> warning: LF will be replaced by CRLF in system/layers/base/org/bouncycastle/main/module.xml.
> The file will have its original line endings in your working directory.
> diff --git a/system/layers/base/org/bouncycastle/main/module.xml b/system/layers/base/org/bouncycastle/main/module.xml
> index 5d13395..83ae97c 100644
> --- a/system/layers/base/org/bouncycastle/main/module.xml
> +++ b/system/layers/base/org/bouncycastle/main/module.xml
> @@ -24,12 +24,17 @@
> <module xmlns="urn:jboss:module:1.3" name="org.bouncycastle">
> <resources>
> + <!--
> <resource-root path="bcprov-jdk15on-1.52.jar"/>
> <resource-root path="bcmail-jdk15on-1.52.jar"/>
> + -->
> + <resource-root path="bcprov-jdk16-1.46.jar"/>
> + <resource-root path="bcmail-jdk16-1.46.jar"/>
> <resource-root path="bcpkix-jdk15on-1.52.jar"/>
> </resources>
> <dependencies>
> <module name="javax.api"/>
> + <module name="javax.mail.api"/>
> + <module name="javax.activation.api"/>
> </dependencies>
> -
> </module>
> {code}
> After applying the above patch then the example can pass all the tests:
> {code}
> power:smime weinanli$ mvn -q clean package
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
> power:smime weinanli$ mvn -q wildfly:deploy
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
> May 11, 2015 9:24:27 PM org.xnio.Xnio <clinit>
> INFO: XNIO version 3.3.0.Final
> May 11, 2015 9:24:27 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.3.0.Final
> May 11, 2015 9:24:27 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 4.0.7.Final
> power:smime weinanli$ mvn -q integration-test
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.resteasy.tests.smime.SMIMETest
> Encrypted Message From Server:
> Customer{name='Bill'}
> Signed Message From Server:
> Customer{name='Bill'}
> Customer{name='Bill'}
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.682 sec - in org.jboss.resteasy.tests.smime.SMIMETest
> Results :
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0
> power:smime weinanli$
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (WFLY-4621) RESTEasy SMIME doesn't work with WildFly current module setup
by Ron Sigal (Jira)
[ https://issues.jboss.org/browse/WFLY-4621?page=com.atlassian.jira.plugin.... ]
Ron Sigal commented on WFLY-4621:
---------------------------------
Ok, thanks, [~mkopecky].
> RESTEasy SMIME doesn't work with WildFly current module setup
> -------------------------------------------------------------
>
> Key: WFLY-4621
> URL: https://issues.jboss.org/browse/WFLY-4621
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 9.0.0.CR1
> Reporter: Weinan Li
> Assignee: Weinan Li
> Priority: Major
> Fix For: 10.0.0.Final
>
> Attachments: patch_WFLY-4621_all, patch_WFLY-4621_new
>
>
> RESTEasy provides the functions of SMIME encryption and here is an example that can be deployed into WildFly:
> https://github.com/liweinan/digital-signatures/tree/master/smime
> And currently resteasy-crypto module doesn't work properly in WildFly unless applied the following patch:
> {code:diff}
> power:modules weinanli$ git diff
> warning: LF will be replaced by CRLF in system/layers/base/org/bouncycastle/main/module.xml.
> The file will have its original line endings in your working directory.
> diff --git a/system/layers/base/org/bouncycastle/main/module.xml b/system/layers/base/org/bouncycastle/main/module.xml
> index 5d13395..83ae97c 100644
> --- a/system/layers/base/org/bouncycastle/main/module.xml
> +++ b/system/layers/base/org/bouncycastle/main/module.xml
> @@ -24,12 +24,17 @@
> <module xmlns="urn:jboss:module:1.3" name="org.bouncycastle">
> <resources>
> + <!--
> <resource-root path="bcprov-jdk15on-1.52.jar"/>
> <resource-root path="bcmail-jdk15on-1.52.jar"/>
> + -->
> + <resource-root path="bcprov-jdk16-1.46.jar"/>
> + <resource-root path="bcmail-jdk16-1.46.jar"/>
> <resource-root path="bcpkix-jdk15on-1.52.jar"/>
> </resources>
> <dependencies>
> <module name="javax.api"/>
> + <module name="javax.mail.api"/>
> + <module name="javax.activation.api"/>
> </dependencies>
> -
> </module>
> {code}
> After applying the above patch then the example can pass all the tests:
> {code}
> power:smime weinanli$ mvn -q clean package
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
> power:smime weinanli$ mvn -q wildfly:deploy
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
> May 11, 2015 9:24:27 PM org.xnio.Xnio <clinit>
> INFO: XNIO version 3.3.0.Final
> May 11, 2015 9:24:27 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.3.0.Final
> May 11, 2015 9:24:27 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 4.0.7.Final
> power:smime weinanli$ mvn -q integration-test
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.resteasy.tests.smime.SMIMETest
> Encrypted Message From Server:
> Customer{name='Bill'}
> Signed Message From Server:
> Customer{name='Bill'}
> Customer{name='Bill'}
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.682 sec - in org.jboss.resteasy.tests.smime.SMIMETest
> Results :
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0
> power:smime weinanli$
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (WFLY-4621) RESTEasy SMIME doesn't work with WildFly current module setup
by Ron Sigal (Jira)
[ https://issues.jboss.org/browse/WFLY-4621?page=com.atlassian.jira.plugin.... ]
Ron Sigal updated WFLY-4621:
----------------------------
Fix Version/s: 10.0.0.Final
> RESTEasy SMIME doesn't work with WildFly current module setup
> -------------------------------------------------------------
>
> Key: WFLY-4621
> URL: https://issues.jboss.org/browse/WFLY-4621
> Project: WildFly
> Issue Type: Bug
> Components: REST
> Affects Versions: 9.0.0.CR1
> Reporter: Weinan Li
> Assignee: Weinan Li
> Priority: Major
> Fix For: 10.0.0.Final
>
> Attachments: patch_WFLY-4621_all, patch_WFLY-4621_new
>
>
> RESTEasy provides the functions of SMIME encryption and here is an example that can be deployed into WildFly:
> https://github.com/liweinan/digital-signatures/tree/master/smime
> And currently resteasy-crypto module doesn't work properly in WildFly unless applied the following patch:
> {code:diff}
> power:modules weinanli$ git diff
> warning: LF will be replaced by CRLF in system/layers/base/org/bouncycastle/main/module.xml.
> The file will have its original line endings in your working directory.
> diff --git a/system/layers/base/org/bouncycastle/main/module.xml b/system/layers/base/org/bouncycastle/main/module.xml
> index 5d13395..83ae97c 100644
> --- a/system/layers/base/org/bouncycastle/main/module.xml
> +++ b/system/layers/base/org/bouncycastle/main/module.xml
> @@ -24,12 +24,17 @@
> <module xmlns="urn:jboss:module:1.3" name="org.bouncycastle">
> <resources>
> + <!--
> <resource-root path="bcprov-jdk15on-1.52.jar"/>
> <resource-root path="bcmail-jdk15on-1.52.jar"/>
> + -->
> + <resource-root path="bcprov-jdk16-1.46.jar"/>
> + <resource-root path="bcmail-jdk16-1.46.jar"/>
> <resource-root path="bcpkix-jdk15on-1.52.jar"/>
> </resources>
> <dependencies>
> <module name="javax.api"/>
> + <module name="javax.mail.api"/>
> + <module name="javax.activation.api"/>
> </dependencies>
> -
> </module>
> {code}
> After applying the above patch then the example can pass all the tests:
> {code}
> power:smime weinanli$ mvn -q clean package
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
> power:smime weinanli$ mvn -q wildfly:deploy
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
> May 11, 2015 9:24:27 PM org.xnio.Xnio <clinit>
> INFO: XNIO version 3.3.0.Final
> May 11, 2015 9:24:27 PM org.xnio.nio.NioXnio <clinit>
> INFO: XNIO NIO Implementation Version 3.3.0.Final
> May 11, 2015 9:24:27 PM org.jboss.remoting3.EndpointImpl <clinit>
> INFO: JBoss Remoting version 4.0.7.Final
> power:smime weinanli$ mvn -q integration-test
> Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
> -------------------------------------------------------
> T E S T S
> -------------------------------------------------------
> Running org.jboss.resteasy.tests.smime.SMIMETest
> Encrypted Message From Server:
> Customer{name='Bill'}
> Signed Message From Server:
> Customer{name='Bill'}
> Customer{name='Bill'}
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.682 sec - in org.jboss.resteasy.tests.smime.SMIMETest
> Results :
> Tests run: 6, Failures: 0, Errors: 0, Skipped: 0
> power:smime weinanli$
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (WFCORE-4364) Allow management audit logging to write JSON log messages to stdout
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFCORE-4364?page=com.atlassian.jira.plugi... ]
James Perkins commented on WFCORE-4364:
---------------------------------------
Looking more at the data it's going to have to be fully restructured. The date looks like an object. It's probably going to have to look more like:
{code}
{
"timestamp" : "2019-03-08 13:29:49"
"type" : "core",
"r/o" : false,
"booting" : false,
"version" : "8.0.1.CR1-SNAPSHOT",
"user" : "$local",
"domainUUID" : null,
"access" : "NATIVE",
"remote-address" : "localhost/127.0.0.1",
"success" : true,
"opAddress" : "/subsystem=logging/json-formatter=json",
"op" : "remove",
"caller-type" : "user",
"access-mechanism" : "NATIVE"
}
{code}
Note we need to determine what values can end up in the {{operation-headers}} object.
> Allow management audit logging to write JSON log messages to stdout
> -------------------------------------------------------------------
>
> Key: WFCORE-4364
> URL: https://issues.jboss.org/browse/WFCORE-4364
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Logging, Management
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Major
>
> Management audit logging can already log messages in JSON format. However these can only be written to a file or a syslog server. We need the ability for these messages to be written to {{stdout}}. This is useful for containers like OpenShift which consume the {{stdout}} data to feed to log aggregators.
> Example Output:
> {code}
> 2019-03-08 13:29:49 - {
> "type" : "core",
> "r/o" : false,
> "booting" : false,
> "version" : "8.0.1.CR1-SNAPSHOT",
> "user" : "$local",
> "domainUUID" : null,
> "access" : "NATIVE",
> "remote-address" : "localhost/127.0.0.1",
> "success" : true,
> "ops" : [{
> "address" : [
> {
> "subsystem" : "logging"
> },
> {
> "json-formatter" : "json"
> }
> ],
> "operation" : "remove",
> "operation-headers" : {
> "caller-type" : "user",
> "access-mechanism" : "NATIVE"
> }
> }]
> }
> {code}
> Note for a log aggregator the complex {{ops}} attribute can be an issue. We may need to find a better way to log that. If possibly maybe convert it into a CLI command.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (WFCORE-4364) Allow management audit logging to write JSON log messages to stdout
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFCORE-4364?page=com.atlassian.jira.plugi... ]
James Perkins updated WFCORE-4364:
----------------------------------
Description:
Management audit logging can already log messages in JSON format. However these can only be written to a file or a syslog server. We need the ability for these messages to be written to {{stdout}}. This is useful for containers like OpenShift which consume the {{stdout}} data to feed to log aggregators.
Example Output:
{code}
2019-03-08 13:29:49 - {
"type" : "core",
"r/o" : false,
"booting" : false,
"version" : "8.0.1.CR1-SNAPSHOT",
"user" : "$local",
"domainUUID" : null,
"access" : "NATIVE",
"remote-address" : "localhost/127.0.0.1",
"success" : true,
"ops" : [{
"address" : [
{
"subsystem" : "logging"
},
{
"json-formatter" : "json"
}
],
"operation" : "remove",
"operation-headers" : {
"caller-type" : "user",
"access-mechanism" : "NATIVE"
}
}]
}
{code}
Note for a log aggregator the complex {{ops}} attribute can be an issue. We may need to find a better way to log that. If possibly maybe convert it into a CLI command.
was:Management audit logging can already log messages in JSON format. However these can only be written to a file or a syslog server. We need the ability for these messages to be written to {{stdout}}. This is useful for containers like OpenShift which consume the {{stdout}} data to feed to log aggregators.
> Allow management audit logging to write JSON log messages to stdout
> -------------------------------------------------------------------
>
> Key: WFCORE-4364
> URL: https://issues.jboss.org/browse/WFCORE-4364
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Logging, Management
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Major
>
> Management audit logging can already log messages in JSON format. However these can only be written to a file or a syslog server. We need the ability for these messages to be written to {{stdout}}. This is useful for containers like OpenShift which consume the {{stdout}} data to feed to log aggregators.
> Example Output:
> {code}
> 2019-03-08 13:29:49 - {
> "type" : "core",
> "r/o" : false,
> "booting" : false,
> "version" : "8.0.1.CR1-SNAPSHOT",
> "user" : "$local",
> "domainUUID" : null,
> "access" : "NATIVE",
> "remote-address" : "localhost/127.0.0.1",
> "success" : true,
> "ops" : [{
> "address" : [
> {
> "subsystem" : "logging"
> },
> {
> "json-formatter" : "json"
> }
> ],
> "operation" : "remove",
> "operation-headers" : {
> "caller-type" : "user",
> "access-mechanism" : "NATIVE"
> }
> }]
> }
> {code}
> Note for a log aggregator the complex {{ops}} attribute can be an issue. We may need to find a better way to log that. If possibly maybe convert it into a CLI command.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months