December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4430) Remove transport from DWM

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4430?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4430. ---------------------------- > Remove transport from DWM > ------------------------- > > Key: WFLY-4430 > URL: https://issues.jboss.org/browse/WFLY-4430 > Project: WildFly > Issue Type: Task > Components: JCA > Reporter: Jesper Pedersen > Assignee: Jesper Pedersen > Priority: Blocker > Fix For: 10.0.0.Beta1 > > > Remove 'transport' and 'transportType' from DWM. Use the unique name of the DWM for channel name -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5195) Persistent timers sometimes remain IN_TIMEOUT in database and don't ever activate again

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5195?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5195. ---------------------------- > Persistent timers sometimes remain IN_TIMEOUT in database and don't ever activate again > --------------------------------------------------------------------------------------- > > Key: WFLY-5195 > URL: https://issues.jboss.org/browse/WFLY-5195 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 10.0.0.Beta2 > Reporter: Jan Martiska > Assignee: Stuart Douglas > Fix For: 10.0.0.CR1 > > Attachments: in-timeout-reproducer.zip > > > The scenario: > A persistent timer goes off right before its application gets undeployed > {noformat} > &amp#27;[0m&amp#27;[32m08:43:38,086 DEBUG [org.jboss.as.ejb3] (EJB default - 1) Timer task invoked at: Tue Aug 25 08:43:38 CEST 2015 for timer [id=d563c5b3-c98c-44c9-87f6-04a492280a67 timedObjectId=testTimerServiceSerialization.a.TimerServiceSerializationBean auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@43ca0624 initialExpiration=Tue Aug 25 08:43:35 CEST 2015 intervalDuration(in milli sec)=100 nextExpiration=Tue Aug 25 08:43:38 CEST 2015 timerState=ACTIVE info=org.jboss.as.test.integration.ejb.timerservice.serialization.InfoA@1ce85ecb] > {noformat} > The timer changes its state to IN_TIMEOUT and persists this into the database. > It fails to invoke the bean method, because the application is no longer available > {noformat} > &amp#27;[0m&amp#27;[31m08:43:38,515 ERROR [org.jboss.as.ejb3] (EJB default - 1) WFLYEJB0020: Error invoking timeout for timer: [id=d563c5b3-c98c-44c9-87f6-04a492280a67 timedObjectId=testTimerServiceSerialization.a.TimerServiceSerializationBean auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@43ca0624 initialExpiration=Tue Aug 25 08:43:35 CEST 2015 intervalDuration(in milli sec)=100 nextExpiration=Tue Aug 25 08:43:38 CEST 2015 timerState=IN_TIMEOUT info=org.jboss.as.test.integration.ejb.timerservice.serialization.InfoA@1ce85ecb]: java.lang.IllegalStateException > at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47) > at org.jboss.as.ejb3.timerservice.TimerServiceImpl.getInvoker(TimerServiceImpl.java:564) > at org.jboss.as.ejb3.timerservice.TimerTask.invokeBeanMethod(TimerTask.java:188) > at org.jboss.as.ejb3.timerservice.TimerTask.callTimeout(TimerTask.java:184) > at org.jboss.as.ejb3.timerservice.TimerTask.run(TimerTask.java:157) > at org.jboss.as.ejb3.timerservice.TimerServiceImpl$Task$1.run(TimerServiceImpl.java:1224) > at org.wildfly.extension.requestcontroller.RequestController$QueuedTask$1.run(RequestController.java:497) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > at org.jboss.threads.JBossThread.run(JBossThread.java:320) > {noformat} > It considers retrying, but then it doesn't retry, because the state is IN_TIMEOUT > {noformat} > 08:43:38,515 INFO [org.jboss.as.ejb3] (EJB default - 1) WFLYEJB0021: Timer: [id=d563c5b3-c98c-44c9-87f6-04a492280a67 timedObjectId=testTimerServiceSerialization.a.TimerServiceSerializationBean auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@43ca0624 initialExpiration=Tue Aug 25 08:43:35 CEST 2015 intervalDuration(in milli sec)=100 nextExpiration=Tue Aug 25 08:43:38 CEST 2015 timerState=IN_TIMEOUT info=org.jboss.as.test.integration.ejb.timerservice.serialization.InfoA@1ce85ecb] will be retried > 08:43:38,515 INFO [org.jboss.as.ejb3] (EJB default - 1) WFLYEJB0024: Timer is not active, skipping retry of timer: [id=d563c5b3-c98c-44c9-87f6-04a492280a67 timedObjectId=testTimerServiceSerialization.a.TimerServiceSerializationBean auto-timer?:false persistent?:true timerService=org.jboss.as.ejb3.timerservice.TimerServiceImpl@43ca0624 initialExpiration=Tue Aug 25 08:43:35 CEST 2015 intervalDuration(in milli sec)=100 nextExpiration=Tue Aug 25 08:43:38 CEST 2015 timerState=IN_TIMEOUT info=org.jboss.as.test.integration.ejb.timerservice.serialization.InfoA@1ce85ecb] > {noformat} > It gives up and tries to persist the state back to ACTIVE, but it fails, because the DatabaseTimerPersistence service is no longer available > {noformat} > 08:43:38,516 WARN [org.jboss.as.ejb3] (EJB default - 1) WFLYEJB0016: Timer persistence is not enabled, persistent timers will not survive JVM restarts > {noformat} > So the state remains IN_TIMEOUT in the database. When the application is redeployed, it is initialized with this state and it never goes off again. > This happens with a JDBC storage in a database that is slow enough so that the update of state to IN_TIMEOUT proceeds correctly, but the actual bean method invocation fails already. > Attaching a reproducer which simulates a slow database using Byteman, so it can be run even with the ExampleDS. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5033) Upgrade Infinispan to 8.0

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5033?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5033. ---------------------------- > Upgrade Infinispan to 8.0 > ------------------------- > > Key: WFLY-5033 > URL: https://issues.jboss.org/browse/WFLY-5033 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 10.0.0.Alpha6 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 10.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4901) Fix or @Ignore org.jboss.as.test.integration.ws.wsse.signencrypt.EJBSignEncryptTestCase.encryptedAndSignedRequest

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4901?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4901. ---------------------------- > Fix or @Ignore org.jboss.as.test.integration.ws.wsse.signencrypt.EJBSignEncryptTestCase.encryptedAndSignedRequest > ----------------------------------------------------------------------------------------------------------------- > > Key: WFLY-4901 > URL: https://issues.jboss.org/browse/WFLY-4901 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Reporter: Rostislav Svoboda > Assignee: Alessio Soldano > Fix For: 10.0.0.Beta2 > > > Brian Stansberry @here who is going to fix or @Ignore org.jboss.as.test.integration.ws.wsse.signencrypt.EJBSignEncryptTestCase.encryptedAndSignedRequest ? > Stuart Douglas I am pretty sure it is a web services issue > Stuart Douglas these failures started happening after a WS upgrade a while back > David M. Lloyd @RostislavSvoboda added it -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4863) Journal file size configuration attribute changed

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4863?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4863. ---------------------------- > Journal file size configuration attribute changed > ------------------------------------------------- > > Key: WFLY-4863 > URL: https://issues.jboss.org/browse/WFLY-4863 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 10.0.0.Alpha5 > > > Attribute journal file-size is set to 102400 bytes in messaging subsystem (in Wildfly 9 with ActiveMQ). This attribute was not set in EAP 6.x and its default value was 10Mb. Current value 102400 bytes causes warnings if message of specific size is sent to server as it is the same value of the connection-factory's min-large-message-size -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4653) Weld thread pool should be wildfly global

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4653?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4653. ---------------------------- > Weld thread pool should be wildfly global > ----------------------------------------- > > Key: WFLY-4653 > URL: https://issues.jboss.org/browse/WFLY-4653 > Project: WildFly > Issue Type: Enhancement > Components: CDI / Weld > Affects Versions: 9.0.0.CR1 > Reporter: Sebastian Maurer > Assignee: Jozef Hartinger > Fix For: 10.0.0.Alpha3 > > > Weld keeps a thread pool for each deployment. > Per default the pool is filled with "numProcessors" threads (see http://docs.jboss.org/weld/reference/latest/en-US/html/configure.html) > When having many deployments, a single thread pool for the wildfly instance could improve the overall performance. > This thread pool should be configurable in the weld subsystem of the wildfly configuration (e.g. standalone.xml). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5064) Upgrade HAL to 2.8.5

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5064?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5064. ---------------------------- > Upgrade HAL to 2.8.5 > -------------------- > > Key: WFLY-5064 > URL: https://issues.jboss.org/browse/WFLY-5064 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Fix For: 10.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5161) Can't set attributes of element transport-config in CLI

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5161?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5161. ---------------------------- > Can't set attributes of element transport-config in CLI > ------------------------------------------------------- > > Key: WFLY-5161 > URL: https://issues.jboss.org/browse/WFLY-5161 > Project: WildFly > Issue Type: Bug > Components: IIOP > Affects Versions: 10.0.0.Beta1 > Reporter: Ondra Chaloupka > Assignee: Tomasz Adamski > Fix For: 10.0.0.CR1 > > > It's not possible to set attributes of element {{transport-config}} in CLI. > When I run {{:read-resource()}} I get > {code} > /subsystem=iiop-openjdk:read-resource() > { > "outcome" => "success", > "result" => { > "add-component-via-interceptor" => true, > "auth-method" => "username_password", > "caller-propagation" => "none", > "client-requires" => "None", > "client-supports" => "ServerAuth", > "confidentiality" => "none", > "detect-misordering" => "none", > "detect-replay" => "none", > "export-corbaloc" => true, > "giop-version" => "1.2", > "high-water-mark" => undefined, > "integrity" => "required", > "number-to-reclaim" => undefined, > "persistent-server-id" => "1", > "properties" => undefined, > "realm" => undefined, > "required" => false, > "root-context" => "JBoss/Naming/root", > "security" => "identity", > "security-domain" => undefined, > "server-requires" => "None", > "server-supports" => "MutualAuth", > "socket-binding" => "iiop", > "ssl-socket-binding" => "iiop-ssl", > "support-ssl" => false, > "transactions" => "spec", > "trust-in-client" => "none", > "trust-in-target" => "none" > } > } > {code} > but XML can contain two emelents > {code} > <client-transport integrity="supported" confidentiality="supported" trust-in-target="supported" trust-in-client="supported" detect-replay="supported" detect-misordering="supported" /> > <transport-config integrity="supported" confidentiality="supported" trust-in-target="supported" trust-in-client="supported" detect-replay="supported" detect-misordering="supported" /> > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4969) Update JSF based on Mojarra 2.2.12

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4969?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4969. ---------------------------- > Update JSF based on Mojarra 2.2.12 > ---------------------------------- > > Key: WFLY-4969 > URL: https://issues.jboss.org/browse/WFLY-4969 > Project: WildFly > Issue Type: Component Upgrade > Components: JSF > Reporter: Farah Juma > Assignee: Farah Juma > Fix For: 9.0.2.Final, 10.0.0.Beta1 > > > Update JSF since Mojarra 2.2.12 was just released. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-5215) [Migration operation] [Web to Undertow] Scheme attribute of ajp connector is not migrated

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5215?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5215. ---------------------------- > [Migration operation] [Web to Undertow] Scheme attribute of ajp connector is not migrated > ----------------------------------------------------------------------------------------- > > Key: WFLY-5215 > URL: https://issues.jboss.org/browse/WFLY-5215 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Beta2 > Reporter: Radim Hatlapatka > Assignee: Stuart Douglas > Fix For: 10.0.0.CR1 > > > Scheme attribute of AJP connector is not migrated. > Web AJP configuration > {noformat} > <connector name="ajp" protocol="AJP/1.3" scheme="http" socket-binding="ajp"/> > {noformat} > should be migrated to > {noformat} > <ajp-listener name="ajp" socket-binding="ajp" scheme="http"/> > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 1 month

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2017