[JBoss JIRA] (WFLY-5293) EJB3 method invocation statistics exposed incorrectly through JMX
by Stefano Coletta (JIRA)
[ https://issues.jboss.org/browse/WFLY-5293?page=com.atlassian.jira.plugin.... ]
Stefano Coletta commented on WFLY-5293:
---------------------------------------
I've found the same problem on wildfly-8.2.0.FInal. Could you confirm me the bug affect also wildfly-8.2.0.Final?
Thanks.
> EJB3 method invocation statistics exposed incorrectly through JMX
> -----------------------------------------------------------------
>
> Key: WFLY-5293
> URL: https://issues.jboss.org/browse/WFLY-5293
> Project: WildFly
> Issue Type: Bug
> Components: JMX
> Affects Versions: 9.0.1.Final
> Reporter: Arto Huusko
> Assignee: Kabir Khan
>
> EJB3 method invocation statistics, that is the "methods" attribute in an EJB3 session JMX object is exposed as CompositeDataSupport object that has the expected keys ("execution-time", and so on), but
> - the values for the keys are always null
> - there is only a single CompositeDataSupport object even when the session has several methods
> - the method name is not available.
> Possibly the invocation statistics should be exposed as an array of CompositeDataSupport objects where one of the keys is the method name.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (DROOLS-1012) kie-ci-osgi Activator doesn't register the ClassLoaderResolver on the ServiceRegistry
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1012?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on DROOLS-1012:
-------------------------------------------------
Ryan Zhang <rzhang(a)redhat.com> changed the Status of [bug 1293455|https://bugzilla.redhat.com/show_bug.cgi?id=1293455] from MODIFIED to ON_QA
> kie-ci-osgi Activator doesn't register the ClassLoaderResolver on the ServiceRegistry
> -------------------------------------------------------------------------------------
>
> Key: DROOLS-1012
> URL: https://issues.jboss.org/browse/DROOLS-1012
> Project: Drools
> Issue Type: Bug
> Reporter: Mario Fusco
> Assignee: Mario Fusco
> Fix For: 6.4.x
>
> Attachments: brms-fuse-integration-master.tgz
>
>
> kie-ci-osgi Activator doesn't register the ClassLoaderResolver on the ServiceRegistry. This implies that when the KieContainer is created in a OSGi environment it is not able to get an instance of the MavenClassLoaderResolver and then cannot create a ClassLoader including all the transitive dependencies of the kjar to be compiled.
> The attached project reproduces this issue. In order to run it, it's enough to do a mvn clean install of the project and issue the following commands in fuse:
> features:addurl mvn:com.redhat/brms-fuse-integration-features/0.0.1-SNAPSHOT/xml/features
> features:install brms-integration-bundle
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (DROOLS-1007) ArrayIndexOutOfBoundsException attempting to remove a rule containing a OR
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1007?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on DROOLS-1007:
-------------------------------------------------
Ryan Zhang <rzhang(a)redhat.com> changed the Status of [bug 1291994|https://bugzilla.redhat.com/show_bug.cgi?id=1291994] from MODIFIED to ON_QA
> ArrayIndexOutOfBoundsException attempting to remove a rule containing a OR
> --------------------------------------------------------------------------
>
> Key: DROOLS-1007
> URL: https://issues.jboss.org/browse/DROOLS-1007
> Project: Drools
> Issue Type: Bug
> Reporter: Mario Fusco
> Assignee: Mario Fusco
> Fix For: 6.4.x
>
>
> At the moment the association between a node and a rule is kept by a Map inside the node having the rule as key. This implementation is not taking count of the fact that the same node could be associated multiple times to the same rule that it is indeed what happens when a rule contains a OR.
> During the removal of such a rule the nodes of the rule are removed from the Rete starting from the RuleTerminalNodes (in this case the rule has more than one RTNs because of the OR). This means that when the first RTN is removed the Join and LIA nodes that are sources for that RTN at any level got completely disassociated from the rule when it is too early. That in the end causes the following exception when the engine tries to remove also the second RTN of that rule
> {code}
> java.lang.ArrayIndexOutOfBoundsException: 1
> at org.drools.core.phreak.AddRemoveRule.removeRule(AddRemoveRule.java:171)
> at org.drools.core.reteoo.ReteooBuilder.removeTerminalNode(ReteooBuilder.java:173)
> at org.drools.core.reteoo.ReteooBuilder.removeRule(ReteooBuilder.java:163)
> at org.drools.core.impl.KnowledgeBaseImpl.removeRule(KnowledgeBaseImpl.java:1635)
> at org.drools.core.impl.KnowledgeBaseImpl.removeRule(KnowledgeBaseImpl.java:1626)
> at org.drools.core.impl.KnowledgeBaseImpl.internalRemoveRule(KnowledgeBaseImpl.java:1610)
> at org.drools.core.impl.KnowledgeBaseImpl.removeRule(KnowledgeBaseImpl.java:1581)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (DROOLS-1017) NPE deleting an expired event in equality mode
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/DROOLS-1017?page=com.atlassian.jira.plugi... ]
RH Bugzilla Integration commented on DROOLS-1017:
-------------------------------------------------
Ryan Zhang <rzhang(a)redhat.com> changed the Status of [bug 1295786|https://bugzilla.redhat.com/show_bug.cgi?id=1295786] from MODIFIED to ON_QA
> NPE deleting an expired event in equality mode
> ----------------------------------------------
>
> Key: DROOLS-1017
> URL: https://issues.jboss.org/browse/DROOLS-1017
> Project: Drools
> Issue Type: Bug
> Reporter: Mario Fusco
> Assignee: Mario Fusco
> Fix For: 6.4.x
>
>
> Trying to delete an already expired event in equality mode causes the following NPE in the TMS:
> {code}
> java.lang.NullPointerException
> at org.drools.core.common.NamedEntryPoint.delete(NamedEntryPoint.java:506)
> at org.drools.core.common.NamedEntryPoint.delete(NamedEntryPoint.java:442)
> at org.drools.core.common.DefaultAgenda.fireActivation(DefaultAgenda.java:1120)
> at org.drools.core.phreak.RuleExecutor.fire(RuleExecutor.java:121)
> at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:74)
> at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1003)
> at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1346)
> at org.drools.core.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1284)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.internalFireAllRules(StatefulKnowledgeSessionImpl.java:1303)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1293)
> at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:1274)
> at org.drools.compiler.integrationtests.CepEspTest.testDeleteExpiredEventWithTimestampAndEqualityKey(CepEspTest.java:5682)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFLY-5994) RejectedExecutionException: XNIO007007 on WFLY 10 CR5 shutdown
by Rostislav Svoboda (JIRA)
Rostislav Svoboda created WFLY-5994:
---------------------------------------
Summary: RejectedExecutionException: XNIO007007 on WFLY 10 CR5 shutdown
Key: WFLY-5994
URL: https://issues.jboss.org/browse/WFLY-5994
Project: WildFly
Issue Type: Bug
Components: Remoting
Affects Versions: 10.0.0.CR5
Reporter: Rostislav Svoboda
Assignee: David Lloyd
Priority: Blocker
WFLY 10 CR5 logs Error message on shutdown (both standalone and domain mode). This happens regularly, platforms like Fedora 23, RHEL 6, RHEL 7. WFLY 10 CR5 does not have clean start & stop.
*reproduce*
\# start WFLY 10 CR5
{noformat}
$ ./standalone.sh
...
10:30:46,536 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: WildFly Full 10.0.0.CR5 (WildFly Core 2.0.5.Final) started in 3999ms - Started 267 of 569 services (386 services are lazy, passive or on-demand)
{noformat}
\# shutdown via CLI
{noformat}
$ ./jboss-cli.sh -c shutdown
{noformat}
\# check console where WFLY 10 CR5 was started
{noformat}
10:30:53,937 ERROR [org.jboss.remoting.resource] (MSC service thread 1-3) Close action for Connection handler for Remoting connection 4181b134 to /127.0.0.1:51703 failed to execute (resource may be left in an indeterminate state): java.util.concurrent.RejectedExecutionException: XNIO007007: Thread is terminating
at org.xnio.nio.WorkerThread.execute(WorkerThread.java:588)
at org.jboss.remoting3.remote.RemoteConnection$RemoteWriteListener.send(RemoteConnection.java:327)
at org.jboss.remoting3.remote.RemoteConnection.send(RemoteConnection.java:142)
at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequestBody(RemoteConnectionHandler.java:289)
at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequestBody(RemoteConnectionHandler.java:278)
at org.jboss.remoting3.remote.RemoteConnectionHandler.sendCloseRequest(RemoteConnectionHandler.java:235)
at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAction(RemoteConnectionHandler.java:413)
at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
at org.jboss.remoting3.ConnectionImpl.closeAction(ConnectionImpl.java:54)
at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
at org.jboss.remoting3.EndpointImpl.closeAction(EndpointImpl.java:225)
at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
at org.jboss.as.remoting.EndpointService.stop(EndpointService.java:98)
at org.jboss.msc.service.ServiceControllerImpl$StopTask.stopService(ServiceControllerImpl.java:2056)
at org.jboss.msc.service.ServiceControllerImpl$StopTask.run(ServiceControllerImpl.java:2017)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{noformat}
{noformat}
10:30:53,936 ERROR [org.jboss.remoting.resource] (Remoting "rs:MANAGEMENT" task-8) Close action for Channel ID 1158edde (inbound) of Remoting connection 4181b134 to /127.0.0.1:51703 failed to execute (resource may be left in an indeterminate state): java.util.concurrent.RejectedExecutionException: XNIO007007: Thread is terminating
at org.xnio.nio.WorkerThread.execute(WorkerThread.java:588)
at org.jboss.remoting3.remote.RemoteConnection$RemoteWriteListener.send(RemoteConnection.java:327)
at org.jboss.remoting3.remote.RemoteConnection.send(RemoteConnection.java:138)
at org.jboss.remoting3.remote.RemoteConnectionChannel.closeReadsAndWrites(RemoteConnectionChannel.java:261)
at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:534)
at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeAsync(AbstractHandleableCloseable.java:372)
at org.jboss.remoting3.remote.RemoteConnectionHandler.closeAllChannels(RemoteConnectionHandler.java:437)
at org.jboss.remoting3.remote.RemoteConnectionHandler.handleConnectionClose(RemoteConnectionHandler.java:114)
at org.jboss.remoting3.remote.RemoteReadListener$1$1.run(RemoteReadListener.java:57)
at org.jboss.remoting3.EndpointImpl$TrackingExecutor$1.run(EndpointImpl.java:717)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JASSIST-244) ProxyFactory will not invoke MethodHandler on method declared in parent classes.
by Elis Edlund (JIRA)
[ https://issues.jboss.org/browse/JASSIST-244?page=com.atlassian.jira.plugi... ]
Elis Edlund commented on JASSIST-244:
-------------------------------------
is there any timeplan for when 3.21.0-GA will be released?
> ProxyFactory will not invoke MethodHandler on method declared in parent classes.
> --------------------------------------------------------------------------------
>
> Key: JASSIST-244
> URL: https://issues.jboss.org/browse/JASSIST-244
> Project: Javassist
> Issue Type: Bug
> Affects Versions: 3.18.0-GA, 3.19.0-GA
> Environment: Windows 7, Java 1.7 and 1.8
> Reporter: Elis Edlund
> Assignee: Shigeru Chiba
> Priority: Blocker
> Fix For: 3.21.0-GA
>
> Attachments: IssueMethodsInParentShouldCallTheMethodHandler.java
>
>
> ProxyFactory factory = new ProxyFactory();
> factory.setSuperclass(Extended.class);
> Extended enchantedObject = (Extended) factory.create(null, null, METHOD_HANDLER);
> Does not work as intended with version newer than 3.17.0-GA
> invoking methods on the created object will go through the METHOD_HANDLER long as the method does not belong to a parent class of 'Extended'. if the method is comes from a parent class of 'Extended' the METHOD_HANDLER will not be used at all (which it was in previous versions)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFLY-5993) Add a testcase for WFCORE-1226
by Chao Wang (JIRA)
Chao Wang created WFLY-5993:
-------------------------------
Summary: Add a testcase for WFCORE-1226
Key: WFLY-5993
URL: https://issues.jboss.org/browse/WFLY-5993
Project: WildFly
Issue Type: Task
Components: Test Suite
Affects Versions: 10.0.0.CR5
Reporter: Chao Wang
Assignee: Chao Wang
since it's on wildfly-core 2.0.6.Final already, this adds a testcase for WFCORE-1226
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFLY-5613) Fixes of help tooltip of transaction configuration in Web Console
by Amos Feng (JIRA)
[ https://issues.jboss.org/browse/WFLY-5613?page=com.atlassian.jira.plugin.... ]
Amos Feng commented on WFLY-5613:
---------------------------------
[~harald.pehl] mention that it could be implemented in the HAL-1032 to get the meta data of attribute to say if it needs to restart/reload to take the effect.
so that every form which is based on the resource description will include this information. Please note that not all forms are based on the metadata from the management model.
we could remove the information such as "this attribute needs to restart/reload to take effect" in the descriptions.
> Fixes of help tooltip of transaction configuration in Web Console
> -----------------------------------------------------------------
>
> Key: WFLY-5613
> URL: https://issues.jboss.org/browse/WFLY-5613
> Project: WildFly
> Issue Type: Enhancement
> Components: Transactions
> Reporter: Ondřej Chaloupka
> Assignee: Amos Feng
> Priority: Minor
> Fix For: 10.0.0.Final
>
> Attachments: jts-tooltip-700.DR132.png
>
>
> I would like ask for changing text in transaction configuration helper tooltip (_Need Help?
> _). First there is an issue of not having an information that jts to be fully enabled is need to set subsystem of iiop orb as well (the same issue was for 6.4.0 https://bugzilla.redhat.com/show_bug.cgi?id=995439).
> Nevertheless I would like ask for a bit more general change of the text in the help webconsole tooltip
> Current text is
> {noformat}
> Default timeout: The default timeout.
> Enable tsm status: Whether the transaction status manager (TSM) service, needed for out of process recovery, should be provided or not..
> Journal store enable async io: Whether AsyncIO should be enabled for the journal store. Default is false. The server should be restarted for this setting to take effect.
> Jts: If true this enables the Java Transaction Service.
> Node identifier: Used to set the node identifier on the core environment.
> Statistics enabled: Whether statistics should be enabled.
> Use journal store: Use the journal store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file system file per transaction log. The server should be restarted for this setting to take effect. It's alternative to jdbc based store.
> {noformat}
> {noformat}
> Process id uuid: Indicates whether the transaction manager should use a UUID based process id.
> Process id socket binding: The name of the socket binding configuration to use if the transaction manager should use a socket-based process id. Will be 'undefined' if 'process-id-uuid' is 'true'; otherwise must be set.
> Process id socket max ports: The maximum number of ports to search for an open port if the transaction manager should use a socket-based process id. If the port specified by the socket binding referenced in 'process-id-socket-binding' is occupied, the next higher port will be tried until an open port is found or the number of ports specified by this attribute have been tried. Will be 'undefined' if 'process-id-uuid' is 'true'.
> {noformat}
> {noformat}
> Socket binding: Used to reference the correct socket binding to use for the recovery environment.
> Status socket binding: Used to reference the correct socket binding to use for the transaction status manager.
> Recovery listener: Used to specify if the recovery system should listen on a network socket or not.
> {noformat}
> {noformat}
> Object store path: Denotes a relative or absolute filesystem path denoting where the transaction manager object store should store data. By default the value is treated as relative to the path denoted by the "relative-to" attribute.
> Object store relative to: References a global path configuration in the domain model, defaulting to the JBoss Application Server data directory (jboss.server.data.dir). The value of the "path" attribute will treated as relative to this path. Use an empty string to disable the default behavior and force the value of the "path" attribute to be treated as an absolute path.
> {noformat}
> {noformat}
> Use jdbc store: Use the jdbc store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file system file per transaction log. The server should be restarted for this setting to take effect. It's alternative to Horneq based store
> Jdbc action store drop table: Configure if jdbc action store should drop tables. Default is false. The server should be restarted for this setting to take effect.
> Jdbc action store table prefix: Optional prefix for table used to write transcation logs in configured jdbc action store. The server should be restarted for this setting to take effect.
> Jdbc communication store drop table: Configure if jdbc communication store should drop tables. Default is false. The server should be restarted for this setting to take effect.
> Jdbc communication store table prefix: Optional prefix for table used to write transcation logs in configured jdbc communication store. The server should be restarted for this setting to take effect.
> Jdbc state store drop table: Configure if jdbc state store should drop tables. Default is false. The server should be restarted for this setting to take effect.
> Jdbc state store table prefix: Optional prefix for table used to write transcation logs in configured jdbc state store. The server should be restarted for this setting to take effect.
> Jdbc store datasource: Jndi name of non-XA datasource used. Datasource sghould be define in datasources subsystem. The server should be restarted for this setting to take effect.
> {noformat}
> I would propose the following changes in the tooltip text
> *Attributes*
> * Default timeout
> ** The default timeout for a transaction managed by the transaction manager.
> * Enable tsm status
> ** Whether the transaction status manager (TSM) service, needed for out of process recovery, should be provided or not.
> * Journal store enable async io
> ** Whether AsyncIO should be enabled for the journal store. Default is false. For this settings being active journal natives libraries needs to be available. The server should be restarted for this setting to take effect.
> * Jts
> ** If true this enables the Java Transaction Service. Use of the JTS needs configuration in IIOP OpenJDK where Transactions parameter needs to be set to full. The server should be restarted for this setting to take effect.
> * Node identifier
> ** Used to set the node identifier on the core environment. Each server should have this identifier unique. It's an identifier which differentiates XA transactions as created by this node. The server should be restarted for this setting to take effect.
> * Statistics enabled
> ** Whether transaction statistics should be enabled. The transaction statistics could be seen in section Runtime > Monitor > Subsystems > Transactions. The server should be reloaded for this setting to take effect.
> * Use journal store
> ** Use the journal store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store creates normally one file file per transaction log. The journal one consists from one file for all the transactions. It's alternative to jdbc based store. The server should be restarted for this setting to take effect.
> *Process ID* + *Recovery*
> Add information that for settings these attributes taking effect the server needs to be reloaded.
> *Path*
> * Object store path
> ** Denotes a relative or absolute filesystem path denoting where the transaction manager object store should store data. By default the value is treated as relative to the path denoted by the "relative-to" attribute. This settings is valid when default or journal store is used. It's not used when jdbc journal store is used. The server should be reloaded for this setting to take effect.
> * Object store relative to
> ** References a global path configuration in the domain model, defaulting to the Application Server data directory (jboss.server.data.dir). The value of the "Object store path" attribute will treated as relative to this path. Use an empty string to disable the default behavior and force the value of the "Object store path" attribute to be treated as an absolute path. The server should be reloaded for this setting to take effect.
> *JDBC*
> * Use jdbc store
> ** Use the jdbc store for writing transaction logs. Set to true to enable and to false to use the default log store type. The default log store is normally one file file per transaction log. It's alternative to journal based store. The server should be restarted for this setting to take effect.
> * Jdbc store datasource
> ** Jndi name of non-XA datasource used. Datasource sghould be define in datasources subsystem. For this would work the non-XA datasource has to be marked as jta="false". The server should be restarted for this setting to take effect.
> ...the rest of the information is ok from my point of view
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (WFCORE-1277) Embed-server from CLI launch shows twice prompt string
by Chao Wang (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1277?page=com.atlassian.jira.plugi... ]
Chao Wang commented on WFCORE-1277:
-----------------------------------
I have rebased the PR and added one more line "consoleBuffer.setPrompted(false);" inside Console.java. After that, I can no longer see the double prompt issue, and wildfly-core and wilfy tests are both passed.
About the failed CtrlCTestCase, it tries to check prompt Username and Password on CLI connection. Thus, I have following steps to see the failure with your two commits:
1. comment out line "<local default-user="$local" skip-group-loading="true"/>" in standalone.xml
2. use add-user.sh to create a new Management User with password.
3. run standalone.sh to start server, and run jboss-cli.sh -c, it will ask user to input username and password as:
{noformat}
Authenticating against security realm: ManagementRealm
Username
{noformat}:
including your two commits, it misses the "Username:" prompt as:
{noformat}
Authenticating against security realm: ManagementRealm
{noformat}
That's why the CtrlCTestCase fails at line "boolean promptFound = cli.executeInteractive("Username");" I think it's due to the remove of this [block|https://github.com/aeshell/aesh/commit/91e4696338c80f2e1f3e7a77a7d8...] which is supposed to display prompt when it sets new prompt "Username" (in this case)
> Embed-server from CLI launch shows twice prompt string
> ------------------------------------------------------
>
> Key: WFCORE-1277
> URL: https://issues.jboss.org/browse/WFCORE-1277
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI
> Affects Versions: 2.0.5.Final
> Reporter: Chao Wang
> Assignee: Ståle Pedersen
> Priority: Minor
>
> {noformat}
> When I launch an embed-server from CLI, it displays twice [standalone@embedded /] [standalone@embedded /] for the first time.
> [wangc@dhcp-128-40 wildfly-10.0.0.Final-SNAPSHOT]$ sh bin/jboss-cli.sh
> You are disconnected at the moment. Type 'connect' to connect to the server or 'help' for the list of supported commands.
> [disconnected /] embed-server
> [standalone@embedded /] [standalone@embedded /] ls
> core-service launch-type=EMBEDDED product-version=undefined
> deployment management-major-version=4 profile-name=undefined
> deployment-overlay management-micro-version=0 release-codename=Kenny
> extension management-minor-version=0 release-version=2.0.5.Final
> interface name=dhcp-128-40 running-mode=ADMIN_ONLY
> path namespaces=[] schema-locations=[]
> socket-binding-group organization=undefined server-state=running
> subsystem process-type=Server suspend-state=RUNNING
> system-property product-name=undefined uuid=8c4ede2f-8e14-48bf-9eaf-73947e23edcf
> [standalone@embedded /] quit
> {noformat}
> This does not happen in 2.0.4.Final.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months