November 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-5894) jboss-ejb3-ext-api is not marked a jboss api module

by Carlo de Wolf (JIRA)

Carlo de Wolf created AS7-5894: ---------------------------------- Summary: jboss-ejb3-ext-api is not marked a jboss api module Key: AS7-5894 URL: https://issues.jboss.org/browse/AS7-5894 Project: Application Server 7 Issue Type: Bug Components: EJB Affects Versions: 7.1.3.Final (EAP) Reporter: Carlo de Wolf Assignee: jaikiran pai jboss-ejb3-ext-api-2.0.0-redhat-2.jar does into org.jboss.ejb3 module which is marked as private. All classes in jboss-ejb3-ext-api should really be public instead. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-5762) Allow multiple quoted strings within a CLI command

by James Perkins (JIRA)

James Perkins created AS7-5762: ---------------------------------- Summary: Allow multiple quoted strings within a CLI command Key: AS7-5762 URL: https://issues.jboss.org/browse/AS7-5762 Project: Application Server 7 Issue Type: Bug Components: CLI Reporter: James Perkins Assignee: Alexey Loubyansky CLI commands with multiple quotes are not properly parsed. {code} /subsystem=logging/console-handler=CONSOLE:write-attribute(name=filter, value="all(match(\"pattern1\"),not(match(\"pattern2\")))") {code} I would expect the above command to return the following to the OSH. {code} all(match("pattern"),not(match("pattern2"))) {code} What actually gets passed to the OSH is {code} all(match( {code} Note this filter syntax relies on PR https://github.com/jbossas/jboss-as/pull/3251 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
1
0 / 0

[JBoss JIRA] (AS7-5893) CLONE - Empty messaging subsystem can not be persisted

by Tom Fonteyne (JIRA)

Tom Fonteyne created AS7-5893: --------------------------------- Summary: CLONE - Empty messaging subsystem can not be persisted Key: AS7-5893 URL: https://issues.jboss.org/browse/AS7-5893 Project: Application Server 7 Issue Type: Feature Request Components: JMS Affects Versions: 7.1.3.Final (EAP) Reporter: Tom Fonteyne Assignee: Jeff Mesnil Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP) When the messaging subsystem is persisted, it requires to have defined hornetq-server nodes but that's not correct. E.g. when the messaging subsystem is added through the CLI, it should be marshalled even though there is no hornetq-server The XSD for the messaging subsystem is correct: minOccurs for hornetq-server element is 0. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
2
0 / 0

[JBoss JIRA] (AS7-5892) Provide access log configuration within the console

by Heiko Braun (JIRA)

Heiko Braun created AS7-5892: -------------------------------- Summary: Provide access log configuration within the console Key: AS7-5892 URL: https://issues.jboss.org/browse/AS7-5892 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-5891) Explicitly define public APIs for the OSGi subsystem

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5891: ----------------------------------- Summary: Explicitly define public APIs for the OSGi subsystem Key: AS7-5891 URL: https://issues.jboss.org/browse/AS7-5891 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.2.0.Alpha1 All subsystem modules should have an export element -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
0
0 / 0

[JBoss JIRA] (AS7-2543) JBoss Admin Console Does not allow to modify attributes like Driver

by Vimal Kansal (Created) (JIRA)

JBoss Admin Console Does not allow to modify attributes like Driver ------------------------------------------------------------------- Key: AS7-2543 URL: https://issues.jboss.org/browse/AS7-2543 Project: Application Server 7 Issue Type: Bug Components: Console Reporter: Vimal Kansal Assignee: Heiko Braun Once a datasource has been defined, I can not change the driver associated with it on console. Edit button allows editing of only JNDI name and the Connection properties. I can't change the driver. -- 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

13 years, 8 months

2
1
0 / 0

[JBoss JIRA] (AS7-4287) Console loading is slow over WAN with high ping

by Radim Kolář (JIRA)

