Unable to configuration-tool.sh from putty - linux

I ran /opt/IBM/Worklight/shortcuts/configuration-tool.sh
I got the below error in logs.
!MESSAGE Application error
!STACK 1
org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]
at org.eclipse.swt.SWT.error(SWT.java:4387)
at org.eclipse.swt.widgets.Display.createDisplay(Display.java:914)
at org.eclipse.swt.widgets.Display.create(Display.java:900)
at org.eclipse.swt.graphics.Device.<init>(Device.java:156)
at org.eclipse.swt.widgets.Display.<init>(Display.java:498)
at org.eclipse.swt.widgets.Display.<init>(Display.java:489)
at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:669)
at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:161)
at com.ibm.worklight.config.ui.Application.start(Application.java:31)
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:353)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:629)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
at org.eclipse.equinox.launcher.Main.main(Main.java:1414)
Please help in fixing this.

The Worklight Server Configuration Tool is, as documented here, a graphical tool, that is, a program with a graphical user interface. It is not possible to run such programs through terminal emulators such as PuTTY without X option, 'ssh' without X option, 'screen', or similar.
You have two options:
Use the Worklight Server Configuration Tool through a network connection that supports a graphical user interface. Examples of such network protocols are VNC, PuTTY with X option, ssh with X option, RDP, or ssh/telnet with 'export DISPLAY' (the latter being deprecated for security reasons). For PuTTY with X option, you find some configuration recipes through a web search for "putty x11", and even a video.
Use the samples based approach for setting up a Worklight Server, without using the Worklight Server Configuration Tool. This path can be a bit more tedious, but you only need a text-mode connection to complete it.

Related

Conflicting CLASS files

In our production environment we encounter Error 500 with some XPage - using Java bean. I have traced the problem to this: when application is built/clean by one of our developers, we get this conflict in classes:
RESViewBean$Kocka(985FB00AF0EEE24BC1258028004C47FE).class
RESViewBean$Kocka.class
RESViewBean$Resource(34A92B0BA75D7267C1258028004C47FC).class
RESViewBean$Resource.class
Build/clean by other developers (including me) removes these conflicting two classes. My thought - something with source control. But said developer did not set it up, and removing application from his list of applications in Designer client (what would break such link) does not help.
What intrigues me the most is the fact, it has no influence on development server and test application on production server (in different path). But production copy of the application will result in this exception:
17.2.2017 9:38: Exception Thrown
javax.servlet.ServletException: java.lang.NoClassDefFoundError: sk/posam/iis/mrp/xsp/RESViewBean$Resource
at com.ibm.xsp.webapp.FacesServlet.handleError(FacesServlet.java:653)
at com.ibm.xsp.webapp.FacesServlet.renderErrorPage(FacesServlet.java:482)
at com.ibm.xsp.webapp.FacesServlet.service(FacesServlet.java:183)
at com.ibm.xsp.webapp.FacesServletEx.service(FacesServletEx.java:138)
at com.ibm.xsp.webapp.DesignerFacesServlet.service(DesignerFacesServlet.java:103)
at com.ibm.designer.runtime.domino.adapter.ComponentModule.invokeServlet(ComponentModule.java:588)
at com.ibm.domino.xsp.module.nsf.NSFComponentModule.invokeServlet(NSFComponentModule.java:1335)
at com.ibm.designer.runtime.domino.adapter.ComponentModule$AdapterInvoker.invokeServlet(ComponentModule.java:865)
at com.ibm.designer.runtime.domino.adapter.ComponentModule$ServletInvoker.doService(ComponentModule.java:808)
at com.ibm.designer.runtime.domino.adapter.ComponentModule.doService(ComponentModule.java:577)
at com.ibm.domino.xsp.module.nsf.NSFComponentModule.doService(NSFComponentModule.java:1319)
at com.ibm.domino.xsp.module.nsf.NSFService.doServiceInternal(NSFService.java:662)
at com.ibm.domino.xsp.module.nsf.NSFService.doService(NSFService.java:482)
at com.ibm.designer.runtime.domino.adapter.LCDEnvironment.doService(LCDEnvironment.java:357)
at com.ibm.designer.runtime.domino.adapter.LCDEnvironment.service(LCDEnvironment.java:313)
at com.ibm.domino.xsp.bridge.http.engine.XspCmdManager.service(XspCmdManager.java:272)
Caused by: java.lang.NoClassDefFoundError: sk/posam/iis/mrp/xsp/RESViewBean$Resource
at sk.posam.iis.mrp.xsp.RESViewBean.updateResources(RESViewBean.java:69)
at sk.posam.iis.mrp.xsp.RESViewBean.<init>(RESViewBean.java:28)
at java.lang.J9VMInternals.newInstanceImpl(Native Method)
at java.lang.Class.newInstance(Class.java:1688)
at java.beans.Beans.instantiate(Beans.java:189)
at java.beans.Beans.instantiate(Beans.java:80)
at com.sun.faces.config.ManagedBeanFactory$1.run(ManagedBeanFactory.java:222)
at java.security.AccessController.doPrivileged(AccessController.java:413)
at com.sun.faces.config.ManagedBeanFactory.newInstance(ManagedBeanFactory.java:216)
at com.sun.faces.application.ApplicationAssociate.createAndMaybeStoreManagedBeans(ApplicationAssociate.java:291)
at com.sun.faces.el.VariableResolverImpl.resolveVariable(VariableResolverImpl.java:135)
What can possibly create those duplicate class files?
Just a rough guess:
We had a similar issue with custom controls and Xpages. One of our developers was working from a remote location, and it turned out that multiplication of XSP elements (Xpages and custom controls but also their localised language properties) happened during replication. The tricky part in our case was, that those multiple versions where only visible in Package Explorer view.
We never really found the real cause but I tend to believe that this had to do with him having to sign elements before doing a local preview. Then during replication of any re-signed element a duplication occurred. Something like a replication conflict.
We stopped that by making our colleague transmit his design elements independent from our development dB (via mail or be replication of a separate db). Then one of us internal developers would copy the elements into our main db. Also we decided that no one in the team would work directly on the server but on a local replica instead.
A bit tedious but from then on there was no more duplication.

