February 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (SECURITY-117) JBossAuthorizationContext is not initializing the modules with the subject passed

by Anil Saldhana (JIRA)

JBossAuthorizationContext is not initializing the modules with the subject passed --------------------------------------------------------------------------------- Key: SECURITY-117 URL: http://jira.jboss.com/jira/browse/SECURITY-117 Project: JBoss Security and Identity Management Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: 2.0.2-BETA4 Reporter: Anil Saldhana Assigned To: Anil Saldhana Fix For: 2.0.2-BETA5 The initialize modules method is taking the instance variable (authenticatedSubject) and not the passed argument. -- 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, 3 months

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-678) NPE in NAKACK under startup load

by Bela Ban (JIRA)

NPE in NAKACK under startup load -------------------------------- Key: JGRP-678 URL: http://jira.jboss.com/jira/browse/JGRP-678 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6.2, 2.7 Attachments: NAKACK.patch.txt Here's another NPE that we found, this time in NAKACK in 2.6.1. Again, we are starting up ~30 systems at once which causes some thrashing for a couple of minutes until things settle down. You will notice that we also moved over to trace the dumping of the NAKACK table which at some points threatened to overwhelm our log systems. That has (I think) been mentioned here before. -- 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, 3 months

1
7
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1188) Deployment of @ManyToMany fails.

by Alexander Tsirel (JIRA)

Deployment of @ManyToMany fails. -------------------------------- Key: EJBTHREE-1188 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1188 Project: EJB 3.0 Issue Type: Bug Components: EJB3 Extensions Affects Versions: AS 4.2.1.GA Environment: JBoss Bootstrap Environment JBOSS_HOME: C:\jboss-4.2.1.GA JAVA: C:\Program Files\Java\jdk1.5.0_09\bin\java JAVA_OPTS: -Dprogram.name=run.bat -server -Xms128m -Xmx512m -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 CLASSPATH: C:\Program Files\Java\jdk1.5.0_09\lib\tools.jar;C:\jboss-4.2.1.GA\bin\run.jar Reporter: Alexander Tsirel Two entities relates as many to many (Course and Student). During deployment it throws: Caused by: org.hibernate.MappingException: Could not determine type for: java.util.Collection, for columns: org.hibernate.mapping.Column(students)] Both sides using Generics. Here is the latest code: @Entity(name = "StudentUni") public class Student implements Serializable { private int id; private String name; private Collection<Course> courses = new ArrayList<Course>(); public Student(){ id = (int) System.nanoTime(); } @Id public int getId() { return id; } public void setId(int id) { this.id = id; } public String getName() { return name; } public void setName(String name) { this.name = name; } @ManyToMany public Collection<Course> getCourses() { return courses; } public void setCourses(Collection<Course> courses) { this.courses = courses; } } @Entity(name = "CourseUni") public class Course implements Serializable { private int id; private String courseName; private Collection<Student> students = new ArrayList<Student>(); public Course(){ id = (int) System.nanoTime(); } @Id public int getId() { return id; } public void setId(int id) { this.id = id; } public String getCourseName() { return courseName; } public void setCourseName(String courseName) { this.courseName = courseName; } @ManyToMany(mappedBy = "courses") public Collection<Student> getStudents() { return students; } public void setStudents(Collection<Student> students) { this.students = students; } } -- 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, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (JGRP-676) Infinite NPE/error loop in ClientGmsImpl.java

by Bela Ban (JIRA)

Infinite NPE/error loop in ClientGmsImpl.java --------------------------------------------- Key: JGRP-676 URL: http://jira.jboss.com/jira/browse/JGRP-676 Project: JGroups Issue Type: Bug Affects Versions: 2.6.1 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6.2, 2.7 Attachments: ClientGmsImpl.stack.txt So we are starting up ~30 hosts at the same time running 2.6.1 and have seen a number of exception stacks and anomalies. There are a couple nasty bugs in the ClientGMSImpl.join() method which caused an infinite loop of NPE exceptions or other errors. I fixed 3 of them and left one more for someone who knows the code better. See the patch. -- 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, 3 months

1
4
0 / 0

[JBoss JIRA] Commented: (JBAS-2705) Expose sub-pool statistics

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2705?page=comments#action_12398215 ] Dimitris Andreadis commented on JBAS-2705: ------------------------------------------ Open a new one for backporting and link to this. > Expose sub-pool statistics > -------------------------- > > Key: JBAS-2705 > URL: http://jira.jboss.com/jira/browse/JBAS-2705 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: JCA service > Reporter: Adrian Brock > Assigned To: Weston Price > Fix For: JBossAS-5.0.0.Beta1 > > > The JBossManagedConnectionPool should have a listStatistics() method > to show the stats per sub-pool. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-2705) Expose sub-pool statistics