Radim Kolář created AS7-4287: -------------------------------- Summary: Console loading is slow over WAN with high ping Key: AS7-4287 URL: https://issues.jboss.org/browse/AS7-4287 Project: Application Server 7 Issue Type: Task Components: Console Affects Versions: 7.1.1.Final Reporter: Radim Kolář Assignee: Heiko Braun Priority: Minor Console loading over WAN network with 250ms ping is very slow. it takes about 1 minute or maybe evenmore to load. I suspect that GWT application is splitted into too many small fragments with GWT splitpoints, which can make loading faster but only if ping time to server is low. On Europe -> USA link it will be very slow. -- 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

13 years, 8 months

2
5
0 / 0

[JBoss JIRA] (JGRP-1537) FILE_PING.writeToTempFile prints error without details

by Jesse Glick (JIRA)

Jesse Glick created JGRP-1537: --------------------------------- Summary: FILE_PING.writeToTempFile prints error without details Key: JGRP-1537 URL: https://issues.jboss.org/browse/JGRP-1537 Project: JGroups Issue Type: Bug Affects Versions: 3.1 Reporter: Jesse Glick Assignee: Bela Ban Priority: Minor I am getting log errors such as {code:none} SEVERE: Failed to write temporary file: /…/jgroups/…(a)....tmp {code} with no explanation of why the write failed. (Bad permissions? Low disk space?) {{writeToTempFile}} should call the two-arg overload of {{error}} and pass {{e}}. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
2
0 / 0

[JBoss JIRA] (AS7-4822) multi-threaded client can't clean up threads

by Rob Stryker (JIRA)

Rob Stryker created AS7-4822: -------------------------------- Summary: multi-threaded client can't clean up threads Key: AS7-4822 URL: https://issues.jboss.org/browse/AS7-4822 Project: Application Server 7 Issue Type: Bug Components: Domain Management Affects Versions: 7.1.0.Final Reporter: Rob Stryker Assignee: Brian Stansberry When using a multi-threaded remote management client, several threads refuse to clean up, leaving to a deadlocked / frozen thread during a call to client.close(). Simple POJP to be attached, with stack trace. Jars on the classpath are as follows: jboss-as-controller-client-7.1.0.Final.jar jboss-as-protocol-7.1.0.Final.jar jboss-dmr-1.1.1.Final.jar jboss-logging-3.1.0.GA.jar jboss-marshalling-1.3.9.GA.jar jboss-remoting-3.2.2.GA.jar jboss-remoting-3.2.7.GA.jar jboss-sasl-1.0.0.Final.jar jboss-threads-2.0.0.GA.jar xnio-api-3.0.3.GA.jar xnio-nio-3.0.3.GA.jar -- 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

13 years, 8 months

2
5
0 / 0

[JBoss JIRA] (AS7-5857) OSGi Resolution failure should be logged as an error

by David Bosschaert (JIRA)

David Bosschaert created AS7-5857: ------------------------------------- Summary: OSGi Resolution failure should be logged as an error Key: AS7-5857 URL: https://issues.jboss.org/browse/AS7-5857 Project: Application Server 7 Issue Type: Feature Request Components: OSGi Affects Versions: 7.2.0.Alpha1 Reporter: David Bosschaert Assignee: Thomas Diesler When deploying an OSGi bundle that fails to resolve, currently only a warning is logged, this should really be an ERROR. {code}13:21:31,275 WARN [org.jboss.as.osgi] (MSC service thread 1-13) JBAS011910: Cannot resolve requirements: [XPackageRequirement[atts={osgi.wiring.package=javax.servlet, version=[2.1.0,3.0.0)},[TestOSGiHttpService:1.0.0]]] 13:21:31,275 INFO [org.jboss.as.server.deployment] (MSC service thread 1-13) JBAS015970: Defer FIRST_MODULE_USE for TestOSGiHttpService_1.0.0.jar making it NEVER 13:21:31,305 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "TestOSGiHttpService_1.0.0.jar"{code} Additionally, the deployment is marked as 'deployed'. It would be better if it could be marked as 'failed' -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
1
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 November 2012