January 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-3300) OSGi remains visible from runtime view after removing the OSGi subsystem

by David Bosschaert (JIRA)

David Bosschaert created AS7-3300: ------------------------------------- Summary: OSGi remains visible from runtime view after removing the OSGi subsystem Key: AS7-3300 URL: https://issues.jboss.org/browse/AS7-3300 Project: Application Server 7 Issue Type: Bug Components: Console Affects Versions: 7.1.0.CR1b Reporter: David Bosschaert Assignee: Heiko Braun Priority: Minor The OSGi menu item (under Runtime Operations) on the Runtime view remains visible after the OSGi subsystem is removed. -- 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, 3 months

3
7
0 / 0

[JBoss JIRA] (AS7-3362) Provide OSGi Tech Preview test integration

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-3362: ----------------------------------- Summary: Provide OSGi Tech Preview test integration Key: AS7-3362 URL: https://issues.jboss.org/browse/AS7-3362 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler Fix For: 7.1.0.Final AS7-3036 removed a bunch of functionality from the AS code base that now lives in the JBOSGi umbrella project. It should be possible to describe the set of tech preview functionality in terms of automated tests that are executed from the jbosgi testsuite. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (AS7-2848) JacORB management attributes should be read-write

by David Bosschaert (Created) (JIRA)

JacORB management attributes should be read-write ------------------------------------------------- Key: AS7-2848 URL: https://issues.jboss.org/browse/AS7-2848 Project: Application Server 7 Issue Type: Task Components: Server Reporter: David Bosschaert Assignee: Jason Greene All the configuration values for jacorb are read-only. This means that the console can display them but not edit them. They should be made read-write. If the subsystem cannot react to value changes it can signal this through a 'restart required' response. {code}subsystem=jacorb] :read-resource-description(recursive=true) { "outcome" => "success", "result" => { "description" => "The JacORB subsystem configuration.", "head-comment-allowed" => true, "tail-comment-allowed" => true, "namespace" => "urn:jboss:domain:jacorb:1.1", "attributes" => { "name" => { "type" => STRING, "description" => "The name of the running ORB.", "expressions-allowed" => false, "nillable" => true, "default" => "JBoss", "min-length" => 1L, "max-length" => 2147483647L, "access-type" => "read-only", "storage" => "configuration" }, "print-version" => { "type" => STRING, "description" => "Indicates whether the version number should be printed during ORB startup (on) or not (off).", "expressions-allowed" => false, "nillable" => true, "default" => "off", "min-length" => 1L, "max-length" => 2147483647L, "access-type" => "read-only", "storage" => "configuration" }, ... and so on... {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, 3 months

7
10
0 / 0

[JBoss JIRA] (AS7-2276) Scripts usability: --help option need not start Java

by Radoslav Husar (Created) (JIRA)

Scripts usability: --help option need not start Java ---------------------------------------------------- Key: AS7-2276 URL: https://issues.jboss.org/browse/AS7-2276 Project: Application Server 7 Issue Type: Bug Components: Scripts Affects Versions: 7.1.0.Alpha1 Environment: all Reporter: Radoslav Husar Assignee: Brian Stansberry It is not necessary to start a JVM to print out raw text on the console. This could be easily handled by the script and print the options in a clean and fast way. {code} [rhusar@rhusar jboss-as-7.0.2.Final]$ time ./bin/standalone.sh --help ========================================================================= JBoss Bootstrap Environment JBOSS_HOME: /home/rhusar/Download/jboss-as-7.0.2.Final JAVA: /home/rhusar/tools/jdk1.6.0/bin/java JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true ========================================================================= 10:36:43,613 INFO [org.jboss.modules] JBoss Modules version 1.0.2.GA 10:36:43,965 INFO [stdout] Usage: ./standalone.sh [args...] 10:36:43,966 INFO [stdout] 10:36:43,968 INFO [stdout] where args include: 10:36:43,968 INFO [stdout] -b=<value> Set system property jboss.bind.address to the given value 10:36:43,969 INFO [stdout] -b <value> Set system property jboss.bind.address to the given value 10:36:43,969 INFO [stdout] -b<interface>=<value> Set system property jboss.bind.address.<interface> to the given value 10:36:43,969 INFO [stdout] -D<name>[=<value>] Set a system property 10:36:43,970 INFO [stdout] -h Display this message and exit 10:36:43,970 INFO [stdout] --help Display this message and exit 10:36:43,970 INFO [stdout] -P=<url> Load system properties from the given url 10:36:43,970 INFO [stdout] -P <url> Load system properties from the given url 10:36:43,971 INFO [stdout] --properties=<url> Load system properties from the given url 10:36:43,972 INFO [stdout] --server-config=<config> Name of the server configuration file to use (default is "standalone.xml") 10:36:43,972 INFO [stdout] -V Print version and exit 10:36:43,972 INFO [stdout] -v Print version and exit 10:36:43,973 INFO [stdout] --version Print version and exit 10:36:43,973 INFO [stdout] real 0m1.071s user 0m0.718s sys 0m0.077s {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, 3 months

