[JBoss JIRA] (AS7-3864) CLI: unable to specify operation headers in generic operations
by Dominik Pospisil (JIRA)
Dominik Pospisil created AS7-3864:
-------------------------------------
Summary: CLI: unable to specify operation headers in generic operations
Key: AS7-3864
URL: https://issues.jboss.org/browse/AS7-3864
Project: Application Server 7
Issue Type: Bug
Reporter: Dominik Pospisil
It seems to me that it is not possible to specify operation headers in generic operation executions. This is required if a user choose to use low-level operation and need to specify roll-out plans, allow-resource-service-restart or other flags.
Something like this should be possible:
[standalone@localhost:9999 /] /subsystem=datasources/data-source=TestDS:disable(headers={"allow-resource-service-restart" => true})
Operation 'disable' does not expect any property.
[standalone@localhost:9999 /] /subsystem=datasources/data-source=TestDS:disable --headers={"allow-resource-service-restart" => true})
'disable --headers=' is not a valid operation name.
--
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, 4 months
[JBoss JIRA] (AS7-2947) org.jboss.as.server.mgmt.HttpManagementService.start leads to NPE
by Richard Opalka (Created) (JIRA)
org.jboss.as.server.mgmt.HttpManagementService.start leads to NPE
-----------------------------------------------------------------
Key: AS7-2947
URL: https://issues.jboss.org/browse/AS7-2947
Project: Application Server 7
Issue Type: Bug
Components: Server
Reporter: Richard Opalka
Assignee: Brian Stansberry
Fix For: 7.1.0.CR1
08:53:58,375 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC00001: Failed to start service jboss.serverManagement.controller.management.http: org.jboss.msc.service.StartException in service jboss.serverManagement.controller.management.http: Failed to start serverManagement socket
at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:189) [jboss-as-server-7.1.0.CR1-SNAPSHOT.jar:]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824) [jboss-msc-1.0.1.GA.jar:]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759) [jboss-msc-1.0.1.GA.jar:]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_29]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_29]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_29]
Caused by: java.lang.NullPointerException
at sun.nio.ch.Util.atBugLevel(Util.java:448) [:1.6.0_29]
at sun.nio.ch.SelectorImpl.<init>(SelectorImpl.java:40) [:1.6.0_29]
at sun.nio.ch.EPollSelectorImpl.<init>(EPollSelectorImpl.java:47) [:1.6.0_29]
at sun.nio.ch.EPollSelectorProvider.openSelector(EPollSelectorProvider.java:18) [:1.6.0_29]
at java.nio.channels.Selector.open(Selector.java:209) [:1.6.0_29]
at org.jboss.sun.net.httpserver.ServerImpl.<init>(ServerImpl.java:147)
at org.jboss.sun.net.httpserver.HttpServerImpl.<init>(HttpServerImpl.java:54)
at org.jboss.sun.net.httpserver.DefaultHttpServerProvider.createHttpServer(DefaultHttpServerProvider.java:38)
at org.jboss.com.sun.net.httpserver.HttpServer.create(HttpServer.java:147)
at org.jboss.as.domain.http.server.ManagementHttpServer.create(ManagementHttpServer.java:105)
at org.jboss.as.server.mgmt.HttpManagementService.start(HttpManagementService.java:154) [jboss-as-server-7.1.0.CR1-SNAPSHOT.jar:]
... 5 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, 4 months
[JBoss JIRA] (AS7-3814) CommandContext.buildRequest(line) throws OperationFormatException for wrong reason
by Alexey Loubyansky (JIRA)
Alexey Loubyansky created AS7-3814:
--------------------------------------
Summary: CommandContext.buildRequest(line) throws OperationFormatException for wrong reason
Key: AS7-3814
URL: https://issues.jboss.org/browse/AS7-3814
Project: Application Server 7
Issue Type: Bug
Components: CLI
Affects Versions: 7.1.0.Final
Reporter: Alexey Loubyansky
Assignee: Alexey Loubyansky
Fix For: 7.1.1.Final
Operation requests aren't affected.
The method translates commands to operation requests. Of course, the command handler is required to implement OperationCommand interface. But the if condition is wrong, i.e. instead of throwing an exception in case the handler doesn't implement the interface, it throws an exception if the handler does implement the interface.
This is a new and not yet publicly advertised functionality, so nobody will suffer from this bug.
--
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, 4 months
[JBoss JIRA] (AS7-3847) Non-standard format of IPv6 address(-es) in LOG files
by jaikiran pai (JIRA)
[ https://issues.jboss.org/browse/AS7-3847?page=com.atlassian.jira.plugin.s... ]
jaikiran pai commented on AS7-3847:
-----------------------------------
For the JBossWeb part, Richard seems to have a filed a separate JIRA here https://issues.jboss.org/browse/AS7-3851 which is assigned to Remy.
> Non-standard format of IPv6 address(-es) in LOG files
> -----------------------------------------------------
>
> Key: AS7-3847
> URL: https://issues.jboss.org/browse/AS7-3847
> Project: Application Server 7
> Issue Type: Bug
> Affects Versions: 7.1.0.Final
> Reporter: Pavel Janousek
>
> There are several places where some IPv6 address related info is logged. The format of a such info is formally correct, but used format is against [RFC-5952|http://tools.ietf.org/html/rfc5952] - this RFC has status of +Proposed standard+ and I don't know any software product which doesn't follow it (at least by-default).
> I think in enterprise product we should not violate this RFC.
> I'm mentioning about LOG messages like:
> {code}
> 15:14:15,985 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on /0:0:0:0:0:0:0:1%1:9999
>
> 15:14:15,990 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on localhost6.localdomain6/0:0:0:0:0:0:0:1%1:4447
> {code}
> In both lines IPv6 address should be stretched to "::1" string.
> More "funny" and obfuscated version of the same LOG content is LOG line like this:
> {code}
> 15:14:14,363 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-1) Starting Coyote HTTP/1.1 on http--0%3A0%3A0%3A0%3A0%3A0%3A0%3A1%251-8080
> {code}
> But both version of the issue is almost unreadable by human.
--
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, 4 months
[JBoss JIRA] (AS7-3723) Add support to weld for a non-standard mode that only scans for classes with annotations
by Stuart Douglas (JIRA)
Stuart Douglas created AS7-3723:
-----------------------------------
Summary: Add support to weld for a non-standard mode that only scans for classes with annotations
Key: AS7-3723
URL: https://issues.jboss.org/browse/AS7-3723
Project: Application Server 7
Issue Type: Feature Request
Components: CDI / Weld
Reporter: Stuart Douglas
Assignee: Stuart Douglas
Fix For: 7.1.1.Final
On 12 Feb 2012, at 04:01, Stuart Douglas wrote:
I have actually toyed with the idea of including this as an AS7 extension.
I was thinking something like this in the beans.xml file:
<as7:only-scan-annotated enabled="true">
<as7:annotation>org.jboss.seam.ExtensionManaged</as7:annotation>
<as7:annotation>com.acme.SomeOtherAnnotation</as7:annotation>
</as7:only:scan-annotation>
This setting would only be applied to the bean archive that has it in its beans.xml (so 3rd party libraries would function properly), and the set of annotations to scan would be merged and applied to all bean archives that use this setting (so if deltaspike defines ExtensionManaged the use would also not have to add that the list of annotations to scan, it would be picked up from the beans.xml file).
This is actually relatively easy to implement, and I could probably get it into AS 7.1.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
14 years, 4 months