December 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-128) RFC 5843 additional hash types for Digest authentication, applied to SASL

by David Lloyd (JIRA)

David Lloyd created ELY-128: ------------------------------- Summary: RFC 5843 additional hash types for Digest authentication, applied to SASL Key: ELY-128 URL: https://issues.jboss.org/browse/ELY-128 Project: WildFly Elytron Issue Type: Enhancement Components: SASL Reporter: David Lloyd Assignee: David Lloyd Fix For: 1.0.0.Beta1 http://tools.ietf.org/html/rfc5843 specifies three additional SHA-based digest schemes. Apply these to SASL. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-671) KnowledgeBaseAdapter in legacy 5.x API is not serializable

by Mario Fusco (JIRA)

Mario Fusco created DROOLS-671: ---------------------------------- Summary: KnowledgeBaseAdapter in legacy 5.x API is not serializable Key: DROOLS-671 URL: https://issues.jboss.org/browse/DROOLS-671 Project: Drools Issue Type: Bug Reporter: Mario Fusco Assignee: Mario Fusco Trying to serialize a KnowledgeBase created with the legacy 5.x API causes the following exception. java.io.NotSerializableException: org.drools.impl.adapters.KnowledgeBaseAdapter at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1184) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:348) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (ELY-117) Support for SSL/TLS protocol and algorithm filtering

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-117?page=com.atlassian.jira.plugin.sy... ] David Lloyd resolved ELY-117. ----------------------------- Resolution: Done > Support for SSL/TLS protocol and algorithm filtering > ---------------------------------------------------- > > Key: ELY-117 > URL: https://issues.jboss.org/browse/ELY-117 > Project: WildFly Elytron > Issue Type: Feature Request > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.0.0.Beta1 > > > Support OpenSSL-style filter expressions. Consider the following prior work for reference: > * The GrokTLS project: https://github.com/timw/groktls > * Previous unmerged enhancement to XNIO: https://github.com/xnio/xnio/pull/56 > * APR/Native connector docs - http://tomcat.apache.org/tomcat-7.0-doc/config/http.html#SSL_Support_-_AP... > * OpenSSL docs: > ** https://www.openssl.org/docs/apps/ciphers.html#CIPHER_STRINGS > ** https://www.openssl.org/docs/apps/ciphers.html#CIPHER_SUITE_NAMES (note that the OpenSSL names are non-standard) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-3266) Exception are hidden by retry and end in a EJBCLIENT000032 Exception - the underlying client or server side cause is swallowed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-3266?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-3266: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1088463|https://bugzilla.redhat.com/show_bug.cgi?id=1088463] from POST to ASSIGNED > Exception are hidden by retry and end in a EJBCLIENT000032 Exception - the underlying client or server side cause is swallowed > ------------------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-3266 > URL: https://issues.jboss.org/browse/WFLY-3266 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.0.0.Final > Reporter: Wolf-Dieter Fink > Assignee: David Lloyd > Priority: Critical > > In case of large parameter input for EJB invocations the ejb-client throw the Exception below. > The underlying OutOfMemory is complete hidden, neither in the server.log nor in the ejb-client with TRACE a hint will be found. > java.lang.IllegalStateException: EJBCLIENT000032: Cannot retry a request which hasn't previously been completed > at org.jboss.ejb.client.EJBClientInvocationContext.retryRequest(EJBClientInvocationContext.java:200) > at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:256) > at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:265) > at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:198) > at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:181) > at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:144) > at com.sun.proxy.$Proxy6.uploadData(Unknown Source) > at de.info.biene.konsens.TestServiceWithAPITest.testUploadData(TestServiceWithAPITest.java:81) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.runners.ParentRunner.run(ParentRunner.java:309) > at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:252) > at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:141) > at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:112) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:189) > at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:165) > at org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:85) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:115) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:75) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (JBVFS-199) RealFileSystem:exists is not case sensitive in windows leading to a compilation failure with undertow and jbossweb

by Enrique González Martínez (JIRA)

