[JBoss JIRA] (WFLY-6695) JspTagTestCase fails on Windows
by Frank Langelage (JIRA)
[ https://issues.jboss.org/browse/WFLY-6695?page=com.atlassian.jira.plugin.... ]
Frank Langelage commented on WFLY-6695:
---------------------------------------
Really strange. Now the Windows build with my change in your CI environment fails.
I have this behavior on my PC at home as well as on my Laptop at work.
Something that might be related: in both cases I use GitHub for Windows and executed the build from within the Git Shell.
I executed a new build in my Laptop now just from DOS command line to see if it makes any difrence.
Stay tuned. ;)
> JspTagTestCase fails on Windows
> -------------------------------
>
> Key: WFLY-6695
> URL: https://issues.jboss.org/browse/WFLY-6695
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 10.1.0.Final
> Environment: Windows 10, Oracle JDK 1.8.0_92
> Reporter: Frank Langelage
>
> build.bat clean install failed with
> -------------------------------------------------------------------------------
> Test set: org.jboss.as.test.integration.jsp.JspTagTestCase
> -------------------------------------------------------------------------------
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.768 sec <<< FAILURE! - in org.jboss.as.test.integration.jsp.JspTagTestCase
> test(org.jboss.as.test.integration.jsp.JspTagTestCase) Time elapsed: 0.486 sec <<< FAILURE!
> org.junit.ComparisonFailure: expected:<This is a header[
> <div>tag</div>
> Static content]
> > but was:<This is a header[
> <div>tag</div>
> Static content
> ]
> >
> at org.junit.Assert.assertEquals(Assert.java:115)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at org.jboss.as.test.integration.jsp.JspTagTestCase.test(JspTagTestCase.java:67)
> Replacing all occurence of "\n" with System.getProperty("line.separator") in the expected String solved the problem for me.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (LOGTOOL-110) Log Tool generates incorrect annotations
by gil cattaneo (JIRA)
[ https://issues.jboss.org/browse/LOGTOOL-110?page=com.atlassian.jira.plugi... ]
gil cattaneo commented on LOGTOOL-110:
--------------------------------------
It would be preferable to have one. Also for not duplicate (e.g. secutity) issues
The problem is related to JDP-24 LOGTOOL-104. Thanks for the info
> Log Tool generates incorrect annotations
> ----------------------------------------
>
> Key: LOGTOOL-110
> URL: https://issues.jboss.org/browse/LOGTOOL-110
> Project: Log Tool
> Issue Type: Bug
> Affects Versions: 2.0.1.Final
> Environment: openjdk version "1.8.0_91"
> OpenJDK Runtime Environment (build 1.8.0_91-b14)
> OpenJDK Server VM (build 25.91-b14, mixed mode)
> Apache Maven 3.3.3
> javax.enterprise:cdi-api:jar:1.2
> javax.inject:javax.inject:jar:1
> org.jboss.weld:weld-api:jar:2.3.Final
> org.jboss.weld:weld-spi:jar:2.3.Final
> org.jboss.classfilewriter:jboss-classfilewriter:jar:1.1.2.Final
> org.jboss.spec.javax.ejb:jboss-ejb-api_3.2_spec:jar:1.0.0.Final
> org.jboss.spec.javax.servlet:jboss-servlet-api_3.1_spec:jar:1.0.0.Final
> org.jboss.spec.javax.transaction:jboss-transaction-api_1.2_spec:jar:1.0.0.Final
> org.jboss.spec.javax.annotation:jboss-annotations-api_1.2_spec:jar:1.0.0.Final
> org.hibernate.javax.persistence:hibernate-jpa-2.1-api:jar:1.0.0.Final
> com.google.guava:guava:jar:18.0
> org.jboss.spec.javax.el:jboss-el-api_3.0_spec:jar:1.0.5.Final
> org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.2_spec:jar:1.0.0.Final
> org.jboss.logging:jboss-logging-processor:jar:2.0.1.Final
> org.jboss.logging:jboss-logging-annotations:jar:2.0.1.Final
> org.jboss.jdeparser:jdeparser:jar:2.0.0.Final
> org.jboss.logging:jboss-logging:jar:3.3.0.Final
> net.sourceforge.findbugs:annotations:jar:1.3.2
> Reporter: gil cattaneo
> Attachments: ReflectionLogger.i18n_locale_COUNTRY_VARIANT.properties, ReflectionLogger.java, ReflectionLogger_$logger.java, ReflectionLogger_logger.java, ResolutionLogger.i18n.properties, weld-core-build.log
>
>
> Hi
> i catch:
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile (default-compile) on project weld-core-impl: Compilation failure: Compilation failure:
> [ERROR] /builddir/build/BUILD/core-2.3.4.Final/impl/target/generated-sources/annotations/org/jboss/weld/logging/ReflectionLogger_$logger.java:[25,8] org.jboss.weld.logging.ReflectionLogger_$logger is not abstract and does not override abstract method illegalArgumentExceptionOnReflectionInvocation(java.lang.Class<?>,java.lang.Object,java.lang.reflect.Method,java.lang.String,java.lang.IllegalArgumentException) in org.jboss.weld.logging.ReflectionLogger
> [ERROR] /builddir/build/BUILD/core-2.3.4.Final/impl/target/generated-sources/annotations/org/jboss/weld/logging/ReflectionLogger_$logger.java:[198,5] method does not override or implement a method from a supertype
> [ERROR] -> [Help 1]
> any ideas?
> thanks in advance
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (LOGTOOL-110) Log Tool generates incorrect annotations
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/LOGTOOL-110?page=com.atlassian.jira.plugi... ]
James Perkins commented on LOGTOOL-110:
---------------------------------------
So in Fedora is only one version of a dependency allowed? Weld just can't use that version to build with.
> Log Tool generates incorrect annotations
> ----------------------------------------
>
> Key: LOGTOOL-110
> URL: https://issues.jboss.org/browse/LOGTOOL-110
> Project: Log Tool
> Issue Type: Bug
> Affects Versions: 2.0.1.Final
> Environment: openjdk version "1.8.0_91"
> OpenJDK Runtime Environment (build 1.8.0_91-b14)
> OpenJDK Server VM (build 25.91-b14, mixed mode)
> Apache Maven 3.3.3
> javax.enterprise:cdi-api:jar:1.2
> javax.inject:javax.inject:jar:1
> org.jboss.weld:weld-api:jar:2.3.Final
> org.jboss.weld:weld-spi:jar:2.3.Final
> org.jboss.classfilewriter:jboss-classfilewriter:jar:1.1.2.Final
> org.jboss.spec.javax.ejb:jboss-ejb-api_3.2_spec:jar:1.0.0.Final
> org.jboss.spec.javax.servlet:jboss-servlet-api_3.1_spec:jar:1.0.0.Final
> org.jboss.spec.javax.transaction:jboss-transaction-api_1.2_spec:jar:1.0.0.Final
> org.jboss.spec.javax.annotation:jboss-annotations-api_1.2_spec:jar:1.0.0.Final
> org.hibernate.javax.persistence:hibernate-jpa-2.1-api:jar:1.0.0.Final
> com.google.guava:guava:jar:18.0
> org.jboss.spec.javax.el:jboss-el-api_3.0_spec:jar:1.0.5.Final
> org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.2_spec:jar:1.0.0.Final
> org.jboss.logging:jboss-logging-processor:jar:2.0.1.Final
> org.jboss.logging:jboss-logging-annotations:jar:2.0.1.Final
> org.jboss.jdeparser:jdeparser:jar:2.0.0.Final
> org.jboss.logging:jboss-logging:jar:3.3.0.Final
> net.sourceforge.findbugs:annotations:jar:1.3.2
> Reporter: gil cattaneo
> Attachments: ReflectionLogger.i18n_locale_COUNTRY_VARIANT.properties, ReflectionLogger.java, ReflectionLogger_$logger.java, ReflectionLogger_logger.java, ResolutionLogger.i18n.properties, weld-core-build.log
>
>
> Hi
> i catch:
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile (default-compile) on project weld-core-impl: Compilation failure: Compilation failure:
> [ERROR] /builddir/build/BUILD/core-2.3.4.Final/impl/target/generated-sources/annotations/org/jboss/weld/logging/ReflectionLogger_$logger.java:[25,8] org.jboss.weld.logging.ReflectionLogger_$logger is not abstract and does not override abstract method illegalArgumentExceptionOnReflectionInvocation(java.lang.Class<?>,java.lang.Object,java.lang.reflect.Method,java.lang.String,java.lang.IllegalArgumentException) in org.jboss.weld.logging.ReflectionLogger
> [ERROR] /builddir/build/BUILD/core-2.3.4.Final/impl/target/generated-sources/annotations/org/jboss/weld/logging/ReflectionLogger_$logger.java:[198,5] method does not override or implement a method from a supertype
> [ERROR] -> [Help 1]
> any ideas?
> thanks in advance
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (LOGTOOL-110) Log Tool generates incorrect annotations
by gil cattaneo (JIRA)
[ https://issues.jboss.org/browse/LOGTOOL-110?page=com.atlassian.jira.plugi... ]
gil cattaneo commented on LOGTOOL-110:
--------------------------------------
we use jboss-logging-tools 2.0.1.Final for Wildfly 10+ upgrading.
> Log Tool generates incorrect annotations
> ----------------------------------------
>
> Key: LOGTOOL-110
> URL: https://issues.jboss.org/browse/LOGTOOL-110
> Project: Log Tool
> Issue Type: Bug
> Affects Versions: 2.0.1.Final
> Environment: openjdk version "1.8.0_91"
> OpenJDK Runtime Environment (build 1.8.0_91-b14)
> OpenJDK Server VM (build 25.91-b14, mixed mode)
> Apache Maven 3.3.3
> javax.enterprise:cdi-api:jar:1.2
> javax.inject:javax.inject:jar:1
> org.jboss.weld:weld-api:jar:2.3.Final
> org.jboss.weld:weld-spi:jar:2.3.Final
> org.jboss.classfilewriter:jboss-classfilewriter:jar:1.1.2.Final
> org.jboss.spec.javax.ejb:jboss-ejb-api_3.2_spec:jar:1.0.0.Final
> org.jboss.spec.javax.servlet:jboss-servlet-api_3.1_spec:jar:1.0.0.Final
> org.jboss.spec.javax.transaction:jboss-transaction-api_1.2_spec:jar:1.0.0.Final
> org.jboss.spec.javax.annotation:jboss-annotations-api_1.2_spec:jar:1.0.0.Final
> org.hibernate.javax.persistence:hibernate-jpa-2.1-api:jar:1.0.0.Final
> com.google.guava:guava:jar:18.0
> org.jboss.spec.javax.el:jboss-el-api_3.0_spec:jar:1.0.5.Final
> org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.2_spec:jar:1.0.0.Final
> org.jboss.logging:jboss-logging-processor:jar:2.0.1.Final
> org.jboss.logging:jboss-logging-annotations:jar:2.0.1.Final
> org.jboss.jdeparser:jdeparser:jar:2.0.0.Final
> org.jboss.logging:jboss-logging:jar:3.3.0.Final
> net.sourceforge.findbugs:annotations:jar:1.3.2
> Reporter: gil cattaneo
> Attachments: ReflectionLogger.i18n_locale_COUNTRY_VARIANT.properties, ReflectionLogger.java, ReflectionLogger_$logger.java, ReflectionLogger_logger.java, ResolutionLogger.i18n.properties, weld-core-build.log
>
>
> Hi
> i catch:
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile (default-compile) on project weld-core-impl: Compilation failure: Compilation failure:
> [ERROR] /builddir/build/BUILD/core-2.3.4.Final/impl/target/generated-sources/annotations/org/jboss/weld/logging/ReflectionLogger_$logger.java:[25,8] org.jboss.weld.logging.ReflectionLogger_$logger is not abstract and does not override abstract method illegalArgumentExceptionOnReflectionInvocation(java.lang.Class<?>,java.lang.Object,java.lang.reflect.Method,java.lang.String,java.lang.IllegalArgumentException) in org.jboss.weld.logging.ReflectionLogger
> [ERROR] /builddir/build/BUILD/core-2.3.4.Final/impl/target/generated-sources/annotations/org/jboss/weld/logging/ReflectionLogger_$logger.java:[198,5] method does not override or implement a method from a supertype
> [ERROR] -> [Help 1]
> any ideas?
> thanks in advance
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6695) JspTagTestCase fails on Windows
by Tomaz Cerar (JIRA)
[ https://issues.jboss.org/browse/WFLY-6695?page=com.atlassian.jira.plugin.... ]
Tomaz Cerar commented on WFLY-6695:
-----------------------------------
that is weird, it works fine for me on exact same environment.
+ we do CI testing on windows server 2012r2 and it passes just fine.
see https://ci.wildfly.org/project.html?projectId=WF&testNameId=3729947640288... for example (login as guest)
I agree with your proposed fix, but don't get why this happens. Anything else on your environment that is different?
> JspTagTestCase fails on Windows
> -------------------------------
>
> Key: WFLY-6695
> URL: https://issues.jboss.org/browse/WFLY-6695
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Affects Versions: 10.1.0.Final
> Environment: Windows 10, Oracle JDK 1.8.0_92
> Reporter: Frank Langelage
>
> build.bat clean install failed with
> -------------------------------------------------------------------------------
> Test set: org.jboss.as.test.integration.jsp.JspTagTestCase
> -------------------------------------------------------------------------------
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.768 sec <<< FAILURE! - in org.jboss.as.test.integration.jsp.JspTagTestCase
> test(org.jboss.as.test.integration.jsp.JspTagTestCase) Time elapsed: 0.486 sec <<< FAILURE!
> org.junit.ComparisonFailure: expected:<This is a header[
> <div>tag</div>
> Static content]
> > but was:<This is a header[
> <div>tag</div>
> Static content
> ]
> >
> at org.junit.Assert.assertEquals(Assert.java:115)
> at org.junit.Assert.assertEquals(Assert.java:144)
> at org.jboss.as.test.integration.jsp.JspTagTestCase.test(JspTagTestCase.java:67)
> Replacing all occurence of "\n" with System.getProperty("line.separator") in the expected String solved the problem for me.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6695) JspTagTestCase fails on Windows
by Frank Langelage (JIRA)
Frank Langelage created WFLY-6695:
-------------------------------------
Summary: JspTagTestCase fails on Windows
Key: WFLY-6695
URL: https://issues.jboss.org/browse/WFLY-6695
Project: WildFly
Issue Type: Bug
Components: Test Suite
Affects Versions: 10.1.0.Final
Environment: Windows 10, Oracle JDK 1.8.0_92
Reporter: Frank Langelage
build.bat clean install failed with
-------------------------------------------------------------------------------
Test set: org.jboss.as.test.integration.jsp.JspTagTestCase
-------------------------------------------------------------------------------
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.768 sec <<< FAILURE! - in org.jboss.as.test.integration.jsp.JspTagTestCase
test(org.jboss.as.test.integration.jsp.JspTagTestCase) Time elapsed: 0.486 sec <<< FAILURE!
org.junit.ComparisonFailure: expected:<This is a header[
<div>tag</div>
Static content]
> but was:<This is a header[
<div>tag</div>
Static content
]
>
at org.junit.Assert.assertEquals(Assert.java:115)
at org.junit.Assert.assertEquals(Assert.java:144)
at org.jboss.as.test.integration.jsp.JspTagTestCase.test(JspTagTestCase.java:67)
Replacing all occurence of "\n" with System.getProperty("line.separator") in the expected String solved the problem for me.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (LOGTOOL-110) Log Tool generates incorrect annotations
by James Perkins (JIRA)
[ https://issues.jboss.org/browse/LOGTOOL-110?page=com.atlassian.jira.plugi... ]
James Perkins commented on LOGTOOL-110:
---------------------------------------
For some reason the build is resolving the wrong dependencies. The {{org.jboss.logging:jboss-logging-processor:jar:1.1.0.Final}} should use the {{org.jboss.logging:jboss-logging-annotations:jar:1.1.0.Final}} dependency not 2.0.1.Final. The 2.0.1.Final version uses a new version of jdeparser which is where the issue is coming from. It's fixed in newer versions of jdeparser, but there's no release of the logging processor that uses the newer version.
{code:title=build.log snippet}
[DEBUG] org.jboss.logging:jboss-logging-processor:jar:1.1.0.Final:provided
[DEBUG] org.jboss.logging:jboss-logging-annotations:jar:2.0.1.Final:provided
[DEBUG] org.jboss.jdeparser:jdeparser:jar:2.0.0.Final:provided
[DEBUG] org.jboss.logging:jboss-logging:jar:3.2.1.Final:compile
{code}
{code:title=Dependency Tree from Weld}
[INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @ weld-core-impl ---
[INFO] org.jboss.weld:weld-core-impl:jar:3.0.0-SNAPSHOT
[INFO] +- org.jboss.weld:weld-api:jar:3.0.Alpha19:compile
[INFO] | \- javax.enterprise:cdi-api:jar:2.0.Alpha4:compile
[INFO] | \- javax.inject:javax.inject:jar:1:compile
[INFO] +- org.jboss.weld:weld-spi:jar:3.0.Alpha19:compile
[INFO] +- org.jboss.classfilewriter:jboss-classfilewriter:jar:1.1.2.Final:compile
[INFO] +- org.jboss.spec.javax.annotation:jboss-annotations-api_1.2_spec:jar:1.0.0.Final:compile
[INFO] +- org.hibernate.javax.persistence:hibernate-jpa-2.1-api:jar:1.0.0.Final:compile
[INFO] +- org.jboss.spec.javax.el:jboss-el-api_3.0_spec:jar:1.0.0.Alpha1:compile
[INFO] +- org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.2_spec:jar:1.0.0.Final:compile
[INFO] +- org.jboss.logging:jboss-logging-processor:jar:1.1.0.Final:provided
[INFO] | \- org.jboss.jdeparser:jdeparser:jar:1.0.0.Final:provided
[INFO] +- org.jboss.logging:jboss-logging:jar:3.2.1.Final:compile
[INFO] +- net.sourceforge.findbugs:annotations:jar:1.3.2:compile
[INFO] +- junit:junit:jar:4.12:test
[INFO] | \- org.hamcrest:hamcrest-core:jar:1.3:test
[INFO] \- org.jboss.logmanager:jboss-logmanager:jar:1.2.2.GA:test
{code}
I don't know much about how Fedora builds/RPM's work, but it looks like it's pulling in bad dependencies.
> Log Tool generates incorrect annotations
> ----------------------------------------
>
> Key: LOGTOOL-110
> URL: https://issues.jboss.org/browse/LOGTOOL-110
> Project: Log Tool
> Issue Type: Bug
> Affects Versions: 2.0.1.Final
> Environment: openjdk version "1.8.0_91"
> OpenJDK Runtime Environment (build 1.8.0_91-b14)
> OpenJDK Server VM (build 25.91-b14, mixed mode)
> Apache Maven 3.3.3
> javax.enterprise:cdi-api:jar:1.2
> javax.inject:javax.inject:jar:1
> org.jboss.weld:weld-api:jar:2.3.Final
> org.jboss.weld:weld-spi:jar:2.3.Final
> org.jboss.classfilewriter:jboss-classfilewriter:jar:1.1.2.Final
> org.jboss.spec.javax.ejb:jboss-ejb-api_3.2_spec:jar:1.0.0.Final
> org.jboss.spec.javax.servlet:jboss-servlet-api_3.1_spec:jar:1.0.0.Final
> org.jboss.spec.javax.transaction:jboss-transaction-api_1.2_spec:jar:1.0.0.Final
> org.jboss.spec.javax.annotation:jboss-annotations-api_1.2_spec:jar:1.0.0.Final
> org.hibernate.javax.persistence:hibernate-jpa-2.1-api:jar:1.0.0.Final
> com.google.guava:guava:jar:18.0
> org.jboss.spec.javax.el:jboss-el-api_3.0_spec:jar:1.0.5.Final
> org.jboss.spec.javax.interceptor:jboss-interceptors-api_1.2_spec:jar:1.0.0.Final
> org.jboss.logging:jboss-logging-processor:jar:2.0.1.Final
> org.jboss.logging:jboss-logging-annotations:jar:2.0.1.Final
> org.jboss.jdeparser:jdeparser:jar:2.0.0.Final
> org.jboss.logging:jboss-logging:jar:3.3.0.Final
> net.sourceforge.findbugs:annotations:jar:1.3.2
> Reporter: gil cattaneo
> Attachments: ReflectionLogger.i18n_locale_COUNTRY_VARIANT.properties, ReflectionLogger.java, ReflectionLogger_$logger.java, ReflectionLogger_logger.java, ResolutionLogger.i18n.properties, weld-core-build.log
>
>
> Hi
> i catch:
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.5.1:compile (default-compile) on project weld-core-impl: Compilation failure: Compilation failure:
> [ERROR] /builddir/build/BUILD/core-2.3.4.Final/impl/target/generated-sources/annotations/org/jboss/weld/logging/ReflectionLogger_$logger.java:[25,8] org.jboss.weld.logging.ReflectionLogger_$logger is not abstract and does not override abstract method illegalArgumentExceptionOnReflectionInvocation(java.lang.Class<?>,java.lang.Object,java.lang.reflect.Method,java.lang.String,java.lang.IllegalArgumentException) in org.jboss.weld.logging.ReflectionLogger
> [ERROR] /builddir/build/BUILD/core-2.3.4.Final/impl/target/generated-sources/annotations/org/jboss/weld/logging/ReflectionLogger_$logger.java:[198,5] method does not override or implement a method from a supertype
> [ERROR] -> [Help 1]
> any ideas?
> thanks in advance
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6678) StackoverflowError ejbclientinvocationcontext
by Jimmy Pannier (JIRA)
[ https://issues.jboss.org/browse/WFLY-6678?page=com.atlassian.jira.plugin.... ]
Jimmy Pannier commented on WFLY-6678:
-------------------------------------
I'll test to increase the default stacksize via -Xss vm option.
> StackoverflowError ejbclientinvocationcontext
> ---------------------------------------------
>
> Key: WFLY-6678
> URL: https://issues.jboss.org/browse/WFLY-6678
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Environment: wildfly 9.0.1, jdk 1.8
> Reporter: Jimmy Pannier
> Attachments: server.log
>
>
> Sometimes after few days i get an exception
> Here is a stacktrace.
> 2016-06-07 07:38:10,441 ERROR [org.jboss.as.ejb3.invocation] (default task-76) WFLYEJB0034: EJB Invocation failed on component StorageServiceImpl for method public abstract java.util.List com.inovelan.cloud.api.storage.service.dataset.IStorageEjbService.loadData(com.inovelan.cloud.api.storage.model.dto.dataset.LoadDataConfig): javax.ejb.EJBTransactionRolledbackException: WFLYEJB0457: Unexpected Error
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleInCallerTx(CMTTxInterceptor.java:153)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInCallerTx(CMTTxInterceptor.java:256)
> at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:329)
> .....
> Caused by: java.lang.StackOverflowError
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
> at com.inovelan.cloud.common.proxy.ProxyInterceptor.handleInvocationResult(ProxyInterceptor.java:37)
> at org.jboss.ejb.client.EJBClientInvocationContext.getResult(EJBClientInvocationContext.java:290)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (SECURITY-943) AdvancedLdapLoginModule authentication fails when some part of DN is part of LDAP URL
by Bartosz Spyrko-Śmietanko (JIRA)
[ https://issues.jboss.org/browse/SECURITY-943?page=com.atlassian.jira.plug... ]
Bartosz Spyrko-Śmietanko commented on SECURITY-943:
---------------------------------------------------
[~dlofthouse] if you haven't already started working on this one, do you mind if I take it over?
> AdvancedLdapLoginModule authentication fails when some part of DN is part of LDAP URL
> -------------------------------------------------------------------------------------
>
> Key: SECURITY-943
> URL: https://issues.jboss.org/browse/SECURITY-943
> Project: PicketBox
> Issue Type: Bug
> Components: Negotiation
> Affects Versions: Negotiation_3_0_2_Final
> Reporter: Ondrej Lukas
> Assignee: Darran Lofthouse
> Fix For: Negotiation_3_0_3_CR1
>
>
> In case when part of DN is placed in LDAP URL instead of baseCtxDN then authentication fails (see [1] for details about this URL) in AdvancedLdapLoginModule. Authentication is provided by binding with user DN and password, but in this case user DN does not include DN part from LDAP URL which leads to fail.
> Thrown exception:
> {code}
> javax.naming.AuthenticationException: LDAP: error code 49 - INVALID_CREDENTIALS: Bind failed: ERR_229 Cannot authenticate user uid=jduke,ou=People
> com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3135)
> com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:3081)
> com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2883)
> com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2797)
> com.sun.jndi.ldap.LdapCtx.<init>(LdapCtx.java:319)
> com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192)
> com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:210)
> com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:153)
> com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:83)
> org.jboss.as.naming.InitialContext.getDefaultInitCtx(InitialContext.java:114)
> org.jboss.as.naming.InitialContext.init(InitialContext.java:99)
> javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:154)
> org.jboss.as.naming.InitialContext.<init>(InitialContext.java:89)
> org.jboss.as.naming.InitialContextFactory.getInitialContext(InitialContextFactory.java:43)
> javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
> javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)
> javax.naming.InitialContext.init(InitialContext.java:244)
> javax.naming.ldap.InitialLdapContext.<init>(InitialLdapContext.java:154)
> org.jboss.security.negotiation.AdvancedLdapLoginModule.constructLdapContext(AdvancedLdapLoginModule.java:486)
> org.jboss.security.negotiation.AdvancedLdapLoginModule.authenticate(AdvancedLdapLoginModule.java:669)
> org.jboss.security.negotiation.AdvancedLdapLoginModule.innerLogin(AdvancedLdapLoginModule.java:397)
> org.jboss.security.negotiation.AdvancedLdapLoginModule$AuthorizeAction.run(AdvancedLdapLoginModule.java:967)
> org.jboss.security.negotiation.AdvancedLdapLoginModule.login(AdvancedLdapLoginModule.java:326)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> ...
> {code}
> [1] https://tools.ietf.org/html/rfc2255
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (ELY-569) Builder for X500Principal objects
by David Lloyd (JIRA)
David Lloyd created ELY-569:
-------------------------------
Summary: Builder for X500Principal objects
Key: ELY-569
URL: https://issues.jboss.org/browse/ELY-569
Project: WildFly Elytron
Issue Type: Feature Request
Components: X.500
Reporter: David Lloyd
Assignee: David Lloyd
In order to support any kind of certificate or CSR creation, we need the ability to construct an X.500 Principal object.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month