August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBAS-2057) Need an EJB3 mbean JSR-77 mapping

by Galder Zamarreno (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2057?page=all ] Galder Zamarreno updated JBAS-2057: ----------------------------------- Priority: Critical (was: Major) > Need an EJB3 mbean JSR-77 mapping > --------------------------------- > > Key: JBAS-2057 > URL: http://jira.jboss.com/jira/browse/JBAS-2057 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: EJB2 > Reporter: Scott M Stark > Assigned To: Bill Burke > Priority: Critical > Fix For: JBossAS-4.0.5.GA > > > Deployment of an ejb3 component should result in an jsr-77 ejb mbean for integration into the management tools. I don't know if an ejb3 deployment can just be treated as an ejb2.1 deployment by the LocalJBossServerDomain and this will just work. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3071) MemoryLeak (redeployment) on EJB3

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3071?page=comments#action_12340323 ] Dimitris Andreadis commented on JBAS-3071: ------------------------------------------ Clebert, is this related to the MBeanProxy usage issue? Any chance someone will be looking to this for 4.0.5.CR1? > MemoryLeak (redeployment) on EJB3 > --------------------------------- > > Key: JBAS-3071 > URL: http://jira.jboss.com/jira/browse/JBAS-3071 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: EJB3 > Affects Versions: JBossAS-4.0.4.CR2 > Reporter: Clebert Suconic > Assigned To: Bill Burke > Priority: Critical > Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.CR1 > > > This might be caused by JBAS-3016: > But I'm seeing this strong reference: > org.jboss.mx.loading.UnifiedClassLoader3@33411906 > !--- org.jboss.ejb3.stateless.StatelessContainer@29610827 > We should make sure EJB3 packages are not leaking. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3242) EE spec requires that web container aborts any active txn at the end of a request

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3242?page=comments#action_12340322 ] Dimitris Andreadis commented on JBAS-3242: ------------------------------------------ Is there is any chance to have a tomcat release that fixes this for jboss 4.0.5.CR1? > EE spec requires that web container aborts any active txn at the end of a request > --------------------------------------------------------------------------------- > > Key: JBAS-3242 > URL: http://jira.jboss.com/jira/browse/JBAS-3242 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Affects Versions: JBossAS-4.0.4.GA > Reporter: Gavin King > Assigned To: Remy Maucherat > Priority: Critical > Fix For: JBossAS-4.0.5.CR1 > > > The Java EE spec requires that if there is any active JTA transaction at the end of a servlet request, then the container must abort the txn. JBoss currently does not do this. Instead it leaves orphaned transactions dangling about on pooled threads, ready and waiting to be resumed by any random request that comes along. > This is really Bad behavior and I'm kinda shocked. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3306) Upgrade JBoss AS to use MyFaces 1.1.3

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3306?page=comments#action_12340321 ] Dimitris Andreadis commented on JBAS-3306: ------------------------------------------ I checked again and there is no new release, so what is it going to be? > Upgrade JBoss AS to use MyFaces 1.1.3 > ------------------------------------- > > Key: JBAS-3306 > URL: http://jira.jboss.com/jira/browse/JBAS-3306 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: JBossAS-4.0.4.GA > Reporter: Gavin King > Assigned To: Stan Silvert > Priority: Critical > Fix For: JBossAS-4.0.5.CR1 > > > We need to upgrade JBoss to use MyFaces 1.1.3, which fixes many bugs. This is critical priority for Seam. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-3183) Integration with WebSphere MQ 5.x

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3183?page=all ] Dimitris Andreadis reassigned JBAS-3183: ---------------------------------------- Assignee: Weston Price (was: Adrian Brock) Assign to Weston. Any updates, BTW? > Integration with WebSphere MQ 5.x > --------------------------------- > > Key: JBAS-3183 > URL: http://jira.jboss.com/jira/browse/JBAS-3183 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: JMS service > Environment: WebSphereMQ 5.3 with Extended TX client > Reporter: Luc Texier > Assigned To: Weston Price > Priority: Critical > Fix For: JBossAS-4.0.5.CR1, JBossAS-5.0.1.CR1 > > > http://wiki.jboss.org/wiki/Wiki.jsp?page=UsingWebSphereMQSeriesWithJBossA... > we need to make some changes to StdServerSession and StdServerSessionPool to integrate two workarounds in order to properly integrate with WSMQ 5.x and support their XA resource implementation and transaction handling -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBESB-38) Migrate existing tests to QA

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-38?page=all ] Mark Little updated JBESB-38: ----------------------------- Fix Version/s: 4.0 (was: 4.0 Beta 1) > Migrate existing tests to QA > ---------------------------- > > Key: JBESB-38 > URL: http://jira.jboss.com/jira/browse/JBESB-38 > Project: JBoss ESB > Issue Type: Task > Security Level: Public(Everyone can see) > Components: ESB Core, Testing > Reporter: Mark Little > Assigned To: Arvinder Singh > Priority: Minor > Fix For: 4.0 > > Time Spent: 1 minute > Remaining Estimate: 2 hours > > Take the existing Rosetta tests and make sure they are added to the QA system for JBossESB. We need to be running this nightly 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBESB-69) General tidy-up of common services code

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-69?page=all ] Mark Little updated JBESB-69: ----------------------------- Fix Version/s: 4.0 (was: 4.0 Beta 1) > General tidy-up of common services code > --------------------------------------- > > Key: JBESB-69 > URL: http://jira.jboss.com/jira/browse/JBESB-69 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: ESB Core > Affects Versions: 4.0 Alpha 1 > Reporter: Mark Little > Assigned To: Arvinder Singh > Priority: Minor > Fix For: 4.0 > > > - common\src\org\jboss\soa\esb\services\* > 1) Refactor naming. > 2) Import specific classes not * -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-3345) Synch up with tomcat6 based jbossweb as the bundled web container

