July 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

13 years, 2 months

2
3
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

13 years, 2 months

6
19
0 / 0

[JBoss JIRA] Created: (JBRULES-2951) regression: cannot compile return value "(java.lang.Object.class)"

by Wolfgang Laun (JIRA)

regression: cannot compile return value "(java.lang.Object.class)" ------------------------------------------------------------------ Key: JBRULES-2951 URL: https://issues.jboss.org/browse/JBRULES-2951 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler Affects Versions: 5.2.0.M2 Reporter: Wolfgang Laun Assignee: Mark Proctor Priority: Critical The rule below compiled with a version build from HEAD on February 10, 2011. But now: Unable to Analyse Expression target == source || target == (java.lang.Object.class): [Error: Failed to compile: 2 compilation error(s): - (1,32) unable to resolve method using strict-mode: ex10.Assignment.java() - (1,32) unqualified type in strict mode for: java] [Near : {... target == source || target == (java.lang.Object.class) ....}] ^ [Line: 1, Column: 32] : [Rule name='SameOrObjectIsAssignable'] ALSO please note that the line number is way off. rule SameOrObjectIsAssignable when $a: Assignment( $t: target, target == source || target == (java.lang.Object.class) ) then System.out.println( $a.toString() + " is OK. " ); retract( $a.getOriginal() ); end -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

7
7
0 / 0

[JBoss JIRA] Created: (JBRULES-3147) Regression: all uppercase field reference results in compile error

by Wolfgang Laun (JIRA)

Regression: all uppercase field reference results in compile error ------------------------------------------------------------------ Key: JBRULES-3147 URL: https://issues.jboss.org/browse/JBRULES-3147 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-compiler (expert) Affects Versions: 5.2.0.Final Reporter: Wolfgang Laun Assignee: Mark Proctor Fix For: 5.2.1.Final Consider the following ways of writing getters, setters and pattern field names element xetter field 5.1.1 5.3.0 ============================================= state xetstate state OK OK state xetState state OK OK staTe xetStaTe staTe OK OK state xetSTATE STATE OK ERR The last variation is a regression from 5.1.1. It is not so absurd - if the field is designated with an acronym (XML,...) this would be the natural way to write xetters and the pattern field. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

6
8
0 / 0

[JBoss JIRA] Created: (JBRULES-3134) Parenthesized class name causes NPE in RuleBuilder (MVEL)

by Wolfgang Laun (JIRA)

Parenthesized class name causes NPE in RuleBuilder (MVEL) --------------------------------------------------------- Key: JBRULES-3134 URL: https://issues.jboss.org/browse/JBRULES-3134 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.2.0.Final Reporter: Wolfgang Laun Assignee: Mark Proctor Fix For: 5.2.1.Final declare Foo clazz : Class end rule testFoo when Foo( clazz == (java.lang.Object) ) then System.out.println( "Foo is Object" ); end causes Exception in thread "main" [Error: not a statement, or badly formed structure] [Near : {... (java.lang.Object) ....}] ^ [Line: 1, Column: 19] at org.mvel2.compiler.ExpressionCompiler._compile(ExpressionCompiler.java:307) at org.mvel2.compiler.ExpressionCompiler.compile(ExpressionCompiler.java:69) at org.mvel2.MVEL.analysisCompile(MVEL.java:668) at org.mvel2.MVEL.analysisCompile(MVEL.java:672) at org.drools.rule.builder.PatternBuilder.setInputs(PatternBuilder.java:779) at org.drools.rule.builder.PatternBuilder.build(PatternBuilder.java:540) at org.drools.rule.builder.PatternBuilder.processConstraintsAndBinds(PatternBuilder.java:349) at org.drools.rule.builder.PatternBuilder.build(PatternBuilder.java:264) at org.drools.rule.builder.PatternBuilder.build(PatternBuilder.java:122) at org.drools.rule.builder.GroupElementBuilder.build(GroupElementBuilder.java:65) at org.drools.rule.builder.RuleBuilder.build(RuleBuilder.java:81) at org.drools.compiler.PackageBuilder.addRule(PackageBuilder.java:1889) at org.drools.compiler.PackageBuilder.addPackage(PackageBuilder.java:755) at org.drools.compiler.PackageBuilder.addPackageFromDrl(PackageBuilder.java:365) at org.drools.compiler.PackageBuilder.addKnowledgeResource(PackageBuilder.java:543) at org.drools.builder.impl.KnowledgeBuilderImpl.add(KnowledgeBuilderImpl.java:28) at listofthree.Main.setup(Main.java:55) at listofthree.Main.main(Main.java:107) Caused by: java.lang.NullPointerException at java.lang.Class.isAssignableFrom(Native Method) at org.mvel2.DataConversion.canConvert(DataConversion.java:104) at org.mvel2.ast.TypeCast.<init>(TypeCast.java:47) at org.mvel2.compiler.AbstractParser.nextToken(AbstractParser.java:1034) at org.mvel2.compiler.ExpressionCompiler._compile(ExpressionCompiler.java:135) ... 17 more -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

