January 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-447) Release 1.2.0 GA after waiting for a week for feedback on the latest CR

by Ovidiu Feodorov (JIRA)

Release 1.2.0 GA after waiting for a week for feedback on the latest CR ----------------------------------------------------------------------- Key: JBMESSAGING-447 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-447 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.2 -- 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

19 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3414) Port EJBDeployer

by Scott M Stark (JIRA)

Port EJBDeployer ---------------- Key: JBAS-3414 URL: http://jira.jboss.com/jira/browse/JBAS-3414 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Deployment services, EJB2 Reporter: Scott M Stark Assigned To: Dimitris Andreadis Fix For: JBossAS-5.0.0.Beta The EJBDeployer needs to be ported to the new VDF and interaction with the EJB3 deployer defined -- 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

19 years, 3 months

3
5
0 / 0

[JBoss JIRA] Created: (EJBTHREE-710) Cleanup E-EJB3 package/code/logging

by Christian Bauer (JIRA)

Cleanup E-EJB3 package/code/logging ----------------------------------- Key: EJBTHREE-710 URL: http://jira.jboss.com/jira/browse/EJBTHREE-710 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Reporter: Christian Bauer Priority: Blocker This is E-EJB3 RC9. The following issues are not minor, they would make me feel uneasy if I was a user: 1. The bundled embedded-jboss-beans.xml uses xmlns="urn:jboss:bean-deployer" and everybody gets a nice WARN on startup that xmlns="urn:jboss:bean-deployer:2.0" should be used. Change that in the distributed configuration file. 2. [java] 13:40:10,676 WARN Ejb3Configuration:104 - Persistence provider caller does not implements the EJB3 spec correctly. PersistenceUnitInfo.getNewTempClassLoader() is null. It's OK to warn users that something is not right, but if something is not right in our distribution there should be a note in the README or something that tells me as a user that this is OK for the moment. Like a link to a JIRA issue. 3. [java] 13:44:59,381 WARN JBossTimerServiceFactory:112 - TIMER SERVICE IS NOT INSTALLED -- Uh, yes, because I don't want it. Find a way for users to disable this warning. I don't see any way to disable the timer service in embedded-jboss-beans.xml and I don't want the .rar and .jar in my libs. 4. In RC9 there is code that prints debugging stuff on STDOUT: [java] lookup [java] UserTransaction: org.jboss.ejb3.embedded.UserTransactionImpl [java] MessageHandlerBean: org.jnp.interfaces.NamingContext This is triggered by EJB3StandaloneBootstrap.scanClasspath("helloworld-ejb3/build"), please remove from code... -- 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

19 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-813) test failure - org.jboss.ejb3.test.clusteredsession.unit.ExtendedPersistenceUnitTestCase(testPassivation)

by Len DiMaggio (JIRA)

test failure - org.jboss.ejb3.test.clusteredsession.unit.ExtendedPersistenceUnitTestCase(testPassivation) --------------------------------------------------------------------------------------------------------- Key: EJBTHREE-813 URL: http://jira.jboss.com/jira/browse/EJBTHREE-813 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798 OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux JDK/JVM: Sun 1.5 java version "1.5.0_10" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03) Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode) EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798 Reporter: Len DiMaggio Priority: Minor JBAS EJB3 test failure - org.jboss.ejb3.test.clusteredsession.unit.ExtendedPersistenceUnitTestCase(testPassivation) Testcase: testPassivation took 11.241 sec FAILED null junit.framework.AssertionFailedError at org.jboss.ejb3.test.clusteredsession.unit.ExtendedPersistenceUnitTestCase.testPassivation(ExtendedPersistenceUnitTestCase.java:123) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) -- 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

19 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-814) test failure - org.jboss.ejb3.test.clusteredsession.unit.NestedBeanUnitTestCase(testPassivation)

by Len DiMaggio (JIRA)

test failure - org.jboss.ejb3.test.clusteredsession.unit.NestedBeanUnitTestCase(testPassivation) ------------------------------------------------------------------------------------------------ Key: EJBTHREE-814 URL: http://jira.jboss.com/jira/browse/EJBTHREE-814 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC9 - FD Environment: JBoss Version: JBoss_4_0_5_GA_EJBTHREE-798 OS: RHEL4/U4 - 2.6.9-42.0.3.ELsmp #1 SMP Mon Sep 25 17:24:31 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux JDK/JVM: Sun 1.5 java version "1.5.0_10" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_10-b03) Java HotSpot(TM) Server VM (build 1.5.0_10-b03, mixed mode) EJB3 tests built from: https://svn.jboss.org/repos/jbossas/branches/JBoss_4_0_5_GA_EJBTHREE-798 Reporter: Len DiMaggio Priority: Minor EJB3 test failure - org.jboss.ejb3.test.clusteredsession.unit.NestedBeanUnitTestCase(testPassivation) Testcase: testPassivation took 11.526 sec FAILED expected:<1> but was:<2> junit.framework.AssertionFailedError: expected:<1> but was:<2> at org.jboss.ejb3.test.clusteredsession.unit.NestedBeanUnitTestCase.testPassivation(NestedBeanUnitTestCase.java:137) at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22) at junit.extensions.TestSetup$1.protect(TestSetup.java:19) at junit.extensions.TestSetup.run(TestSetup.java:23) -- 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

