August 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (EJBTHREE-326) Some queries are slower when executed in JBoss EJB3

by Andreas Zimmer (JIRA)

[ http://jira.jboss.com/jira/browse/EJBTHREE-326?page=comments#action_12340486 ] Andreas Zimmer commented on EJBTHREE-326: ----------------------------------------- This may be the same as described in the following bug: http://jira.jboss.com/jira/browse/EJBTHREE-649?page=comments#action_12340482 We've seen some evidence that the problem is related to the FLUSH MODE. The more detailed information in this case as well as in the referenced forum thread may help during analysis of this problem . > Some queries are slower when executed in JBoss EJB3 > --------------------------------------------------- > > Key: EJBTHREE-326 > URL: http://jira.jboss.com/jira/browse/EJBTHREE-326 > Project: EJB 3.0 > Issue Type: Bug > Components: EJB3 Extensions > Affects Versions: EJB 3.0 RC3 > Environment: JBoss4.0.3 rc2 > Reporter: J-C jc > Assigned To: Emmanuel Bernard > > When a lot of objects have been resolved in the current transaction, queries becomes slow. see http://www.jboss.com/index.html?module=bb&op=viewtopic&t=68954&postdays=0... for more details. > More generally, it seems that EJB3 persistence access is slower in JBoss EJB3 compare to access in EJB3 outside of JBoss: > see http://forum.hibernate.org/viewtopic.php?t=948850 -- 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] Created: (EJBTHREE-676) Upgrade javax.xml.bin api to version 2.0

by Wonne Keysers (JIRA)

Upgrade javax.xml.bin api to version 2.0 ---------------------------------------- Key: EJBTHREE-676 URL: http://jira.jboss.com/jira/browse/EJBTHREE-676 Project: EJB 3.0 Issue Type: Feature Request Components: EJB3 Extensions Affects Versions: EJB 3.0 RC8 - FD, EJB 3.0 RC7 - FD, EJB 3.0 RC6 - PFD Reporter: Wonne Keysers Using the Embeddable EJB3 jars to compile our EJB3 project. In order to be able to use JAXB 2.0, we had to remove the javax.xml.bind.* packages from jboss-ejb3-all.jar. Would it be possible to extract the javax.xml.bind package from the ejb3 jars such that it can be replaced or upgrade the JAXB classes to JAXB 2.0? Thanks -- 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] Created: (JBMESSAGING-481) Implement a round robin routing

by Tim Fox (JIRA)

Implement a round robin routing ------------------------------- Key: JBMESSAGING-481 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-481 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox The current implementation of PointToPointRouter always favours the first Receiver. In the case of message batching this can cause starvation of receivers if there are not many messages in the queue/subscription (since earlier Receives grab all the messages) This can result in reduced throughput. We should implement a round robin routing strategy and make it the default for queues or subscriptions with multiple consumers. -- 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
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-479) Implement iteration

by Tim Fox (JIRA)

Implement iteration ------------------- Key: JBMESSAGING-479 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-479 Project: JBoss Messaging Issue Type: Sub-task Reporter: Tim Fox Assigned To: Tim Fox -- 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
3
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-275) Move Selector processing IN the Channel

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-275?page=comments#action_12... ] Tim Fox commented on JBMESSAGING-275: ------------------------------------- I have split the work for this task into two subtasks- One to to implement the iteration in memory (the main part) The other to implement the indexes and make sure it works with paging. > Move Selector processing IN the Channel > --------------------------------------- > > Key: JBMESSAGING-275 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-275 > Project: JBoss Messaging > Issue Type: Task > Components: Messaging Core > Reporter: Ovidiu Feodorov > Assigned To: Tim Fox > Priority: Critical > Fix For: 1.2.0.Alpha1 > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Currently, a consumer "arrests" a message that is being handled to it and doesn't match the Selector. That means it returns an active Delivery for it, but it doesn't forward the message to the client. This is because the consumer needs to be able to receiver further messages coming after the non-matching message, and that may potentially match the selector. > This is a poor solution that doesn't scale. We may end up with lots of non-matching messages being "arrested" by a consumer, while they could just be simply returned to the channel and forwarded to other potential consumers. > A possible (right) approach is to move selector processing in the Channel, so the message is not even handled to the non-accepting cosumer. Review this and refactor. -- 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] Created: (EJBTHREE-675) jboss-ejb3.jar: Manifest.mf does not contain the right implemation version

by J-C jc (JIRA)

