I have come across a rather weird scenario, not sure if anyone has seen it.
I have a sql developer version 3.xx installed and working properly for years until this morning.... when I tried to export a view of 300K+ records to an excel file. I then left sql developer but when I came back in, I can no longer start the application. No error but nothing happened. I went into sqldeveloper folder inside the application and started the application using cmd.com and this is the error (not sure if I am supposed to run it from command prompt though)
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\sqldeveloper\sqldeveloper\bin>sqldeveloper
java.awt.AWTError: Assistive Technology not found: com.sun.java.accessibility.Ac
cessBridge
at java.awt.Toolkit.loadAssistiveTechnologies(Toolkit.java:773)
at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:872)
at java.awt.Window.getToolkit(Window.java:1174)
at java.awt.Window.init(Window.java:396)
at java.awt.Window.<init>(Window.java:434)
at java.awt.Frame.<init>(Frame.java:403)
at javax.swing.JFrame.<init>(JFrame.java:202)
at oracle.ide.IdeCore$StartupWindow.<init>(IdeCore.java:1960)
at oracle.ide.IdeCore.startupImpl(IdeCore.java:1148)
at oracle.ide.Ide.startup(Ide.java:703)
at oracle.ideimpl.DefaultIdeStarter.startIde(DefaultIdeStarter.java:35)
at oracle.ideimpl.Main.start(Main.java:184)
at oracle.ideimpl.Main.main(Main.java:146)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.ide.boot.PCLMain.callMain(PCLMain.java:62)
at oracle.ide.boot.PCLMain.main(PCLMain.java:54)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.classloader.util.MainClass.invoke(MainClass.java:128)
at oracle.ide.boot.IdeLauncher.bootClassLoadersAndMain(IdeLauncher.java:
189)
at oracle.ide.boot.IdeLauncher.launchImpl(IdeLauncher.java:89)
at oracle.ide.boot.IdeLauncher.launch(IdeLauncher.java:65)
at oracle.ide.boot.IdeLauncher.main(IdeLauncher.java:54)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at oracle.ide.boot.Launcher.invokeMain(Launcher.java:713)
at oracle.ide.boot.Launcher.launchImpl(Launcher.java:115)
at oracle.ide.boot.Launcher.launch(Launcher.java:68)
at oracle.ide.boot.Launcher.main(Launcher.java:57)
Does someone have an idea of what was going on? I have tried to delete and get another copy of sqldeveloper from the Oracle site, but the situation has not improved. Is there something that I have overlooked? I believe the export did something to the application but I am not smart enough to figure out what. Your hints are highly appreciated!
try running the batch file to start it
It's probably in the same folder as the sqldeveloper.exe. It may be a Java level mismatch in which case you will be warned and asked if you want to proceed, or you can install a compatible version.
Related
The error I get is
org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed] at org.eclipse.swt.SWT.error(SWT.java:4621) at org.eclipse.swt.widgets.Display.createDisplay(Display.java:1038) at org.eclipse.swt.widgets.Display.create(Display.java:1025) at org.eclipse.swt.graphics.Device.<init>(Device.java:179) at org.eclipse.swt.widgets.Display.<init>(Display.java:590) at org.eclipse.swt.widgets.Display.<init>(Display.java:581) at org.pentaho.di.ui.spoon.Spoon.main(Spoon.java:668) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.pentaho.commons.launcher.Launcher.main(Launcher.java:92)
If I run it with root user there is no problem but when I try to run it with pentaho user I get this error. According to my research on google it is about display parameter but I could not find a way to fix it. What can I do to solve this problem?
Thanks in advance.
I'm hoping someone can point me in the right direction. I'm trying to configure a development environment for Notes 10 using Eclipse 4.6.2 (32bit on Windows 10). The plugin I'm working with works in Notes 9 compiled with Eclipse 3, and continues to work as compiled in Notes 10, but I wish to make some changes.
I've used the instructions from Mikkel Heisterberg's site and modified the VM Argument variables :
install_id = 1564665877146
rcp.home = c:\notes\framework
rcp.base_version = 10.0.0.20181128-1343
The problem is when I try and launch the plugin, the notes UI window opens with the message No LoginModules configured for NOTES, and the stack trace below in Eclipse. I've tried completely reinstalling the notes/designer installation on my machine along with eclipse. I've also tried repeating the process on a system having only the notes client, but always to the same effect. I'm guessing there is something wrong with my process, so the question is, what do I need to do to successfully get Eclipse to launch notes so I can test & debug my plugin.
Any assistance is appreciated.
Configuration location:
file:/C:/Users/sdelicata/workspace-neon/.metadata/.plugins/org.eclipse.pde.core/Notes 2/
Configuration file:
file:/C:/Users/sdelicata/workspace-neon/.metadata/.plugins/org.eclipse.pde.core/Notes 2/config.ini loaded
Install location:
file:/c:/notes/framework/eclipse
Framework located:
file:/C:/notes/framework/rcp/eclipse/plugins/org.eclipse.osgi_3.11.3.20181108-1144.jar
Framework classpath:
file:/C:/notes/framework/rcp/eclipse/plugins/org.eclipse.osgi_3.11.3.20181108-1144.jar
Debug options:
file:/C:/Windows/System32/.options not found
Time to load bundles: 22
2019/08/11 21:26:11.784 SEVERE CWPPR0101E: Could not find file C:\Windows\System32\.config\rcpinstall.properties ::class.method=com.ibm.rcp.provisioning.internal.core.ProvisioningUtils.savePropertiesFile() ::thread=Start Level: Equinox Container: 5bab7e6c-fa69-414c-8c98-843705bd127d ::loggername=com.ibm.rcp.provisioning.internal.core
2019/08/11 21:26:11.850 WARNING CLFRU0029W: Your data is not currently roaming because you started the session with a different application than the Notes client (for example, Symphony or Designer). ::class.method=com.ibm.notes.roaming.provider.operations.NotesRoamingVeto.shouldRoam() ::thread=Start Level: Equinox Container: 5bab7e6c-fa69-414c-8c98-843705bd127d ::loggername=com.ibm.notes.roaming.provider.notesadapter
Starting application: 6951
osgi> Application Started: 10164
2019/08/11 21:26:15.299 SEVERE CWPST0081E: An error occurred while trying to locate the default login context. ::class.method=com.ibm.rcp.internal.security.auth.service.DefaultLoginContextService.getLoginContext() ::thread=main ::loggername=com.ibm.rcp.internal.security.auth.service
javax.security.auth.login.LoginException: No LoginModules configured for NOTES
at javax.security.auth.login.LoginContext.init(LoginContext.java:267)
at javax.security.auth.login.LoginContext.<init>(LoginContext.java:351)
at com.ibm.rcp.internal.security.auth.service.DefaultLoginContextService.getLoginContext(DefaultLoginContextService.java:119)
at com.ibm.rcp.security.auth.service.AbstractLoginService.login(AbstractLoginService.java:112)
at com.ibm.rcp.internal.security.auth.service.DefaultLoginContextService.login(DefaultLoginContextService.java:130)
at com.ibm.rcp.platform.personality.DefaultWorkbenchWindowAdvisor.doLogin(DefaultWorkbenchWindowAdvisor.java:2683)
at com.ibm.rcp.platform.personality.DefaultWorkbenchWindowAdvisor.postWindowCreate(DefaultWorkbenchWindowAdvisor.java:2079)
at org.eclipse.ui.internal.WorkbenchWindow.setup(WorkbenchWindow.java:680)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:508)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:966)
at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:151)
at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:118)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.inject(ContextInjectionFactory.java:73)
at org.eclipse.ui.internal.Workbench.createWorkbenchWindow(Workbench.java:1534)
at org.eclipse.ui.internal.Workbench.openWorkbenchWindow(Workbench.java:2662)
at com.ibm.rcp.platform.personality.e4.DefaultWBWRenderer.processContents(DefaultWBWRenderer.java:59)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:665)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:757)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:728)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:722)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:706)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1059)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:693)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:610)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
at com.ibm.rcp.personality.framework.internal.RCPApplication.run(RCPApplication.java:71)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:508)
at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
at java.lang.reflect.Method.invoke(Method.java:508)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
2019/08/11 21:26:15.346 WARNING Keybinding conflicts occurred. They may interfere with normal accelerator operation. ::class.method=unknown ::thread=Thread-9 ::loggername=org.eclipse.ui.workbench
I just ran into this same error when using Eclipse to launch Notes 11.0. I believe it was an issue with the requires plugin dependencies. This is what I did to fix it:
upgraded to Notes 12.0
reloaded the JRE files (Prefs => Java => Installed JREs)
reloaded the plugins (Prefs => Plug-in Dev => Target Platform)
updated my VM argument variables as per the new values in \Notes\framework\rcp\rcplauncher.properties
install_id=1629781684647
rcp.base_version=10.0.0.20210507-1607
rcp.home=C:\Progra~2\IBM\Notes\framework
Reselect all run config plugins (edit Run Configuration => Plug-ins tab => Select All). I had previously set this as a subset to avoid duplicates/conflicts.
I hope this helps the next person!
When running Tycho UI tests for Eclipse on a Redhat server (6.7) via Jenkins, the Exception below occurs. I know that a graphical subsystem must be installed and running, but there seems to be something amiss with my setup. I already installed GTK via "yum groupinstall Desktop".
org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]
at org.eclipse.swt.SWT.error(SWT.java:4517)
at org.eclipse.swt.widgets.Display.createDisplay(Display.java:908)
at org.eclipse.swt.widgets.Display.create(Display.java:892)
at org.eclipse.swt.graphics.Device.<init>(Device.java:156)
at org.eclipse.swt.widgets.Display.<init>(Display.java:512)
at org.eclipse.swt.widgets.Display.<init>(Display.java:503)
at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:790)
at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:162)
at org.eclipse.ui.internal.ide.application.IDEApplication.createDisplay(IDEApplication.java:169)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:111)
at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:115)
at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
A virtual desktop must run. One can use Xvfb for this as described at http://www-01.ibm.com/support/docview.wss?uid=swg21421214. On Redhat one can use:
yum install xorg-x11-server-Xvfb
Xvfb :5 -screen 0 1280x1024x8 -fbdir /tmp &
export DISPLAY=:5
The number for the display can be chosen arbitrarily. In the Jenkins job the environment variable must be set as well (via set-env plugin).
For enabling this for all jobs a script as desribed here: https://superuser.com/questions/319040/proper-way-to-start-xvfb-on-startup-on-centos should be setup with chkconfig. Finally the environment variable DISPLAY should be made available by adding a shell script to /etc/profile.d/ which contains the sole line:
export DISPLAY=:5
During experimenting I set the default runlevel to 5 in /etc/inittab/ but I did no further research whether this is strictly necessary.
We have a project with Spring Batch & Spring Batch Admin.
Recently we got java.util.EmptyStackException while running the batch process.
After googling I got some idea of the problem and resolved it by upgrading the jettison jar from 1.1 to 1.3.2.
We did this by excluding the jettison in the spring batch core declaration in pom.xml and adding jettison as a dependency in the pom.xml.
The question we have is Is this the right way to resolve this issue?
Will there be any issue with Spring Batch because of upgrading jettison to 1.3.2?
The stack trace of the error we were getting:
Caused by: java.util.EmptyStackException
at org.codehaus.jettison.util.FastStack.peek(FastStack.java:39)
at org.codehaus.jettison.mapped.MappedXMLStreamWriter.writeEndElement(MappedXMLStreamWriter.java:200)
at com.thoughtworks.xstream.io.xml.StaxWriter.endNode(StaxWriter.java:107)
at com.thoughtworks.xstream.io.WriterWrapper.endNode(WriterWrapper.java:37)
at com.thoughtworks.xstream.io.path.PathTrackingWriter.endNode(PathTrackingWriter.java:48)
at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter$2.writeField(AbstractReflectionConverter.java:138)
at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter$2.visit(AbstractReflectionConverter.java:113)
at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:129)
at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.doMarshal(AbstractReflectionConverter.java:95)
at com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.marshal(AbstractReflectionConverter.java:54)
at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:65)
at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:78)
at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:63)
at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.writeItem(AbstractCollectionConverter.java:63)
at com.thoughtworks.xstream.converters.collections.MapConverter.marshal(MapConverter.java:58)
at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:65)
at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:78)
at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:63)
at com.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:98)
at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.marshal(AbstractTreeMarshallingStrategy.java:38)
at com.thoughtworks.xstream.XStream.marshal(XStream.java:845)
at com.thoughtworks.xstream.XStream.marshal(XStream.java:834)
at com.thoughtworks.xstream.XStream.toXML(XStream.java:815)
at com.thoughtworks.xstream.XStream.toXML(XStream.java:805)
at org.springframework.batch.core.repository.dao.XStreamExecutionContextStringSerializer.serialize(XStreamExecutionContextStringSerializer.java:43)
at org.springframework.batch.core.repository.dao.JdbcExecutionContextDao.serializeContext(JdbcExecutionContextDao.java:212)
at org.springframework.batch.core.repository.dao.JdbcExecutionContextDao.updateExecutionContext(JdbcExecutionContextDao.java:122)
at org.springframework.batch.core.repository.support.SimpleJobRepository.updateExecutionContext(SimpleJobRepository.java:188)
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.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:309)
at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:110)
at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
at $Proxy61.updateExecutionContext(Unknown Source)
at org.springframework.batch.core.job.SimpleStepHandler.handleStep(SimpleStepHandler.java:145)
at org.springframework.batch.core.job.flow.JobFlowExecutor.executeStep(JobFlowExecutor.java:61)
at org.springframework.batch.core.job.flow.support.state.StepState.handle(StepState.java:60)
at org.springframework.batch.core.job.flow.support.SimpleFlow.resume(SimpleFlow.java:144)
... 7 more
I've also recently come across this. I'm not sure if you have the full stacktrace there but in my app there was a call to:
sun.misc.Unsafe
There was a change in 2016 that broke a number of jvm langs like groovy. The jettison 1.1 is clearly not using this 'Unsafe' call which may change in JVM versions(it's not part of the normal java API's)
I want to debug the afterDataSetFilled method of a chart. When I start debugging, I am getting a dialog prompting me to enter the values of all the report parameters (two of which are datetime). No matter under which format I enter the datetime parameters, I always get the following exception:
SEVERE: Engine exception
org.eclipse.birt.report.engine.api.impl.ParameterValidationException: The type of parameter "startDate" is expected as "dateTime", not "java.lang.String".
at org.eclipse.birt.report.engine.api.impl.EngineTask.validateParameterValueType(EngineTask.java:865)
at org.eclipse.birt.report.engine.api.impl.EngineTask.validateAbstractScalarParameter(EngineTask.java:829)
at org.eclipse.birt.report.engine.api.impl.EngineTask.access$0(EngineTask.java:756)
at org.eclipse.birt.report.engine.api.impl.EngineTask$ParameterValidationVisitor.visitScalarParameter(EngineTask.java:686)
at org.eclipse.birt.report.engine.api.impl.EngineTask$ParameterVisitor.visit(EngineTask.java:1400)
at org.eclipse.birt.report.engine.api.impl.EngineTask.doValidateParameters(EngineTask.java:670)
at org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.doRun(RunAndRenderTask.java:94)
at org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.run(RunAndRenderTask.java:77)
at org.eclipse.birt.report.debug.internal.core.launcher.ReportLauncher.createReport(ReportLauncher.java:594)
at org.eclipse.birt.report.debug.internal.core.launcher.ReportLauncher.renderReport(ReportLauncher.java:541)
at org.eclipse.birt.report.debug.internal.core.launcher.ReportLauncher.run(ReportLauncher.java:455)
at org.eclipse.birt.report.debug.internal.core.launcher.ReportLauncher.main(ReportLauncher.java:104)
at org.eclipse.birt.report.debug.internal.core.ReportDebugger.start(ReportDebugger.java:39)
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:585)
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)
May 10, 2011 10:08:11 AM org.eclipse.birt.report.debug.internal.core.vm.ReportVMServer$1 run
WARNING: [Server] client disconnected
I couldn't find what was wrong. The default values I entered (in the yyyy-MM-dd HH:mm:ss format) for the report parameters are ok, and the report is generated correctly. However, when starting the debugger they are entered under a different format (MMMM d, y h:mm:ss). If I leave them like that I get the exception. If I change them to the yyyy-MM-dd HH:mm:ss format I still get the exception. Is this a known BIRT issue, or am I doing something wrong?
I was able to bypass this issue by hard-coding these values within the SQL query (and removing the datetime report parameters). But after I did that, another exception appeared:
SEVERE: Engine exception
org.eclipse.birt.report.engine.api.EngineException: Failed to initialize emitter.
at org.eclipse.birt.report.engine.emitter.EmitterUtil.getOuputStream(EmitterUtil.java:80)
at org.eclipse.birt.report.engine.emitter.html.HTMLReportEmitter.initialize(HTMLReportEmitter.java:350)
at org.eclipse.birt.report.engine.api.impl.EngineTask.initializeContentEmitter(EngineTask.java:2044)
at org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.doRun(RunAndRenderTask.java:117)
at org.eclipse.birt.report.engine.api.impl.RunAndRenderTask.run(RunAndRenderTask.java:77)
at org.eclipse.birt.report.debug.internal.core.launcher.ReportLauncher.createReport(ReportLauncher.java:594)
at org.eclipse.birt.report.debug.internal.core.launcher.ReportLauncher.renderReport(ReportLauncher.java:541)
at org.eclipse.birt.report.debug.internal.core.launcher.ReportLauncher.run(ReportLauncher.java:455)
at org.eclipse.birt.report.debug.internal.core.launcher.ReportLauncher.main(ReportLauncher.java:104)
at org.eclipse.birt.report.debug.internal.core.ReportDebugger.start(ReportDebugger.java:39)
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:585)
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)
Caused by: java.io.FileNotFoundException: /StandardOCE_PRS2_OperatorProductivity.rptdesign.html (Permission denied)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
at org.eclipse.birt.report.engine.emitter.EmitterUtil.getOuputStream(EmitterUtil.java:75)
... 22 more
Have you encountered this issue before? What do you suggest I do to fix it?
I did as suggested:
Changed to the standard 'Debug' perspective
Under the full 'Run' menu, opened 'Debug Configurations'
I changed the "Temp Folder" entry to a directory OUTSIDE my Windows User Account (ie something under the C-drive, say: C:\Temp\Birt). I created the specified directory.
Then Eclipse debugging worked.
I ran into the same FileNotFoundException as you today and I found a solution.
The reason for the exception is that the file path is absolute and tries to save a temporary file in / where it doesn't have write permission. A workaround for this is to simply create the file (/StandardOCE_PRS2_OperatorProductivity.rptdesign.html in your case. I assume you are on Linux) and make it writable by the user that runs Eclipse. That will get you past this error, but I just got another one right after that, so this wasn't a good solution for me. I think this is obviously a bug in the BIRT plugin, as it should have used /tmp for this. It even seems to be configured in the Debug Configuration, but doesn't use it.
I then tried to find out how to change the Debug configuration. Eclipse hides this from you in the Report Design perspective so I was confused for a while, but if you change to the Java perspective you will see the Debug button and the full Run menu. Open Debug Configurations from the button or the menu and you will see the configurations that the BIRT Plugin created for you earlier.
If I then run it from there it uses the /tmp directory as it should and debugging works. And now you can also play around with the Debug Configuration. Might be useful! :-)
I agree with Harrys solution.
The root cause is that the fallback to the configured temp folder is only evaluated if a Debug Configuration has been created in Eclipse. If a Debug Configuration was added for that report, the pre-filled Temp Folder works well (user's temp folder). Just create a Debug Configuration without modifying anything, and it works.
If NO Debug Configuration is present for that report, Eclipse is not using the default mentioned above. This is the bug.