[JBoss JIRA] (WFLY-8515) Deployments fails if AsyncListener in WEB-INF/classes or in a jar in WEB-INF/lib implements a class that isn't on the classpath
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-8515?page=com.atlassian.jira.plugin.... ]
Stuart Douglas reopened WFLY-8515:
----------------------------------
> Deployments fails if AsyncListener in WEB-INF/classes or in a jar in WEB-INF/lib implements a class that isn't on the classpath
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-8515
> URL: https://issues.jboss.org/browse/WFLY-8515
> Project: WildFly
> Issue Type: Bug
> Components: EE
> Affects Versions: 9.0.2.Final, 10.1.0.Final
> Reporter: Andy Wilkinson
> Assignee: Stuart Douglas
> Attachments: wildfly-problem.zip
>
>
> If a web application contains, anywhere in {{WEB-INF/classes}} or a jar in {{WEB-INF/lib}}, an {{AsyncListener}} that implements an interface that isn't on the classpath, deployment of the web application will fail. A concrete example is Spring Framework's {{spring-web}} module which contains [such a listener|https://github.com/spring-projects/spring-framework/blob/f716c8e...].
> When a war file is deployed to Wildfly 9.0.2.Final with {{spring-web}} in {{WEB-INF/lib}} deployment fails:
> {noformat}
> ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."bootapp.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."bootapp.war".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment "bootapp.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163)
> 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:745)
> Caused by: java.lang.LinkageError: Failed to link org/springframework/http/server/reactive/ServletHttpHandlerAdapter$HandlerResultSubscriber (Module "deployment.bootapp.war:main" from Service Module Loader)
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:437)
> at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:269)
> at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:77)
> at org.jboss.modules.Module.loadModuleClass(Module.java:560)
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:197)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at org.jboss.as.server.deployment.reflect.DeploymentClassIndex.classIndex(DeploymentClassIndex.java:54)
> at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.processComponentConfig(InterceptorAnnotationProcessor.java:85)
> at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.deploy(InterceptorAnnotationProcessor.java:77)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156)
> ... 5 more
> Caused by: java.lang.NoClassDefFoundError: org/reactivestreams/Subscriber
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:353)
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:432)
> ... 19 more
> Caused by: java.lang.ClassNotFoundException: org.reactivestreams.Subscriber from [Module "deployment.bootapp.war:main" from Service Module Loader]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130)
> ... 23 more
> {noformat}
> This listener is only ever actually registered when the {{Subscriber}} class is on the classpath so it seems unreasonable for it to cause a failure at deployment time.
> I'll attach a very basic example that triggers a similar problem. In the case of the example it fails with the following upon deployment to Wildfly 10.1.0.Final:
> {noformat}
> 15:52:51,752 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.unit."wildfly-problem.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."wildfly-problem.war".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment "wildfly-problem.war"
> 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:745)
> Caused by: java.lang.NoClassDefFoundError: Failed to link com/example/BrokenAsyncListener (Module "deployment.wildfly-problem.war:main" from Service Module Loader): org/reactivestreams/Subscriber
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:446)
> at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:274)
> at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:78)
> at org.jboss.modules.Module.loadModuleClass(Module.java:606)
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at org.jboss.as.ee.utils.ClassLoadingUtils.loadClass(ClassLoadingUtils.java:21)
> at org.jboss.as.ee.utils.ClassLoadingUtils.loadClass(ClassLoadingUtils.java:14)
> at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.processComponentConfig(InterceptorAnnotationProcessor.java:84)
> at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.deploy(InterceptorAnnotationProcessor.java:76)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
> ... 5 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (WFLY-8515) Deployments fails if AsyncListener in WEB-INF/classes or in a jar in WEB-INF/lib implements a class that isn't on the classpath
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-8515?page=com.atlassian.jira.plugin.... ]
Stuart Douglas updated WFLY-8515:
---------------------------------
Fix Version/s: (was: 11.0.0.Beta1)
> Deployments fails if AsyncListener in WEB-INF/classes or in a jar in WEB-INF/lib implements a class that isn't on the classpath
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-8515
> URL: https://issues.jboss.org/browse/WFLY-8515
> Project: WildFly
> Issue Type: Bug
> Components: EE
> Affects Versions: 9.0.2.Final, 10.1.0.Final
> Reporter: Andy Wilkinson
> Assignee: Stuart Douglas
> Attachments: wildfly-problem.zip
>
>
> If a web application contains, anywhere in {{WEB-INF/classes}} or a jar in {{WEB-INF/lib}}, an {{AsyncListener}} that implements an interface that isn't on the classpath, deployment of the web application will fail. A concrete example is Spring Framework's {{spring-web}} module which contains [such a listener|https://github.com/spring-projects/spring-framework/blob/f716c8e...].
> When a war file is deployed to Wildfly 9.0.2.Final with {{spring-web}} in {{WEB-INF/lib}} deployment fails:
> {noformat}
> ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.unit."bootapp.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."bootapp.war".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment "bootapp.war"
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163)
> 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:745)
> Caused by: java.lang.LinkageError: Failed to link org/springframework/http/server/reactive/ServletHttpHandlerAdapter$HandlerResultSubscriber (Module "deployment.bootapp.war:main" from Service Module Loader)
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:437)
> at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:269)
> at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:77)
> at org.jboss.modules.Module.loadModuleClass(Module.java:560)
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:197)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at org.jboss.as.server.deployment.reflect.DeploymentClassIndex.classIndex(DeploymentClassIndex.java:54)
> at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.processComponentConfig(InterceptorAnnotationProcessor.java:85)
> at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.deploy(InterceptorAnnotationProcessor.java:77)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156)
> ... 5 more
> Caused by: java.lang.NoClassDefFoundError: org/reactivestreams/Subscriber
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
> at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:353)
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:432)
> ... 19 more
> Caused by: java.lang.ClassNotFoundException: org.reactivestreams.Subscriber from [Module "deployment.bootapp.war:main" from Service Module Loader]
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:205)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:455)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:404)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:385)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:130)
> ... 23 more
> {noformat}
> This listener is only ever actually registered when the {{Subscriber}} class is on the classpath so it seems unreasonable for it to cause a failure at deployment time.
> I'll attach a very basic example that triggers a similar problem. In the case of the example it fails with the following upon deployment to Wildfly 10.1.0.Final:
> {noformat}
> 15:52:51,752 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-6) MSC000001: Failed to start service jboss.deployment.unit."wildfly-problem.war".POST_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."wildfly-problem.war".POST_MODULE: WFLYSRV0153: Failed to process phase POST_MODULE of deployment "wildfly-problem.war"
> 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:745)
> Caused by: java.lang.NoClassDefFoundError: Failed to link com/example/BrokenAsyncListener (Module "deployment.wildfly-problem.war:main" from Service Module Loader): org/reactivestreams/Subscriber
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:446)
> at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:274)
> at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:78)
> at org.jboss.modules.Module.loadModuleClass(Module.java:606)
> at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:363)
> at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:351)
> at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:93)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:348)
> at org.jboss.as.ee.utils.ClassLoadingUtils.loadClass(ClassLoadingUtils.java:21)
> at org.jboss.as.ee.utils.ClassLoadingUtils.loadClass(ClassLoadingUtils.java:14)
> at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.processComponentConfig(InterceptorAnnotationProcessor.java:84)
> at org.jboss.as.ee.component.deployers.InterceptorAnnotationProcessor.deploy(InterceptorAnnotationProcessor.java:76)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:147)
> ... 5 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (WFLY-7085) Server should verify EJB business methods during deployment and reject
by Tomasz Adamski (JIRA)
[ https://issues.jboss.org/browse/WFLY-7085?page=com.atlassian.jira.plugin.... ]
Tomasz Adamski reassigned WFLY-7085:
------------------------------------
Assignee: Tomasz Adamski
> Server should verify EJB business methods during deployment and reject
> ----------------------------------------------------------------------
>
> Key: WFLY-7085
> URL: https://issues.jboss.org/browse/WFLY-7085
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 11.0.0.Alpha1
> Reporter: Wolf-Dieter Fink
> Assignee: Tomasz Adamski
>
> The ejb 3.2 core specification state in chapter 4.9.6 that business methods should not be declared as final or static.
> But a Bean with a business method declared in the local or remote interface can be correct deployed and is accesible under some circumstances.
> To ensure that the Bean is according to the spec and avoid runtime or injection issues the methods should be checked and a VerifyError should be thrown at deployment time.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (WFLY-8875) Improve exception when injecting EJB Local Interface Proxy loaded from two different classloaders
by Tomasz Adamski (JIRA)
[ https://issues.jboss.org/browse/WFLY-8875?page=com.atlassian.jira.plugin.... ]
Tomasz Adamski reassigned WFLY-8875:
------------------------------------
Assignee: Tomasz Adamski
> Improve exception when injecting EJB Local Interface Proxy loaded from two different classloaders
> -------------------------------------------------------------------------------------------------
>
> Key: WFLY-8875
> URL: https://issues.jboss.org/browse/WFLY-8875
> Project: WildFly
> Issue Type: Enhancement
> Components: EE, EJB
> Affects Versions: 11.0.0.Alpha1
> Environment: Deploy test-case.ear to reproducer
> Reporter: Brad Maxwell
> Assignee: Tomasz Adamski
> Priority: Minor
> Attachments: test-case.ear
>
>
> If an EJB client tries to use @EJB to inject an EJB Local Proxy and the Local interface is in two different classloaders/modules/sub-deployments, it throws the error below. It would be helpful for the user to identify the issue if the exception indicated multiple classloaders or class HelloWorld is loaded from multiple modules or class cast exception.
> {code}
> Caused by: java.lang.IllegalArgumentException: Can not set example.api.HelloWorld field example.client.ClientSingleton.helloWorld to example.api.HelloWorld$$$view1
> at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:167)
> at sun.reflect.UnsafeFieldAccessorImpl.throwSetIllegalArgumentException(UnsafeFieldAccessorImpl.java:171)
> at sun.reflect.UnsafeObjectFieldAccessorImpl.set(UnsafeObjectFieldAccessorImpl.java:81)
> at java.lang.reflect.Field.set(Field.java:764)
> at org.jboss.as.ee.component.ManagedReferenceFieldInjectionInterceptorFactory$ManagedReferenceFieldInjectionInterceptor.processInvocation(ManagedReferenceFieldInjectionInterceptorFactory.java:106)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
> at org.jboss.as.ee.component.AroundConstructInterceptorFactory$1.processInvocation(AroundConstructInterceptorFactory.java:28)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
> at org.jboss.as.weld.injection.WeldInterceptorInjectionInterceptor.processInvocation(WeldInterceptorInjectionInterceptor.java:56)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
> at org.jboss.as.weld.interceptors.Jsr299BindingsCreateInterceptor.processInvocation(Jsr299BindingsCreateInterceptor.java:100)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
> at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)
> at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:240)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:275)
> ... 26 more
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (WFLY-9521) Optimize marshalling of org.wildfly.clustering.group.Node implementations
by Paul Ferraro (JIRA)
Paul Ferraro created WFLY-9521:
----------------------------------
Summary: Optimize marshalling of org.wildfly.clustering.group.Node implementations
Key: WFLY-9521
URL: https://issues.jboss.org/browse/WFLY-9521
Project: WildFly
Issue Type: Enhancement
Components: Clustering
Affects Versions: 11.0.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
The Node implementations currently serialize:
* org.jgroups.Address
* The logical name (typically a host name)
* The socket binding address/port of its transport
This is overkill. The Node should only need to serialize enough information to reconstruct itself using a NodeFactory<Address>, which should only include:
* its Address
* something to minimally identify the NodeFactory<Address>, with which to use to reconstruct the Node, e.g. a group name
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (ELY-302) Add SHA-512-256 to list of algorithms for digest passwords and SASL digest
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-302?page=com.atlassian.jira.plugin.sy... ]
Jan Kalina edited comment on ELY-302 at 11/4/17 5:27 AM:
---------------------------------------------------------
SHA-512-256 cannot be implemented using SHA-512 - truncation is not sufficient - the initialization vector needs to be different too, which MessageDigest API does not allow - only by extending JDK-specific class it would be possible...
I see two possibilities:
* to rely on MessageDigest SHA-512-256 provided by bouncycastle of other library (when not present any SHA-512-256 provider, it would be unsupported)
* to add custom implementation of SHA-512-256 as part of elytron - will try...
was (Author: honza889):
SHA-512-256 cannot be implemented using SHA-512 - the initialization vector would have to be different, which MessageDigest API does not allow - sun-specific SHA5 class would have to be extended.
There are two possibilities:
* to rely on MessageDigest SHA-512-256 provided by bouncycastle of other library (when not present any SHA-512-256 provider, it would be unsupported)
* to add custom implementation of SHA-512-256 as part of elytron - will try...
> Add SHA-512-256 to list of algorithms for digest passwords and SASL digest
> --------------------------------------------------------------------------
>
> Key: ELY-302
> URL: https://issues.jboss.org/browse/ELY-302
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: Passwords, SASL
> Reporter: David Lloyd
> Assignee: Jan Kalina
>
> [RFC 7616|http://www.rfc-editor.org/rfc/rfc7616.txt] was released, indicating that SHA-512-256 is a supported algorithm for digest HTTP mechanisms. We need support for that algorithm as a password. We also then should add a corresponding SASL variant to the DIGEST suite.
> There is no MessageDigest for SHA-512-256. This can be accomplished by truncating the output of SHA-512 to 256 bits (32 bytes). A wrapper MessageDigest could be created, or the ability to arbitrarily truncate the digest could be added to the DIGEST mechanism.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (ELY-302) Add SHA-512-256 to list of algorithms for digest passwords and SASL digest
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-302?page=com.atlassian.jira.plugin.sy... ]
Jan Kalina commented on ELY-302:
--------------------------------
SHA-512-256 cannot be implemented using SHA-512 - the initialization vector would have to be different, which MessageDigest API does not allow - sun-specific SHA5 class would have to be extended.
There are two possibilities:
* to rely on MessageDigest SHA-512-256 provided by bouncycastle of other library (when not present any SHA-512-256 provider, it would be unsupported)
* to add custom implementation of SHA-512-256 as part of elytron - will try...
> Add SHA-512-256 to list of algorithms for digest passwords and SASL digest
> --------------------------------------------------------------------------
>
> Key: ELY-302
> URL: https://issues.jboss.org/browse/ELY-302
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: Passwords, SASL
> Reporter: David Lloyd
> Assignee: Jan Kalina
>
> [RFC 7616|http://www.rfc-editor.org/rfc/rfc7616.txt] was released, indicating that SHA-512-256 is a supported algorithm for digest HTTP mechanisms. We need support for that algorithm as a password. We also then should add a corresponding SASL variant to the DIGEST suite.
> There is no MessageDigest for SHA-512-256. This can be accomplished by truncating the output of SHA-512 to 256 bits (32 bytes). A wrapper MessageDigest could be created, or the ability to arbitrarily truncate the digest could be added to the DIGEST mechanism.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (WFLY-9519) default values in org.infinispan.configuration.cache.ExpirationConfiguration
by R O (JIRA)
[ https://issues.jboss.org/browse/WFLY-9519?page=com.atlassian.jira.plugin.... ]
R O commented on WFLY-9519:
---------------------------
{quote}You can either inject the desired cache directly:{quote}
Thank you, it works like a charm.
{quote}... or, alternatively, add a dependency on the cache configuration:{quote}
Too tricky for me, I have found better solution:
{code:java}
EmbeddedCacheManager manager = cache.getCacheManager();
{code}
Injecting EmbeddedCacheManager directly via @Resource should be banned, don't you think?
> default values in org.infinispan.configuration.cache.ExpirationConfiguration
> ----------------------------------------------------------------------------
>
> Key: WFLY-9519
> URL: https://issues.jboss.org/browse/WFLY-9519
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 11.0.0.Beta1, 11.0.0.CR1, 11.0.0.Final
> Reporter: R O
> Assignee: Paul Ferraro
> Attachments: wildfly-infinispan-showcase.tar.gz
>
>
> I had noticed regression issue in WildFly's Infinispan submodule. Object of class {{org.infinispan.configuration.cache.ExpirationConfiguration}} always contains default values.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (WFLY-9520) Ability to inject ModelControllerClient
by Brad Maxwell (JIRA)
Brad Maxwell created WFLY-9520:
----------------------------------
Summary: Ability to inject ModelControllerClient
Key: WFLY-9520
URL: https://issues.jboss.org/browse/WFLY-9520
Project: WildFly
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 11.0.0.Final
Reporter: Brad Maxwell
Assignee: Brian Stansberry
Being able to inject the ModelControllerClient via @Inject / @Resource / JNDI lookup would be useful for applications wanting to access the management interface without needing to setup a remote call via the java api and needing to know the host/port/user/pass.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months
[JBoss JIRA] (WFLY-9519) default values in org.infinispan.configuration.cache.ExpirationConfiguration
by Paul Ferraro (JIRA)
[ https://issues.jboss.org/browse/WFLY-9519?page=com.atlassian.jira.plugin.... ]
Paul Ferraro closed WFLY-9519.
------------------------------
Resolution: Rejected
The issue here is that your code injects the cache container, but does nothing to ensure that the requested cache configuration is installed. While this code may have worked in 11.0.0.Alpha1, it was not to be relied upon (and would have been vulnerable to a race condition between your deployment and the passively installed cache configuration).
You can either inject the desired cache directly:
{code:java}@Resource(lookup="java:jboss/infinispan/cache/custom-cache-container/custom-cache")
Cache<?, ?> cache;{code}
... or, alternatively, add a dependency on the cache configuration:
{code:java}@Resource(lookup="java:jboss/infinispan/container/custom-cache-container")
EmbeddedCacheManager manager;
@Resource(lookup="java:jboss/infinispan/configuration/custom-cache-container/custom-cache")
Configuration config;{code}
With the requisite dependency in place, you can safely call manager.getCache("custom-cache") or manager.getCacheConfiguration("custom-cache").
> default values in org.infinispan.configuration.cache.ExpirationConfiguration
> ----------------------------------------------------------------------------
>
> Key: WFLY-9519
> URL: https://issues.jboss.org/browse/WFLY-9519
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 11.0.0.Beta1, 11.0.0.CR1, 11.0.0.Final
> Reporter: R O
> Assignee: Paul Ferraro
> Attachments: wildfly-infinispan-showcase.tar.gz
>
>
> I had noticed regression issue in WildFly's Infinispan submodule. Object of class {{org.infinispan.configuration.cache.ExpirationConfiguration}} always contains default values.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 8 months