June 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-634) If Server is restarted, client leases IDs might be out of sync

by Clebert Suconic (JIRA)

If Server is restarted, client leases IDs might be out of sync -------------------------------------------------------------- Key: JBMESSAGING-634 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-634 Project: JBoss Messaging Issue Type: Bug Reporter: Clebert Suconic Assigned To: Ovidiu Feodorov This is the scenario I have: I start the server... I have clients opening/closing connections in a loop... I kill the server... (will ignore the errors on client until I get restarted) I restart the server.... I will get a bunch of errors on client, regarding not being able to find ClientIds on Lease operations (Just WARNs) Kill the client... after some time.. .the server gets into an unexpected state, after we have seen this exception: 20:59:37,765 ERROR [STDERR] java.lang.NullPointerException 20:59:37,765 ERROR [STDERR] at org.jboss.remoting.Lease.notifyClientLost(Lease.java:211) 20:59:37,765 ERROR [STDERR] at org.jboss.remoting.Lease.access$300(Lease.java:39) 20:59:37,765 ERROR [STDERR] at org.jboss.remoting.Lease$LeaseTimerTask.run(Lease.java:242) 20:59:37,765 ERROR [STDERR] at java.util.TimerThread.mainLoop(Timer.java:512) 20:59:37,765 ERROR [STDERR] at java.util.TimerThread.run(Timer.java:462) I consider the description of this JIRA issue very subjective, we should rename it as soon as we have found the real cause. -- 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

18 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-923) Creating queue/topic with JNDI subcontexts fails, e.g. names such as queue/foo/bar

by Elias Ross (JIRA)

Creating queue/topic with JNDI subcontexts fails, e.g. names such as queue/foo/bar ---------------------------------------------------------------------------------- Key: JBMESSAGING-923 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-923 Project: JBoss Messaging Issue Type: Bug Reporter: Elias Ross Assigned To: Ovidiu Feodorov The following service.xml will generate an exception: <server> <loader-repository> jboss.messaging:loader=ScopedLoaderRepository <loader-repository-config> java2ParentDelegation=false </loader-repository-config> </loader-repository> <mbean code="org.jboss.jms.server.destination.QueueService" name="jboss.messaging.destination:service=Queue,name=ppm/mt" xmbean-dd="xmdesc/Queue-xmbean.xml"> <depends optional-attribute-name="ServerPeer">jboss.messaging:service=Se rverPeer</depends> <depends>jboss.messaging:service=PostOffice</depends> </mbean> </server> 15:46:12,205 ERROR [ExceptionUtil] Queue[/queue/ppm/bridge/mqube, name=ppm/bridg e/mqube] startService javax.naming.NameNotFoundException: ppm not bound at org.jnp.server.NamingServer.getBinding(NamingServer.java:529) at org.jnp.server.NamingServer.getBinding(NamingServer.java:537) at org.jnp.server.NamingServer.getObject(NamingServer.java:543) at org.jnp.server.NamingServer.rebind(NamingServer.java:165) at org.jnp.server.NamingServer.rebind(NamingServer.java:168) at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:510) at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:477) at org.jboss.jms.server.DestinationJNDIMapper.registerDestination(Destin ationJNDIMapper.java:146) at org.jboss.jms.server.destination.QueueService.startService(QueueServi ce.java:142) -- 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

18 years, 9 months

3
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-899) WebServiceRef injection from DD doesn't work

by Carlo de Wolf (JIRA)

WebServiceRef injection from DD doesn't work -------------------------------------------- Key: EJBTHREE-899 URL: http://jira.jboss.com/jira/browse/EJBTHREE-899 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC10 - FD Reporter: Carlo de Wolf -- 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

18 years, 9 months

3
9
0 / 0

[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

18 years, 9 months

5
14
0 / 0

[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

18 years, 9 months

3
9
0 / 0

[JBoss JIRA] Created: (JASSIST-29) StackMapTable support

by Shigeru Chiba (JIRA)

StackMapTable support --------------------- Key: JASSIST-29 URL: http://jira.jboss.com/jira/browse/JASSIST-29 Project: Javassist Issue Type: Feature Request Reporter: Shigeru Chiba Assigned To: Shigeru Chiba Priority: Blocker All class files must support StackMapTable in Java SE 6. -- 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

18 years, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-910) upgrade GWT to 1.4

by Michael Neale (JIRA)

upgrade GWT to 1.4 ------------------ Key: JBRULES-910 URL: http://jira.jboss.com/jira/browse/JBRULES-910 Project: JBoss Rules Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-brms Reporter: Michael Neale Assigned To: Fernando Meyer Would also be nice to use the new RichText widget on the documentation (for the doucmentation widget on the rule editors). Also, using the Vertical and horizontal splitters would be awesome for the rule editor (so people can drag stuff around). -- 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

18 years, 9 months

3
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-641) Make sure smoke tests pass on an un-scoped JBoss5/Messaging instance

by Ovidiu Feodorov (JIRA)

Make sure smoke tests pass on an un-scoped JBoss5/Messaging instance -------------------------------------------------------------------- Key: JBMESSAGING-641 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-641 Project: JBoss Messaging Issue Type: Sub-task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.CR1 -- 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

18 years, 9 months

5
11
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-639) AS Integration

by Ovidiu Feodorov (JIRA)

AS Integration -------------- Key: JBMESSAGING-639 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-639 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2.0.CR1 Container task for anything related to integration. -- 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

18 years, 9 months

4
7
0 / 0

[JBoss JIRA] Created: (JBPM-886) change ejb timers from SLSB to an entity bean approach

by Tom Baeyens (JIRA)

change ejb timers from SLSB to an entity bean approach ------------------------------------------------------ Key: JBPM-886 URL: http://jira.jboss.com/jira/browse/JBPM-886 Project: JBoss jBPM Issue Type: Feature Request Reporter: Tom Baeyens Assigned To: Tom Baeyens Fix For: jBPM jPDL 3.2.1 the problem is that all the timers are put on a single slsb. so we have to loop through all the timers to cancel or find one. that is a bottleneck. we need to change that approach to the use of entity beans. 1 entity bean per job. so that we can put queries for jobs and that way have a more efficient way of finding and cancelling ejb timers. -- 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

18 years, 9 months

1
5
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2007