Clicking on eclipse causes the splash screen to show then the application is killed silently with no error message. The .log file has the following information ( summarized)
!ENTRY org.eclipse.ui 4 4 2012-11-09 11:33:45.323
!MESSAGE Class load Failure: 'com.google.gdt.eclipse.login.ui.LoginTrimContribution'
!ENTRY org.eclipse.ui 4 0 2012-11-09 11:33:45.323
!MESSAGE Class load Failure: 'com.google.gdt.eclipse.login.ui.LoginTrimContribution'
!STACK 1
org.eclipse.core.runtime.CoreException: Plug-in "com.google.gdt.eclipse.login" was
unable to instantiate class "com.google.gdt.eclipse.login.ui.LoginTrimContribution".
Caused by: java.lang.ExceptionInInitializerError
at com.google.gdt.eclipse.login.ui.LoginTrimContribution.<init>(LoginTrimContribution.java:129)
...
org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184)
... 51 more
Caused by: java.lang.NullPointerException
at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:187)
at com.google.api.client.auth.oauth2.draft10.AccessProtectedResource.<init>(AccessProtectedResource.java:184)
at com.google.api.client.googleapis.auth.oauth2.draft10.GoogleAccessProtectedResource.<init>(GoogleAccessProtectedResource.java:87)
at com.google.gdt.eclipse.login.GoogleLogin.loadLogin(GoogleLogin.java:628)
at com.google.gdt.eclipse.login.GoogleLogin.<clinit>(GoogleLogin.java:98)
and a bunch of other error messages revolving around com.google.gdt.eclipse.login
A google searched yielded nothing about eclipse.login. The package is not in the .metadata/.plugins directory and deleting other google packages or .properties did nothing.
Hoping someone encountered this before and has a work around. Nothing major changes to system or eclipse or Java before this error occurred other than I hadn't launched in a few weeks.
Eclipse EE Indigo
in the Eclipse software plugin folder I found that the com.google.gdt.eclipse.login package file had a version number attached to the end of the file name something like 3.03_v1 etc. I renamed this to just com.google.gdt.eclipse.login.jar and eclipse launched.
I am not sure how the file name changed and why it suddenly stopped working but that solved the issue.
Related
I'm trying to record tests on my app. I could successfully add AUT( in applications view) But when i'm to record test My App is loaded (AUT has splash screen to get credentials, after entering credentials AUT is loaded ) and i can interact with AUT, but RCPTT errors out with message
Timeout error :AUT doesn't respond.
Following is the log:
These are some parts from log.
!ENTRY org.eclipse.emf.ant 4 0 2019-10-08 09:41:24.138
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.emf.ant [146]
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.emf.codegen [147]
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.emf.codegen.ecore [148]
Unresolved requirement: Require-Bundle: org.eclipse.jdt.core; bundle-version="[3.5.0,4.0.0)"
java.lang.IllegalStateException: Workbench has not been created yet.
at org.eclipse.ui.PlatformUI.getWorkbench(PlatformUI.java:93)
Warning: validation was turned on but an org.xml.sax.ErrorHandler was not set, which is probably not what is desired. Parser will use a default ErrorHandler to print the first 0 errors. Please call the setErrorHandler method to fix this
Warning: NLS unused message: DIRView_btnCheckButton_text in: com.student.programs.ui.view.messages
Error: URI=null Line=5448: Attribute value "CVC100150" of type ID must be unique within the document.
Error: URI=null Line=6566: Attribute value "CVC102357" of type ID must be unique within the document.
Error: URI=null Line=6757: The content of element type "lists" must match "(list)+".
UPDATE:
Following is how i'm launching RCPTT IDE.
- Downloaded the RCPTT IDE from eclipse downloads
- Launching RCPTT by using exe
- Create new RCPTT project
- Add AUT to the RCPTT IDE
- start recording test This is when i see the error
The most probable reason is this: RCPTT Runtime plug-in is not being installed/activated in your AUT. Without this being active, the AUT is invisible to the RCPTT Runner.
With OSGi console of the AUT you could have tell that for sure.
I advice you to reach out to developers and find out together why runtime plug-in is not being activated. This should happen once the login screen is gone and the AUT's Workbench is displayed.
Hint: RCPTT's runtime is called Tesla, can you find a line beginning with this?
!MESSAGE Tesla server started on port
Update: I took a look at the log and it is like RCPTT IDE is installed as part of the AUT, not just the Runtime plug-in. Is this intentional? Your application will also be able to create RCPTT tests?
I am getting the following error when running Pax-Exam tests in windows. And found this issue https://ops4j1.jira.com/browse/PAXEXAM-701
Pax-version 4.7.0 and OSGi version org.eclipse.osgi-3.10.2.v20150203-1939
How can we overcome this issue?.
Caused by: org.osgi.framework.BundleException: Error while renaming bundle file to final location: C:\Users\aruna\AppData\Local\Temp\1450091333855-0\org.eclipse.osgi\5\0\bundleFile
at org.eclipse.osgi.storage.Storage.getContentFile0(Storage.java:767)
at org.eclipse.osgi.storage.Storage.getContentFile(Storage.java:743)
at org.eclipse.osgi.storage.Storage.install(Storage.java:508)
at org.eclipse.osgi.internal.framework.BundleContextImpl.installBundle(BundleContextImpl.java:146)
at org.eclipse.osgi.internal.framework.BundleContextImpl.installBundle(BundleContextImpl.java:139)
at org.ops4j.pax.exam.nat.internal.NativeTestContainer.installAndStartBundles(NativeTestContainer.java:308)
at org.ops4j.pax.exam.nat.internal.NativeTestContainer.start(NativeTestContainer.java:177)
at org.ops4j.pax.exam.spi.reactors.EagerSingleStagedReactor.setUp(EagerSingleStagedReactor.java:86)
at org.ops4j.pax.exam.spi.reactors.EagerSingleStagedReactor.beforeClass(EagerSingleStagedReactor.java:136)
at org.ops4j.pax.exam.spi.reactors.ReactorManager.beforeClass(ReactorManager.java:448)
at org.ops4j.pax.exam.testng.listener.PaxExam.runByDriver(PaxExam.java:443)
at org.ops4j.pax.exam.testng.listener.PaxExam.run(PaxExam.java:308)
at org.testng.internal.MethodInvocationHelper.invokeHookable(MethodInvocationHelper.java:212)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:652)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:845)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1153)
at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:125)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:108)
at org.testng.TestRunner.privateRun(TestRunner.java:771)
at org.testng.TestRunner.run(TestRunner.java:621)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:357)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:352)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:310)
at org.testng.SuiteRunner.run(SuiteRunner.java:259)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1199)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1124)
at org.testng.TestNG.run(TestNG.java:1032)
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:295)
at org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:84)
at org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:90)
at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203)
at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155)
at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)
What I would do is the following:
set up in your IDE a conditional breakpoint on BundleException constructor. Condition is that the message argument contains "Error while renaming"
the test should be set up to run in debug mode with waiting for debugger attach
the test should be set up to start with with file leak detector agent
start the test
attach the debugger
as soon as the breakpoint stops look for
the file name which you see in the message in the leak detector web page. There you will see the
stack of the thread which has created the file handler and you will
find your bug.
The PAX option you need will be something like this:
vmOptions("-Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=5005", "-javaagent:path/to/file-leak-detector.jar=http=19999")
If it is a PAX bug, please report it to their team.
Sometimes, after server restart all applications fail because of missing ExtLib libraries. They should be installed during HTTP startup from NSF update site. Server log shows:
HTTP JVM: CLFAD0330I: NSF Based plugins are being
installed in the OSGi runtime. For more information please consult the
log
HTTP JVM: null. For more detailed information,
please consult error-log-0.xml located
in /data/domino/workspace/logs
... repeated ~30x
Content of the error-log-0.xml is no help - fails show only as empty line. Thankfully there is another log file startup.log containing stack trace of the problem:
!ENTRY org.eclipse.osgi 4 0 2015-04-24 09:20:02.450 !MESSAGE Error
installing bundle:
osginsf:update/extlib.nsf/E7D8A0430DEAFDF2C1257B4F003FF202/com.ibm.xsp.extlib.core_8.5.3.20130315-0724.jar
!STACK 0 java.io.IOException at
com.ibm.domino.internal.protocol.osginsf.OSGiNSFUrlConnection.getInputStream(OSGiNSFUrlConnection.java:133)
at java.net.URL.openStream(URL.java:1022) at
org.eclipse.core.runtime.adaptor.EclipseStarter.installBundles(EclipseStarter.java:1105)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.loadBasicBundles(EclipseStarter.java:646)
at
org.eclipse.core.runtime.adaptor.EclipseStarter.access$1(EclipseStarter.java:623)
at
org.eclipse.core.runtime.adaptor.EclipseStarter$1.bundleChanged(EclipseStarter.java:308)
at
... stripped ...
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611) at
com.ibm.domino.http.bootstrap.osgi.LaunchRCP.startRCP(LaunchRCP.java:342)
at
com.ibm.domino.http.bootstrap.osgi.LaunchRCP.launchOSGIFramework(LaunchRCP.java:172)
at
com.ibm.domino.http.bootstrap.BootstrapOSGIClassLoader.launchOSGIFramework(BootstrapOSGIClassLoader.java:79)
at
com.ibm.domino.http.bootstrap.BootstrapOSGIClassLoader.loadClass(BootstrapOSGIClassLoader.java:63)
at java.lang.ClassLoader.loadClass(ClassLoader.java:638) at
com.ibm.domino.http.bootstrap.BootstrapClassLoader.findClass(BootstrapClassLoader.java:79)
!ENTRY org.eclipse.update.configurator 4 0 2015-04-24 09:20:02.762
!MESSAGE
D:\Lotus\Domino\data\domino\workspace.config\domino\eclipse\plugins\plugins
is not a valid plugins directory.
What catched my eye is the last line - the mentioned plugin directory does not exist (one extra '/plugins' directory).
The only workaround is to recreate update site from scratch (delete all content and reimport local update site).
BTW, I have found very old discussion, with no solution on ExtLib project site.
What is the cause of failed update? I can't tell whether IO exception is caused by wrong file path or dead URL to update site (network misconfiguration).
Problem was solved by increasing disk size for Domino binaries - it went out of space (and nobody noticed) by growth of Windows directory (Windows updates). Data and translog directories use different drives, so server was running with no "out of space" errors.
It seems IO Exception was thrown during unsuccessful disk write.
After upgrading to OLE 1.5.2.1 when I try to upload a local MARC .mrc-file via batch process I get the following error:
Batch process Failed for profile :: Test_Bib_Import
The same exact file worked fine in OLE 1.5.0-M2
Catalina.out contains the following error:
[INFO] org.kuali.ole.batch.impl.OLEBatchProcessAdhocStep - Executing Batch process type :: Bib Import
[ERROR] org.kuali.ole.batch.ingest.BatchProcessBibImport - java.lang.NullPointerException
[ERROR] org.kuali.ole.batch.helper.OLEBatchProcessDataHelper - Error while performing batch process for profile :: Test_Bib_Import
java.lang.RuntimeException: java.lang.NullPointerException
at org.kuali.ole.batch.ingest.BatchProcessBibImport.processBatch(BatchProcessBibImport.java:90)
at org.kuali.ole.batch.impl.AbstractBatchProcess.process(AbstractBatchProcess.java:87)
at org.kuali.ole.batch.impl.OLEBatchProcessAdhocStep.executeBatch(OLEBatchProcessAdhocStep.java:50)
at org.kuali.ole.batch.impl.OLEBatchProcessAdhocStep.execute(OLEBatchProcessAdhocStep.java:30)
at org.kuali.ole.sys.batch.Job.runStep(Job.java:175)
at org.kuali.ole.sys.batch.Job.execute(Job.java:121)
at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549)
Caused by: java.lang.NullPointerException
at org.kuali.ole.batch.helper.BatchBibImportHelper.processBibMarcRecord(BatchBibImportHelper.java:89)
at org.kuali.ole.batch.helper.BatchBibImportHelper.processBatch(BatchBibImportHelper.java:70)
at org.kuali.ole.batch.ingest.BatchProcessBibImport.processBatch(BatchProcessBibImport.java:152)
at org.kuali.ole.batch.ingest.BatchProcessBibImport.processBatch(BatchProcessBibImport.java:83)
... 7 more
[ERROR] org.kuali.ole.batch.impl.OLEBatchProcessAdhocStep - Error while running Batch Process Step::OLEBatchProcessAdhocStep
java.lang.Exception: Batch process Failed
at org.kuali.ole.batch.impl.AbstractBatchProcess.process(AbstractBatchProcess.java:123)
at org.kuali.ole.batch.impl.OLEBatchProcessAdhocStep.executeBatch(OLEBatchProcessAdhocStep.java:50)
at org.kuali.ole.batch.impl.OLEBatchProcessAdhocStep.execute(OLEBatchProcessAdhocStep.java:30)
at org.kuali.ole.sys.batch.Job.runStep(Job.java:175)
at org.kuali.ole.sys.batch.Job.execute(Job.java:121)
at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549)
Caused by: java.lang.RuntimeException: java.lang.NullPointerException
at org.kuali.ole.batch.ingest.BatchProcessBibImport.processBatch(BatchProcessBibImport.java:90)
at org.kuali.ole.batch.impl.AbstractBatchProcess.process(AbstractBatchProcess.java:87)
... 6 more
Caused by: java.lang.NullPointerException
at org.kuali.ole.batch.helper.BatchBibImportHelper.processBibMarcRecord(BatchBibImportHelper.java:89)
at org.kuali.ole.batch.helper.BatchBibImportHelper.processBatch(BatchBibImportHelper.java:70)
at org.kuali.ole.batch.ingest.BatchProcessBibImport.processBatch(BatchProcessBibImport.java:152)
at org.kuali.ole.batch.ingest.BatchProcessBibImport.processBatch(BatchProcessBibImport.java:83)
... 7 more
The line from which that that error is coming from suggests that the Batch Profile you are using has not been set up correctly in the database (specifically, it can't find the matching profile). One definitive indicator would be a stack trace output in catalina.out involving the getMatchingProfileObj method in the org.kuali.ole.batch.bo.OLEBatchProcessProfileBo class.
If you migrated your application code over top of an existing database without having fully migrated the data in that database correctly, this problem could result. Given that your question illustrates you used 1.5.0-M2 previously, which is a pre-release milestone, you are better off re-initializing your database and reloading your data before running batch processes with a new version of the OLE codebase.
If you already did that, then this may be fodder for a bug report.
Note that there were a lot of changes to the match/overlay part of the profiles in 1.5.2. You might want to look at how it is set up and make sure the choices apply. Match and overlay was added for holdings and items and is being tested, this makes for more complicated possible choices. YOu could try setting it to no match, just add the bib and see if that works. As long as your file is utf8, not MARC8 encoding it shoul dload
I'm using WSO2 ESB 4.8.1 with JDK 1.7.0_67 x64 on windows 7 x64.
I'm deploying carbon application(.car) using any method:
maven car deploy plugin
web admin console
CarbonAppUploader web service
First deployment succeeds but log file contains:
CarbonAppUploader temp file: C:\Java\WSO2ES~1.1\bin\..\tmp\carbonappsuploads\first-esb_1.0.0.car deletion failed, scheduled deletion on server exit.
Second deployment of same car (name and version) fails with exception in logs (see below)
I Apologize for localized error message but generally it says cant overwrite this file.
If you check, it's actually locked for deletion. Looks like CarbonAppUploader class didn't properly close InputStream.
Strangely enough this bug is not reproducible in unix (centos)
Question to WSO2: do you plan to fix that?
Question to all: Did you meet such bug and how did you solve it?
exception stack trace (partially)
TID: [0] [ESB] [2014-08-18 22:04:58,254] ERROR {org.wso2.carbon.application.upload.CarbonAppUploader} - Error occurred while uploading Carbon App artifacts {org.wso2.carbon.application.upload.CarbonAppUploader}
java.io.FileNotFoundException: C:\Java\WSO2ES~1.1\bin\..\tmp\carbonappsuploads\first-esb_1.0.0.car (Запрошенную операцию нельзя выполнить для файла с открытой пользователем сопоставленной секцией)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.<init>(FileOutputStream.java:221)
at java.io.FileOutputStream.<init>(FileOutputStream.java:171)
at org.wso2.carbon.application.upload.CarbonAppUploader.writeResource(CarbonAppUploader.java:78)
at org.wso2.carbon.application.upload.CarbonAppUploader.uploadApp(CarbonAppUploader.java:55)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
I checked out source code from svn, fixed bug myself. If anybody experiencing same issue, you may download sources and compiled jar from https://wso2.org/jira/browse/ESBJAVA-3272
Hopefully this bug fix will be included in next releases