Re: [JPP-Devel] Data lost on system shutdown or killed java vm

[Giuseppe Aruta]

As I know both Kosmo and GvSIG save working data into a temp folder. This
makes easier to restore, at least saved informations, whenever JAVA VM is
killed.



2013/5/31 Michaël Michaud 

> Hi Matthias,
>
> Thanks to take care about this.
> > I try to fix this problem:
> >
> http://sourceforge.net/tracker/?func=detail&aid=3613871&group_id=118054&atid=679906
> > I've seen, that OJ closes without any warning if you kill the Java VM
> > with the taskmanager or on a Linux shell with the kill command too. This
> > seems to be the same as during OS shutdown. But we can catch this with a
> > Runtime.addShutdownHook(). This is simply a Thead. The Thread is
> > executed, during Java VM shutdown.
> > I've made some tests with a ShutdownHook in the WorkbenchFrame. If i
> > call the closeApplication() method (it's the same as you closing the
> > WorkbenchFrame window), then you get only a JOptionPane with the
> > possibility to exit OJ or to cancel. The problem for now is, that we do
> > not have a possibillity to stop the Java VM shutdown. This dialog makes
> > no sense here.
> > My question is, do we have a "End"-dialog which can save unsafed data
> > automatically?
> We have something close to this situation when user try to "save as" a
> project
> containing layers without datasource.
> I did not use this option while closing the application containing
> unsaved layer
> because I felt that this is not the normal way to save data (only two
> formats
> available and no possibility to choose the directory where data is saved).
>
> But for special situation where the main goal is saving, it is OK.
> To go one step further and totally cancel the dialog box, my option would
> be
> -  to save data in jml (shapefile can lost information and make problems
> with
> heterogeneous geometries)
> - to save the project in the system temp directory.
>
> Any other opinion about how to handle this situation ?
>
> Michaël
> >   Or what should we do with unsaved data in this situation?
> > I mean, that we must do fast some things, because the OS do not wait
> > infinity during shutdown. Problematic are especially new layers, without
> > a datastore (never saved before). Any "old" or previous saved layers we
> > can save automatically. Is this right in every situation? I mean, that
> > the user should make a decision. But a fast
> >
> > Please tell me your opinion.
> >
> > Matthias
> >
>
>
>
> --
> Get 100% visibility into Java/.NET code with AppDynamics Lite
> It's a free troubleshooting tool designed for production
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap2
> ___
> Jump-pilot-devel mailing list
> Jump-pilot-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>
--
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Re: [JPP-Devel] Data lost on system shutdown or killed java vm

[Matthias Scholz]

Hi,

to save the data into the system temp directory (java.io.tmpdir) is not 
a good idea. Most Linux distributions runs a clean-tmp job during system 
startup! I would prefer the users home directory (user.home). Not the 
best solution, but here we have the guaranty, that this directory is 
writeable and no data will be removed through any automatic services. 
Perhaps we can create a subdirectory "openjump_tmp" in users home and 
save the data here. On next OJ startup we can check this directory for 
data and inform the user about automatically  saved data.


Is this ok?

Matthias

As I know both Kosmo and GvSIG save working data into a temp folder. 
This makes easier to restore, at least saved informations, whenever 
JAVA VM is killed.




2013/5/31 Michaël Michaud >


Hi Matthias,

Thanks to take care about this.
> I try to fix this problem:
>

http://sourceforge.net/tracker/?func=detail&aid=3613871&group_id=118054&atid=679906
> I've seen, that OJ closes without any warning if you kill the
Java VM
> with the taskmanager or on a Linux shell with the kill command
too. This
> seems to be the same as during OS shutdown. But we can catch
this with a
> Runtime.addShutdownHook(). This is simply a Thead. The Thread is
> executed, during Java VM shutdown.
> I've made some tests with a ShutdownHook in the WorkbenchFrame. If i
> call the closeApplication() method (it's the same as you closing the
> WorkbenchFrame window), then you get only a JOptionPane with the
> possibility to exit OJ or to cancel. The problem for now is,
that we do
> not have a possibillity to stop the Java VM shutdown. This
dialog makes
> no sense here.
> My question is, do we have a "End"-dialog which can save unsafed
data
> automatically?
We have something close to this situation when user try to "save as" a
project
containing layers without datasource.
I did not use this option while closing the application containing
unsaved layer
because I felt that this is not the normal way to save data (only two
formats
available and no possibility to choose the directory where data is
saved).

