September 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-4615) Define a database of system modules

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-4615: ----------------------------------- Summary: Define a database of system modules Key: AS7-4615 URL: https://issues.jboss.org/browse/AS7-4615 Project: Application Server 7 Issue Type: Task Components: OSGi, Server Reporter: Thomas Diesler Assignee: Thomas Diesler The OSGi configuration supports ModuleIdentifiers. So for example {code} <capability name="javax.transaction.api"/> {code} references the JTA API module. This actually delegates to the repository implementations which in turn delegates to the ModuleIdentityArtifactProvider. If the AppServer supports the notion of multiple directories where modules can get loaded from, the ServerEnvironment should reflect that properly. I cannot just load a module on trial/error basis because we use the Repository for impact ananlysis. i.e. Find the modules/bundles that provide the transitive set of capabilities for a given set of requirements (without modifying the runtime). -- 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

1
9
0 / 0

[JBoss JIRA] (AS7-5051) Allow EE deployments to define dependency requirements with OSGi metadata

by Thomas Diesler (JIRA)

Thomas Diesler created AS7-5051: ----------------------------------- Summary: Allow EE deployments to define dependency requirements with OSGi metadata Key: AS7-5051 URL: https://issues.jboss.org/browse/AS7-5051 Project: Application Server 7 Issue Type: Task Components: OSGi Reporter: Thomas Diesler Assignee: Thomas Diesler This essentially means that you can put OSGi metadata into an EE deployment manifest, which essentially makes it an OSGi bundle. Deployment unit processing should be such that the EE bundle gets resolved according to it's defined capabilities/requirements. Subsystem processors should not need to care whether the Module was created as a result of OSGi resolution or by the ModuleSpecProcessor. This task is complete when we can do this with the EE core technologies (i.e. webapp, ejb3, cdi) -- 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

1
6
0 / 0

[JBoss JIRA] (JBRULES-3635) Can we change the encoding used in Drools by default encoding to be configured?

by 大伟张 (JIRA)

大伟张 created JBRULES-3635: ----------------------------- Summary: Can we change the encoding used in Drools by default encoding to be configured? Key: JBRULES-3635 URL: https://issues.jboss.org/browse/JBRULES-3635 Project: Drools Issue Type: Enhancement Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.0.1.FINAL Reporter: 大伟张 Assignee: Mark Proctor Can we change the encoding used in Drools by default encoding to be configured? bacause i want to use chinese charset in rule content, according to the current Mechanism of drools, i need to change system default encoding to UTF-8 or other supporting the Chinese character set, it will make impact to whole system, So we hope Drools can support set encoding. like follow method: {code:title=ByteArrayResource.java|borderStyle=solid} public Reader getReader() throws IOException { return new InputStreamReader( getInputStream()); //here can we support config encoding //return new InputStreamReader( getInputStream(), "UTF-8" ); } {code} -- 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
7
0 / 0

[JBoss JIRA] (JBCL-181) Cache getResources in all layers

by Ales Justin (Created) (JIRA)

Cache getResources in all layers -------------------------------- Key: JBCL-181 URL: https://issues.jboss.org/browse/JBCL-181 Project: JBoss ClassLoader Issue Type: Enhancement Components: ClassLoader Reporter: Ales Justin Assignee: Ales Justin Fix For: JBossCL.2.4.0.Alpha1 -- 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

3
3
0 / 0

[JBoss JIRA] (JBMESSAGING-1935) The MessagingClusterHealthMBean does not provide JMX otifications

by Doug Grove (JIRA)

Doug Grove created JBMESSAGING-1935: --------------------------------------- Summary: The MessagingClusterHealthMBean does not provide JMX otifications Key: JBMESSAGING-1935 URL: https://issues.jboss.org/browse/JBMESSAGING-1935 Project: JBoss Messaging Issue Type: Feature Request Components: Messaging Core Affects Versions: 1.4.8.SP5 Reporter: Doug Grove The MessagingClusterHealthMBean effectively shuts down JBoss Messaging on certain error conditions. Loss of connectivity to the database is one such condition. JMX notification of stop and start events should be provided so that management tools can be made aware of these events and take appropriate action. -- 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
4
0 / 0

[JBoss JIRA] (AS7-5578) Revisit handling of scanner-controlled deployments in the console

by Brian Stansberry (JIRA)

Brian Stansberry created AS7-5578: ------------------------------------- Summary: Revisit handling of scanner-controlled deployments in the console Key: AS7-5578 URL: https://issues.jboss.org/browse/AS7-5578 Project: Application Server 7 Issue Type: Sub-task Components: Console Reporter: Brian Stansberry Assignee: Heiko Braun Fix For: 7.2.0.CR1 The parent issue is resolved, meaning the problem of undeploying a scanner-controlled deployment via the CLI or console just resulting in the next scan run deploying it again is fixed. So, the console handling of such deployments should be revisited to see if the console user should be allowed to do more things. -- 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
3
0 / 0

[JBoss JIRA] (AS7-4944) Update managed server registration process

by Emanuel Muckenhuber (JIRA)

