[JBoss JIRA] (AS7-4472) CLONE - JacORB throws BindException: Address in use in a clustered environment with IPv6 addresses
by Richard Achmatowicz (JIRA)
[ https://issues.jboss.org/browse/AS7-4472?page=com.atlassian.jira.plugin.s... ]
Richard Achmatowicz deleted AS7-4472:
-------------------------------------
> CLONE - JacORB throws BindException: Address in use in a clustered environment with IPv6 addresses
> --------------------------------------------------------------------------------------------------
>
> Key: AS7-4472
> URL: https://issues.jboss.org/browse/AS7-4472
> Project: Application Server 7
> Issue Type: Bug
> Reporter: Richard Achmatowicz
> Assignee: Stefan Guilhen
>
> JacORB throws an BindException (address in use) when starting in a clustered environment with IPv6 global addresses:
> {noformat}
> 13:15:43,833 INFO [org.jboss.as.jacorb] (MSC service thread 1-8) JBAS016330: CORBA ORB Service started
> 13:15:43,969 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /tmp/as71/standalone/deployments
> 13:15:43,972 WARN [jacorb.iiop.address] (MSC service thread 1-8) init_host, 3ffe:ffff:100:f101:0:0:0:1%2 is local-link address
> 13:15:43,960 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-6) live server is starting with configuration HornetQ Configuration (clustered=true,backup=false,sharedStore=true,journalDirectory=/tmp/as71/standalone/data/messagingjournal,bindingsDirectory=/tmp/as71/standalone/data/messagingbindings,largeMessagesDirectory=/tmp/as71/standalone/data/messaginglargemessages,pagingDirectory=/tmp/as71/standalone/data/messagingpaging)
> 13:15:43,971 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on /3ffe:ffff:100:f101:0:0:0:1%2:9999
> 13:15:43,971 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 3ffe:ffff:100:f101:0:0:0:1%2/3ffe:ffff:100:f101:0:0:0:1%2:4447
> 13:15:43,975 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-6) Waiting to obtain live lock
> 13:15:43,978 WARN [jacorb.iiop.address] (MSC service thread 1-8) init_host, 3ffe:ffff:100:f101:0:0:0:1%2 is local-link address
> 13:15:43,979 WARN [jacorb.orb.iiop] (MSC service thread 1-8) could not create server socket port: 3528 host: null: java.net.BindException: Address already in use
> at java.net.PlainSocketImpl.socketBind(Native Method) [rt.jar:1.6.0_26]
> at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:383) [rt.jar:1.6.0_26]
> at java.net.ServerSocket.bind(ServerSocket.java:328) [rt.jar:1.6.0_26]
> at java.net.ServerSocket.<init>(ServerSocket.java:194) [rt.jar:1.6.0_26]
> at org.jacorb.orb.factory.DefaultServerSocketFactory.createServerSocket(DefaultServerSocketFactory.java:49) [jacorb-2.3.1.jbossorg-1.jar:]
> at org.jacorb.orb.iiop.IIOPListener$Acceptor.createServerSocket(IIOPListener.java:572) [jacorb-2.3.1.jbossorg-1.jar:]
> at org.jacorb.orb.iiop.IIOPListener$Acceptor.init(IIOPListener.java:417) [jacorb-2.3.1.jbossorg-1.jar:]
> at org.jacorb.orb.iiop.IIOPListener.configure(IIOPListener.java:163) [jacorb-2.3.1.jbossorg-1.jar:]
> at org.jacorb.orb.etf.FactoriesBase.newInstance(FactoriesBase.java:125) [jacorb-2.3.1.jbossorg-1.jar:]
> at org.jacorb.orb.etf.FactoriesBase.create_listener(FactoriesBase.java:74) [jacorb-2.3.1.jbossorg-1.jar:]
> at org.jacorb.orb.BasicAdapter.configure(BasicAdapter.java:102) [jacorb-2.3.1.jbossorg-1.jar:]
> at org.jacorb.orb.ORB.getRootPOA(ORB.java:1036) [jacorb-2.3.1.jbossorg-1.jar:]
> at org.jacorb.orb.ORB.resolve_initial_references(ORB.java:1307) [jacorb-2.3.1.jbossorg-1.jar:]
> at org.jboss.as.jacorb.service.CorbaPOAService.start(CorbaPOAService.java:153) [jboss-as-jacorb-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]
> 13:15:43,998 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC00001: Failed to start service jboss.jacorb.poa-service.rootpoa: org.jboss.msc.service.StartException in service jboss.jacorb.poa-service.rootpoa: org.omg.CORBA.INITIALIZE: Could not create server socket (3528): java.net.BindException: Address already in use
> at org.jboss.as.jacorb.service.CorbaPOAService.start(CorbaPOAService.java:155)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26]
> at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]
> Caused by: org.omg.CORBA.INITIALIZE: Could not create server socket (3528): java.net.BindException: Address already in use
> at org.jacorb.orb.iiop.IIOPListener$Acceptor.createServerSocket(IIOPListener.java:580)
> at org.jacorb.orb.iiop.IIOPListener$Acceptor.init(IIOPListener.java:417)
> at org.jacorb.orb.iiop.IIOPListener.configure(IIOPListener.java:163)
> at org.jacorb.orb.etf.FactoriesBase.newInstance(FactoriesBase.java:125)
> at org.jacorb.orb.etf.FactoriesBase.create_listener(FactoriesBase.java:74)
> at org.jacorb.orb.BasicAdapter.configure(BasicAdapter.java:102)
> at org.jacorb.orb.ORB.getRootPOA(ORB.java:1036)
> at org.jacorb.orb.ORB.resolve_initial_references(ORB.java:1307)
> at org.jboss.as.jacorb.service.CorbaPOAService.start(CorbaPOAService.java:153)
> ... 5 more
> 13:15:44,055 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
> {noformat}
> This should not happen. I suspect that the IPv6 addresses are being mishandled somewhere.
--
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, 2 months
[JBoss JIRA] (AS7-4472) CLONE - JacORB throws BindException: Address in use in a clustered environment with IPv6 addresses
by Richard Achmatowicz (JIRA)
Richard Achmatowicz created AS7-4472:
----------------------------------------
Summary: CLONE - JacORB throws BindException: Address in use in a clustered environment with IPv6 addresses
Key: AS7-4472
URL: https://issues.jboss.org/browse/AS7-4472
Project: Application Server 7
Issue Type: Bug
Components: IIOP
Affects Versions: 7.1.1.Final
Reporter: Richard Achmatowicz
Assignee: Stefan Guilhen
Fix For: 7.1.2.Final-redhat1
JacORB throws an BindException (address in use) when starting in a clustered environment with IPv6 global addresses:
{noformat}
13:15:43,833 INFO [org.jboss.as.jacorb] (MSC service thread 1-8) JBAS016330: CORBA ORB Service started
13:15:43,969 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /tmp/as71/standalone/deployments
13:15:43,972 WARN [jacorb.iiop.address] (MSC service thread 1-8) init_host, 3ffe:ffff:100:f101:0:0:0:1%2 is local-link address
13:15:43,960 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-6) live server is starting with configuration HornetQ Configuration (clustered=true,backup=false,sharedStore=true,journalDirectory=/tmp/as71/standalone/data/messagingjournal,bindingsDirectory=/tmp/as71/standalone/data/messagingbindings,largeMessagesDirectory=/tmp/as71/standalone/data/messaginglargemessages,pagingDirectory=/tmp/as71/standalone/data/messagingpaging)
13:15:43,971 INFO [org.jboss.as.remoting] (MSC service thread 1-2) JBAS017100: Listening on /3ffe:ffff:100:f101:0:0:0:1%2:9999
13:15:43,971 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 3ffe:ffff:100:f101:0:0:0:1%2/3ffe:ffff:100:f101:0:0:0:1%2:4447
13:15:43,975 INFO [org.hornetq.core.server.impl.HornetQServerImpl] (MSC service thread 1-6) Waiting to obtain live lock
13:15:43,978 WARN [jacorb.iiop.address] (MSC service thread 1-8) init_host, 3ffe:ffff:100:f101:0:0:0:1%2 is local-link address
13:15:43,979 WARN [jacorb.orb.iiop] (MSC service thread 1-8) could not create server socket port: 3528 host: null: java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method) [rt.jar:1.6.0_26]
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:383) [rt.jar:1.6.0_26]
at java.net.ServerSocket.bind(ServerSocket.java:328) [rt.jar:1.6.0_26]
at java.net.ServerSocket.<init>(ServerSocket.java:194) [rt.jar:1.6.0_26]
at org.jacorb.orb.factory.DefaultServerSocketFactory.createServerSocket(DefaultServerSocketFactory.java:49) [jacorb-2.3.1.jbossorg-1.jar:]
at org.jacorb.orb.iiop.IIOPListener$Acceptor.createServerSocket(IIOPListener.java:572) [jacorb-2.3.1.jbossorg-1.jar:]
at org.jacorb.orb.iiop.IIOPListener$Acceptor.init(IIOPListener.java:417) [jacorb-2.3.1.jbossorg-1.jar:]
at org.jacorb.orb.iiop.IIOPListener.configure(IIOPListener.java:163) [jacorb-2.3.1.jbossorg-1.jar:]
at org.jacorb.orb.etf.FactoriesBase.newInstance(FactoriesBase.java:125) [jacorb-2.3.1.jbossorg-1.jar:]
at org.jacorb.orb.etf.FactoriesBase.create_listener(FactoriesBase.java:74) [jacorb-2.3.1.jbossorg-1.jar:]
at org.jacorb.orb.BasicAdapter.configure(BasicAdapter.java:102) [jacorb-2.3.1.jbossorg-1.jar:]
at org.jacorb.orb.ORB.getRootPOA(ORB.java:1036) [jacorb-2.3.1.jbossorg-1.jar:]
at org.jacorb.orb.ORB.resolve_initial_references(ORB.java:1307) [jacorb-2.3.1.jbossorg-1.jar:]
at org.jboss.as.jacorb.service.CorbaPOAService.start(CorbaPOAService.java:153) [jboss-as-jacorb-7.1.1.Final-SNAPSHOT.jar:7.1.1.Final-SNAPSHOT]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]
13:15:43,998 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC00001: Failed to start service jboss.jacorb.poa-service.rootpoa: org.jboss.msc.service.StartException in service jboss.jacorb.poa-service.rootpoa: org.omg.CORBA.INITIALIZE: Could not create server socket (3528): java.net.BindException: Address already in use
at org.jboss.as.jacorb.service.CorbaPOAService.start(CorbaPOAService.java:155)
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_26]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_26]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_26]
Caused by: org.omg.CORBA.INITIALIZE: Could not create server socket (3528): java.net.BindException: Address already in use
at org.jacorb.orb.iiop.IIOPListener$Acceptor.createServerSocket(IIOPListener.java:580)
at org.jacorb.orb.iiop.IIOPListener$Acceptor.init(IIOPListener.java:417)
at org.jacorb.orb.iiop.IIOPListener.configure(IIOPListener.java:163)
at org.jacorb.orb.etf.FactoriesBase.newInstance(FactoriesBase.java:125)
at org.jacorb.orb.etf.FactoriesBase.create_listener(FactoriesBase.java:74)
at org.jacorb.orb.BasicAdapter.configure(BasicAdapter.java:102)
at org.jacorb.orb.ORB.getRootPOA(ORB.java:1036)
at org.jacorb.orb.ORB.resolve_initial_references(ORB.java:1307)
at org.jboss.as.jacorb.service.CorbaPOAService.start(CorbaPOAService.java:153)
... 5 more
13:15:44,055 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
{noformat}
This should not happen. I suspect that the IPv6 addresses are being mishandled somewhere.
--
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, 2 months
[JBoss JIRA] (AS7-4418) Atrribute <factory-type> is not parsed correctly in configuration of connection-factory
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/AS7-4418?page=com.atlassian.jira.plugin.s... ]
Jeff Mesnil resolved AS7-4418.
------------------------------
Resolution: Duplicate Issue
> Atrribute <factory-type> is not parsed correctly in configuration of connection-factory
> ---------------------------------------------------------------------------------------
>
> Key: AS7-4418
> URL: https://issues.jboss.org/browse/AS7-4418
> Project: Application Server 7
> Issue Type: Bug
> Components: JMS
> Reporter: Miroslav Novak
> Assignee: Jeff Mesnil
> Fix For: 7.1.2.Final-redhat1
>
>
> Attribute factory-type in configuration connection factory is not parsed correctly and default "CF" type is always used.
> Following configuration should register XAConnectionFactory but attribute factory-type is ignored:
> {code}
> <connection-factory name="RemoteConnectionFactory">
>
> <jms-connection-factories>
> ...
> <connection-factory name="RemoteConnectionFactory">
> <factory-type>XA_GENERIC</factory-type>
> <connectors>
> <connector-ref connector-name="netty"/>
> </connectors>
> <entries>
> <entry name="RemoteConnectionFactory"/>
> <entry name="java:jboss/exported/jms/RemoteConnectionFactory"/>
> </entries>
> <ha>true</ha>
> </connection-factory>
> ...
> </jms-connection-factories>
> {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
14 years, 2 months
[JBoss JIRA] (AS7-4436) setting debug-enabled and debug-options via dmr does not work
by Michael Voegele (JIRA)
Michael Voegele created AS7-4436:
------------------------------------
Summary: setting debug-enabled and debug-options via dmr does not work
Key: AS7-4436
URL: https://issues.jboss.org/browse/AS7-4436
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.1.Final
Reporter: Michael Voegele
Assignee: Brian Stansberry
Setting the following jvm configuration works, including *debug-enabled* and *debug-options*:
(see also https://issues.jboss.org/browse/AS7-1606)
{code:xml}
<servers>
<server name="server-1" group="server-group-1" auto-start="true">
<jvm name="default" java-home="C:/eplatform/java/jdk1.7.0" debug-enabled="true"
debug-options="runjdwp:transport=dt_socket,address=13013,server=y,suspend=n">
<heap size="128m" max-size="256m" />
<permgen size="64m" max-size="128m" />
<stack size="512k" />
</jvm>
<socket-bindings port-offset="100" />
</server>
</servers>
{code}
however, *setting these two attributes via dmr does not work*. The following operation:
{code:xml}
{
"operation" => "add",
"address" => [
("host" => "master"),
("server-config" => "server-1"),
("jvm" => "default")
],
"java-home" => "C:/eplatform/java/jdk1.7.0",
"debug-enabled" => "true",
"debug-options" => "runjdwp:transport=dt_socket,address=13013,server=y,suspend=n",
"heap-size" => "128m",
"max-heap-size" => "256m",
"permgen-size" => "64m",
"max-permgen-size" => "128m",
"stack-size" => "512k"
}
{code}
results in:
{code:xml}
<servers>
<server name="server-1" group="server-group-1" auto-start="true">
<jvm name="default" java-home="C:/eplatform/java/jdk1.7.0">
<heap size="128m" max-size="256m"/>
<permgen size="64m" max-size="128m"/>
<stack size="512k"/>
</jvm>
<socket-bindings port-offset="100"/>
</server>
</servers>
{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
14 years, 2 months
[JBoss JIRA] (AS7-4261) Keystore element of ssl server-identities, cannot specify 'alias' of key to use for identity
by Stian Lund (JIRA)
Stian Lund created AS7-4261:
-------------------------------
Summary: Keystore element of ssl server-identities, cannot specify 'alias' of key to use for identity
Key: AS7-4261
URL: https://issues.jboss.org/browse/AS7-4261
Project: Application Server 7
Issue Type: Bug
Components: Security, Server
Affects Versions: 7.1.0.Final
Reporter: Stian Lund
Assignee: Anil Saldhana
When securing the management interface, you need to specify a server identity and a SSL keystore to use, example:
<server-identities>
<ssl>
<keystore path="keystore.jks" relative-to="jboss.home.dir" password="xxx">
</ssl>
</server-identities>
*However* this does not support (in the XSD) using an alias to specify the private key to use for the identity. It seems to just use the first private key pair it finds in the keystore. This is quite a big problem if your keystore contains several key pairs (as for instance JKS supports)
--
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, 2 months
[JBoss JIRA] (AS7-4115) Jboss Web Connector resources max-threads data not available in ui or cli/json data
by Jean-Frederic Clere (JIRA)
[ https://issues.jboss.org/browse/AS7-4115?page=com.atlassian.jira.plugin.s... ]
Jean-Frederic Clere updated AS7-4115:
-------------------------------------
Complexity: High
> Jboss Web Connector resources max-threads data not available in ui or cli/json data
> ------------------------------------------------------------------------------------
>
> Key: AS7-4115
> URL: https://issues.jboss.org/browse/AS7-4115
> Project: Application Server 7
> Issue Type: Bug
> Environment: Using JBEAP-6.0.0.ER1.
> Reporter: Simeon Pinder
> Assignee: Jean-Frederic Clere
> Priority: Critical
> Labels: rhq
>
> Looks like max-threads is not currently exposed for JBoss Web Connectors.
> "connector" => {"http" => {
> "bytesReceived" => "0",
> "bytesSent" => "0",
> "enable-lookups" => false,
> "enabled" => true,
> "errorCount" => "0",
> "max-post-size" => 2097152,
> "max-save-post-size" => 4096,
> "maxTime" => "0",
> "processingTime" => "0",
> "protocol" => "HTTP/1.1",
> "redirect-port" => 8443,
> "requestCount" => "0",
> "scheme" => "http",
> "secure" => false,
> "socket-binding" => "http",
> "ssl" => undefined,
> "virtual-server" => undefined
> }}
--
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, 2 months
[JBoss JIRA] (AS7-4447) Operations add-jvm-option and remove-jvm-option don't work in a reasonable way
by Michael Voegele (JIRA)
Michael Voegele created AS7-4447:
------------------------------------
Summary: Operations add-jvm-option and remove-jvm-option don't work in a reasonable way
Key: AS7-4447
URL: https://issues.jboss.org/browse/AS7-4447
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Affects Versions: 7.1.1.Final
Reporter: Michael Voegele
Assignee: Brian Stansberry
The following operation (cli/dmr) can be executed many times.
{code:xml}
:add-jvm-option(jvm-option=-Xdebug)
{code}
The result will be:
{code:xml}
[domain@localhost:10099 jvm=default] :read-resource
{
"outcome" => "success",
"result" => {
"agent-lib" => undefined,
"agent-path" => undefined,
"env-classpath-ignored" => undefined,
"environment-variables" => undefined,
"heap-size" => "384m",
"java-agent" => undefined,
"java-home" => "C:/eplatform/java/jdk1.6.0",
"jvm-options" => [
"-Xdebug",
"-Xdebug",
"-Xdebug",
"-Xdebug",
"-Xdebug"
],
"max-heap-size" => "512m",
"max-permgen-size" => "128m",
"permgen-size" => "64m",
"stack-size" => "512k",
"type" => undefined
}
}
{code}
The same string (jvm-option) can be added several times, this should not be possible.
When removing a jvm-option, all jvm-options are removed:
{code:xml}
:remove-jvm-option(jvm-option=foo)
{code}
results in:
{code:xml}
[domain@localhost:10099 jvm=default] :remove-jvm-option(jvm-option=foo)
{
"outcome" => "success",
"result" => undefined,
"server-groups" => undefined
}
[domain@localhost:10099 jvm=default] :read-resource
{
"outcome" => "success",
"result" => {
"agent-lib" => undefined,
"agent-path" => undefined,
"env-classpath-ignored" => undefined,
"environment-variables" => undefined,
"heap-size" => "384m",
"java-agent" => undefined,
"java-home" => "C:/eplatform/java/jdk1.6.0",
"jvm-options" => [],
"max-heap-size" => "512m",
"max-permgen-size" => "128m",
"permgen-size" => "64m",
"stack-size" => "512k",
"type" => undefined
}
}
{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
14 years, 2 months
[JBoss JIRA] (AS7-3347) Datasources installed via deployment not shown in the management model
by Dominik Pospisil (JIRA)
Dominik Pospisil created AS7-3347:
-------------------------------------
Summary: Datasources installed via deployment not shown in the management model
Key: AS7-3347
URL: https://issues.jboss.org/browse/AS7-3347
Project: Application Server 7
Issue Type: Bug
Components: CLI, Domain Management
Affects Versions: 7.1.0.Final
Reporter: Dominik Pospisil
Assignee: Alexey Loubyansky
Datasources installed via deployment are not shown in the management model. I am not quite sure if this is intended or not but I see this as serious usability issue. How is the user supposed to quess the driver name installed via deployment to be able to manage data sources using this driver?
[standalone@localhost:9999 /] ls /subsystem=datasources/jdbc-driver
h2
[standalone@localhost:9999 /] deploy /usr/share/java/postgresql-jdbc3.jar
[standalone@localhost:9999 /] ls /subsystem=datasources/jdbc-driver
h2
[standalone@localhost:9999 /]
--
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, 2 months
[JBoss JIRA] (AS7-2088) CLI usability: Parse compound operation parameters
by Dominik Pospisil (Created) (JIRA)
CLI usability: Parse compound operation parameters
--------------------------------------------------
Key: AS7-2088
URL: https://issues.jboss.org/browse/AS7-2088
Project: Application Server 7
Issue Type: Feature Request
Components: CLI
Affects Versions: 7.1.0.Alpha1
Reporter: Dominik Pospisil
Assignee: Alexey Loubyansky
Currently, CLI does not parse compound operation parameters and relies on ModelNode.fromString() method.
This means that an user have to use "key" => "value" notation to denote compound parameters. This is inconsistent with the rest of CLI using key="value" notation.
As an example, to add https connector one needs to use:
/subsystem=web/connector=https:add(socket-binding=https, scheme=https, protocol="HTTP/1.1", enabled=true, ssl={ "certificate-key-file" =>"/tmp/test.key"}))
command instead of more straightforward:
/subsystem=web/connector=https:add(socket-binding=https, scheme=https, protocol="HTTP/1.1", enabled=true, ssl={certificate-key-file="/tmp/test.key"}))
This is never documented.
Also any exceptions thrown by ModelNode.fromString() are discarded. I think they should be reported back to the user. (DefaultCallbackHandler lines 448-453)
--
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, 2 months