by Vicky Kak (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2705?page=comments#action_12398204 ] Vicky Kak commented on JBAS-2705: --------------------------------- Dimitiris , this JIRA should be backported for Jboss4.2.* . I am looking at the related JBAS-1436 , I am not sure if this JIRA should be reopened Or new one for backporting should be created. I will incorporate "maximum waiting time for a connection in a pool" at sub-pool level which would also be updated in the Jboss5 later . > Expose sub-pool statistics > -------------------------- > > Key: JBAS-2705 > URL: http://jira.jboss.com/jira/browse/JBAS-2705 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: JCA service > Reporter: Adrian Brock > Assigned To: Weston Price > Fix For: JBossAS-5.0.0.Beta1 > > > The JBossManagedConnectionPool should have a listStatistics() method > to show the stats per sub-pool. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JGRP-677) Another NPE in ClientGmsImpl

by Bela Ban (JIRA)

Another NPE in ClientGmsImpl ---------------------------- Key: JGRP-677 URL: http://jira.jboss.com/jira/browse/JGRP-677 Project: JGroups Issue Type: Bug Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6.2, 2.7 Also saw this NPE inside of ClientGmsImpl.join() with 2.6.1. -- 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, 3 months

1
4
0 / 0

[JBoss JIRA] Created: (JGRP-683) Provide hooks to enable creation of all daemon threads

by Bela Ban (JIRA)

Provide hooks to enable creation of all daemon threads ------------------------------------------------------ Key: JGRP-683 URL: http://jira.jboss.com/jira/browse/JGRP-683 Project: JGroups Issue Type: Task Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.6.2, 2.7 Goal: to enable a developer to setup JGroups to use only daemon threads. Default will still be that IO bound threads are non-daemons Jon Richards wrote: > It works OK for the thread pools used by TP but a couple of problems: > > Problem 1: I need to kludge it a bit: it turns out that I need to do a > channel.connect() before I can modify/set the TP thread pools because > the thread pools are created in TP.start(). This means that non-daemon > threads can get created before I have a chance to modify the setting. What if I check in TP.start() if thread_pool/oob_thread_pool is already set and don't create a thread pool of already set ? Then you could create a JChannel, set the thread pool(s) and then call JChannel.connect(). > Problem 2: there are other threads at the transport level that get > created using ProtocolStack.getThreadFactory() and there is not way to > override how this thread factory gets created. I could provide setters for the 2 thread factories in ProtocolStack and make them non-final. Would that help ? -- 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, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1227) Statement leak in HandleBeforeCommit1PCRunner

by Kevin Conner (JIRA)

Statement leak in HandleBeforeCommit1PCRunner --------------------------------------------- Key: JBMESSAGING-1227 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1227 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3 Reporter: Kevin Conner Assigned To: Tim Fox Priority: Blocker >From JBESB-1450 "This leak appears to be coming from JBoss Messaging, specifically JDBCPersistenceManager$1HandleBeforeCommit1PCRunner.doTransaction(JDBCPersistenceManager.java:1587) This line creates a prepared statement within a loop but only the last statement created will be released. Other examples of this construct, within this file, use a simple guard to prevent subsequent allocations. This appears to be the only occurrence which does not." "The following change fixes the leak. Index: src/main/org/jboss/messaging/core/impl/JDBCPersistenceManager.java =================================================================== --- src/main/org/jboss/messaging/core/impl/JDBCPersistenceManager.java (revision 3648) +++ src/main/org/jboss/messaging/core/impl/JDBCPersistenceManager.java (working copy) @@ -1584,8 +1584,11 @@ ChannelRefPair pair = (ChannelRefPair) i.next(); MessageReference ref = pair.ref; - psReference = conn + if (psReference == null) + { + psReference = conn .prepareStatement(getSQLStatement("INSERT_MESSAGE_REF")); + } // Now store the reference addReference(pair.channelID, ref, psReference, false); " -- 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, 3 months

2
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1218) ResultSet not explicitly closed in JDBCPersistenceManager

by Tim Fox (JIRA)

ResultSet not explicitly closed in JDBCPersistenceManager --------------------------------------------------------- Key: JBMESSAGING-1218 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1218 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.4.0.SP3 Reporter: Tim Fox Assigned To: Tim Fox Priority: Minor Fix For: Stable branch A ResultSet is left open at line 924 JDBCPersistenceManager:loadFromStart. The JCA adapter will close this automatically so the only negative effect of this bug is a warning in the logs. Can safely ignore this until the next release when it will be fixed. -- 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, 3 months

2
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 2008