[JBoss JIRA] (AS7-669) Missing error message for composite operations
by David Lloyd (Commented) (JIRA)
[ https://issues.jboss.org/browse/AS7-669?page=com.atlassian.jira.plugin.sy... ]
David Lloyd commented on AS7-669:
---------------------------------
Is this issue resolved?
> Missing error message for composite operations
> ----------------------------------------------
>
> Key: AS7-669
> URL: https://issues.jboss.org/browse/AS7-669
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: 7.0.0.Beta3
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: 7.1.0.Beta1
>
>
> Heiko Braun reports:
> I don't see any error details when composite op's fail.
> Is it just me or a general problem?
> Request
> {
> "operation" => "composite",
> "address" => [],
> "steps" => [
> {
> "operation" => "write-attribute",
> "address" => [
> ("host" => "local"),
> ("server-config" => "server-one")
> ],
> "name" => "socket-binding-group",
> "value" => "standard-sockets"
> },
> {
> "operation" => "write-attribute",
> "address" => [
> ("host" => "local"),
> ("server-config" => "server-one")
> ],
> "name" => "socket-binding-port-offset",
> "value" => 0
> }
> ],
> "child-type" => undefined
> }
>
> Response
>
> Internal Server Error
--
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, 8 months
[JBoss JIRA] Created: (JBAS-8137) Simple start and stop scripts
by Brian Stansberry (JIRA)
Simple start and stop scripts
-----------------------------
Key: JBAS-8137
URL: https://jira.jboss.org/browse/JBAS-8137
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Domain Management
Reporter: Brian Stansberry
Fix For: Unscheduled
This JIRA is based on feedback we received after the Andiamo BOF at JBoss World 2010:
>> I would like to see all the configurations that normally get set on the
>> command line (JBoss opts and system props) moved to a config file so all
>> that is ever required to start a Jboss instance is simply "run.sh
>> /<configuration>/".
The domain and host configuration files we'll introduce with AS 7 should encapsulate most things that are currently passed in via -D or the arguments to main(). If we start adding additional command line options that need to be processed before the domain/host configuration files are read, we should make it easy to set those in a configuration file (perhaps a simple properties file).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Created: (JBAS-9306) Expose address of DC as runtime attributes on the HC
by Heiko Rupp (JIRA)
Expose address of DC as runtime attributes on the HC
----------------------------------------------------
Key: JBAS-9306
URL: https://issues.jboss.org/browse/JBAS-9306
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: Domain Management
Reporter: Heiko Rupp
Currently there is no way to learn about the http management port of the DC from a slave's host.xml or runtime.
17:02:31] <pilhuhn> I am reading host.xml to find the DC, so that I can contact its http port for e.g. querying the /socket-binding-group if the one on the host is undefined
[17:02:41] <+bstansberry> I don't want it in the config, but I'm ok with adding it as a runtime attribute
[17:04:13] <pilhuhn> bstansberry fine with me when I can query the HC for the http port of the DC
[17:04:46] <+bstansberry> pilhuhn: the native API port should be a runtime attribute as well
[17:04:51] <+bstansberry> yes please
[17:05:04] <+bstansberry> what i mean by that is we should expose it as a runtime attribute
17:05:49] <+bstansberry> the config bit is an instruction to the HC, but we are going to add alternatives, e.g. a multicast address
[17:06:55] <+bstansberry> so using the config will not be a reliable source; runtime can be
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months
[JBoss JIRA] Created: (JBAS-8952) Fix the testsuite/integration testcase failures
by jaikiran pai (JIRA)
Fix the testsuite/integration testcase failures
-----------------------------------------------
Key: JBAS-8952
URL: https://issues.jboss.org/browse/JBAS-8952
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: Test Suite
Environment: JBoss AS7 master
Reporter: jaikiran pai
Assignee: Shelly McGowan
Fix For: 7.0.0.CR1
As reported in the mailing list http://lists.jboss.org/pipermail/jboss-as7-dev/2011-March/000759.html thread, the "testsuite/integration" tests are failing with a CCE in JSFUnitApplicationArchiveProcessor:
{code}
Caused by: java.lang.ClassCastException: org.jboss.shrinkwrap.impl.base.spec.ResourceAdapterArchiveImpl cannot be cast to org.jboss.shrinkwrap.api.spec.WebArchive
at org.jboss.jsfunit.arquillian.JSFUnitApplicationArchiveProcessor.process(JSFUnitApplicationArchiveProcessor.java:41)
at org.jboss.arquillian.impl.ClientDeploymentGenerator.applyApplicationProcessors(ClientDeploymentGenerator.java:91)
at org.jboss.arquillian.impl.ClientDeploymentGenerator.generate(ClientDeploymentGenerator.java:64)
at org.jboss.arquillian.impl.handler.ArchiveGenerator.callback(ArchiveGenerator.java:52)
at org.jboss.arquillian.impl.handler.ArchiveGenerator.callback(ArchiveGenerator.java:42)
at org.jboss.arquillian.impl.event.MapEventManager.fire(MapEventManager.java:63)
{code}
The tests are currently disabled and need to be fixed and enabled in some upcoming release.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 8 months