October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4862) Verify whether -Djava.net.preferIPv4Stack=true should be disabled on Linux/jdk6+

by lepe (JIRA)

Verify whether -Djava.net.preferIPv4Stack=true should be disabled on Linux/jdk6+ -------------------------------------------------------------------------------- Key: JBAS-4862 URL: http://jira.jboss.com/jira/browse/JBAS-4862 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: System service Reporter: lepe Assigned To: Dimitris Andreadis Fix For: JBossAS-5.0.1.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

16 years, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-4861) CLONE -bin/run.sh should force IPv4 on Darwin systems

by lepe (JIRA)

CLONE -bin/run.sh should force IPv4 on Darwin systems ----------------------------------------------------- Key: JBAS-4861 URL: http://jira.jboss.com/jira/browse/JBAS-4861 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: System service Reporter: lepe Assigned To: Dimitris Andreadis Fix For: JBossAS-4.2.0.CR2, JBossAS-5.0.0.Beta3 There is an issue in the Linux kernel that causes ipv6 to not work correctly with JDK 1.5 and lower. As a result, jbossas does not start by default on Linux unless ipv4 is forced. To that end, run.sh needs updating. Something like: if [ "`uname`" = "Linux" ]; then JAVA_OPTS="$JAVA_OPTS -Djava.net.preferIPv4Stack=true" fi fi So that Linux systems use ipv4 -- 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

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1063) Ensure EJBSpecUnitTestCase Passes for Anil

by Andrew Rubinger (JIRA)

Ensure EJBSpecUnitTestCase Passes for Anil ------------------------------------------ Key: EJBTHREE-1063 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1063 Project: EJB 3.0 Issue Type: Task Affects Versions: HEAD Reporter: Andrew Rubinger Assigned To: Andrew Rubinger Fix For: HEAD Requested by Anil; possibly related to EJB3Registry -- 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

1
5
0 / 0

[JBoss JIRA] Created: (JBAS-4860) List of Timers contains all SLSB and MDB, not only those implementing TimedObject

by Frank Langelage (JIRA)

List of Timers contains all SLSB and MDB, not only those implementing TimedObject --------------------------------------------------------------------------------- Key: JBAS-4860 URL: http://jira.jboss.com/jira/browse/JBAS-4860 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.2.GA Environment: JBoss-4.2.2.GA, built from the current sources. Sun JDK 1.5.0_13 on Sun Solaris 10 SPARC. Reporter: Frank Langelage Priority: Minor If I call the listTimers operation using the jmx-console I see all Stateless session Beans and all Message Driven Beans now, but only 5 of this 64 are really TimeObjects: Output is for example: [target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-core.jar,name=MbiWaehrFacade] [target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-planning.jar,name=MbiProbfSelect] [target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-costing.jar,name=PreliminaryCosting] [target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-common.jar,name=Version] [target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-core.jar,name=Calendar] [target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-inventory.jar,name=StockManagement] [target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-sales.jar,name=SalesOrder] [target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-sales.jar,name=SalesItem] [target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-core.jar,name=MailService] handle: [id=1190398872277,target=[target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-core.jar,name=MailService],first=21-Sep-2007 20:23:00.000,periode=60000] [id=1190398872277,target=[target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-core.jar,name=MailService],remaining=47564,periode=60000,in_timeout] [target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-core.jar,name=MbiFistaFacade] [target=jboss.j2ee:service=EJB3,ear=mbi2e-lafr-sb2000-ipc.ear,jar=ejb-session-core.jar,name=MessageRetrieval] MailService implements TimeObject, but all others do not. My Stateful Session Beans don't appear in the list, but all Stateless and MDBs do. -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1755) Identity chapter has lots of typos

by Chris Laprun (JIRA)

Identity chapter has lots of typos ---------------------------------- Key: JBPORTAL-1755 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1755 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Chris Laprun -- 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

1
0
0 / 0

[JBoss JIRA] Created: (JBAOP-469) Make sure @Aspect works in older versions of AS

by Kabir Khan (JIRA)

Make sure @Aspect works in older versions of AS ----------------------------------------------- Key: JBAOP-469 URL: http://jira.jboss.com/jira/browse/JBAOP-469 Project: JBoss AOP Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kabir Khan Assigned To: Stale Pedersen Fix For: 2.0.0.beta2 The repackaging of the annotations stuff http://jira.jboss.com/jira/browse/JBAOP-428 has caused some problems. Create a simple test in the testsuite for https://svn.jboss.org/repos/jbossas/branches/Branch_4_2/ using @Aspect + @Bind, instead of a jboss-aop.xml file. If any classes are missing, add jars taken from jboss-container.jar to the AS 4.x deployers for both jdk 1.4 and jdk 5. There are some examples for this already in https://svn.jboss.org/repos/jbossas/projects/aop/trunk/build/build-releas... JBoss 5 uses the correct version of MC, so all the classes will be available there. -- 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

