[JBoss JIRA] (AS7-5534) read-config-as-xml on the domain node throws an ExecutionException
by Jeff Mesnil (JIRA)
Jeff Mesnil created AS7-5534:
--------------------------------
Summary: read-config-as-xml on the domain node throws an ExecutionException
Key: AS7-5534
URL: https://issues.jboss.org/browse/AS7-5534
Project: Application Server 7
Issue Type: Bug
Components: Domain Management
Reporter: Jeff Mesnil
Assignee: Brian Stansberry
on AS7 master branch
{noformat}
[disconnected /] connect
[domain@localhost:9999 /][domain@localhost:9999 /] :read-config-as-xml
Communication error: java.util.concurrent.ExecutionException: Operation failed
[disconnected /]
{noformat}
There is no log or warning in the domain.sh output.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] (AS7-5491) CLI error when data is over 64k
by Dennis Reed (JIRA)
Dennis Reed created AS7-5491:
--------------------------------
Summary: CLI error when data is over 64k
Key: AS7-5491
URL: https://issues.jboss.org/browse/AS7-5491
Project: Application Server 7
Issue Type: Bug
Components: CLI
Affects Versions: 7.1.2.Final (EAP)
Reporter: Dennis Reed
Assignee: Alexey Loubyansky
Running a command from the CLI that generates too much data aborted with an error:
[standalone@localhost:9999 /] /core-service=service-container:dump-services
Communication error: java.util.concurrent.ExecutionException: Operation failed
[disconnected /]
The root cause is only logged at debug level in server.log:
16:12:15,887 DEBUG [org.jboss.as.protocol] (management-handler-thread - 7) active-op (1846420313) failed null: java.io.UTFDataFormatException: encoded string too long: 96453 bytes
at java.io.DataOutputStream.writeUTF(DataOutputStream.java:347) [rt.jar:1.6.0_24]
at java.io.DataOutputStream.writeUTF(DataOutputStream.java:306) [rt.jar:1.6.0_24]
at org.jboss.as.protocol.mgmt.FlushableDataOutputImpl.writeUTF(FlushableDataOutputImpl.java:109) [jboss-as-protocol-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
at org.jboss.dmr.StringModelValue.writeExternal(StringModelValue.java:46) [jboss-dmr-1.1.1.Final-redhat-1.jar:1.1.1.Final-redhat-1]
at org.jboss.dmr.ModelNode.writeExternal(ModelNode.java:1476) [jboss-dmr-1.1.1.Final-redhat-1.jar:1.1.1.Final-redhat-1]
at org.jboss.dmr.ObjectModelValue.writeExternal(ObjectModelValue.java:75) [jboss-dmr-1.1.1.Final-redhat-1.jar:1.1.1.Final-redhat-1]
at org.jboss.dmr.ModelNode.writeExternal(ModelNode.java:1476) [jboss-dmr-1.1.1.Final-redhat-1.jar:1.1.1.Final-redhat-1]
at org.jboss.as.controller.remote.ModelControllerClientOperationHandler$ExecuteRequestHandler$1.execute(ModelControllerClientOperationHandler.java:116) [jboss-as-controller-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
at org.jboss.as.protocol.mgmt.AbstractMessageHandler$2$1.doExecute(AbstractMessageHandler.java:295) [jboss-as-protocol-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
at org.jboss.as.protocol.mgmt.AbstractMessageHandler$AsyncTaskRunner.run(AbstractMessageHandler.java:512) [jboss-as-protocol-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_24]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_24]
at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_24]
at org.jboss.threads.JBossThread.run(JBossThread.java:122) [jboss-threads-2.0.0.GA-redhat-1.jar:2.0.0.GA-redhat-1]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 8 months
[JBoss JIRA] (AS7-4437) Pls add a dmr handler to add and remove a single environment variable
by Michael Voegele (JIRA)
Michael Voegele created AS7-4437:
------------------------------------
Summary: Pls add a dmr handler to add and remove a single environment variable
Key: AS7-4437
URL: https://issues.jboss.org/browse/AS7-4437
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Affects Versions: 7.1.1.Final
Reporter: Michael Voegele
Assignee: Brian Stansberry
For adding a single jvm-option, operations exist for convenience:
add-jvm-option
remove-jvm-option
The same would be good for environment variables:
add-environment-variable
remove-environment-variable
At the moment, the same can only be achieved by writing the whole attribute environment-variables, which does not allow to add a *single* variable (if some already exist, the existing ones have to be included when writing the attribute):
{code:xml}
{
"operation" => "write-attribute",
"address" => [
("host" => "master"),
("server-config" => "server-1"),
("jvm" => "default")
],
"name" => "environment-variables",
"value" => [
{"foo1" => "bar1"},
{"foo2" => "bar2"}
]
}
{code}
Operations write-attribute and undefine-attribute have to be used.
--
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
13 years, 8 months
[JBoss JIRA] (AS7-5432) TransactionRolledbackLocalException doesn't reference the originating exception
by Barnabas Bodnar (JIRA)
Barnabas Bodnar created AS7-5432:
------------------------------------
Summary: TransactionRolledbackLocalException doesn't reference the originating exception
Key: AS7-5432
URL: https://issues.jboss.org/browse/AS7-5432
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.1.1.Final
Reporter: Barnabas Bodnar
Assignee: jaikiran pai
Priority: Minor
If a runtime-exception thrown by an EJB v.2x application leads to javax.ejb.TransactionRolledbackLocalException (s. org.jboss.as.ejb3.tx.CMTTxInterceptor.handleInCallerTx(...)), the TransactionRolledbackLocalException doesn't reference the originating exception (either as getCause() or as getCausedByException()).
The originating exception gets in org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories.LOCAL_INSTANCE lost: the javax.ejb.EJBTransactionRolledbackException catched here does still contain it, it will, however, not be propagated to the javax.ejb.TransactionRolledbackLocalException created here.
This behavior also deviates from that in the case of a locally started transaction: the wrapping javax.ejb.EJBException (s. org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(...)) is thrown unchanged to the caller (s. org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories.LOCAL_INSTANCE) and it references the originating exception both as getCause() and as getCausedByException().
--
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
13 years, 8 months