Struts2 jasper reports not opening in Linux

I have developed Web Application using Struts2. When I host my web application in Windows OS Jasper Reports (PDF formats) are opening correctly. But same war file if I host in Linux (RHEL OS) it is neither opening report, nor writing any logs. It will be in fetching mode only. Only for reports it is happening. JSP pages are opening correctly. Is it a OS issue or any other issue.
Some one already has posted similar question i.e. JR report is not generating on Linux using Struts 2. But no relevant answers.
I tried a lot but nothing is working out.
One instance when i stopped the operation (only once i got this) then I got following stack trace
WARNING [localhost-startStop-2] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [XXXXX] is still processing a request that has yet to finish. This is very likely to create a memory leak. You can control the time allowed for requests to finish by using the unloadDelay attribute of the standard Context implementation. Stack trace of request processing thread:
java.io.UnixFileSystem.getBooleanAttributes0(Native Method)
java.io.UnixFileSystem.getBooleanAttributes(UnixFileSystem.java:242)
java.io.File.exists(File.java:819)
net.sf.jasperreports.engine.util.JRResourcesUtil.resolveFile(JRResourcesUtil.java:283)
net.sf.jasperreports.repo.DefaultRepositoryService.getInputStream(DefaultRepositoryService.java:135)
net.sf.jasperreports.repo.InputStreamPersistenceService.load(InputStreamPersistenceService.java:48)
net.sf.jasperreports.repo.DefaultRepositoryService.getResource(DefaultRepositoryService.java:187)
net.sf.jasperreports.repo.RepositoryUtil.findInputStream(RepositoryUtil.java:304)
net.sf.jasperreports.repo.RepositoryUtil.getInputStreamFromLocation(RepositoryUtil.java:275)
net.sf.jasperreports.engine.fonts.SimpleFontExtensionHelper.loadFontFamilies(SimpleFontExtensionHelper.java:183)
net.sf.jasperreports.engine.fonts.FontExtensionsRegistry.getExtensions(FontExtensionsRegistry.java:56)net.sf.jasperreports.extensions.DefaultExtensionsRegistry.getExtensions(DefaultExtensionsRegistry.java:110)
net.sf.jasperreports.engine.util.JRStyledTextParser.<clinit>(JRStyledTextParser.java:83)
net.sf.jasperreports.engine.fill.JRBaseFiller.<init>(JRBaseFiller.java:121)
net.sf.jasperreports.engine.fill.JRVerticalFiller.<init>(JRVerticalFiller.java:88)
net.sf.jasperreports.engine.fill.JRVerticalFiller.<init>(JRVerticalFiller.java:103)
net.sf.jasperreports.engine.fill.JRVerticalFiller.<init>(JRVerticalFiller.java:61)
net.sf.jasperreports.engine.fill.JRFiller.createFiller(JRFiller.java:179)
net.sf.jasperreports.engine.fill.JRFiller.fill(JRFiller.java:108)
net.sf.jasperreports.engine.JasperFillManager.fill(JasperFillManager.java:653)
net.sf.jasperreports.engine.JasperFillManager.fill(JasperFillManager.java:569)
net.sf.jasperreports.engine.JasperFillManager.fillReport(JasperFillManager.java:915)
XYZJasperAction.execute(XYZJasperAction.java:1008)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
java.lang.reflect.Method.invoke(Method.java:483)
We were using two Tomcat server instances for 2 different web applications. When I reinstalled Apache Tomcat with single instance it was working. May be we have not set the port properly.