1
2
0 / 0

[JBoss JIRA] Updated: (JBCACHE-295) Add unit tests for ReplicationQueue

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-295?page=all ] Brian Stansberry updated JBCACHE-295: ------------------------------------- Fix Version/s: 2.2.0.GA (was: 2.1.0.GA) (was: 2.1.0.CR1) > Add unit tests for ReplicationQueue > ----------------------------------- > > Key: JBCACHE-295 > URL: http://jira.jboss.com/jira/browse/JBCACHE-295 > Project: JBoss Cache > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Priority: Minor > Fix For: 2.2.0.GA > > -- 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

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-375) Grouping of messages with JMSXGroupId

by Jeff Mesnil (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-375?page=all ] Jeff Mesnil updated JBMESSAGING-375: ------------------------------------ Attachment: patch-JBMESSAGING-375.txt updated Stian's patch for JBoss Messaging 1.4.0 (based on r3190): - base class is RoundRobinDistributor - "grouping" round robin algorithm is done in GroupingRoundRobinDistributor - associated tests are in GroupingRoundRobinDistributorTest - put test code common to RRDTest and GroupingRRDTest into SimpleReferenceableReceiver class - added support to reset bound receiver by setting JMSXGroupSeq to 0 some caveats: - GroupingRRD's algorithm is brittle and depends on a lot of internals from RRD which should not be exposed -> maybe grouping should be handled directly by RRD? - GroupingRRD is not used by MessagingQueue (still using RRD) > Grouping of messages with JMSXGroupId > ------------------------------------- > > Key: JBMESSAGING-375 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-375 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 2.0.0 Beta 1 > > Attachments: jbmessaging-375.patch, patch-JBMESSAGING-375.txt > > Original Estimate: 1 week > Remaining Estimate: 1 week > > We should add an ability to group messages by JMSXGroupID, so any messages with the same group id always go to the same consumer on a queue. > This would be useful when having competing consumers on a queue and you want each consumer to handle all messages with a particular value of JMSXGroupID -- 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

1
0
0 / 0

[JBoss JIRA] Created: (GPD-156) GenericElementXmlAdapter doesnt add child nodes

by Imran Naqvi (JIRA)

GenericElementXmlAdapter doesnt add child nodes ----------------------------------------------- Key: GPD-156 URL: http://jira.jboss.com/jira/browse/GPD-156 Project: JBoss jBPM GPD Issue Type: Bug Components: jpdl Affects Versions: jBPM JPDL Designer 3.1.0.CR Reporter: Imran Naqvi Assigned To: Koen Aers If you have a template such as: <?xml version="1.0"?> <process-definition name="Movie" version="11"> <start-state name="Start"> <transition to="Get MPEG Properties" /> </start-state> <node name="Get MPEG Properties"> <action class="SomeActionHandler"><send>010901</send> <keys> <entry> <key>VarName</key> <value>1122</value> </entry> </keys> <receive> <element>030101</element> <element>030102</element> </receive> </action> <transition to="End"/> </node> <end-state name="End" /> The nested Generic Elements arent added by the adapter. The reason for this is that the GenericElementXmlAdapter.doModelAdd() doesnt do anything. We need to add the following code to this method: String type = child.getElementType(); SemanticElement jpdlElement; jpdlElement = getSemanticElementFactory().createById("org.jbpm.gd.jpdl.genericElement"); child.initialize(jpdlElement); GenericElement genericElement= (GenericElement )getSemanticElement(); genericElement.addGenericElement((GenericElement)jpdlElement); -- 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

2
2
0 / 0

[JBoss JIRA] Created: (JBAOP-415) Advice Matching algorithm is ignoring generics

by Flavia Rainone (JIRA)

Advice Matching algorithm is ignoring generics ---------------------------------------------- Key: JBAOP-415 URL: http://jira.jboss.com/jira/browse/JBAOP-415 Project: JBoss AOP Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.0.0.alpha4 Reporter: Flavia Rainone Assigned To: Flavia Rainone Fix For: 2.0.0.alpha5 Advice Matching does not takes into account generic types; it is working with the old reflection API instead (Class instead of Type). To modifiy this, we need to update code in classes: - org.jboss.aop.advice.annotation.AdviceInfo - org.jboss.aop.advice.annotation.AnnotatedParameterAdviceInfo - org.jboss.aop.advice.AdviceMethodProperties - joinpoint generators that pass the return, arguments and exception types to AdviceMethodProperties instances. This includes updating the assignability degree algorithm of org.jboss.aop.advice.annotation package. The methods for this task are partly written in org.jboss.test.aop.beforeafterArgs.ArgAspectGenerics. Tests for generic return types are also necessary, and need to be written. -- 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

2
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007