But for special situation where the main goal is saving, it is OK.
To go one step further and totally cancel the dialog box, my
option would be
-  to save data in jml (shapefile can lost information and make
problems
with
heterogeneous geometries)
- to save the project in the system temp directory.

Any other opinion about how to handle this situation ?

Michaël
>   Or what should we do with unsaved data in this situation?
> I mean, that we must do fast some things, because the OS do not wait
> infinity during shutdown. Problematic are especially new layers,
without
> a datastore (never saved before). Any "old" or previous saved
layers we
> can save automatically. Is this right in every situation? I
mean, that
> the user should make a decision. But a fast
>
> Please tell me your opinion.
>
> Matthias
>



--
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel




--
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2


___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel



--

 _ __ ___ _ ___ __ _
 
  Technologieconsulting

  Matthias Scholz
  Siebigeröder Str 17a
  06308 Klostermansfeld

  T +49 34772 34150
  E m...@jammerhund.de
  W www.openjump.de
_ __ ___ _ ___ __ _

--
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2_

Re: [JPP-Devel] Data lost on system shutdown or killed java vm

[Michaël Michaud]

Hi Matthias,

This is OK for me,
I've already a plugin using ~/.OpenJUMP/myplugin
Maybe you could use  ~/.OpenJUMP/tmp instead of ~/openjump_tmp
as we can have other resources or config to store in the home directory

Michaël

Hi,

to save the data into the system temp directory (java.io.tmpdir) is 
not a good idea. Most Linux distributions runs a clean-tmp job during 
system startup! I would prefer the users home directory (user.home). 
Not the best solution, but here we have the guaranty, that this 
directory is writeable and no data will be removed through any 
automatic services. Perhaps we can create a subdirectory 
"openjump_tmp" in users home and save the data here. On next OJ 
startup we can check this directory for data and inform the user about 
automatically  saved data.


Is this ok?

Matthias

As I know both Kosmo and GvSIG save working data into a temp folder. 
This makes easier to restore, at least saved informations, whenever 
JAVA VM is killed.




2013/5/31 Michaël Michaud >


Hi Matthias,

Thanks to take care about this.
> I try to fix this problem:
>

http://sourceforge.net/tracker/?func=detail&aid=3613871&group_id=118054&atid=679906
> I've seen, that OJ closes without any warning if you kill the
Java VM
> with the taskmanager or on a Linux shell with the kill command
too. This
> seems to be the same as during OS shutdown. But we can catch
this with a
> Runtime.addShutdownHook(). This is simply a Thead. The Thread is
> executed, during Java VM shutdown.
> I've made some tests with a ShutdownHook in the WorkbenchFrame.
If i
> call the closeApplication() method (it's the same as you
closing the
> WorkbenchFrame window), then you get only a JOptionPane with the
> possibility to exit OJ or to cancel. The problem for now is,
that we do
> not have a possibillity to stop the Java VM shutdown. This
dialog makes
> no sense here.
> My question is, do we have a "End"-dialog which can save
unsafed data
> automatically?
We have something close to this situation when user try to "save
as" a
project
containing layers without datasource.
I did not use this option while closing the application containing
unsaved layer
because I felt that this is not the normal way to save data (only two
formats
available and no possibility to choose the directory where data
is saved).

But for special situation where the main goal is saving, it is OK.
To go one step further and totally cancel the dialog box, my
option would be
-  to save data in jml (shapefile can lost information and make
problems
with
heterogeneous geometries)
- to save the project in the system temp directory.

Any other opinion about how to handle this situation ?

Michaël
>   Or what should we do with unsaved data in this situation?
> I mean, that we must do fast some things, because the OS do not
wait
> infinity during shutdown. Problematic are especially new
layers, without
> a datastore (never saved before). Any "old" or previous saved
layers we
> can save automatically. Is this right in every situation? I
mean, that
> the user should make a decision. But a fast
>
> Please tell me your opinion.
>
> Matthias
>



--
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2
___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel




--
Get 100% visibility into Java/.NET code with AppDynamics Lite
It's a free troubleshooting tool designed for production
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap2


___
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel



--

  _ __ ___ _ ___ __ _
  
   Technologieconsulting

   Matthias Scholz
   Siebigeröder Str 17a
   06308 Klostermansfeld

   T +49 34772 34150
   e...@jammerhund.de
   Wwww.openjump.de
_ __ ___ _ ___ __ _


--
Get 100% visibility into Java/.NET code with AppDynamic

Re: [JPP-Devel] Data lost on system shutdown or killed java vm

[edgar . soldin]

generally the value of

  -state 
