October 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (AS7-1078) executor in <connector/> of web subsystem doesn't work.

by Jean-Frederic Clere (JIRA)

executor in <connector/> of web subsystem doesn't work. ------------------------------------------------------- Key: AS7-1078 URL: https://issues.jboss.org/browse/AS7-1078 Project: Application Server 7 Issue Type: Bug Components: Web Affects Versions: 7.0.0.Beta3 Reporter: Jean-Frederic Clere Add in threads subsystem: <bounded-queue-thread-pool name="executor" blocking="true"> <core-threads count="10" per-cpu="20"/> <queue-length count="10" per-cpu="20"/> <max-threads count="10" per-cpu="20"/> <keepalive-time time="10" unit="seconds"/> </bounded-queue-thread-pool> and: <connector name="http" scheme="http" protocol="HTTP/1.1" socket-binding="http" executor="executor" /> web will still use the default executor. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

2
3
0 / 0

[JBoss JIRA] (JBRULES-3262) Rule Search feature

by G Patel (Created) (JIRA)

Rule Search feature ------------------- Key: JBRULES-3262 URL: https://issues.jboss.org/browse/JBRULES-3262 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-core (expert), drools-guvnor Reporter: G Patel Assignee: Mark Proctor Drools sorely lacks a rule search feature i.e - ability to search and display rules that match a particular criteria. For example: show all rules that contain the fact Person whose age > 21 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3260) Events with no expiration declared being set to zero expirationOffset during package assembly

by Rob Crawford (Created) (JIRA)

Events with no expiration declared being set to zero expirationOffset during package assembly --------------------------------------------------------------------------------------------- Key: JBRULES-3260 URL: https://issues.jboss.org/browse/JBRULES-3260 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (expert), drools-core (fusion) Affects Versions: 5.3.0.Final, 5.3.0.CR1 Reporter: Rob Crawford Assignee: Mark Proctor Had a problem with events being expired immediately on being inserted. These events have no @expiration declaration. Tracing and debugging led to this line: ReteooRuleBase, line 477: node.setExpirationOffset( Math.max( node.getExpirationOffset(), typeDeclaration.getExpirationOffset()+1 ) ); Since neither the type and its supertype have expirations declared, getExpirationOffset() returns -1 in both cases. Max(-1, -1 + 1) == 0, so the event is assigned an expiration of zero. Should make sure not to set the expiration when both are already -1. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

5
4
0 / 0

[JBoss JIRA] Created: (AS7-1015) Deployment fails with NullPointerException when installing JDBC Driver as a deployment

by Sande Gilda (JIRA)

Deployment fails with NullPointerException when installing JDBC Driver as a deployment -------------------------------------------------------------------------------------- Key: AS7-1015 URL: https://issues.jboss.org/browse/AS7-1015 Project: Application Server 7 Issue Type: Bug Components: JCA Environment: Fedora 14. JBoss AS7 build from June 8, Using MySQL JDBC driver downloaded as an example from http://community.jboss.org/wiki/DataSourceConfigurationinAS7#Installing_a... Reporter: Sande Gilda I am working on the DataSource configuration changes for the EAP5 -> EAP6 migration guide and am following the steps here: http://community.jboss.org/wiki/DataSourceConfigurationinAS7. I have been able to successfully install the MySQL JDBC driver as a module, however, I am not having much luck installing the driver as a deployment, which this document says is the recommended way to install it. I've done the following: - I copied the JDBC-compliant mysql-connector-java-5.1.15.jar (downloaded from the above web site) into my <jboss7>/standalone/deployments directory. - I still have the <datasource> and <driver> elements defined in my standalone.xml file from when I successfully installed the driver as a module. When I start the server, I see the following error in the log: 11:53:42,348 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC00001: Failed to start service jboss.deployment.unit."TopicIndex.war".CONFIGURE_MODULE: org.jboss.msc.service.StartException in service jboss.deployment.unit."TopicIndex.war".CONFIGURE_MODULE: Failed to process phase CONFIGURE_MODULE of deployment "TopicIndex.war" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) [jboss-as-server-7.0.0.Beta4-SNAPSHOT.jar:7.0.0.Beta4-SNAPSHOT] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1675) [jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_25] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_25] at java.lang.Thread.run(Thread.java:662) [:1.6.0_25] Caused by: java.lang.NullPointerException at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:188) [jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8] at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2165) [jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8] at org.jboss.msc.service.ServiceTargetImpl.install(ServiceTargetImpl.java:188) [jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8] at org.jboss.msc.service.ServiceControllerImpl$ChildServiceTarget.install(ServiceControllerImpl.java:2165) [jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8] at org.jboss.msc.service.ServiceBuilderImpl.install(ServiceBuilderImpl.java:325) [jboss-msc-1.0.0.Beta8.jar:1.0.0.Beta8] at org.jboss.as.server.deployment.module.ModuleSpecProcessor.createModuleService(ModuleSpecProcessor.java:193) [jboss-as-server-7.0.0.Beta4-SNAPSHOT.jar:7.0.0.Beta4-SNAPSHOT] at org.jboss.as.server.deployment.module.ModuleSpecProcessor.deploy(ModuleSpecProcessor.java:99) [jboss-as-server-7.0.0.Beta4-SNAPSHOT.jar:7.0.0.Beta4-SNAPSHOT] at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) [jboss-as-server-7.0.0.Beta4-SNAPSHOT.jar:7.0.0.Beta4-SNAPSHOT] ... 4 more 11:53:42,350 ERROR [org.jboss.as] (MSC service thread 1-1) JBoss AS 7.0.0.Beta4-SNAPSHOT "(TBD)" started (with errors) in 6159ms - Started 136 of 196 services (5 services failed or missing dependencies, 55 services are passive or on-demand) Later I see the message that deployment of my WAR failed due to the missing dependency: 11:53:42,394 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Starting deployment of "TopicIndex.war" 11:53:42,394 INFO [org.jboss.as.server] (MSC service thread 1-6) Service status report New missing/unsatisfied dependencies: service jboss.jdbc-driver._________________________ (missing) required by [service jboss.data-source.java:/TopicIndexDatasource] Is there something else I need to be doing here? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

