[jboss-as7-dev] Should I be able to ls a socket-binding in the admin shell?

Scott Stark sstark at redhat.com
Thu Apr 7 21:42:10 EDT 2011


When I go into the admin shell and navigate down to the socket-binding 
in the standard-sockets, tab completion shows the available bindings, 
but I am unable to ls any particular socket-binding. I would expect that 
when I ls socket-binding-group=standard-sockets/socket-binding=http I 
would see the attributes of the node. Is that correct? This is what I see:

[localhost:9999 /] ls socket-binding-group=standard-sockets/socket-binding=

socket-binding=http
socket-binding=https
socket-binding=jmx-connector-registry
socket-binding=jmx-connector-server
socket-binding=jndi
socket-binding=messaging
socket-binding=messaging-throughput
socket-binding=osgi-http
socket-binding=remoting
socket-binding=txn-recovery-environment
socket-binding=txn-socket-process-id
socket-binding=txn-status-manager
[localhost:9999 /] ls 
socket-binding-group=standard-sockets/socket-binding=jndi
[localhost:9999 /] ls 
socket-binding-group=standard-sockets/socket-binding=jndi
[localhost:9999 /] ls socket-binding-group=standard-sockets/socket-binding
jndi                       jmx-connector-registry     jmx-connector-server
http                       https                      osgi-http
remoting                   txn-recovery-environment   txn-status-manager
txn-socket-process-id      messaging                  messaging-throughput
[localhost:9999 /] ls 
socket-binding-group=standard-sockets/socket-binding=http
[localhost:9999 /] ls 
socket-binding-group=standard-sockets/socket-binding='http'
[localhost:9999 /]

The exceptions seen on the server console are of the form:

18:32:47,658 ERROR [org.jboss.as.controller] (pool-2-thread-4) operation 
("read-children-types") failed - address: ([
     ("socket-binding-group" => "standard-sockets"),
     ("socket-binding" => "'http'")
]): java.util.NoSuchElementException: No child ''http'' exists
     at org.jboss.dmr.ModelValue.requireChild(ModelValue.java:362)
     at 
org.jboss.dmr.ObjectModelValue.requireChild(ObjectModelValue.java:298)
     at org.jboss.dmr.ModelNode.require(ModelNode.java:703)
     at org.jboss.as.controller.PathAddress.navigate(PathAddress.java:233)
     at 
org.jboss.as.controller.BasicModelController.getOperationSubModel(BasicModelController.java:286)
     at 
org.jboss.as.controller.BasicModelController$2.getOperationContext(BasicModelController.java:94)
     at 
org.jboss.as.controller.BasicModelController.execute(BasicModelController.java:257)
     at 
org.jboss.as.controller.BasicModelController.execute(BasicModelController.java:216)
     at 
org.jboss.as.controller.BasicModelController.execute(BasicModelController.java:77)
     at 
org.jboss.as.controller.SynchronousOperationSupport.execute(SynchronousOperationSupport.java:88)
     at 
org.jboss.as.controller.AbstractModelController.execute(AbstractModelController.java:40)
     at 
org.jboss.as.controller.remote.ModelControllerOperationHandlerImpl$ExecuteSynchronousOperation.sendResponse(ModelControllerOperationHandlerImpl.java:187)
     at 
org.jboss.as.protocol.mgmt.ManagementResponse$2.handle(ManagementResponse.java:119)
     at 
org.jboss.as.protocol.mgmt.AbstractMessageHandler.handleMessage(AbstractMessageHandler.java:59)
     at 
org.jboss.as.protocol.ConnectionImpl.safeHandleMessage(ConnectionImpl.java:254)
     at 
org.jboss.as.protocol.ConnectionImpl$1$1.run(ConnectionImpl.java:213)
     at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) 
[:1.6.0_24]
     at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) 
[:1.6.0_24]
     at java.lang.Thread.run(Thread.java:680) [:1.6.0_24]





More information about the jboss-as7-dev mailing list