Websphere Startup Error

I am trying to set up workspace using Websphere 7.0 application server on RAD IDE. I am using Java 1.6
When ever i try to start my server it throws following error:
Exception in thread "main" java.lang.NoClassDefFoundError: Files
Caused by: java.lang.ClassNotFoundException: Files
at java.net.URLClassLoader.findClass(URLClassLoader.java:434)
at java.lang.ClassLoader.loadClass(ClassLoader.java:660)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:358)
at java.lang.ClassLoader.loadClass(ClassLoader.java:626)
Could not find the main class: Files. Program will exit.
What would be reason for this? Did anyone get this kind of error before.
Note: I tried googling out and people suggest try changing classpath, which i tried and didn't work.
It looks like something, somewhere is failing to quote an argument containing C:\Program Files, probably due to custom JVM configuration. If you use the -script option to bin\startServer.bat, you might be able to determine where things are going wrong. This might be a product issue, so if you can't figure it out (or you don't think your configuration is to blame), then you might consider opening a PMR with IBM.
If you are facing this issue when trying to start the server from RAD console , this might be a product issue , a quick way to solve this might be to start the server using command line see below example on how to start the server
C:\WorkFolder\WASV8.5_Install\profiles\AppSrv03\bin>startServer.bat server1 -profileName AppSrv02
Try to start in an command prompt you would see the servers starting in your RAD console as well.
C:\WorkFolder\WASV8.5_Install\profiles\AppSrv02\logs\server1\startServer.log
ADMU0128I: Starting tool with the AppSrv02 profile
ADMU3100I: Reading configuration for server: server1
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server server1 open for e-business; process id is 20484

Eclipse crashes when attempting to "Sign in to Google" on Linux using two-factor authentication

