October 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-7287) OOM encountered with tomcat-sso-tests with 64 bit JVM

by Shelly McGowan (JIRA)

OOM encountered with tomcat-sso-tests with 64 bit JVM ----------------------------------------------------- Key: JBAS-7287 URL: https://jira.jboss.org/jira/browse/JBAS-7287 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Shelly McGowan -- 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

16 years, 9 months

2
14
0 / 0

[JBoss JIRA] Created: (JBID-141) JBoss STS - add logging to the STS classes

by Stefan Guilhen (JIRA)

JBoss STS - add logging to the STS classes ------------------------------------------ Key: JBID-141 URL: https://jira.jboss.org/jira/browse/JBID-141 Project: JBoss Identity Issue Type: Task Components: Identity-Federation Affects Versions: IDFED-1.0.0.alpha3 Reporter: Stefan Guilhen Assignee: Stefan Guilhen Fix For: IDFED-1.0.0.alpha4 We need to log the important events in the STS classes using the appropriate log levels. -- 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

16 years, 9 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-7351) Update jboss-as-spring-int to use VFS3

by David Lloyd (JIRA)

Update jboss-as-spring-int to use VFS3 -------------------------------------- Key: JBAS-7351 URL: https://jira.jboss.org/jira/browse/JBAS-7351 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: David Lloyd -- 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

16 years, 9 months

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-7373) Upgrade EJB3 to 1.1.19

by jaikiran pai (JIRA)

Upgrade EJB3 to 1.1.19 ---------------------- Key: JBAS-7373 URL: https://jira.jboss.org/jira/browse/JBAS-7373 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: EJB3 Reporter: jaikiran pai Assignee: jaikiran pai Fix For: JBossAS-5.2.0.Beta1 Upgrade Branch_5_x to the latest 1.1.19 version of EJB3. -- 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

16 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1894) Portlet instances cannot be deleted with the GUI after undeployment

by Martin Putz (JIRA)

Portlet instances cannot be deleted with the GUI after undeployment ------------------------------------------------------------------- Key: JBPORTAL-1894 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1894 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Admin Affects Versions: 2.6.3 Final Reporter: Martin Putz Assigned To: Thomas Heute When a portlet application (*.war) is undeployed, the portlet instances defined in portlet-instances.xml remain in the JBP_INSTANCE table. This causes problems if the same application is redeployed under a different context name. The instances are also not listed in the management portlet GUI, which would allow to delete them manually. -- 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

16 years, 9 months

2
1
0 / 0

[JBoss JIRA] Created: (JBAS-3521) OptimisticLockUnitTestCase Intermittently Fails

by Matt Wringe (JIRA)

OptimisticLockUnitTestCase Intermittently Fails ----------------------------------------------- Key: JBAS-3521 URL: http://jira.jboss.com/jira/browse/JBAS-3521 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Test Suite Affects Versions: JBossAS-4.0.4.GA Environment: Sun 1.4.2_12 JVM RHEL 4, Linux Kernel 2.6.9 Reporter: Matt Wringe The OptimisticLockUnitTestCase testBug1006723 test seems to fail randomly. This is a known issue, and is described here: http://wiki.jboss.org/wiki/Wiki.jsp?page=TestsuiteTroubleShooting But there does not appear to be a bug filed about this issue, nor can I find bug 1006723 "Problem OptimisticLockUnitTestCase fails Suite: org.jboss.test.cmp2.optimisticlock.test.OptimisticLockUnitTestCase Test: testBug1006723 Type: error Exception: javax.ejb.CreateException Message: Error checking if entity exists:java.sql.SQLException: Column not found: \ OIDCMP in statement SELECT COUNT(*) FROM ENTITYA WHERE OIDCMP=? This test passes intermintently. Run it a few times" -- 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

16 years, 9 months

6
9
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1940) Create tutorials and reference documentation for EJB3.1 features

by jaikiran pai (JIRA)

