[JBoss JIRA] Created: (JBMESSAGING-553) Run AS (4.x and 5.x) integration tests with Messaging
by Ovidiu Feodorov (JIRA)
Run AS (4.x and 5.x) integration tests with Messaging
-----------------------------------------------------
Key: JBMESSAGING-553
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-553
Project: JBoss Messaging
Issue Type: Task
Components: Tests and Performance
Reporter: Ovidiu Feodorov
Assigned To: Richard Achmatowicz
Priority: Critical
Fix For: 1.2.0.Beta1
This is the container task for everthing required to run JBoss AS JMS integration tests with JBoss Messaging. The existing integration test framework should be modified in such a manner to allow interchangeably running the same JMS tests with JBossMQ and JBoss Messaging. None of the existing JBossMQ tests should be removed, they must be at most refactored so the JBossMQ-specific tests will be executed with JBossMQ only (as part of the JBossMQ functional testsuite) and generic JMS tests will be executed with both JBossMQ and JBoss Messaging.
More details in the sub-tasks.
--
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
16 years, 11 months
[JBoss JIRA] Created: (JBAOP-471) Method enforceArgsConsistency() not found on field interception with @Arg-annotated param
by Flavia Rainone (JIRA)
Method enforceArgsConsistency() not found on field interception with @Arg-annotated param
-----------------------------------------------------------------------------------------
Key: JBAOP-471
URL: http://jira.jboss.com/jira/browse/JBAOP-471
Project: JBoss AOP
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.0.0.beta1
Reporter: Flavia Rainone
Assigned To: Flavia Rainone
Fix For: 2.0.0.beta2
The method enforceArgsConsistency() is not generated but is used on field interceptions when there is an @Arg-annotated parameter on an around advice.
The result:
Error generating joinpoint class for joinpoint Field Write[field=public java.util.List org.jboss.test.aop.annotatedAdviceParams.ArgsPOJO.field5]
java.lang.RuntimeException: Error generating joinpoint class for joinpoint Field Write[field=public java.util.List org.jboss.test.aop.annotatedAdviceParams.A
rgsPOJO.field5]
at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:310)
at org.jboss.aop.instrument.JoinPointGenerator.access$100(JoinPointGenerator.java:75)
at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$1$1.run(JoinPointGenerator.java:1618)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.aop.instrument.JoinPointGenerator$GenerateJoinPointClassAction$1.generateJoinPointClass(JoinPointGenerator.java:1614)
at org.jboss.aop.instrument.JoinPointGenerator.generateJoinPointClass(JoinPointGenerator.java:244)
at org.jboss.aop.GeneratedClassAdvisor.generateJoinPointClass(GeneratedClassAdvisor.java:1023)
at org.jboss.test.aop.annotatedAdviceParams.ArgsPOJO$ArgsPOJOAdvisor.ArgsPOJO$ArgsPOJOAdvisor$field5_w_$aop(ArgsPOJO$ArgsPOJOAdvisor.java)
at org.jboss.test.aop.annotatedAdviceParams.ArgsPOJO.field5_w_$aop(ArgsPOJO.java)
at org.jboss.test.aop.annotatedAdviceParams.ArgTestCase.testGenerics3(ArgTestCase.java:480)
Caused by: java.lang.RuntimeException: Error creating invokeNext method: { try{ switch(++super.currentInterceptor){ case 1:enforceArgsConsistency
(); around6.around1(this.arg0);
break; case 2:enforceArgsConsistency(); around7.around2(this.arg0);
break; case 3:enforceArgsConsistency(); around8.around3(this.arg0);
break; case 4:enforceArgsConsistency(); around9.around4(this.arg0);
break; case 5:enforceArgsConsistency(); around10.around6(this.arg0);
break; default: this.dispatch(); } }finally{ --super.currentInterceptor; } return null;}
at org.jboss.aop.instrument.JoinPointGenerator.createInvokeNextMethod(JoinPointGenerator.java:939)
at org.jboss.aop.instrument.JoinPointGenerator.generateJoinpointClass(JoinPointGenerator.java:398)
at org.jboss.aop.instrument.JoinPointGenerator.doGenerateJoinPointClass(JoinPointGenerator.java:276)
... 26 more
Caused by: javassist.CannotCompileException: [source error] enforceArgsConsistency() not found in org.jboss.test.aop.annotatedAdviceParams.JoinPoint_w_field5
_16
at javassist.CtBehavior.setBody(CtBehavior.java:367)
at javassist.CtBehavior.setBody(CtBehavior.java:334)
at org.jboss.aop.instrument.JoinPointGenerator.createInvokeNextMethod(JoinPointGenerator.java:935)
... 28 more
Caused by: compile error: enforceArgsConsistency() not found in org.jboss.test.aop.annotatedAdviceParams.JoinPoint_w_field5_16
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)
--
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
16 years, 11 months
[JBoss JIRA] Created: (JGRP-384) DistributedLockManager.unlock() throws an exception if one of the group members terminates.
by Sean Landis (JIRA)
DistributedLockManager.unlock() throws an exception if one of the group members terminates.
-------------------------------------------------------------------------------------------
Key: JGRP-384
URL: http://jira.jboss.com/jira/browse/JGRP-384
Project: JGroups
Issue Type: Bug
Affects Versions: 2.4
Environment: Suse Linux 10.1 Desktop
java version "1.5.0_07"
Dell Optiplex GX280
Reporter: Sean Landis
Assigned To: Bela Ban
I am trying to use the DLM to implement a failover mechanism. Two
identical processes are started. One acquires the lock and becomes the
primary; the other can't acquire the lock and becomes the backup. The
primary does it's processing. The backup checks periodically if it can
get the lock. Should the primary fail, the backup will acquire the
lock and do the processing.
This works fine. The problem I am having is if both are running, the
backup fails, and the primary tries to unlock. I get the following
stack trace:
Exception in thread "main"
org.jgroups.blocks.LockNotReleasedException: Lock cannot be unlocked.
at org.jgroups.blocks.DistributedLockManager.unlock(DistributedLockManager.java:318)
at org.jgroups.blocks.DistributedLockManager.unlock(DistributedLockManager.java:260)
at com.overstock.distlock.examples.FailoverTest.doIt(FailoverTest.java:50)
at com.overstock.distlock.examples.FailoverTest.main(FailoverTest.java:61)
I am running version 2.4. Here's a sample program:
package distlock.examples;
import org.jgroups.JChannel;
import org.jgroups.blocks.DistributedLockManager;
import org.jgroups.blocks.LockNotGrantedException;
import org.jgroups.blocks.VotingAdapter;
public class FailoverTest {
public static final String SERVER_PROTOCOL_STACK =
"UDP(mcast_addr=228.3.11.76;mcast_port=12345;ip_ttl=1;"
+ "mcast_send_buf_size=150000;mcast_recv_buf_size=80000)"
+ ":PING(timeout=500;num_initial_members=1)"
+ ":FD"
+ ":VERIFY_SUSPECT(timeout=1500)"
+ ":pbcast.NAKACK(gc_lag=50;retransmit_timeout=300,600,1200,2400,4800)"
+ ":UNICAST(timeout=5000)"
+ ":pbcast.STABLE(desired_avg_gossip=200)"
+ ":FRAG(frag_size=4096)"
+ ":pbcast.GMS(join_timeout=5000;join_retry_timeout=1000;"
+ "shun=false;print_local_addr=false)"
;
private void doIt() throws Exception {
JChannel channel = new JChannel(SERVER_PROTOCOL_STACK);
VotingAdapter adapter = new VotingAdapter(channel);
channel.connect("cluster");
DistributedLockManager dlm = new DistributedLockManager(adapter, "Mgr");
String lockId = "theLock";
for (int i = 0; i < 40; i++) {
while (true) {
try {
System.out.println("Trying to get lock.");
dlm.lock(lockId, channel.getLocalAddress(), 10000);
break;
} catch (LockNotGrantedException ex) {
System.out.println("Could not get lock.");
}
try {
Thread.sleep(5000);
} catch(InterruptedException ex) {
}
}
System.out.println("Got lock, sleeping.");
try {
Thread.sleep(10000);
} catch(InterruptedException ex) {
}
System.out.println("unlocking and sleeping.");
dlm.unlock(lockId, channel.getLocalAddress());
try {
Thread.sleep(5000);
} catch(InterruptedException ex) {
}
}
channel.close();
}
public static void main(String[] args) throws Exception {
System.setProperty("java.net.preferIPv4Stack", "true");
new FailoverTest().doIt();
}
}
--
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
16 years, 11 months
[JBoss JIRA] Created: (JBPM-1064) mail nodes cannot resolve variables with hyphenated names
by Ross McDonald (JIRA)
mail nodes cannot resolve variables with hyphenated names
---------------------------------------------------------
Key: JBPM-1064
URL: http://jira.jboss.com/jira/browse/JBPM-1064
Project: JBoss jBPM
Issue Type: Bug
Components: Core Engine
Affects Versions: jBPM jPDL 3.2.1
Environment: mac osx tiger, tomcat 5.0.28, mysql 5.0.37, eclipse 3.3.0, JBoss JBPM JPDL Designer 3.1.0 CR1
Reporter: Ross McDonald
Assigned To: Tom Baeyens
In subject and text fields in mail nodes, at runtime, variables with names like 'my-variable' are not resolved, instead a '0' is displayed. Changing this variable to be 'myVariable' instead resolves it correctly.
I would guess the problem lies maybe in org.jbpm.mail.Mail perhaps around the 'evaluate' method.
Unfortunately I am working close to a deadline at the moment and do not have time to fix this, so I am changing my variable names.
--
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
16 years, 11 months