[JBoss JIRA] (WFLY-11044) Quickstart jaxws-retail illegal access warning with JDK11
by Eduardo Martins (Jira)
[ https://issues.jboss.org/browse/WFLY-11044?page=com.atlassian.jira.plugin... ]
Eduardo Martins commented on WFLY-11044:
----------------------------------------
Once WFLY-11113 is resolved we will sync dependency management with server.
> Quickstart jaxws-retail illegal access warning with JDK11
> ---------------------------------------------------------
>
> Key: WFLY-11044
> URL: https://issues.jboss.org/browse/WFLY-11044
> Project: WildFly
> Issue Type: Bug
> Components: Quickstarts
> Reporter: Jan Blizňák
> Assignee: Eduardo Martins
> Priority: Critical
>
> the `jaxws-retail` quickstart executed on JDK11 as:
> {noformat}
> mvn clean install wildfly:deploy -Dmaven.compiler.target=11 -Dmaven.compiler.source=11 -Dmaven.test.failure.ignore=true
> {noformat}
> now throws:
> {code:java}
> [ERROR] WARNING: An illegal reflective access operation has occurred
> [ERROR] WARNING: Illegal reflective access by com.sun.xml.bind.v2.runtime.reflect.opt.Injector (file:/home/jbliznak/.m2/repository/org/glassfish/jaxb/jaxb-runtime/2.3.0/jaxb-runtime-2.3.0.jar) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)
> [ERROR] WARNING: Please consider reporting this to the maintainers of com.sun.xml.bind.v2.runtime.reflect.opt.Injector
> [ERROR] WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
> [ERROR] WARNING: All illegal access operations will be denied in a future release
> {code}
> The problematic part is in JAXB component. There is a new version of JAXb that is fixing this https://github.com/javaee/jaxb-v2/releases/tag/2.3.1 (comit https://github.com/javaee/jaxb-v2/commit/9805bc91473a9f4dee95e7192998a5bb...) but it is not in maven central yet (https://github.com/javaee/jaxb-v2/issues/1213#issuecomment-422717074).
> The fix for the quickstart is to use either new version of jbossws-cxf-client consuming this new JAXB version or explicit dependency to new JAXB in quickstart itself.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11185) Transaction subsystem should use optional module dependencies for remoting and undertow
by Brian Stansberry (Jira)
Brian Stansberry created WFLY-11185:
---------------------------------------
Summary: Transaction subsystem should use optional module dependencies for remoting and undertow
Key: WFLY-11185
URL: https://issues.jboss.org/browse/WFLY-11185
Project: WildFly
Issue Type: Enhancement
Components: Transactions
Reporter: Brian Stansberry
Assignee: Brian Stansberry
TransactionSubsystemAdd checks whether capabilities are installed before calling any code that requires remoting or undertow. This means the subsystem module's dependencies on remoting and undertow can be optional.
Making these optional will help Galleon to provision smaller servers.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11103) If ServletInputStream.isReady returns false it is illegal to call the ServletInputStream.read method and EAP returns HTTP 200
by Alessio Soldano (Jira)
[ https://issues.jboss.org/browse/WFLY-11103?page=com.atlassian.jira.plugin... ]
Alessio Soldano updated WFLY-11103:
-----------------------------------
Fix Version/s: 15.0.0.Alpha1
> If ServletInputStream.isReady returns false it is illegal to call the ServletInputStream.read method and EAP returns HTTP 200
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-11103
> URL: https://issues.jboss.org/browse/WFLY-11103
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 14.0.1.Final
> Reporter: Adam Krajcik
> Assignee: Romain Pelisse
> Priority: Major
> Fix For: 15.0.0.Alpha1
>
> Attachments: JBEAP-12223.zip
>
>
> EAP returns HTTP 200 instead of 500 when IllegalStateException is thrown if ServletInputStream.isReady returns false.
> This exists in 7.2.0.CD14, it works in 7.2.0.CD13.
> {code}
> Caused by: java.lang.IllegalStateException: UT010035: Stream in async mode was not ready for IO operation
> at io.undertow.servlet.spec.ServletInputStreamImpl.read(ServletInputStreamImpl.java:164)
> at io.undertow.servlet.spec.ServletInputStreamImpl.read(ServletInputStreamImpl.java:154)
> at org.resteasy.simple.deployment.er2.ResourceInfoInjectionResource$1.onDataAvailable(ResourceInfoInjectionResource.java:42)
> at io.undertow.servlet.spec.ServletContextImpl$3.call(ServletContextImpl.java:188)
> at io.undertow.servlet.spec.ServletContextImpl$3.call(ServletContextImpl.java:185)
> at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48)
> at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
> at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
> at io.undertow.servlet.spec.ServletContextImpl.invokeOnDataAvailable(ServletContextImpl.java:1009)
> ... 4 more
> 16:27:16,509 ERROR [org.jboss.resteasy.resteasy_jaxrs.i18n] (default I/O-5) RESTEASY002020: Unhandled asynchronous exception, sending back 500: org.jboss.resteasy.spi.UnhandledException: java.lang.RuntimeException: java.lang.IllegalStateException: UT010035: Stream in async mode was not ready for IO operation
> at org.jboss.resteasy.core.ExceptionHandler.handleException(ExceptionHandler.java:257)
> at org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:197)
> at org.jboss.resteasy.core.SynchronousDispatcher.asynchronousExceptionDelivery(SynchronousDispatcher.java:513)
> at org.jboss.resteasy.core.AbstractAsynchronousResponse.internalResume(AbstractAsynchronousResponse.java:228)
> at org.jboss.resteasy.plugins.server.servlet.Servlet3AsyncHttpRequest$Servlet3ExecutionContext$Servle3AsychronousResponse.resume(Servlet3AsyncHttpRequest.java:118)
> at org.resteasy.simple.deployment.er2.ResourceInfoInjectionResource$1.onError(ResourceInfoInjectionResource.java:61)
> at io.undertow.servlet.spec.ServletInputStreamImpl$ServletInputStreamChannelListener$1.run(ServletInputStreamImpl.java:317)
> at io.undertow.servlet.spec.ServletContextImpl$2.call(ServletContextImpl.java:181)
> at io.undertow.servlet.spec.ServletContextImpl$2.call(ServletContextImpl.java:178)
> at io.undertow.servlet.spec.ServletContextImpl.invokeRunnable(ServletContextImpl.java:1027)
> at io.undertow.servlet.spec.ServletInputStreamImpl$ServletInputStreamChannelListener.handleEvent(ServletInputStreamImpl.java:314)
> at io.undertow.servlet.spec.ServletInputStreamImpl$1$1.run(ServletInputStreamImpl.java:135)
> at org.xnio.nio.WorkerThread.safeRun(WorkerThread.java:612)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:479)
> Caused by: java.lang.RuntimeException: java.lang.IllegalStateException: UT010035: Stream in async mode was not ready for IO operation
> at io.undertow.servlet.spec.ServletContextImpl.invokeOnDataAvailable(ServletContextImpl.java:1011)
> at io.undertow.servlet.spec.ServletInputStreamImpl$ServletInputStreamChannelListener.handleEvent(ServletInputStreamImpl.java:295)
> ... 3 more
> Caused by: java.lang.IllegalStateException: UT010035: Stream in async mode was not ready for IO operation
> at io.undertow.servlet.spec.ServletInputStreamImpl.read(ServletInputStreamImpl.java:164)
> at io.undertow.servlet.spec.ServletInputStreamImpl.read(ServletInputStreamImpl.java:154)
> at org.resteasy.simple.deployment.er2.ResourceInfoInjectionResource$1.onDataAvailable(ResourceInfoInjectionResource.java:42)
> at io.undertow.servlet.spec.ServletContextImpl$3.call(ServletContextImpl.java:188)
> at io.undertow.servlet.spec.ServletContextImpl$3.call(ServletContextImpl.java:185)
> at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:48)
> at io.undertow.servlet.core.ContextClassLoaderSetupAction$1.call(ContextClassLoaderSetupAction.java:43)
> at org.wildfly.extension.undertow.security.SecurityContextThreadSetupAction.lambda$create$0(SecurityContextThreadSetupAction.java:105)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1502)
> at io.undertow.servlet.spec.ServletContextImpl.invokeOnDataAvailable(ServletContextImpl.java:1009)
> ... 4 more
> {code}
> The exception mentions that HTTP 500, should be returned.
> [Comment|https://issues.jboss.org/browse/JBEAP-12223?focusedCommentId=1363...] from [~rpelisse] previous JIRA:
> {quote}Thanks for the step to reproduce, I've also managed to reproduce the behavior. Debugging through the problem, i've established that the code inserted to adress the isssue is still being used, the exception that lead to a 500 error to be returned is no longer being leading to 500 (but a 200).
> If I'm not mistaken, CD13 used Undertow 2.0.9 while CD14 is now using 2.0.13. I'll keep looking tomorrow to which of the few commits introduced in between those versions can have caused the issue.
> {quote}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFCORE-4116) JDK 10: illegal reflective access by ClassReflectionIndex
by James Perkins (Jira)
[ https://issues.jboss.org/browse/WFCORE-4116?page=com.atlassian.jira.plugi... ]
James Perkins reassigned WFCORE-4116:
-------------------------------------
Assignee: James Perkins (was: Jason Greene)
> JDK 10: illegal reflective access by ClassReflectionIndex
> ---------------------------------------------------------
>
> Key: WFCORE-4116
> URL: https://issues.jboss.org/browse/WFCORE-4116
> Project: WildFly Core
> Issue Type: Bug
> Components: Server
> Affects Versions: 6.0.0.Final, 6.0.2.Final
> Reporter: Thorsten Moeller
> Assignee: James Perkins
> Priority: Major
>
> Using WF14 and Oracle JDK 10.0.2, there is an illegal reflective access warning while WF boots:
> {code}
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by org.jboss.as.server.deployment.reflect.ClassReflectionIndex (jar:file:/Users/.../wildfly-14.0.0.Final/modules/system/layers/base/org/jboss/as/server/main/wildfly-server-6.0.1.Final.jar!/) to method java.lang.Object.finalize()
> WARNING: Please consider reporting this to the maintainers of org.jboss.as.server.deployment.reflect.ClassReflectionIndex
> {code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3142) [DMN Designer] Relation: Add additional Properties to drill-down
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3142?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3142:
-----------------------------------
Description:
The Properties Panel currently shows properties for Stunner-level "graph" components.
*Further to DROOLS-2804, that added the generic support for "drill down" and {{ExpressionLanguage}} on {{LiteralExpression}}, this JIRA is to add support for the remaining properties that should be rendered when a component is "drilled down".*
h2. Properties on the Grid Level
The selection on the grid level should show the properties below. Please notice that selection of multiple cells, rows or columns should show empty properties panel.
(everything should have ID, Description properties. Components which inherit from "NamedElement" should also have Name property)
h3. Relation
||Selected item||Properties panel items||type|| ||
|Row|n/a|n/a|n/a|
|Column|type Ref|ItemDefinition ref|(x)|
|Cell|ExpressionLanguage|URI|(x)|
h2. Manual Acceptance Test
- Switching between DRG and Grid editor, check proper fields shown
- Switching between rows, columns, cells in Grid editor, check proper fields
-- In same expression kind
-- Across different expression kinds
- Clear expression kind
- Read only mode - older asset version
- All Grid specific properties saved
was:
The Properties Panel currently shows properties for Stunner-level "graph" components.
*Further to DROOLS-2804, that added the generic support for "drill down" and {{ExpressionLanguage}} on {{LiteralExpression}}, this JIRA is to add support for the remaining properties that should be rendered when a component is "drilled down".*
h2. Properties on the Grid Level
The selection on the grid level should show the properties below. Please notice that selection of multiple cells, rows or columns should show empty properties panel.
(everything should have ID, Description properties. Components which inherit from "NamedElement" should also have Name property)
h3. Relation
||Selected item||Properties panel items||type|| ||
|Row|n/a|n/a|n/a|
|Column|type Ref|ItemDefinition ref|(/)|
|Cell|ExpressionLanguage|URI|(x)|
h2. Manual Acceptance Test
- Switching between DRG and Grid editor, check proper fields shown
- Switching between rows, columns, cells in Grid editor, check proper fields
-- In same expression kind
-- Across different expression kinds
- Clear expression kind
- Read only mode - older asset version
- All Grid specific properties saved
> [DMN Designer] Relation: Add additional Properties to drill-down
> ----------------------------------------------------------------
>
> Key: DROOLS-3142
> URL: https://issues.jboss.org/browse/DROOLS-3142
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
>
> The Properties Panel currently shows properties for Stunner-level "graph" components.
> *Further to DROOLS-2804, that added the generic support for "drill down" and {{ExpressionLanguage}} on {{LiteralExpression}}, this JIRA is to add support for the remaining properties that should be rendered when a component is "drilled down".*
> h2. Properties on the Grid Level
> The selection on the grid level should show the properties below. Please notice that selection of multiple cells, rows or columns should show empty properties panel.
> (everything should have ID, Description properties. Components which inherit from "NamedElement" should also have Name property)
> h3. Relation
> ||Selected item||Properties panel items||type|| ||
> |Row|n/a|n/a|n/a|
> |Column|type Ref|ItemDefinition ref|(x)|
> |Cell|ExpressionLanguage|URI|(x)|
> h2. Manual Acceptance Test
> - Switching between DRG and Grid editor, check proper fields shown
> - Switching between rows, columns, cells in Grid editor, check proper fields
> -- In same expression kind
> -- Across different expression kinds
> - Clear expression kind
> - Read only mode - older asset version
> - All Grid specific properties saved
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (WFLY-11178) WSTrustTestCase failing on IBM
by David Lloyd (Jira)
[ https://issues.jboss.org/browse/WFLY-11178?page=com.atlassian.jira.plugin... ]
David Lloyd commented on WFLY-11178:
------------------------------------
Yes, we substantially changed how JAXP providers are loaded. We should not be using the system properties at all now.
I wonder if the {{javax.xml.validation.SchemaFactory}} system property is being set by the test as a workaround to some problem in the old system? Normally the standard JAXP discovery mechanism should be used.
> WSTrustTestCase failing on IBM
> ------------------------------
>
> Key: WFLY-11178
> URL: https://issues.jboss.org/browse/WFLY-11178
> Project: WildFly
> Issue Type: Bug
> Components: Web Services
> Affects Versions: 14.0.0.Final
> Reporter: Jan Blizňák
> Assignee: Alessio Soldano
> Priority: Major
> Attachments: log.txt
>
>
> As discovered during investigation in WFLY-10336, we are now getting test failures in WSTrustTestCase when IBM JDK is used. The relevant part of the exception is:
> {code:java}
> Caused by: java.lang.IllegalArgumentException: Provider org.apache.xerces.jaxp.validation.XMLSchemaFactory not found
> at javax.xml.validation.SchemaFactory.newInstance(Unknown Source)
> at org.opensaml.core.xml.config.XMLConfigurator.<init>(XMLConfigurator.java:94)
> at org.apache.wss4j.common.saml.OpenSAMLBootstrap.bootstrap(OpenSAMLBootstrap.java:85)
> at org.apache.wss4j.common.saml.OpenSAMLUtil.initSamlEngine(OpenSAMLUtil.java:91)
> at org.apache.wss4j.common.saml.OpenSAMLUtil.initSamlEngine(OpenSAMLUtil.java:75)
> at org.apache.wss4j.common.saml.SamlAssertionWrapper.<init>(SamlAssertionWrapper.java:184)
> at org.apache.cxf.sts.token.provider.SAMLTokenProvider.createSamlToken(SAMLTokenProvider.java:308)
> at org.apache.cxf.sts.token.provider.SAMLTokenProvider.createToken(SAMLTokenProvider.java:120)
> ... 102 more
> {code}
> It turned out the issue is in wildfly for some time, the breaking change was identified as https://github.com/wildfly/wildfly-core/pull/3201/
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3140) [DMN Designer] Function: Add additional Properties to drill-down
by Michael Anstis (Jira)
[ https://issues.jboss.org/browse/DROOLS-3140?page=com.atlassian.jira.plugi... ]
Michael Anstis updated DROOLS-3140:
-----------------------------------
Description:
The Properties Panel currently shows properties for Stunner-level "graph" components.
*Further to DROOLS-2804, that added the generic support for "drill down" and {{ExpressionLanguage}} on {{LiteralExpression}}, this JIRA is to add support for the remaining properties that should be rendered when a component is "drilled down".*
h2. Properties on the Grid Level
The selection on the grid level should show the properties below. Please notice that selection of multiple cells, rows or columns should show empty properties panel.
(everything should have ID, Description properties. Components which inherit from "NamedElement" should also have Name property)
h3. Function
||Selected item||Properties panel items||type|| ||
|Row|n/a|n/a|n/a|
|Column|n/a|n/a|n/a|
|Cell|ExpressionLanguage|URI|(/)|
h2. Manual Acceptance Test
- Switching between DRG and Grid editor, check proper fields shown
- Switching between rows, columns, cells in Grid editor, check proper fields
-- In same expression kind
-- Across different expression kinds
- Clear expression kind
- Read only mode - older asset version
- All Grid specific properties saved
was:
The Properties Panel currently shows properties for Stunner-level "graph" components.
*Further to DROOLS-2804, that added the generic support for "drill down" and {{ExpressionLanguage}} on {{LiteralExpression}}, this JIRA is to add support for the remaining properties that should be rendered when a component is "drilled down".*
h2. Properties on the Grid Level
The selection on the grid level should show the properties below. Please notice that selection of multiple cells, rows or columns should show empty properties panel.
(everything should have ID, Description properties. Components which inherit from "NamedElement" should also have Name property)
h3. Function
||Selected item||Properties panel items||type|| ||
|Row|n/a|n/a|n/a|
|Column|n/a|n/a|n/a|
|Cell|ExpressionLanguage|URI|(x)|
h2. Manual Acceptance Test
- Switching between DRG and Grid editor, check proper fields shown
- Switching between rows, columns, cells in Grid editor, check proper fields
-- In same expression kind
-- Across different expression kinds
- Clear expression kind
- Read only mode - older asset version
- All Grid specific properties saved
> [DMN Designer] Function: Add additional Properties to drill-down
> ----------------------------------------------------------------
>
> Key: DROOLS-3140
> URL: https://issues.jboss.org/browse/DROOLS-3140
> Project: Drools
> Issue Type: Feature Request
> Components: DMN Editor
> Reporter: Michael Anstis
> Assignee: Michael Anstis
> Priority: Critical
> Labels: drools-tools
>
> The Properties Panel currently shows properties for Stunner-level "graph" components.
> *Further to DROOLS-2804, that added the generic support for "drill down" and {{ExpressionLanguage}} on {{LiteralExpression}}, this JIRA is to add support for the remaining properties that should be rendered when a component is "drilled down".*
> h2. Properties on the Grid Level
> The selection on the grid level should show the properties below. Please notice that selection of multiple cells, rows or columns should show empty properties panel.
> (everything should have ID, Description properties. Components which inherit from "NamedElement" should also have Name property)
> h3. Function
> ||Selected item||Properties panel items||type|| ||
> |Row|n/a|n/a|n/a|
> |Column|n/a|n/a|n/a|
> |Cell|ExpressionLanguage|URI|(/)|
> h2. Manual Acceptance Test
> - Switching between DRG and Grid editor, check proper fields shown
> - Switching between rows, columns, cells in Grid editor, check proper fields
> -- In same expression kind
> -- Across different expression kinds
> - Clear expression kind
> - Read only mode - older asset version
> - All Grid specific properties saved
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months