[JBoss JIRA] (WFLY-9118) Change the default value of call-failover-timeout from infinite to 30s
by Jeff Mesnil (JIRA)
Jeff Mesnil created WFLY-9118:
---------------------------------
Summary: Change the default value of call-failover-timeout from infinite to 30s
Key: WFLY-9118
URL: https://issues.jboss.org/browse/WFLY-9118
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 11.0.0.Alpha1
Reporter: Jeff Mesnil
Assignee: Jeff Mesnil
This is related to https://issues.jboss.org/browse/WFLY-8492.
Currently, the messaging-activemq resources that defines the call-failover-timeout attribute uses a default value of -1.
That means that during failover, if an Artemis client sends a Packet in a non-blocking call, they will wait forever to get a response. It leaves no opportunity for the client to "give up" (e.g. if the application is asked to shut down).
Artemis changed their default values to 30s (in ARTEMIS-255) and we should do the same for the messaging-activemq attribute.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (WFCORE-3086) standalone.bat restart EAP unexpectedly
by Radovan Stancel (JIRA)
[ https://issues.jboss.org/browse/WFCORE-3086?page=com.atlassian.jira.plugi... ]
Radovan Stancel moved JBEAP-12274 to WFCORE-3086:
-------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-3086 (was: JBEAP-12274)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Affects Version/s: 3.0.0.Beta28
(was: 7.0.7.GA)
> standalone.bat restart EAP unexpectedly
> ---------------------------------------
>
> Key: WFCORE-3086
> URL: https://issues.jboss.org/browse/WFCORE-3086
> Project: WildFly Core
> Issue Type: Bug
> Affects Versions: 3.0.0.Beta28
> Reporter: Radovan Stancel
> Assignee: Radovan Stancel
> Labels: downstream_dependency
>
> Description of problem:
> By the following code in standalone.bat, domain.bat, EAP restarts unexpectedly when the ERRORLEVEL set more than 10.
> > if ERRORLEVEL 10 goto RESTART
> For example, when Shutting down Windows while EAP is running, exit code is set as 143 and EAP is restarted.
> Originally, EAP expect 10 for restarting.
> The value is defined as the following constant.
> org.jboss.as.process.ExitCodes.RESTART_PROCESS_FROM_STARTUP_SCRIPT
> Version-Release number of selected component (if applicable):
> 6.x, 7.x
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (ELY-1299) X509EvidenceVerificationSuiteChild.testX509Auth() fails on IBM JDK
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/ELY-1299?page=com.atlassian.jira.plugin.s... ]
Peter Palaga commented on ELY-1299:
-----------------------------------
Looks like IBM's PEM parser is less permissive than the one of Oracle/OpenJDK. When the plain text part starting with
{code}
Certificate:
Data:
{code}
up to
{code}
-----BEGIN CERTIFICATE-----
{code}
is removed, the test passes as expected.
It is worth noting that our {{Pem.parsePemX509Certificate()}} does not accept PEM files with paintext prefix either. Should I file that as a separate issue?
> X509EvidenceVerificationSuiteChild.testX509Auth() fails on IBM JDK
> ------------------------------------------------------------------
>
> Key: ELY-1299
> URL: https://issues.jboss.org/browse/ELY-1299
> Project: WildFly Elytron
> Issue Type: Bug
> Reporter: Peter Palaga
> Assignee: Peter Palaga
>
> {code}
> export JAVA_HOME=path/to/ibm/java8
> $JAVA_HOME/bin/java -version
> java version "1.8.0"
> Java(TM) SE Runtime Environment (build pxa6480sr3fp12-20160919_01(SR3 FP12))
> IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20160915_318796 (JIT enabled, AOT enabled)
> J9VM - R28_Java8_SR3_20160915_0912_B318796
> JIT - tr.r14.java.green_20160818_122998
> GC - R28_Java8_SR3_20160915_0912_B318796_CMPRSS
> J9CL - 20160915_318796)
> JCL - 20160914_01 based on Oracle jdk8u101-b13
> mvn clean test -Dtest=LdapTestSuite
> {code}
> Expected: the selected test suite passes
> Actual: {{X509EvidenceVerificationSuiteChild.testX509Auth()}} fails with the following exception:
> {code}
> java.security.cert.CertificateException: Unable to initialize, java.io.IOException: insufficient data
> at com.ibm.security.x509.X509CertImpl.<init>(X509CertImpl.java:268)
> at java.security.cert.CertificateFactory.generateCertificate(CertificateFactory.java:407)
> at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.loadCertificate(X509EvidenceVerificationSuiteChild.java:74)
> at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.testX509Auth(X509EvidenceVerificationSuiteChild.java:65)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.lang.reflect.Method.invoke(Method.java:508)
> at org.wildfly.security.ldap.DirContextFactoryRule$1.evaluate(DirContextFactoryRule.java:61)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (ELY-1299) X509EvidenceVerificationSuiteChild.testX509Auth() fails on IBM JDK
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/ELY-1299?page=com.atlassian.jira.plugin.s... ]
Peter Palaga updated ELY-1299:
------------------------------
Description:
{code}
export JAVA_HOME=path/to/ibm/java8
$JAVA_HOME/bin/java -version
java version "1.8.0"
Java(TM) SE Runtime Environment (build pxa6480sr3fp12-20160919_01(SR3 FP12))
IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20160915_318796 (JIT enabled, AOT enabled)
J9VM - R28_Java8_SR3_20160915_0912_B318796
JIT - tr.r14.java.green_20160818_122998
GC - R28_Java8_SR3_20160915_0912_B318796_CMPRSS
J9CL - 20160915_318796)
JCL - 20160914_01 based on Oracle jdk8u101-b13
mvn clean test -Dtest=LdapTestSuite
{code}
Expected: the selected test suite passes
Actual: {{X509EvidenceVerificationSuiteChild.testX509Auth()}} fails with the following exception:
{code}
java.security.cert.CertificateException: Unable to initialize, java.io.IOException: insufficient data
at com.ibm.security.x509.X509CertImpl.<init>(X509CertImpl.java:268)
at java.security.cert.CertificateFactory.generateCertificate(CertificateFactory.java:407)
at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.loadCertificate(X509EvidenceVerificationSuiteChild.java:74)
at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.testX509Auth(X509EvidenceVerificationSuiteChild.java:65)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.lang.reflect.Method.invoke(Method.java:508)
at org.wildfly.security.ldap.DirContextFactoryRule$1.evaluate(DirContextFactoryRule.java:61)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
{code}
was:
{code}
export JAVA_HOME=path/to/ibm/java8
$JAVA_HOME/bin/java -version
java version "1.8.0"
Java(TM) SE Runtime Environment (build pxa6480sr3fp12-20160919_01(SR3 FP12))
IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20160915_318796 (JIT enabled, AOT enabled)
J9VM - R28_Java8_SR3_20160915_0912_B318796
JIT - tr.r14.java.green_20160818_122998
GC - R28_Java8_SR3_20160915_0912_B318796_CMPRSS
J9CL - 20160915_318796)
JCL - 20160914_01 based on Oracle jdk8u101-b13
mvn clean test -Dtest=LdapTestSuite
{code}
Expected: the selected test suite passes
Actual: {{X509EvidenceVerificationSuiteChild.testX509Auth()}} fails with the followinf exception:
{code}
java.security.cert.CertificateException: Unable to initialize, java.io.IOException: insufficient data
at com.ibm.security.x509.X509CertImpl.<init>(X509CertImpl.java:268)
at java.security.cert.CertificateFactory.generateCertificate(CertificateFactory.java:407)
at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.loadCertificate(X509EvidenceVerificationSuiteChild.java:74)
at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.testX509Auth(X509EvidenceVerificationSuiteChild.java:65)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.lang.reflect.Method.invoke(Method.java:508)
at org.wildfly.security.ldap.DirContextFactoryRule$1.evaluate(DirContextFactoryRule.java:61)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
{code}
> X509EvidenceVerificationSuiteChild.testX509Auth() fails on IBM JDK
> ------------------------------------------------------------------
>
> Key: ELY-1299
> URL: https://issues.jboss.org/browse/ELY-1299
> Project: WildFly Elytron
> Issue Type: Bug
> Reporter: Peter Palaga
> Assignee: Peter Palaga
>
> {code}
> export JAVA_HOME=path/to/ibm/java8
> $JAVA_HOME/bin/java -version
> java version "1.8.0"
> Java(TM) SE Runtime Environment (build pxa6480sr3fp12-20160919_01(SR3 FP12))
> IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20160915_318796 (JIT enabled, AOT enabled)
> J9VM - R28_Java8_SR3_20160915_0912_B318796
> JIT - tr.r14.java.green_20160818_122998
> GC - R28_Java8_SR3_20160915_0912_B318796_CMPRSS
> J9CL - 20160915_318796)
> JCL - 20160914_01 based on Oracle jdk8u101-b13
> mvn clean test -Dtest=LdapTestSuite
> {code}
> Expected: the selected test suite passes
> Actual: {{X509EvidenceVerificationSuiteChild.testX509Auth()}} fails with the following exception:
> {code}
> java.security.cert.CertificateException: Unable to initialize, java.io.IOException: insufficient data
> at com.ibm.security.x509.X509CertImpl.<init>(X509CertImpl.java:268)
> at java.security.cert.CertificateFactory.generateCertificate(CertificateFactory.java:407)
> at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.loadCertificate(X509EvidenceVerificationSuiteChild.java:74)
> at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.testX509Auth(X509EvidenceVerificationSuiteChild.java:65)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.lang.reflect.Method.invoke(Method.java:508)
> at org.wildfly.security.ldap.DirContextFactoryRule$1.evaluate(DirContextFactoryRule.java:61)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (ELY-1299) X509EvidenceVerificationSuiteChild.testX509Auth() fails on IBM JDK
by Peter Palaga (JIRA)
Peter Palaga created ELY-1299:
---------------------------------
Summary: X509EvidenceVerificationSuiteChild.testX509Auth() fails on IBM JDK
Key: ELY-1299
URL: https://issues.jboss.org/browse/ELY-1299
Project: WildFly Elytron
Issue Type: Bug
Reporter: Peter Palaga
Assignee: Peter Palaga
{code}
export JAVA_HOME=path/to/ibm/java8
$JAVA_HOME/bin/java -version
java version "1.8.0"
Java(TM) SE Runtime Environment (build pxa6480sr3fp12-20160919_01(SR3 FP12))
IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20160915_318796 (JIT enabled, AOT enabled)
J9VM - R28_Java8_SR3_20160915_0912_B318796
JIT - tr.r14.java.green_20160818_122998
GC - R28_Java8_SR3_20160915_0912_B318796_CMPRSS
J9CL - 20160915_318796)
JCL - 20160914_01 based on Oracle jdk8u101-b13
mvn clean test -Dtest=LdapTestSuite
{code}
Expected: the selected test suite passes
Actual: {{X509EvidenceVerificationSuiteChild.testX509Auth()}} fails with the followinf exception:
{code}
java.security.cert.CertificateException: Unable to initialize, java.io.IOException: insufficient data
at com.ibm.security.x509.X509CertImpl.<init>(X509CertImpl.java:268)
at java.security.cert.CertificateFactory.generateCertificate(CertificateFactory.java:407)
at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.loadCertificate(X509EvidenceVerificationSuiteChild.java:74)
at org.wildfly.security.ldap.X509EvidenceVerificationSuiteChild.testX509Auth(X509EvidenceVerificationSuiteChild.java:65)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.lang.reflect.Method.invoke(Method.java:508)
at org.wildfly.security.ldap.DirContextFactoryRule$1.evaluate(DirContextFactoryRule.java:61)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (ELY-1293) System.currentTimeMillis() cannot be mocked on IBM JDK
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/ELY-1293?page=com.atlassian.jira.plugin.s... ]
Peter Palaga commented on ELY-1293:
-----------------------------------
Now that the PR https://github.com/wildfly-security/wildfly-elytron/pull/917 was merged, I moved the unsolved part with {{GssapiCompatibilitySuiteChild}} to a new issue ELY-1298
> System.currentTimeMillis() cannot be mocked on IBM JDK
> ------------------------------------------------------
>
> Key: ELY-1293
> URL: https://issues.jboss.org/browse/ELY-1293
> Project: WildFly Elytron
> Issue Type: Bug
> Reporter: Peter Palaga
> Assignee: Peter Palaga
>
> {{System.currentTimeMillis()}} is native in IBM JDK and at the same time, IBM JDK does not support java.lang.instrument API for native methods. Therefore, {{System.currentTimeMillis()}} cannot be mocked on IBM JDK using jmockit.
> {code}
> export JAVA_HOME=path/to/ibm/java8
> $JAVA_HOME/bin/java -version
> java version "1.8.0"
> Java(TM) SE Runtime Environment (build pxa6480sr3fp12-20160919_01(SR3 FP12))
> IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20160915_318796 (JIT enabled, AOT enabled)
> J9VM - R28_Java8_SR3_20160915_0912_B318796
> JIT - tr.r14.java.green_20160818_122998
> GC - R28_Java8_SR3_20160915_0912_B318796_CMPRSS
> J9CL - 20160915_318796)
> JCL - 20160914_01 based on Oracle jdk8u101-b13
> mvn clean test
> {code}
> Expected: the tests mocking {{System.currentTimeMillis()}} should pass
> Actual: the tests mocking {{System.currentTimeMillis()}} throw the following exception or similar:
> {code}
> java.lang.UnsupportedOperationException: class redefinition failed: attempted to change method modifiers
> at org.wildfly.security.audit.PeriodicRotatingFileAuditEndpointTest$1.<init>(PeriodicRotatingFileAuditEndpointTest.java:212)
> at org.wildfly.security.audit.PeriodicRotatingFileAuditEndpointTest.mockTime(PeriodicRotatingFileAuditEndpointTest.java:212)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.lang.reflect.Method.invoke(Method.java:508)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
> {code}
> This is the case with
> * PeriodicRotatingFileAuditEndpointTest
> * SizeRotatingFileAuditEndpointTest
> * GssapiCompatibilitySuiteChild
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (ELY-1298) GssapiCompatibilitySuiteChild fails on IBM JDK
by Peter Palaga (JIRA)
Peter Palaga created ELY-1298:
---------------------------------
Summary: GssapiCompatibilitySuiteChild fails on IBM JDK
Key: ELY-1298
URL: https://issues.jboss.org/browse/ELY-1298
Project: WildFly Elytron
Issue Type: Bug
Reporter: Peter Palaga
Assignee: Darran Lofthouse
A followup of ELY-1293
{{System.currentTimeMillis()}} is native in IBM JDK and at the same time, IBM JDK does not support java.lang.instrument API for native methods. Therefore, {{System.currentTimeMillis()}} cannot be mocked on IBM JDK using jmockit.
{code}
export JAVA_HOME=path/to/ibm/java8
$JAVA_HOME/bin/java -version
java version "1.8.0"
Java(TM) SE Runtime Environment (build pxa6480sr3fp12-20160919_01(SR3 FP12))
IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20160915_318796 (JIT enabled, AOT enabled)
J9VM - R28_Java8_SR3_20160915_0912_B318796
JIT - tr.r14.java.green_20160818_122998
GC - R28_Java8_SR3_20160915_0912_B318796_CMPRSS
J9CL - 20160915_318796)
JCL - 20160914_01 based on Oracle jdk8u101-b13
mvn clean test
{code}
Expected: the tests mocking {{System.currentTimeMillis()}} should pass
Actual: the tests mocking {{System.currentTimeMillis()}} throw the following exception or similar:
{code}
java.lang.UnsupportedOperationException: class redefinition failed: attempted to change method modifiers
at org.wildfly.security.audit.PeriodicRotatingFileAuditEndpointTest$1.<init>(PeriodicRotatingFileAuditEndpointTest.java:212)
at org.wildfly.security.audit.PeriodicRotatingFileAuditEndpointTest.mockTime(PeriodicRotatingFileAuditEndpointTest.java:212)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.lang.reflect.Method.invoke(Method.java:508)
at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
{code}
This is currently the case with
* GssapiCompatibilitySuiteChild
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (ELY-1298) GssapiCompatibilitySuiteChild fails on IBM JDK
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/ELY-1298?page=com.atlassian.jira.plugin.s... ]
Peter Palaga reassigned ELY-1298:
---------------------------------
Assignee: Peter Palaga (was: Darran Lofthouse)
> GssapiCompatibilitySuiteChild fails on IBM JDK
> ----------------------------------------------
>
> Key: ELY-1298
> URL: https://issues.jboss.org/browse/ELY-1298
> Project: WildFly Elytron
> Issue Type: Bug
> Reporter: Peter Palaga
> Assignee: Peter Palaga
>
> A followup of ELY-1293
> {{System.currentTimeMillis()}} is native in IBM JDK and at the same time, IBM JDK does not support java.lang.instrument API for native methods. Therefore, {{System.currentTimeMillis()}} cannot be mocked on IBM JDK using jmockit.
> {code}
> export JAVA_HOME=path/to/ibm/java8
> $JAVA_HOME/bin/java -version
> java version "1.8.0"
> Java(TM) SE Runtime Environment (build pxa6480sr3fp12-20160919_01(SR3 FP12))
> IBM J9 VM (build 2.8, JRE 1.8.0 Linux amd64-64 Compressed References 20160915_318796 (JIT enabled, AOT enabled)
> J9VM - R28_Java8_SR3_20160915_0912_B318796
> JIT - tr.r14.java.green_20160818_122998
> GC - R28_Java8_SR3_20160915_0912_B318796_CMPRSS
> J9CL - 20160915_318796)
> JCL - 20160914_01 based on Oracle jdk8u101-b13
> mvn clean test
> {code}
> Expected: the tests mocking {{System.currentTimeMillis()}} should pass
> Actual: the tests mocking {{System.currentTimeMillis()}} throw the following exception or similar:
> {code}
> java.lang.UnsupportedOperationException: class redefinition failed: attempted to change method modifiers
> at org.wildfly.security.audit.PeriodicRotatingFileAuditEndpointTest$1.<init>(PeriodicRotatingFileAuditEndpointTest.java:212)
> at org.wildfly.security.audit.PeriodicRotatingFileAuditEndpointTest.mockTime(PeriodicRotatingFileAuditEndpointTest.java:212)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.lang.reflect.Method.invoke(Method.java:508)
> at org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:367)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:274)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:238)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:161)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:290)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:242)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:121)
> {code}
> This is currently the case with
> * GssapiCompatibilitySuiteChild
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (ELY-437) Elytron compilation fails with IBM JDK
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/ELY-437?page=com.atlassian.jira.plugin.sy... ]
Peter Palaga commented on ELY-437:
----------------------------------
[~dlofthouse] I feel being addressed :)
> Elytron compilation fails with IBM JDK
> --------------------------------------
>
> Key: ELY-437
> URL: https://issues.jboss.org/browse/ELY-437
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta4
> Reporter: Ondrej Lukas
> Assignee: Peter Palaga
> Priority: Critical
> Fix For: 1.2.0.Beta1
>
>
> Compilation of wildfly-elytron project with IBM JDK 1.8 fails with:
> {code}
> wildfly-elytron/src/main/java/org/wildfly/security/x500/X500PrincipalUtil.java:[31,25] cannot find symbol
> symbol: class X500Name
> location: package sun.security.x509
> {code}
> Class X500PrincipalUtil using sun.security.x509.X500Name which comes from internal API and leads to mentioned above issue.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (ELY-437) Elytron compilation fails with IBM JDK
by Peter Palaga (JIRA)
[ https://issues.jboss.org/browse/ELY-437?page=com.atlassian.jira.plugin.sy... ]
Peter Palaga reassigned ELY-437:
--------------------------------
Assignee: Peter Palaga (was: Darran Lofthouse)
> Elytron compilation fails with IBM JDK
> --------------------------------------
>
> Key: ELY-437
> URL: https://issues.jboss.org/browse/ELY-437
> Project: WildFly Elytron
> Issue Type: Bug
> Affects Versions: 1.1.0.Beta4
> Reporter: Ondrej Lukas
> Assignee: Peter Palaga
> Priority: Critical
> Fix For: 1.2.0.Beta1
>
>
> Compilation of wildfly-elytron project with IBM JDK 1.8 fails with:
> {code}
> wildfly-elytron/src/main/java/org/wildfly/security/x500/X500PrincipalUtil.java:[31,25] cannot find symbol
> symbol: class X500Name
> location: package sun.security.x509
> {code}
> Class X500PrincipalUtil using sun.security.x509.X500Name which comes from internal API and leads to mentioned above issue.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months