February 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JGRP-699) NAKACK: merging of digests is incorrect

by Bela Ban (JIRA)

NAKACK: merging of digests is incorrect --------------------------------------- Key: JGRP-699 URL: http://jira.jboss.com/jira/browse/JGRP-699 Project: JGroups Issue Type: Bug Affects Versions: 2.4.2, 2.4.1 SP4, 2.4.1 SP3, 2.4.1 SP2, 2.4.1 SP1, 2.4.1, 2.4 Reporter: Bela Ban Assigned To: Bela Ban Fix For: 2.4.3 The merge view is: 2008-02-20 23:49:30,872 DEBUG [org.jgroups.protocols.pbcast.GMS] view=MergeView::[172.16.172.233:19382|3] [172.16.172.233:19382, 172.16.172.234:19382], subgroups=[[172.16.172.233:19382|1] [172.16.172.233:19382, 172.16.172.234:19382], [172.16.172.234:19382|2] [172.16.172.234:19382]], digest=172.16.172.233:19382: [557 : 564(564)], 172.16.172.234:19382: [901 : 923 (923)] So, the digest for 234:19382 is 901-923, which means 234 could actually satisfy the retransmit request below. However, when the xmit req arrives: 2008-02-20 23:49:32,004 ERROR [org.jgroups.protocols.pbcast.NAKACK] (requester=172.16.172.233:19382, local_addr=172.16.172.234:19382) message 172.16.172.234:19382::919 not found in retransmission table of 172.16.172.233:19382:[557 : 565 (565)] 172.16.172.234:19382: [921 : 924 (924) (size=3, missing=0, highest stability=921)] , we can see that now the digest for 234:19382 is 921-924. In 2.4, the merge algorith for digests (NAKACK.mergeDigest()) takes the *max* of the low seqnos (MAX(901,921), in 2.5 and higher we don't touch an existing entry, so the digest for 234:19382 would still be 901-923, and we could therefore satisfy the merge request. SOLUTION: use the solution implemented in 2.5 and higher: don't set digests for existing entries. -- 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, 5 months

1
8
0 / 0

[JBoss JIRA] Commented: (JBAS-1808) Expose PreparedStatementCache via JMX

by Vicky Kak (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-1808?page=comments#action_12400688 ] Vicky Kak commented on JBAS-1808: --------------------------------- Dimitiris , the changes are made in the Branch_4_2 . > Expose PreparedStatementCache via JMX > ------------------------------------- > > Key: JBAS-1808 > URL: http://jira.jboss.com/jira/browse/JBAS-1808 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JCA service > Reporter: Scott M Stark > Assigned To: Vicky Kak > Priority: Minor > Fix For: JBossAS-5.1.0.CR1 > > > The PreparedStatementCache cache in the JCA layer has no exposure via jmx. Info like the min, max, avg, etc. number of prepared statements are in the cache would be useful. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-5030) Upgrade jboss-ha-client.jar to 1.0.0.GA

by Brian Stansberry (JIRA)

Upgrade jboss-ha-client.jar to 1.0.0.GA --------------------------------------- Key: JBAS-5030 URL: http://jira.jboss.com/jira/browse/JBAS-5030 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 Need a GA 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

18 years, 5 months

2
6
0 / 0

[JBoss JIRA] Created: (JBREM-897) Provide a mechanism for configuring client and server interceptors

by David Lloyd (JIRA)

Provide a mechanism for configuring client and server interceptors ------------------------------------------------------------------ Key: JBREM-897 URL: http://jira.jboss.com/jira/browse/JBREM-897 Project: JBoss Remoting Issue Type: Task Security Level: Public (Everyone can see) Reporter: David Lloyd Fix For: Remoting 3 M2 -- 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, 5 months

1
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1762) Myfaces Example

by Wesley Hales (JIRA)

Myfaces Example --------------- Key: JBPORTAL-1762 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1762 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Wesley Hales Assigned To: Wesley Hales -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1760) JSR-301 JSF Portlet Bridge Integration

by Wesley Hales (JIRA)

JSR-301 JSF Portlet Bridge Integration -------------------------------------- Key: JBPORTAL-1760 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1760 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Reporter: Wesley Hales Assigned To: Wesley Hales Integrate Implementation of 301 spec into JBP. -- 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, 5 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3996) Web Console AppletBrowser hangs browser because of missing Logger

by teej TJ (JIRA)