First, apologies if StackOverflow is the wrong Q&A site for this question, I'm happy to move it to another if needed...
Eclipse crashes whenever I try to sign in to my Google account in the plugin (the link in bottom left of eclipse). I can enter my email and password ok, it then loads the page for my verification code (because I use Google's two-factor authentication). After I submit my verification code, eclipse completely crashes and disappears from my desktop.
Any ideas?
Environment: Fresh install of the following:
Mint Linux 13
I have two-factor authentication enabled on my Google (apps) account.
Eclipse Indigo
Google plugin for eclipse
Update - 2012/06/27
This is the output in the console:
$ eclipse
12:26:50.336 [org.eclipse.jdt.internal.ui.text.JavaReconciler] INFO org.mortbay.log - Logging to Logger[org.mortbay.log] via org.mortbay.log.Slf4jLog
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGILL (0x4) at pc=0x00b16e62, pid=3853, tid=3077970176
#
# JRE version: 6.0_24-b24
# Java VM: OpenJDK Client VM (20.0-b12 mixed mode, sharing linux-x86 )
# Derivative: IcedTea6 1.11.1
# Distribution: Ubuntu 12.04 LTS, package 6b24-1.11.1-4ubuntu3
# Problematic frame:
# C 0x00b16e62
#
# An error report file with more information is saved as:
# /home/matt/gitrepos/OddPrints/hs_err_pid3853.log
#
# If you would like to submit a bug report, please include
# instructions how to reproduce the bug and visit:
# https://bugs.launchpad.net/ubuntu/+source/openjdk-6/
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Aborted (core dumped)
Or if you're really keen the full log is here.
Update - 2012/06/28
As suggested by #jpe, I tried updating my default browser in the eclipse config to "mozilla". This just kicked up an error saying it couldn't launch a browser and so was going to launch one externally for my lo log into. I t also gave me a box to enter the verification code. I did this but after entering the verification code it bombed out with error 400. Here is the tail of the eclipse log:
!ENTRY com.google.gdt.eclipse.login 4 0 2012-06-28 14:53:36.043
!MESSAGE Could not sign in. Make sure that you entered the correct verification code.
!STACK 0
com.google.api.client.http.HttpResponseException: 400 Bad Request
at com.google.api.client.http.HttpRequest.execute(HttpRequest.java:380)
at com.google.api.client.auth.oauth2.draft10.AccessTokenRequest.executeUnparsed(AccessTokenRequest.java:457)
at com.google.api.client.auth.oauth2.draft10.AccessTokenRequest.execute(AccessTokenRequest.java:473)
at com.google.gdt.eclipse.login.GoogleLogin.logIn(GoogleLogin.java:376)
at com.google.gdt.eclipse.login.GoogleLogin.logIn(GoogleLogin.java:312)
at com.google.gdt.eclipse.login.ui.LoginTrimContribution$1.mouseUp(LoginTrimContribution.java:102)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:219)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3588)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
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:344)
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:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
It seems to me that you stumbled upon the Incompatibility between WebKit and XULRunner's sqlite Eclipse bug. A quote from the bug report: "The only way to ensure that this error does not happen is to set the org.eclipse.swt.browser.DefaultType property."
So the above fixed the Eclipse crash as was hinted by an editet of the question. Now you seem to have stumbled upon a Google App Engine issue, perhaps this one. People say that if the time is significantly inaccurate in your computer, appengine will refuse login.
It would help if you could test the login you attempt from Eclipse using some other method from your computer.
I found the solution, at least a workaround.
I have the same problem, Ubuntu 10.04 x64, eclipse Juno on a Virtual Machine..
So, instead of using the button Sign in to Google Account in the lower end of the Eclipse window, just use the option from the G icon on the top toolbar, where you can create new projects, update etc with GWT. So: press Deploy to App Engine and sign in before doing anything. Then, you'll be logged in. Then again, Eclipse will crash, but at least the login will remain, so after you restart Eclipse, you should have your account synched with your IDE. Hope it helps, it worked for me.

Cannot remote debug IIS -- w3wp.exe is grayed out

I am trying to debug an IIS Web Service using remote debugging. Because of our domain configuration (which we CANNOT change) I get an Access is denied when remote debugging via the Default option. The only solution I've found is to switch to Remote (Native only with no authentication) option in VS 2008.
The problem is that when I connect to the remote system the w3wp.exe is grayed out and oddly enough it's the only one in the list that is. Does this have to do with the Remote choice? Is there a way around this?
I actually solved mine problem. The w3wp.exe was grayed out because I had installed Debug Diagnostics Tool on the server machine and set it up to follow IIS for crashed. Even though the program was not running it still had the "marked" the process for debugging (This might be totally wrong assumption). After removing the "markers" I could attach to the process.
So check out your services/programs if something is already attatched it self to the process. Does not solve the problem of not beeing able to debug managed code at all.
When you switch to "Native only with no authentication" mode, you're explicitly saying that you only want to debug "native" i.e. Win32 code, rather than .net code. There is, unfortunately as far as I'm aware, no way around this (I've tried! :().

Resources