January 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-5177) JBoss AS 5.0.0.Beta3 not compatible with Netbeans 6.0

by pedalshoe (JIRA)

JBoss AS 5.0.0.Beta3 not compatible with Netbeans 6.0 ----------------------------------------------------- Key: JBAS-5177 URL: http://jira.jboss.com/jira/browse/JBAS-5177 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-5.0.0.Beta3 Environment: MS Windows XP Netbeans IDE v6.0 JDK v1.5.0_10 Reporter: pedalshoe JBoss as5.0.0.Beta2 worked with Netbeans 6.0. I tried to add a new J2ee server and chose the the Beta3 directory but I get the message: "The domain path is not valid or your domains don't meet minimal requirements." from Netbeans 6.0. -- 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, 5 months

4
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1131) Allow EJB3 testsuite to have JGroups send/receive via a different interface than other services

by Brian Stansberry (JIRA)

Allow EJB3 testsuite to have JGroups send/receive via a different interface than other services ----------------------------------------------------------------------------------------------- Key: EJBTHREE-1131 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1131 Project: EJB 3.0 Issue Type: Feature Request Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Priority: Minor Fix For: AS 5.0.0.Beta3, Branch_4_2 Allow the testsuite to do the equivalent to this for clustered tests: ./run.sh -c node0 -b localhost -Djgroups.bind_addr=10.xx.xx.xx ./run.sh -c node1 -b 10.xx.xx.xx -Djgroups.bind_addr=10.xx.xx.xx The non-clustering portion of the EJB3 testsuite has problems if node0 does not use -b localhost. On some test servers, we're finding troubles multicasting between lo and ethX, causing issues with the clustering tests. The intent here is to allow JGroups on both nodes to send/receive via the interface where multicast works. The value passed to -Djgroups.bind_addr is set via ant property node0.jgroups.bind_addr and node1.jgroups.bind_addr. If not explicitly set, by default the former is equal to ${node0} and the latter is equal to ${node1}. That is, by default JGroups will use the same interface as is passed to -b, the same behavior as before this change is made. See JBPAPP-448 -- 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, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1052) doc for SFSB removal timeout

by William DeCoste (JIRA)

doc for SFSB removal timeout ---------------------------- Key: EJBTHREE-1052 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1052 Project: EJB 3.0 Issue Type: Task Affects Versions: AS 4.2.1.GA Reporter: William DeCoste Assigned To: William DeCoste Priority: Minor -- 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, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1090) NPE when combining AOP and EJB3 interceptors

by William DeCoste (JIRA)

NPE when combining AOP and EJB3 interceptors -------------------------------------------- Key: EJBTHREE-1090 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1090 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.2.GA, AS 4.2.1.GA, AS 4.2.0 GA Reporter: William DeCoste Assigned To: William DeCoste -- 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, 5 months

2
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1057) SessionContext.getEJBObject should throw an IllegalStateException if there is no remote interface defined

by Carlo de Wolf (JIRA)

SessionContext.getEJBObject should throw an IllegalStateException if there is no remote interface defined --------------------------------------------------------------------------------------------------------- Key: EJBTHREE-1057 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1057 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Fix For: AS 4.2.2.GA SessionContext.getEJBObject should throw an IllegalStateException when the bean doesn't have a remote interface. (Similar for getEJBLocalObject.) -- 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, 5 months

3
12
0 / 0

[JBoss JIRA] Created: (EJBTHREE-905) SessionContext.getEJBLocalObject & SessionContext.getEJBObject() fail on @PostConstruct

by William DeCoste (JIRA)

SessionContext.getEJBLocalObject & SessionContext.getEJBObject() fail on @PostConstruct --------------------------------------------------------------------------------------- Key: EJBTHREE-905 URL: http://jira.jboss.com/jira/browse/EJBTHREE-905 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.0 CR1 Reporter: William DeCoste Assigned To: William DeCoste Fix For: AS 4.2.0 CR2 Either call creates a new beqan instance via jndi lookup. Call to getEJBLocalObject() in @PostConstruct causes infinite loop. -- 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, 5 months

