[JBoss JIRA] (DROOLS-5095) [DMN Designer] Investigate performance switching between editor instances
by Michael Biarnes Kiefer (Jira)
[ https://issues.redhat.com/browse/DROOLS-5095?page=com.atlassian.jira.plug... ]
Michael Biarnes Kiefer updated DROOLS-5095:
-------------------------------------------
Fix Version/s: 7.44.0.Final
(was: 7.43.0.Final)
> [DMN Designer] Investigate performance switching between editor instances
> -------------------------------------------------------------------------
>
> Key: DROOLS-5095
> URL: https://issues.redhat.com/browse/DROOLS-5095
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Affects Versions: 7.33.0.Final
> Reporter: Jozef Marko
> Assignee: Guilherme Gomes
> Priority: Minor
> Labels: drools-tools
> Fix For: 7.44.0.Final
>
> Attachments: switch-dmn.webm
>
>
> This JIRA is to investigate the reported performance issue switching between different DMN Designer instances in Business Central.
> The issue was noticed by [~jomarko] when testing DROOLS-5058 (although the fix therein should have had *zero* affect on switching).
> For more details see the video [^switch-dmn.webm]
> h2. Manual acceptance test
> - Prepare 5 DMN models in project
> - Open all in parallel
> - Try to switch between them, keep all opened
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFLY-13838) plain text j_password appears in the legacy audit log
by Hisanobu Okuda (Jira)
Hisanobu Okuda created WFLY-13838:
-------------------------------------
Summary: plain text j_password appears in the legacy audit log
Key: WFLY-13838
URL: https://issues.redhat.com/browse/WFLY-13838
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 20.0.1.Final
Reporter: Hisanobu Okuda
Assignee: Flavia Rainone
Attachments: web-form-auth.tar.gz
The unmasked value of j_password is written in the audit log as `[parameters=guest::,guest::,]`.
{code}
12:48:45,385 TRACE [org.jboss.security.audit] (default task-1) [Success]principal=guest;request=[/test:cookies=[javax.servlet.http.Cookie@46b3f22]:headers=Origin=http://localhost:8080,Cookie=JSESSIONID=dbDjUA6QeA2UXCyyPaqdSSgE4Kjd0_JvxUG7-pBx.localhost,Accept=text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8,User-Agent=Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0,Connection=keep-alive,Referer=http://localhost:8080/test/secure/index.jsp,Host=localhost:8080,Accept-Encoding=gzip, deflate,DNT=1,Upgrade-Insecure-Requests=1,Accept-Language=en-US,en;q=0.5,Content-Length=33,Content-Type=application/x-www-form-urlencoded,][parameters=guest::,guest::,][attributes=];message=UT000030: User guest successfully authenticated.;Source=org.wildfly.extension.undertow.security.AuditNotificationReceiver;
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFLY-13838) plain text j_password appears in the legacy audit log
by Hisanobu Okuda (Jira)
[ https://issues.redhat.com/browse/WFLY-13838?page=com.atlassian.jira.plugi... ]
Hisanobu Okuda updated WFLY-13838:
----------------------------------
Git Pull Request: https://github.com/wildfly/wildfly/pull/13547
> plain text j_password appears in the legacy audit log
> -----------------------------------------------------
>
> Key: WFLY-13838
> URL: https://issues.redhat.com/browse/WFLY-13838
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 20.0.1.Final
> Reporter: Hisanobu Okuda
> Assignee: Flavia Rainone
> Priority: Major
> Attachments: web-form-auth.tar.gz
>
>
> The unmasked value of j_password is written in the audit log as `[parameters=guest::,guest::,]`.
> {code}
> 12:48:45,385 TRACE [org.jboss.security.audit] (default task-1) [Success]principal=guest;request=[/test:cookies=[javax.servlet.http.Cookie@46b3f22]:headers=Origin=http://localhost:8080,Cookie=JSESSIONID=dbDjUA6QeA2UXCyyPaqdSSgE4Kjd0_JvxUG7-pBx.localhost,Accept=text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8,User-Agent=Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0,Connection=keep-alive,Referer=http://localhost:8080/test/secure/index.jsp,Host=localhost:8080,Accept-Encoding=gzip, deflate,DNT=1,Upgrade-Insecure-Requests=1,Accept-Language=en-US,en;q=0.5,Content-Length=33,Content-Type=application/x-www-form-urlencoded,][parameters=guest::,guest::,][attributes=];message=UT000030: User guest successfully authenticated.;Source=org.wildfly.extension.undertow.security.AuditNotificationReceiver;
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFLY-13838) plain text j_password appears in the legacy audit log
by Hisanobu Okuda (Jira)
[ https://issues.redhat.com/browse/WFLY-13838?page=com.atlassian.jira.plugi... ]
Hisanobu Okuda updated WFLY-13838:
----------------------------------
Attachment: web-form-auth.tar.gz
> plain text j_password appears in the legacy audit log
> -----------------------------------------------------
>
> Key: WFLY-13838
> URL: https://issues.redhat.com/browse/WFLY-13838
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 20.0.1.Final
> Reporter: Hisanobu Okuda
> Assignee: Flavia Rainone
> Priority: Major
> Attachments: web-form-auth.tar.gz
>
>
> The unmasked value of j_password is written in the audit log as `[parameters=guest::,guest::,]`.
> {code}
> 12:48:45,385 TRACE [org.jboss.security.audit] (default task-1) [Success]principal=guest;request=[/test:cookies=[javax.servlet.http.Cookie@46b3f22]:headers=Origin=http://localhost:8080,Cookie=JSESSIONID=dbDjUA6QeA2UXCyyPaqdSSgE4Kjd0_JvxUG7-pBx.localhost,Accept=text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8,User-Agent=Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0,Connection=keep-alive,Referer=http://localhost:8080/test/secure/index.jsp,Host=localhost:8080,Accept-Encoding=gzip, deflate,DNT=1,Upgrade-Insecure-Requests=1,Accept-Language=en-US,en;q=0.5,Content-Length=33,Content-Type=application/x-www-form-urlencoded,][parameters=guest::,guest::,][attributes=];message=UT000030: User guest successfully authenticated.;Source=org.wildfly.extension.undertow.security.AuditNotificationReceiver;
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFLY-13771) Create a Galleon layers for the messaging subsystem
by Brian Stansberry (Jira)
[ https://issues.redhat.com/browse/WFLY-13771?page=com.atlassian.jira.plugi... ]
Brian Stansberry reopened WFLY-13771:
-------------------------------------
> Create a Galleon layers for the messaging subsystem
> ---------------------------------------------------
>
> Key: WFLY-13771
> URL: https://issues.redhat.com/browse/WFLY-13771
> Project: WildFly
> Issue Type: Feature Request
> Components: Build System, JMS
> Reporter: Yeray Borges Santana
> Assignee: Emmanuel Hugonnet
> Priority: Major
> Fix For: 21.0.0.Beta1
>
>
> We have three possible messaging-activemq configuration options that should be supplied via Galleon layers:
> # messaging-activemq subsystem configuration ready to be used as an Embedded broker. This configuration is useful to run quick demos only, it should not be used in production environments or cloud environments.
> # messaging-activemq subsystem configuration ready to be used with an external broker.
> # An empty messaging-activemq subsystem configuration and capabilities to deploy a Resource Adapter file to connect to an external broker. This .rar file has to be deployed by the user.
> The existing jms-activemq layer was meant to allow client-side JMS, it is almost covering the third option, however, the user should be able to deploy .rar files. The analysis document should clarify whether these capabilities should be included in a Galleon layer itself or by contrast, users should add the resource-adapters Galleon layer to provide it.
> Another point to clear up is if the Galleon layers will supply capabilities to invoke remote objects configured in the WildFly JNDI tree, hence the need for remoting naming.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFLY-13837) Investigate JSP (Jakarta EE 9 Platform) TCK failures
by Scott Marlow (Jira)
[ https://issues.redhat.com/browse/WFLY-13837?page=com.atlassian.jira.plugi... ]
Scott Marlow reassigned WFLY-13837:
-----------------------------------
Assignee: Scott Marlow (was: Brian Stansberry)
> Investigate JSP (Jakarta EE 9 Platform) TCK failures
> ----------------------------------------------------
>
> Key: WFLY-13837
> URL: https://issues.redhat.com/browse/WFLY-13837
> Project: WildFly
> Issue Type: Sub-task
> Components: EE
> Reporter: Scott Marlow
> Assignee: Scott Marlow
> Priority: Major
> Labels: EE9
>
> I'm not exactly sure yet where the reference to "DTD Web Application 2.2" is coming from in the follow deployment error that occurring during JSP TCK testing:
> {quote}
> 2020-09-09 16:48:42,512 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "jsp_arrayelresolver_web.war" (runtime-name: "jsp_arrayelresolver_web.war")
> 2020-09-09 16:48:42,625 ERROR [org.jboss.metadata.parser.util.XMLSchemaValidator] (MSC service thread 1-1) Cannot get schema for location: -//Sun Microsystems, Inc.//DTD Web Application 2.2//EN: org.xml.sax.SAXParseException; systemId: file:///mnt/hudson_workspace/customWorkspaceName/wildfly/bin/-//Sun%20Microsystems,%20Inc.//DTD%20Web%20Application%202.2//EN; lineNumber: 81; columnNumber: 3; The markup in the document preceding the root element must be well-formed.
> at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:201)
> at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:175)
> at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:398)
> at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:325)
> at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:282)
> at org.apache.xerces.impl.XMLScanner.reportFatalError(XMLScanner.java:1496)
> at org.apache.xerces.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch(XMLDocumentScannerImpl.java:784)
> at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:324)
> at org.apache.xerces.impl.xs.opti.SchemaParsingConfig.parse(SchemaParsingConfig.java:623)
> at org.apache.xerces.impl.xs.opti.SchemaParsingConfig.parse(SchemaParsingConfig.java:679)
> at org.apache.xerces.impl.xs.opti.SchemaDOMParser.parse(SchemaDOMParser.java:527)
> at org.apache.xerces.impl.xs.traversers.XSDHandler.getSchemaDocument(XSDHandler.java:2168)
> at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(XSDHandler.java:558)
> at org.apache.xerces.impl.xs.XMLSchemaLoader.loadSchema(XMLSchemaLoader.java:580)
> at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:547)
> at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:513)
> at org.apache.xerces.jaxp.validation.XMLSchemaFactory.newSchema(XMLSchemaFactory.java:234)
> at javax.xml.validation.SchemaFactory.newSchema(SchemaFactory.java:638) [rt.jar:1.8.0_191]
> at __redirected.__SchemaFactory.newSchema(__SchemaFactory.java:115) [jboss-modules.jar:1.10.2.Final]
> at org.jboss.metadata.parser.util.XMLSchemaValidator.getSchemaForLocation(XMLSchemaValidator.java:117) [jboss-metadata-common-14.0.0.Alpha1.jar:14.0.0.Alpha1]
> at org.jboss.metadata.parser.util.XMLSchemaValidator.validate(XMLSchemaValidator.java:85) [jboss-metadata-common-14.0.0.Alpha1.jar:14.0.0.Alpha1]
> at org.wildfly.extension.undertow.deployment.WebParsingDeploymentProcessor.deploy(WebParsingDeploymentProcessor.java:117)
> at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:182)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
> at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_191]
> 2020-09-09 16:48:42,631 WARN [org.jboss.metadata.parser.util.XMLSchemaValidator] (MSC service thread 1-1) Cannot get schema for location: -//Sun Microsystems, Inc.//DTD Web Application 2.2//EN
> 2020-09-09 16:48:42,896 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0047: Could not find Extension-List entry ExtensionListEntry [implementationVendorId=com.sun, implementationVersion=1.4, name=tsharness, specificationVersion=1.4, title=tsharness] referenced from ResourceRoot [root="/content/jsp_arrayelresolver_web.war"]
> 2020-09-09 16:48:42,896 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0047: Could not find Extension-List entry ExtensionListEntry [implementationVendorId=com.sun, implementationVersion=1.4, name=cts, specificationVersion=1.4, title=cts] referenced from ResourceRoot [root="/content/jsp_arrayelresolver_web.war"]
> 2020-09-09 16:48:43,243 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "jsp_arrayelresolver_web.war")]) - failure description: {
> "WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.jsp_arrayelresolver_web.jsp_arrayelresolver_web.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"]
> {quote}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFLY-13837) Investigate JSP (Jakarta EE 9 Platform) TCK failures
by Scott Marlow (Jira)
Scott Marlow created WFLY-13837:
-----------------------------------
Summary: Investigate JSP (Jakarta EE 9 Platform) TCK failures
Key: WFLY-13837
URL: https://issues.redhat.com/browse/WFLY-13837
Project: WildFly
Issue Type: Sub-task
Components: EE
Reporter: Scott Marlow
Assignee: Brian Stansberry
I'm not exactly sure yet where the reference to "DTD Web Application 2.2" is coming from in the follow deployment error that occurring during JSP TCK testing:
{quote}
2020-09-09 16:48:42,512 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "jsp_arrayelresolver_web.war" (runtime-name: "jsp_arrayelresolver_web.war")
2020-09-09 16:48:42,625 ERROR [org.jboss.metadata.parser.util.XMLSchemaValidator] (MSC service thread 1-1) Cannot get schema for location: -//Sun Microsystems, Inc.//DTD Web Application 2.2//EN: org.xml.sax.SAXParseException; systemId: file:///mnt/hudson_workspace/customWorkspaceName/wildfly/bin/-//Sun%20Microsystems,%20Inc.//DTD%20Web%20Application%202.2//EN; lineNumber: 81; columnNumber: 3; The markup in the document preceding the root element must be well-formed.
at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:201)
at org.apache.xerces.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:175)
at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:398)
at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:325)
at org.apache.xerces.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:282)
at org.apache.xerces.impl.XMLScanner.reportFatalError(XMLScanner.java:1496)
at org.apache.xerces.impl.XMLDocumentScannerImpl$PrologDispatcher.dispatch(XMLDocumentScannerImpl.java:784)
at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:324)
at org.apache.xerces.impl.xs.opti.SchemaParsingConfig.parse(SchemaParsingConfig.java:623)
at org.apache.xerces.impl.xs.opti.SchemaParsingConfig.parse(SchemaParsingConfig.java:679)
at org.apache.xerces.impl.xs.opti.SchemaDOMParser.parse(SchemaDOMParser.java:527)
at org.apache.xerces.impl.xs.traversers.XSDHandler.getSchemaDocument(XSDHandler.java:2168)
at org.apache.xerces.impl.xs.traversers.XSDHandler.parseSchema(XSDHandler.java:558)
at org.apache.xerces.impl.xs.XMLSchemaLoader.loadSchema(XMLSchemaLoader.java:580)
at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:547)
at org.apache.xerces.impl.xs.XMLSchemaLoader.loadGrammar(XMLSchemaLoader.java:513)
at org.apache.xerces.jaxp.validation.XMLSchemaFactory.newSchema(XMLSchemaFactory.java:234)
at javax.xml.validation.SchemaFactory.newSchema(SchemaFactory.java:638) [rt.jar:1.8.0_191]
at __redirected.__SchemaFactory.newSchema(__SchemaFactory.java:115) [jboss-modules.jar:1.10.2.Final]
at org.jboss.metadata.parser.util.XMLSchemaValidator.getSchemaForLocation(XMLSchemaValidator.java:117) [jboss-metadata-common-14.0.0.Alpha1.jar:14.0.0.Alpha1]
at org.jboss.metadata.parser.util.XMLSchemaValidator.validate(XMLSchemaValidator.java:85) [jboss-metadata-common-14.0.0.Alpha1.jar:14.0.0.Alpha1]
at org.wildfly.extension.undertow.deployment.WebParsingDeploymentProcessor.deploy(WebParsingDeploymentProcessor.java:117)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:182)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701)
at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559)
at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_191]
2020-09-09 16:48:42,631 WARN [org.jboss.metadata.parser.util.XMLSchemaValidator] (MSC service thread 1-1) Cannot get schema for location: -//Sun Microsystems, Inc.//DTD Web Application 2.2//EN
2020-09-09 16:48:42,896 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0047: Could not find Extension-List entry ExtensionListEntry [implementationVendorId=com.sun, implementationVersion=1.4, name=tsharness, specificationVersion=1.4, title=tsharness] referenced from ResourceRoot [root="/content/jsp_arrayelresolver_web.war"]
2020-09-09 16:48:42,896 WARN [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0047: Could not find Extension-List entry ExtensionListEntry [implementationVendorId=com.sun, implementationVersion=1.4, name=cts, specificationVersion=1.4, title=cts] referenced from ResourceRoot [root="/content/jsp_arrayelresolver_web.war"]
2020-09-09 16:48:43,243 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "jsp_arrayelresolver_web.war")]) - failure description: {
"WFLYCTL0412: Required services that are not installed:" => ["jboss.naming.context.java.jboss.DefaultJMSConnectionFactory"],
"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.naming.context.java.module.jsp_arrayelresolver_web.jsp_arrayelresolver_web.DefaultJMSConnectionFactory is missing [jboss.naming.context.java.jboss.DefaultJMSConnectionFactory]"]
{quote}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months
[JBoss JIRA] (WFCORE-5125) Remove the wildfly-openssl-linux-i386 binding
by Farah Juma (Jira)
Farah Juma created WFCORE-5125:
----------------------------------
Summary: Remove the wildfly-openssl-linux-i386 binding
Key: WFCORE-5125
URL: https://issues.redhat.com/browse/WFCORE-5125
Project: WildFly Core
Issue Type: Task
Components: Security
Reporter: Farah Juma
Assignee: Farah Juma
WFCORE-5124 updates WildFly OpenSSL Natives to 2.1.0.Final. The WildFly OpenSSL Natives now require JDK 11 to build. Since there isn't a supported Linux JDK 11 32-bit version, we should now remove the wildfly-openssl-linux-i386 binding. Its removal was already being planned anyway (as per WFCORE-5013).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
4 years, 3 months