[JBoss JIRA] Created: (AS7-1877) cd to subsystems that don't exist
by Bill Meyer (JIRA)
cd to subsystems that don't exist
---------------------------------
Key: AS7-1877
URL: https://issues.jboss.org/browse/AS7-1877
Project: Application Server 7
Issue Type: Bug
Components: CLI
Affects Versions: 7.0.1.Final
Environment: JBoss AS 7.0.1 CLI interface
Reporter: Bill Meyer
Assignee: Alexey Loubyansky
The CLI utility allows you to cd to subsystems (one example) that don't exist.
For example, (yes the jms subsystem was merged into the messaging subsystem), if I execute the following:
[standalone@localhost:9999 /] pwd
/
[standalone@localhost:9999 /] cd /subsystem=jms
[standalone@localhost:9999 subsystem=jms] ls
[standalone@localhost:9999 subsystem=jms]
I get no error message that I've cd'd into something that doesn't exist. Internal JBoss SAs have done some useability testing and agree that this is very confusing functionality. Either an error message should be displayed preventing you from executing the cd command, or some sort of feedback needs to be provided as to why this is expected behavior.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (AS7-4770) read-attribute on servelt causes NPE
by Stan Silvert (JIRA)
Stan Silvert created AS7-4770:
---------------------------------
Summary: read-attribute on servelt causes NPE
Key: AS7-4770
URL: https://issues.jboss.org/browse/AS7-4770
Project: Application Server 7
Issue Type: Bug
Components: Web
Affects Versions: 7.2.0.Alpha1
Reporter: Stan Silvert
Assignee: Remy Maucherat
Attempt to read any attribute exposed by WebDeploymentServletDefinition results in NPE:
On CLI
{noformat}
/deployment=InjectionTest.war/subsystem=web/servlet=Faces_Servlet/:read-attribute(name=min-time)
{
"outcome" => "failed",
"failure-description" => "JBAS014749: Operation handler failed: null",
"rolled-back" => true
}
{noformat}
On server:
{noformat}
12:32:49,861 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 17) JBAS014612: Operation ("read-attribute") failed - address: ([
("deployment" => "InjectionTest.war"),
("subsystem" => "web"),
("servlet" => "Faces_Servlet")
]): java.lang.NullPointerException
at org.jboss.as.web.WebDeploymentServletDefinition$3.handle(WebDeploymentServletDefinition.java:57) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.web.WebDeploymentServletDefinition$AbstractMetricsHandler$1.execute(WebDeploymentServletDefinition.java:97) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.ja
r:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:397) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNA
PSHOT]
at org.jboss.as.controller.AbstractOperationContext.doCompleteStep(AbstractOperationContext.java:284) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-
SNAPSHOT]
at org.jboss.as.controller.AbstractOperationContext.completeStep(AbstractOperationContext.java:211) [jboss-as-controller-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SN
APSHOT]
at org.jboss.as.web.WebDeploymentServletDefinition$AbstractMetricsHandler.execute(WebDeploymentServletDefinition.java:103) [jboss-as-web-7.2.0.Alpha1-SNAPSHOT.jar
:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.controller.operations.global.GlobalOperationHandlers$ReadAttributeHandler.doExecute(GlobalOperationHandlers.java:465) [jboss-as-controller-7.2.0.A
lpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
at org.jboss.as.controller.operations.global.GlobalOperationHandlers$AbstractMultiTargetHandler.execute(GlobalOperationHandlers.java:997) [jboss-as-controller-7.2
.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
{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, 10 months
[JBoss JIRA] (JBLOGGING-78) SMTPAppender Not sending mails
by Nisha Suresh (JIRA)
Nisha Suresh created JBLOGGING-78:
-------------------------------------
Summary: SMTPAppender Not sending mails
Key: JBLOGGING-78
URL: https://issues.jboss.org/browse/JBLOGGING-78
Project: JBoss Logging
Issue Type: Task
Security Level: Public (Everyone can see)
Components: jboss-logging-log4j
Environment: JDK1.6
Reporter: Nisha Suresh
Assignee: David Lloyd
I have enabled the SMTPAppender for threshold level "ERROR". After that when an error occurs in the application the server.log is showing like:
2012-01-27 14:20:58,565 FINE [javax.activation] (http-127.0.0.1-8090-1) MailcapCommandMap: createDataContentHandler for text/plain
2012-01-27 14:20:58,565 FINE [javax.activation] (http-127.0.0.1-8090-1) search DB #1
2012-01-27 14:20:58,565 FINE [javax.activation] (http-127.0.0.1-8090-1) got content-handler
2012-01-27 14:20:58,565 FINE [javax.activation] (http-127.0.0.1-8090-1) class com.sun.mail.handlers.text_plain
No other mail sending errors are shown. What does this log actually means?
Why the mails are not getting send?
--
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, 10 months
[JBoss JIRA] (AS7-2653) Intermittent failures in ServerManagementTestCase
by Brian Stansberry (Created) (JIRA)
Intermittent failures in ServerManagementTestCase
-------------------------------------------------
Key: AS7-2653
URL: https://issues.jboss.org/browse/AS7-2653
Project: Application Server 7
Issue Type: Task
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Emanuel Muckenhuber
Fix For: 7.1.0.CR1
I'm seeing this fairly frequently:
Tests run: 48, Failures: 1, Errors: 0, Skipped: 2, Time elapsed: 117.8 sec <<< FAILURE!
testAddAndRemoveServer(org.jboss.as.test.integration.domain.suites.ServerManagementTestCase) Time elapsed: 6.298 sec <<< FAILURE!
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:92)
at org.junit.Assert.assertTrue(Assert.java:43)
at org.junit.Assert.assertTrue(Assert.java:54)
at org.jboss.as.test.integration.domain.suites.ServerManagementTestCase.testAddAndRemoveServer(ServerManagementTestCase.java:153)
I'm going to @Ignore the test.
--
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, 10 months
[JBoss JIRA] Created: (JBRULES-3157) Add information such as line number or source code in VerifierComponent
by Jérémie Lagarde (JIRA)
Add information such as line number or source code in VerifierComponent
-----------------------------------------------------------------------
Key: JBRULES-3157
URL: https://issues.jboss.org/browse/JBRULES-3157
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-verifier
Reporter: Jérémie Lagarde
Assignee: Mark Proctor
Priority: Optional
We can link the VerifierComponent with their descriptions.
This provides a simple access to information from the descriptions of the component or its associated VerifierMessageBase.
I tested this by adding to the VerifierComponent constructor the BaseDescr :
public abstract class VerifierComponent implements Comparable<VerifierComponent>, Cause {
private BaseDescr descr;
public VerifierComponent(BaseDescr descr) {
this.descr = descr;
}
...
}
And integrate that in all Visitors.
This seems to work. ( https://github.com/jerr/drools/tree/line-number-in-verifier )
What do you think of this, I can add test cases and provide a patch or git pull request.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months