19 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-814) Concurrency issue with passivation

by Brian Stansberry (JIRA)

Concurrency issue with passivation ---------------------------------- Key: JBCACHE-814 URL: http://jira.jboss.com/jira/browse/JBCACHE-814 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Cache loaders Affects Versions: 1.4.0.SP1 Reporter: Brian Stansberry Assigned To: Manik Surtani If the eviction thread attempts to passivate a node roughly concurrently with a get() call, it is quite easy for the get() to return null even though the passivated node has data. Test org.jboss.cache.passivation.ConcurrentPassivationTest shows the problem. I believe the problem results from having the PessimisticLockInterceptor in the chain after the Activation and Passivation interceptors. Potential cause is a race to the PessimisticLockInterceptor between the eviction thread and an application thread doing a get(). 1) Eviction thread wins race, acquires a WL on a node. 2) Application thread is trailing in the race but proceeds through the Activation/Passivation interceptors w/o loading data, because the desired node is still in the cache. 3) Application thread blocks waiting for eviction thread's WL to be released. 4) Eviction thread removes the node from the tree structure. 5) Eviction thread releases the WL. Application thread acquires a RL (it already had a ref to the node). 6) Application thread gets to the cache _get method, which can't find the node in the tree structure, and thus returns null. Another variation on the same theme: 1) Eviction thread wins race, acquires a WL on a node. 2) Application thread is trailing in the race but proceeds through the Activation/Passivation interceptors w/o loading data, because the desired node is still in the cache. 3) Eviction thread removes the node from the tree structure. 4) Application thread gets to PessimisticLockInterceptor, which can't find the node. No need to acquire lock on non-existent node, so thread proceeds. 5) Application thread gets to the cache _get method, which can't find the node in the tree structure, and thus returns null. -- 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

19 years, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (JBPM-714) packaging just the webapp takes way to long

by Ronald van Kuijk (JIRA)

packaging just the webapp takes way to long ------------------------------------------- Key: JBPM-714 URL: http://jira.jboss.com/jira/browse/JBPM-714 Project: JBoss jBPM Issue Type: Feature Request Affects Versions: jBPM 3.2 alpha 1 Environment: Eclipse 3.2, gpd 3.0.11, jdk 1.5 windhoos Reporter: Ronald van Kuijk Assigned To: Tom Baeyens Fix For: jBPM 3.2 Packaging just the webapp takes 13 seconds. In this time the 'global' compile is used. This results in packaging jbpm-jpdl.jar twice and copying it to the repository twice. This should be optimised in combination with a 'deploy' target which deploys it to a configured location. Even better would be if it is a real WTP web (sub?) project which can have things like 'auto deployment' small updates to .xhtml files available immediately, etc.... -- 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

19 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBAS-3888) Upgrade to EJB3 RC10 as a binary dependency

by Dimitris Andreadis (JIRA)

Upgrade to EJB3 RC10 as a binary dependency ------------------------------------------- Key: JBAS-3888 URL: http://jira.jboss.com/jira/browse/JBAS-3888 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: EJB3 Reporter: Dimitris Andreadis Fix For: JBossAS-4.2.0.CR1 -- 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

19 years, 3 months

3
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-437) Non durable subscription optimization

by Tim Fox (JIRA)

Non durable subscription optimization ------------------------------------- Key: JBMESSAGING-437 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-437 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.0.1.CR3 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.0.2 Since non durable subscriptions only live for the life-time of the consumer the it's struck me that we don't actually need to send any acks from the client to the server as messages are acknowledged for non durable subs. Basically I think we can acknowledge them before they are sent from server to client. This is because there's no case where messages will be redelivered from the server to the non durable sub, therefore no need for acks. On session recovery and session rollback messages are redelivered locally (i.e. they are already on the client) so no need for the server to redeliver. This also means we don't need to maintain a delivery list in the server consumer endpoint in this case, and the server consumer endpoint can return a done delivery every time. -- 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

19 years, 3 months

4
6
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-701) Optimisation - Allow onMessage to be executed on the remoting thread

by Tim Fox (JIRA)

Optimisation - Allow onMessage to be executed on the remoting thread -------------------------------------------------------------------- Key: JBMESSAGING-701 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-701 Project: JBoss Messaging Issue Type: Task Affects Versions: 1.2.0.Beta1 Reporter: Tim Fox Assigned To: Tim Fox Fix For: 1.2.1 As an optimisation we should allow message listeners to be executed straight through using the same thread that delivers the message to the message callback handler. This would avoid an extra context switch.. Currently the thread used is from an executor per session - so as to be strictly JMS compliant. -- 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

19 years, 3 months

3
4
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 January 2007