Question: I have written a Java application which creates an H2 file database (1.4.184). It works fine on Windows and Ubuntu.
When I deployed it to the Red Hat server, it creates the database but is unable to connect. It just hangs and doesn't exit with any exception.
This is the bean-configuration, used by the application:

```
<bean id="dataSource" class="org.apache.commons.dbcp.BasicDataSource">  
    <property name="driverClassName"  value="org.h2.Driver"></property>  
    <property name="url" value="jdbc:h2:file:./db/h2/my_data_base"></property>
    <property name="username" value="username"></property>  
    <property name="password" value="password"></property>  
    <property name="defaultAutoCommit" value="false" />
</bean>

```

I first thought it might be something wrong with the configuration, but then I also tried out a simple connection-example [http://www.h2database.com/](http://www.h2database.com/html/tutorial.html#connecting_using_jdbc)
with the same result: When it should connect it starts hanging... (had it running already nearly an hour before terminating the process).
I also found some issue with using: auto\_server=true; but this doesn't apply in my case as I don't use it anyway.
There is also no difference on the file permissions in comparison with Ubuntu.

Probably somebody has any idea what might cause this issue?

Answer: 
No. That would be an enormous security loophole. You cannot programmatically change the client's file system.
You can do it with the [`fs` (filesystem) api](https://nodejs.org/api/fs.html) in node.js.

```
var fs = require("fs");

fs.rename("/tmp/hello", "/tmp/world", function (err) {
    if (err) {
        throw err;
    } else {
        console.log("rename complete");
    }
});

```