5
4
0 / 0

[JBoss JIRA] Created: (AS7-1846) JMS connection factories bad configuration

by Martin Vecera (JIRA)

JMS connection factories bad configuration ------------------------------------------ Key: AS7-1846 URL: https://issues.jboss.org/browse/AS7-1846 Project: Application Server 7 Issue Type: Bug Components: JMS Affects Versions: 7.0.1.Final, 7.1.0.Alpha1 Reporter: Martin Vecera Assignee: Clebert Suconic Connection factories (ConnectionFactory and JmsXA) are configured in the following way in standalone*.xml: <entries> <entry name="java:/ConnectionFactory"/> </entries> <entries> <entry name="java:/JmsXA"/> </entries> That makes them to be bound under java:/java:/ConnectionFactory and java:/java:/JmsXA. RemoteConnectionFactory is configured properly and removing the java:/ prefix fixes the binding location. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
6
0 / 0

[JBoss JIRA] (AS7-2500) The CLI no longer shows the ssl attribute of a connector

by Rich Raposa (Created) (JIRA)

The CLI no longer shows the ssl attribute of a connector -------------------------------------------------------- Key: AS7-2500 URL: https://issues.jboss.org/browse/AS7-2500 Project: Application Server 7 Issue Type: Bug Components: CLI Reporter: Rich Raposa Assignee: Alexey Loubyansky When adding a new connector, tab completion shows ssl as a valid attribute and the following command works: /subsystem=web/connector=https:add(socket-binding=https,scheme=https,protocol="HTTP/1.1",secure=true,ssl={}) But read-resource does not show ssl anymore: [standalone@localhost:9999 /] /subsystem=web/connector=https:read-resource(recursive=true) { "outcome" => "success", "result" => { "enable-lookups" => false, "enabled" => true, "max-post-size" => 2097152, "max-save-post-size" => 4096, "protocol" => "HTTP/1.1", "redirect-port" => 8443, "scheme" => "https", "secure" => true, "socket-binding" => "https", "virtual-server" => undefined } } Also, there is no way in the CLI to add/modify the attributes of ssl (like the certificate-key-file and password): [standalone@localhost:9999 /] /subsystem=web/connector=https:write-attribute(name=ssl,value={"password"=>"changeit","certificate-key-file"=>".keystore"}) { "outcome" => "failed", "failure-description" => "No known attribute called ssl", "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, 3 months

9
12
0 / 0

[JBoss JIRA] Created: (JBAS-8412) Algorithms for generating server names

by Brian Stansberry (JIRA)

Algorithms for generating server names -------------------------------------- Key: JBAS-8412 URL: https://jira.jboss.org/browse/JBAS-8412 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry Fix For: 7.0.0.M1 Right now we're identifying servers by the static "name" attribute value in the host.xml server element. We need pluggable algorithms for other mechanisms to come up with a name, particularly for cloud use cases. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (AS7-793) Expose thread queue usage/metrics

by Heiko Braun (JIRA)

Expose thread queue usage/metrics --------------------------------- Key: AS7-793 URL: https://issues.jboss.org/browse/AS7-793 Project: Application Server 7 Issue Type: Feature Request Components: Domain Management Reporter: Heiko Braun Assignee: Brian Stansberry I am missing things like current queue size, etc. basically anything that gives you an idea of the load on the system -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
6
0 / 0

[JBoss JIRA] (AS7-2878) Properly expose JCA pool properties

by Heiko Braun (Created) (JIRA)

