February 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3367) Admin console should not allow setting min-pool-size for datasources greater than max-pool-size

by Jan Martiska (JIRA)

Jan Martiska created AS7-3367: --------------------------------- Summary: Admin console should not allow setting min-pool-size for datasources greater than max-pool-size Key: AS7-3367 URL: https://issues.jboss.org/browse/AS7-3367 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.CR1b Reporter: Jan Martiska Assignee: Heiko Braun Priority: Optional Attachments: poolsizes.png I think the title says everything. See screenshot. Concerns both Regular Datasources and XA Datasources. -- 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, 4 months

2
4
0 / 0

[JBoss JIRA] (AS7-3574) Creating a work manager leads to invalid server configuration

by Jan Martiska (JIRA)

Jan Martiska created AS7-3574: --------------------------------- Summary: Creating a work manager leads to invalid server configuration Key: AS7-3574 URL: https://issues.jboss.org/browse/AS7-3574 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.CR1b Reporter: Jan Martiska Assignee: Heiko Braun Fix For: 7.1.1.Final Creating a JCA workmanager in admin console does not work properly. The attributes "queue-length" and "max-threads" expect type INT, but admin console passes something which causes that configuration xml will look this way: <workmanager name="asd"> <short-running-threads allow-core-timeout="false"> <queue-length count="{"count" => 10,"per-cpu" => 20}"/> <max-threads count="{"count" => 10,"per-cpu" => 20}"/> </short-running-threads> </workmanager> It will cause the server will be unable to boot up because XML parsing will fail. These attributes should also be configurable, all these values seem to be hardcoded and impossible to change. -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] (AS7-3412) Unable to add ejb3 thread pool

by Jan Martiska (JIRA)

Jan Martiska created AS7-3412: --------------------------------- Summary: Unable to add ejb3 thread pool Key: AS7-3412 URL: https://issues.jboss.org/browse/AS7-3412 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.CR1b Reporter: Jan Martiska Assignee: Heiko Braun Fix For: 7.1.0.Final In the latest update, ejb3 thread pools now require specifying the time unit for keepalive-time, until now, it has only been a simple number, now it is an object. Trying to create an ejb3 thread pool in admin console will fail: { "outcome" => "failed", "failure-description" => "Attribute keepalive-time expects values of type OBJECT but got 100 of type INT", "rolled-back" => true } -- 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, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (AS7-1758) CLI usability: operations need conventient help option too

by Radoslav Husar (JIRA)

CLI usability: operations need conventient help option too ---------------------------------------------------------- Key: AS7-1758 URL: https://issues.jboss.org/browse/AS7-1758 Project: Application Server 7 Issue Type: Bug Components: CLI Affects Versions: 7.0.1.Final, 7.0.0.Final Reporter: Radoslav Husar Assignee: Alexey Loubyansky Priority: Critical This is a critical usability issue. We must provide a way to get help about operations usage too. Its difficult to comprehend how to use operations from this model: {code} [domain@localhost:9999 /] :read-operation-description(name="upload-deployment-url") { "outcome" => "success", "result" => { "operation-name" => "upload-deployment-url", "description" => "Indicates that the deployment content available at the included URL should be added to the deployment content repository. Note that this operation does not indicate the content should be deployed into the runtime.", "request-properties" => {"url" => { "type" => STRING, "description" => "The URL at which the deployment content is available for upload to the domain's or standalone server's deployment content repository.. Note that the URL must be accessible from the target of the operation (i.e. the Domain Controller or standalone server).", "required" => true, "min-length" => 1, "nillable" => false }}, "reply-properties" => { "type" => BYTES, "description" => "The hash of managed deployment content that has been uploaded to the domain's or standalone server's deployment content repository.", "min-length" => 20, "max-length" => 20, "nillable" => false } } } [domain@localhost:9999 /] {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 4 months

5
6
0 / 0

[JBoss JIRA] (AS7-3822) Unable to deploy without Bundle-Manifest Version or with Bundle-ManifestVersion: 1

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-3822?page=com.atlassian.jira.plugin.s... ] Thomas Diesler moved JBOSGI-523 to AS7-3822: -------------------------------------------- Project: Application Server 7 (was: JBoss OSGi) Key: AS7-3822 (was: JBOSGI-523) Workflow: GIT Pull Request workflow (was: jira) Component/s: OSGi (was: Core Framework) Security: (was: Public) > Unable to deploy without Bundle-Manifest Version or with Bundle-ManifestVersion: 1 > ---------------------------------------------------------------------------------- > > Key: AS7-3822 > URL: https://issues.jboss.org/browse/AS7-3822 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi > Affects Versions: 7.1.0.Final > Reporter: Rico Neubauer > Assignee: Thomas Diesler > Attachments: server.log > > > Affects version 1.1.5, included in JBoss 7.1.final. > OSGI-specification r4.core.pdf chapter 3.5.7 holds the rules for legacy (version 1) bundles. > According to that a bundle without Bundle-ManifestVersion must be handles as Bundle-ManifestVersion: 1. > Neither a bundle having Bundle-ManifestVersion: 1, not without a Bundle-ManifestVersion does deploy at all. You can only see "Starting deployment of ..." in the log, nothing else happens. > See attached log file for a test showing the deployment of a bundle without/with version-1/with versio-2 ManifestVersion. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-3822) Unable to deploy without Bundle-Manifest Version or with Bundle-ManifestVersion: 1

