Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Remote Application Platform (RAP) » problems deploying RAP application using RAP 1.2 and Galileo
problems deploying RAP application using RAP 1.2 and Galileo [message #137736] Thu, 25 June 2009 04:19 Go to next message
David Donohue is currently offline David DonohueFriend
Messages: 104
Registered: July 2009
Senior Member
Hello, I had a nice deployment mechanism for my standalone, Jetty powered
RAP 1.1 app. I was using the methodology described
here:http://eclipsesource.com/blogs/2007/11/28/rap-deploymen t-part-1-deploying-your-application-with-jetty/

I have tried to recreate using RAP 1.2 and Eclipse 3.5, structure but
running into difficulties
(1) I cannot get new launcher jars to work in Windows. I get
NoClassDefFoundError for the laucher classes. When i use older launcher
jars the app launches fine.
But I can work around this by using the older launcher bundles:
org.eclipse.equinox.launcher.win32.win32.x86_1.0.2.R331_v200 71019
org.eclipse.equinox.launcher_1.0.1.R33x_v20070828.jar

(2) Using latest Jetty jars (instead of org.mortbay.jetty 5.1, which was
working fine). My app starts up and the bundles are active, but I do not
see in the console any evidence that Jetty is running, and it does not
respond to requests.

Thanks for your help!
David Donohue
Re: problems deploying RAP application using RAP 1.2 and Galileo [message #137832 is a reply to message #137736] Thu, 25 June 2009 11:03 Go to previous messageGo to next message
David Donohue is currently offline David DonohueFriend
Messages: 104
Registered: July 2009
Senior Member
Here are my bundles running.

id State Bundle
0 ACTIVE org.eclipse.osgi_3.5.0.v20090520
71 ACTIVE org.eclipse.equinox.common_3.5.0.v20090520-1800
72 ACTIVE org.eclipse.update.configurator_3.3.0.v20090312
73 ACTIVE org.eclipse.rap.ui_1.2.0.20090616-1425
74 ACTIVE org.eclipse.equinox.http.jetty_2.0.0.v20090520-1800
75 ACTIVE org.inqle.ui.rap_1.0.0
76 <<LAZY>> com.ibm.icu.base_4.0.1.v20090415
77 RESOLVED javax.servlet_2.5.0.v200806031605
78 RESOLVED org.apache.commons.logging_1.0.4.v200904062259
79 <<LAZY>> org.eclipse.core.boot_3.1.100.v20080218
80 RESOLVED org.eclipse.core.commands_3.5.0.I20090525-2000
81 <<LAZY>> org.eclipse.core.contenttype_3.4.0.v20090429-1800
82 RESOLVED org.eclipse.core.databinding.beans_1.2.0.I20090525-2000
83 <<LAZY>>
org.eclipse.core.databinding.observable_1.2.0.I20090604-2000
84 <<LAZY>>
org.eclipse.core.databinding.property_1.2.0.I20090526-2000
85 <<LAZY>> org.eclipse.core.databinding_1.2.0.I20090604-2000
86 <<LAZY>> org.eclipse.core.expressions_3.4.100.v20090429-1800
87 ACTIVE org.eclipse.core.jobs_3.4.100.v20090429-1800
88 ACTIVE
org.eclipse.core.runtime.compatibility.auth_3.2.100.v2009041 3
89 RESOLVED
org.eclipse.core.runtime.compatibility.registry_3.2.200.v200 90429-1800
Master=99
90 ACTIVE org.eclipse.core.runtime_3.5.0.v20090525
91 ACTIVE org.eclipse.equinox.app_1.2.0.v20090520-1800
94 RESOLVED
org.eclipse.equinox.http.registry_1.0.200.v20090520-1800
95 ACTIVE org.eclipse.equinox.http.servlet_1.0.200.v20090520-1800
96 RESOLVED
org.eclipse.equinox.launcher.win32.win32.x86_1.0.2.R331_v200 71019
Master=97
97 RESOLVED org.eclipse.equinox.launcher_1.0.1.R33x_v20070828
Fragments=96
98 ACTIVE org.eclipse.equinox.preferences_3.2.300.v20090520-1800
99 ACTIVE org.eclipse.equinox.registry_3.4.100.v20090520-1800
Fragments=89
100 RESOLVED org.eclipse.osgi.services_3.2.0.v20090520-1800
102 RESOLVED org.eclipse.rap.jface.databinding_1.2.0.20090616-1425
103 ACTIVE org.eclipse.rap.jface_1.2.0.20090616-1425
104 RESOLVED org.eclipse.rap.rwt.q07_1.2.0.20090616-1425
Master=105
105 RESOLVED org.eclipse.rap.rwt_1.2.0.20090616-1425
Fragments=104
106 ACTIVE org.eclipse.rap.ui.workbench_1.2.0.20090616-1425
108 RESOLVED org.eclipse.rwt.widgets.upload_1.0.0
110 RESOLVED org.inqle.agent_1.0.0
111 RESOLVED org.inqle.core.extensions_1.0.0
112 RESOLVED org.inqle.core_1.0.0
Fragments=117
113 RESOLVED org.inqle.data.rdf.jenabean_1.0.0
114 RESOLVED org.inqle.data.sampling_1.0.0
115 <<LAZY>> org.inqle.experiment.rapidminer_1.0.0
116 RESOLVED org.inqle.http.lookup_1.0.0
117 RESOLVED org.inqle.log4j.properties_1.0.0
Master=112
119 RESOLVED org.mortbay.jetty.server_6.1.15.v200905151201
120 RESOLVED org.mortbay.jetty.util_6.1.15.v200905182336
Re: problems deploying RAP application using RAP 1.2 and Galileo [message #137846 is a reply to message #137736] Thu, 25 June 2009 11:08 Go to previous messageGo to next message
Rüdiger Herrmann is currently offline Rüdiger HerrmannFriend
Messages: 581
Registered: July 2009
Senior Member
Hi David,

just some random ideas:
* did you update the config.ini / re-run the ConfigIniCreator? There
are some new bundles in 1.2
* try to "verify" the feature. Create a feature-based product and
let it reference your feature. There is a "Validate" button in the
top-left corner of the product editor
* do you see any exceptions (start with -consolelog)?

HTH
Rüdiger

David Donohue wrote:
> Hello, I had a nice deployment mechanism for my standalone, Jetty
> powered RAP 1.1 app. I was using the methodology described
> here:http://eclipsesource.com/blogs/2007/11/28/rap-deploymen t-part-1-deploying-your-application-with-jetty/
>
>
> I have tried to recreate using RAP 1.2 and Eclipse 3.5, structure but
> running into difficulties
> (1) I cannot get new launcher jars to work in Windows. I get
> NoClassDefFoundError for the laucher classes. When i use older launcher
> jars the app launches fine.
> But I can work around this by using the older launcher bundles:
> org.eclipse.equinox.launcher.win32.win32.x86_1.0.2.R331_v200 71019
> org.eclipse.equinox.launcher_1.0.1.R33x_v20070828.jar
>
> (2) Using latest Jetty jars (instead of org.mortbay.jetty 5.1, which was
> working fine). My app starts up and the bundles are active, but I do
> not see in the console any evidence that Jetty is running, and it does
> not respond to requests.
>
> Thanks for your help!
> David Donohue
>
Re: problems deploying RAP application using RAP 1.2 and Galileo [message #138023 is a reply to message #137846] Thu, 25 June 2009 21:24 Go to previous messageGo to next message
David Donohue is currently offline David DonohueFriend
Messages: 104
Registered: July 2009
Senior Member
Rüdiger,
Thanks for your time and help!

I have not updated config.ini but I manually start the relevalt Jetty
bundles and that does not change anything. Do you still think generating
config.ini using the product would help? I am unfamiliar with the Product
Configuration in general. Do you recommend using it?

I did as you said and my feature project validates with no errors.
I always start with -consolelog and no errors.

Here is what I see in the browser.
HTTP ERROR 404
Problem accessing /inqle. Reason:
ProxyServlet: /inqle
Powered by Jetty://

When I try to start bundle org.eclipse.rap.ui.workbench, I get
java.lang.NullPointerException
at
org.eclipse.rap.ui.internal.branding.BrandingExtension.readB ody(BrandingExtension.java:213)
at
org.eclipse.rap.ui.internal.branding.BrandingExtension.readB randing(BrandingExtension.java:94)
at
org.eclipse.rap.ui.internal.branding.BrandingExtension.read( BrandingExtension.java:72)
at
org.eclipse.ui.internal.WorkbenchPlugin$3.addingService(Work benchPlugin.java:1093)
...

I started all other bundles and Jetty still will not respond.

I diag org.mortbay.jetty.server and get this
osgi> diag 119
update@plugins/org.mortbay.jetty.server_6.1.15.v200905151201.jar [119]
Direct constraints which are unresolved:
Missing imported package javax.servlet.jsp_0.0.0.
Missing imported package org.apache.jasper.servlet_0.0.0.
Missing imported package org.mortbay.jetty.handler.management_0.0.0.

I diag org.mortbay.jetty.util and get this
osgi> diag 120
update@plugins/org.mortbay.jetty.util_6.1.15.v200905182336/ [120]
Direct constraints which are unresolved:
Missing imported package org.slf4j_1.3.0.

Could the missing SLF4J explain the lack of logging from Jetty?

Many thanks,
David Donohue
Re: problems deploying RAP application using RAP 1.2 and Galileo [message #138067 is a reply to message #138023] Fri, 26 June 2009 05:06 Go to previous messageGo to next message
David Donohue is currently offline David DonohueFriend
Messages: 104
Registered: July 2009
Senior Member
I tried adding every single available bundle to my feature project and
deploying that. Except the 2 launcher bundles - these fail to launch on
Windows.

My bundles are mostly running. I tried 2 methods of running the app:
(1) java -Dorg.osgi.framework.bootdelegation=* -jar
org.eclipse.osgi_3.5.0.v20090520.jar -configuration config-linux
-consoleLog -debug -clean -console -dev -vmargs -server -Xmx256m

This gives short message in the console, no errors
C:\dave_work\inqle\dist\INQLE3>java -Dorg.osgi.framework.bootdelegation=* -jar
org.eclipse.osgi_3.5.0.v2009052
0.jar -configuration config-linux -consoleLog -debug -clean -console -dev
-vmargs -server -Xmx256m
Debug options:
file:/C:/dave_work/inqle/dist/INQLE3/.options not found

(2) eclipse -console -consolelog -debug -dev -vmargs -Xmx256m -server
This gives longer message, but no indication that Jetty is started and
listening on port whatever

Start VM: -Xmx256m
-server
-Djava.class.path=C:\dave_work\inqle\dist\INQLE3\plugins\org .eclipse.equinox.launcher_1.0.1.R33x_v20070828.jar

-os win32
-ws win32
-arch x86
-showsplash
-launcher C:\dave_work\inqle\dist\INQLE3\eclipse.exe
-name Eclipse
--launcher.library
C:\dave_work\inqle\dist\INQLE3\plugins\org.eclipse.equinox.l auncher.win32.win32.x86_1.0.2.R
331_v20071019\eclipse_1021.dll
-startup
C:\dave_work\inqle\dist\INQLE3\plugins\org.eclipse.equinox.l auncher_1.0.1.R33x_v20070828.jar
-console
-consolelog
-debug
-dev
-vm C:\Java\jdk1.6.0_13\bin\..\jre\bin\client\jvm.dll
-vmargs
-Xmx256m
-server
-Djava.class.path=C:\dave_work\inqle\dist\INQLE3\plugins\org .eclipse.equinox.launcher_1.0.1.R33x_v20070828.jar

Install location:
file:/c:/dave_work/inqle/dist/INQLE3/
Configuration file:
file:/c:/dave_work/inqle/dist/INQLE3/configuration/config.in i loaded
Configuration location:
file:/c:/dave_work/inqle/dist/INQLE3/configuration/
Framework located:

file:/c:/dave_work/inqle/dist/INQLE3/plugins/org.eclipse.osg i_3.5.0.v20090520.jar
Framework classpath:

file:/c:/dave_work/inqle/dist/INQLE3/plugins/org.eclipse.osg i_3.5.0.v20090520.jar
Splash location:
null
Debug options:
file:/C:/dave_work/inqle/dist/INQLE3/.options not found

osgi> Time to load bundles: 91
Re: problems deploying RAP application using RAP 1.2 and Galileo [message #138201 is a reply to message #138067] Fri, 26 June 2009 12:49 Go to previous messageGo to next message
David Donohue is currently offline David DonohueFriend
Messages: 104
Registered: July 2009
Senior Member
I think i found my problem. Due to an error message i had seen at one
point, i renamed my entry point from "default" to something else. (I
think the error message arose when i accidentally ran the same app twice,
so i go a message about multiple "default" entry points).
So in the end the only aberrant things i had to do to get my RAP 1.1
application to run using RAP 1.2 & Eclipse 3.5 jars:
(1) Do not use with either of the 2 newer launcher bundles. Rather, use
the older 2 launcher bundles (see earlier in this thread for those 2
bundles).
(2) add this to config.ini: org.eclipse.equinox.http.registry@4:start
Thanks,
David
Re: problems deploying RAP application using RAP 1.2 and Galileo [message #138224 is a reply to message #138023] Fri, 26 June 2009 13:06 Go to previous message
Rüdiger Herrmann is currently offline Rüdiger HerrmannFriend
Messages: 581
Registered: July 2009
Senior Member
David Donohue wrote:
> Rüdiger,
> Thanks for your time and help!
>
> I have not updated config.ini but I manually start the relevalt Jetty
> bundles and that does not change anything. Do you still think
> generating config.ini using the product would help? I am unfamiliar
> with the Product Configuration in general. Do you recommend using it?

There was a misunderstanding. I only mentioned the product
configuration because it offers a way to validate the feature. If
some of the bundles in the feature are missing required bundles or
such things, that would surface before trying to run the incomplete
feature.

>
> I did as you said and my feature project validates with no errors.
> I always start with -consolelog and no errors.
>
> Here is what I see in the browser.
> HTTP ERROR 404
> Problem accessing /inqle. Reason:
> ProxyServlet: /inqle
> Powered by Jetty://
>
> When I try to start bundle org.eclipse.rap.ui.workbench, I get
> java.lang.NullPointerException
> at
> org.eclipse.rap.ui.internal.branding.BrandingExtension.readB ody(BrandingExtension.java:213)
>
> at
> org.eclipse.rap.ui.internal.branding.BrandingExtension.readB randing(BrandingExtension.java:94)
>
> at
> org.eclipse.rap.ui.internal.branding.BrandingExtension.read( BrandingExtension.java:72)
>
> at
> org.eclipse.ui.internal.WorkbenchPlugin$3.addingService(Work benchPlugin.java:1093)
>
> ...
>
Here we go! To me this very likely the reason why your application
doesn't run.
Most likely the file that is specified in the body attribute of the
branding does not exist or isn't deployed.

> I started all other bundles and Jetty still will not respond.
>
> I diag org.mortbay.jetty.server and get this
> osgi> diag 119
> update@plugins/org.mortbay.jetty.server_6.1.15.v200905151201.jar [119]
> Direct constraints which are unresolved:
> Missing imported package javax.servlet.jsp_0.0.0.
> Missing imported package org.apache.jasper.servlet_0.0.0.
> Missing imported package org.mortbay.jetty.handler.management_0.0.0.
>
> I diag org.mortbay.jetty.util and get this
> osgi> diag 120
> update@plugins/org.mortbay.jetty.util_6.1.15.v200905182336/ [120]
> Direct constraints which are unresolved:
> Missing imported package org.slf4j_1.3.0.
>
> Could the missing SLF4J explain the lack of logging from Jetty?
>
> Many thanks,
> David Donohue
>
Previous Topic:[ANN] RAP 1.2 released
Next Topic:Combo Widget
Goto Forum:
  


Current Time: Thu Apr 25 13:13:26 GMT 2024

Powered by FUDForum. Page generated in 0.03331 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top