[JBoss JIRA] Created: (JGRP-429) Optionally disable message bundling for unicast messages
by Bela Ban (JIRA)
Optionally disable message bundling for unicast messages
--------------------------------------------------------
Key: JGRP-429
URL: http://jira.jboss.com/jira/browse/JGRP-429
Project: JGroups
Issue Type: Task
Affects Versions: 2.5
Reporter: Bela Ban
Assigned To: Bela Ban
Fix For: 2.6
Unicast messages are often used for responses (e.g. Rpc/MessageDispatcher). While requests arrive as multicast messages, responses are sent back as unicast messages. When sending many requests, bundling may be preferred because we never have to wait for the bundle to fill up: as we're sending many messages, bundles fill up quickly. However, for responses, that may not be the case, so we may want to disable bundling for unicasts. This should be configurable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years
[JBoss JIRA] Created: (JBAOP-444) initialisePerInstanceAspects not found (CannotCompileException)
by Flavia Rainone (JIRA)
initialisePerInstanceAspects not found (CannotCompileException)
---------------------------------------------------------------
Key: JBAOP-444
URL: http://jira.jboss.com/jira/browse/JBAOP-444
Project: JBoss AOP
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.0.0.alpha5
Reporter: Flavia Rainone
Assigned To: Flavia Rainone
Priority: Critical
Fix For: 2.0.0.beta
Attachments: tests.txt
On method by constructor call scenarios (written as part of task JBAOP-327), the following error is occurring:
compile error: initialisePerInstanceAspects(org.jboss.test.aop.beforeafterthrowingscoped.SuperTargetPOJO) not found in org.jboss.test.aop.beforeaf
terthrowingscoped.JoinPoint_MByC__1org_jboss_test_aop_beforeafterthrowingscoped_SuperTargetPOJO_1919852402921562826_12
at javassist.compiler.TypeChecker.atMethodCallCore(TypeChecker.java:716)
at javassist.compiler.TypeChecker.atCallExpr(TypeChecker.java:681)
at javassist.compiler.JvstTypeChecker.atCallExpr(JvstTypeChecker.java:156)
at javassist.compiler.ast.CallExpr.accept(CallExpr.java:45)
at javassist.compiler.CodeGen.doTypeCheck(CodeGen.java:241)
at javassist.compiler.CodeGen.atStmnt(CodeGen.java:329)
at javassist.compiler.ast.Stmnt.accept(Stmnt.java:49)
at javassist.compiler.CodeGen.atStmnt(CodeGen.java:350)
at javassist.compiler.ast.Stmnt.accept(Stmnt.java:49)
at javassist.compiler.CodeGen.atIfStmnt(CodeGen.java:390)
at javassist.compiler.CodeGen.atStmnt(CodeGen.java:354)
at javassist.compiler.ast.Stmnt.accept(Stmnt.java:49)
at javassist.compiler.CodeGen.atStmnt(CodeGen.java:350)
at javassist.compiler.ast.Stmnt.accept(Stmnt.java:49)
at javassist.compiler.CodeGen.atIfStmnt(CodeGen.java:390)
at javassist.compiler.CodeGen.atStmnt(CodeGen.java:354)
at javassist.compiler.ast.Stmnt.accept(Stmnt.java:49)
at javassist.compiler.CodeGen.atStmnt(CodeGen.java:350)
at javassist.compiler.ast.Stmnt.accept(Stmnt.java:49)
at javassist.compiler.CodeGen.atMethodBody(CodeGen.java:291)
at javassist.compiler.Javac.compileBody(Javac.java:222)
at javassist.CtBehavior.setBody(CtBehavior.java:360)
... 34 more
Complete stack is attached.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
19 years