[JBoss JIRA] (WFLY-12295) Deployments fails if de.odysseus.juel is included in the war
by Tomas Hofman (Jira)
[ https://issues.jboss.org/browse/WFLY-12295?page=com.atlassian.jira.plugin... ]
Tomas Hofman moved JBEAP-17205 to WFLY-12295:
---------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-12295 (was: JBEAP-17205)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: JSF
(was: JSF)
Fix Version/s: (was: 7.2.4.GA)
> Deployments fails if de.odysseus.juel is included in the war
> -------------------------------------------------------------
>
> Key: WFLY-12295
> URL: https://issues.jboss.org/browse/WFLY-12295
> Project: WildFly
> Issue Type: Bug
> Components: JSF
> Reporter: Tomas Hofman
> Assignee: Tomas Hofman
> Priority: Major
>
> If the war file contains spring-mvc and de.odysseus.juel in WEB-INF/lib, the deployment fails with the following message. The deployment is successful on EAP7.0.9 and EAP7.1.0, but it fails on EAP7.2.x.
> This behavior breaks backward compatibility between EAP7.1 and EAP7.2.
> {noformat}
> 14:55:59,808 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 73) MSC000001: Failed to start service jboss.deployment.unit."reproduce.war".undertow-deployment: org.jboss.msc.service.StartException in service jboss.deployment.unit."reproduce.war".undertow-deployment: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.NullPointerException
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:81)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> Caused by: java.lang.RuntimeException: java.lang.RuntimeException: java.lang.NullPointerException
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:252)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService.startContext(UndertowDeploymentService.java:96)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$1.run(UndertowDeploymentService.java:78)
> ... 8 more
> Caused by: java.lang.RuntimeException: java.lang.NullPointerException
> at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:315)
> at io.undertow.servlet.core.ApplicationListeners.contextInitialized(ApplicationListeners.java:187)
> at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:216)
> at io.undertow.servlet.core.DeploymentManagerImpl$1.call(DeploymentManagerImpl.java:185)
> at io.undertow.servlet.core.ServletRequestContextThreadSetupAction$1.call(ServletRequestContextThreadSetupAction.java:42)
> 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:1504)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1504)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1504)
> at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService$UndertowThreadSetupAction.lambda$create$0(UndertowDeploymentInfoService.java:1504)
> at io.undertow.servlet.core.DeploymentManagerImpl.deploy(DeploymentManagerImpl.java:250)
> ... 10 more
> Caused by: java.lang.NullPointerException
> at javax.el.CompositeELResolver.add(CompositeELResolver.java:117)
> at com.sun.faces.el.DemuxCompositeELResolver.addRootELResolver(DemuxCompositeELResolver.java:142)
> at com.sun.faces.el.ELUtils.addEL3_0_Resolvers(ELUtils.java:336)
> at com.sun.faces.el.ELUtils.buildFacesResolver(ELUtils.java:258)
> at com.sun.faces.application.ApplicationAssociate.initializeELResolverChains(ApplicationAssociate.java:503)
> at com.sun.faces.application.ApplicationImpl.performOneTimeELInitialization(ApplicationImpl.java:1405)
> at com.sun.faces.application.ApplicationImpl.getELResolver(ApplicationImpl.java:529)
> at javax.faces.application.ApplicationWrapper.getELResolver(ApplicationWrapper.java:621)
> at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:256)
> ... 21 more
> {noformat}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (SWSQE-829) Prepare for Middleware Infra Upgrade
by Filip Brychta (Jira)
[ https://issues.jboss.org/browse/SWSQE-829?page=com.atlassian.jira.plugin.... ]
Filip Brychta commented on SWSQE-829:
-------------------------------------
Filed https://redhat.service-now.com/surl.do?n=PNT0607316
> Prepare for Middleware Infra Upgrade
> ------------------------------------
>
> Key: SWSQE-829
> URL: https://issues.jboss.org/browse/SWSQE-829
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Filip Brychta
> Assignee: Filip Brychta
> Priority: Major
> Labels: infrastructure
>
> There is outage scheduled for MW Lab. We need to prepare plan for that.
> More info:
> Hi,
> You are receiving this email as a stakeholder of the Middleware lab environment which will be impacted by the following lab work.
> We are working on a project to upgrade the old Cisco networking infrastructure in the labs to new Juniper hardware.
> This work will impact all Middleware systems which are in Westford Lab 3. That is, anything with an IP address starting with 10.16.x.x, things with 10.19.x.x addresses will not be impacted.
> A spreadsheet listing the systems including all hardware can be found here: https://docs.google.com/spreadsheets/d/1lSB0cAfX2Jvp0iCJn4gsuArw8mlyqZnG4...
> Note that this may not show all virtual systems.
> The main work will be done in two parts:
> First, we will swap out switches for all the system listed on the "Row E" tab of the spreadsheet. This is scheduled to be done on Monday, August 12th and Tuesday the 13th.
> After that we will swap out switches for everything else listed on "Row D" and "Row C". This is scheduled to be done on Tuesday, August 20th and Wednesday the 21st.
> Please expect the noted systems to be unavailable during these days.
> These dates were scheduled to try to accommodate product releases, though it looks like a couple things were pushed back so it shouldn't be a problem.
> In preparation for this we will also need to migrate the routing instance for all the affected networks. This will be a much shorter maintenance, no more than an hour should be needed.
> I was advised that this should just be done outside of BRQ working hours, so will probably be done on a Friday evening or over the weekend. I will update when we have a solid timeframe for that.
> Additionally, there are a few systems that will need to get moved to the middleware network, and some things which should be physically moved. I will send a separate email to people regarding those.
> Most things, however, will not be getting new addresses and will simply be inaccessible for the duration of the work.
> Following each maintenance window the systems should be back online and otherwise unaffected. However, if you do encounter any problems please feel free to respond directly to this email.
> If you experience issues outside of business hours please refer to the escalation procedures found here: https://mojo.redhat.com/docs/DOC-1049381
> Let me know if you have any questions.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (WFLY-7418) Batch deployments with a large number of executed jobs can lock up or slow down the web console
by Timon Zilles (Jira)
[ https://issues.jboss.org/browse/WFLY-7418?page=com.atlassian.jira.plugin.... ]
Timon Zilles commented on WFLY-7418:
------------------------------------
Is there any progress regarding this issue?
In our case we have the problem, that the database selects lead to a timeout during the load of MBeans in JConsole or Hawtio. When we try to connect to JMX the database process has a CPU usage of about 100%, the application therefore slows down and the connection at the end fails because of the timeout, respectively the blocked threads.
With about ~3400 job executions and ~3400 job instances we have approximately 28.000 database selection. On our test environment we have ~160.000 job executions, which leads to the fact that we cannot access the MBeans.
We also tried to remove the MBeans from WildFly, but this is forbidden.
Is there any possibility to prevent the load of the data? We do not need them in the MBean - but in the application, so we cannot simply delete them.
> Batch deployments with a large number of executed jobs can lock up or slow down the web console
> -----------------------------------------------------------------------------------------------
>
> Key: WFLY-7418
> URL: https://issues.jboss.org/browse/WFLY-7418
> Project: WildFly
> Issue Type: Enhancement
> Components: Batch, Web Console
> Reporter: James Perkins
> Assignee: James Perkins
> Priority: Major
> Labels: move_to_halnext
>
> Batch deployments which contain a large number of executed jobs can be extremely slow to process as the {{/deployment=batch.war/subsystem=batch-jberet}} processes each job instance then each job execution of that job instance.
> One possibly helpful option for the web console would be to add a new description attribute to indicate the resource may be slow to process. The web console might be able to run a background task to populate data rather than locking up the UI. There would still be an issue with a large memory footprint here however.
> JBeret might want to consider having a way to archive jobs too rather than just purge them. Some users may want to keep all job execution data. Archiving this data could reduce the size of the current data being retrieved.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (DROOLS-4331) Error when copying Guided Rule with Bigdecimal
by Toni Rikkola (Jira)
[ https://issues.jboss.org/browse/DROOLS-4331?page=com.atlassian.jira.plugi... ]
Toni Rikkola moved RHPAM-2268 to DROOLS-4331:
---------------------------------------------
Project: Drools (was: Red Hat Process Automation Manager)
Key: DROOLS-4331 (was: RHPAM-2268)
Workflow: GIT Pull Request workflow (was: CDW with docs v1)
Docs QE Status: NEW
Component/s: Guided Rule Editor
(was: Business Central)
Affects Version/s: (was: 7.3.1.GA)
QE Status: NEW
> Error when copying Guided Rule with Bigdecimal
> ----------------------------------------------
>
> Key: DROOLS-4331
> URL: https://issues.jboss.org/browse/DROOLS-4331
> Project: Drools
> Issue Type: Bug
> Components: Guided Rule Editor
> Environment: RHPAM 7.3
> Reporter: Karina Varela
> Assignee: Toni Rikkola
> Priority: Critical
> Labels: drools-tools, support
>
> When copying a guided rule that contains a BigDecimal field, it adds another letter "B" in the drools file.
> Initial file:
> package com.myspace.reproducer_02415008;
> import java.lang.Number;
> rule "GuidedRule"
> dialect "mvel"
> when
> DataObject( field == 0.0B )
> then
> end
> --------
> Copied file source result code. Note the two B's :
> package com.myspace.reproducer_02415008;
> import java.lang.Number;
> rule "teste"
> dialect "mvel"
> when
> DataObject( field == 0.0BB )
> then
> end
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (WFLY-11617) Validation not working for pooled-connection-factory's transaction attribute.
by Martin Stefanko (Jira)
[ https://issues.jboss.org/browse/WFLY-11617?page=com.atlassian.jira.plugin... ]
Martin Stefanko updated WFLY-11617:
-----------------------------------
Labels: downstream_dependency (was: )
> Validation not working for pooled-connection-factory's transaction attribute.
> ------------------------------------------------------------------------------
>
> Key: WFLY-11617
> URL: https://issues.jboss.org/browse/WFLY-11617
> Project: WildFly
> Issue Type: Bug
> Components: JMS, Transactions
> Affects Versions: 15.0.1.Final
> Reporter: Varsha Kamble
> Assignee: Chao Wang
> Priority: Minor
> Labels: downstream_dependency
> Fix For: 16.0.0.Final
>
>
> Validation not working for pooled-connection-factory's "transaction" attribute. According to xsd, it should accept only xa, local and none. However it is accepting anything.
> [standalone@localhost:9990 /] /subsystem=messaging-activemq/server=default/pooled-connection-factory=activemq-ra:write-attribute(name=transaction,value=jjj)
> {
> "outcome" => "success",
> "response-headers" => {
> "operation-requires-reload" => true,
> "process-state" => "reload-required"
> }
> }
> [standalone@localhost:9990 /] :relaod
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (DROOLS-3953) DMN UX - overlay validation error reporting
by Elizabeth Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3953?page=com.atlassian.jira.plugi... ]
Elizabeth Clayton commented on DROOLS-3953:
-------------------------------------------
[~danielezonca] Okay thanks. When you are ready to look at it, it would be good to fold in [~bdellasc] to see if we can enhance the visual presentation to make sure the final solution is accessible to all users.
> DMN UX - overlay validation error reporting
> -------------------------------------------
>
> Key: DROOLS-3953
> URL: https://issues.jboss.org/browse/DROOLS-3953
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Elizabeth Clayton
> Assignee: Tao Zhu
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam, drools-tools
> Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run-popup.png, Error reporting after test run.png, ut.png, ux-decision button.png, ux-decision table.png
>
>
> As user during DMN model editing, I want to see validation errors on the model in case of wrong FEEL expression or invalid decision table.
> I want to see this kind of errors in the decisions and at diagram level.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years