jboss-ejb3.jar: Manifest.mf does not contain the right implemation version -------------------------------------------------------------------------- Key: EJBTHREE-675 URL: http://jira.jboss.com/jira/browse/EJBTHREE-675 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC8 - FD Environment: NA Reporter: J-C jc Priority: Minor Manifest.mf in jar jboss-ejb3.jar has a implementation version to RC7, in fact it is a RC8. -- 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] Created: (JBIDE-345) Error: "Cannot get value for expression '#{XXX.pageTitle}'"

by Kip (JIRA)

Error: "Cannot get value for expression '#{XXX.pageTitle}'" ----------------------------------------------------------- Key: JBIDE-345 URL: http://jira.jboss.com/jira/browse/JBIDE-345 Project: JBoss IDE Issue Type: Bug Environment: WinXP Reporter: Kip Using JBossIDE-200608021549-nightly-ALL.zip. Used HibernateConsole to generate Seam files. When I access /seamapp and click "Search for existing XXX records", I get this error: Cannot get value for expression '#{XXX.pageTitle}' Per the forum discussion (http://forum.hibernate.org/viewtopic.php?p=2314747&sid=fc624587d62db8641c...), the error appears to be in selector.java.ftl. Fix is probably to change @${pojo.importType("org.jboss.seam.annotations.In")} private transient ${pojo.importType("java.util.ResourceBundle")} resourceBundle; to @${pojo.importType("org.jboss.seam.annotations.In")}(create=true) private transient ${pojo.importType("java.util.ResourceBundle")} resourceBundle; -- 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

2
1
0 / 0

[JBoss JIRA] Closed: (JBAS-3004) Use a combination of FD and FD_SOCK in the default JGroups protocol stack.

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3004?page=all ] Brian Stansberry closed JBAS-3004. ---------------------------------- Resolution: Done Done for cluster-service.xml and tcX-cluster.sar; separate issue for the EJB3 caches. For FD I used a 20 sec timeout with 5 tries; total is 1 min 40 secs which I think is long enough to prevent false suspicions while not so long that FD_SOCK failures are ignored for long periods. > Use a combination of FD and FD_SOCK in the default JGroups protocol stack. > -------------------------------------------------------------------------- > > Key: JBAS-3004 > URL: http://jira.jboss.com/jira/browse/JBAS-3004 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Clustering > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.5.CR1 > > > FD_SOCK to promptly detect most issues. FD with a long (say 2 min) timeout as a backup to detect things like machine/switch crashes where FD_SOCK isn't aware of the TCP connection failure. Long timeout avoids false suspicions. -- 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] Created: (JBSEAM-326) Dynamic view-id in Pageflow

by John Conner (JIRA)

Dynamic view-id in Pageflow --------------------------- Key: JBSEAM-326 URL: http://jira.jboss.com/jira/browse/JBSEAM-326 Project: JBoss Seam Issue Type: Feature Request Components: BPM Affects Versions: 1.1 Environment: seam cvs as of 8/2/2006 Reporter: John Conner I have a need where I would like to have an el expression in the view-id of a pageflow. I've looked a bit at themes; and while I might be able to do what I want by replacing the template.xhtml dynamically, I don't (at least initial) like indirection. I believe the patch for this functionality is reletively trivial. Altough, I very well could have missed something. Basically, I modified the Page.getViewId() method to evaulate the value returned and replace any el expressions. I also modified the Number Guess example to use this feature. I have attached an initial patch as a proof of concept if it is of any interest to the Seam developers. -- JC -- 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
2
0 / 0

[JBoss JIRA] Resolved: (JBREM-218) investigate why jrunit report on cruisecontrol inaccurate

by Tom Elrod (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-218?page=all ] Tom Elrod resolved JBREM-218. ------------------------------ Resolution: Done > investigate why jrunit report on cruisecontrol inaccurate > --------------------------------------------------------- > > Key: JBREM-218 > URL: http://jira.jboss.com/jira/browse/JBREM-218 > Project: JBoss Remoting > Issue Type: Task > Components: general > Affects Versions: 1.4.0 beta > Reporter: Tom Elrod > Assigned To: Tom Elrod > Priority: Minor > Fix For: 2.0.0.CR1 (Boon) > > > http://cruisecontrol.jboss.com/cc/artifacts/jboss-remoting-testsuite-1.5/... (and several previous ones) shows that the socket transport tests are extremely slow. This should not be the case (local performance tests using same ant build target as cruisecontrol consistenly shows is the fastest). -- 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