November 2006 - 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, 5 months

2
2
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, 5 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, 5 months

2
1
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, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (JBRULES-476) DSL constraint appending needs to be tolerant of spaces

by Michael Neale (JIRA)

DSL constraint appending needs to be tolerant of spaces ------------------------------------------------------- Key: JBRULES-476 URL: http://jira.jboss.com/jira/browse/JBRULES-476 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 3.0.4 Reporter: Michael Neale Assigned To: Michael Neale If you do [when]-foo bar=Baz() it will fail to expand unless you put a space after the "-". -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3431) AuthorizationInterceptor throwing ArrayIndexOutOfBoundsException

by Anil Saldhana (JIRA)

AuthorizationInterceptor throwing ArrayIndexOutOfBoundsException ---------------------------------------------------------------- Key: JBAS-3431 URL: http://jira.jboss.com/jira/browse/JBAS-3431 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: JMX, Security Affects Versions: JBossAS-4.0.4.GA Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.CR1 As Originally reported in JBJMX-97, the user says: ========================================================================================== I have secured the jmx-invoker-service using JAAS and the standard UsersRolesLoginModule. I am able to authenticate (basic authentication) through the web UI and manage the console using the same login config. I am getting a remote connection to the JMX server from an InitialContext that is populated with the user name and password: env.put(Context.SECURITY_PRINCIPAL, userName); env.put(Context.SECURITY_CREDENTIALS, password); Then I look up the MBeanServerConnection and try to get the MBeanInfo MBeanServerConnection server = lookup("jmx/invoker/RMIAdaptor", MBeanServerConnection.class); ObjectName name = new ObjectName(theName); MBeanInfo info = server.getMBeanInfo(name); At this point the server throws an ArrayIndexOutOfBoundsException from org.jboss.jmx.connector.invoker.AuthorizationInterceptor line 107. If I try and set an attribute: server.setAttribute(name, new Attribute("searchText", searchText)); I get instead at the same line: java.lang.ClassCastException: javax.management.Attribute at org.jboss.jmx.connector.invoker.AuthorizationInterceptor.invoke(AuthorizationInterceptor.java:107) at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:108) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) ========================================================================================== -- 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, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-965) Localization Support bug

by 吴奕雄 (JIRA)

Localization Support bug ------------------------ Key: JBPORTAL-965 URL: http://jira.jboss.com/jira/browse/JBPORTAL-965 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal CMS Affects Versions: 2.4 Final Environment: windowxp,ie6,charset=zh-ch Reporter: 吴奕雄 Priority: Minor Fix For: 2.0 Branch, 2.0.2 Final, 2.2 Branch, 2.4 Final -- 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, 5 months

4
7
0 / 0

[JBoss JIRA] Created: (JBAS-3887) Upgrade Javassist to v3.4.0

by Dimitris Andreadis (JIRA)

Upgrade Javassist to v3.4.0 --------------------------- Key: JBAS-3887 URL: http://jira.jboss.com/jira/browse/JBAS-3887 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Other Reporter: Dimitris Andreadis Fix For: JBossAS-4.2.0.CR1 Upgrade to the latest Javassist -- 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, 5 months

3
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-567) Bring persistence manager configs up to date

by Tim Fox (JIRA)

Bring persistence manager configs up to date -------------------------------------------- Key: JBMESSAGING-567 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-567 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.0.Alpha2 For Alpha1, only the mysql persistence manager config has been brought up to date with the new database related changes. We need to bring the postgres, mssql, oracle and sybase configs up to date too. -- 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, 5 months

5
11
0 / 0

[JBoss JIRA] Created: (JBAS-3776) Update SerialVersionUIDUnitTestCase to test against new versions

by Ryan Campbell (JIRA)

Update SerialVersionUIDUnitTestCase to test against new versions ---------------------------------------------------------------- Key: JBAS-3776 URL: http://jira.jboss.com/jira/browse/JBAS-3776 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Ryan Campbell Priority: Critical Fix For: JBossAS-4.0.6.CR1 Here is how to build the .ser database of serialVersionUIDs: Builid jboss-4.0.5 with jdk14 cd build/output java -XX:MaxPermSize=512m -Xmx2000m -cp ../../varia/output/classes org.jboss.tools.SerialVersionUID jboss-4.0.5.GA/ cp serialuid.ser $WORK/Branch_4_0/testsuite/src/etc/serialVersionUID/405.ser Then the SerialVersionUIDUnitTestCase needs to be updated to test against 4.0.3SP1, 4.0.4, and 4.0.5. The badpackages list will probably need to be different for each version. -- 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, 5 months

4
4
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 November 2006