[JBoss JIRA] (AS7-6012) AS7 violating alternate client view of EJB 3.1 spec
by John Ament (JIRA)
John Ament created AS7-6012:
-------------------------------
Summary: AS7 violating alternate client view of EJB 3.1 spec
Key: AS7-6012
URL: https://issues.jboss.org/browse/AS7-6012
Project: Application Server 7
Issue Type: Bug
Components: EJB
Reporter: John Ament
Assignee: jaikiran pai
Section 4.4.2.2 of the EJB 3.1 spec states that the following JNDI locations should be populated for "other client views," which includes remote. AS7 is using a highly custom pattern for this view. This is shown when trying to run the following test case in Arquillian:
@Remote
public interface RemoteDatabaseIntegrator {
public void runQuery(String query) throws SQLException;
}
@Remote(RemoteDatabaseIntegrator.class)
@Stateless(name="RemoteDatabaseIntegrator")
public class RemoteDatabaseIntegratorImpl implements RemoteDatabaseIntegrator {
@Resource(name="jdbc/AppDS")
private DataSource ds;
private Connection conn;
@PostConstruct
public void init() throws SQLException {
this.conn = ds.getConnection();
}
@PreDestroy
public void cleanup() throws SQLException {
this.conn.close();
}
public void runQuery(String query) throws SQLException {
this.conn.createStatement().execute(query);
}
}
@RunWith(Arquillian.class)
@RunAsClient
public class RemoteDatabaseIntegratorTest {
@Deployment(testable=false)
public static JavaArchive createTestArchive() {
return ShrinkWrap.create(JavaArchive.class,"test.jar")
.addClasses(RemoteDatabaseIntegrator.class,RemoteDatabaseIntegratorImpl.class);
}
private static final String JNDI_LOC = "?";
@Test
public void testDbServiceInjectionFailure() throws Exception{
Context context = createAS7Context();
RemoteDatabaseIntegrator dbIntegrator = (RemoteDatabaseIntegrator)context.lookup(JNDI_LOC);
dbIntegrator.runQuery("select 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
11 years, 10 months
[JBoss JIRA] (AS7-6020) Update slf4j-api dependency for module
by Bernd Eckenfels (JIRA)
Bernd Eckenfels created AS7-6020:
------------------------------------
Summary: Update slf4j-api dependency for module
Key: AS7-6020
URL: https://issues.jboss.org/browse/AS7-6020
Project: Application Server 7
Issue Type: Feature Request
Components: Build System, Logging
Affects Versions: 7.1.1.Final, 7.2.0.CR1
Reporter: Bernd Eckenfels
Assignee: Paul Gier
The org.slf4j-api artifact shipped with 7.1.1-final is at level 1.6.1 and I noticed that it is not upgraded with 7.2. There are newer 1.6.x versions but also the option to switch to 1.7.x which features vararg.
--
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
11 years, 10 months
[JBoss JIRA] (AS7-6018) NillableOrExpressionParameterValidator fails when undefining a nillable attribute
by Stefan Guilhen (JIRA)
Stefan Guilhen created AS7-6018:
-----------------------------------
Summary: NillableOrExpressionParameterValidator fails when undefining a nillable attribute
Key: AS7-6018
URL: https://issues.jboss.org/browse/AS7-6018
Project: Application Server 7
Issue Type: Bug
Affects Versions: 7.1.3.Final (EAP)
Reporter: Stefan Guilhen
Assignee: Stefan Guilhen
Fix For: 7.2.0.Alpha1, 7.1.4.Final (EAP)
Undefining a nillable attribute via CLI results in a validation error:
[standalone@localhost:9999 /] /subsystem=security/security-domain=other:undefine-attribute(name=cache-type)
{
"outcome" => "failed",
"failure-description" => "JBAS014746: value may not be null",
"rolled-back" => true
}
This is caused by the validateResolvedParameter method in the NillableOrExpressionParameterValidator. The method incorrectly qualifies the value as an expression when its undefined:
if (!value.isDefined()) {
if (!allowExpression) {
throw MESSAGES.nullNotAllowed(parameterName);
}
} else {
delegate.validateResolvedParameter(parameterName, value);
}
It should check the value type instead, just like validateParameter does.
--
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
11 years, 10 months
[JBoss JIRA] (AS7-6008) Logging transformers do not work
by Kabir Khan (JIRA)
Kabir Khan created AS7-6008:
-------------------------------
Summary: Logging transformers do not work
Key: AS7-6008
URL: https://issues.jboss.org/browse/AS7-6008
Project: Application Server 7
Issue Type: Bug
Reporter: Kabir Khan
Assignee: James Perkins
Trying to debug an issue in logging transformers when an old slave is connected to master's DC I noticed that SubsystemParsing11TestCase contains the transformers test. As mentioned in AS7-6007 this test was disabled and the parser does not work. It makes more sense to parse the latest xml and test transformation there, as I attempted to do in https://github.com/kabir/jboss-as/tree/logging-transformers-for-james. However, there are still some issues with the transformers there which needs to be fixed. The current stumbling block is:
{code}
[~/sourcecontrol/jboss-as7/git/jboss-as]
$more logging/target/surefire-reports/org.jboss.as.logging.LoggingSubsystemTestCase.txt
-------------------------------------------------------------------------------
Test set: org.jboss.as.logging.LoggingSubsystemTestCase
-------------------------------------------------------------------------------
Tests run: 2, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.816 sec <<< FAILURE!
testTransformers_1_1(org.jboss.as.logging.LoggingSubsystemTestCase) Time elapsed: 0.309 sec <<< ERROR!
java.lang.IllegalArgumentException: JBAS014880: No operation entry called 'add' registered at '[
("subsystem" => "logging"),
("logging-profile" => "test-profile"),
("console-handler" => "CONSOLE")
]'
at org.jboss.as.controller.operations.validation.OperationValidator.throwOrWarnAboutDescriptorProblem(OperationValidator.java:552)
at org.jboss.as.controller.operations.validation.OperationValidator.validateOperation(OperationValidator.java:123)
at org.jboss.as.controller.operations.validation.OperationValidator.validateOperations(OperationValidator.java:95)
at org.jboss.as.model.test.ModelTestModelControllerService.boot(ModelTestModelControllerService.java:136)
at org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:217)
at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:185)
at java.lang.Thread.run(Thread.java:680)
{code}
--
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
11 years, 10 months
[JBoss JIRA] (AS7-5170) add deployed JMS destinations to the Web console
by Jeff Mesnil (JIRA)
Jeff Mesnil created AS7-5170:
--------------------------------
Summary: add deployed JMS destinations to the Web console
Key: AS7-5170
URL: https://issues.jboss.org/browse/AS7-5170
Project: Application Server 7
Issue Type: Enhancement
Components: Console
Reporter: Jeff Mesnil
Assignee: Heiko Braun
The user can deploy JMS destinations as parts of deployed archives.
These destinations are manageable from the CLI and exposes their metrics
(e.g. /deployment=jboss-as-helloworld-mdb.war/subsystem=messaging/hornetq-server=default/jms-queue=HELLOWORLDMDBQueue)
It'd be useful for users if these deployed JMS destinations could display their metrics in the runtime tab of the Web console in addition to the regular JMS destinations
--
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
11 years, 10 months
[JBoss JIRA] (JBRULES-3661) NullPointerException at org.drools.base.evaluators.AfterEvaluatorDefinition$AfterEvaluator.getInterval(AfterEvaluatorDefinition.java:272)
by Kiran Kumar A (JIRA)
Kiran Kumar A created JBRULES-3661:
--------------------------------------
Summary: NullPointerException at org.drools.base.evaluators.AfterEvaluatorDefinition$AfterEvaluator.getInterval(AfterEvaluatorDefinition.java:272)
Key: JBRULES-3661
URL: https://issues.jboss.org/browse/JBRULES-3661
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Kiran Kumar A
Assignee: Mark Proctor
I am getting the below exception when creating knowledge base using knowledge agent.
The things I have done :
I have created a package in Guvnor
And uploaded a jar using 'New POJO Model Jar'
And declared some of the POJOs as events using 'New declarative MOdel'
I added role and timestamp annotations to declare them as events.
I wrote CEP rules. The below is the one of the rule.
rule 'Rule 1'
when
$eventA: EventA($eventId:eventId) from enrtry-point "STREAM1"
not EventB($eventId == eventId, this after[0s,3m] $eventA) from enrtry-point "STREAM1"
then
helper.doAction1($eventA);
I built package. And downloaded changeset.xml.
Copied the changeset to project classpath.
I created web application having rule engine as a component.
I tried creating knowledge base using knowledge agent.
ava.lang.NullPointerException
at org.drools.base.evaluators.AfterEvaluatorDefinition$AfterEvaluator.getInterval(AfterEvaluatorDefinition.java:272)
at org.drools.rule.constraint.EvaluatorConstraint.getInterval(EvaluatorConstraint.java:100)
at org.drools.reteoo.builder.BuildUtils.gatherTemporalRelationships(BuildUtils.java:326)
at org.drools.reteoo.builder.BuildUtils.calculateTemporalDistance(BuildUtils.java:292)
at org.drools.reteoo.builder.ReteooRuleBuilder.addRule(ReteooRuleBuilder.java:113)
at org.drools.reteoo.ReteooBuilder.addRule(ReteooBuilder.java:116)
at org.drools.reteoo.ReteooRuleBase.addRule(ReteooRuleBase.java:445)
at org.drools.common.AbstractRuleBase.addRule(AbstractRuleBase.java:956)
at org.drools.common.AbstractRuleBase.addPackages(AbstractRuleBase.java:627)
at org.drools.reteoo.ReteooRuleBase.addPackages(ReteooRuleBase.java:472)
at org.drools.impl.KnowledgeBaseImpl.addKnowledgePackages(KnowledgeBaseImpl.java:150)
at org.drools.agent.impl.KnowledgeAgentImpl.addResourcesToKnowledgeBase(KnowledgeAgentImpl.java:1085)
at org.drools.agent.impl.KnowledgeAgentImpl.incrementalBuildResources(KnowledgeAgentImpl.java:971)
at org.drools.agent.impl.KnowledgeAgentImpl.buildKnowledgeBase(KnowledgeAgentImpl.java:675)
at org.drools.agent.impl.KnowledgeAgentImpl.applyChangeSet(KnowledgeAgentImpl.java:203)
at org.drools.agent.impl.KnowledgeAgentImpl.applyChangeSet(KnowledgeAgentImpl.java:182)
at com.abccomp.rules.engine.impl.GuvnorKnowledgeBaseProvider.createKnowledgeBase(GuvnorKnowledgeBaseProvider.java:126)
at com.abccomp.rules.engine.impl.RuleEngineImpl.start(RuleEngineImpl.java:203)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeCustomInitMethod(AbstractAutowireCapableBeanFactory.java:1414)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1375)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1335)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:429)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:728)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:380)
at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255)
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4206)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4705)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:943)
at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:778)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:504)
at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1385)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:306)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1389)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1653)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1662)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1642)
at java.lang.Thread.run(Thread.java:680)
2012-10-17 19:07:59,761 [ContainerBackgroundProcessor[StandardEngine[Catalina]]] ERROR com.abccomp.rules.engine.impl.RuleEngineImpl - Error while starting knolwdge base
java.lang.Exception: Error while creating knowledge base
at com.abccomp.rules.engine.impl.GuvnorKnowledgeBaseProvider.createKnowledgeBase(GuvnorKnowledgeBaseProvider.java:136)
at com.abccomp.rules.engine.impl.RuleEngineImpl.start(RuleEngineImpl.java:203)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeCustomInitMethod(AbstractAutowireCapableBeanFactory.java:1414)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1375)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1335)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:473)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:429)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:728)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:380)
at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255)
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4206)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4705)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:799)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:779)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:601)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:943)
at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:778)
at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:504)
at org.apache.catalina.startup.HostConfig.check(HostConfig.java:1385)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:306)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1389)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1653)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1662)
at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1642)
at java.lang.Thread.run(Thread.java:680)
--
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
11 years, 10 months