[JBoss JIRA] (AS7-4167) Admin console: cannot set attribute max-attempts of modcluster subsystem
by Jan Martiska (JIRA)
Jan Martiska created AS7-4167:
---------------------------------
Summary: Admin console: cannot set attribute max-attempts of modcluster subsystem
Key: AS7-4167
URL: https://issues.jboss.org/browse/AS7-4167
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.1.Final
Reporter: Jan Martiska
Assignee: Heiko Braun
Priority: Minor
Under Networking tab of modcluster configuration - property "Max Attempts" cannot be set- console references it as "max-attemps" instead of the correct "max-attempts"
{noformat}
{
"outcome" => "failed",
"result" => {"step-1" => {
"outcome" => "failed",
"failure-description" => "JBAS014792: Unknown attribute max-attemps",
"rolled-back" => true
}},
"failure-description" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014792: Unknown attribute max-attemps"}},
"rolled-back" => true,
"response-headers" => {"process-state" => "reload-required"}
}
{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
13 years, 7 months
[JBoss JIRA] (AS7-4166) Admin console: cannot set attribute auto-enable-contexts of modcluster subsystem
by Jan Martiska (JIRA)
Jan Martiska created AS7-4166:
---------------------------------
Summary: Admin console: cannot set attribute auto-enable-contexts of modcluster subsystem
Key: AS7-4166
URL: https://issues.jboss.org/browse/AS7-4166
Project: Application Server 7
Issue Type: Bug
Components: Console
Affects Versions: 7.1.1.Final
Reporter: Jan Martiska
Assignee: Heiko Braun
Priority: Minor
Under Web Contexts tab of modcluster configuration - property "Auto Enable Contexts" cannot be set- console references it as "auto-enableContexts" instead of the correct "auto-enable-contexts"
{noformat}
{
"outcome" => "failed",
"result" => {"step-1" => {
"outcome" => "failed",
"failure-description" => "JBAS014792: Unknown attribute auto-enableContexts",
"rolled-back" => true
}},
"failure-description" => {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-1" => "JBAS014792: Unknown attribute auto-enableContexts"}},
"rolled-back" => true,
"response-headers" => {"process-state" => "reload-required"}
{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
13 years, 7 months
[JBoss JIRA] (AS7-2385) Management - readding file handler logger fails
by Dominik Pospisil (Created) (JIRA)
Management - readding file handler logger fails
-----------------------------------------------
Key: AS7-2385
URL: https://issues.jboss.org/browse/AS7-2385
Project: Application Server 7
Issue Type: Bug
Components: Domain Management, Logging
Affects Versions: 7.1.0.Beta1
Reporter: Dominik Pospisil
Assignee: Brian Stansberry
Removing and adding file handler fails. Perhaps remove operation does not clean up all resources properlly.
Steps to reproduce:
[standalone@localhost:9999 /] /subsystem=logging/file-handler=test-fh:add(name="test-fh", level="WARN", file={"path" => "/home/dpospisi/testfh.log"})
{"outcome" => "success"}
[standalone@localhost:9999 /] /subsystem=logging/file-handler=test-fh:remove
{"outcome" => "success"}
[standalone@localhost:9999 /] /subsystem=logging/file-handler=test-fh:add(name="test-fh", level="WARN", file={"path" => "/home/dpospisi/testfh.log"})
{
"outcome" => "failed",
"failure-description" => "Operation handler failed: org.jboss.msc.service.DuplicateServiceException: Service jboss.logging.handler-file.test-fh is already registered",
"rolled-back" => true
}
[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
13 years, 7 months
[JBoss JIRA] (AS7-2873) EJB not defining an EJB 2 view method should not deploy
by Carlo de Wolf (Created) (JIRA)
EJB not defining an EJB 2 view method should not deploy
-------------------------------------------------------
Key: AS7-2873
URL: https://issues.jboss.org/browse/AS7-2873
Project: Application Server 7
Issue Type: Bug
Components: EJB
Reporter: Carlo de Wolf
Assignee: Stuart Douglas
A bean which does not implement the sayHello method of the following EJB 2 remote view:
{code:title=HelloRemote.java}
public interface HelloRemote extends EJBObject {
String sayHello(String name) throws RemoteException;
}
{code}
gets the following exception during invocation:
{noformat}
Caused by: javax.ejb.EJBException: org.jboss.invocation.CannotProceedException: INV-00002:Invocation cannot proceed (end of interceptor chain has been hit)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:241)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:316)
at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:201)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.remote.EJBRemoteTransactionPropogatingInterceptor.processInvocation(EJBRemoteTransactionPropogatingInterceptor.java:86)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:70)
at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:288)
at org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories$1.processInvocation(EjbExceptionTransformingInterceptorFactories.java:56)
... 126 more
{noformat}
Instead the EJB should not have deployed properly and throw a DeploymentException.
--
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, 7 months
[JBoss JIRA] (LOGTOOL-52) Remove string concatenation during message construction
by David Lloyd (JIRA)
David Lloyd created LOGTOOL-52:
----------------------------------
Summary: Remove string concatenation during message construction
Key: LOGTOOL-52
URL: https://issues.jboss.org/browse/LOGTOOL-52
Project: Log Tool
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Bill Burke
Assignee: David Lloyd
Fix For: 1.0.3.Final, 1.1.0.Beta1
I have noticed a small deficiency in your otherwise completely excellent software! As it turns out, the source code generation produces superfluous string concatenations. It would be more efficient if the string concatenation were to happen either during processing, or within the right-hand side of the static field assignment expression in the generated classes.
Keep up the top-notch work on the definitely not over-engineered project! Excelsior!!
--
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, 7 months