6
19
0 / 0

[JBoss JIRA] (AS7-2203) Add support for AS 7 domain controller

by Aslak Knutsen (Moved) (JIRA)

[ https://issues.jboss.org/browse/AS7-2203?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen moved ARQ-498 to AS7-2203: ---------------------------------------- Project: Application Server 7 (was: Arquillian) Key: AS7-2203 (was: ARQ-498) Security: (was: Public) > Add support for AS 7 domain controller > -------------------------------------- > > Key: AS7-2203 > URL: https://issues.jboss.org/browse/AS7-2203 > Project: Application Server 7 > Issue Type: Feature Request > Reporter: Ondrej Zizka > Assignee: Andrew Rubinger > Priority: Critical > > A container for AS 7 domain controller would be very helpful for it's integration testsuite. > Such container should support: > * Attaching hosts to a domain > * Start, stop a domain with multiple hosts > * Configuration (creation) of the domain using domain config file > * Configuration (creation) of a profile using a CLI batch > * Configuration (creation) of a profile using a callback class which would handle communication with Java API > More requirements to come. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] (AS7-2203) Add Arquillian Container support for AS 7 domain controller

by Aslak Knutsen (Updated) (JIRA)

[ https://issues.jboss.org/browse/AS7-2203?page=com.atlassian.jira.plugin.s... ] Aslak Knutsen updated AS7-2203: ------------------------------- Summary: Add Arquillian Container support for AS 7 domain controller (was: Add support for AS 7 domain controller) Component/s: Test Suite > Add Arquillian Container support for AS 7 domain controller > ------------------------------------------------------------ > > Key: AS7-2203 > URL: https://issues.jboss.org/browse/AS7-2203 > Project: Application Server 7 > Issue Type: Feature Request > Components: Test Suite > Reporter: Ondrej Zizka > Assignee: Andrew Rubinger > Priority: Critical > > A container for AS 7 domain controller would be very helpful for it's integration testsuite. > Such container should support: > * Attaching hosts to a domain > * Start, stop a domain with multiple hosts > * Configuration (creation) of the domain using domain config file > * Configuration (creation) of a profile using a CLI batch > * Configuration (creation) of a profile using a callback class which would handle communication with Java API > More requirements to come. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBRULES-3261) testing fluent api

by Mark Proctor (Created) (JIRA)

testing fluent api ------------------ Key: JBRULES-3261 URL: https://issues.jboss.org/browse/JBRULES-3261 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Proctor Assignee: Mark Proctor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (AS7-1989) Reading a server group resource in the CLI doesn't show the socket group

by Misty Stanley-Jones (JIRA)

Reading a server group resource in the CLI doesn't show the socket group ------------------------------------------------------------------------ Key: AS7-1989 URL: https://issues.jboss.org/browse/AS7-1989 Project: Application Server 7 Issue Type: Bug Components: CLI Environment: Fedora 15, Bash, very recent AS trunk. Reporter: Misty Stanley-Jones Assignee: Alexey Loubyansky Priority: Minor I added a server group using the following command: [domain@localhost:9999 /] /server-group=clustered-group:add(profile=ha,socket-group=ha-sockets) I then used the following command to read the resource: [domain@localhost:9999 /] /server-group=clustered-group:read-resource { "outcome" => "success", "result" => { "deployment" => undefined, "jvm" => undefined, "profile" => "ha", "system-property" => undefined } } It shows the profile but not the socket binding group. It seems like it should show both. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
3
0 / 0

[JBoss JIRA] (AS7-2162) System properties propagated from command line using -D, -P or --properties aren't visible in CLI and console

by Rostislav Svoboda (Created) (JIRA)

System properties propagated from command line using -D, -P or --properties aren't visible in CLI and console ------------------------------------------------------------------------------------------------------------- Key: AS7-2162 URL: https://issues.jboss.org/browse/AS7-2162 Project: Application Server 7 Issue Type: Bug Components: CLI, Console, Domain Management Reporter: Rostislav Svoboda Assignee: Brian Stansberry Fix For: 7.1.0.CR1 CLI and console shows only properties defined in .xml configuration files. System properties propagated from command line using -D, -P or --properties args should be visible too. It would be useful for administrators when searching for possible problems, the same applies to devels. For domain I'd like to see sysprops on each instance and separate overview for DC. Previous versions of AS/EAP provide such overview in /web-console/SysProperties.jsp. NOTE: JVM based properties like java.vendor etc. would be beneficial too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

4
3
0 / 0

[JBoss JIRA] (JBMESSAGING-1903) autogenerate server peer ID when S3_PING is in use

by Aleksandar Kostadinov (Created) (JIRA)

autogenerate server peer ID when S3_PING is in use -------------------------------------------------- Key: JBMESSAGING-1903 URL: https://issues.jboss.org/browse/JBMESSAGING-1903 Project: JBoss Messaging Issue Type: Feature Request Components: Configuration and Management Affects Versions: EAP/SOA-P Integration Environment: EC2 Reporter: Aleksandar Kostadinov Fix For: EAP/SOA-P Integration In EC2 one cannot easily generate unique server peer IDs for each server (see JBPAPP-7208). I thought it will not be too hard to use S3_PING to also generate unique server peer IDs. How feasible is implementation of such functionality? If not feasible, please provide your ideas about other possible approaches. Thank you! -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2011