Web Console AppletBrowser hangs browser because of missing Logger ----------------------------------------------------------------- Key: JBAS-3996 URL: http://jira.jboss.com/jira/browse/JBAS-3996 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Web Console Affects Versions: JBossAS-5.0.0.Beta1 Environment: Ubuntu Edgy Eft 6.10 Linux 2.6.17-10-generic #2 SMP Tue Dec 5 22:28:26 UTC 2006 i686 GNU/Linux Firefox 2.0.0.1 Sun Java 1.5.0_08 Reporter: teej TJ Assigned To: Darran Lofthouse Firefox hangs and has to be killed when the JBoss Web Console link is followed on the JBoss Management service (http://localhost:8080/). The hang is caused by a NoClassDefFoundError exception whilst attempting to load AppletBrowser in applet.jar. This appears to be another instance of the use of Logger where it has been removed (as in the shutdown.sh script bugs JBAS-3560). org.jboss.console.remote.Util: private static org.jboss.logging.Logger log = org.jboss.logging.Logger.getLogger(Util.class); --- Java Console Report --- basic: Loading applet ... basic: Initializing applet ... basic: Starting applet ... network: Connecting http://10.254.251.2:8080/web-console/applet.jar with proxy=DIRECT network: Connecting http://10.254.251.2:8080/web-console/applet.jar with cookie "JSESSIONID=239D5221F10892A8D9A66F83680E589C" basic: Loading http://10.254.251.2:8080/web-console/applet.jar from cache basic: No certificate info, this is unsigned JAR file. http://10.254.251.2:8080/web-console/Invoker network: Connecting http://10.254.251.2:8080/web-console/org/jboss/logging/Logger.class with proxy=DIRECT network: Connecting http://10.254.251.2:8080/web-console/org/jboss/logging/Logger.class with cookie "JSESSIONID=239D5221F10892A8D9A66F83680E589C" java.lang.NoClassDefFoundError: org/jboss/logging/Logger at org.jboss.console.remote.Util.<clinit>(Util.java:33) at org.jboss.console.remote.AppletRemoteMBeanInvoker.invoke(AppletRemoteMBeanInvoker.java:64) at org.jboss.console.navtree.ConsoleTreeModel.loadTree(ConsoleTreeModel.java:118) at org.jboss.console.navtree.ConsoleTreeModel.<init>(ConsoleTreeModel.java:73) at org.jboss.console.navtree.AdminTreeBrowser.<init>(AdminTreeBrowser.java:77) at org.jboss.console.navtree.AppletBrowser.start(AppletBrowser.java:65) at sun.applet.AppletPanel.run(AppletPanel.java:418) at java.lang.Thread.run(Thread.java:595) basic: Exception: java.lang.NoClassDefFoundError: org/jboss/logging/Logger java.lang.NoClassDefFoundError: org/jboss/logging/Logger at org.jboss.console.remote.Util.<clinit>(Util.java:33) at org.jboss.console.remote.AppletRemoteMBeanInvoker.invoke(AppletRemoteMBeanInvoker.java:64) at org.jboss.console.navtree.ConsoleTreeModel.loadTree(ConsoleTreeModel.java:118) at org.jboss.console.navtree.ConsoleTreeModel.<init>(ConsoleTreeModel.java:73) at org.jboss.console.navtree.AdminTreeBrowser.<init>(AdminTreeBrowser.java:77) at org.jboss.console.navtree.AppletBrowser.start(AppletBrowser.java:65) at sun.applet.AppletPanel.run(AppletPanel.java:418) at java.lang.Thread.run(Thread.java:595) -- 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, 5 months

6
5
0 / 0

[JBoss JIRA] Created: (JBAS-3857) shutdown.sh does not work

by Ovidiu Feodorov (JIRA)

shutdown.sh does not work ------------------------- Key: JBAS-3857 URL: http://jira.jboss.com/jira/browse/JBAS-3857 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Other Affects Versions: JBossAS-5.0.0.Beta1 Reporter: Ovidiu Feodorov $ ./shutdown.sh -S Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/system/server/ServerImplMBean at org.jboss.Shutdown.main(Shutdown.java:116) -- 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, 5 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-5151) Resource loading fails for WEB-INF/xyz.txt

by Heiko Braun (JIRA)

Resource loading fails for WEB-INF/xyz.txt ------------------------------------------ Key: JBAS-5151 URL: http://jira.jboss.com/jira/browse/JBAS-5151 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: ClassLoading Reporter: Heiko Braun Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.Beta4 Heiko Braun wrote: > With recent versions it seems that loading resources from WEB-INF > seems to be broken for a lot of WS tests. Have there been any > classloader changes that may explain this? -- 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, 5 months

5
19
0 / 0

[JBoss JIRA] Updated: (JBAS-2577) isolating Hibernate as an internal impl detail

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2577?page=all ] Dimitris Andreadis updated JBAS-2577: ------------------------------------- Component/s: Hibernate service > isolating Hibernate as an internal impl detail > ---------------------------------------------- > > Key: JBAS-2577 > URL: http://jira.jboss.com/jira/browse/JBAS-2577 > Project: JBoss Application Server > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Hibernate service > Reporter: Steve Ebersole > Assigned To: Steve Ebersole > Fix For: JBossAS-5.0.0.CR1 > > > Currently Hibernate is used within JBossAS for EJB3 as well as the Hibernate-intg code, with plans/discussions to expand usage to JBoss Messaging and JBossMQ. This represents Hibernate usage as an internal implementation detail > Additionally, Hibernate is also used within JBossAS by user applications. This represents Hibernate usage as a deployment detail. > Currently, the two are not isolated from each other. Thus, a user attempting to bundle Hibernate with their application is actually using the Hibernate bundled with EJB3 and/or the integration code. This can cause problems when we have internal usage and external usage needing to rely on different releases of Hibernate. > Need to devise a scheme to isolate the internal usages of Hibernate. Two potential solutions: > 1) source-level import and package renaming of Hibernate code (i.e. org.jboss.hibernate) > 2) some form of classloader isolation -- 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, 5 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 February 2008