[JBoss JIRA] (WFLY-9811) Serve gzip encoded resources
by Flavia Rainone (Jira)
[ https://issues.jboss.org/browse/WFLY-9811?page=com.atlassian.jira.plugin.... ]
Flavia Rainone updated WFLY-9811:
---------------------------------
Labels: hal (was: )
> Serve gzip encoded resources
> ----------------------------
>
> Key: WFLY-9811
> URL: https://issues.jboss.org/browse/WFLY-9811
> Project: WildFly
> Issue Type: Feature Request
> Components: Web (Undertow)
> Reporter: Stuart Douglas
> Assignee: Flavia Rainone
> Priority: Major
> Labels: hal
>
> Generally you want two things to happen:
> # serve files using #sendfile
> # serve gzipped versions resources
> Compressing resources in memory saves bandwidth but is suboptimal since the whole resource needs to be loaded into memory.
> Jetty implements this like this:
> - if the Accept-Encoding includes "gzip"
> - and there is a ".gz" version of the file (eg. you request "style.css" and there is "style.css.gz")
> then the ".gz" version is served.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (WFLY-12458) WebServices tests failing in IBM JDK8
by Richard Opalka (Jira)
Richard Opalka created WFLY-12458:
-------------------------------------
Summary: WebServices tests failing in IBM JDK8
Key: WFLY-12458
URL: https://issues.jboss.org/browse/WFLY-12458
Project: WildFly
Issue Type: Bug
Components: Web Services
Environment: java version "1.8.0_211"
Java(TM) SE Runtime Environment (build 8.0.5.36 - pxa6480sr5fp36-20190510_01(SR5 FP36))
IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20190502_415899 (JIT enabled, AOT enabled)
OpenJ9 - 46e57f9
OMR - 06a046a
IBM - 0b909bf)
JCL - 20190409_01 based on Oracle jdk8u211-b25
Reporter: Richard Opalka
Assignee: Jim Ma
Fix For: 18.0.0.Beta1
[ERROR] EJBSignTestCase.signedRequest:86 » SOAPFault MustUnderstand headers: [{http://...
[ERROR] SignTestCase.signedRequest:88 » SOAPFault MustUnderstand headers: [{http://doc...
[ERROR] EJBSignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromAlice:90 » SOAPFault
[ERROR] EJBSignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromJohn:102 » SOAPFault
[ERROR] EJBSignEncryptTestCase.encryptedAndSignedRequest:88 » SOAPFault MustUnderstand...
[ERROR] SignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromAlice:91 » SOAPFault
[ERROR] SignEncryptMultipleClientsTestCase.encryptedAndSignedRequestFromJohn:103 » SOAPFault
[ERROR] SignEncryptTestCase.encryptedAndSignedRequest:90 » SOAPFault MustUnderstand he...
[ERROR] WSBearerElytronSecurityPropagationTestCase.testBearer:133 » SOAPFault MustUnde...
[ERROR] WSBearerSecurityPropagationTestCase.testBearer:133 » SOAPFault MustUnderstand ...
[ERROR] WSTrustTestCase.test:319 » SOAPFault MustUnderstand headers: [{http://docs.oas...
[ERROR] WSTrustTestCase.testActAs:442 » SOAPFault MustUnderstand headers: [{http://doc...
[ERROR] WSTrustTestCase.testBearer:553 » SOAPFault MustUnderstand headers: [{http://do...
[ERROR] WSTrustTestCase.testHolderOfKey:494 » SOAPFault MustUnderstand headers: [{http...
[ERROR] WSTrustTestCase.testNoClientCallback:384 » SOAPFault MustUnderstand headers: [...
[ERROR] WSTrustTestCase.testNoSignatureUsername:415 » SOAPFault MustUnderstand headers...
[ERROR] WSTrustTestCase.testOnBehalfOf:469 » SOAPFault MustUnderstand headers: [{http:...
[ERROR] WSTrustTestCase.testPicketLink:526 » SOAPFault MustUnderstand headers: [{http:...
[ERROR] WSTrustTestCase.testUsingEPR:351 » SOAPFault MustUnderstand headers: [{http://...
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (WFLY-12457) Single action timer is not triggered automatically after a DB outage, requires server restart
by Enrique González Martínez (Jira)
[ https://issues.jboss.org/browse/WFLY-12457?page=com.atlassian.jira.plugin... ]
Enrique González Martínez commented on WFLY-12457:
--------------------------------------------------
When the ejb timers datastore is not accesible and a timer is in timeout it causes an inconsistency. first the timer is never retried, and in memory is in a end state.
> Single action timer is not triggered automatically after a DB outage, requires server restart
> ---------------------------------------------------------------------------------------------
>
> Key: WFLY-12457
> URL: https://issues.jboss.org/browse/WFLY-12457
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: Enrique González Martínez
> Assignee: Cheng Fang
> Priority: Major
>
> A timer is created with the {{timerService.createSingleActionTimer(..)}} method. When the database is down at the time this timer expires, the timer execution fails with the following ERROR:
> {noformat}
> 09:01:32,968 ERROR [org.jboss.as.ejb3.timer] (EJB timer-thread-pool - 4) WFLYEJB0502: Exception checking if timer [id=7ac2a79a-daa8-46fb-afa1-9e72f39a5b01 timedObjectId=ejb-timer-db-outage.ejb-timer-db-outage.TimeoutExample auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@7071c87c initialExpiration=Fri Aug 09 09:01:32 MDT 2019 intervalDuration(in milli sec)=0 nextExpiration=Fri Aug 09 09:01:32 MDT 2019 timerState=ACTIVE info=timer_1565362882955_10000] should run: java.sql.SQLException: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:jboss/datasources/ejb_timer
> at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:159)
> at org.jboss.as.connector.subsystems.datasources.WildFlyDataSource.getConnection(WildFlyDataSource.java:64)
> at org.jboss.as.ejb3.timerservice.persistence.database.DatabaseTimerPersistence.shouldRun(DatabaseTimerPersistence.java:405)
> at org.jboss.as.ejb3.timerservice.TimerServiceImpl.shouldRun(TimerServiceImpl.java:1148)
> at org.jboss.as.ejb3.timerservice.TimerTask.run(TimerTask.java:133)
> at org.jboss.as.ejb3.timerservice.TimerServiceImpl$Task$1.run(TimerServiceImpl.java:1304)
> at org.wildfly.extension.requestcontroller.RequestController$QueuedTask$1.run(RequestController.java:494)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> Caused by: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:jboss/datasources/ejb_timer
> at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:690)
> at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:440)
> at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:789)
> at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:151)
> ... 10 more
> {noformat}
> EXPECTATION: The timer should fire once the DB is accessible again.
> RESULT: The timer is not executed even after the DB connection has been restored.
> After a server restart, the timer is executed again.
> Note: This issue has originally been reported in the context of RHPAM as RHPAM-2180 where processes with timers get stuck after a DB outage. The relevant [jBPM code|https://github.com/kiegroup/jbpm/blob/master/jbpm-services/jbpm-serv...] calls {{timerService.createSingleActionTimer(..)}}.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months
[JBoss JIRA] (WFLY-12457) Single action timer is not triggered automatically after a DB outage, requires server restart
by Enrique González Martínez (Jira)
[ https://issues.jboss.org/browse/WFLY-12457?page=com.atlassian.jira.plugin... ]
Enrique González Martínez moved JBEAP-17514 to WFLY-12457:
----------------------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-12457 (was: JBEAP-17514)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: EJB
(was: EJB)
Affects Version/s: (was: 7.2.2.GA)
> Single action timer is not triggered automatically after a DB outage, requires server restart
> ---------------------------------------------------------------------------------------------
>
> Key: WFLY-12457
> URL: https://issues.jboss.org/browse/WFLY-12457
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Reporter: Enrique González Martínez
> Assignee: Cheng Fang
> Priority: Major
>
> A timer is created with the {{timerService.createSingleActionTimer(..)}} method. When the database is down at the time this timer expires, the timer execution fails with the following ERROR:
> {noformat}
> 09:01:32,968 ERROR [org.jboss.as.ejb3.timer] (EJB timer-thread-pool - 4) WFLYEJB0502: Exception checking if timer [id=7ac2a79a-daa8-46fb-afa1-9e72f39a5b01 timedObjectId=ejb-timer-db-outage.ejb-timer-db-outage.TimeoutExample auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@7071c87c initialExpiration=Fri Aug 09 09:01:32 MDT 2019 intervalDuration(in milli sec)=0 nextExpiration=Fri Aug 09 09:01:32 MDT 2019 timerState=ACTIVE info=timer_1565362882955_10000] should run: java.sql.SQLException: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:jboss/datasources/ejb_timer
> at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:159)
> at org.jboss.as.connector.subsystems.datasources.WildFlyDataSource.getConnection(WildFlyDataSource.java:64)
> at org.jboss.as.ejb3.timerservice.persistence.database.DatabaseTimerPersistence.shouldRun(DatabaseTimerPersistence.java:405)
> at org.jboss.as.ejb3.timerservice.TimerServiceImpl.shouldRun(TimerServiceImpl.java:1148)
> at org.jboss.as.ejb3.timerservice.TimerTask.run(TimerTask.java:133)
> at org.jboss.as.ejb3.timerservice.TimerServiceImpl$Task$1.run(TimerServiceImpl.java:1304)
> at org.wildfly.extension.requestcontroller.RequestController$QueuedTask$1.run(RequestController.java:494)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> at org.jboss.threads.JBossThread.run(JBossThread.java:485)
> Caused by: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:jboss/datasources/ejb_timer
> at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:690)
> at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:440)
> at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:789)
> at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:151)
> ... 10 more
> {noformat}
> EXPECTATION: The timer should fire once the DB is accessible again.
> RESULT: The timer is not executed even after the DB connection has been restored.
> After a server restart, the timer is executed again.
> Note: This issue has originally been reported in the context of RHPAM as RHPAM-2180 where processes with timers get stuck after a DB outage. The relevant [jBPM code|https://github.com/kiegroup/jbpm/blob/master/jbpm-services/jbpm-serv...] calls {{timerService.createSingleActionTimer(..)}}.
--
This message was sent by Atlassian Jira
(v7.13.5#713005)
6 years, 10 months