[JBoss JIRA] (JGRP-2227) Use of AUTH does not result in a SecurityException, but instead nodes create separate clusters with the same name
by Bela Ban (JIRA)
[ https://issues.jboss.org/browse/JGRP-2227?page=com.atlassian.jira.plugin.... ]
Bela Ban updated JGRP-2227:
---------------------------
Fix Version/s: 4.0.11
(was: 4.0.8)
> Use of AUTH does not result in a SecurityException, but instead nodes create separate clusters with the same name
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JGRP-2227
> URL: https://issues.jboss.org/browse/JGRP-2227
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 4.0.6
> Reporter: Robert Cernak
> Assignee: Bela Ban
> Fix For: 4.0.11
>
> Attachments: jgroupsLogs.zip
>
>
> I implemented method org.jgroups.auth.AuthToken#authenticate(AuthToken token, Message msg) in my class and its body contained only one line: return false;
> In this way authentication should be false and I should get SecurityException.
> When I started joining of nodes together to form a cluster, instead of getting SecurityException, nodes formed 2 different clusters with the same name.
> I am sure method was evaluated, since I tried to run it also with breakpoint, which was triggered during joining process.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-9778) Test suite is putting temporary modules in build directory
by Chao Wang (JIRA)
[ https://issues.jboss.org/browse/WFLY-9778?page=com.atlassian.jira.plugin.... ]
Chao Wang reassigned WFLY-9778:
-------------------------------
Assignee: Chao Wang
> Test suite is putting temporary modules in build directory
> ----------------------------------------------------------
>
> Key: WFLY-9778
> URL: https://issues.jboss.org/browse/WFLY-9778
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: David Lloyd
> Assignee: Chao Wang
> Priority: Critical
>
> Something (I think the test suite) is generating non-distribution-related modules into the {{build}} directory of the server, for example {{build/target/wildfly-12.0.0.Alpha1-SNAPSHOT/modules/connlistener}}. We should not be doing this; these kinds of special modules should be generated elsewhere and overlaid on the test suite images that need them.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-10016) HTTP + EJB - UnsupportedOperationException trying to write to an AbstractMap
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-10016?page=com.atlassian.jira.plugin... ]
Stuart Douglas commented on WFLY-10016:
---------------------------------------
I have made this map a mutable map upstream, so it should be fixed once I cut a new release.
> HTTP + EJB - UnsupportedOperationException trying to write to an AbstractMap
> ----------------------------------------------------------------------------
>
> Key: WFLY-10016
> URL: https://issues.jboss.org/browse/WFLY-10016
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: Brian Stansberry
> Assignee: Stuart Douglas
>
> [~tremes] Has hit this failure when running some tests against our OpenShift images using WF code from, I believe, 12 CR1.
> {code}
> 13:03:50,832 ERROR [org.jboss.as.ejb3.remote] (default task-1) WFLYEJB0150: Could not write method invocation failure for method public abstract void com.redhat.xpaas.ejb.server.RemoteCounter.increment() on bean named CounterBean for appname modulename ROOT distinctname due to: java.lang.UnsupportedOperationException
> at java.util.AbstractMap.put(AbstractMap.java:209)
> at org.jboss.as.ejb3.remote.AssociationImpl.updateAffinities(AssociationImpl.java:267)
> at org.jboss.as.ejb3.remote.AssociationImpl.lambda$receiveInvocationRequest$0(AssociationImpl.java:233)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> {code}
> He or [~luck3y] can give you more details re the specific test.
> Just walking through code, my guess is the Collections.emptyMap() produced at [1] is getting passed through the stack to the failing code. (I'm filing this because I did this bit of brilliant analysis. ;) )
> [1] https://github.com/wildfly/wildfly-http-client/blob/master/ejb/src/main/j...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-10027) Provide metric attribute to see max number of concurrently active sessions for deployment
by Stuart Douglas (JIRA)
[ https://issues.jboss.org/browse/WFLY-10027?page=com.atlassian.jira.plugin... ]
Stuart Douglas moved JBEAP-14396 to WFLY-10027:
-----------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-10027 (was: JBEAP-14396)
Issue Type: Feature Request (was: Enhancement)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Web (Undertow)
(was: Web (Undertow))
Affects Version/s: (was: 7.1.0.DR8)
> Provide metric attribute to see max number of concurrently active sessions for deployment
> -----------------------------------------------------------------------------------------
>
> Key: WFLY-10027
> URL: https://issues.jboss.org/browse/WFLY-10027
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Reporter: Stuart Douglas
> Assignee: Stuart Douglas
> Priority: Minor
>
> Add metric attribute that shows maximum number of concurrently active sessions for particular deployment. Currently we have only:
> {code}
> /deployment=helloworld.war/subsystem=undertow:read-attribute(name=max-active-sessions)
> {code}
> which is just:
> {code}
> "max-active-sessions" => {
> "type" => INT,
> "description" => "The maximum allowed number of concurrent sessions that this session manager supports",
> "expressions-allowed" => false,
> "nillable" => false,
> "access-type" => "metric",
> "storage" => "runtime"
> },
> {code}
> Providing also metric to see what was the maximum number of concurrently active sessions for particular deployment might be useful for user too.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-9971) wsprovide && wsconsume scritps don't work on Windows
by Jan Blizňák (JIRA)
[ https://issues.jboss.org/browse/WFLY-9971?page=com.atlassian.jira.plugin.... ]
Jan Blizňák reassigned WFLY-9971:
---------------------------------
Assignee: Jan Blizňák (was: R Searls)
> wsprovide && wsconsume scritps don't work on Windows
> ----------------------------------------------------
>
> Key: WFLY-9971
> URL: https://issues.jboss.org/browse/WFLY-9971
> Project: WildFly
> Issue Type: Bug
> Components: Scripts, Web Services
> Affects Versions: 12.0.0.Final
> Reporter: Marek Kopecký
> Assignee: Jan Blizňák
> Priority: Blocker
>
> *Description of the issue:*
> Wsprovide and wsconsume scripts don't work on Windows. Scripts print jboss-modules help message with any attributes.
> *How reproducible:*
> Always
> *Steps to Reproduce:*
> # wsprovide.bat -h
> # wsconsume.bat -h
> *Actual results:*
> {noformat}
> C:\Users\Administrator\playground\wfly.12\wildfly\bin>wsprovide.bat -h
> Argument expected for option
> Usage: java [-jvmoptions...] -jar jboss-modules.jar [-options...] <module-spec> [args...]
> java [-jvmoptions...] -jar jboss-modules.jar [-options...] -jar <jar-name> [args...]
> java [-jvmoptions...] -jar jboss-modules.jar [-options...] -cp <class-path> <class-name> [args...]
> java [-jvmoptions...] -jar jboss-modules.jar [-options...] -class <class-name> [args...]
> java [-jvmoptions...] -jar jboss-modules.jar -addindex [-modify] <jar-name>
> where <module-spec> is a valid module specification string
> and options include:
> -help Display this message
> -mp, -modulepath <search path of directories>
> A list of directories, separated by ';', where modules may be located
> If not specified, the value of the "module.path" system property is used
> -class Specify that the final argument is a
> class to load from the class path; not compatible with -jar
> -cp,-classpath <search path of archives or directories>
> A search path for class files; implies -class
> -dep,-dependencies <module-spec>[,<module-spec>,...]
> A list of module dependencies to add to the class path;
> requires -class or -cp
> -deptree Print the dependency tree of the given module instead of running it
> -debuglog Enable debug mode output to System.out during bootstrap before any logging manager is installed
> -jar Specify that the final argument is the name of a
> JAR file to run as a module; not compatible with -class
> -jaxpmodule <module-spec>
> The default JAXP implementation to use of the JDK
> -secmgr Run with a security manager installed; not compatible with -secmgrmodule
> -secmgrmodule <module-spec>
> Run with a security manager module; not compatible with -secmgr
> -addindex Specify that the final argument is a
> jar to create an index for
> -modify Modify the indexes jar in-place
> -version Print version and exit
> C:\Users\Administrator\playground\wfly.12\wildfly\bin>wsconsume.bat -h
> Argument expected for option
> Usage: java [-jvmoptions...] -jar jboss-modules.jar [-options...] <module-spec> [args...]
> java [-jvmoptions...] -jar jboss-modules.jar [-options...] -jar <jar-name> [args...]
> java [-jvmoptions...] -jar jboss-modules.jar [-options...] -cp <class-path> <class-name> [args...]
> java [-jvmoptions...] -jar jboss-modules.jar [-options...] -class <class-name> [args...]
> java [-jvmoptions...] -jar jboss-modules.jar -addindex [-modify] <jar-name>
> where <module-spec> is a valid module specification string
> and options include:
> -help Display this message
> -mp, -modulepath <search path of directories>
> A list of directories, separated by ';', where modules may be located
> If not specified, the value of the "module.path" system property is used
> -class Specify that the final argument is a
> class to load from the class path; not compatible with -jar
> -cp,-classpath <search path of archives or directories>
> A search path for class files; implies -class
> -dep,-dependencies <module-spec>[,<module-spec>,...]
> A list of module dependencies to add to the class path;
> requires -class or -cp
> -deptree Print the dependency tree of the given module instead of running it
> -debuglog Enable debug mode output to System.out during bootstrap before any logging manager is installed
> -jar Specify that the final argument is the name of a
> JAR file to run as a module; not compatible with -class
> -jaxpmodule <module-spec>
> The default JAXP implementation to use of the JDK
> -secmgr Run with a security manager installed; not compatible with -secmgrmodule
> -secmgrmodule <module-spec>
> Run with a security manager module; not compatible with -secmgr
> -addindex Specify that the final argument is a
> jar to create an index for
> -modify Modify the indexes jar in-place
> -version Print version and exit
> C:\Users\Administrator\playground\wfly.12\wildfly\bin>
> {noformat}
> *Expected results:*
> {noformat}
> C:\Users\Administrator\playground\7.1.0.CR4\jboss-eap-7.1\bin>wsprovide.bat -h
> WSProvideTask generates portable JAX-WS artifacts for an endpoint implementation.
> usage: wsprovide.bat [options] <endpoint class name>
> options:
> -h, --help Show this help message
> -k, --keep Keep/Generate Java source
> -w, --wsdl Enable WSDL file generation
> -a, --address=<address> The generated port soap:address in wsdl
> -c, --classpath=<path> The classpath that contains the endpoint
> -o, --output=<directory> The directory to put generated artifacts
> -r, --resource=<directory> The directory to put resource artifacts
> -s, --source=<directory> The directory to put Java source
> -e, --extension Enable SOAP 1.2 binding extension
> -q, --quiet Be somewhat more quiet
> -t, --show-traces Show full exception stack traces
> -v, --verbose Show full exception stack traces
> -l, --load-provider Load the provider and exit (debug utility)
> C:\Users\Administrator\playground\7.1.0.CR4\jboss-eap-7.1\bin>wsconsume.bat -h
> WSConsumeTask is a cmd line tool that generates portable JAX-WS artifacts from a WSDL file.
> usage: wsconsume.bat [options] <wsdl-url>
> options:
> -h, --help Show this help message
> -b, --binding=<file> One or more JAX-WS or JAXB binding files
> -k, --keep Keep/Generate Java source
> -c --catalog=<file> Oasis XML Catalog file for entity resolution
> -j --clientjar=<name> Create a jar file of the generated artifacts for calling the webservice
> -p --package=<name> The target package for generated source
> -w --wsdlLocation=<loc> Value to use for @WebService.wsdlLocation
> -o, --output=<directory> The directory to put generated artifacts
> -s, --source=<directory> The directory to put Java source
> -t, --target=<2.1|2.2> The JAX-WS specification target
> -q, --quiet Be somewhat more quiet
> -v, --verbose Show full exception stack traces
> -l, --load-consumer Load the consumer and exit (debug utility)
> -e, --extension Enable SOAP 1.2 binding extension
> -a, --additionalHeaders Enable processing of implicit SOAP headers
> -d --encoding=<charset> The charset encoding to use for generated sources
> -n, --nocompile Do not compile generated sources
> C:\Users\Administrator\playground\7.1.0.CR4\jboss-eap-7.1\bin>
> {noformat}
> *Additional info:*
> cc: [~asoldano], [~jbliznak]
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (ELY-1543) org.wildfly.security.asn1.DEREncoderTest fails on new JDK8 v.161
by Ilia Vassilev (JIRA)
Ilia Vassilev created ELY-1543:
----------------------------------
Summary: org.wildfly.security.asn1.DEREncoderTest fails on new JDK8 v.161
Key: ELY-1543
URL: https://issues.jboss.org/browse/ELY-1543
Project: WildFly Elytron
Issue Type: Bug
Components: Testsuite
Reporter: Ilia Vassilev
Assignee: Jan Kalina
Priority: Minor
Fix For: 1.2.0.Beta12
The org.wildfly.security.asn1.DEREncoderTest#testEncodeDSAKey() fails on JDK8 v.161 due to:
{noformat}
[ERROR] testEncodeDSAKey(org.wildfly.security.asn1.DEREncoderTest) Time elapsed: 0.124 s <<< ERROR!
java.security.InvalidKeyException: The security strength of SHA-1 digest algorithm is not sufficient for this key size
at sun.security.provider.DSA.checkKey(DSA.java:111)
at sun.security.provider.DSA.engineInitSign(DSA.java:143)
at java.security.Signature$Delegate.init(Signature.java:1156)
at java.security.Signature$Delegate.chooseProvider(Signature.java:1116)
at java.security.Signature$Delegate.engineInitSign(Signature.java:1180)
at java.security.Signature.initSign(Signature.java:531)
at org.wildfly.security.asn1.DEREncoderTest.testEncodeDSAKey(DEREncoderTest.java:458)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:386)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:323)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:143)
{noformat}
It affects also older tags, not only 1.1.8. It might be related to
https://bugs.java.com/view_bug.do?bug_id=8184341
It seems to be a testsuite issue only.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (ELY-1543) org.wildfly.security.asn1.DEREncoderTest fails on new JDK8 v.161
by Ilia Vassilev (JIRA)
[ https://issues.jboss.org/browse/ELY-1543?page=com.atlassian.jira.plugin.s... ]
Ilia Vassilev reassigned ELY-1543:
----------------------------------
Assignee: Ilia Vassilev (was: Jan Kalina)
> org.wildfly.security.asn1.DEREncoderTest fails on new JDK8 v.161
> ----------------------------------------------------------------
>
> Key: ELY-1543
> URL: https://issues.jboss.org/browse/ELY-1543
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Testsuite
> Reporter: Ilia Vassilev
> Assignee: Ilia Vassilev
> Priority: Minor
> Fix For: 7.1.2.GA
>
>
> The org.wildfly.security.asn1.DEREncoderTest#testEncodeDSAKey() fails on JDK8 v.161 due to:
> {noformat}
> [ERROR] testEncodeDSAKey(org.wildfly.security.asn1.DEREncoderTest) Time elapsed: 0.124 s <<< ERROR!
> java.security.InvalidKeyException: The security strength of SHA-1 digest algorithm is not sufficient for this key size
> at sun.security.provider.DSA.checkKey(DSA.java:111)
> at sun.security.provider.DSA.engineInitSign(DSA.java:143)
> at java.security.Signature$Delegate.init(Signature.java:1156)
> at java.security.Signature$Delegate.chooseProvider(Signature.java:1116)
> at java.security.Signature$Delegate.engineInitSign(Signature.java:1180)
> at java.security.Signature.initSign(Signature.java:531)
> at org.wildfly.security.asn1.DEREncoderTest.testEncodeDSAKey(DEREncoderTest.java:458)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:365)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:272)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:236)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:159)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:386)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:323)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:143)
> {noformat}
> It affects also older tags, not only 1.1.8. It might be related to
> https://bugs.java.com/view_bug.do?bug_id=8184341
> It seems to be a testsuite issue only.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (WFLY-6634) Add remote-cache-container configuration to Infinispan subsystem
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6634?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-6634:
--------------------------------------
bq. Right now, EAP7-942 covers only the security configuration for the remote-cache-manager.
No, that's incorrect. How could a feature pass QE without it's configuration being tested? I recommend looking into the proposal document, this item is the first one in the 'requirements' section. Please talk to the issue owner [~mvinkler] to figure out the internal QE details.
Nevertheless, we may now want to support injection as well, I have opened EAP7-961 for PM input.
> Add remote-cache-container configuration to Infinispan subsystem
> ----------------------------------------------------------------
>
> Key: WFLY-6634
> URL: https://issues.jboss.org/browse/WFLY-6634
> Project: WildFly
> Issue Type: Feature Request
> Components: Clustering
> Affects Versions: 10.0.0.Final
> Reporter: Paul Ferraro
> Assignee: Radoslav Husar
>
> Need to establish schema/model.
> We probably want to create new capabilities for existing container/caches to expose generic BasicCache/BasicCacheContainer types.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months