[JBoss JIRA] (JBAS-9524) NullPointerException from org.jboss.aop.InstanceAdvisorDelegate on start up
by Rick Qui (JIRA)
Rick Qui created JBAS-9524:
------------------------------
Summary: NullPointerException from org.jboss.aop.InstanceAdvisorDelegate on start up
Key: JBAS-9524
URL: https://issues.jboss.org/browse/JBAS-9524
Project: Application Server 3 4 5 and 6
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: AOP
Affects Versions: JBossAS-5.1.0.GA
Environment: JBossAS-5.1.0 GA, Java 6, Linux
Reporter: Rick Qui
Assignee: Kabir Khan
Priority: Minor
Fix For: JBossAS-5.1.0.GA
Occasional NullPointerException on startup
server.log
----------------------------------------
2012-07-27 10:34:27,596 134762 INFO [org.granite.messaging.webapp.AMFMessageFilter] (main:) Using configuration: {closeStreams=true, inputBufferSize=null, outputBufferSize=null}
2012-07-27 10:34:27,657 134823 ERROR [org.jboss.aspects.tx.TxPolicy] (WorkManager(2)-10:) javax.ejb.EJBTransactionRolledbackException
2012-07-27 10:34:27,672 134838 ERROR [org.jboss.resource.adapter.jms.inflow.JmsServerSession] (WorkManager(2)-10:) Unexpected error delivering message delegator->JBossMessage[22009965240795136]:PERSISTENT, deliveryId=0
javax.ejb.EJBTransactionRolledbackException
at org.jboss.ejb3.tx.Ejb3TxPolicy.handleInCallerTx(Ejb3TxPolicy.java:115)
at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:130)
at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:194)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:80)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.mdb.MessagingContainer.localInvoke(MessagingContainer.java:282)
at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.delivery(MessageInflowLocalProxy.java:270)
at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:140)
at $Proxy770.onMessage(Unknown Source)
at org.jboss.resource.adapter.jms.inflow.JmsServerSession.onMessage(JmsServerSession.java:178)
at org.jboss.jms.client.container.ClientConsumer.callOnMessageStatic(ClientConsumer.java:160)
at org.jboss.jms.client.container.SessionAspect.handleRun(SessionAspect.java:831)
at org.jboss.aop.advice.org.jboss.jms.client.container.SessionAspect_z_handleRun_1566129382.invoke(SessionAspect_z_handleRun_1566129382.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:86)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.jms.client.delegate.ClientSessionDelegate.run(ClientSessionDelegate.java)
at org.jboss.jms.client.JBossSession.run(JBossSession.java:199)
at org.jboss.resource.adapter.jms.inflow.JmsServerSession.run(JmsServerSession.java:234)
at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205)
at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.NullPointerException
at org.jboss.aop.InstanceAdvisorDelegate.getJoinpointAspect(InstanceAdvisorDelegate.java:263)
at org.jboss.aop.InstanceAdvisorDelegate.getPerInstanceJoinpointAspect(InstanceAdvisorDelegate.java:215)
at org.jboss.ejb3.interceptors.container.ManagedObjectAdvisor.getPerInstanceJoinpointAspect(ManagedObjectAdvisor.java:288)
at org.jboss.aop.advice.PerJoinpointAdvice.invoke(PerJoinpointAdvice.java:158)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.fillMethod(InvocationContextInterceptor.java:72)
at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_fillMethod_1566129382.invoke(InvocationContextInterceptor_z_fillMethod_1566129382.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor.setup(InvocationContextInterceptor.java:88)
at org.jboss.aop.advice.org.jboss.ejb3.interceptors.aop.InvocationContextInterceptor_z_setup_1566129382.invoke(InvocationContextInterceptor_z_setup_1566129382.java)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.connectionmanager.CachedConnectionInterceptor.invoke(CachedConnectionInterceptor.java:62)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.entity.TransactionScopedEntityManagerInterceptor.invoke(TransactionScopedEntityManagerInterceptor.java:56)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.AllowedOperationsInterceptor.invoke(AllowedOperationsInterceptor.java:47)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.tx.NullInterceptor.invoke(NullInterceptor.java:42)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.ejb3.stateless.StatelessInstanceInterceptor.invoke(StatelessInstanceInterceptor.java:68)
at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
at org.jboss.aspects.tx.TxPolicy.invokeInCallerTx(TxPolicy.java:126)
... 30 more
--
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-5922) Grouping-handler's type attribute does not support expressions
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/AS7-5922?page=com.atlassian.jira.plugin.s... ]
Jeff Mesnil updated AS7-5922:
-----------------------------
Summary: Grouping-handler's type attribute does not support expressions (was: Group-id element does not support expressions)
> Grouping-handler's type attribute does not support expressions
> --------------------------------------------------------------
>
> Key: AS7-5922
> URL: https://issues.jboss.org/browse/AS7-5922
> Project: Application Server 7
> Issue Type: Bug
> Components: JMS
> Affects Versions: 7.1.3.Final (EAP)
> Environment: JBoss EAP 6.x
> Reporter: Tom Ross
> Assignee: Jeff Mesnil
>
> When creating messaging grouping in cluster mode it is necessary to provide <type> for <group-id> for each node. In a cluster there could only one node with group-id <type>LOCAL</type> and remaining nodes have to be of type REMOTE. In JBoss EAP 6 in domain cluster there is only one profile for each node so it is necessary to be able to specify type as an expression i.e <type>${type.name}</type>
--
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-5922) Grouping-handler's type attribute does not support expressions
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/AS7-5922?page=com.atlassian.jira.plugin.s... ]
Jeff Mesnil updated AS7-5922:
-----------------------------
Affects Version/s: 7.1.3.Final (EAP)
> Grouping-handler's type attribute does not support expressions
> --------------------------------------------------------------
>
> Key: AS7-5922
> URL: https://issues.jboss.org/browse/AS7-5922
> Project: Application Server 7
> Issue Type: Bug
> Components: JMS
> Affects Versions: 7.1.3.Final (EAP)
> Environment: JBoss EAP 6.x
> Reporter: Tom Ross
> Assignee: Jeff Mesnil
>
> When creating messaging grouping in cluster mode it is necessary to provide <type> for <group-id> for each node. In a cluster there could only one node with group-id <type>LOCAL</type> and remaining nodes have to be of type REMOTE. In JBoss EAP 6 in domain cluster there is only one profile for each node so it is necessary to be able to specify type as an expression i.e <type>${type.name}</type>
--
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-5922) Group-id element does not support expressions
by Jeff Mesnil (JIRA)
[ https://issues.jboss.org/browse/AS7-5922?page=com.atlassian.jira.plugin.s... ]
Jeff Mesnil moved HORNETQ-1086 to AS7-5922:
-------------------------------------------
Project: Application Server 7 (was: HornetQ)
Key: AS7-5922 (was: HORNETQ-1086)
Workflow: GIT Pull Request workflow (was: jira)
Component/s: JMS
(was: Core)
> Group-id element does not support expressions
> ---------------------------------------------
>
> Key: AS7-5922
> URL: https://issues.jboss.org/browse/AS7-5922
> Project: Application Server 7
> Issue Type: Bug
> Components: JMS
> Environment: JBoss EAP 6.x
> Reporter: Tom Ross
> Assignee: Jeff Mesnil
>
> When creating messaging grouping in cluster mode it is necessary to provide <type> for <group-id> for each node. In a cluster there could only one node with group-id <type>LOCAL</type> and remaining nodes have to be of type REMOTE. In JBoss EAP 6 in domain cluster there is only one profile for each node so it is necessary to be able to specify type as an expression i.e <type>${type.name}</type>
--
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-5920) OSGi provisioning service
by Thomas Diesler (JIRA)
Thomas Diesler created AS7-5920:
-----------------------------------
Summary: OSGi provisioning service
Key: AS7-5920
URL: https://issues.jboss.org/browse/AS7-5920
Project: Application Server 7
Issue Type: Feature Request
Components: OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.CR1
It should be possible to provision the server with a set of capabilities similar to Eclipse plugin installation. For this we need to prime the Repository with the caps/reqs associated with the resources that are already available in the Runtime. The resolver needs to do impact analysis based on a snapshot of caps in the environment. Finally, the resources coming from the repository can be deployed. This functionality could be the foundation to do this at build time such that even subsystems can be layered on a basic Core Runtime.
--
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-5919) Optimize OSGi subsystem bootstrap
by Thomas Diesler (JIRA)
Thomas Diesler created AS7-5919:
-----------------------------------
Summary: Optimize OSGi subsystem bootstrap
Key: AS7-5919
URL: https://issues.jboss.org/browse/AS7-5919
Project: Application Server 7
Issue Type: Feature Request
Components: OSGi
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: 7.2.0.CR1
The OSGi subsystem in AS7 is alrady activated lazily. However, in many cases users only want to deploy a simple artefact that "happens to be" an OSGi bundle (i.e. a JDBC driver) and do not want to deploy a large set of interconnected bundles that make up a complex modular enterprise application. For those cases the OSGi subsystem should bootstrap in a jiffy and we should not see a performance impact that is worth talking about.
--
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] (JBRULES-3529) JMS messanger for JBOSS AS 7.1
by Cyril Sochor (JIRA)
Cyril Sochor created JBRULES-3529:
-------------------------------------
Summary: JMS messanger for JBOSS AS 7.1
Key: JBRULES-3529
URL: https://issues.jboss.org/browse/JBRULES-3529
Project: Drools
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: drools-core (fusion)
Affects Versions: 5.3.1.Final
Environment: jboss-as-7.1.1.Final, java 1.6.9_29 64
Reporter: Cyril Sochor
Assignee: Mark Proctor
Fix For: 5.3.2.Final
JBOSS AS 7.1 is not supported by pipeline JmsMessanger. Connection factory JNDI name is string constant "ConnectionFactory" and is not customizable! JBOSS AS 7.1 has new remote interface and JNDI name "RemoteConnectionFactory" is required. Connection with principal and credentials is also required.
--
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, 8 months
[JBoss JIRA] (JBRULES-3240) Unable to build expression for 'inline-eval' when using Lists of objects
by Richard Ambridge (Created) (JIRA)
Unable to build expression for 'inline-eval' when using Lists of objects
------------------------------------------------------------------------
Key: JBRULES-3240
URL: https://issues.jboss.org/browse/JBRULES-3240
Project: Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-compiler
Affects Versions: 5.3.0.CR1
Environment: Ubuntu, JDK 1.6.0.26
Reporter: Richard Ambridge
Assignee: Mark Proctor
If a Rule has a .size== in when and the variable is an Object, then we get the following:-
Unable to build expression for 'inline-eval' : [Error: incompatible types in statement: class java.lang.Integer (compared from: class droolstesting.SubType)]
Full example:
Rule:
package droolstesting
rule "rule2"
dialect "mvel"
when
$m : MyItem(items!=null || items.size == 0)
then
System.out.println("Got 0");
retract($m)
end
MyItems.java:
package droolstesting;
import java.util.ArrayList;
import java.util.List;
public class MyItem {
int number=0;
String string="empty";
List<SubType> items=new ArrayList<SubType>();
public List<SubType> getItems() {
return items;
}
public void setItems(List<SubType> items) {
this.items = items;
}
public int getNumber() {
return number;
}
public void setNumber(int number) {
this.number = number;
}
public String getString() {
return string;
}
public void setString(String string) {
this.string = string;
}
}
SubType.java:
package droolstesting;
public class SubType {
String name="";
}
Main.java:
package droolstesting;
import java.io.File;
import java.io.IOException;
import org.drools.compiler.DroolsParserException;
import org.drools.compiler.PackageBuilder;
import org.drools.io.ResourceFactory;
/**
*
* @author richarda
*/
public class Main {
/**
* @param args the command line arguments
*/
public static void main(String[] args) throws IOException, DroolsParserException {
PackageBuilder pkgBuilder = new PackageBuilder();
pkgBuilder.addPackageFromDrl(ResourceFactory.newClassPathResource("rule1.drl"));
if (pkgBuilder.hasErrors()) {
System.err.println(pkgBuilder.getErrors().toString());
throw new RuntimeException("Unable to compile rules");
}
pkgBuilder.addPackageFromDrl(ResourceFactory.newClassPathResource("rule2.drl"));
if (pkgBuilder.hasErrors()) {
System.err.println(pkgBuilder.getErrors().toString());
throw new RuntimeException("Unable to compile rules");
}
}
}
Result:
run:
Unable to build expression for 'inline-eval' : [Error: incompatible types in statement: class java.lang.Integer (compared from: class droolstesting.SubType)]
[Near : {... items != null || items.size == 0 ....}]
^
[Line: 6, Column: 14]'items != null || items.size == 0'
[Error: incompatible types in statement: class java.lang.Integer (compared from: class droolstesting.SubType)]
[Near : {... items != null || items.size == 0 ....}]
^
[Line: 6, Column: 14] : [Rule name='rule2']
[Error: incompatible types in statement: class java.lang.Integer (compared from: class droolstesting.SubType)]
[Near : {... items != null || items.size == 0 ....}]
^
[Line: 1, Column: 18]
Exception in thread "main" java.lang.RuntimeException: Unable to compile rules
at droolstesting.Main.main(Main.java:32)
Java Result: 1
BUILD SUCCESSFUL (total time: 1 second)
--
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, 8 months