February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-768) MDB deployment error

by Ramil Israfilov (JIRA)

MDB deployment error -------------------- Key: EJBTHREE-768 URL: http://jira.jboss.com/jira/browse/EJBTHREE-768 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Environment: JDK1.5.0_06, UNIX and windows platforms Reporter: Ramil Israfilov Fix For: EJB 3.0 RC10 - FD I have an MDB which is defined like that import javax.jms.MessageListener; @MessageDriven(name = "EJBExecutorMDB", activationConfig = { @ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"), @ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/ExecutorQueue"), @ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "AUTO_ACKNOWLEDGE"), @ActivationConfigProperty(propertyName = "maxSession", propertyValue = "4"), @ActivationConfigProperty(propertyName = "SubscriptionDurability", propertyValue = "Durable") }) public class EJBExecutorMDB implements MessageListener { .... It works perfect during in JBOSS, but then I run it in JUNIT it fails with exception: "unable to determine messagingType interface for MDB" Only one difference that in JUNIT test I instrument built classes using cobertura - in that case my class implements two interfaces: MessageListener and cobertura interface. After looking in source code I found in org.jboss.ejb3.mdb.MDB: if (messagingType.getName().equals(Object.class.getName())) { ArrayList<Class> list = ProxyFactoryHelper.getBusinessInterfaces(clazz); if (list.size() > 1 || list.size() == 0) throw new RuntimeException("unable to determine messagingType interface for MDB"); messagingType = list.get(0); } Why such a dummy check is done ??? Why class must implement one and only one interface ?? could you check superclasses and allow multiple interfaces implementations on the class. Also on the link to forum people has similar problem: they don't implement interface, but extend superclass. And they got the same exception. -- 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, 2 months

2
2
0 / 0

[JBoss JIRA] Updated: (JGRP-155) TP.loopback should always be used

by Bela Ban (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-155?page=all ] Bela Ban updated JGRP-155: -------------------------- Fix Version/s: 2.6 (was: 2.5) > TP.loopback should always be used > --------------------------------- > > Key: JGRP-155 > URL: http://jira.jboss.com/jira/browse/JGRP-155 > Project: JGroups > Issue Type: Task > Affects Versions: 2.2.9, 2.2.8 > Reporter: Bela Ban > Assigned To: Bela Ban > Fix For: 2.6 > > > Investigate the 3 potential problem areas below: > - Memory leak caused by FC when credits are received too quickly > - Deadlocks caused by same threads calling themselves (e.g. VIEW_OK ack msgs) > - Preemption doesn't work: Scheduler is meaningless here -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-354) If response unmarshalling fails, RequestCorrelator passes garbage as the response

by Brian Stansberry (JIRA)

If response unmarshalling fails, RequestCorrelator passes garbage as the response --------------------------------------------------------------------------------- Key: JGRP-354 URL: http://jira.jboss.com/jira/browse/JGRP-354 Project: JGroups Issue Type: Bug Affects Versions: 2.4 Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.5 >From RequestCorrelator.receiveMessage: RspCollector coll=findEntry(hdr.id); if(coll != null) { Address sender=msg.getSrc(); Object retval=null; byte[] buf=msg.getBuffer(); try { retval=marshaller != null? marshaller.objectFromByteBuffer(buf) : Util.objectFromByteBuffer(buf); } catch(Exception e) { log.error("failed unmarshalling buffer into return value", e); try { retval=marshaller != null? marshaller.objectToByteBuffer(e) : Util.objectToByteBuffer(e); } catch(Exception e1) { log.error("failed marshalling exception " + e1 + " into buffer", e1); } } coll.receiveResponse(retval, sender); } The outer catch block should just be catch (Exception e) { log.error("failed unmarshalling buffer into return value", e); retval = e; } Looks like the bit about marshalling the exception came from handleRequest(), where it's needed. -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-274) Don't bind to a NIC if bind address is not set

by Bela Ban (JIRA)