Properly expose JCA pool properties ----------------------------------- Key: AS7-2878 URL: https://issues.jboss.org/browse/AS7-2878 Project: Application Server 7 Issue Type: Bug Components: Domain Management, JCA Reporter: Heiko Braun Assignee: Stefano Maestri Fix For: 7.1.0.CR1 they need to be subresources: {noformat} [INFO] { [INFO] "operation" => "add", [INFO] "address" => [ [INFO] ("subsystem" => "jca"), [INFO] ("workmanager" => "default"), [INFO] ("short-running-threads" => "default-short-running-threads"), [INFO] ("properties" => "property_name") [INFO] ], [INFO] "value" => "property_value", [INFO] "boot-time" => false [INFO] } [ERROR] 2011-12-01 16:09:13,299 [ERROR] On Thu Dec 01 16:09:13 CET 2011, MessageCenter received Failed: Create property property_name [ERROR] 2011-12-01 16:09:13,300 [ERROR] Message{conciseMessage='Failed: Create property property_name', detailedMessage='{ [ERROR] "outcome" => "failed", [ERROR] "failure-description" => "JBAS014739: No handler for add at address [ [ERROR] (\"subsystem\" => \"jca\"), [ERROR] (\"workmanager\" => \"default\"), [ERROR] (\"short-running-threads\" => \"default-short-running-threads\"), [ERROR] (\"properties\" => \"property_name\") [ERROR] ]", [ERROR] "rolled-back" => true, [ERROR] "response-headers" => {"process-state" => "reload-required"} [ERROR] }', fired=Thu Dec 01 16:09:13 CET 2011, severity=Error, options=[]} {noformat} -- 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, 3 months

8
9
0 / 0

[JBoss JIRA] (AS7-3340) NPE during stop of service jboss.jacorb.poa-service.rootpoa

by Stefan Guilhen (JIRA)

[ https://issues.jboss.org/browse/AS7-3340?page=com.atlassian.jira.plugin.s... ] Stefan Guilhen commented on AS7-3340: ------------------------------------- BTW, what is the jacorb version used by EAP? I'm trying to reproduce this using the community version and I never see this exception. > NPE during stop of service jboss.jacorb.poa-service.rootpoa > ----------------------------------------------------------- > > Key: AS7-3340 > URL: https://issues.jboss.org/browse/AS7-3340 > Project: Application Server 7 > Issue Type: Bug > Components: IIOP > Affects Versions: 7.1.0.CR1b > Reporter: Pavel Janousek > Assignee: Stefan Guilhen > Priority: Critical > Fix For: 7.1.0.Final > > > There is randomly occured NPE when stopping EAP a bit quickly after it started. > {code} > 15:55:17,151 ERROR [org.jboss.as] (Controller Boot Thread) JBoss EAP 6.0.0.Alpha2 (AS 7.1.0.CR1-redhat-1) started (with errors) in 8066ms - Started 132 of 222 services (20 services failed or missing dependencies, 68 services are passive or on-demand) > ^C15:55:19,867 INFO [org.jboss.as.messaging] (MSC service thread 1-1) JBAS011605: Unbound messaging object to jndi name java:/queue/test > 15:55:19,870 INFO [org.jboss.as.osgi] (MSC service thread 1-8) JBAS011921: Stopping OSGi Framework > 15:55:19,876 INFO [org.jboss.as.messaging] (MSC service thread 1-7) JBAS011605: Unbound messaging object to jndi name java:/RemoteConnectionFactory > 15:55:19,878 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS] > 15:55:19,888 INFO [org.jboss.as.logging] JBAS011503: Restored bootstrap log handlers > 15:55:19,897 INFO [jacorb.poa] POA IRPOA destroyed > 15:55:19,898 INFO [jacorb.poa] POA Naming destroyed > 15:55:19,906 WARN [org.jboss.msc.service.fail] MSC000004: Failure during stop of service jboss.jacorb.poa-service.rootpoa: java.lang.NullPointerException > at org.jacorb.poa.POA.destroy(Unknown Source) > at org.jboss.as.jacorb.service.CorbaPOAService.stop(CorbaPOAService.java:187) > at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:1909) [jboss-msc-1.0.1.GA-redhat-1.jar:1.0.1.GA-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:1872) [jboss-msc-1.0.1.GA-redhat-1.jar:1.0.1.GA-redhat-1] > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_27] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_27] > at java.lang.Thread.run(Thread.java:662) [:1.6.0_27] > 15:55:19,910 INFO [jacorb.orb] prepare ORB for shutdown... > {code} > As you can see above, I hit Ctrl-C in two seconds after start is done. NPE isn't occurred every time and I didn't see it anytime when EAP was running for a longer time (let say 10 seconds and more). -- 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, 3 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 January 2012