November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCACHE-1168) Sometimes aquired locks are not released

by Jacek Halat (JIRA)

Sometimes aquired locks are not released ---------------------------------------- Key: JBCACHE-1168 URL: http://jira.jboss.com/jira/browse/JBCACHE-1168 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: PojoCache Affects Versions: 1.4.1.SP4 Environment: Windows XP, jrockit90_150_06 Solaris 10 Reporter: Jacek Halat Assigned To: Jason T. Greene Attachments: TransactionStormTest.java Sometimes under heavy load acquired locks are not released - node is locked forever. Only what can we do is stop/start cache. Main loop: while (true) { for (int x = 0; x < 2; x++) { WorkThread t = new WorkThread(x == 1); threads.add(t); t.start(); } for (WorkThread separateThread : threads) { separateThread.join(); if (separateThread.getException() != null) { //separateThread.getException().getMessage(); } } int locksNum = getNumberOfLocksHeld(); // System.out.println("Locks="+locksNum); // checkpoint if (cache.getNumberOfLocksHeld()>0){ System.out.println("ERROR, locks="+locksNum); doDomethingOnCache(1); } assertEquals(0, locksNum); } Exception - after //checkpoint line numberOfLocks is grater than 0! JUnit is provided to this issue, but this error is nondeterministic - sometimes fails after 5 seconds and another time after 20 minutes. -- 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, 1 month

3
13
0 / 0

[JBoss JIRA] Created: (JBCACHE-1183) Acquired WL lock could be not released after async transaction rolback

by Jacek Halat (JIRA)

Acquired WL lock could be not released after async transaction rolback ---------------------------------------------------------------------- Key: JBCACHE-1183 URL: http://jira.jboss.com/jira/browse/JBCACHE-1183 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Environment: WindowsXP, jdk150_06 Reporter: Jacek Halat Assigned To: Manik Surtani In some cases on weblogic (and other servers where transaction manager with async transaction rollback after timeout is used) acquired WL can be not released. Only way to release lock is stop/start cche again. -- 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, 1 month

2
9
0 / 0

[JBoss JIRA] Created: (EJBTHREE-748) The implementation of equals() in org.jboss.ejb3.ProxyUtils.handleCallLocally() throws a NPE when being passed a null argument.

by Nicolas Bielza (JIRA)

The implementation of equals() in org.jboss.ejb3.ProxyUtils.handleCallLocally() throws a NPE when being passed a null argument. ------------------------------------------------------------------------------------------------------------------------------- Key: EJBTHREE-748 URL: http://jira.jboss.com/jira/browse/EJBTHREE-748 Project: EJB 3.0 Issue Type: Bug Environment: Embedded EJB3 container Reporter: Nicolas Bielza When looking up an entity bean, we get a proxy which implements equals() in a broken way: Here's an example: // Proxy NPE test: InitialContext ctx = new InitialContext(); Manager m = (Manager)ctx.lookup("ManagerAction/local"); try { if(m != null) { m.equals(null); } System.err.println("What bug ???"); } catch(NullPointerException e) { System.err.println("ProxyUtils NPE bug detected."); e.printStackTrace(); } And the output: ProxyUtils NPE bug detected. java.lang.NullPointerException at org.jboss.ejb3.ProxyUtils.handleCallLocally(ProxyUtils.java:156) at org.jboss.ejb3.ProxyUtils.handleCallLocally(ProxyUtils.java:137) at org.jboss.ejb3.stateful.StatefulLocalProxy.invoke(StatefulLocalProxy.java:92) at $Proxy34.equals(Unknown Source) at com.alligacom.nett.NetTransferAdminInterface.<init>(NetTransferAdminInterface.java:49) at com.alligacom.nett.NetTransferAdminInterface.main(NetTransferAdminI nterface.java:87) The incriminated line (156) in ProxyUtils is: return new Boolean(ih.toString().equals(args[0].toString())); and should be: return new Boolean(args[0] == null ? false : ih.toString().equals(args[0].toString())); -- 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, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-220) Support for nested properties