[ https://issues.jboss.org/browse/JBVFS-199?page=com.atlassian.jira.plugin.... ] Enrique González Martínez edited comment on JBVFS-199 at 12/18/14 10:29 AM: ---------------------------------------------------------------------------- Problems during VirtualFile::exists If the real root mount point provided to the RealFileSystem is not an exact match (canonical form) if the flag jboss.vfs.forceCaseSensitive is set was (Author: elguardian): Problems during VirtualFile::exists If the real root mount point provided to the RealFileSystem is not an exact match (canonical form). > RealFileSystem:exists is not case sensitive in windows leading to a compilation failure with undertow and jbossweb > ------------------------------------------------------------------------------------------------------------------ > > Key: JBVFS-199 > URL: https://issues.jboss.org/browse/JBVFS-199 > Project: JBoss VFS > Issue Type: Bug > Affects Versions: 3.2.5.Final, 3.5.0.Alpha1 > Environment: Windows 64 bits > JDK 1.7.0_71 > Reporter: Enrique González Martínez > Assignee: Enrique González Martínez > Fix For: 3.2.8.Final, 3.5.0.Alpha1 > > > In Wildfly, during jsp compilation the lookup function uses the Classloader::getResourceAsStream that relies on VFSResourceLoader for opening an InputStream. This function is working different due to windows file system (not case sensitive). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-486) cli echo command should not output the result in columns

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-486?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated WFCORE-486: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1173615 > cli echo command should not output the result in columns > -------------------------------------------------------- > > Key: WFCORE-486 > URL: https://issues.jboss.org/browse/WFCORE-486 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI > Reporter: Alexey Loubyansky > Assignee: Alexey Loubyansky > > Current implementation of echo command displays the results in columns. Originally its arguments where limited to variables only. Now it also accepts arbitrary text mixed with expressions. So, the logical and expected output would be now the string with the expressions resolved. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (JBVFS-199) RealFileSystem:exists is not case sensitive in windows leading to a compilation failure with undertow and jbossweb

by Enrique González Martínez (JIRA)

[ https://issues.jboss.org/browse/JBVFS-199?page=com.atlassian.jira.plugin.... ] Enrique González Martínez reopened JBVFS-199: --------------------------------------------- Problems during VirtualFile::exists If the real root mount point provided to the RealFileSystem is not an exact match (canonical form). > RealFileSystem:exists is not case sensitive in windows leading to a compilation failure with undertow and jbossweb > ------------------------------------------------------------------------------------------------------------------ > > Key: JBVFS-199 > URL: https://issues.jboss.org/browse/JBVFS-199 > Project: JBoss VFS > Issue Type: Bug > Affects Versions: 3.2.5.Final, 3.5.0.Alpha1 > Environment: Windows 64 bits > JDK 1.7.0_71 > Reporter: Enrique González Martínez > Assignee: Enrique González Martínez > Fix For: 3.2.8.Final, 3.5.0.Alpha1 > > > In Wildfly, during jsp compilation the lookup function uses the Classloader::getResourceAsStream that relies on VFSResourceLoader for opening an InputStream. This function is working different due to windows file system (not case sensitive). -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-486) cli echo command should not output the result in columns

by Alexey Loubyansky (JIRA)

Alexey Loubyansky created WFCORE-486: ---------------------------------------- Summary: cli echo command should not output the result in columns Key: WFCORE-486 URL: https://issues.jboss.org/browse/WFCORE-486 Project: WildFly Core Issue Type: Enhancement Components: CLI Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Current implementation of echo command displays the results in columns. Originally its arguments where limited to variables only. Now it also accepts arbitrary text mixed with expressions. So, the logical and expected output would be now the string with the expressions resolved. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4100) Intermittent failure in org.jboss.as.test.integration.ejb.stateful.passivation.PassivationTestCase

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-4100?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-4100: -------------------------------------- Another PassivationTestCase.testPassivationMaxSize failure seen here http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=31906&buildTyp... > Intermittent failure in org.jboss.as.test.integration.ejb.stateful.passivation.PassivationTestCase > -------------------------------------------------------------------------------------------------- > > Key: WFLY-4100 > URL: https://issues.jboss.org/browse/WFLY-4100 > Project: WildFly > Issue Type: Bug > Components: Clustering, EJB > Affects Versions: 9.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > Seems to be a transactional issue with Infinispan eviction. > {noformat} > javax.ejb.EJBException: java.lang.IllegalStateException: WFLYCLEJBINF0008: Stateful session bean {[-89, -53, -3, -58, 52, -115, 78, 79, -106, -9, -119, 3, 0, 35, -10, -106]} refers to an invalid bean group 6c5836ab-086a-464c-8ae9-29e1a79a8254 > at org.wildfly.clustering.ejb.infinispan.bean.InfinispanBeanFactory.createBean(InfinispanBeanFactory.java:75) > at org.wildfly.clustering.ejb.infinispan.InfinispanBeanManager.findBean(InfinispanBeanManager.java:266) > at org.jboss.as.ejb3.cache.distributable.DistributableCache.get(DistributableCache.java:115) > at org.jboss.as.ejb3.component.stateful.StatefulComponentInstanceInterceptor.processInvocation(StatefulComponentInstanceInterceptor.java:58) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:280) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:345) > at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:243) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.remote.EJBRemoteTransactionPropagatingInterceptor.processInvocation(EJBRemoteTransactionPropagatingInterceptor.java:79) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:44) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:59) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:55) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) > at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:622) > at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:326) > at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309) > at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195) > at org.jboss.as.ejb3.remote.LocalEjbReceiver.processInvocation(LocalEjbReceiver.java:243) > at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:184) > at org.jboss.ejb.client.EJBObjectInterceptor.handleInvocation(EJBObjectInterceptor.java:58) > at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186) > at org.jboss.ejb.client.EJBHomeInterceptor.handleInvocation(EJBHomeInterceptor.java:83) > at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186) > at org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:42) > at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186) > at org.jboss.as.test.integration.ejb.remote.client.api.interceptor.SimpleEJBClientInterceptor.handleInvocation(SimpleEJBClientInterceptor.java:48) > at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186) > at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:125) > at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186) > at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:253) > at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:198) > at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:181) > at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:144) > at com.sun.proxy.$Proxy328.getManagedBeanMessage(Unknown Source) > at org.jboss.as.test.integration.ejb.stateful.passivation.PassivationTestCase.testPassivationMaxSize(PassivationTestCase.java:103) > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

[JBoss JIRA] (WFLY-670) Using "attribute" tag causes injection of null values

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-670?page=com.atlassian.jira.plugin.s... ] Kabir Khan resolved WFLY-670. ----------------------------- Resolution: Rejected > Using "attribute" tag causes injection of null values > ----------------------------------------------------- > > Key: WFLY-670 > URL: https://issues.jboss.org/browse/WFLY-670 > Project: WildFly > Issue Type: Bug > Components: JMX > Reporter: Anders Welen > Assignee: Tomasz Adamski > Priority: Minor > Fix For: Awaiting Volunteers > > > Using "attribute" tag in "jboss-service.xml" in a SAR archive causes injection of null values. Even if your code can handle this it makes it impossible to use primitive datatypes. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2014