[JBoss JIRA] (AS7-6972) JBAS014884: No operation named 'composite' exists at address
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6972?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry commented on AS7-6972:
---------------------------------------
Tomaz, no, composite is not a global op.
> JBAS014884: No operation named 'composite' exists at address
> ------------------------------------------------------------
>
> Key: AS7-6972
> URL: https://issues.jboss.org/browse/AS7-6972
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
> Environment: RHEL 6, JDK 1.7
> Reporter: Van Halbert
> Assignee: Tomaz Cerar
>
> I'm using EAP 6.1 ER5, and trying to execute the following using CLI:
>
> /profile=ha/subsystem=security/security-domain=teiid-security:add(cache-type=default)
> /profile=ha/subsystem=security/security-domain=teiid-security/authentication=classic/:add(login-modules=[{"code"=>"org.jboss.security.auth.spi.UsersRolesLoginModule", "flag"=>"required", "module-options"=>[("usersProperties"=>"${jboss.domain.config.dir}/teiid-security-users.properties"), ("rolesProperties"=>"${jboss.domain.config.dir}/teiid-security-roles.properties")]}])
> but I get the message:
> …
> "failure-description" => "JBAS014884: No operation named 'composite' exists at address [
> …
> (see forum for full discussion)
--
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, 8 months
[JBoss JIRA] (DROOLS-107) NPE when inserting through rule (object already present as derived class)
by Davide Sottara (JIRA)
[ https://issues.jboss.org/browse/DROOLS-107?page=com.atlassian.jira.plugin... ]
Davide Sottara commented on DROOLS-107:
---------------------------------------
Could you please try master (5.5.1-SNAPSHOT) ?
I tried to reproduce it but I didn't get any exception.
To be fair, I had to simplify Triple due to some
missing dependencies, so I may have removed the bug
as well :)
> NPE when inserting through rule (object already present as derived class)
> -------------------------------------------------------------------------
>
> Key: DROOLS-107
> URL: https://issues.jboss.org/browse/DROOLS-107
> Project: Drools
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 5.5.0.Final
> Environment: % java -version
> java version "1.7.0_21"
> Java(TM) SE Runtime Environment (build 1.7.0_21-b11)
> Java HotSpot(TM) 64-Bit Server VM (build 23.21-b01, mixed mode)
> % uname -a
> Linux oem-laptop 3.5.0-28-generic #47-Ubuntu SMP Tue Apr 9 19:03:54 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
> Reporter: Jean-Marc Vanel
> Assignee: Mark Proctor
>
> NPE : unit test which depends only on 3 non Drools simple classes : Assignment, Triple, TripleUser
> unit test has 2 rules , 5 inserts, 3 fireAllRules : the last one makes the NPE.
> TestDroolsNPE.testRunRulesBefore
> testRunRulesBefore(eulergui.project.TestDroolsNPE)
> Exception executing consequence for rule "project-java-rules2.n3 0" in project_java_rules2_n3_1: java.lang.NullPointerException
> at org.drools.runtime.rule.impl.DefaultConsequenceExceptionHandler.handleException(DefaultConsequenceExceptionHandler.java:39)
> at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:1297)
> at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1221)
> at org.drools.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1456)
> at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:710)
> at org.drools.common.AbstractWorkingMemory.fireAllRules(AbstractWorkingMemory.java:674)
> at org.drools.impl.StatefulKnowledgeSessionImpl.fireAllRules(StatefulKnowledgeSessionImpl.java:230)
> at eulergui.project.TestDroolsNPE.testRunRulesBefore(TestDroolsNPE.java:110)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
> Caused by: java.lang.NullPointerException
> at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:196)
> at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:903)
> at org.drools.base.DefaultKnowledgeHelper.insertLogical(DefaultKnowledgeHelper.java:245)
> at org.drools.base.DefaultKnowledgeHelper.insertLogical(DefaultKnowledgeHelper.java:210)
> at org.drools.base.DefaultKnowledgeHelper.insertLogical(DefaultKnowledgeHelper.java:205)
> at project_java_rules2_n3_1.Rule_project_java_rules2_n3_0_dd5596b676034b1fb5b32877015997e3.defaultConsequence(Rule_project_java_rules2_n3_0_dd5596b676034b1fb5b32877015997e3.java:12)
> at project_java_rules2_n3_1.Rule_project_java_rules2_n3_0_dd5596b676034b1fb5b32877015997e3DefaultConsequenceInvokerGenerated.evaluate(Unknown Source)
> at project_java_rules2_n3_1.Rule_project_java_rules2_n3_0_dd5596b676034b1fb5b32877015997e3DefaultConsequenceInvoker.evaluate(Unknown Source)
> at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:1287)
> ... 25 more
> in class NamedEntryPoint :
>
> protected FactHandle insert(final Object object,
> final Object tmsValue,
> final boolean dynamic,
> boolean logical,
> final Rule rule,
> final Activation activation) throws FactException {
> if ( object == null ) {
> // you cannot assert a null object
> return null;
> }
>
> try {
> this.wm.startOperation();
>
> ObjectTypeConf typeConf = this.typeConfReg.getObjectTypeConf( this.entryPoint,
> object );
> if ( logical && !typeConf.isTMSEnabled()) {
> enableTMS(object, typeConf);
> }
>
> InternalFactHandle handle = null;
>
> if ( this.wm.isSequential() ) {
> handle = createHandle( object,
> typeConf );
> insert( handle,
> object,
> rule,
> activation,
> typeConf );
> return handle;
> }
> try {
> this.lock.lock();
> this.ruleBase.readLock();
> // check if the object already exists in the WM
> handle = this.objectStore.getHandleForObject( object );
>
> if ( typeConf.isTMSEnabled() ) {
>
> EqualityKey key;
>
> TruthMaintenanceSystem tms = wm.getTruthMaintenanceSystem();
> if ( handle == null ) {
> // lets see if the object is already logical asserted
> key = tms.get( object );
> } else {
> // Object is already asserted, so check and possibly correct its
> // status and then return the handle
> key = handle.getEqualityKey();
>
> if ( key.getStatus() == EqualityKey.STATED ) {
>
> // key == null here !!!!!!!!!!!!!!!!!!!
> // conf.setAssertBehaviour( AssertBehaviour.EQUALITY );
>
> when rule inserts Triple :
> <file:/home/jmv/src/eulergui-code/eulergui/test/import.n3p.n3> <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.w3.org/2002/07/owl#Ontology> .
>
> that is already present, as a TripleUser extends Triple, but equals() and hashCode() are the same ;
> this object is both asserted and inferred as a Triple object
--
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, 8 months
[JBoss JIRA] (AS7-6972) JBAS014884: No operation named 'composite' exists at address
by Brian Stansberry (JIRA)
[ https://issues.jboss.org/browse/AS7-6972?page=com.atlassian.jira.plugin.s... ]
Brian Stansberry updated AS7-6972:
----------------------------------
Assignee: Tomaz Cerar (was: Brian Stansberry)
> JBAS014884: No operation named 'composite' exists at address
> ------------------------------------------------------------
>
> Key: AS7-6972
> URL: https://issues.jboss.org/browse/AS7-6972
> Project: Application Server 7
> Issue Type: Bug
> Components: Domain Management
> Affects Versions: EAP 6.1.0.Alpha (7.2.0.Final)
> Environment: RHEL 6, JDK 1.7
> Reporter: Van Halbert
> Assignee: Tomaz Cerar
>
> I'm using EAP 6.1 ER5, and trying to execute the following using CLI:
>
> /profile=ha/subsystem=security/security-domain=teiid-security:add(cache-type=default)
> /profile=ha/subsystem=security/security-domain=teiid-security/authentication=classic/:add(login-modules=[{"code"=>"org.jboss.security.auth.spi.UsersRolesLoginModule", "flag"=>"required", "module-options"=>[("usersProperties"=>"${jboss.domain.config.dir}/teiid-security-users.properties"), ("rolesProperties"=>"${jboss.domain.config.dir}/teiid-security-roles.properties")]}])
> but I get the message:
> …
> "failure-description" => "JBAS014884: No operation named 'composite' exists at address [
> …
> (see forum for full discussion)
--
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, 8 months
[JBoss JIRA] (AS7-4464) EJB3 deployment metrics missing
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-4464?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-4464:
----------------------------------------------
Carlo de Wolf <cdewolf(a)redhat.com> made a comment on [bug 911117|https://bugzilla.redhat.com/show_bug.cgi?id=911117]
We are still missing the cache statistics. These were never ported over from the deprecated StatefulCache interface.
As for the other ones, they don't make sense.
The statistics are meant to be used in a round-robin database. Where the RRD dictates the interval. So for EAP the interval should be an external variable.
In EAP 5 you could reset the statistics, but the time-series between last query and reset would be lost. Essentially it is a very crude hammer to notify EAP of the interval.
This also makes it an unstable piece of EJB3 code.
I choose to ditch that, which makes min, max and average non-existent. There is no interval known to EAP. This makes for stable data point queries.
Ultimately I still want to be able to have a performance ui as I drafted ~4 years ago, wherein the pressure on each EJB is properly visualized.
I'm not sure whether it needs a re-introduction of the interval notion.
It would need some additional means to provide data points to the histogram though.
> EJB3 deployment metrics missing
> -------------------------------
>
> Key: AS7-4464
> URL: https://issues.jboss.org/browse/AS7-4464
> Project: Application Server 7
> Issue Type: Bug
> Components: EJB
> Affects Versions: 7.1.1.Final
> Reporter: Stefan Negrea
> Assignee: Carlo de Wolf
> Priority: Critical
> Labels: rhq
> Fix For: 8.0.0.Alpha1
>
>
> The following metrics are missing from AS7 EJB3 subsystem from deployment when compared to AS5 exposed metrics:
> Stateless Session Bean
> Method Invocation Time - The minimum, maximum, and average invocation times for each of the methods exposed by this EJB
> Stateful Session Bean
> Method Invocation Time - The minimum, maximum, and average invocation times for each of the methods exposed by this EJB
> Cache Size - Cache Size
> Passivated Count - Passivated Count
> Total Size - Total Size
--
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, 8 months
[JBoss JIRA] (AS7-4464) EJB3 deployment metrics missing
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-4464?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-4464:
----------------------------------------------
Carlo de Wolf <cdewolf(a)redhat.com> made a comment on [bug 911117|https://bugzilla.redhat.com/show_bug.cgi?id=911117]
> EJB3 deployment metrics missing
> -------------------------------
>
> Key: AS7-4464
> URL: https://issues.jboss.org/browse/AS7-4464
> Project: Application Server 7
> Issue Type: Bug
> Components: EJB
> Affects Versions: 7.1.1.Final
> Reporter: Stefan Negrea
> Assignee: Carlo de Wolf
> Priority: Critical
> Labels: rhq
> Fix For: 8.0.0.Alpha1
>
>
> The following metrics are missing from AS7 EJB3 subsystem from deployment when compared to AS5 exposed metrics:
> Stateless Session Bean
> Method Invocation Time - The minimum, maximum, and average invocation times for each of the methods exposed by this EJB
> Stateful Session Bean
> Method Invocation Time - The minimum, maximum, and average invocation times for each of the methods exposed by this EJB
> Cache Size - Cache Size
> Passivated Count - Passivated Count
> Total Size - Total Size
--
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, 8 months
[JBoss JIRA] (AS7-4932) CLONE - Using session passivation results in WeldListener: java.lang.NullPointerException on normal operation
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/AS7-4932?page=com.atlassian.jira.plugin.s... ]
RH Bugzilla Integration commented on AS7-4932:
----------------------------------------------
Paul Ferraro <paul.ferraro(a)redhat.com> made a comment on [bug 900549|https://bugzilla.redhat.com/show_bug.cgi?id=900549]
Status: Still under investigation. I suspect this is to blame for BZ 901164.
> CLONE - Using session passivation results in WeldListener: java.lang.NullPointerException on normal operation
> -------------------------------------------------------------------------------------------------------------
>
> Key: AS7-4932
> URL: https://issues.jboss.org/browse/AS7-4932
> Project: Application Server 7
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 7.1.2.Final (EAP)
> Reporter: Radoslav Husar
> Assignee: Paul Ferraro
> Priority: Blocker
> Labels: as713tracking
> Fix For: 7.1.3.Final (EAP)
>
>
> NPE is thrown in roughly 0.36% of HTTP session request processing in the test.
> This results in response code 503 returned to the client with the exception.
> The test is using passivation-enabled WAR of clusterbench
> https://github.com/rhusar/clusterbench
> Here is a shorter soak test run that uncovered the issue
> https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Clustering-Soak/jo...
> {noformat}
> [JBossINF] 19:52:10,113 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host]] (ajp-perf20/10.16.90.58:8009-2570) Exception sending request initialized lifecycle event to listener instance of class org.jboss.weld.servlet.WeldListener: java.lang.NullPointerException
> [JBossINF] at org.jboss.as.web.session.ClusteredSession.update(ClusteredSession.java:972) [jboss-as-web-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> [JBossINF] at org.jboss.as.web.session.DistributableSessionManager.loadSession(DistributableSessionManager.java:1377) [jboss-as-web-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> [JBossINF] at org.jboss.as.web.session.DistributableSessionManager.findSession(DistributableSessionManager.java:673) [jboss-as-web-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> [JBossINF] at org.jboss.as.web.session.DistributableSessionManager.findSession(DistributableSessionManager.java:84) [jboss-as-web-7.1.2.Final-redhat-1.jar:7.1.2.Final-redhat-1]
> [JBossINF] at org.apache.catalina.connector.Request.doGetSession(Request.java:2618) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at org.apache.catalina.connector.Request.getSession(Request.java:2375) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at org.apache.catalina.connector.RequestFacade.getSession(RequestFacade.java:841) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at org.jboss.weld.context.beanstore.http.LazySessionBeanStore.getSession(LazySessionBeanStore.java:72) [weld-core-1.1.8.Final-redhat-1.jar:1.1.8.Final-redhat-1]
> [JBossINF] at org.jboss.weld.context.beanstore.http.LazySessionBeanStore.<init>(LazySessionBeanStore.java:58) [weld-core-1.1.8.Final-redhat-1.jar:1.1.8.Final-redhat-1]
> [JBossINF] at org.jboss.weld.context.http.HttpSessionContextImpl.associate(HttpSessionContextImpl.java:31) [weld-core-1.1.8.Final-redhat-1.jar:1.1.8.Final-redhat-1]
> [JBossINF] at org.jboss.weld.context.http.HttpSessionContextImpl.associate(HttpSessionContextImpl.java:16) [weld-core-1.1.8.Final-redhat-1.jar:1.1.8.Final-redhat-1]
> [JBossINF] at org.jboss.weld.servlet.WeldListener.requestInitialized(WeldListener.java:134) [weld-core-1.1.8.Final-redhat-1.jar:1.1.8.Final-redhat-1]
> [JBossINF] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:143) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:368) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:505) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at org.apache.coyote.ajp.AjpProtocol$AjpConnectionHandler.process(AjpProtocol.java:452) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:931) [jbossweb-7.0.16.Final-redhat-1.jar:]
> [JBossINF] at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]
> {noformat}
--
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, 8 months
[JBoss JIRA] (AS7-6975) Allow Dependencies: header to be empty, don't throw exception or fail deployment startup
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/AS7-6975?page=com.atlassian.jira.plugin.s... ]
David Lloyd moved MODULES-164 to AS7-6975:
------------------------------------------
Project: Application Server 7 (was: JBoss Modules)
Key: AS7-6975 (was: MODULES-164)
Workflow: GIT Pull Request workflow (was: jira)
Affects Version/s: (was: 1.2.0.CR1)
Component/s: Class Loading
(was: core)
> Allow Dependencies: header to be empty, don't throw exception or fail deployment startup
> ----------------------------------------------------------------------------------------
>
> Key: AS7-6975
> URL: https://issues.jboss.org/browse/AS7-6975
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Class Loading
> Environment: EAP6.1
> Reporter: Darryl Miles
> Assignee: David Lloyd
>
> Exception throw for empty "Dependencies:" header in MANIFEST.MF.
> This is a perfectly well-formed header and should have the same meaning as if the header does not exist.
> By all means emit a warning explaining which JAR the MANIFEST.MF is in, the header name and that the value is an empty string and this is not allow (due to some spec/rule you cite).
> But don't fail a deployment from starting.
> Sometimes headers are not going to be perfect from dependent JARs you have little control over. You don't want to make the user do extra work of repacking/fixing those JAR just to get them to deploy on JBoss AS.
> If the empty header has a special meaning then I suggest you use a keyword token instead. Like you do for "export", "services" and "optional".
--
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, 8 months
[JBoss JIRA] (AS7-6975) Allow Dependencies: header to be empty, don't throw exception or fail deployment startup
by David Lloyd (JIRA)
[ https://issues.jboss.org/browse/AS7-6975?page=com.atlassian.jira.plugin.s... ]
David Lloyd updated AS7-6975:
-----------------------------
Assignee: (was: David Lloyd)
> Allow Dependencies: header to be empty, don't throw exception or fail deployment startup
> ----------------------------------------------------------------------------------------
>
> Key: AS7-6975
> URL: https://issues.jboss.org/browse/AS7-6975
> Project: Application Server 7
> Issue Type: Feature Request
> Components: Class Loading
> Environment: EAP6.1
> Reporter: Darryl Miles
>
> Exception throw for empty "Dependencies:" header in MANIFEST.MF.
> This is a perfectly well-formed header and should have the same meaning as if the header does not exist.
> By all means emit a warning explaining which JAR the MANIFEST.MF is in, the header name and that the value is an empty string and this is not allow (due to some spec/rule you cite).
> But don't fail a deployment from starting.
> Sometimes headers are not going to be perfect from dependent JARs you have little control over. You don't want to make the user do extra work of repacking/fixing those JAR just to get them to deploy on JBoss AS.
> If the empty header has a special meaning then I suggest you use a keyword token instead. Like you do for "export", "services" and "optional".
--
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, 8 months