December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBTM-173) Integrate with AS 4.2

by Mark Little (JIRA)

Integrate with AS 4.2 --------------------- Key: JBTM-173 URL: http://jira.jboss.com/jira/browse/JBTM-173 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Release Reporter: Mark Little Assigned To: Jonathan Halliday Fix For: 4.2.3 -- 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
2
0 / 0

[JBoss JIRA] Created: (JBAS-3724) NotFoundInDispatcherException from InvokerLocator when accessing remote calls when on a non default port

by Grant Quimby (JIRA)

NotFoundInDispatcherException from InvokerLocator when accessing remote calls when on a non default port -------------------------------------------------------------------------------------------------------- Key: JBAS-3724 URL: http://jira.jboss.com/jira/browse/JBAS-3724 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services, EJB3, Remoting Affects Versions: JBossAS-4.0.4.GA Environment: One JBoss 4.0.4.GA install with two instances, one on the default ports and one on ports with an increase of 1000 on all port numbers. Reporter: Grant Quimby Assigned To: Dimitris Andreadis Priority: Blocker When trying to access a remote application that is running in a server instance that does not have the default InvokerLocator port (3873) the remote caller recieves a NotFoundInDispatcherException when trying to call a method in the EJB3 Stateless Session Bean as the EJB3 Session Bean's InvokerLocator is at port 4873 and not port 3873 where the Remote Proxy looks. Similar issue for Service Beans at http://www.jboss.com/index.html?module=bb&op=viewtopic&t=89537 This is okay presently but in approximately two weeks we need to be running four instances with Session beans in two of them, which is currently not possible in a production version. -- 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
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-849) PojoCache jmx test case failure

by Ben Wang (JIRA)

PojoCache jmx test case failure ------------------------------- Key: JBCACHE-849 URL: http://jira.jboss.com/jira/browse/JBCACHE-849 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Brian Stansberry Fix For: 2.0.0.GA Current pojo.jmx test is failing so I have commented them out. But we need to fix them before GA. -- 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
2
0 / 0

[JBoss JIRA] Created: (JBAS-3856) Update JBossRemoting to version 2.2.0

by Dimitris Andreadis (JIRA)

Update JBossRemoting to version 2.2.0 ------------------------------------- Key: JBAS-3856 URL: http://jira.jboss.com/jira/browse/JBAS-3856 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Remoting Reporter: Dimitris Andreadis Assigned To: Tom Elrod Fix For: JBossAS-5.0.0.Beta2 JBAS-3273 brought JBossAS Beta1 to remoting 2.2.0.Alpha2. This task is to track the upgrade to a stable 2.2.0 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

19 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-3908) Upgrade jboss and thirdparty dependencies for JBoss 5.0.0.Beta2

by Dimitris Andreadis (JIRA)

Upgrade jboss and thirdparty dependencies for JBoss 5.0.0.Beta2 --------------------------------------------------------------- Key: JBAS-3908 URL: http://jira.jboss.com/jira/browse/JBAS-3908 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Other Reporter: Dimitris Andreadis Fix For: JBossAS-5.0.0.Beta2 Container to task to track upgrades of jboss/thirdparty binary dependencies. -- 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
5
0 / 0

[JBoss JIRA] Created: (JBAS-3726) Introduce basic twiddle tests in the testsuite

by Dimitris Andreadis (JIRA)

Introduce basic twiddle tests in the testsuite ---------------------------------------------- Key: JBAS-3726 URL: http://jira.jboss.com/jira/browse/JBAS-3726 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Test Suite Reporter: Dimitris Andreadis Fix For: JBossAS-4.0.6.CR1 We currently have no automated tests for twidde. -- 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
11
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1049) LDAP integration in JBoss Portal

by Boleslaw Dawidowicz (JIRA)