Don't bind to a NIC if bind address is not set ---------------------------------------------- Key: JGRP-274 URL: http://jira.jboss.com/jira/browse/JGRP-274 Project: JGroups Issue Type: Feature Request Affects Versions: 2.3 SP1, 2.3, 2.2.9 SP3 (2.2.9.3), 2.2.9.2, 2.2.9.1, 2.2.9, 2.2.8, 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 If -Dbind.address or bind_addr are not set, JGroups picks the NIC to bind sockets to itself. However, especially for ServerSockets, this may not be desirable because we may want to have ServerSockets be able to receive packets through all interfaces, e.g. - NICs are 192.168.5.2, 192.168.0.2 and 127.0.0.1 (loopback) - When the bind address is set to 192.168.5.2, a given ServerSocket on port 7500 will *only accept packets from this NIC* - If someone connects to 192.168.0.2:7500 or 127.0.0.1:7500, the client will not be able to establish a connection because nobody is listening on those ports on the given NICs - If bind address was not set, this would be possible - Affected: FD_SOCK, FD_PING, TCP, TCP_NIO etc - We need to think about semantics for MulticastSockets where a wildcard address (not setting the bind address) means that the operating system picks the NIC, and *not* that the MulticastSocket will listen on all interfaces for incoming packets -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JGRP-385) TLS: provide OOB method calls for RpcDispatcher and MessageDispatcher

by Bela Ban (JIRA)

TLS: provide OOB method calls for RpcDispatcher and MessageDispatcher --------------------------------------------------------------------- Key: JGRP-385 URL: http://jira.jboss.com/jira/browse/JGRP-385 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 E.g. RcpDispatcher.callRemoteMethods(..., boolean oob) -- 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, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JGRP-277) Threadpool for timer (TimeScheduler)

by Bela Ban (JIRA)

Threadpool for timer (TimeScheduler) ------------------------------------ Key: JGRP-277 URL: http://jira.jboss.com/jira/browse/JGRP-277 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.4 Current, TimeScheduler is single threaded; long running tasks delay the execution of other tasks. Introduce a thread pool and let the user configure it: e.g. single-threaded, max of 5 threads etc -- 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, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JGRP-411) Timer: expose number of timer tasks (ProtocolStack) via JMX

by Bela Ban (JIRA)

Timer: expose number of timer tasks (ProtocolStack) via JMX ----------------------------------------------------------- Key: JGRP-411 URL: http://jira.jboss.com/jira/browse/JGRP-411 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.5 -- 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, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-849) Port the "mdb failure" smoke test from the 1.0 branch on the trunk

by Ovidiu Feodorov (JIRA)

Port the "mdb failure" smoke test from the 1.0 branch on the trunk ------------------------------------------------------------------ Key: JBMESSAGING-849 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-849 Project: JBoss Messaging Issue Type: Feature Request 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

19 years, 2 months

1
1
0 / 0

[JBoss JIRA] Updated: (JBRULES-214) goddamn keyword collisions damn it damn damn

by Michael Neale (JIRA)

[ http://jira.jboss.com/jira/browse/JBRULES-214?page=all ] Michael Neale updated JBRULES-214: ---------------------------------- Priority: Minor (was: Critical) downgrading it as most has been solved now. > goddamn keyword collisions damn it damn damn > -------------------------------------------- > > Key: JBRULES-214 > URL: http://jira.jboss.com/jira/browse/JBRULES-214 > Project: JBoss Rules > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Drl Parser/Builder > Affects Versions: 3.0-rc1 > Reporter: Michael Neale > Assigned To: Edson Tirelli > Priority: Minor > Fix For: 3.1-m3 > > > Getting more complaints about collisions with keywords. Things like "end" are obvious, but even "duration" etc... > Parser possibly needs to be a bit cleverer (not sure why duration is barfing.. but anyway). > I guess the only clear way forward is to enforce newline characters. > Most often the problem happens in the LHS. On the RHS its just "end" that is a problem. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-847) Some installer JBoss installations (4.0.3, 4.0.3SP1) do not contain a BindingManager declaration in their jboss-service.xml, so release-admin.xml doesn' t work properly

by Ovidiu Feodorov (JIRA)

Some installer JBoss installations (4.0.3, 4.0.3SP1) do not contain a BindingManager declaration in their jboss-service.xml, so release-admin.xml doesn' t work properly ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Key: JBMESSAGING-847 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-847 Project: JBoss Messaging Issue Type: Bug Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Priority: Critical 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

19 years, 2 months

1
2
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 February 2007