by Thomas Diesler (JIRA)

[ https://issues.jboss.org/browse/AS7-3822?page=com.atlassian.jira.plugin.s... ] Thomas Diesler updated AS7-3822: -------------------------------- Fix Version/s: 7.2.0.Alpha1 Affects Version/s: 7.1.0.Final > Unable to deploy without Bundle-Manifest Version or with Bundle-ManifestVersion: 1 > ---------------------------------------------------------------------------------- > > Key: AS7-3822 > URL: https://issues.jboss.org/browse/AS7-3822 > Project: Application Server 7 > Issue Type: Bug > Components: OSGi > Affects Versions: 7.1.0.Final > Reporter: Rico Neubauer > Assignee: Thomas Diesler > Fix For: 7.2.0.Alpha1 > > Attachments: server.log > > > Affects version 1.1.5, included in JBoss 7.1.final. > OSGI-specification r4.core.pdf chapter 3.5.7 holds the rules for legacy (version 1) bundles. > According to that a bundle without Bundle-ManifestVersion must be handles as Bundle-ManifestVersion: 1. > Neither a bundle having Bundle-ManifestVersion: 1, not without a Bundle-ManifestVersion does deploy at all. You can only see "Starting deployment of ..." in the log, nothing else happens. > See attached log file for a test showing the deployment of a bundle without/with version-1/with versio-2 ManifestVersion. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (AS7-3818) equals()/hashCode() is wrong for component view descriptions

by Stuart Douglas (JIRA)

Stuart Douglas created AS7-3818: ----------------------------------- Summary: equals()/hashCode() is wrong for component view descriptions Key: AS7-3818 URL: https://issues.jboss.org/browse/AS7-3818 Project: Application Server 7 Issue Type: Bug Components: EE, EJB Affects Versions: 7.1.0.Final Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 7.1.1.Final This can result in views being considered equal even if they do not belong to the same component, which means that resolutions that should be ambiguos deploy as normal. -- 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, 4 months

1
1
0 / 0

[JBoss JIRA] (AS7-2232) TS: On -Dtest=..., activate appropriate modules automatically (using package prefix)

by Ondrej Zizka (Created) (JIRA)

TS: On -Dtest=..., activate appropriate modules automatically (using package prefix) ------------------------------------------------------------------------------------ Key: AS7-2232 URL: https://issues.jboss.org/browse/AS7-2232 Project: Application Server 7 Issue Type: Sub-task Components: Test Suite Reporter: Ondrej Zizka Assignee: Ondrej Zizka ...to relieve people from writing `-Dintegration.module` all the time. -- 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, 4 months

2
1
0 / 0

[JBoss JIRA] (AS7-3720) clustering-impl doesn't set a version but refers to it by ${project.version}

by Ondrej Zizka (JIRA)

Ondrej Zizka created AS7-3720: --------------------------------- Summary: clustering-impl doesn't set a version but refers to it by ${project.version} Key: AS7-3720 URL: https://issues.jboss.org/browse/AS7-3720 Project: Application Server 7 Issue Type: Bug Components: Clustering Affects Versions: 7.1.0.CR1b Reporter: Ondrej Zizka Assignee: James Perkins {code} [WARNING] Some problems were encountered while building the effective model for org.jboss.as:jboss-as-clustering-impl:jar:7.1.0.Final-SNAPSHOT [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.jboss.as:jboss-as-clustering-common:jar -> version (?) vs ${project.version} @ line 53, column 21 {code} The impl module doesn't set a version but refers to it: {code:xml} <dependency> <groupId>org.jboss.as</groupId> <artifactId>jboss-as-clustering-common</artifactId> <version>${project.version}</version> </dependency> {code} -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] (JASSIST-155) StackMapTable is not properly updated (for Java7)

by Shigeru Chiba (JIRA)

Shigeru Chiba created JASSIST-155: ------------------------------------- Summary: StackMapTable is not properly updated (for Java7) Key: JASSIST-155 URL: https://issues.jboss.org/browse/JASSIST-155 Project: Javassist Issue Type: Bug Affects Versions: 3.15.0-GA Reporter: Shigeru Chiba Assignee: Shigeru Chiba Fix For: 3.16.0-GA If a Java7 application on top of Javassist only uses the high-level API (only javassist.* classes), Javassist must be responsible for properly updating stack map tables. However, Javassist does not update a stack map table in some situation. For an application directly using a lower-level API (javassist.bytecode.* classes), updating a stack map table is the responsibility of the application. -- 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, 4 months

2
2
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 February 2012