specifies the folder where OpenJUMP stores data between executions
(workbench-state.xml).
Default: JUMP_HOME or SETTINGS_HOME

parameter should be used here. currently this is either ~/.openjump or the 
OJ_FOLDER, depending on what is writable or configured.

_not_ using the system temp folder should happen with care. as files easily 
pile up there, there should be routines that clean out files when they are 
needed anymore.

..ede

On 01.06.2013 11:58, Michaël Michaud wrote:
> Hi Matthias,
> 
> This is OK for me,
> I've already a plugin using ~/.OpenJUMP/myplugin
> Maybe you could use  ~/.OpenJUMP/tmp instead of ~/openjump_tmp
> as we can have other resources or config to store in the home directory
> 
> Michaël
>> Hi,
>>
>> to save the data into the system temp directory (java.io.tmpdir) is not a 
>> good idea. Most Linux distributions runs a clean-tmp job during system 
>> startup! I would prefer the users home directory (user.home). Not the best 
>> solution, but here we have the guaranty, that this directory is writeable 
>> and no data will be removed through any automatic services. Perhaps we can 
>> create a subdirectory "openjump_tmp" in users home and save the data here. 
>> On next OJ startup we can check this directory for data and inform the user 
>> about automatically  saved data.
>>
>> Is this ok?
>>
>> Matthias
>>
>>> As I know both Kosmo and GvSIG save working data into a temp folder. This 
>>> makes easier to restore, at least saved informations, whenever JAVA VM is 
>>> killed.
>>>
>>>
>>>
>>> 2013/5/31 Michaël Michaud >> >
>>>
>>> Hi Matthias,
>>>
>>> Thanks to take care about this.
>>> > I try to fix this problem:
>>> > 
>>> http://sourceforge.net/tracker/?func=detail&aid=3613871&group_id=118054&atid=679906
>>> > I've seen, that OJ closes without any warning if you kill the Java VM
>>> > with the taskmanager or on a Linux shell with the kill command too. 
>>> This
>>> > seems to be the same as during OS shutdown. But we can catch this 
>>> with a
>>> > Runtime.addShutdownHook(). This is simply a Thead. The Thread is
>>> > executed, during Java VM shutdown.
>>> > I've made some tests with a ShutdownHook in the WorkbenchFrame. If i
>>> > call the closeApplication() method (it's the same as you closing the
>>> > WorkbenchFrame window), then you get only a JOptionPane with the
>>> > possibility to exit OJ or to cancel. The problem for now is, that we 
>>> do
>>> > not have a possibillity to stop the Java VM shutdown. This dialog 
>>> makes
>>> > no sense here.
>>> > My question is, do we have a "End"-dialog which can save unsafed data
>>> > automatically?
>>> We have something close to this situation when user try to "save as" a
>>> project
>>> containing layers without datasource.
>>> I did not use this option while closing the application containing
>>> unsaved layer
>>> because I felt that this is not the normal way to save data (only two
>>> formats
>>> available and no possibility to choose the directory where data is 
>>> saved).
>>>
>>> But for special situation where the main goal is saving, it is OK.
>>> To go one step further and totally cancel the dialog box, my option 
>>> would be
>>> -  to save data in jml (shapefile can lost information and make problems
>>> with
>>> heterogeneous geometries)
>>> - to save the project in the system temp directory.
>>>
>>> Any other opinion about how to handle this situation ?
>>>
>>> Michaël
>>> >   Or what should we do with unsaved data in this situation?
>>> > I mean, that we must do fast some things, because the OS do not wait
>>> > infinity during shutdown. Problematic are especially new layers, 
>>> without
>>> > a datastore (never saved before). Any "old" or previous saved layers 
>>> we
>>> > can save automatically. Is this right in every situation? I mean, that
>>> > the user should make a decision. But a fast
>>> >
>>> > Please tell me your opinion.
>>> >
>>> > Matthias
>>> >
>>>
>>>
>>> 
>>> --
>>> Get 100% visibility into Java/.NET code with AppDynamics Lite
>>> It's a free troubleshooting tool designed for production
>>> Get down to code-level detail for bottlenecks, with <2% overhead.
>>> Download for free and get started troubleshooting in minutes.
>>> http://p.sf.net/sfu/appdyn_d2d_ap2
>>> ___
>>> Jump-pilot-devel mailing list
>>> Jump-pilot-devel@lists.sourceforge.net 
>>> 
>>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>>>
>>>
>>>
>>>
>>> --
>>> Get 100% visibility into Java