April 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (BPEL-247) throw repeatedCompensation when invoking a compensation handler more than once

by Alejandro Guizar (JIRA)

throw repeatedCompensation when invoking a compensation handler more than once ------------------------------------------------------------------------------ Key: BPEL-247 URL: http://jira.jboss.com/jira/browse/BPEL-247 Project: JBoss jBPM BPEL Issue Type: Task Security Level: Public (Everyone can see) Components: Engine Affects Versions: jBPM BPEL 1.1 beta 3 Reporter: Alejandro Guizar Assigned To: Alejandro Guizar Fix For: jBPM BPEL 1.1.1 -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBBUILD-354) If there are no artifacts to deploy, the deploy plugin should not create folders.

by Paul Gier (JIRA)

If there are no artifacts to deploy, the deploy plugin should not create folders. --------------------------------------------------------------------------------- Key: JBBUILD-354 URL: http://jira.jboss.com/jira/browse/JBBUILD-354 Project: JBoss Build System Issue Type: Feature Request Components: jboss-deploy-maven-plugin Reporter: Paul Gier Assigned To: Paul Gier Fix For: jboss-deploy-maven-plugin-1.2.GA If the jboss deploy plugin does not find any artifacts attached to the build, it should not bother creating the deployment directory and the component-info.xml. -- 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, 7 months

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

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

18 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-4216) Out Of Memory Errors

by Richard Achmatowicz (JIRA)

Out Of Memory Errors -------------------- Key: JBAS-4216 URL: http://jira.jboss.com/jira/browse/JBAS-4216 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.2.0.GA Reporter: Richard Achmatowicz Priority: Blocker Fix For: JBossAS-4.2.0.GA I've run the testsuite on dev03 twice now and got out of memory errors (see output at end). The testsuite is starting server 'all' with the command: jboss-all-config-tests: [server:start] Starting server "all" with command: [server:start] /opt/jdk1.5.0_11/bin/java -cp /home/dtf-admin/JBPAPP-03-19-07/jboss-4.2.0.GA/bin/run.jar:/opt/jdk1.5.0_11/lib/tools.jar -Xmx128m -Djava.endorsed.dirs=/home/dtf-admin/JBPAPP-03-19-07/jboss-4.2.0.GA/lib/endorsed -Djgroups.udp.ip_ttl=0 org.jboss.Main -c all -b 10.16.6.161 -u 239.11.12.6 --------------------------- System.out ------------------------------------------------------------------------------- [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 9.417 sec [junit] Running org.jboss.test.txtimer.test.TimerSerializationTestCase [junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 4.367 sec [junit] Running org.jboss.test.txtimer.test.TransactionalTimerTestCase [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 7.285 sec [server:stop] Shutting down server: all [server:stop] Failed to shutdown server "all" before timeout. Destroying the process. tests-security-manager: [server:start] Starting server "securitymgr" with command: [server:start] /opt/jdk1.5.0_11/bin/java -cp /home/dtf-admin/JBPAPP-03-19-07/jboss-4.2.0.GA/bin/run.jar:/opt/jdk1.5.0_11/lib/tools.jar -Xmx64m -Djboss.home.dir=/home/dtf-admin/JBPAPP-03-19-07/jboss-4.2.0.GA -Djboss.server.home.dir=/home/dtf-admin/JBPAPP-03-19-07/jboss-4.2.0.GA/server/default -Djboss.test.deploy.dir=/home/dtf-admin/JBPAPP-03-19-07/src/testsuite/output/lib -Djava.security.manager -Djava.security.policy==/home/dtf-admin/JBPAPP-03-19-07/src/testsuite/output/resources/securitymgr/server.policy -Djava.security.debug=policy org.jboss.Main -c default -b 10.16.6.161 -u 239.11.12.6 [server:start] Failed to start server "securitymgr" before timeout. Destroying the process. BUILD FAILED /home/dtf-admin/JBPAPP-03-19-07/src/testsuite/build.xml:714: The following error occurred while executing this line: /home/dtf-admin/JBPAPP-03-19-07/src/testsuite/build.xml:1577: Error starting server "securitymgr": Server failed to start; see logs. Total time: 69 minutes 57 seconds Exiting: testsuite failed -------------------------- output.log -------------------------------------- java.lang.OutOfMemoryError: PermGen space 18:23:08,027 ERROR [STDERR] Exception in thread "JBoss System Threads(1)-108" 18:23:08,027 WARN [RunnableTaskWrapper] Unhandled throwable for runnable: org.jnp.server.Main$BootstrapRequestHandler@8aba19 java.lang.OutOfMemoryError: PermGen space 18:23:08,027 ERROR [STDERR] java.lang.OutOfMemoryError: PermGen space 18:23:08,051 WARN [RunnableTaskWrapper] Unhandled throwable for runnable: org.jnp.server.Main$BootstrapRequestHandler@e27907 java.lang.OutOfMemoryError: PermGen space 18:23:10,282 WARN [RunnableTaskWrapper] Unhandled throwable for runnable: org.jnp.server.Main$BootstrapRequestHandler@77dcdf java.lang.OutOfMemoryError: PermGen space 18:23:13,343 WARN [UDP] packet from 10.16.6.97:45459 has different version (12338) from ours (241). Packet is discarded 18:23:13,527 WARN [RunnableTaskWrapper] Unhandled throwable for runnable: org.jnp.server.Main$BootstrapRequestHandler@145c626 java.lang.OutOfMemoryError: PermGen space 18:23:15,412 ERROR [STDERR] Exception in thread "JBoss System Threads(1)-97" 18:23:15,412 ERROR [STDERR] java.lang.OutOfMemoryError: PermGen space 18:23:15,413 WARN [RunnableTaskWrapper] Unhandled throwable for runnable: org.jnp.server.Main$BootstrapRequestHandler@17468 97 java.lang.OutOfMemoryError: PermGen space 18:23:17,595 ERROR [STDERR] Exception in thread "JBoss System Threads(1)-107" 18:23:17,595 ERROR [STDERR] java.lang.OutOfMemoryError: PermGen space 18:23:17,818 WARN [RunnableTaskWrapper] Unhandled throwable for runnable: org.jnp.server.Main$BootstrapRequestHandler@1a02ba8 java.lang.OutOfMemoryError: PermGen space 18:23:19,634 ERROR [STDERR] Exception in thread "JBoss System Threads(1)-104" 18:23:19,634 ERROR [STDERR] java.lang.OutOfMemoryError: PermGen space 18:23:19,634 WARN [RunnableTaskWrapper] Unhandled throwable for runnable: org.jnp.server.Main$BootstrapRequestHandler@2c40a java.lang.OutOfMemoryError: PermGen space 18:23:21,313 ERROR [STDERR] Exception in thread "JBoss System Threads(1)-110" 18:23:21,313 ERROR [STDERR] java.lang.OutOfMemoryError: PermGen space 18:23:27,676 WARN [RunnableTaskWrapper] Unhandled throwable for runnable: org.jnp.server.Main$BootstrapRequestHandler@1b184a6 -- 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, 7 months

