[JBoss JIRA] (AS7-3780) Expose Resource Adapter deployment information
by Heiko Braun (JIRA)
Heiko Braun created AS7-3780:
--------------------------------
Summary: Expose Resource Adapter deployment information
Key: AS7-3780
URL: https://issues.jboss.org/browse/AS7-3780
Project: Application Server 7
Issue Type: Feature Request
Components: Console
Reporter: Heiko Braun
Assignee: Heiko Braun
Fix For: 7.2.0.Alpha1
Attachments: multiple-full.rar, multiple-full.xml
It would be great if the console could present a view of a resource adapter deployment with all its properties.
If you deploy the attached .rar and insert the configuration in the subsystem you will be able to see the entire tree of all the resource adapter components.
A connection-definition is almost the same as a data source deployment, so you can probably re-use a lot of code from there.
The best way would be a tree-like structure:
ResourceAdapter
|
+- Connection definitions
|
+- JNDI name 1 (first <connection-definition>)
| |
| +- Pool
|
+- JNDI name 2 (second <connection-definition>)
|
+- Admin objects
|
+- JNDI name 1 (first <admin-object>)
--
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, 10 months
[JBoss JIRA] (AS7-4422) Usability enhancement - make the list of deployments linkable
by Burr Sutter (JIRA)
Burr Sutter created AS7-4422:
--------------------------------
Summary: Usability enhancement - make the list of deployments linkable
Key: AS7-4422
URL: https://issues.jboss.org/browse/AS7-4422
Project: Application Server 7
Issue Type: Enhancement
Reporter: Burr Sutter
Attachments: Screen Shot 2012-04-05 at 6.55.18 PM.png
AS7/EAP6's Browser based web console is a wonderful tool for interacting with my local server. I am often reviewing the Deployments under Runtime section to see if my application dropped into standalone/deployments deployed successfully without closely watching the logs. Typically, if I am refreshing the Admin Page to see if the deployment happened, the next thing I wish to do is hit the applications URL - ideally, the deployments table would make the name of the application linked - at the moment it provides the finger mouse pointer which suggests it is clickable.
--
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, 10 months
[JBoss JIRA] (AS7-4321) OSGi management console needs inspector of wiring
by Heiko Braun (JIRA)
[ https://issues.jboss.org/browse/AS7-4321?page=com.atlassian.jira.plugin.s... ]
Heiko Braun updated AS7-4321:
-----------------------------
Fix Version/s: No Release
(was: 7.2.0.CR1)
> OSGi management console needs inspector of wiring
> -------------------------------------------------
>
> Key: AS7-4321
> URL: https://issues.jboss.org/browse/AS7-4321
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Console, OSGi
> Affects Versions: 7.1.1.Final
> Environment: Mac OS X 10.7.3
> Reporter: Tim Diekmann
> Assignee: David Bosschaert
> Fix For: No Release
>
>
> The OSGi management console for AS 7 needs a viewer of the current wiring. The console log showed the following error on start of the bundle and there is no way to inspect the wiring to see where the problem lies and how to solve it. There is some inconsistency in the deployment, but how to find out what?
> {code}
> 00:09:14,480 ERROR [org.mortbay.log] (HttpManagementService-threads - 3) Error starting handlers: java.lang.IncompatibleClassChangeError: Class org.eclipse.equinox.http.servlet.HttpServiceServlet does not implement the requested interface javax.servlet.Servlet
> at org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet.init(HttpServerManager.java:294)
> at org.mortbay.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:431)
> at org.mortbay.jetty.servlet.ServletHolder.doStart(ServletHolder.java:263)
> at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:681)
> at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
> at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:517)
> at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:130)
> at org.mortbay.jetty.Server.doStart(Server.java:224)
> at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at org.eclipse.equinox.http.jetty.internal.HttpServerManager.updated(HttpServerManager.java:109)
> at org.eclipse.equinox.http.jetty.internal.Activator.start(Activator.java:60)
> at org.jboss.osgi.framework.internal.HostBundleState.transitionToActive(HostBundleState.java:300)
> at org.jboss.osgi.framework.internal.HostBundleState.startInternal(HostBundleState.java:223)
> at org.jboss.osgi.framework.internal.AbstractBundleState.start(AbstractBundleState.java:488)
> at org.jboss.as.osgi.parser.BundleRuntimeHandler.handleOperation(BundleRuntimeHandler.java:132)
> at org.jboss.as.osgi.parser.BundleRuntimeHandler.executeRuntimeStep(BundleRuntimeHandler.java:89)
> at org.jboss.as.controller.AbstractRuntimeOnlyHandler$1.execute(AbstractRuntimeOnlyHandler.java:90)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:387)
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:274)
> at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:202)
> at org.jboss.as.controller.ModelControllerImpl$DefaultPrepareStepHandler.execute(ModelControllerImpl.java:461)
> at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:387)
> at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:274)
> at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:202)
> at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:121)
> at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:304)
> at org.jboss.as.controller.ModelControllerImpl$1.execute(ModelControllerImpl.java:294)
> at org.jboss.as.domain.http.server.DomainApiHandler.processRequest(DomainApiHandler.java:294)
> at org.jboss.as.domain.http.server.DomainApiHandler.doHandle(DomainApiHandler.java:201)
> at org.jboss.as.domain.http.server.DomainApiHandler.handle(DomainApiHandler.java:208)
> at org.jboss.as.domain.http.server.security.SubjectAssociationHandler.handle(SubjectAssociationHandler.java:51)
> at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78)
> at org.jboss.sun.net.httpserver.AuthFilter.doFilter(AuthFilter.java:69)
> at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81)
> at org.jboss.sun.net.httpserver.ServerImpl$Exchange$LinkHandler.handle(ServerImpl.java:710)
> at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:78)
> at org.jboss.as.domain.http.server.RealmReadinessFilter.doFilter(RealmReadinessFilter.java:54)
> at org.jboss.com.sun.net.httpserver.Filter$Chain.doFilter(Filter.java:81)
> at org.jboss.sun.net.httpserver.ServerImpl$Exchange.run(ServerImpl.java:682)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [classes.jar:1.6.0_29]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [classes.jar:1.6.0_29]
> at java.lang.Thread.run(Thread.java:680) [classes.jar:1.6.0_29]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> {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
13 years, 10 months
[JBoss JIRA] (AS7-5082) Add missing jgroups config options in the console
by Heiko Braun (JIRA)
Heiko Braun created AS7-5082:
--------------------------------
Summary: Add missing jgroups config options in the console
Key: AS7-5082
URL: https://issues.jboss.org/browse/AS7-5082
Project: Application Server 7
Issue Type: Feature Request
Components: Console
Reporter: Heiko Braun
Assignee: Heiko Braun
Fix For: 7.2.0.Alpha1
The GUI cannot be used because:
1. The available protocols to add are hard-coded, and TCPPING is not included.
2. Neither is RSVP, which is in the standard configurations, so you cannot even recreate a copy of an existing stack.
3. "socket-binding" is a required field when adding a protocol, when it is only used on a couple of them
4. You can't re-order the protocols. If you want to change one, you get to blow it all away and start from scratch
--
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, 10 months
[JBoss JIRA] (AS7-5023) Socket binding not marked as mandatory in console generates StringIndexOutOfBoundsException
by Akram Ben Aissi (JIRA)
Akram Ben Aissi created AS7-5023:
------------------------------------
Summary: Socket binding not marked as mandatory in console generates StringIndexOutOfBoundsException
Key: AS7-5023
URL: https://issues.jboss.org/browse/AS7-5023
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.2.Final (EAP)
Reporter: Akram Ben Aissi
Assignee: Heiko Braun
While editing a server configuration in the Server Configurations tab, the socket binding value is not selected and neither marked as mandatory.
So the Save button is active and triggers a call with an invalid empty value for this field which leads to the following exception:
[Host Controller] 16:00:40,005 ERROR [org.jboss.as.controller.management-operation] (HttpManagementService-threads - 26) JBAS014612: Operation ("write-attribute") failed - address: ([
[Host Controller] ("host" => "master"),
[Host Controller] ("server-config" => "server-three")
[Host Controller] ]): java.lang.StringIndexOutOfBoundsException: String index out of range: 0
[Host Controller] at java.lang.String.charAt(Unknown Source) [rt.jar:1.7.0_01]
[Host Controller] at org.jboss.as.controller.PathElement.<init>(PathElement.java:103) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
[Host Controller] at org.jboss.as.controller.PathElement.pathElement(PathElement.java:68) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
--
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, 10 months