February 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-2337) Big performance issue caused by Task entity and I18N

by Julien Cheype (JIRA)

Big performance issue caused by Task entity and I18N ---------------------------------------------------- Key: JBRULES-2337 URL: https://jira.jboss.org/jira/browse/JBRULES-2337 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-process-task Reporter: Julien Cheype Assignee: Mark Proctor There is a big performance issue with the Task entity, for example query to TasksAssignedAsPotentialOwner can take more than 2 seconds for returning less than 20 records using a MySql server Correction consist in adding mappedBy="id" to subjects, names and description attributes -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
7
0 / 0

[JBoss JIRA] Created: (JBREM-1272) Remove JBoss.ORG EULA file

by Ron Sigal (JIRA)

Remove JBoss.ORG EULA file -------------------------- Key: JBREM-1272 URL: https://issues.jboss.org/browse/JBREM-1272 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: Ron Sigal Assignee: Ron Sigal Priority: Minor Fix For: 2.2.3.SP4, 2.5.4.SP1 This file is no longer to be used. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-8862) Copyright notice for JBoss 6.0.0 Final is missing

by Anders Welen (JIRA)

Copyright notice for JBoss 6.0.0 Final is missing ------------------------------------------------- Key: JBAS-8862 URL: https://issues.jboss.org/browse/JBAS-8862 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 6.0.0.Final Reporter: Anders Welen Priority: Minor The "copyright.txt" file is missing from JBoss 6.0.0 Final download making it somewhat uncertain under what copyright and license the application server is released. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (SECURITY-568) Move networking code under a new project

by Darran Lofthouse (JIRA)

Move networking code under a new project ---------------------------------------- Key: SECURITY-568 URL: https://issues.jboss.org/browse/SECURITY-568 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2.0.4 The project jboss-negotiation-spnego is specifically for the message parsing and server side login module, client side interactions are external to this project so all networking should be in it's own specific project. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-567) Bring all dependencies in-line with AS6

by Darran Lofthouse (JIRA)

Bring all dependencies in-line with AS6 --------------------------------------- Key: SECURITY-567 URL: https://issues.jboss.org/browse/SECURITY-567 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Task Security Level: Public (Everyone can see) Components: Negotiation Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: Negotiation_2.0.4 The next release of JBoss Negotiation will target JBoss AS 6 so all dependencies should be brought in-line. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
1
0 / 0

[JBoss JIRA] Commented: (JBAOP-800) AopC report generation throws java.lang.ArrayIndexOutOfBoundsException

by James Wilson (JIRA)

