[JBoss JIRA] (AS7-6073) Initial OSGi / CDI Integration
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/AS7-6073?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler moved JBOSGI-445 to AS7-6073:
--------------------------------------------
Project: Application Server 7 (was: JBoss OSGi)
Key: AS7-6073 (was: JBOSGI-445)
Workflow: GIT Pull Request workflow (was: jira)
Component/s: CDI / Weld
OSGi
(was: CDI)
Security: (was: Public)
Fix Version/s: 7.2.0.CR1
(was: Approved / Unscheduled)
> Initial OSGi / CDI Integration
> -------------------------------
>
> Key: AS7-6073
> URL: https://issues.jboss.org/browse/AS7-6073
> Project: Application Server 7
> Issue Type: Feature Request
> Components: CDI / Weld, OSGi
> Reporter: Thomas Diesler
> Assignee: David Bosschaert
> Fix For: 7.2.0.CR1
>
>
> Provide an example test that shows CDI integration
--
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, 5 months
[JBoss JIRA] (AS7-5558) More useful error messages when management operations can't be found
by Brian Stansberry (JIRA)
Brian Stansberry created AS7-5558:
-------------------------------------
Summary: More useful error messages when management operations can't be found
Key: AS7-5558
URL: https://issues.jboss.org/browse/AS7-5558
Project: Application Server 7
Issue Type: Enhancement
Components: Domain Management
Reporter: Brian Stansberry
Fix For: 7.2.0.CR1
When the ModelController attempts to find the OperationStepHandler for a given operation + address, it needs to handle failure more intelligently. Instead of providing a one-size fits all exception, it should try to determine why the OSH couldn't be found and tailor the exception accordingly. Specifically, clarify whether the problem is the address is invalid or the operation name is invalid, and if it's the address that's invalid, clarify the point in the resource tree where the address goes wrong.
For example, a user attempting to administer a server that has already been shut down gets this fairly useless exception:
Error loading VM metrics
Unexpected HTTP response: 500
Request
{
"operation" => "composite",
"address" => [],
"steps" => [
{
"address" => [
("host" => "master"),
("server" => "server-one"),
("core-service" => "platform-mbean"),
("type" => "memory")
],
"operation" => "read-resource",
"include-runtime" => true
},
{
"address" => [
("host" => "master"),
("server" => "server-one"),
("core-service" => "platform-mbean"),
("type" => "threading")
],
"operation" => "read-resource",
"include-runtime" => true
},
{
"address" => [
("host" => "master"),
("server" => "server-one"),
("core-service" => "platform-mbean"),
("type" => "runtime")
],
"operation" => "read-resource",
"include-runtime" => true
},
{
"address" => [
("host" => "master"),
("server" => "server-one"),
("core-service" => "platform-mbean"),
("type" => "operating-system")
],
"operation" => "read-resource",
"include-runtime" => true
}
]
}
Response
Internal Server Error
{
"outcome" => "failed",
"failure-description" => "JBAS010850: No handler for operation read-resource at address [
(\"host\" => \"master\"),
(\"server\" => \"server-one\"),
(\"core-service\" => \"platform-mbean\"),
(\"type\" => \"memory\")
]",
"rolled-back" => true
}
The reality is no resource exists at address /host=master/server=server-one. The failure message should emphasize this fact.
--
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, 5 months
[JBoss JIRA] (AS7-6062) Datasource lookup broken in domain mode
by Nicklas Karlsson (JIRA)
Nicklas Karlsson created AS7-6062:
-------------------------------------
Summary: Datasource lookup broken in domain mode
Key: AS7-6062
URL: https://issues.jboss.org/browse/AS7-6062
Project: Application Server 7
Issue Type: Bug
Components: Server
Affects Versions: 7.2.0.Alpha1
Reporter: Nicklas Karlsson
Assignee: Jason Greene
A web app with a servlet doing
System.out.println(new InitialContext().lookup("java:jboss/datasources/ExampleDS"));
returns an object when the server is run in standalone mode but throws an exception of the DS not being found when run in domain mode.
--
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, 5 months
[JBoss JIRA] (AS7-6070) Domain mode: kill an unresponsive JVM
by Dennis Reed (JIRA)
[ https://issues.jboss.org/browse/AS7-6070?page=com.atlassian.jira.plugin.s... ]
Dennis Reed moved JBPAPP6-1682 to AS7-6070:
-------------------------------------------
Project: Application Server 7 (was: JBoss Enterprise Application Platform 6)
Key: AS7-6070 (was: JBPAPP6-1682)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: 7.1.2.Final (EAP)
(was: EAP 6.0.0)
Component/s: Domain Management
(was: Consoles)
Security: (was: Public)
Fix Version/s: (was: TBD EAP 6)
Docs QE Status: (was: NEW)
> Domain mode: kill an unresponsive JVM
> -------------------------------------
>
> Key: AS7-6070
> URL: https://issues.jboss.org/browse/AS7-6070
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Domain Management
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Dennis Reed
> Assignee: Heiko Braun
>
> If an AS instance gets into a state where it cannot be controlled normally by the host controller, local OS commands must be used to kill it.
> It would be helpful to be able to kill an unresponsive JVM through the management interface.
--
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, 5 months