Re: [equinox-dev] equinox standalone problem
On Tue, Mar 11, 2008 at 11:34 PM, Thomas Watson <[EMAIL PROTECTED]> wrote: > > > Are you certain you are using the Thread.setDaemon(false) method? If you are > not then the threads will inherit their daemon status from the invoking > thread. If this happens to be one of the daemon framework threads then your > bundle threads will be daemon also. Yup, I figured that out by myself and this is what happened (see previous mail :-). > One quick way to find out is to run with a console and run the "threads" > command. It will tell you the daemon status of your bundle threads. Yes, that is what I did. Sorry again. regards, Karl > Tom > > > > "Karl Pauls" ---03/11/2008 05:14:20 PM---> Hi Karl, > > > > > From: > "Karl Pauls" <[EMAIL PROTECTED]> > > To: > "Equinox development mailing list" > > Date: > 03/11/2008 05:14 PM > > Subject: > Re: [equinox-dev] equinox standalone problem > > > > > > > > Hi Karl, > > > > You are running into bug > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=215730 > > :-) > > > With 3.4 M5 you can set the configuration property > > osgi.framework.activeThreadType=normal to force a non-daemon thread be > > started so that the VM does not exit when the framework is running. The > > reason you see it stay up for 30 seconds is because there is a non-daemon > > thread spinning in the background waiting for a period of inactivity > before > > persisting data. After it persists the data the thread exits and there is > no > > other non-daemon thread alive to keep the VM running. > > Well, that works but I don't really understand it. As I mentioned in > my previous mail, I actually have bundles installed that are creating > their own (non-daemon) threads so that should keep the jvm alive, no? > > Thanks a lot for this workaround! > > regards, > > Karl > > > HTH > > > > Tom > > > > > > > > "Karl Pauls" ---03/11/2008 04:04:49 PM---Hi, > > > > > > > > > > From: > > "Karl Pauls" <[EMAIL PROTECTED]> > > > > To: > > equinox-dev@eclipse.org > > > > Date: > > 03/11/2008 04:04 PM > > > > Subject: > > [equinox-dev] equinox standalone problem > > > > > > > > > > > > > Hi, > > > > I have a problem running equinox standalone. Basically, what I am > > trying to do is to run equinox without a console. The set-up is as > > follows: > > > > equinox/ > > configuration/ > > config.ini > > plugins/ > > > > > > > ../configuration/config.ini > > osgi.bundles= > > eclipse.ignoreApp=true > > osgi.noShutdown=true > > > > > java -jar org.eclipse.equinox.launcher_1.0.100.v20080303.jar -noExit > > > > The above set-up does shutdown unexpectedly after a couple of seconds > > (~ 30) on the first startup and immediately on subsequent ones. > > > > I tried with all sorts of versions of equinox (including 3.3.2 3.4.M4 > > nightly, integration) and any combination of -Dosgi.noShutdown=true > > config.ini/osgi.noShutdown=true and -noExit but to no avail. If I use > > -console everything works fine. > > > > Help would be much appreciated. > > > > regards, > > > > Karl > > > > -- > > Karl Pauls > > [EMAIL PROTECTED] > > ___ > > equinox-dev mailing list > > equinox-dev@eclipse.org > > > > https://dev.eclipse.org/mailman/listinfo/equinox-dev > > > > > > > > > > ___ > > equinox-dev mailing list > > equinox-dev@eclipse.org > > https://dev.eclipse.org/mailman/listinfo/equinox-dev > > > > > > > > -- > Karl Pauls > [EMAIL PROTECTED] > ___ > equinox-dev mailing list > equinox-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/equinox-dev > > > > > ___ > equinox-dev mailing list > equinox-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/equinox-dev > > -- Karl Pauls [EMAIL PROTECTED] ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] equinox standalone problem
Are you certain you are using the Thread.setDaemon(false) method? If you are not then the threads will inherit their daemon status from the invoking thread. If this happens to be one of the daemon framework threads then your bundle threads will be daemon also. One quick way to find out is to run with a console and run the "threads" command. It will tell you the daemon status of your bundle threads. Tom From: "Karl Pauls" <[EMAIL PROTECTED]> To: "Equinox development mailing list" Date: 03/11/2008 05:14 PM Subject:Re: [equinox-dev] equinox standalone problem > Hi Karl, > > You are running into bug > https://bugs.eclipse.org/bugs/show_bug.cgi?id=215730 :-) > With 3.4 M5 you can set the configuration property > osgi.framework.activeThreadType=normal to force a non-daemon thread be > started so that the VM does not exit when the framework is running. The > reason you see it stay up for 30 seconds is because there is a non-daemon > thread spinning in the background waiting for a period of inactivity before > persisting data. After it persists the data the thread exits and there is no > other non-daemon thread alive to keep the VM running. Well, that works but I don't really understand it. As I mentioned in my previous mail, I actually have bundles installed that are creating their own (non-daemon) threads so that should keep the jvm alive, no? Thanks a lot for this workaround! regards, Karl > HTH > > Tom > > > > "Karl Pauls" ---03/11/2008 04:04:49 PM---Hi, > > > > > From: > "Karl Pauls" <[EMAIL PROTECTED]> > > To: > equinox-dev@eclipse.org > > Date: > 03/11/2008 04:04 PM > > Subject: > [equinox-dev] equinox standalone problem > > > > > > Hi, > > I have a problem running equinox standalone. Basically, what I am > trying to do is to run equinox without a console. The set-up is as > follows: > > equinox/ > configuration/ > config.ini > plugins/ > > > > ../configuration/config.ini > osgi.bundles= > eclipse.ignoreApp=true > osgi.noShutdown=true > > > java -jar org.eclipse.equinox.launcher_1.0.100.v20080303.jar -noExit > > The above set-up does shutdown unexpectedly after a couple of seconds > (~ 30) on the first startup and immediately on subsequent ones. > > I tried with all sorts of versions of equinox (including 3.3.2 3.4.M4 > nightly, integration) and any combination of -Dosgi.noShutdown=true > config.ini/osgi.noShutdown=true and -noExit but to no avail. If I use > -console everything works fine. > > Help would be much appreciated. > > regards, > > Karl > > -- > Karl Pauls > [EMAIL PROTECTED] > ___ > equinox-dev mailing list > equinox-dev@eclipse.org > > https://dev.eclipse.org/mailman/listinfo/equinox-dev > > > > > ___ > equinox-dev mailing list > equinox-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/equinox-dev > > -- Karl Pauls [EMAIL PROTECTED] ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev <><>___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] equinox standalone problem
> > Hi Karl, > > > > You are running into bug > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=215730 > > :-) > > > With 3.4 M5 you can set the configuration property > > osgi.framework.activeThreadType=normal to force a non-daemon thread be > > started so that the VM does not exit when the framework is running. The > > reason you see it stay up for 30 seconds is because there is a non-daemon > > thread spinning in the background waiting for a period of inactivity before > > persisting data. After it persists the data the thread exits and there is > no > > other non-daemon thread alive to keep the VM running. > > Well, that works but I don't really understand it. As I mentioned in > my previous mail, I actually have bundles installed that are creating > their own (non-daemon) threads so that should keep the jvm alive, no? Darn, from the javadoc of java.lang.Thread: "The newly created thread is initially marked as being a daemon thread if and only if the thread creating it is currently marked as a daemon thread." so what is happening is that equinox starts my bundles in a daemon thread and hence, my threads end-up being daemons under equinox. In other words, one has to always call setDaemon unless one doesn't care - pff. Sorry - didn't know about that one. regards, Karl > Thanks a lot for this workaround! > > regards, > > Karl > > > > > HTH > > > > Tom > > > > > > > > "Karl Pauls" ---03/11/2008 04:04:49 PM---Hi, > > > > > > > > > > From: > > "Karl Pauls" <[EMAIL PROTECTED]> > > > > To: > > equinox-dev@eclipse.org > > > > Date: > > 03/11/2008 04:04 PM > > > > Subject: > > [equinox-dev] equinox standalone problem > > > > > > > > > > > > Hi, > > > > I have a problem running equinox standalone. Basically, what I am > > trying to do is to run equinox without a console. The set-up is as > > follows: > > > > equinox/ > > configuration/ > > config.ini > > plugins/ > > > > > > > ../configuration/config.ini > > osgi.bundles= > > eclipse.ignoreApp=true > > osgi.noShutdown=true > > > > > java -jar org.eclipse.equinox.launcher_1.0.100.v20080303.jar -noExit > > > > The above set-up does shutdown unexpectedly after a couple of seconds > > (~ 30) on the first startup and immediately on subsequent ones. > > > > I tried with all sorts of versions of equinox (including 3.3.2 3.4.M4 > > nightly, integration) and any combination of -Dosgi.noShutdown=true > > config.ini/osgi.noShutdown=true and -noExit but to no avail. If I use > > -console everything works fine. > > > > Help would be much appreciated. > > > > regards, > > > > Karl > > > > -- > > Karl Pauls > > [EMAIL PROTECTED] > > ___ > > equinox-dev mailing list > > equinox-dev@eclipse.org > > > > https://dev.eclipse.org/mailman/listinfo/equinox-dev > > > > > > > > > > ___ > > equinox-dev mailing list > > equinox-dev@eclipse.org > > https://dev.eclipse.org/mailman/listinfo/equinox-dev > > > > > > > > -- > > > Karl Pauls > [EMAIL PROTECTED] > -- Karl Pauls [EMAIL PROTECTED] ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] equinox standalone problem
> Hi Karl, > > You are running into bug > https://bugs.eclipse.org/bugs/show_bug.cgi?id=215730 :-) > With 3.4 M5 you can set the configuration property > osgi.framework.activeThreadType=normal to force a non-daemon thread be > started so that the VM does not exit when the framework is running. The > reason you see it stay up for 30 seconds is because there is a non-daemon > thread spinning in the background waiting for a period of inactivity before > persisting data. After it persists the data the thread exits and there is no > other non-daemon thread alive to keep the VM running. Well, that works but I don't really understand it. As I mentioned in my previous mail, I actually have bundles installed that are creating their own (non-daemon) threads so that should keep the jvm alive, no? Thanks a lot for this workaround! regards, Karl > HTH > > Tom > > > > "Karl Pauls" ---03/11/2008 04:04:49 PM---Hi, > > > > > From: > "Karl Pauls" <[EMAIL PROTECTED]> > > To: > equinox-dev@eclipse.org > > Date: > 03/11/2008 04:04 PM > > Subject: > [equinox-dev] equinox standalone problem > > > > > > Hi, > > I have a problem running equinox standalone. Basically, what I am > trying to do is to run equinox without a console. The set-up is as > follows: > > equinox/ > configuration/ > config.ini > plugins/ > > > > ../configuration/config.ini > osgi.bundles= > eclipse.ignoreApp=true > osgi.noShutdown=true > > > java -jar org.eclipse.equinox.launcher_1.0.100.v20080303.jar -noExit > > The above set-up does shutdown unexpectedly after a couple of seconds > (~ 30) on the first startup and immediately on subsequent ones. > > I tried with all sorts of versions of equinox (including 3.3.2 3.4.M4 > nightly, integration) and any combination of -Dosgi.noShutdown=true > config.ini/osgi.noShutdown=true and -noExit but to no avail. If I use > -console everything works fine. > > Help would be much appreciated. > > regards, > > Karl > > -- > Karl Pauls > [EMAIL PROTECTED] > ___ > equinox-dev mailing list > equinox-dev@eclipse.org > > https://dev.eclipse.org/mailman/listinfo/equinox-dev > > > > > ___ > equinox-dev mailing list > equinox-dev@eclipse.org > https://dev.eclipse.org/mailman/listinfo/equinox-dev > > -- Karl Pauls [EMAIL PROTECTED] ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Re: [equinox-dev] equinox standalone problem
Hi Karl, You are running into bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=215730 With 3.4 M5 you can set the configuration property osgi.framework.activeThreadType=normal to force a non-daemon thread be started so that the VM does not exit when the framework is running. The reason you see it stay up for 30 seconds is because there is a non-daemon thread spinning in the background waiting for a period of inactivity before persisting data. After it persists the data the thread exits and there is no other non-daemon thread alive to keep the VM running. HTH Tom From: "Karl Pauls" <[EMAIL PROTECTED]> To: equinox-dev@eclipse.org Date: 03/11/2008 04:04 PM Subject:[equinox-dev] equinox standalone problem Hi, I have a problem running equinox standalone. Basically, what I am trying to do is to run equinox without a console. The set-up is as follows: equinox/ configuration/ config.ini plugins/ > ../configuration/config.ini osgi.bundles= eclipse.ignoreApp=true osgi.noShutdown=true > java -jar org.eclipse.equinox.launcher_1.0.100.v20080303.jar -noExit The above set-up does shutdown unexpectedly after a couple of seconds (~ 30) on the first startup and immediately on subsequent ones. I tried with all sorts of versions of equinox (including 3.3.2 3.4.M4 nightly, integration) and any combination of -Dosgi.noShutdown=true config.ini/osgi.noShutdown=true and -noExit but to no avail. If I use -console everything works fine. Help would be much appreciated. regards, Karl -- Karl Pauls [EMAIL PROTECTED] ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev <><>___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
Fw: [equinox-dev] [prov] ui projects have fixes in HEAD good for I-rebuild
Pascal suggested I go ahead and tag and update the map file. So I did. susan - Forwarded by Susan Franklin McCourt/Beaverton/IBM on 03/11/2008 02:41 PM - Susan Franklin McCourt/Beaverton/IBTo: equinox-dev@eclipse.org [EMAIL PROTECTED] cc: Sent by:Subject: [equinox-dev] [prov] ui projects have fixes in HEAD good for I-rebuild equinox-dev-bounces@ eclipse.org 03/11/2008 02:18 PM Please respond to Equinox development mailing list I have released some surgical fixes to HEAD for these bugs: https://bugs.eclipse.org/bugs/show_bug.cgi?id=61 https://bugs.eclipse.org/bugs/show_bug.cgi?id=222000 The changes are in org.eclipse.equinox.p2.ui org.eclipse.equinox.p2.ui.sdk If there is a rebuild, these should be tagged and put in. They don't warrant a rebuild on their own, but they are important enough to go in. Without them, you can sometimes "lose" your update/install dialog and when you choose help>software updates, nothing happens. All of my other work today won't go in HEAD until I know someone has tagged, so please post here when things are tagged for the next rebuild. thanks, susan___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev<><>___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
RE: [equinox-dev] equinox standalone problem
Greetings Karl, When you supply a port for the console (osgi.console=), or allow it to use the default one with the -console switch, OSGi has something other than the framework to start and run. What you need is an OSGi "application" which becomes the job for which OSGi was started. The Corona subproject has actually done this and provides an extension mechanism for you to add your own. Have a look here: http://wiki.eclipse.org/Corona/GettingStarted/Platform and here: http://www.eclipse.org/corona/. Eventually, you'll want to use the new runtime project. Regards, Michael Murphree [EMAIL PROTECTED] The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Karl Pauls Sent: Tuesday, March 11, 2008 5:04 PM To: equinox-dev@eclipse.org Subject: [equinox-dev] equinox standalone problem Hi, I have a problem running equinox standalone. Basically, what I am trying to do is to run equinox without a console. The set-up is as follows: equinox/ configuration/ config.ini plugins/ > ../configuration/config.ini osgi.bundles= eclipse.ignoreApp=true osgi.noShutdown=true > java -jar org.eclipse.equinox.launcher_1.0.100.v20080303.jar -noExit The above set-up does shutdown unexpectedly after a couple of seconds (~ 30) on the first startup and immediately on subsequent ones. I tried with all sorts of versions of equinox (including 3.3.2 3.4.M4 nightly, integration) and any combination of -Dosgi.noShutdown=true config.ini/osgi.noShutdown=true and -noExit but to no avail. If I use -console everything works fine. Help would be much appreciated. regards, Karl -- Karl Pauls [EMAIL PROTECTED] ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] [prov] ui projects have fixes in HEAD good for I-rebuild
I have released some surgical fixes to HEAD for these bugs: https://bugs.eclipse.org/bugs/show_bug.cgi?id=61 https://bugs.eclipse.org/bugs/show_bug.cgi?id=222000 The changes are in org.eclipse.equinox.p2.ui org.eclipse.equinox.p2.ui.sdk If there is a rebuild, these should be tagged and put in. They don't warrant a rebuild on their own, but they are important enough to go in. Without them, you can sometimes "lose" your update/install dialog and when you choose help>software updates, nothing happens. All of my other work today won't go in HEAD until I know someone has tagged, so please post here when things are tagged for the next rebuild. thanks, susan___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] equinox standalone problem
Hi, I have a problem running equinox standalone. Basically, what I am trying to do is to run equinox without a console. The set-up is as follows: equinox/ configuration/ config.ini plugins/ > ../configuration/config.ini osgi.bundles= eclipse.ignoreApp=true osgi.noShutdown=true > java -jar org.eclipse.equinox.launcher_1.0.100.v20080303.jar -noExit The above set-up does shutdown unexpectedly after a couple of seconds (~ 30) on the first startup and immediately on subsequent ones. I tried with all sorts of versions of equinox (including 3.3.2 3.4.M4 nightly, integration) and any combination of -Dosgi.noShutdown=true config.ini/osgi.noShutdown=true and -noExit but to no avail. If I use -console everything works fine. Help would be much appreciated. regards, Karl -- Karl Pauls [EMAIL PROTECTED] ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] OSGi, RMI, stubs, and Javassist
Hi, I am fairly new to OSGi and Equinox, and I am having some issues. I am working on a project that began as Java Classic and became OSGi when I needed to incorporate OSGi bundles into this project. Several capabilities that once worked in Java Classic now no longer work. In particular, I am trying to use RMI to enable communication between my OSGi app and several non-OSGi applications. However, when I try to create a Stub for this object at runtime, I get a ClassNotFoundException on the *_Stub class. I am also experiencing problems with the ProActive library, which is a plain vanilla JAR that I manually made into an OSGi bundle. ProActive uses Javassist, a bytecode manipulator, to generate stub classes of its own. Calls within Javassist throw NoClassDefFoundException because the Javassist code uses Class.forName() which does not work properly under OSGi. Has anyone managed to get RMI and stub generation working under RMI? What about Javassist? I can provide more information upon request. Thanks, Steve THIS MESSAGE IS INTENDED FOR THE USE OF THE PERSON TO WHOM IT IS ADDRESSED. IT MAY CONTAIN INFORMATION THAT IS PRIVILEGED, CONFIDENTIAL AND EXEMPT FROM DISCLOSURE UNDER APPLICABLE LAW. If you are not the intended recipient, your use of this message for any purpose is strictly prohibited. If you have received this communication in error, please delete the message and notify the sender so that we may correct our records. ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
[equinox-dev] Equinox projects tagged for the I-Build
I tagged the projects last night, but I forgot to hit the send message ;-) The map file has been updated for the following Bug changes: + Bug 220014. [sec] Adding ability to select encryption algorithms to secure properties (FIXED) + Bug 220203. [ds] wrong invocation order of bind and activate (FIXED) + Bug 220818. [sec] Add graduated security bundles to the build (FIXED) + Bug 221473. [config] ConfigurationImpl contains broken equals() method (FIXED) + Bug 221657. Security bundles should using Import-Package for javax packages (FIXED) + Bug 222037. [ds] Cannot bind services to multiple DS factory components (FIXED) + Bug 222097. chkpii error in N20080310-0010 (FIXED) The following projects have changed: org.eclipse.equinox.security.ui org.eclipse.equinox.ds org.eclipse.equinox.security org.eclipse.equinox.security.win32.x86 org.eclipse.equinox.cm org.eclipse.equinox.security.tests org.eclipse.osgi Tom ___ equinox-dev mailing list equinox-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/equinox-dev