Create tutorials and reference documentation for EJB3.1 features ---------------------------------------------------------------- Key: EJBTHREE-1940 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1940 Project: EJB 3.0 Issue Type: Task Components: docs Affects Versions: EJB 3.1 Reporter: jaikiran pai Assignee: jaikiran pai Fix For: EJB 3.1 Container task to track EJB3.1 tutorials and any reference documentation for EJB 3.1 features. Sub-tasks will be created for each EJB3.1 feature documentation. -- 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

16 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1941) Create tutorials for EJB3.1 nointerface feature

by jaikiran pai (JIRA)

Create tutorials for EJB3.1 nointerface feature ----------------------------------------------- Key: EJBTHREE-1941 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1941 Project: EJB 3.0 Issue Type: Sub-task Components: docs Reporter: jaikiran pai Assignee: jaikiran pai Fix For: EJB 3.1 Create tutorials for EJB3.1 nointerface feature. -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (GPD-271) Exception logged on connection test in jBPM editor

by Koen Aers (JIRA)

[ https://jira.jboss.org/jira/browse/GPD-271?page=com.atlassian.jira.plugin... ] Koen Aers closed GPD-271. ------------------------- Resolution: Done I could only reproduce the bug on a Linux machine. Moreover, as the problem seems to have disappeared with Eclipse 3.5 and as the bug is harmless, I won't put any more energy in it. > Exception logged on connection test in jBPM editor > -------------------------------------------------- > > Key: GPD-271 > URL: https://jira.jboss.org/jira/browse/GPD-271 > Project: jBPM GPD > Issue Type: Bug > Components: jpdl > Environment: JBossTools-3.0.0.CR1-N200811050757-ALL-linux-gtk > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: jBPM jPDL Designer 3.2 > > > Opened a process definition in the jBPM editor, went to the Deployment tab, and clicked on "Test Connection". The test completes as expected (the server is running), but the following exceptions are logged: > eclipse.buildId=M20080911-1700 > java.version=1.6.0_07 > java.vendor=Sun Microsystems Inc. > BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US > Command-line arguments: -os linux -ws gtk -arch x86 -clean > Error > Wed Nov 05 12:12:04 GMT-05:00 2008 > An unexpected exception was thrown. > java.util.ConcurrentModificationException > at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793) > at java.util.HashMap$KeyIterator.next(HashMap.java:828) > at org.eclipse.ui.internal.handlers.HandlerAuthority.processChangedCommands(HandlerAuthority.java:627) > at org.eclipse.ui.internal.handlers.HandlerAuthority.access$1(HandlerAuthority.java:610) > at org.eclipse.ui.internal.handlers.HandlerAuthority$1.propertyChange(HandlerAuthority.java:175) > at org.eclipse.ui.internal.services.EvaluationAuthority$1.run(EvaluationAuthority.java:252) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) > at org.eclipse.ui.internal.services.EvaluationAuthority.fireServiceChange(EvaluationAuthority.java:246) > at org.eclipse.ui.internal.services.EvaluationAuthority.endSourceChange(EvaluationAuthority.java:197) > at org.eclipse.ui.internal.services.EvaluationAuthority.sourceChanged(EvaluationAuthority.java:135) > at org.eclipse.ui.internal.services.ExpressionAuthority.sourceChanged(ExpressionAuthority.java:310) > at org.eclipse.ui.internal.services.ExpressionAuthority.sourceChanged(ExpressionAuthority.java:289) > at org.eclipse.ui.AbstractSourceProvider.fireSourceChanged(AbstractSourceProvider.java:99) > at org.eclipse.ui.internal.services.ActivePartSourceProvider.checkActivePart(ActivePartSourceProvider.java:244) > at org.eclipse.ui.internal.services.ActivePartSourceProvider$2.windowDeactivated(ActivePartSourceProvider.java:125) > at org.eclipse.ui.internal.Workbench$13.run(Workbench.java:824) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) > at org.eclipse.ui.internal.Workbench.fireWindowDeactivated(Workbench.java:822) > at org.eclipse.ui.internal.WorkbenchWindow$26.shellDeactivated(WorkbenchWindow.java:3012) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:105) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1182) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1163) > at org.eclipse.swt.widgets.Shell.filterProc(Shell.java:683) > at org.eclipse.swt.widgets.Display.filterProc(Display.java:1470) > at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) > at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:1550) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3031) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) > at org.eclipse.jface.window.Window.open(Window.java:801) > at org.jbpm.gd.jpdl.util.ProcessDeployer.pingServer(Unknown Source) > at org.jbpm.gd.jpdl.deployment.DeploymentForm$5.widgetSelected(Unknown Source) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033) > at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) > at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) > at org.eclipse.equinox.launcher.Main.run(Main.java:1236) > ------------------------------------- > eclipse.buildId=M20080911-1700 > java.version=1.6.0_07 > java.vendor=Sun Microsystems Inc. > BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US > Command-line arguments: -os linux -ws gtk -arch x86 -clean > Error > Wed Nov 05 12:12:04 GMT-05:00 2008 > Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench". > java.util.ConcurrentModificationException > at java.util.HashMap$HashIterator.nextEntry(HashMap.java:793) > at java.util.HashMap$KeyIterator.next(HashMap.java:828) > at org.eclipse.ui.internal.handlers.HandlerAuthority.processChangedCommands(HandlerAuthority.java:627) > at org.eclipse.ui.internal.handlers.HandlerAuthority.access$1(HandlerAuthority.java:610) > at org.eclipse.ui.internal.handlers.HandlerAuthority$1.propertyChange(HandlerAuthority.java:175) > at org.eclipse.ui.internal.services.EvaluationAuthority$1.run(EvaluationAuthority.java:252) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) > at org.eclipse.ui.internal.services.EvaluationAuthority.fireServiceChange(EvaluationAuthority.java:246) > at org.eclipse.ui.internal.services.EvaluationAuthority.endSourceChange(EvaluationAuthority.java:197) > at org.eclipse.ui.internal.services.EvaluationAuthority.sourceChanged(EvaluationAuthority.java:135) > at org.eclipse.ui.internal.services.ExpressionAuthority.sourceChanged(ExpressionAuthority.java:310) > at org.eclipse.ui.internal.services.ExpressionAuthority.sourceChanged(ExpressionAuthority.java:289) > at org.eclipse.ui.AbstractSourceProvider.fireSourceChanged(AbstractSourceProvider.java:99) > at org.eclipse.ui.internal.services.ActivePartSourceProvider.checkActivePart(ActivePartSourceProvider.java:244) > at org.eclipse.ui.internal.services.ActivePartSourceProvider$2.windowDeactivated(ActivePartSourceProvider.java:125) > at org.eclipse.ui.internal.Workbench$13.run(Workbench.java:824) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) > at org.eclipse.ui.internal.Workbench.fireWindowDeactivated(Workbench.java:822) > at org.eclipse.ui.internal.WorkbenchWindow$26.shellDeactivated(WorkbenchWindow.java:3012) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:105) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1182) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1163) > at org.eclipse.swt.widgets.Shell.filterProc(Shell.java:683) > at org.eclipse.swt.widgets.Display.filterProc(Display.java:1470) > at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) > at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:1550) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3031) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) > at org.eclipse.jface.window.Window.open(Window.java:801) > at org.jbpm.gd.jpdl.util.ProcessDeployer.pingServer(Unknown Source) > at org.jbpm.gd.jpdl.deployment.DeploymentForm$5.widgetSelected(Unknown Source) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033) > at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) > at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:386) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) > at org.eclipse.equinox.launcher.Main.run(Main.java:1236) -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBEE-14) Release 5.2.0.Beta1

by Shelly McGowan (JIRA)

Release 5.2.0.Beta1 ------------------- Key: JBEE-14 URL: https://jira.jboss.org/jira/browse/JBEE-14 Project: JBoss JavaEE APIs Issue Type: Release Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 5.2.0.Beta1 -- 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

16 years, 9 months

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