August 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Assigned: (JBPORTAL-2102) cms admin ui testing

by Prabhat Jha (JIRA)

[ https://jira.jboss.org/jira/browse/JBPORTAL-2102?page=com.atlassian.jira.... ] Prabhat Jha reassigned JBPORTAL-2102: ------------------------------------- Assignee: Viliam Rockai (was: Prabhat Jha) > cms admin ui testing > -------------------- > > Key: JBPORTAL-2102 > URL: https://jira.jboss.org/jira/browse/JBPORTAL-2102 > Project: JBoss Portal > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Prabhat Jha > Assignee: Viliam Rockai > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
0
0 / 0

[JBoss JIRA] Assigned: (JBPORTAL-2101) identity admin ui testing

by Prabhat Jha (JIRA)

[ https://jira.jboss.org/jira/browse/JBPORTAL-2101?page=com.atlassian.jira.... ] Prabhat Jha reassigned JBPORTAL-2101: ------------------------------------- Assignee: Viliam Rockai (was: Prabhat Jha) > identity admin ui testing > ------------------------- > > Key: JBPORTAL-2101 > URL: https://jira.jboss.org/jira/browse/JBPORTAL-2101 > Project: JBoss Portal > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Prabhat Jha > Assignee: Viliam Rockai > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-210) Release 1.1.0.CR3 to align with current jboss-ha-server-api release.

by Paul Ferraro (JIRA)

Release 1.1.0.CR3 to align with current jboss-ha-server-api release. -------------------------------------------------------------------- Key: JBCLUSTER-210 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-210 Project: JBoss Clustering Issue Type: Feature Request Security Level: Public (Everyone can see) Components: HA-Client Affects Versions: 1.1.0.CR2 Reporter: Paul Ferraro Assignee: Paul Ferraro Priority: Minor Fix For: 1.1.0.CR3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
4
0 / 0

[JBoss JIRA] Commented: (JBPORTAL-2101) identity admin ui testing

by Prabhat Jha (JIRA)

[ https://jira.jboss.org/jira/browse/JBPORTAL-2101?page=com.atlassian.jira.... ] Prabhat Jha commented on JBPORTAL-2101: --------------------------------------- Please see reference guide for details. But this is what needs to be automated: 0. Login as admin 1. Create a new user and verify 2. Create a new role and verify 3. Assigning a new user to new role and verify 4. Deleting a user 5. Deleting a role 6. Removing a user from role > identity admin ui testing > ------------------------- > > Key: JBPORTAL-2101 > URL: https://jira.jboss.org/jira/browse/JBPORTAL-2101 > Project: JBoss Portal > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Prabhat Jha > Assignee: Prabhat Jha > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMETA-87) switch to JBossXB-2.0.0.CR12

by Alexey Loubyansky (JIRA)

switch to JBossXB-2.0.0.CR12 ---------------------------- Key: JBMETA-87 URL: https://jira.jboss.org/jira/browse/JBMETA-87 Project: JBoss Metadata Issue Type: Thirdparty Change Security Level: Public (Everyone can see) Reporter: Alexey Loubyansky Assignee: Alexey Loubyansky Fix For: 1.0.0.CR1 JBMETA-76 depends on the fixes in JBossXB-2.0.0.CR12 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-5760) Allow mc bootstrap file to be specified via the "jboss.bootstrap.url" system property

by Scott M Stark (JIRA)

Allow mc bootstrap file to be specified via the "jboss.bootstrap.url" system property ------------------------------------------------------------------------------------- Key: JBAS-5760 URL: http://jira.jboss.com/jira/browse/JBAS-5760 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: MicroContainer bus Affects Versions: JBossAS-5.0.0.CR1 Reporter: Scott M Stark Assigned To: Scott M Stark Fix For: JBossAS-5.0.0.CR2 We have a BOOTSTRAP_URL = "jboss.bootstrap.url" system property for identifying the bootstrap file processed by the Server implementation in use. It needs to be used for overriding the mc bootstrap file as well. -- 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

15 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBREM-1012) CLONE [JBREM-1010] - Add feature to declaratively turn on leasing for 2.4.0

by Ron Sigal (JIRA)

CLONE [JBREM-1010] - Add feature to declaratively turn on leasing for 2.4.0 --------------------------------------------------------------------------- Key: JBREM-1012 URL: https://jira.jboss.org/jira/browse/JBREM-1012 Project: JBoss Remoting Issue Type: Feature Request Security Level: Public (Everyone can see) Components: general Affects Versions: 2.2.2.SP7 Reporter: Ron Sigal Assignee: Ron Sigal Fix For: 2.2.2.SP9 We have a request to declaratively turn on leasing. Currently you can only do it via debugging. Here's the conversation from Ron so far. It says more than I could. -------------------------------------------------------------- The problem lies in org.jboss.aspects.remoting.InvokeRemoteInterceptor, which (1) opens an org.jboss.remoting.Client, (2) makes the invocation, and (3) closes the Remoting client. I guess that's because there's no notion of a "session" or a "lifetime" with EJBs, so there's no other natural place to close the Client. The other part of the story is the relationship between Client and the actual invoker, org.jboss.remoting.transport.socket.MicroSocketClientInvoker in this case. Multiple Clients connected to the same server will share an invoker, increasing its reference count. So if multiple threads were calling on the same EJB at the same time, closing the connection after an invocation wouldn't close the MicroSocketClientInvoker (and its cache of connections) if another thread was in the middle of another invocation. The gap in my explanation is the lack of evidence of multithreading in the example. I don't know what method1() is doing. But if there were some simultaneous processing going on, then enabling leasing would add an extra invocation to the process of connecting and disconnecting, thereby changing the timing of things, which might then lead to keeping a MicroSocketClientInvoker alive long enough to be reused. Unfortunately, there's no declarative way to turn on leasing. Just an oversight, I guess, and it's never come up so I never thought about fixing it. I could, though. However, there's a more direct approach. I put a feature in Remoting 2.4 which makes it possible to configure Client.disconnect() to delay the destruction of the client invoker by putting it in a TimerTask: JBREM-877 "New Socket Connection is being Created for Every Client Request to the Server". On the EJB3 forum thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=130264, I asked the EJB3 guys to create a JBPAPP issue if they wanted the same feature in Remoting 2.2, but it never happened so I never did it. Since it's certainly a Remoting feature, and not really an EJB3 bug, I guess it's a judgment call whether to go ahead and make the change in Remoting 2.2. But Jay, if you create the JIRA issue(s), I'll be happy to do it and attach a preview jboss-remoting.jar. -------------------------------------------------------------- -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
4
0 / 0

[JBoss JIRA] Created: (JBRULES-1717) BRMS: test scenario configuration doesn't work

by Jaroslaw Kijanowski (JIRA)

BRMS: test scenario configuration doesn't work ---------------------------------------------- Key: JBRULES-1717 URL: https://jira.jboss.org/jira/browse/JBRULES-1717 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 5.0.0.M1 Reporter: Jaroslaw Kijanowski Assignee: Michael Neale Fix For: 5.0.0.M2 I've got a test that fires two rules, but when I use the 'configuration' section to allow only one particular rule to fire or prevent a rule to fire, both rules fire, instead of only one. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
2
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1060) getInvokedBusinessInterface doesn't return correct interface

by Carlo de Wolf (JIRA)

getInvokedBusinessInterface doesn't return correct interface ------------------------------------------------------------ Key: EJBTHREE-1060 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1060 Project: EJB 3.0 Issue Type: Bug Reporter: Carlo de Wolf Assigned To: Andrew Rubinger When there is a common super interface, getInvokedBusinessInterface doesn't return the correct interface. @Stateless @Remote({Remote1.class, Remote2.class}) interface Remote1 extends CommonRemote interface Remote2 extends CommonRemote -- 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

15 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-1336) Pooling Object Streams

by Mircea Markus (JIRA)

Pooling Object Streams ---------------------- Key: JBCACHE-1336 URL: http://jira.jboss.com/jira/browse/JBCACHE-1336 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mircea Markus Assigned To: Manik Surtani Fix For: 3.0.0 ObjectStreams creation consumes a lot of time when it comes to marshalling commands (e.g. > 5% of total command in case of put is in building the ObjectStream). Pooling them would be an important performance enhancement. We cannot pool the ones from JDK as these cache .class information which results in memory leakage. Investigate the possibility of implementing own alternative ObjectStreams which would be pool-able. -- 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

15 years, 8 months

3
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2008