by Trustin Lee (JIRA)

Support for nested properties ----------------------------- Key: JBMICROCONT-220 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-220 Project: JBoss MicroContainer Issue Type: Feature Request Environment: N/A Reporter: Trustin Lee Priority: Minor Support for nested properties make beans XML more concise and easy to understand. Before: <bean name="beanX" ...> ... </bean> <bean name="propA" ...> <constructor><factory bean="beanX" method="getPropA"/></constructor> <property name="propB">...</property> </bean> <bean name="beanY" ...> <property name="propC"><inject bean="propA" property="propB"/></property> </bean> After: <bean name="beanX" ...> <property name="propA.propB">...</property> </bean> <bean name="beanY" ...>  <property name="propC"><inject bean="beanX" property="propA.propB"/></property>  <property name="propC ref="beanX.propA.propB"/> </bean> -- 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, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-4928) Compare AS library names between 4.2.x & 5.0.x

by Dimitris Andreadis (JIRA)

Compare AS library names between 4.2.x & 5.0.x ----------------------------------------------- Key: JBAS-4928 URL: http://jira.jboss.com/jira/browse/JBAS-4928 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Build System Reporter: Dimitris Andreadis Assigned To: Rajesh Rajasekaran Fix For: JBossAS-5.0.0.CR1 Check how similar libraries are deployed under different names in server/xxx/lib between 4.2.x & 5.0.x The names shouldn't change, unless there is a good reason for that. E.g. lib/servlet-api.jar in 4.2.x lib/javax.servlet.jar in 5.0.x -- 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, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4971) org.jboss.test.cmp2.audit.test.AuditUnitTestCase

by Dimitris Andreadis (JIRA)

org.jboss.test.cmp2.audit.test.AuditUnitTestCase ------------------------------------------------ Key: JBAS-4971 URL: http://jira.jboss.com/jira/browse/JBAS-4971 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: CMP service Reporter: Dimitris Andreadis Assigned To: Anil Saldhana Fix For: JBossAS-5.0.0.Beta3 Looks like a security setup issue: http://hudson.qa.jboss.com/hudson/view/JBoss%20AS/job/JBoss-AS-5.0.x-Test... -- 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, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-3450) Fix org.jboss.test.webservice.jbws309.JBWS309TestCase running under JACC

by Anil Saldhana (JIRA)

Fix org.jboss.test.webservice.jbws309.JBWS309TestCase running under JACC ------------------------------------------------------------------------ Key: JBAS-3450 URL: http://jira.jboss.com/jira/browse/JBAS-3450 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Security, Web Services Reporter: Anil Saldhana Assigned To: Thomas Diesler Fix For: JBossAS-5.0.0.Beta EJBContext.isCallerInRole checks now goes through the JACC layer. (http://jira.jboss.com/jira/browse/JBAS-2661) So there may be changes needed in the ejb-jar.xml wrt security role-refs -- 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, 1 month

5
4
0 / 0

[JBoss JIRA] Created: (JBAS-4228) Preferred server HASingletonElectionPolicy

by Brian Stansberry (JIRA)

Preferred server HASingletonElectionPolicy ------------------------------------------ Key: JBAS-4228 URL: http://jira.jboss.com/jira/browse/JBAS-4228 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry An HASingletonElectionPolicy impl that allows configurable specification of a "preferred server". If the preferred server is running, it's the master, otherwise the master is deterministically selected based on the standard policy. 1) Determine if you are the preferred server by comparing you node name to the configured "preferred server" value. 2) When you get a view change, check if preferred server is in the view. If yes, and you're the preferred server, become master, otherwise don't. If preferred server is not in view, fall back on the base policy. Have to make sure the mechanism of identifying and matching the "preferred server" is bullet proof (machine names vs. configuration-specified names vs. IP addresses, plus ports.) -- 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, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBRULES-1110) Rules with 'From' condition with another not using From causes problem

by Arjun Dhar (JIRA)

