July 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (EJBTHREE-662) sfsb bean remove is not properly done

by Ben Wang (JIRA)

sfsb bean remove is not properly done -------------------------------------- Key: EJBTHREE-662 URL: http://jira.jboss.com/jira/browse/EJBTHREE-662 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC8 - FD Reporter: Ben Wang Assigned To: Ben Wang Fix For: EJB 3.0 RC9 - FD Currently in StatefulRemoveInterceptor, when user calls @Remove, it removes directly the bean instance in the cache. However, this is incorrect when there is nested bean involved. Correct procedure is to do StatefulBeanContext.remove() that will remove it recursively. -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-653) No pooling for stateless session beans

by Guido Bening (JIRA)

No pooling for stateless session beans -------------------------------------- Key: EJBTHREE-653 URL: http://jira.jboss.com/jira/browse/EJBTHREE-653 Project: EJB 3.0 Issue Type: Bug Components: EJB3 Extensions Affects Versions: EJB 3.0 RC8 - FD Environment: OS: Windows XP SP2 JDK 1.5.0_06_b05 JBoss AS 4.0.4 GA Reporter: Guido Bening Scenario: Client VM calls a method on a EJB 2 Stateful Session Bean (SFSB) via the remote interface in a loop for 1000 times.Transaction starts on the application server. The SFSB method calls a method on a EJB3 Stateless Session Bean (SLSB) - via the remote interface (local interface makes no difference). The print out in the PostConstruct callback method of the EJB3 SLSB shows us, that a new bean instance was created for each of the 1000 method calls. Because of ThreadLocal pooling approach, we print out the Thread id too to show, that we always have the same Thread for each method call. CallBack method: /** * EJBCreate method. */ @PostConstruct public void ejb3Create() { System.out.println("New SessionBean " + this); System.out.println("Thread " + Thread.currentThread().getId()); setupBean(); } And the log for a few of the 1000 calls: ... 09:17:51,119 INFO [STDOUT] New SessionBean com.jcoffee.components.um3.UserManagementComponent3@231ae2 09:17:51,129 INFO [STDOUT] Thread 97 09:17:51,139 INFO [STDOUT] New SessionBean com.jcoffee.components.um3.UserManagementComponent3@1662174 09:17:51,139 INFO [STDOUT] Thread 97 09:17:51,219 INFO [STDOUT] New SessionBean com.jcoffee.components.um3.UserManagementComponent3@189f155 09:17:51,219 INFO [STDOUT] Thread 97 09:17:51,239 INFO [STDOUT] New SessionBean com.jcoffee.components.um3.UserManagementComponent3@1a82dfb 09:17:51,239 INFO [STDOUT] Thread 97 09:17:51,289 INFO [STDOUT] New SessionBean com.jcoffee.components.um3.UserManagementComponent3@198813a 09:17:51,289 INFO [STDOUT] Thread 97 09:17:51,309 INFO [STDOUT] New SessionBean com.jcoffee.components.um3.UserManagementComponent3@59eefd 09:17:51,309 INFO [STDOUT] Thread 97 09:17:51,359 INFO [STDOUT] New SessionBean com.jcoffee.components.um3.UserManagementComponent3@2e3520 09:17:51,369 INFO [STDOUT] Thread 97 09:17:51,379 INFO [STDOUT] New SessionBean com.jcoffee.components.um3.UserManagementComponent3@1ed457 09:17:51,379 INFO [STDOUT] Thread 97 09:17:51,439 INFO [STDOUT] New SessionBean com.jcoffee.components.um3.UserManagementComponent3@1e1c7f3 09:17:51,439 INFO [STDOUT] Thread 97 09:17:51,449 INFO [STDOUT] New SessionBean com.jcoffee.components.um3.UserManagementComponent3@15cb8ed 09:17:51,449 INFO [STDOUT] Thread 97 09:17:51,519 INFO [STDOUT] New SessionBean com.jcoffee.components.um3.UserManagementComponent3@1a4a949 09:17:51,519 INFO [STDOUT] Thread 97 09:17:51,529 INFO [STDOUT] New SessionBean com.jcoffee.components.um3.UserManagementComponent3@19ae0a 09:17:51,529 INFO [STDOUT] Thread 97 09:17:51,589 INFO [STDOUT] New SessionBean com.jcoffee.components.um3.UserManagementComponent3@567fa0 09:17:51,599 INFO [STDOUT] Thread 97 09:17:51,609 INFO [STDOUT] New SessionBean com.jcoffee.components.um3.UserManagementComponent3@19956fe 09:17:51,609 INFO [STDOUT] Thread 97 09:17:51,659 INFO [STDOUT] New SessionBean com.jcoffee.components.um3.UserManagementComponent3@150e574 09:17:51,669 INFO [STDOUT] Thread 97 09:17:51,679 INFO [STDOUT] New SessionBean com.jcoffee.components.um3.UserManagementComponent3@aa46ad 09:17:51,679 INFO [STDOUT] Thread 97 ... -- 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, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (EJBTHREE-650) javax.ejb.SessionContext.getInvokedBusinessInterface() has wrong return type

by Carlo de Wolf (JIRA)

javax.ejb.SessionContext.getInvokedBusinessInterface() has wrong return type ---------------------------------------------------------------------------- Key: EJBTHREE-650 URL: http://jira.jboss.com/jira/browse/EJBTHREE-650 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC8 - FD Reporter: Carlo de Wolf javax.ejb.SessionContext.getInvokedBusinessInterface() must return Class not Object. See http://java.sun.com/javaee/5/docs/api/javax/ejb/SessionContext.html#getIn... -- 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, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBPM-705) Provide monitoring for standalone applications

by Ryan Campbell (JIRA)

Provide monitoring for standalone applications ---------------------------------------------- Key: JBPM-705 URL: http://jira.jboss.com/jira/browse/JBPM-705 Project: JBoss jBPM Issue Type: Feature Request Reporter: Ryan Campbell Assigned To: Tom Baeyens Fix For: jBPM 3.2 Provide jmx interfaces for monitor processes not in a webapp. Or can you point the monitoring webapp at a jBPM datastore? -- 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, 9 months

3
8
0 / 0

[JBoss JIRA] Created: (JBTM-111) Check QA into CVS

by Mark Little (JIRA)

Check QA into CVS ----------------- Key: JBTM-111 URL: http://jira.jboss.com/jira/browse/JBTM-111 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Testing Affects Versions: 4.2 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.4 -- 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, 9 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-445) Update user documentation with clustering-related details

by Ovidiu Feodorov (JIRA)

Update user documentation with clustering-related details --------------------------------------------------------- Key: JBMESSAGING-445 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-445 Project: JBoss Messaging Issue Type: Task Reporter: Ovidiu Feodorov Assigned To: Ovidiu Feodorov Fix For: 1.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

18 years, 9 months

2
9
0 / 0

[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

18 years, 9 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

18 years, 9 months

3
5
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

18 years, 9 months

2
2
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

18 years, 10 months

4
6
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2006