Emanuel Muckenhuber created AS7-4944: ---------------------------------------- Summary: Update managed server registration process Key: AS7-4944 URL: https://issues.jboss.org/browse/AS7-4944 Project: Application Server 7 Issue Type: Task Components: Domain Management Affects Versions: 7.1.0.Final Reporter: Emanuel Muckenhuber Assignee: Emanuel Muckenhuber Fix For: 7.2.0.Alpha1 Currently the managed server boot updates are generated when starting, leaving a window where updates might not be applied to a (starting) server. We need to change this process so that the host-controller remains locked until the registration is complete. -- 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

1
1
0 / 0

[JBoss JIRA] (AS7-5437) Failed to load messaging connections

by Heiko Braun (JIRA)

Heiko Braun created AS7-5437: -------------------------------- Summary: Failed to load messaging connections Key: AS7-5437 URL: https://issues.jboss.org/browse/AS7-5437 Project: Application Server 7 Issue Type: Feature Request Reporter: Heiko Braun profile = full {noformat} [ERROR] java.lang.IllegalArgumentException [ERROR] at org.jboss.dmr.client.ModelValue.asObject(ModelValue.java:98) [ERROR] at org.jboss.dmr.client.ModelNode.asObject(ModelNode.java:252) [ERROR] at org.jboss.as.console.client.shared.subsys.messaging.LoadJMSCmd$1.onSuccess(LoadJMSCmd.java:59) [ERROR] at org.jboss.as.console.client.shared.subsys.messaging.LoadJMSCmd$1.onSuccess(LoadJMSCmd.java:1) {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

13 years, 8 months

1
2
0 / 0

[JBoss JIRA] (AS7-5431) Unable to change server group for server configuration

by Heiko Braun (JIRA)

Heiko Braun created AS7-5431: -------------------------------- Summary: Unable to change server group for server configuration Key: AS7-5431 URL: https://issues.jboss.org/browse/AS7-5431 Project: Application Server 7 Issue Type: Feature Request Components: Console Reporter: Heiko Braun Assignee: Heiko Braun Fix For: 7.2.0.CR1 Fails with no reasonable exception -- 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

1
1
0 / 0

[JBoss JIRA] (AS7-3019) Arquillian Managed Container fails to start JBoss AS with ServiceNotFoundException

by Martin Gencur (Created) (JIRA)

Arquillian Managed Container fails to start JBoss AS with ServiceNotFoundException ---------------------------------------------------------------------------------- Key: AS7-3019 URL: https://issues.jboss.org/browse/AS7-3019 Project: Application Server 7 Issue Type: Bug Components: Test Suite Reporter: Martin Gencur Assignee: Aslak Knutsen Affects JBossAS 7.1.0.CR1-SNAPSHOT (HEAD=d9e236d - Update timeout to be more reasonable with load) When I'm starting AS with jboss-as-arquillian-container-managed (7.1.0.CR1-SNAPSHOT), I get the following exception (no configuration in standalone.xml was changed after building the distribution): 14:57:41,690 INFO [org.jboss.as] (Controller Boot Thread) JBoss AS 7.1.0.CR1-SNAPSHOT "Tesla" started in 3547ms - Started 131 of 200 services (68 services are passive or on-demand) 14:57:42,037 ERROR [org.jboss.as.controller.management-operation] (pool-1-thread-1) JBAS014612: Operation ("read-attribute") failed - address: ({ "socket-binding-group" => "standard-sockets", "socket-binding" => "undefined" }): org.jboss.msc.service.ServiceNotFoundException: Service service jboss.binding.undefined not found at org.jboss.msc.service.ServiceContainerImpl.getRequiredService(ServiceContainerImpl.java:447) [jboss-msc-1.0.1.GA.jar:] at org.jboss.as.server.services.net.BindingMetricHandlers$AbstractBindingMetricsHandler$1.execute(BindingMetricHandlers.java:66) [jboss-as-server-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:359) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:254) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:190) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.server.services.net.BindingMetricHandlers$AbstractBindingMetricsHandler.execute(BindingMetricHandlers.java:76) [jboss-as-server-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.server.services.net.BindingMetricHandlers$BoundAddressHandler.execute(BindingMetricHandlers.java:106) [jboss-as-server-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.operations.global.GlobalOperationHandlers$ReadAttributeHandler.doExecute(GlobalOperationHandlers.java:452) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractMultiTargetHandler.execute(GlobalOperationHandlers.java:974) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:359) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:254) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:190) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:432) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:359) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:254) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:190) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:119) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler.doExecute(ModelControllerClientOperationHandler.java:121) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:98) [jboss-as-controller-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$3$1.doExecute(AbstractMessageHandler.java:268) [jboss-as-protocol-7.1.0.CR1-SNAPSHOT.jar:] at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:424) [jboss-as-protocol-7.1.0.CR1-SNAPSHOT.jar:] at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_21] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_21] at java.lang.Thread.run(Thread.java:619) [:1.6.0_21] Starting the same AS manually works fine. -- 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

5
4
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 September 2012