Rules with 'From' condition with another not using From causes problem ---------------------------------------------------------------------- Key: JBRULES-1110 URL: http://jira.jboss.com/jira/browse/JBRULES-1110 Project: JBoss Rules Issue Type: Bug Security Level: Public (Everyone can see) Components: Decision tables, Reteoo Affects Versions: 4.0.0.GA Environment: Any Reporter: Arjun Dhar Assigned To: Mark Proctor Test case: Write a Rule that uses a From clause and on another object does not use a from clause: example: #From row number: 28 rule "Rules_28" when cntct: Contact(initialized==true) config: BooleanConfiguration(value==true) from meta.getConfiguration(cntct.getClient(), "Param1") pref: Relation(contact==cntct, type=="old") or (eval(false==true) and not Relation(contact==cntct, type=="old")) then System.out.println("Fired 28"); end If All 3 are true: 1. Delete Condition 2 --> Rule fires 2. Delete COnditon 3 (But keep 2) --> Rule fires 3. Keep 2 & 3 (with 1) --> Rule does not fire Whats strage is that conditon 1 does not use from and it works with condition 2 without any problem, but when 2 & 3 are there together the rule does not work. Please see if it is a bug -- 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, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-4642) Fix org.jboss.test.xml.mbeanserver.XMBean2UnitTestCase

by Dimitris Andreadis (JIRA)

