September 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-2492) <valid-connection-checker> does not have module attribute

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-2492?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-2492: ----------------------------------------------- tom.jenkinson(a)redhat.com changed the Status of [bug 1029311|https://bugzilla.redhat.com/show_bug.cgi?id=1029311] from NEW to CLOSED > <valid-connection-checker> does not have module attribute > --------------------------------------------------------- > > Key: WFLY-2492 > URL: https://issues.jboss.org/browse/WFLY-2492 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JCA > Affects Versions: 8.0.0.Beta1 > Reporter: James Livingston > Assignee: Stefano Maestri > Priority: Minor > > A datasource's <valid-connection-checker> element lets you specify the class name. It does not let you specify the module name, so you can only use IJ-provided ones. It should let you specify a module name too, so you can use custom connection checkers. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3804) WildFly Multi JSF Feature do not support myfaces 1.2

by roman jablonka (JIRA)

[ https://issues.jboss.org/browse/WFLY-3804?page=com.atlassian.jira.plugin.... ] roman jablonka commented on WFLY-3804: -------------------------------------- I have done alike the discription Steps to add any new JSF implementation or version to WildFly on WildFly 8.1.0 final and test ist with the provided test application there for mojarra-1.2_15 which works as expected myfaces-2.1.14 which works as expected myfaces-1.2.12 which produces exception while deployment, and is marked deployment failed. MyFaces 1.2.12 is an implementation of Faces 1.2, so I would expect, it is working at WildFly. if nessesary, I can provide the slot installation cli and of course the testapplications. > WildFly Multi JSF Feature do not support myfaces 1.2 > ---------------------------------------------------- > > Key: WFLY-3804 > URL: https://issues.jboss.org/browse/WFLY-3804 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Class Loading, JSF > Affects Versions: 8.1.0.Final > Environment: Windows 7 64, Java 8 64 (jdk1.8_11) Myfaces Slot 1.2.12 > Reporter: roman jablonka > Assignee: David Lloyd > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3804) WildFly Multi JSF Feature do not support myfaces 1.2

by roman jablonka (JIRA)

roman jablonka created WFLY-3804: ------------------------------------ Summary: WildFly Multi JSF Feature do not support myfaces 1.2 Key: WFLY-3804 URL: https://issues.jboss.org/browse/WFLY-3804 Project: WildFly Issue Type: Bug Security Level: Public (Everyone can see) Components: Class Loading, JSF Affects Versions: 8.1.0.Final Environment: Windows 7 64, Java 8 64 (jdk1.8_11) Myfaces Slot 1.2.12 Reporter: roman jablonka Assignee: David Lloyd -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBWEB-298) NPE on addFilter in WsServerContainer

by Remy Maucherat (JIRA)

[ https://issues.jboss.org/browse/JBWEB-298?page=com.atlassian.jira.plugin.... ] Remy Maucherat resolved JBWEB-298. ---------------------------------- Fix Version/s: JBossWeb-7.5.0.GA Resolution: Done r2499 in web. > NPE on addFilter in WsServerContainer > ------------------------------------- > > Key: JBWEB-298 > URL: https://issues.jboss.org/browse/JBWEB-298 > Project: JBoss Web > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Tomcat > Reporter: Bartosz Baranowski > Assignee: Remy Maucherat > Priority: Minor > Fix For: JBossWeb-7.5.0.GA > > Attachments: jboss-websocket-hello.war > > > I'm not sure if this is just faulty test/edge case/WFLY/EAP integration failure, but there is case when org.apache.tomcat.websocket.server.WsSci is scheduled and triggered twice. This makes WsServerContainer throw NPE, since servletContext.addFilter[1] return null if filter with specified name exist. > Regardless this case being a valid one or not, WsServerContainer should handle this either with proper message or different exception than NPE. > I'm assigning this to myself for time being( until I can establish if WFLY/EAP being at fault and procure testcase ) > [1] https://source.jboss.org/browse/JBossWeb/branches/7.4.x/src/main/java/org... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3724) Batch jobs don't receive partition-specific parameters

by Enrique González Martínez (JIRA)

[ https://issues.jboss.org/browse/WFLY-3724?page=com.atlassian.jira.plugin.... ] Enrique González Martínez resolved WFLY-3724. --------------------------------------------- Resolution: Won't Fix > Batch jobs don't receive partition-specific parameters > ------------------------------------------------------ > > Key: WFLY-3724 > URL: https://issues.jboss.org/browse/WFLY-3724 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Batch > Affects Versions: 8.1.0.Final > Environment: Windows 7 Home Premium Service Pack 1 64-bit + JDK8u11 + WildFly 8.1.0 Final > Reporter: Ari Silvan > Assignee: Enrique González Martínez > > When defining a batch job chunk step to run as partitions, ItemReader doesn't receive the partition-specific parameters specified by an implementation of the PartitionPlan interface. Parameters are null. See steps to reproduce for further details. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3724) Batch jobs don't receive partition-specific parameters

by Enrique González Martínez (JIRA)

[ https://issues.jboss.org/browse/WFLY-3724?page=com.atlassian.jira.plugin.... ] Enrique González Martínez commented on WFLY-3724: ------------------------------------------------- I close the Jira based on the answer of the expert group. > Batch jobs don't receive partition-specific parameters > ------------------------------------------------------ > > Key: WFLY-3724 > URL: https://issues.jboss.org/browse/WFLY-3724 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Batch > Affects Versions: 8.1.0.Final > Environment: Windows 7 Home Premium Service Pack 1 64-bit + JDK8u11 + WildFly 8.1.0 Final > Reporter: Ari Silvan > Assignee: Enrique González Martínez > > When defining a batch job chunk step to run as partitions, ItemReader doesn't receive the partition-specific parameters specified by an implementation of the PartitionPlan interface. Parameters are null. See steps to reproduce for further details. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1196) Backport SemaphoreConcurrentLinkedQueueManagedConnectionPool

by John O'Hara (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1196?page=com.atlassian.jira.plugin... ] John O'Hara commented on JBJCA-1196: ------------------------------------ PR created for back port to 1.0: https://github.com/ironjacamar/ironjacamar/pull/226 > Backport SemaphoreConcurrentLinkedQueueManagedConnectionPool > ------------------------------------------------------------ > > Key: JBJCA-1196 > URL: https://issues.jboss.org/browse/JBJCA-1196 > Project: IronJacamar > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Core > Reporter: John O'Hara > Assignee: Jesper Pedersen > Fix For: 1.0.28.Final > > > Can we backport the SemaphoreConcurrentLinkedQueueManagedConnectionPool to 1.0 and 1.1 branches. We will need this to be pulled into EAP6.4 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3652) Network connection leak

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-3652?page=com.atlassian.jira.plugin.... ] Stuart Douglas resolved WFLY-3652. ---------------------------------- Fix Version/s: 9.0.0.Beta1 Resolution: Done > Network connection leak > ----------------------- > > Key: WFLY-3652 > URL: https://issues.jboss.org/browse/WFLY-3652 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Undertow) > Affects Versions: 8.1.0.Final > Environment: Linux 2.6.38-16-server > Java(TM) SE Runtime Environment (build 1.7.0_45-b18) > Reporter: Jan Vanhercke > Assignee: Stuart Douglas > Fix For: 9.0.0.Beta1 > > > When using Asynchronous servlets and AsyncListeners for long polling we observe a connection leak in the undertow subsystem. > Heap dumps show a large number of org.xnio.io.NioSocketConduit, io.undertow.server.protocol.http.HttpServerConnection and related objects. > However, since the effective number of connections is far less, nearly all AsyncContext instances we find are in a complete state and lsof output returns a large number of sockets with 'can't identify protocol' entries indicating that sockets are kept open by the JVM but are in fact half closed by the network stack. > Not all connections appear to be leaking, but over time, depending on the load, the server instance fills up. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-586) Drools doesn't calculate maximum expiration time properly

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-586?page=com.atlassian.jira.plugin... ] Edson Tirelli closed DROOLS-586. -------------------------------- > Drools doesn't calculate maximum expiration time properly > --------------------------------------------------------- > > Key: DROOLS-586 > URL: https://issues.jboss.org/browse/DROOLS-586 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.1.0.CR2, 6.2.0.Beta1 > Environment: Linux, Java SE 1.7 > Reporter: kairat kushaev > Assignee: Edson Tirelli > Priority: Critical > Fix For: 6.2.0.Beta2 > > > Hello guys, > we found some contradiction between actual Drools behavior, > We use the following Rule: > import drools.test.Event; > dialect "mvel" > declare Event > @role(event) > @expires(10s) > end > rule "ExampleRule" > when > ( $a : Event(name == "event a") ) and > ( $b : Event((name == "event b") && (this after [1ms, 15s] $a)) ) > then > System.out.println("bingo!"); > end > In the code above Drools should wait for the second event when the first event came. But it turns out that Drools doesn't wait for the second event because of @expires tag. The value in this tag is less than this after value. > According to documentation > "The engine will make this analysis for the whole rulebase and find the offset for every event type. Whenever an implicit expiration offset clashes with the explicit expiration offset, then engine will use the greater of the two." > but it is not calculating maximal expiration offset. Also we are using STREAM mode. > Could you please clarify the situation? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-586) Drools doesn't calculate maximum expiration time properly

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-586?page=com.atlassian.jira.plugin... ] Edson Tirelli resolved DROOLS-586. ---------------------------------- Fix Version/s: 6.2.0.Beta2 Resolution: Done > Drools doesn't calculate maximum expiration time properly > --------------------------------------------------------- > > Key: DROOLS-586 > URL: https://issues.jboss.org/browse/DROOLS-586 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 6.1.0.CR2, 6.2.0.Beta1 > Environment: Linux, Java SE 1.7 > Reporter: kairat kushaev > Assignee: Edson Tirelli > Priority: Critical > Fix For: 6.2.0.Beta2 > > > Hello guys, > we found some contradiction between actual Drools behavior, > We use the following Rule: > import drools.test.Event; > dialect "mvel" > declare Event > @role(event) > @expires(10s) > end > rule "ExampleRule" > when > ( $a : Event(name == "event a") ) and > ( $b : Event((name == "event b") && (this after [1ms, 15s] $a)) ) > then > System.out.println("bingo!"); > end > In the code above Drools should wait for the second event when the first event came. But it turns out that Drools doesn't wait for the second event because of @expires tag. The value in this tag is less than this after value. > According to documentation > "The engine will make this analysis for the whole rulebase and find the offset for every event type. Whenever an implicit expiration offset clashes with the explicit expiration offset, then engine will use the greater of the two." > but it is not calculating maximal expiration offset. Also we are using STREAM mode. > Could you please clarify the situation? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

9 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2014