5
19
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1177) impossible to move the windows on the right with the management portlet

by St￩phane HUDEC (JIRA)

impossible to move the windows on the right with the management portlet ----------------------------------------------------------------------- Key: JBPORTAL-1177 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1177 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Portlet Affects Versions: 2.4.1 Final, 2.6.DR1, 2.4 Final Reporter: St￩phane HUDEC Assigned To: Julien Viet Impossible to move the windows on the right with the management portlet. To reproduce on the default portal : try to move the CatalogPortletWindow of the Test page to the right (left --> navigation), the window in fact is moved to the left (center). I think that a "break" was omitted in the method "public void move(Window target, int direction) " of the "org.jboss.portal.core.portlet.management.PortalObjectManagerBean" before "case MOVE_LEFT" instruction. -- 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, 7 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-4290) Timer.getTimeRemaining() returns incorrect value

by David Boeren (JIRA)

Timer.getTimeRemaining() returns incorrect value ------------------------------------------------ Key: JBAS-4290 URL: http://jira.jboss.com/jira/browse/JBAS-4290 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: JBossAS-4.0.4.GA Reporter: David Boeren Priority: Minor >From case: "If I use a Timer for a SLSB and persist it, all work correct if I start it. The getNextTimeOut() give the correct time, the getRemaining() will show a value between 4990 and 4999 (intervall was 5000) after a restart of the server the NextTimeout is in the past and the remaining is negative. Looks like that the service continue with the old time." So, getRemaining() returns a negative value after a server restart. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMICROCONT-171) Add support for static aliases defined on the ControllerContext

by Adrian Brock (JIRA)

Add support for static aliases defined on the ControllerContext --------------------------------------------------------------- Key: JBMICROCONT-171 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-171 Project: JBoss MicroContainer Issue Type: Sub-task Components: Dependency Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossMC_2_0_0_CR1 Add a getAliases() to the ControllerContext interface. This should allow retrieval of the real context from the context using any of the aliases. -- 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, 7 months

1
4
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

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

18 years, 7 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 April 2007