6
5
0 / 0

[JBoss JIRA] Created: (AS7-747) Subsystem "web": Boolean model values must not be "undefined"

by Heiko Braun (JIRA)

Subsystem "web": Boolean model values must not be "undefined" ------------------------------------------------------------- Key: AS7-747 URL: https://issues.jboss.org/browse/AS7-747 Project: Application Server 7 Issue Type: Bug Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

5
9
0 / 0

[JBoss JIRA] Created: (AS7-1299) Interface resource's criteria attribute should be read-write

by Brian Stansberry (JIRA)

Interface resource's criteria attribute should be read-write ------------------------------------------------------------- Key: AS7-1299 URL: https://issues.jboss.org/browse/AS7-1299 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.0.0.Final Reporter: Brian Stansberry Fix For: 7.1.0.Alpha1 http://lists.jboss.org/pipermail/jboss-as7-dev/2011-July/003123.html -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

6
10
0 / 0

[JBoss JIRA] Created: (JBAS-9293) Display default interface for a socket-binding-group

by Brian Stansberry (JIRA)

Display default interface for a socket-binding-group ---------------------------------------------------- Key: JBAS-9293 URL: https://issues.jboss.org/browse/JBAS-9293 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Web Console Reporter: Brian Stansberry Assignee: Heiko Braun A socket binding group has a default interface attribute that becomes the interface value for any socket binding that doesn't declare one. The Beta7-SNAPSHOT UI isn't showing this. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (JBAS-8978) Complete async EJB invocation

by David Lloyd (JIRA)

Complete async EJB invocation ----------------------------- Key: JBAS-8978 URL: https://issues.jboss.org/browse/JBAS-8978 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: 7.0.0.Beta2 Integrate the interceptor; test with cancellation; handle @Asynchronous annotation as well as any descriptor stuff -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

6
10
0 / 0

[JBoss JIRA] Created: (AS7-1267) Can't set "append" attribute on file handlers

by Stan Silvert (JIRA)

Can't set "append" attribute on file handlers --------------------------------------------- Key: AS7-1267 URL: https://issues.jboss.org/browse/AS7-1267 Project: Application Server 7 Issue Type: Bug Components: Logging Affects Versions: 7.1.0.Alpha1 Reporter: Stan Silvert Assignee: David Lloyd I can't tell what is really happening here. It seems to parse the "append" attribute OK, but it doesn't show up in the CLI. I've also set it programmatically in the console code, but I never get a value back for it. <periodic-rotating-file-handler name="FILE"> <level name="INFO"/> <formatter> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/> </formatter> <file relative-to="jboss.server.log.dir" path="server.log"/> <suffix value=".yyyy-MM-dd"/> <append value="true"/> </periodic-rotating-file-handler> [standalone@localhost:9999 /] /subsystem=logging/periodic-rotating-file-handler=FILE:read-resource { "outcome" => "success", "result" => { "autoflush" => true, "encoding" => undefined, "file" => { "path" => "server.log", "relative-to" => "jboss.server.log.dir" }, "formatter" => "%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n", "level" => "INFO", "suffix" => ".yyyy-MM-dd" } } -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 2 months

4
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2011