[JBoss JIRA] (WFLY-6422) ejb3 subsystem thread-pools default config & xsd misleading
by Brad Maxwell (JIRA)
Brad Maxwell created WFLY-6422:
----------------------------------
Summary: ejb3 subsystem thread-pools default config & xsd misleading
Key: WFLY-6422
URL: https://issues.jboss.org/browse/WFLY-6422
Project: WildFly
Issue Type: Bug
Components: EJB
Affects Versions: 10.0.0.Final
Reporter: Brad Maxwell
keepalive-time should be removed from the default profile configurations standalone*.xml / domain.xml as well as the ejb3 docs/schema xsd as the thread pool effectively takes the max-threads count and sets the core size of the thread pool to it, so keepalive-time is never used. Also, max-threads is misleading, the thread count is actually the core size as currently implemented, this causes confusion as if you set max-threads to 300 and you have at most 1 client, your thread pool will create a new thread upon ever request until it reaches 300 and thus while it is technically the max, it is also the core or min, or just # of threads.
{code}
<thread-pools>
<thread-pool name="default">
<max-threads count="10"/>
<keepalive-time time="100" unit="milliseconds"/>
</thread-pool>
</thread-pools>
{code}
{code}
A thread pool executor with an unbounded queue. Such a thread pool has a core size and a queue with no
upper bound. When a task is submitted, if the number of running threads is less than the core size,
a new thread is created. Otherwise, the task is placed in queue. If too many tasks are allowed to be
submitted to this type of executor, an out of memory condition may occur.
The "name" attribute is the name of the created executor.
The "max-threads" attribute must be used to specify the thread pool size. The nested
"keepalive-time" element may used to specify the amount of time that pool threads should
be kept running when idle; if not specified, threads will run until the executor is shut down.
The "thread-factory" element specifies the bean name of a specific threads subsystem thread factory to
use to create worker threads. Usually it will not be set for an EJB3 thread pool and an appropriate
default thread factory will be used.
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6420) 30secs delay on consumer.receive() in spite of shorter timeout
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/WFLY-6420?page=com.atlassian.jira.plugin.... ]
Jeff Mesnil resolved WFLY-6420.
-------------------------------
Fix Version/s: 10.1.0.Final
Resolution: Cannot Reproduce Bug
I can not reproduce with laster WildFly master branch. Your test works as expected and there is no delay:
{noformat}
17:04:44,455 INFO [ArtemisHornetQClientTest] [ 109]: Starting to send/receive using Artemis client API
17:04:44,592 INFO [ArtemisHornetQClientTest] [ 246]: * * * Sent a message 'foobar-0' to 'ActiveMQQueue[DLQ]'
17:04:44,596 INFO [ArtemisHornetQClientTest] [ 249]: * * * Sent a message 'foobar-1' to 'ActiveMQQueue[DLQ]'
17:04:44,598 INFO [ArtemisHornetQClientTest] [ 252]: * * * Sent a message 'foobar-2' to 'ActiveMQQueue[DLQ]'
17:04:44,603 INFO [ArtemisHornetQClientTest] [ 257]: * * * Sent a message 'foobar-3' to 'ActiveMQQueue[DLQ]'
17:04:44,607 INFO [ArtemisHornetQClientTest] [ 261]: * * * Sent a message 'foobar-4' to 'ActiveMQQueue[DLQ]'
17:04:44,670 INFO [ArtemisHornetQClientTest] [ 324]: * * * Received a message 'foobar-0' to 'ActiveMQQueue[DLQ]'
17:04:44,670 INFO [ArtemisHornetQClientTest] [ 324]: * * * Received a message 'foobar-1' to 'ActiveMQQueue[DLQ]'
17:04:44,671 INFO [ArtemisHornetQClientTest] [ 325]: * * * Received a message 'foobar-2' to 'ActiveMQQueue[DLQ]'
17:04:44,671 INFO [ArtemisHornetQClientTest] [ 325]: * * * Received a message 'foobar-3' to 'ActiveMQQueue[DLQ]'
17:04:44,672 INFO [ArtemisHornetQClientTest] [ 326]: * * * Received a message 'foobar-4' to 'ActiveMQQueue[DLQ]'
{noformat}
> 30secs delay on consumer.receive() in spite of shorter timeout
> --------------------------------------------------------------
>
> Key: WFLY-6420
> URL: https://issues.jboss.org/browse/WFLY-6420
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 10.0.0.Final
> Reporter: Tomohisa igarashi
> Assignee: Jeff Mesnil
> Fix For: 10.1.0.Final
>
> Attachments: artemis-hornetq-client.tgz
>
>
> consumer.receive() is blocked 30secs even if shorter timeout is specified. Attached a maven project including testcases.
> The ArtemisStandaloneTest do same against embedded server, but this in contrast works fine. So the issue seems to happen only on WildFly via http upgrade connection.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBJCA-1318) list driven ExceptionSorter, StaleConnectionChecker
by Johnathon Lee (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1318?page=com.atlassian.jira.plugin... ]
Johnathon Lee updated JBJCA-1318:
---------------------------------
Description:
Configuration defined ExceptionSorter, StaleConnectionChecker.
Using an externally (from the implementation) defined "," separated list.
Defined via '<config-property name=prop_name >value1,value2,value3</>' in the standalone/domain configuration files.
ie:
set via <config-property name="FatalExceptions">10099,10100,10101</>
set via <config-property name="StaleExceptions">10099,10100,10101</>
Documentation updated to reflect suggested error codes for vendor based upon the current implementations.
was:
Configuration defined ExceptionSorter, ValidConnectionChecker, StaleConnectionChecker.
Using an externally (from the implementation) defined "," separated list.
Defined via '<config-property name=prop_name >value1,value2,value3</>' in the standalone/domain configuration files.
Documentation updated to reflect suggested error codes for vendor based upon the current implementations.
> list driven ExceptionSorter, StaleConnectionChecker
> ---------------------------------------------------
>
> Key: JBJCA-1318
> URL: https://issues.jboss.org/browse/JBJCA-1318
> Project: IronJacamar
> Issue Type: Enhancement
> Components: JDBC
> Reporter: Johnathon Lee
> Assignee: Johnathon Lee
>
> Configuration defined ExceptionSorter, StaleConnectionChecker.
> Using an externally (from the implementation) defined "," separated list.
> Defined via '<config-property name=prop_name >value1,value2,value3</>' in the standalone/domain configuration files.
> ie:
> set via <config-property name="FatalExceptions">10099,10100,10101</>
> set via <config-property name="StaleExceptions">10099,10100,10101</>
> Documentation updated to reflect suggested error codes for vendor based upon the current implementations.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBJCA-1318) list driven ExceptionSorter, StaleConnectionChecker
by Johnathon Lee (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1318?page=com.atlassian.jira.plugin... ]
Johnathon Lee updated JBJCA-1318:
---------------------------------
Summary: list driven ExceptionSorter, StaleConnectionChecker (was: list driven ExceptionSorter, StaleConnectionChecker & ValidConnectionChecker)
> list driven ExceptionSorter, StaleConnectionChecker
> ---------------------------------------------------
>
> Key: JBJCA-1318
> URL: https://issues.jboss.org/browse/JBJCA-1318
> Project: IronJacamar
> Issue Type: Enhancement
> Components: JDBC
> Reporter: Johnathon Lee
> Assignee: Johnathon Lee
>
> Configuration defined ExceptionSorter, ValidConnectionChecker, StaleConnectionChecker.
> Using an externally (from the implementation) defined "," separated list.
> Defined via '<config-property name=prop_name >value1,value2,value3</>' in the standalone/domain configuration files.
> Documentation updated to reflect suggested error codes for vendor based upon the current implementations.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6421) Servlet mapping does not match url-pattern with wildcard if Filter mapping matches url-pattern without wildcard previously
by antonluca formichella (JIRA)
antonluca formichella created WFLY-6421:
-------------------------------------------
Summary: Servlet mapping does not match url-pattern with wildcard if Filter mapping matches url-pattern without wildcard previously
Key: WFLY-6421
URL: https://issues.jboss.org/browse/WFLY-6421
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 9.0.2.Final
Reporter: antonluca formichella
Assignee: Stuart Douglas
First scenario (filter + servlet with same url-pattern, works):
<filter-mapping>
<filter-name>TestFilter</filter-name>
<url-pattern>/test/*</url-pattern>
</filter-mapping>
<servlet-mapping>
<servlet-name>TestServlet</servlet-name>
<url-pattern>/test/*</url-pattern>
</servlet-mapping>
accessing /test both TestFilter and TestServlet are invoked
Second scenario (filter + servlet with different url-pattern, does not work):
<filter-mapping>
<filter-name>TestFilter</filter-name>
<url-pattern>/test</url-pattern>
</filter-mapping>
<servlet-mapping>
<servlet-name>TestServlet</servlet-name>
<url-pattern>/test/*</url-pattern>
</servlet-mapping>
accessing /test TestFilter is invoked, TestServlet is not invoked!!!
The second scenario works fine on wildfly 8.2.0, but does not work on wildfly 9.0.2
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBJCA-1318) list driven ExceptionSorter, StaleConnectionChecker & ValidConnectionChecker
by Johnathon Lee (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1318?page=com.atlassian.jira.plugin... ]
Johnathon Lee updated JBJCA-1318:
---------------------------------
Description:
Configuration defined ExceptionSorter, ValidConnectionChecker, StaleConnectionChecker.
Using an externally (from the implementation) defined "," separated list.
Defined via '<config-property name=prop_name >value1,value2,value3</>' in the standalone/domain configuration files.
Documentation updated to reflect suggested error codes for vendor based upon the current implementations.
was:
Configuration defined ExceptionSorter, ValidConnectionChecker, StaleConnectionChecker.
Using an externally (from the implementation) defined "," separated list. Possibly passed in via System Properties, arguements or defined via a new structure in the standalone/domain configuration files.
Documentation updated to reflect suggested error codes for vendor based upon the current implementations.
> list driven ExceptionSorter, StaleConnectionChecker & ValidConnectionChecker
> ----------------------------------------------------------------------------
>
> Key: JBJCA-1318
> URL: https://issues.jboss.org/browse/JBJCA-1318
> Project: IronJacamar
> Issue Type: Enhancement
> Components: JDBC
> Reporter: Johnathon Lee
> Assignee: Johnathon Lee
>
> Configuration defined ExceptionSorter, ValidConnectionChecker, StaleConnectionChecker.
> Using an externally (from the implementation) defined "," separated list.
> Defined via '<config-property name=prop_name >value1,value2,value3</>' in the standalone/domain configuration files.
> Documentation updated to reflect suggested error codes for vendor based upon the current implementations.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFLY-6420) 30secs delay on consumer.receive() in spite of shorter timeout
by Tomohisa igarashi (JIRA)
Tomohisa igarashi created WFLY-6420:
---------------------------------------
Summary: 30secs delay on consumer.receive() in spite of shorter timeout
Key: WFLY-6420
URL: https://issues.jboss.org/browse/WFLY-6420
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 10.0.0.Final
Reporter: Tomohisa igarashi
Assignee: Jeff Mesnil
Attachments: artemis-hornetq-client.tgz
consumer.receive() is blocked 30secs even if shorter timeout is specified. Attached a maven project including testcases.
The ArtemisStandaloneTest do same against embedded server, but this in contrast works fine. So the issue seems to happen only on WildFly via http upgrade connection.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFCORE-1449) truststore-type incorrect case in management schema
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1449?page=com.atlassian.jira.plugi... ]
Darran Lofthouse moved JBEAP-3938 to WFCORE-1449:
-------------------------------------------------
Project: WildFly Core (was: JBoss Enterprise Application Platform)
Key: WFCORE-1449 (was: JBEAP-3938)
Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1)
Component/s: Domain Management
Security
(was: Domain Management)
(was: Security)
Target Release: (was: 7.backlog.GA)
Affects Version/s: 2.1.0.Final
(was: 7.0.0.ER7)
> truststore-type incorrect case in management schema
> ---------------------------------------------------
>
> Key: WFCORE-1449
> URL: https://issues.jboss.org/browse/WFCORE-1449
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management, Security
> Affects Versions: 2.1.0.Final
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
>
> truststore-Type attribute of element server-sslType should be named truststore-type in XSD. Wildfly configuration parser works with truststore-type, but for example eclipse xml validator complains when truststore-type is used in configuration file.
> On the other side when truststore-Type (comply to XSD) is used, wildfly configuration parser starts to complain:
> {code}
> [Host Controller] 14:49:21,822 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0033: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
> [Host Controller] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131)
> [Host Controller] at org.jboss.as.host.controller.HostControllerConfigurationPersister.load(HostControllerConfigurationPersister.java:188)
> [Host Controller] at org.jboss.as.host.controller.DomainModelControllerService.boot(DomainModelControllerService.java:585)
> [Host Controller] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299)
> [Host Controller] at java.lang.Thread.run(Thread.java:745)
> [Host Controller] Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[110,13]
> [Host Controller] Message: WFLYCTL0197: Unexpected attribute 'truststore-Type' encountered
> [Host Controller] at org.jboss.as.controller.parsing.ParseUtils.unexpectedAttribute(ParseUtils.java:117)
> [Host Controller] at org.jboss.as.host.controller.parsing.HostXml_4.parseServerSsl(HostXml_4.java:1271)
> [Host Controller] at org.jboss.as.host.controller.parsing.HostXml_4.parseServerContent(HostXml_4.java:1131)
> [Host Controller] at org.jboss.as.host.controller.parsing.HostXml_4.parseServer(HostXml_4.java:1088)
> [Host Controller] at org.jboss.as.host.controller.parsing.HostXml_4.parseServers(HostXml_4.java:1071)
> [Host Controller] at org.jboss.as.host.controller.parsing.HostXml_4.readHostElement(HostXml_4.java:388)
> [Host Controller] at org.jboss.as.host.controller.parsing.HostXml_4.readElement(HostXml_4.java:170)
> [Host Controller] at org.jboss.as.host.controller.parsing.HostXml.readElement(HostXml.java:79)
> [Host Controller] at org.jboss.as.host.controller.parsing.HostXml.readElement(HostXml.java:50)
> [Host Controller] at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
> [Host Controller] at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)
> [Host Controller] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123)
> [Host Controller] ... 4 more
> [Host Controller]
> [Host Controller] 14:49:21,823 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0034: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (WFCORE-1449) truststore-type incorrect case in management schema
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1449?page=com.atlassian.jira.plugi... ]
Darran Lofthouse updated WFCORE-1449:
-------------------------------------
Fix Version/s: 3.0.0.Alpha1
> truststore-type incorrect case in management schema
> ---------------------------------------------------
>
> Key: WFCORE-1449
> URL: https://issues.jboss.org/browse/WFCORE-1449
> Project: WildFly Core
> Issue Type: Bug
> Components: Domain Management, Security
> Affects Versions: 2.1.0.Final
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Fix For: 3.0.0.Alpha1
>
>
> truststore-Type attribute of element server-sslType should be named truststore-type in XSD. Wildfly configuration parser works with truststore-type, but for example eclipse xml validator complains when truststore-type is used in configuration file.
> On the other side when truststore-Type (comply to XSD) is used, wildfly configuration parser starts to complain:
> {code}
> [Host Controller] 14:49:21,822 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0033: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
> [Host Controller] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:131)
> [Host Controller] at org.jboss.as.host.controller.HostControllerConfigurationPersister.load(HostControllerConfigurationPersister.java:188)
> [Host Controller] at org.jboss.as.host.controller.DomainModelControllerService.boot(DomainModelControllerService.java:585)
> [Host Controller] at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:299)
> [Host Controller] at java.lang.Thread.run(Thread.java:745)
> [Host Controller] Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[110,13]
> [Host Controller] Message: WFLYCTL0197: Unexpected attribute 'truststore-Type' encountered
> [Host Controller] at org.jboss.as.controller.parsing.ParseUtils.unexpectedAttribute(ParseUtils.java:117)
> [Host Controller] at org.jboss.as.host.controller.parsing.HostXml_4.parseServerSsl(HostXml_4.java:1271)
> [Host Controller] at org.jboss.as.host.controller.parsing.HostXml_4.parseServerContent(HostXml_4.java:1131)
> [Host Controller] at org.jboss.as.host.controller.parsing.HostXml_4.parseServer(HostXml_4.java:1088)
> [Host Controller] at org.jboss.as.host.controller.parsing.HostXml_4.parseServers(HostXml_4.java:1071)
> [Host Controller] at org.jboss.as.host.controller.parsing.HostXml_4.readHostElement(HostXml_4.java:388)
> [Host Controller] at org.jboss.as.host.controller.parsing.HostXml_4.readElement(HostXml_4.java:170)
> [Host Controller] at org.jboss.as.host.controller.parsing.HostXml.readElement(HostXml.java:79)
> [Host Controller] at org.jboss.as.host.controller.parsing.HostXml.readElement(HostXml.java:50)
> [Host Controller] at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110)
> [Host Controller] at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)
> [Host Controller] at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:123)
> [Host Controller] ... 4 more
> [Host Controller]
> [Host Controller] 14:49:21,823 FATAL [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0034: Host Controller boot has failed in an unrecoverable manner; exiting. See previous messages for details
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month
[JBoss JIRA] (JBJCA-1318) list driven ExceptionSorter, StaleConnectionChecker & ValidConnectionChecker
by Johnathon Lee (JIRA)
[ https://issues.jboss.org/browse/JBJCA-1318?page=com.atlassian.jira.plugin... ]
Johnathon Lee updated JBJCA-1318:
---------------------------------
Description:
Configuration defined ExceptionSorter, ValidConnectionChecker, StaleConnectionChecker.
Using an externally (from the implementation) defined "," separated list. Possibly passed in via System Properties, arguements or defined via a new structure in the standalone/domain configuration files.
Documentation updated to reflect suggested error codes for vendor based upon the current implementations.
was:
Configuration/property defined ExceptionSorter, ValidConnectionChecker, StaleConnectionChecker.
Using an externally (from the implementation) defined "," separated list. Possibly passed in via System Properties, .properties, etc or defined via a new structure in the standalone/domain configuration files.
Documentation updated to reflect suggested error codes for vendor based upon the current implementations.
> list driven ExceptionSorter, StaleConnectionChecker & ValidConnectionChecker
> ----------------------------------------------------------------------------
>
> Key: JBJCA-1318
> URL: https://issues.jboss.org/browse/JBJCA-1318
> Project: IronJacamar
> Issue Type: Enhancement
> Components: JDBC
> Reporter: Johnathon Lee
> Assignee: Johnathon Lee
>
> Configuration defined ExceptionSorter, ValidConnectionChecker, StaleConnectionChecker.
> Using an externally (from the implementation) defined "," separated list. Possibly passed in via System Properties, arguements or defined via a new structure in the standalone/domain configuration files.
> Documentation updated to reflect suggested error codes for vendor based upon the current implementations.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 1 month