3
9
0 / 0

[JBoss JIRA] Created: (EJBTHREE-699) StackOverflowError in org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy

by Michael Grübsch (JIRA)

StackOverflowError in org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy ----------------------------------------------------------------------- Key: EJBTHREE-699 URL: http://jira.jboss.com/jira/browse/EJBTHREE-699 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC7 - FD Environment: Windows XP Reporter: Michael Grübsch Priority: Critical I refer to source version $Revision: 1.1.4.2 $ This is an excerpt from the stack trace: at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.getProxyString(MessageInflowLocalProxy.java:502) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:114) at $Proxy398.toString(Unknown Source) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.getProxyString(MessageInflowLocalProxy.java:502) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:114) at $Proxy398.toString(Unknown Source) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.getProxyString(MessageInflowLocalProxy.java:502) at org.jboss.ejb3.mdb.inflow.MessageInflowLocalProxy.invoke(MessageInflowLocalProxy.java:114) You may see, that invoke calls getProxyString which in turn on the proxy calls invoke! -- 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, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1062) Finding the default local business interface on a bean with a superclass that implements interfaces doesn't work

by Carlo de Wolf (JIRA)

Finding the default local business interface on a bean with a superclass that implements interfaces doesn't work ---------------------------------------------------------------------------------------------------------------- Key: EJBTHREE-1062 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1062 Project: EJB 3.0 Issue Type: Bug Affects Versions: AS 4.2.2.GA Reporter: Carlo de Wolf The following doesn't work: @Stateless class MyBean extends SuperBean implements ExpectedLocalInterface {} interface ExpectedLocalInterface {} class SuperBean implements OtherInterface {} interface OtherInterface {} Based on the spec ExpectedLocalInterface is expected to become the local business interface. EJB 3 4.6.6: If bean class implements a single interface, that interface is assumed to be the busi- ness interface of the bean. This business interface will be a local interface unless the interface is designated as a remote business interface by use of the Remote annota- tion on the bean class or interface or by means of the deployment descriptor. -- 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, 5 months

4
16
0 / 0

[JBoss JIRA] Created: (JGRP-408) Expose classes, attributes and operations via @ManagedResource, @ManagedAttribute and @ManagedOperation

by Bela Ban (JIRA)

Expose classes, attributes and operations via @ManagedResource, @ManagedAttribute and @ManagedOperation ------------------------------------------------------------------------------------------------------- Key: JGRP-408 URL: http://jira.jboss.com/jira/browse/JGRP-408 Project: JGroups Issue Type: Feature Request Affects Versions: 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6 We should be able to simply make an object expose management information by annotating it. Input: annotations and classes Output: classes which are registered with the platform MBeanServer at runtime using an API (which is also provided). This API uses the annotations and reflection to create DynamicMBeans (or MXBeans ?) which are then registered with the MBeanServer. Example: @ManagedResource(objectName="jgroups:type=protocol;name=UDP") public class UDP extends Protocol { @ManagedAttribute(name="Sent", descr="Number of bytes sent") long sent_msgs=0; // generates a 'public long getSent()' getter, *no* setter ! @ManagedOperation(description="Prints statistics over the last N seconds") @Parameters({@Parameter(name="timeframe", description="Number of milliseconds (0 for all stats)")}) public String printStats(long timeframe) { // implement; } } -- 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, 5 months

3
5
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-156) JBoss clustering start reboots machine

by Samuel (JIRA)

JBoss clustering start reboots machine -------------------------------------- Key: JBCLUSTER-156 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-156 Project: JBoss Clustering Issue Type: Bug Security Level: Public (Everyone can see) Environment: JBOSS 4.0.3, Java 5,XP professional Reporter: Samuel Assigned To: Brian Stansberry Priority: Blocker I was setting up clustering and ran JBoss app server with run -c all option. First time it ran fine. Well and good. Then I shutdown the server. Re-launched run -c all and when the server brings up it reboots my windows xp. -- 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, 5 months

4
14
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 January 2008