by Remy Maucherat (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3345?page=comments#action_12340318 ] Remy Maucherat commented on JBAS-3345: -------------------------------------- The jbossweb svn module can now be used by the AS build. > Synch up with tomcat6 based jbossweb as the bundled web container > ----------------------------------------------------------------- > > Key: JBAS-3345 > URL: http://jira.jboss.com/jira/browse/JBAS-3345 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service > Reporter: Scott M Stark > Assigned To: Remy Maucherat > Priority: Blocker > Fix For: JBossAS-5.0.0.Beta > > > We need a tomcat6 based version of jbosseb as the bundled web container for the jboss5 release. -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBESB-68) Tidy-up JDBC classes

by Mark Little (JIRA)

[ http://jira.jboss.com/jira/browse/JBESB-68?page=all ] Mark Little reassigned JBESB-68: -------------------------------- Assignee: Mohit Keswani (was: Arvinder Singh) > Tidy-up JDBC classes > -------------------- > > Key: JBESB-68 > URL: http://jira.jboss.com/jira/browse/JBESB-68 > Project: JBoss ESB > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Documentation, ESB Core > Affects Versions: 4.0 Alpha 1 > Reporter: Mark Little > Assigned To: Mohit Keswani > Priority: Minor > Fix For: 4.0 Beta 1 > > > - common\src\org\jboss\soa\esb\helpers\persist\JdbcCleanConn.java > 1) Refactor > - rename to conventions > - categorize exceptions instead of using Exception > - group into a db specific package instead of persist > - common\src\org\jboss\soa\esb\helpers\persist\SqlDbTable.java > 1) Refactor > - rename to conventions e.g getFldName - > getFieldName -- 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

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMESSAGING-328) Optimisation - batch messages to consumers

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-328?page=all ] Tim Fox closed JBMESSAGING-328. ------------------------------- Resolution: Won't Fix This is irrelvant now I have refactored with batching > Optimisation - batch messages to consumers > ------------------------------------------ > > Key: JBMESSAGING-328 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-328 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 1.0.5 > > Original Estimate: 3 days > Remaining Estimate: 3 days > > Instead of sending messages to client side consumers immediately, server side consumers can batch messages up and send them periodically every x milliseconds, the same can occur in the other direction for acknowledgements. This would be likely to increase overall throughput due to reduction in lock contention on the queue due to consumers not continually asking if there are any more messages to be delivered. > The trade off here is there would be some increase in latency. -- 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

17 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2006