[JBoss JIRA] Updated: (JBIDE-8067) OutOfMemoryError while opening or closing faces-config.xml
by Yahor Radtsevich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-8067?page=com.atlassian.jira.plugin... ]
Yahor Radtsevich updated JBIDE-8067:
------------------------------------
Affects Version/s: 3.2.0.Beta2
Environment: Windows XP, JBDS 4.0.0.Beta2 (was: Windows XP, JBDS 4.0.0.Beta2, .)
> OutOfMemoryError while opening or closing faces-config.xml
> ----------------------------------------------------------
>
> Key: JBIDE-8067
> URL: https://issues.jboss.org/browse/JBIDE-8067
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JSF
> Affects Versions: 3.2.0.Beta2
> Environment: Windows XP, JBDS 4.0.0.Beta2
> Reporter: Yahor Radtsevich
> Assignee: Alexey Kazakov
> Priority: Critical
>
> The error appears sometimes when I try to open or close faces-config.xml and Studio proposes to exit. If I choose exit, than this workspace cannot be opened anymore and Studio fails to start.
> I do not know any reproducible way to catch this error, but it appears several times a day in my workspace that has two JSF projects in it.
> The full stacktrace follows:
> java.lang.OutOfMemoryError
> at java.io.FileInputStream.readBytes(Native Method)
> at java.io.FileInputStream.read(FileInputStream.java:199)
> at java.io.BufferedInputStream.read1(BufferedInputStream.java:256)
> at java.io.BufferedInputStream.read(BufferedInputStream.java:317)
> at org.jboss.tools.common.util.FileUtil.readBytes(FileUtil.java:103)
> at org.jboss.tools.common.util.FileUtil.readFileWithEncodingCheck(FileUtil.java:83)
> at org.jboss.tools.common.model.filesystems.impl.EclipseFileBodySource.get(FolderImpl.java:1184)
> at org.jboss.tools.common.model.filesystems.impl.FolderImpl.getEntityProperties(FolderImpl.java:240)
> at org.jboss.tools.common.model.filesystems.impl.FolderImpl.updateNew(FolderImpl.java:673)
> at org.jboss.tools.common.model.filesystems.impl.FolderImpl.update(FolderImpl.java:399)
> at org.jboss.tools.common.model.util.EclipseResourceUtil.findResourceInFileSystem(EclipseResourceUtil.java:552)
> at org.jboss.tools.common.model.util.EclipseResourceUtil.getObjectByResource(EclipseResourceUtil.java:137)
> at org.jboss.tools.common.model.util.EclipseResourceUtil.createObjectForResource(EclipseResourceUtil.java:335)
> at org.jboss.tools.common.model.markers.XMarkerManager.reload(XMarkerManager.java:105)
> at org.jboss.tools.common.model.markers.XMarkerManager.reload(XMarkerManager.java:90)
> at org.jboss.tools.common.model.markers.XMarkerManager.<init>(XMarkerManager.java:40)
> at org.jboss.tools.common.model.markers.XMarkerManager.getInstance(XMarkerManager.java:31)
> at org.jboss.tools.common.model.ui.navigator.LabelDecoratorImpl.getErrorState(LabelDecoratorImpl.java:71)
> at org.jboss.tools.common.model.ui.navigator.LabelDecoratorImpl.decorateImage(LabelDecoratorImpl.java:40)
> at org.eclipse.jface.viewers.DecoratingLabelProvider.getImage(DecoratingLabelProvider.java:94)
> at org.eclipse.jface.viewers.DecoratingLabelProvider.updateLabel(DecoratingLabelProvider.java:356)
> at org.eclipse.jface.viewers.WrappedViewerLabelProvider.update(WrappedViewerLabelProvider.java:183)
> at org.eclipse.jface.viewers.ViewerColumn.refresh(ViewerColumn.java:152)
> at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:934)
> at org.eclipse.jface.viewers.AbstractTreeViewer$UpdateItemSafeRunnable.run(AbstractTreeViewer.java:102)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
> at org.eclipse.jface.viewers.AbstractTreeViewer.doUpdateItem(AbstractTreeViewer.java:1014)
> at org.eclipse.jface.viewers.StructuredViewer$UpdateItemSafeRunnable.run(StructuredViewer.java:481)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175)
> at org.eclipse.jface.viewers.StructuredViewer.updateItem(StructuredViewer.java:2141)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createTreeItem(AbstractTreeViewer.java:829)
> at org.eclipse.jface.viewers.AbstractTreeViewer$1.run(AbstractTreeViewer.java:804)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:778)
> at org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:644)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:749)
> at org.eclipse.jface.viewers.AbstractTreeViewer.internalInitializeTree(AbstractTreeViewer.java:1492)
> at org.eclipse.jface.viewers.TreeViewer.internalInitializeTree(TreeViewer.java:833)
> at org.eclipse.jface.viewers.AbstractTreeViewer$5.run(AbstractTreeViewer.java:1476)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1422)
> at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:403)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1383)
> at org.eclipse.jface.viewers.AbstractTreeViewer.inputChanged(AbstractTreeViewer.java:1469)
> at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:274)
> at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1664)
> at org.jboss.tools.common.editor.XModelObjectTreeViewComponent.createControl(XModelObjectTreeViewComponent.java:90)
> at org.jboss.tools.common.editor.form.SampleTreeForm.createClientArea(SampleTreeForm.java:81)
> at org.jboss.tools.common.model.ui.forms.ExpandableForm.createControl(ExpandableForm.java:108)
> at org.jboss.tools.common.model.ui.forms.SplitFormContainer.createFirstForm(SplitFormContainer.java:79)
> at org.jboss.tools.common.model.ui.forms.SplitFormContainer.createControl(SplitFormContainer.java:103)
> at org.jboss.tools.common.model.ui.forms.DefaultFormContainer.createControl(DefaultFormContainer.java:47)
> at org.jboss.tools.common.model.ui.forms.DefaultFormPage.createFormControl(DefaultFormPage.java:94)
> at org.jboss.tools.common.editor.TreeFormPage.createFormControl(TreeFormPage.java:151)
> at org.jboss.tools.common.model.ui.forms.DefaultFormPage.createControl(DefaultFormPage.java:108)
> at org.jboss.tools.common.editor.TreeFormPage.createPartControl(TreeFormPage.java:405)
> at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:241)
> at org.eclipse.ui.part.MultiPageEditorPart.addPage(MultiPageEditorPart.java:211)
> at org.jboss.tools.common.editor.ObjectMultiPageEditor.addFormPage(ObjectMultiPageEditor.java:933)
> at org.jboss.tools.jsf.ui.editor.FacesConfigEditor.doCreatePages(FacesConfigEditor.java:59)
> at org.jboss.tools.common.editor.ObjectMultiPageEditor.createPages(ObjectMultiPageEditor.java:239)
> at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:348)
> at org.jboss.tools.common.model.ui.editor.EditorPartWrapper.createPartControl(EditorPartWrapper.java:176)
> at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:670)
> at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:465)
> at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595)
> at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:313)
> at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:180)
> at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:270)
> at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65)
> at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:473)
> at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1254)
> at org.eclipse.ui.internal.PartStack.handleDeferredEvents(PartStack.java:1222)
> at org.eclipse.ui.internal.LayoutPart.deferUpdates(LayoutPart.java:400)
> at org.eclipse.ui.internal.PartSashContainer.handleDeferredEvents(PartSashContainer.java:1409)
> at org.eclipse.ui.internal.LayoutPart.deferUpdates(LayoutPart.java:400)
> at org.eclipse.ui.internal.WorkbenchPage.handleDeferredEvents(WorkbenchPage.java:1420)
> at org.eclipse.ui.internal.WorkbenchPage.deferUpdates(WorkbenchPage.java:1410)
> at org.eclipse.ui.internal.WorkbenchPage.access$14(WorkbenchPage.java:1401)
> at org.eclipse.ui.internal.WorkbenchPage$16.runWithException(WorkbenchPage.java:3304)
> at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4041)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660)
> at org.eclipse.ui.application.WorkbenchAdvisor.openWindows(WorkbenchAdvisor.java:803)
> at org.eclipse.ui.internal.Workbench$31.runWithException(Workbench.java:1567)
> at org.eclipse.ui.internal.StartupThreading$StartupRunnable.run(StartupThreading.java:31)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4041)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3660)
> at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2548)
> at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438)
> at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> 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:369)
> 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:619)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1383)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (JBIDE-8056) Jboss 6.0 final and jboss developer studio simple application execution issue
by dee bharam (JIRA)
Jboss 6.0 final and jboss developer studio simple application execution issue
-----------------------------------------------------------------------------
Key: JBIDE-8056
URL: https://issues.jboss.org/browse/JBIDE-8056
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Reporter: dee bharam
Assignee: Rob Stryker
1) I downloaded jboss6.0 final, unziped, and place under c:
2) downloaded and installed jboss developer studio
3) created application per
http://community.jboss.org/en/tools/blog/2010/12/10/simple-cdi-hello-worl...
4) gets following on server log
13:57:58,116 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/cditest].[org.cdi.HelloServlet]] Servlet.service() for servlet org.cdi.HelloServlet threw exception: java.lang.NullPointerException
at org.cdi.HelloServlet.doGet(HelloServlet.java:32) [:]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) [:1.0.0.Final]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [:1.0.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:324) [:6.0.0.Final]
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242) [:6.0.0.Final]
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:275) [:6.0.0.Final]
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) [:6.0.0.Final]
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:181) [:6.0.0.Final]
at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.event(CatalinaContext.java:285) [:1.1.0.Final]
at org.jboss.modcluster.catalina.CatalinaContext$RequestListenerValve.invoke(CatalinaContext.java:261) [:1.1.0.Final]
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:88) [:6.0.0.Final]
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:100) [:6.0.0.Final]
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) [:6.0.0.Final]
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) [:6.0.0.Final]
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158) [:6.0.0.Final]
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) [:6.0.0.Final]
at org.jboss.web.tomcat.service.request.ActiveRequestResponseCacheValve.invoke(ActiveRequestResponseCacheValve.java:53) [:6.0.0.Final]
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:362) [:6.0.0.Final]
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:877) [:6.0.0.Final]
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:654) [:6.0.0.Final]
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951) [:6.0.0.Final]
at java.lang.Thread.run(Unknown Source) [:1.6.0_21]
5) and on brower get
HTTP Status 500 -
--------------------------------------------------------------------------------
type Exception report
message
description The server encountered an internal error () that prevented it from fulfilling this request.
exception
java.lang.NullPointerException
org.cdi.HelloServlet.doGet(HelloServlet.java:32)
javax.servlet.http.HttpServlet.service(HttpServlet.java:734)
javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
note The full stack trace of the root cause is available in the JBoss Web/3.0.0-CR1 logs.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Updated: (JBIDE-7887) Execution Plan for a query executed in Teiid is hard to find in JBDS
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-7887?page=com.atlassian.jira.plugin... ]
Brian Fitzpatrick updated JBIDE-7887:
-------------------------------------
Fix Version/s: 3.2.x
(was: 3.2.0.CR1)
Bumping to 3.2.x for now then. Thanks for the update. :)
> Execution Plan for a query executed in Teiid is hard to find in JBDS
> --------------------------------------------------------------------
>
> Key: JBIDE-7887
> URL: https://issues.jboss.org/browse/JBIDE-7887
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: teiid
> Reporter: Ramesh Reddy
> Assignee: John Doyle
> Fix For: 3.2.x
>
>
> Currently viewing of the execution plan is little cumbersome, it is not readily available as it did previous incarnation of the MetaMatrix Designer. Currently, the user needs to right click on the query and select "Teiid_7.1 --> Query Plan" see the query plan.
> When a query is executed, the statement executed has the query already associated with it, so there is no good reason for user to take yet another step before they can see the query plan. It should be automatically populated in the "Execution Plan" tab when the query is executed. Or provide tool bar button on the "SQL Results" panel, that will take user to the "Execution Plan" of the current query. In case of query plan not available this tool bar button could be greyed out.
> Since the query plan is in XML, show it in XML editor (read-only), that will let the user collapse or expand the the nodes to see and understand it, otherwise these are rather long, could be confusing to scroll.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Commented: (JBIDE-7887) Execution Plan for a query executed in Teiid is hard to find in JBDS
by John Doyle (JIRA)
[ https://issues.jboss.org/browse/JBIDE-7887?page=com.atlassian.jira.plugin... ]
John Doyle commented on JBIDE-7887:
-----------------------------------
Brian, No, not for CR1. Perhaps not for this release.
> Execution Plan for a query executed in Teiid is hard to find in JBDS
> --------------------------------------------------------------------
>
> Key: JBIDE-7887
> URL: https://issues.jboss.org/browse/JBIDE-7887
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: teiid
> Reporter: Ramesh Reddy
> Assignee: John Doyle
> Fix For: 3.2.0.CR1
>
>
> Currently viewing of the execution plan is little cumbersome, it is not readily available as it did previous incarnation of the MetaMatrix Designer. Currently, the user needs to right click on the query and select "Teiid_7.1 --> Query Plan" see the query plan.
> When a query is executed, the statement executed has the query already associated with it, so there is no good reason for user to take yet another step before they can see the query plan. It should be automatically populated in the "Execution Plan" tab when the query is executed. Or provide tool bar button on the "SQL Results" panel, that will take user to the "Execution Plan" of the current query. In case of query plan not available this tool bar button could be greyed out.
> Since the query plan is in XML, show it in XML editor (read-only), that will let the user collapse or expand the the nodes to see and understand it, otherwise these are rather long, could be confusing to scroll.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Commented: (JBIDE-7887) Execution Plan for a query executed in Teiid is hard to find in JBDS
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-7887?page=com.atlassian.jira.plugin... ]
Brian Fitzpatrick commented on JBIDE-7887:
------------------------------------------
John, is this one going to be done for CR1? I'm guessing not, but wanted to check.
> Execution Plan for a query executed in Teiid is hard to find in JBDS
> --------------------------------------------------------------------
>
> Key: JBIDE-7887
> URL: https://issues.jboss.org/browse/JBIDE-7887
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: teiid
> Reporter: Ramesh Reddy
> Assignee: John Doyle
> Fix For: 3.2.0.CR1
>
>
> Currently viewing of the execution plan is little cumbersome, it is not readily available as it did previous incarnation of the MetaMatrix Designer. Currently, the user needs to right click on the query and select "Teiid_7.1 --> Query Plan" see the query plan.
> When a query is executed, the statement executed has the query already associated with it, so there is no good reason for user to take yet another step before they can see the query plan. It should be automatically populated in the "Execution Plan" tab when the query is executed. Or provide tool bar button on the "SQL Results" panel, that will take user to the "Execution Plan" of the current query. In case of query plan not available this tool bar button could be greyed out.
> Since the query plan is in XML, show it in XML editor (read-only), that will let the user collapse or expand the the nodes to see and understand it, otherwise these are rather long, could be confusing to scroll.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months
[JBoss JIRA] Created: (JBIDE-6356) Hibernate mapping file editor sometime shows old content
by Jiri Peterka (JIRA)
Hibernate mapping file editor sometime shows old content
--------------------------------------------------------
Key: JBIDE-6356
URL: https://jira.jboss.org/browse/JBIDE-6356
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Hibernate
Affects Versions: 3.1.1
Reporter: Jiri Peterka
Fix For: 3.2.next
Sometimes old hbm.xml file is shown in Hibernate editor after class modification and hbm.xml regenerating (even after close all, and refresh).
I don't know if it's Eclipse problem or some Hibernate Tools problem but I've noticed that several times. After restart content is ok. It's question of editor content refresh, hbm.xml generation is ok and file system has proper file content.
Steps:
1. Create some POJOs
2. Create hbml.xml mapping file
3. Open hbm.xml
4. Update created POJOs
5. Delete hbml.mxl files
6. Generate hbm.xml again
7. Open generated hbm.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 3 months