[ https://issues.jboss.org/browse/JBAOP-800?page=com.atlassian.jira.plugin.... ] James Wilson commented on JBAOP-800: ------------------------------------ The trunk commit won't show in the Subversion Commits log, but it's revision 110614. > AopC report generation throws java.lang.ArrayIndexOutOfBoundsException > ---------------------------------------------------------------------- > > Key: JBAOP-800 > URL: https://issues.jboss.org/browse/JBAOP-800 > Project: JBoss AOP > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.1.6.GA, 2.1.6 CP01 > Reporter: Magesh Bojan > Assignee: Kabir Khan > Priority: Minor > Fix For: 2.1.6.CP02, Branch_2_2, TRUNK > > Attachments: diff.txt, HelloAOP5.zip > > > Using the related JIRA [JBPAPP-3082]'s sample trying a > <aopc compilerclasspathref="jboss.aop.classpath" verbose="true" report="true"> > <classpath path="${classes.dir}"/> > <src path="${classes.dir}"/> > <include name="**/hello/HelloBean.class"/> > </aopc> > results in error > [aopc] Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 0 > [aopc] at org.jboss.aop.standalone.XmlReport.outputAdvisor(XmlReport.java:204) > [aopc] at org.jboss.aop.standalone.XmlReport.outputPackage(XmlReport.java:139) > [aopc] at org.jboss.aop.standalone.XmlReport.outputPackage(XmlReport.java:127) > [aopc] at org.jboss.aop.standalone.XmlReport.outputPackage(XmlReport.java:127) > [aopc] at org.jboss.aop.standalone.XmlReport.outputPackage(XmlReport.java:127) > [aopc] at org.jboss.aop.standalone.XmlReport.outputPackage(XmlReport.java:127) > [aopc] at org.jboss.aop.standalone.XmlReport.outputPackage(XmlReport.java:127) > [aopc] at org.jboss.aop.standalone.XmlReport.outputPackage(XmlReport.java:127) > [aopc] at org.jboss.aop.standalone.XmlReport.toXml(XmlReport.java:70) > [aopc] at org.jboss.aop.standalone.Compiler.compile(Compiler.java:216) > [aopc] at org.jboss.aop.standalone.Compiler.main(Compiler.java:88) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBAOP-800) AopC report generation throws java.lang.ArrayIndexOutOfBoundsException

by James Wilson (JIRA)

[ https://issues.jboss.org/browse/JBAOP-800?page=com.atlassian.jira.plugin.... ] James Wilson resolved JBAOP-800. -------------------------------- Fix Version/s: Branch_2_2 TRUNK Resolution: Done > AopC report generation throws java.lang.ArrayIndexOutOfBoundsException > ---------------------------------------------------------------------- > > Key: JBAOP-800 > URL: https://issues.jboss.org/browse/JBAOP-800 > Project: JBoss AOP > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.1.6.GA, 2.1.6 CP01 > Reporter: Magesh Bojan > Assignee: Kabir Khan > Priority: Minor > Fix For: 2.1.6.CP02, Branch_2_2, TRUNK > > Attachments: diff.txt, HelloAOP5.zip > > > Using the related JIRA [JBPAPP-3082]'s sample trying a > <aopc compilerclasspathref="jboss.aop.classpath" verbose="true" report="true"> > <classpath path="${classes.dir}"/> > <src path="${classes.dir}"/> > <include name="**/hello/HelloBean.class"/> > </aopc> > results in error > [aopc] Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 0 > [aopc] at org.jboss.aop.standalone.XmlReport.outputAdvisor(XmlReport.java:204) > [aopc] at org.jboss.aop.standalone.XmlReport.outputPackage(XmlReport.java:139) > [aopc] at org.jboss.aop.standalone.XmlReport.outputPackage(XmlReport.java:127) > [aopc] at org.jboss.aop.standalone.XmlReport.outputPackage(XmlReport.java:127) > [aopc] at org.jboss.aop.standalone.XmlReport.outputPackage(XmlReport.java:127) > [aopc] at org.jboss.aop.standalone.XmlReport.outputPackage(XmlReport.java:127) > [aopc] at org.jboss.aop.standalone.XmlReport.outputPackage(XmlReport.java:127) > [aopc] at org.jboss.aop.standalone.XmlReport.outputPackage(XmlReport.java:127) > [aopc] at org.jboss.aop.standalone.XmlReport.toXml(XmlReport.java:70) > [aopc] at org.jboss.aop.standalone.Compiler.compile(Compiler.java:216) > [aopc] at org.jboss.aop.standalone.Compiler.main(Compiler.java:88) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-1286) ConcurrentModificationException encountered when starting JGroups 2.12RC1 when diagnostics is enabled

by William Burns (JIRA)

ConcurrentModificationException encountered when starting JGroups 2.12RC1 when diagnostics is enabled ----------------------------------------------------------------------------------------------------- Key: JGRP-1286 URL: https://issues.jboss.org/browse/JGRP-1286 Project: JGroups Issue Type: Bug Affects Versions: 2.12 Reporter: William Burns Assignee: Bela Ban I saw this error once when starting up my server using the default TCP.xml file. I have not been able to reproduce it more than once. I just wanted to submit this so that the handlers object can be properly protected via synchronization or java.util.concurrent related facility. 48 E 15:55:19,696 (TCP ) failure handling diagnostics request java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(Unknown Source) at java.util.HashMap$KeyIterator.next(Unknown Source) at org.jgroups.protocols.TP$DiagnosticsHandler.handleDiagnosticProbe(TP.java:2157) at org.jgroups.protocols.TP$DiagnosticsHandler.run(TP.java:2130) at java.lang.Thread.run(Unknown Source) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JGRP-1268) Allow 0.0.0.0 as bind address

by Bela Ban (JIRA)

Allow 0.0.0.0 as bind address ----------------------------- Key: JGRP-1268 URL: https://issues.jboss.org/browse/JGRP-1268 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban Fix For: 2.12 Currently, bind_addr has to be a valid interface and the wildcard (0.0.0.0) address is not permitted. The reason is that bind_addr determines the physical address of a node, e.g. 192.168.1.5:46537, and using 0.0.0.0:46537 wouldn't allow us to identify the node in order to send it a message. To allow for TCP and UDP sockets to bind to the wildcard address, we could either use a bind_addr of 0.0.0.0 and introduce an additional property to pick the physical address (e.g. physical_addr="192.168.1.5" / physical_addr="GLOBAL"), or continue using bind_addr to determine the physical address and add a property (bind_to_wild_card_addr="true") to make the UDP and TCP sockets bind to the wildcard address (if true). -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-7049) tests-jacc-securitymgr test server fails to start with OpenJDK 6

by Shelly McGowan (JIRA)

tests-jacc-securitymgr test server fails to start with OpenJDK 6 ---------------------------------------------------------------- Key: JBAS-7049 URL: https://jira.jboss.org/jira/browse/JBAS-7049 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security Reporter: Shelly McGowan Assignee: Anil Saldhana Fix For: JBossAS-5.2.0.Beta1 This test server runs with security manager and a server.policy file. The test target boots fine with Sun JDK 6. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
17
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 2011