August 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBAS-1636) Don't try to delist a track-connection-by-tx connection that is already broken and has been closed.

by Thomas Saxtoft (JIRA)

[ https://jira.jboss.org/browse/JBAS-1636?page=com.atlassian.jira.plugin.sy... ] Thomas Saxtoft commented on JBAS-1636: -------------------------------------- Well I just found that the server reports 4.3.0.GA_CP07_EAP, that's why I thought it was the version number. Then I downloaded the source code for that version and verified that it has not been fixed. You have to be aware that the noise in the log, raises questions to our support from our customers. So I still think it would be good to weed out this sort of log statements. > Don't try to delist a track-connection-by-tx connection that is already broken and has been closed. > --------------------------------------------------------------------------------------------------- > > Key: JBAS-1636 > URL: https://jira.jboss.org/browse/JBAS-1636 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: JBossAS-3.2.7 Final, JBossAS-4.0.1 Final, JBossAS-4.0.1 SP1, JBossAS-4.0.2RC1 > Reporter: Adrian Brock > Assignee: Adrian Brock > Fix For: JBossAS-4.0.2 Final > > > The transaction synchronization that returns track-connection-by-tx > should not try to process connections that are broken and have already been > closed. > This leads to a spurious error message: > org.jboss.resource.connectionmanager.TxConnectionManager - The re is something wrong with the pooling? > java.lang.IllegalStateException: afterCompletion called with wrong tx! > Expected: null, actual: TransactionImpl:XidImpl [...] > at > org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventLi > stener$TxRemover.afterCompletion(TxConnectio > nManager.java:588) > The error message does not cause problems but it can be noisy/disconcerting in the logs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-8298) WeldBootstrap class is leaked through application CL

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8298?page=com.atlassian.jira.plugin.sy... ] Pete Muir reassigned JBAS-8298: ------------------------------- Assignee: David Allen David, just want to make sure you have this on your radar. > WeldBootstrap class is leaked through application CL > ---------------------------------------------------- > > Key: JBAS-8298 > URL: https://jira.jboss.org/browse/JBAS-8298 > Project: JBoss Application Server > Issue Type: Bug > Components: Weld/CDI > Reporter: David Allen > Assignee: David Allen > > The WeldBootstrap class is being added as a dependency in the JBoss AS dependency controller. Since this class is loaded within a deployment's classloader, every deployment CL is leaked. > I will be working on identifying where this dependency is generated and try to identify a fix for it. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-8284) SFSB proxies not serializable in JBoss AS

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8284?page=com.atlassian.jira.plugin.sy... ] Pete Muir updated JBAS-8284: ---------------------------- Comment: was deleted (was: I think this might be an duplicate of JBAS-8291) > SFSB proxies not serializable in JBoss AS > ----------------------------------------- > > Key: JBAS-8284 > URL: https://jira.jboss.org/browse/JBAS-8284 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Weld/CDI > Reporter: David Allen > Fix For: 6.0.0.CR1 > > > The deserialization of a client proxy for a stateful session bean fails in JBoss AS. It appears to be serializing Microkernel classes in the object graph which are naturally not available to the classloader of the test application during deserialization. > This is demonstrated by test org.jboss.jsr299.tck.tests.implementation.enterprise.lifecycle.EnterpriseBeanLifecycleTest.testSerializeSFSB(). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-8291) EJB unable to load bean for before transaction completion observer

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8291?page=com.atlassian.jira.plugin.sy... ] Pete Muir closed JBAS-8291. --------------------------- Assignee: Pete Muir Fix Version/s: (was: 6.0.0.CR1) Resolution: Done Test has been removed from CDI TCK in 1.0.2.CR2 > EJB unable to load bean for before transaction completion observer > ------------------------------------------------------------------ > > Key: JBAS-8291 > URL: https://jira.jboss.org/browse/JBAS-8291 > Project: JBoss Application Server > Issue Type: Bug > Components: Weld/CDI > Reporter: Pete Muir > Assignee: Pete Muir > > See org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest.testBeforeTransactionCompletionObserver() -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBAS-8291) EJB unable to load bean for before transaction completion observer

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8291?page=com.atlassian.jira.plugin.sy... ] Pete Muir reopened JBAS-8291: ----------------------------- > EJB unable to load bean for before transaction completion observer > ------------------------------------------------------------------ > > Key: JBAS-8291 > URL: https://jira.jboss.org/browse/JBAS-8291 > Project: JBoss Application Server > Issue Type: Bug > Components: Weld/CDI > Reporter: Pete Muir > Assignee: Pete Muir > > See org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest.testBeforeTransactionCompletionObserver() -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-8291) EJB unable to load bean for before transaction completion observer

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8291?page=com.atlassian.jira.plugin.sy... ] Pete Muir closed JBAS-8291. --------------------------- Resolution: Out of Date > EJB unable to load bean for before transaction completion observer > ------------------------------------------------------------------ > > Key: JBAS-8291 > URL: https://jira.jboss.org/browse/JBAS-8291 > Project: JBoss Application Server > Issue Type: Bug > Components: Weld/CDI > Reporter: Pete Muir > Assignee: Pete Muir > > See org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest.testBeforeTransactionCompletionObserver() -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Commented: (JBAS-8217) Simple war based ejb deployment does not work on JBoss 6.0M3

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8217?page=com.atlassian.jira.plugin.sy... ] Pete Muir commented on JBAS-8217: --------------------------------- Please try M4 Vladimir, we made substantial advances there around CDI/EJB 3.1 integration. > Simple war based ejb deployment does not work on JBoss 6.0M3 > ------------------------------------------------------------- > > Key: JBAS-8217 > URL: https://jira.jboss.org/browse/JBAS-8217 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Weld/CDI > Environment: Snow Leopard 10.6.3, Java 6. > Reporter: Vladimir Blagojevic > Assignee: Marius Bogoevici > Fix For: 6.0.0.Final > > Attachments: weldint-64.zip > > > Have a simple war app with pojo ejb, trying to inject ejb field into a managed bean which is in turn accessed from a facelet. @EJB and @Inject dot not work on JBoss 6.0 M3. Attaching minimal example app. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBAS-8093) Weld should visibly log when /WEB-INF/beans.xml is not found.

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8093?page=com.atlassian.jira.plugin.sy... ] Pete Muir reassigned JBAS-8093: ------------------------------- Assignee: Jason T. Greene Underlying issue is that if CDI annotations are present but beans.xml isn't then the AS should complain. However I don't think the AS can do this right now? Maybe in AS7? Jason, could you let me know what the best course of action is. > Weld should visibly log when /WEB-INF/beans.xml is not found. > ------------------------------------------------------------- > > Key: JBAS-8093 > URL: https://jira.jboss.org/browse/JBAS-8093 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Weld/CDI > Reporter: Lincoln Baxter III > Assignee: Jason T. Greene > > An INFO or WARNING level log message must be displayed when loading a web-application where /WEB-INF/beans.xml is missing. > "/WEB-INF/beans.xml is not present - Beans in WAR " +warName+ " will not be loaded." > The user needs to know this because weld is making an important decision. Also, a common pitfall, defining EJBs with @Injected dependencies will break because the EJB's are discovered, @Injection is attempted, but fails because no other beans were loaded. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-8315) Make Weld docs available for JBoss AS 6

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8315?page=com.atlassian.jira.plugin.sy... ] Pete Muir closed JBAS-8315. --------------------------- Assignee: Pete Muir (was: Dan Allen) Resolution: Duplicate Issue > Make Weld docs available for JBoss AS 6 > --------------------------------------- > > Key: JBAS-8315 > URL: https://jira.jboss.org/browse/JBAS-8315 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Weld/CDI > Reporter: Pete Muir > Assignee: Pete Muir > Priority: Critical > > Magnolia is the tool we use to build out the JBoss community site. Please take a moment and go to http://www.jboss.org/author. > Username: ********** > Password: ********** > Scroll down and open jbossas --> docs --> 6-x > Highlight 6-x and press the "Open page..." button at the bottom. The main AS6 docs page will open in another tab or window. > From here you can see how AS6 documentation will be broken up into "Core" and "Component". Click on the "JavaServer Faces (JSF)" link You'll get an idea of what you can do with your section. > As you can see, we want to provide something beyond the DocBook documentation we've had in the past. We want a developer to be able to come to the docs section and find everything he might need to work with a particular part of AS6, including spec info, javadoc, sample code, and links to other info. > Of course, we don't want to fork the stuff we already have but we also need to recognize that developers want to use AS6 as a single product and they come to AS6 with an "AS6" mindset. So they are thinking, "How do I use the EJB features built into AS6?" or "How do I use the Weld framework built into AS6?". We need to provide documentation that answers those questions from an AS6 point of view. But I'm using the word "documentation" in a loose sense. It doesn't have to be a single document. The aggregation of AS6 information is done with Magnolia and not necessarily with a single DocBook monograph. > I am assuming that most components will have at least some AS6-specific content that needs to go somewhere. If it's possible/practical to use Maven profiles to pull in special content and create an AS6 version of a document then that would be best. If not, then AS6-specific content could be put into its own small document. The rest can be referenced with links to the component's project documentation. > As for where the doco lives in what part of SVN, I don't think that it really matters. I like the idea that each component team is responsible for handling their section however is most practical for them. I just want to make sure that at the end of the day an AS6 user has everything he needs in a way that is easy to find and understand. > Action items for you: > * Take a look at http://jboss.org/help/projectpageguide.html to learn about Magnolia. > * Find the section on Weld and start building out the page(s) > * Work out how best to incorporate the Weld ref guide into the JBoss AS docs > - remove irrelevant sections > - apply JBoss AS styling -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-8283) Context not propagated to event observer

by Pete Muir (JIRA)

[ https://jira.jboss.org/browse/JBAS-8283?page=com.atlassian.jira.plugin.sy... ] Pete Muir closed JBAS-8283. --------------------------- Assignee: Pete Muir Fix Version/s: (was: 6.0.0.CR1) Resolution: Out of Date Tests are removed from CDI TCK. > Context not propagated to event observer > ---------------------------------------- > > Key: JBAS-8283 > URL: https://jira.jboss.org/browse/JBAS-8283 > Project: JBoss Application Server > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Weld/CDI > Reporter: Pete Muir > Assignee: Pete Muir > > See org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest.testTransactionalObserverNotifiedImmediatelyWhenNoTransactionInProgress() -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 11 months

1
0
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 August 2010