LDAP integration in JBoss Portal -------------------------------- Key: JBPORTAL-1049 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1049 Project: JBoss Portal Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Portal Identity Affects Versions: 2.6.Alpha1 Reporter: Boleslaw Dawidowicz Assigned To: Boleslaw Dawidowicz Fix For: 2.6.Alpha1 Grouping task for all ldap issues in portal for 2.6 -- 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: (JBPORTAL-1044) test cases against LDAP implementation of identity modules

by Boleslaw Dawidowicz (JIRA)

test cases against LDAP implementation of identity modules ---------------------------------------------------------- Key: JBPORTAL-1044 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1044 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Identity Affects Versions: 2.6.Alpha1 Reporter: Boleslaw Dawidowicz Assigned To: Boleslaw Dawidowicz Fix For: 2.6.Alpha1 - Testing in identity module should be implemented to perform implementation agnostic tests on different implementations of UserModule and RoleModule - UserTestCase -> DBUserTestCase - Introduce LDAPUserTestCase - both reuse UserTest code so we can perform same tests on different implementations -- 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
3
0 / 0

[JBoss JIRA] Created: (JBAS-3780) Deploying empty file to farm directory causes ScannerThread to hang

by Brian Stansberry (JIRA)

Deploying empty file to farm directory causes ScannerThread to hang ------------------------------------------------------------------- Key: JBAS-3780 URL: http://jira.jboss.com/jira/browse/JBAS-3780 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Environment: Fedora Core 5 JBoss [Zion] 4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339) Reporter: Brian Stansberry Assigned To: Brian Stansberry As reported by Dan Delany in JBCLUSTER-151: Creating a 0 byte long file in the farm directory causes the server to stop scanning the farm directory. To reproduce: Deploy a fresh instance of JBoss. Do not deploy any applications to it. Configure it to be part of a cluster. Launch JBoss. After it is running, touch farm/foo.xml The log will show 07:45:34,555 INFO [JkMain] Jk running ID=0 time=0/33 config=null 07:45:34,562 INFO [Server] JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)] Started in 42s:633ms 07:45:48,664 INFO [ClusterFileTransfer] Start push of file foo.xml to cluster. -- 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
4
0 / 0

[JBoss JIRA] Created: (JBAS-3798) EJB Interceptors Initialised Before Dependent Services Started

by Darran Lofthouse (JIRA)

EJB Interceptors Initialised Before Dependent Services Started -------------------------------------------------------------- Key: JBAS-3798 URL: http://jira.jboss.com/jira/browse/JBAS-3798 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Deployment services, EJB2 Affects Versions: JBossAS-4.0.5.GA, JBossAS-4.0.4.GA Reporter: Darran Lofthouse Assigned To: Dimitris Andreadis Fix For: JBossAS-4.0.6.CR1 The interceptors for an EJB are initialised in the create step of EJB deployment, this means that they can be initialised before the services the EJB depends on have been started. This can be reproduced by deploying a sar that contains a jar that contains a MDB and then starting JBoss, the CachedConnectionInterceptor is initialised before the CachedConnectionManager is available and the following warning is logged: - 12:27:54,179 WARN [EjbModule] Could not load the org.jboss.resource.connectionmanager.CachedConnectionInterceptor interceptor for this container javax.management.InstanceNotFoundException: jboss.jca:service=CachedConnectionManager is not registered. at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:523) at org.jboss.mx.server.MBeanServerImpl.getAttribute(MBeanServerImpl.java:550) at org.jboss.resource.connectionmanager.CachedConnectionInterceptor.<init>(CachedConnectionInterceptor.java:78) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at java.lang.Class.newInstance0(Class.java:350) at java.lang.Class.newInstance(Class.java:303) at org.jboss.ejb.EjbModule.addInterceptors(EjbModule.java:930) at org.jboss.ejb.EjbModule.initializeContainer(EjbModule.java:816) at org.jboss.ejb.EjbModule.createMessageDrivenContainer(EjbModule.java:602) at org.jboss.ejb.EjbModule.createContainer(EjbModule.java:569) at org.jboss.ejb.EjbModule.createService(EjbModule.java:342) at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260) at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:243) -- 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2006