[JBoss JIRA] (AS7-4096) The "--command(s)" argument doesn't work
by Ron Šmeral (JIRA)
Ron Šmeral created AS7-4096:
-------------------------------
Summary: The "--command(s)" argument doesn't work
Key: AS7-4096
URL: https://issues.jboss.org/browse/AS7-4096
Project: Application Server 7
Issue Type: Bug
Components: CLI
Affects Versions: 7.1.0.Final
Environment: Fedora 16 64-bit, Oracle JDK 1.6.0_30
Reporter: Ron Šmeral
Assignee: Alexey Loubyansky
*Current behaviour*
{noformat}
$> jboss-cli.sh --commands "connect,version"
Duplicate argument '--command'/'--commands'.
{noformat}
*Expected behaviour*
{noformat}
$> jboss-cli.sh --commands "connect,version"
JBoss Admin Command-line Interface
...
{noformat}
It works, however, when the \-\-command/\-\-commands is omitted completely, as in:
{noformat}
$> jboss-cli.sh "connect,version"
{noformat}
Therefore, the command/commands arguments should probably be removed from help and usage, if this is the correct behaviour.
--
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, 1 month
[JBoss JIRA] Created: (JBAS-8843) size-rotating-file-handler not rotating
by Matthias Unverzagt (JIRA)
size-rotating-file-handler not rotating
---------------------------------------
Key: JBAS-8843
URL: https://issues.jboss.org/browse/JBAS-8843
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Logging
Affects Versions: 6.0.0.Final
Environment: Copied from boot.log:
############################
19:38:58,804 INFO [AbstractServer] Starting: JBossAS [6.0.1.SNAPSHOT "Neo"]
19:39:00,419 INFO [ServerInfo] Java version: 1.6.0_23,Sun Microsystems Inc.
19:39:00,419 INFO [ServerInfo] Java Runtime: Java(TM) SE Runtime Environment (build 1.6.0_23-b05)
19:39:00,419 INFO [ServerInfo] Java VM: Java HotSpot(TM) 64-Bit Server VM 19.0-b09,Sun Microsystems Inc.
19:39:00,420 INFO [ServerInfo] OS-System: Windows 7 6.1,amd64
19:39:00,420 INFO [ServerInfo] VM arguments: -Dprogram.name=run.bat -Xms1g -Xmx3g -XX:MaxPermSize=700M -Xdebug -Xrunjdwp:transport=dt_socket,address=9009,server=y,suspend=n -Djava.endorsed.dirs=E:\work\prgs\jboss-6.0.1-SNAPSHOT\lib\endorsed
19:39:00,420 DEBUG [ServerInfo] Full System Properties Dump
19:39:00,421 DEBUG [ServerInfo] awt.toolkit: sun.awt.windows.WToolkit
19:39:00,421 DEBUG [ServerInfo] bind.address: nb-matthias
19:39:00,421 DEBUG [ServerInfo] file.encoding: Cp1252
19:39:00,421 DEBUG [ServerInfo] file.encoding.pkg: sun.io
19:39:00,421 DEBUG [ServerInfo] file.separator: \
19:39:00,421 DEBUG [ServerInfo] java.awt.graphicsenv: sun.awt.Win32GraphicsEnvironment
19:39:00,422 DEBUG [ServerInfo] java.awt.printerjob: sun.awt.windows.WPrinterJob
19:39:00,422 DEBUG [ServerInfo] java.class.path: C:\Program Files\Java\jdk1.6.0_23\lib\tools.jar;E:\work\prgs\jboss-6.0.1-SNAPSHOT\bin\run.jar
19:39:00,422 DEBUG [ServerInfo] java.class.version: 50.0
19:39:00,422 DEBUG [ServerInfo] java.endorsed.dirs: E:\work\prgs\jboss-6.0.1-SNAPSHOT\lib\endorsed
19:39:00,422 DEBUG [ServerInfo] java.ext.dirs: C:\Program Files\Java\jdk1.6.0_23\jre\lib\ext;C:\Windows\Sun\Java\lib\ext
19:39:00,422 DEBUG [ServerInfo] java.home: C:\Program Files\Java\jdk1.6.0_23\jre
19:39:00,422 DEBUG [ServerInfo] java.io.tmpdir: C:\Users\matthias\AppData\Local\Temp\
19:39:00,423 DEBUG [ServerInfo] java.library.path: C:\Program Files\Java\jdk1.6.0_23\bin;.;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program Files\Java\jdk1.6.0_23\bin;C:\apps\apache-maven-3.0.2\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files\TortoiseGit\bin;C:\Program Files\TortoiseSVN\bin;C:\Program Files (x86)\NTRU Cryptosystems\NTRU TCG Software Stack\bin\;C:\Program Files\NTRU Cryptosystems\NTRU TCG Software Stack\bin\;C:\Program Files\Wave Systems Corp\Gemalto\Access Client\v5\;C:\Program Files\SlikSvn\bin\
19:39:00,423 DEBUG [ServerInfo] java.protocol.handler.pkgs: org.jboss.net.protocol|org.jboss.vfs.protocol
19:39:00,423 DEBUG [ServerInfo] java.rmi.server.RMIClassLoaderSpi: org.jboss.system.JBossRMIClassLoader
19:39:00,423 DEBUG [ServerInfo] java.rmi.server.hostname: nb-matthias
19:39:00,423 DEBUG [ServerInfo] java.runtime.name: Java(TM) SE Runtime Environment
19:39:00,423 DEBUG [ServerInfo] java.runtime.version: 1.6.0_23-b05
19:39:00,423 DEBUG [ServerInfo] java.specification.name: Java Platform API Specification
19:39:00,423 DEBUG [ServerInfo] java.specification.vendor: Sun Microsystems Inc.
19:39:00,424 DEBUG [ServerInfo] java.specification.version: 1.6
19:39:00,424 DEBUG [ServerInfo] java.util.logging.manager: org.jboss.logmanager.LogManager
19:39:00,424 DEBUG [ServerInfo] java.vendor: Sun Microsystems Inc.
19:39:00,424 DEBUG [ServerInfo] java.vendor.url: http://java.sun.com/
19:39:00,424 DEBUG [ServerInfo] java.vendor.url.bug: http://java.sun.com/cgi-bin/bugreport.cgi
19:39:00,424 DEBUG [ServerInfo] java.version: 1.6.0_23
19:39:00,424 DEBUG [ServerInfo] java.vm.info: mixed mode
19:39:00,425 DEBUG [ServerInfo] java.vm.name: Java HotSpot(TM) 64-Bit Server VM
19:39:00,425 DEBUG [ServerInfo] java.vm.specification.name: Java Virtual Machine Specification
19:39:00,425 DEBUG [ServerInfo] java.vm.specification.vendor: Sun Microsystems Inc.
19:39:00,425 DEBUG [ServerInfo] java.vm.specification.version: 1.0
19:39:00,425 DEBUG [ServerInfo] java.vm.vendor: Sun Microsystems Inc.
19:39:00,425 DEBUG [ServerInfo] java.vm.version: 19.0-b09
19:39:00,425 DEBUG [ServerInfo] javax.management.builder.initial: org.jboss.mx.server.MBeanServerBuilderImpl
19:39:00,425 DEBUG [ServerInfo] jboss.bind.address: 0.0.0.0
19:39:00,426 DEBUG [ServerInfo] jboss.boot.server.log.dir: E:\work\prgs\jboss-6.0.1-SNAPSHOT\server\default\log
19:39:00,426 DEBUG [ServerInfo] jboss.bootstrap.home.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/server/default/conf/
19:39:00,426 DEBUG [ServerInfo] jboss.bootstrap.name: bootstrap.xml
19:39:00,426 DEBUG [ServerInfo] jboss.bootstrap.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/server/default/conf/bootstrap.xml
19:39:00,426 DEBUG [ServerInfo] jboss.common.base.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/common/
19:39:00,426 DEBUG [ServerInfo] jboss.common.lib.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/common/lib/
19:39:00,426 DEBUG [ServerInfo] jboss.home: E:\work\prgs\jboss-6.0.1-SNAPSHOT
19:39:00,426 DEBUG [ServerInfo] jboss.home.dir: E:\work\prgs\jboss-6.0.1-SNAPSHOT
19:39:00,427 DEBUG [ServerInfo] jboss.home.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/
19:39:00,427 DEBUG [ServerInfo] jboss.host.name: nb-matthias
19:39:00,427 DEBUG [ServerInfo] jboss.lib.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/lib/
19:39:00,427 DEBUG [ServerInfo] jboss.native.dir: E:\work\prgs\jboss-6.0.1-SNAPSHOT\server\default\tmp\native
19:39:00,427 DEBUG [ServerInfo] jboss.native.load: false
19:39:00,427 DEBUG [ServerInfo] jboss.node.name: nb-matthias
19:39:00,427 DEBUG [ServerInfo] jboss.partition.name: DefaultPartition
19:39:00,427 DEBUG [ServerInfo] jboss.platform.mbeanserver: true
19:39:00,428 DEBUG [ServerInfo] jboss.qualified.host.name: nb-matthias
19:39:00,428 DEBUG [ServerInfo] jboss.server.base.dir: E:\work\prgs\jboss-6.0.1-SNAPSHOT\server
19:39:00,428 DEBUG [ServerInfo] jboss.server.base.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/server/
19:39:00,428 DEBUG [ServerInfo] jboss.server.config.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/server/default/conf/
19:39:00,428 DEBUG [ServerInfo] jboss.server.data.dir: E:\work\prgs\jboss-6.0.1-SNAPSHOT\server\default\data
19:39:00,428 DEBUG [ServerInfo] jboss.server.home.dir: E:\work\prgs\jboss-6.0.1-SNAPSHOT\server\default
19:39:00,428 DEBUG [ServerInfo] jboss.server.home.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/server/default/
19:39:00,428 DEBUG [ServerInfo] jboss.server.lib.url: file:/E:/work/prgs/jboss-6.0.1-SNAPSHOT/server/default/lib/
19:39:00,429 DEBUG [ServerInfo] jboss.server.log.dir: E:\work\prgs\jboss-6.0.1-SNAPSHOT\server\default\log
19:39:00,429 DEBUG [ServerInfo] jboss.server.name: default
19:39:00,429 DEBUG [ServerInfo] jboss.server.temp.dir: E:\work\prgs\jboss-6.0.1-SNAPSHOT\server\default\tmp
19:39:00,429 DEBUG [ServerInfo] jboss.vfs.forceCopy: true
19:39:00,429 DEBUG [ServerInfo] jbossmx.loader.repository.class: org.jboss.mx.loading.UnifiedLoaderRepository3
19:39:00,429 DEBUG [ServerInfo] jgroups.bind_addr: nb-matthias
19:39:00,429 DEBUG [ServerInfo] line.separator:
19:39:00,429 DEBUG [ServerInfo] log4j.defaultInitOverride: true
19:39:00,430 DEBUG [ServerInfo] org.jboss.deployers.spi.deployer.matchers.NameIgnoreMechanism: org.jboss.deployers.spi.deployer.helpers.DummyNameIgnoreMechanism
19:39:00,430 DEBUG [ServerInfo] org.jboss.logging.Logger.pluginClass: org.jboss.logging.logmanager.LoggerPluginImpl
19:39:00,444 DEBUG [ServerInfo] org.jboss.reflect.spi.TypeInfoFactory: org.jboss.reflect.plugins.introspection.IntrospectionTypeInfoFactory
19:39:00,444 DEBUG [ServerInfo] os.arch: amd64
19:39:00,444 DEBUG [ServerInfo] os.name: Windows 7
19:39:00,444 DEBUG [ServerInfo] os.version: 6.1
19:39:00,444 DEBUG [ServerInfo] path.separator: ;
19:39:00,444 DEBUG [ServerInfo] program.name: run.bat
19:39:00,445 DEBUG [ServerInfo] sun.arch.data.model: 64
19:39:00,445 DEBUG [ServerInfo] sun.boot.class.path: E:\work\prgs\jboss-6.0.1-SNAPSHOT\lib\endorsed\activation.jar;E:\work\prgs\jboss-6.0.1-SNAPSHOT\lib\endorsed\jboss-annotations-api_1.1_spec.jar;E:\work\prgs\jboss-6.0.1-SNAPSHOT\lib\endorsed\jboss-jaxb-api_2.2_spec.jar;E:\work\prgs\jboss-6.0.1-SNAPSHOT\lib\endorsed\jboss-jaxws-api_2.2_spec.jar;E:\work\prgs\jboss-6.0.1-SNAPSHOT\lib\endorsed\jbossws-cxf-factories.jar;E:\work\prgs\jboss-6.0.1-SNAPSHOT\lib\endorsed\stax-api.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\resources.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\rt.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\sunrsasign.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\jsse.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\jce.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\charsets.jar;C:\Program Files\Java\jdk1.6.0_23\jre\lib\modules\jdk.boot.jar;C:\Program Files\Java\jdk1.6.0_23\jre\classes
19:39:00,445 DEBUG [ServerInfo] sun.boot.library.path: C:\Program Files\Java\jdk1.6.0_23\jre\bin
19:39:00,445 DEBUG [ServerInfo] sun.cpu.endian: little
19:39:00,445 DEBUG [ServerInfo] sun.cpu.isalist: amd64
19:39:00,445 DEBUG [ServerInfo] sun.desktop: windows
19:39:00,445 DEBUG [ServerInfo] sun.io.unicode.encoding: UnicodeLittle
19:39:00,446 DEBUG [ServerInfo] sun.java.launcher: SUN_STANDARD
19:39:00,446 DEBUG [ServerInfo] sun.jnu.encoding: Cp1252
19:39:00,446 DEBUG [ServerInfo] sun.management.compiler: HotSpot 64-Bit Server Compiler
19:39:00,446 DEBUG [ServerInfo] sun.os.patch.level:
19:39:00,446 DEBUG [ServerInfo] user.country: DE
19:39:00,446 DEBUG [ServerInfo] user.dir: C:\Windows\System32
19:39:00,446 DEBUG [ServerInfo] user.home: C:\Users\matthias
19:39:00,446 DEBUG [ServerInfo] user.language: de
19:39:00,447 DEBUG [ServerInfo] user.name: matthias
19:39:00,447 DEBUG [ServerInfo] user.timezone: Europe/Berlin
19:39:00,447 DEBUG [ServerInfo] user.variant:
19:39:00,447 DEBUG [ServerInfo] xb.builder.repeatableParticleHandlers: false
19:39:00,447 DEBUG [ServerInfo] xb.builder.useUnorderedSequence: true
Reporter: Matthias Unverzagt
Assignee: David Lloyd
size-rotating-file-handler only rotates once and then the logfile grows.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (AS7-4072) Method asList called on an empty ModelNode should return an empty list
by Jan Martiska (JIRA)
Jan Martiska created AS7-4072:
---------------------------------
Summary: Method asList called on an empty ModelNode should return an empty list
Key: AS7-4072
URL: https://issues.jboss.org/browse/AS7-4072
Project: Application Server 7
Issue Type: Bug
Components: Remoting
Reporter: Jan Martiska
Assignee: Emanuel Muckenhuber
Priority: Minor
{noformat}
ModelNode op = new ModelNode();
op.get("foo").add("bar");
for(ModelNode child : op.asList()) {
System.out.println(child.toString());
}
{noformat}
.. if you omit the second line of this snippet, that means call asList on an empty node (empty, not null of course), an IllegalArgumentException will be thrown. I think this behavior is not appropriate. It should rather return an empty list.
If I picked the wrong component or assignee, fell free to change it :)
--
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, 1 month
[JBoss JIRA] (AS7-4061) CLONE - String configuration parameters for HornetQ address cannot be set via CLI
by Emanuel Muckenhuber (JIRA)
[ https://issues.jboss.org/browse/AS7-4061?page=com.atlassian.jira.plugin.s... ]
Emanuel Muckenhuber resolved AS7-4061.
--------------------------------------
Fix Version/s: 7.1.1.Final
(was: 7.1.2.Final)
Resolution: Done
Yes, this is fixed upstream.
> CLONE - String configuration parameters for HornetQ address cannot be set via CLI
> ---------------------------------------------------------------------------------
>
> Key: AS7-4061
> URL: https://issues.jboss.org/browse/AS7-4061
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management, JMS
> Affects Versions: 7.1.0.Final
> Reporter: Pavel Slavicek
> Assignee: Emanuel Muckenhuber
> Labels: eap6_need_triage
> Fix For: 7.1.1.Final
>
>
> String configuration parameters for HornetQ address cannot be set via CLI because of the following issue "JBAS014688: Wrong type for value. Expected [STRING] but was OBJECT".
> pwd:
> /subsystem=messaging/hornetq-server=default/address-setting=#
> [standalone@localhost:9999 address-setting=#:read-attribute(name=redistribution-delay)
> {
> "outcome" => "success",
> "result" => -1L
> }
> [standalone@localhost:9999 address-setting=#] :write-attribute(name=redistribution-delay, value=1000L)
> {"outcome" => "success"}
> [standalone@localhost:9999 address-setting=#:read-attribute(name=redistribution-delay)
> {
> "outcome" => "success",
> "result" => 1000L
> }
> [standalone@localhost:9999 address-setting=#] :write-attribute(name=address-full-policy, value=PAGE)
> {
> "outcome" => "failed",
> "failure-description" => "JBAS014688: Wrong type for value. Expected [STRING] but was OBJECT",
> "rolled-back" => true
> }
> [standalone@localhost:9999 address-setting=#] :write-attribute(name=address-full-policy, value="PAGE")
> {
> "outcome" => "failed",
> "failure-description" => "JBAS014688: Wrong type for value. Expected [STRING] but was OBJECT",
> "rolled-back" => true
> }
> [standalone@localhost:9999 address-setting=#] :write-attribute(name=expiry-address, value="jms.queue.DLQ")
> {
> "outcome" => "failed",
> "failure-description" => "JBAS014688: Wrong type for value. Expected [STRING] but was OBJECT",
> "rolled-back" => true
> }
> [standalone@localhost:9999 address-setting=#] ls -l
> ATTRIBUTE VALUE TYPE
> address-full-policy BLOCK STRING
> dead-letter-address jms.queue.DLQ STRING
> expiry-address jms.queue.ExpiryQueue STRING
> last-value-queue false BOOLEAN
> max-delivery-attempts 10 INT
> max-size-bytes 10485760 INT
> message-counter-history-day-limit 10 INT
> page-max-cache-size 5 INT
> page-size-bytes 10485760 LONG
> redelivery-delay 0 INT
> redistribution-delay -1 LONG
> send-to-dla-on-no-route false BOOLEAN
--
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, 1 month
[JBoss JIRA] (AS7-4061) CLONE - String configuration parameters for HornetQ address cannot be set via CLI
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-4061?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry commented on AS7-4061:
---------------------------------------
Emanuel, can this be resolved for 7.1.1?
> CLONE - String configuration parameters for HornetQ address cannot be set via CLI
> ---------------------------------------------------------------------------------
>
> Key: AS7-4061
> URL: https://issues.jboss.org/browse/AS7-4061
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management, JMS
> Affects Versions: 7.1.0.Final
> Reporter: Pavel Slavicek
> Assignee: Emanuel Muckenhuber
> Labels: eap6_need_triage
> Fix For: 7.1.2.Final
>
>
> String configuration parameters for HornetQ address cannot be set via CLI because of the following issue "JBAS014688: Wrong type for value. Expected [STRING] but was OBJECT".
> pwd:
> /subsystem=messaging/hornetq-server=default/address-setting=#
> [standalone@localhost:9999 address-setting=#:read-attribute(name=redistribution-delay)
> {
> "outcome" => "success",
> "result" => -1L
> }
> [standalone@localhost:9999 address-setting=#] :write-attribute(name=redistribution-delay, value=1000L)
> {"outcome" => "success"}
> [standalone@localhost:9999 address-setting=#:read-attribute(name=redistribution-delay)
> {
> "outcome" => "success",
> "result" => 1000L
> }
> [standalone@localhost:9999 address-setting=#] :write-attribute(name=address-full-policy, value=PAGE)
> {
> "outcome" => "failed",
> "failure-description" => "JBAS014688: Wrong type for value. Expected [STRING] but was OBJECT",
> "rolled-back" => true
> }
> [standalone@localhost:9999 address-setting=#] :write-attribute(name=address-full-policy, value="PAGE")
> {
> "outcome" => "failed",
> "failure-description" => "JBAS014688: Wrong type for value. Expected [STRING] but was OBJECT",
> "rolled-back" => true
> }
> [standalone@localhost:9999 address-setting=#] :write-attribute(name=expiry-address, value="jms.queue.DLQ")
> {
> "outcome" => "failed",
> "failure-description" => "JBAS014688: Wrong type for value. Expected [STRING] but was OBJECT",
> "rolled-back" => true
> }
> [standalone@localhost:9999 address-setting=#] ls -l
> ATTRIBUTE VALUE TYPE
> address-full-policy BLOCK STRING
> dead-letter-address jms.queue.DLQ STRING
> expiry-address jms.queue.ExpiryQueue STRING
> last-value-queue false BOOLEAN
> max-delivery-attempts 10 INT
> max-size-bytes 10485760 INT
> message-counter-history-day-limit 10 INT
> page-max-cache-size 5 INT
> page-size-bytes 10485760 LONG
> redelivery-delay 0 INT
> redistribution-delay -1 LONG
> send-to-dla-on-no-route false BOOLEAN
--
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, 1 month
[JBoss JIRA] (AS7-4073) can not :write-attribute expression values
by Heiko Rupp (JIRA)
Heiko Rupp created AS7-4073:
-------------------------------
Summary: can not :write-attribute expression values
Key: AS7-4073
URL: https://issues.jboss.org/browse/AS7-4073
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.0.Final
Reporter: Heiko Rupp
Assignee: Brian Stansberry
socket bindings return on read expression in the form {"EXPRESSION_VALUE":"${foo:123}"}
[standalone@localhost:9999 socket-binding=management-http] :read-attribute(name=port)
{
"outcome" => "success",
"result" => expression "${jboss.management.http.port:9990}"
}
First this is confusing, as the description describes the port as int:
[standalone@localhost:9999 socket-binding=http] :read-resource-description
{
"outcome" => "success",
"result" => {
"description" => "Configuration information for a socket.",
"attributes" => {
"port" => {
"type" => INT,
"description" => "Number of the port to which the socket should be bound.",
"expressions-allowed" => true,
"nillable" => false,
"min" => 0L,
"max" => 65535L,
"access-type" => "read-write",
"storage" => "configuration",
"restart-required" => "all-services"
},
I can still work around this in json-land by having the expression toString()'d and then remove the {EXPRESSION_VALUE=..} part around it.
Now writing back an expression does not work:
[standalone@localhost:9999 socket-binding=management-http] :write-attribute(name=port,value=${jboss.management.http.port:19990})
{
"outcome" => "failed",
"failure-description" => "JBAS014688: Wrong type for port. Expected [EXPRESSION, INT] but was STRING",
"rolled-back" => true
}
Same applies to json-interface when I do a write-attribute call with {name="port",value="${...}"} as payload
Operation <CompositeOperation{steps=23}> returned <"JBAS014688: Wrong type for port. Expected [EXPRESSION, INT] but was STRING","rolled-back":true},
--
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, 1 month
[JBoss JIRA] (AS7-3792) Remote EJB client still throws exception rather than blocking
by Radoslav Husar (JIRA)
Radoslav Husar created AS7-3792:
-----------------------------------
Summary: Remote EJB client still throws exception rather than blocking
Key: AS7-3792
URL: https://issues.jboss.org/browse/AS7-3792
Project: Application Server 7
Issue Type: Bug
Components: Clustering, EJB
Affects Versions: 7.1.0.Final
Reporter: Radoslav Husar
Assignee: jaikiran pai
Priority: Critical
Fix For: 7.1.1.Final
Lets reopen this topic, there seems to be flaw in implementation of EJBCLIENT-23, I am really seeing this exception with 1.0.2.Final client and AS 7.1.0.Final.
The exception is thrown on invoking method on the remote SFSB.
{noformat}
2012/02/16 08:34:58:715 EST [ERROR][Runner - 36] HOST perf17.mw.lab.eng.bos.redhat.com:rootProcess:c - Error getting response. <java.lang.reflect.UndeclaredThrowableException>
java.lang.reflect.UndeclaredThrowableException
at $Proxy0.getSerialAndIncrement(Unknown Source)
at org.jboss.smartfrog.clustering.ejb3.StatefulSBProcessorFactoryImpl$EJB3RequestProcessor.processRequest(StatefulSBProcessorFactoryImpl.java:68)
at org.jboss.smartfrog.loaddriver.CompoundRequestProcessorFactoryImpl$CompoundRequestProcessor.processRequest(CompoundRequestProcessorFactoryImpl.java:51)
at org.jboss.smartfrog.loaddriver.Runner.run(Runner.java:87)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.jboss.remoting3.ChannelBusyException: Too many open outbound writes
at org.jboss.remoting3.remote.RemoteConnectionChannel.openOutboundMessage(RemoteConnectionChannel.java:111)
at org.jboss.remoting3.remote.RemoteConnectionChannel.writeMessage(RemoteConnectionChannel.java:296)
at org.jboss.ejb.client.remoting.ChannelAssociation.acquireChannelMessageOutputStream(ChannelAssociation.java:235)
at org.jboss.ejb.client.remoting.RemotingConnectionEJBReceiver.processInvocation(RemotingConnectionEJBReceiver.java:193)
at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:173)
at org.jboss.ejb.client.TransactionInterceptor.handleInvocation(TransactionInterceptor.java:43)
at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:175)
at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:92)
at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:175)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:136)
at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:121)
at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:104)
... 5 more
{noformat}
--
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, 1 month