[JBoss JIRA] (AS7-5100) JMX client does not work inside web application (servlet)
by Francois Billard (JIRA)
Francois Billard created AS7-5100:
-------------------------------------
Summary: JMX client does not work inside web application (servlet)
Key: AS7-5100
URL: https://issues.jboss.org/browse/AS7-5100
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.1.Final, 7.0.2.Final
Environment: JBoss 7.1.1 on Windows XP, Operating system should not doing impact
Reporter: Francois Billard
a simple jmx client connection to get an attribute on a remote MBeanServer does not work and produce errors at runtime :
Failed to retrieve RMIServer stub: javax.naming.NameNotFoundException: rmi://192.168.47.23:50000/jmxrmi -- service jboss.naming.context.java.rmi:."192.168.47.23:50000".jmxrmi
and
Caused by: javax.naming.NameNotFoundException: rmi://192.168.47.23:50000/jmxrmi -- service jboss.naming.context.java.rmi:."192.168.47.23:50000".jmxrmi
--
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
11 years, 10 months
[JBoss JIRA] (AS7-2171) Revisit deployment triggering subsystem startup
by Thomas Diesler (Created) (JIRA)
Revisit deployment triggering subsystem startup
-----------------------------------------------
Key: AS7-2171
URL: https://issues.jboss.org/browse/AS7-2171
Project: Application Server 7
Issue Type: Task
Components: OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Currently the RestEasyIntegrationTestCase deploys a JAXRS endpoint that integrates with an OSGi service. The endoint deployment does not trigger the OSGi subsystem to start up, but depends on the compendium being deployed. The compendium gets deployed during OSGi subsystem startup.
There is currently no way for a deployment foo to declare a dependency on deployment bar when bar gets deployed during subsystem startup, which gets triggered by deployment foo.
OSGi has the notion of dynamic package import which seems to be required here for non-osgi deployments
--
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
11 years, 10 months