Fix org.jboss.test.xml.mbeanserver.XMBean2UnitTestCase ------------------------------------------------------ Key: JBAS-4642 URL: http://jira.jboss.com/jira/browse/JBAS-4642 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.Beta3 The error message doesn't look very helpful: testJavaBeanSchemaInitializerInterceptor Failure description expected:<...eanSchemaInitializer[ ]> but was:<...eanSchemaInitializer[]> junit.framework.ComparisonFailure: description expected:<...eanSchemaInitializer[ ]> but was:<...eanSchemaInitializer[]> at org.jboss.test.xml.mbeanserver.XMBean2UnitTestCase.testJavaBeanSchemaInitializerInterceptor(XMBean2UnitTestCase.java:129) log snipet ... 2007-08-28 20:02:49,906 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true 2007-08-28 20:02:49,906 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl@c79809, isNamespaceAware: true, isValidating: true, isXIncludeAware: true 2007-08-28 20:02:49,921 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Created parser: org.apache.xerces.jaxp.SAXParserImpl@1ce784b, isNamespaceAware: true, isValidating: true, isXIncludeAware: true 2007-08-28 20:02:49,921 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/validation set to: true 2007-08-28 20:02:49,921 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://xml.org/sax/features/namespaces set to: true 2007-08-28 20:02:49,921 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] http://apache.org/xml/features/validation/dynamic set to: true 2007-08-28 20:02:49,921 DEBUG [org.jboss.xb.binding.parser.sax.SaxJBossXBParser] Using parser: org.apache.xerces.jaxp.SAXParserImpl@1ce784b, isNamespaceAware: true, isValidating: true, isXIncludeAware: true 2007-08-28 20:02:49,968 DEBUG [org.jboss.mx.metadata.xb.DescriptorSupportContainer] addChild, {urn:jboss-test:xmbean:2.0}interceptors,org.jboss.mx.metadata.xb.InterceptorsHolder@9934d4 2007-08-28 20:02:49,968 DEBUG [org.jboss.mx.metadata.xb.ModelMBeanConstructorInfoContainer] addChild, {urn:jboss-test:xmbean:2.0}name,JNDIBindingService 2007-08-28 20:02:49,968 DEBUG [org.jboss.mx.metadata.xb.ModelMBeanConstructorInfoContainer] addChild, {urn:jboss-test:xmbean:2.0}description,The default no-arg constructor 2007-08-28 20:02:49,968 DEBUG [org.jboss.mx.metadata.xb.ModelMBeanAttributeInfoContainer] addChild, access,read-write 2007-08-28 20:02:49,968 DEBUG [org.jboss.mx.metadata.xb.ModelMBeanAttributeInfoContainer] addChild, {urn:jboss-test:xmbean:2.0}description,The root JNDI name of the context the bindings are to be added under 2007-08-28 20:02:49,968 DEBUG [org.jboss.mx.metadata.xb.ModelMBeanAttributeInfoContainer] addChild, {urn:jboss-test:xmbean:2.0}name,RootName 2007-08-28 20:02:49,968 DEBUG [org.jboss.mx.metadata.xb.ModelMBeanAttributeInfoContainer] addChild, {urn:jboss-test:xmbean:2.0}type,java.lang.String 2007-08-28 20:02:49,968 DEBUG [org.jboss.mx.metadata.xb.ModelMBeanAttributeInfoContainer] addChild, access,read-write 2007-08-28 20:02:49,968 DEBUG [org.jboss.mx.metadata.xb.ModelMBeanAttributeInfoContainer] addChild, {urn:jboss-test:xmbean:2.0}description,The JNDI bindings to add under the RootName 2007-08-28 20:02:49,968 DEBUG [org.jboss.mx.metadata.xb.ModelMBeanAttributeInfoContainer] addChild, {urn:jboss-test:xmbean:2.0}name,Bindings 2007-08-28 20:02:49,968 DEBUG [org.jboss.mx.metadata.xb.ModelMBeanAttributeInfoContainer] addChild, {urn:jboss-test:xmbean:2.0}type,org.jboss.naming.JNDIBindings 2007-08-28 20:02:49,968 DEBUG [org.jboss.mx.metadata.xb.ModelMBeanOperationInfoContainer] addChild, impact,ACTION_INFO 2007-08-28 20:02:49,968 DEBUG [org.jboss.mx.metadata.xb.ModelMBeanOperationInfoContainer] addChild, {urn:jboss-test:xmbean:2.0}description,The start lifecycle operation 2007-08-28 20:02:49,968 DEBUG [org.jboss.mx.metadata.xb.ModelMBeanOperationInfoContainer] addChild, {urn:jboss-test:xmbean:2.0}name,start 2007-08-28 20:02:49,968 DEBUG [org.jboss.mx.metadata.xb.ModelMBeanOperationInfoContainer] addChild, {urn:jboss-test:xmbean:2.0}return-type,void 2007-08-28 20:02:49,968 DEBUG [org.jboss.mx.metadata.xb.ModelMBeanOperationInfoContainer] addChild, impact,ACTION_INFO 2007-08-28 20:02:49,968 DEBUG [org.jboss.mx.metadata.xb.ModelMBeanOperationInfoContainer] addChild, {urn:jboss-test:xmbean:2.0}description,The stop lifecycle operation 2007-08-28 20:02:49,968 DEBUG [org.jboss.mx.metadata.xb.ModelMBeanOperationInfoContainer] addChild, {urn:jboss-test:xmbean:2.0}name,stop 2007-08-28 20:02:49,984 DEBUG [org.jboss.mx.metadata.xb.ModelMBeanOperationInfoContainer] addChild, {urn:jboss-test:xmbean:2.0}return-type,void 2007-08-28 20:02:49,984 DEBUG [org.jboss.mx.metadata.xb.ModelMBeanNotificationInfoContainer] addChild, {urn:jboss-test:xmbean:2.0}description,The bind event notification 2007-08-28 20:02:49,984 DEBUG [org.jboss.mx.metadata.xb.ModelMBeanNotificationInfoContainer] addChild, {urn:jboss-test:xmbean:2.0}name,bindEvent 2007-08-28 20:02:50,203 DEBUG [org.jboss.test.xml.mbeanserver.XMBean2UnitTestCase] testJavaBeanSchemaInitializerInterceptor took 750ms 2007-08-28 20:02:50,203 DEBUG [org.jboss.test.xml.mbeanserver.XMBean2UnitTestCase] ==== Stopping testJavaBeanSchemaInitializerInterceptor ==== 2007-08-28 20:02:50,203 DEBUG [org.jboss.test.xml.mbeanserver.XMBean2UnitTestCase] ==== tornDown org.jboss.test.xml.mbeanserver.XMBean2UnitTestCase ==== ... -- 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, 1 month

2
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2007