I first tried to run it from the service control panel again but that didn’t help either, although I got a message from the panel saying it was running, it in fact wasn’t.

Next, I tried to run it manually from an SSH shell:

/usr/bin/perl -w /volume1/@appstore/SqueezeCenter/slimserver.pl --daemon --user admin --pidfile /volume1/@appstore/SqueezeCenter

and found out that it was simply blocking because it could not write to the log file:


Can't open /volume1/@appstore/SqueezeCenter/Logs/server.log (Permission denied) at /volume1/@appstore/SqueezeCenter/CPAN/Log/Log4perl/Appender/File.pm line 103.

Looking at the server.log file it somehow belonged to root while the slimserver was started with admin. Changing the owner of the server.log file worked fine and solved the bug.

mpg321 input.mp3 -w - | oggenc -o output.ogg -

Source post

sleep 3s; import -window root screenshot.png

Source: http://www.linux-noob.com/forums/index.php?/topic/339-how-to-take-a-screenshot-in-linux/

Thus, we decided to embed a SQLite database in the app. This worked fine as long as I was locally testing the application. However, when deploying to a production Tomcat instance I started getting these exceptions:

java.sql.SQLException: opening db: 'restfulepcis.db': Permission denied
at org.sqlite.Conn. init(Conn.java:117)
at org.sqlite.Conn. init(Conn.java:49)
at org.sqlite.JDBC.connect(JDBC.java:86)

The reason is pretty clear, on the production server I did not have permission to write to the Tomcat working directory.

I was left with two solutions:
1) have the directory where the database has to be created as a config parameter
2) find a directory that’s universally accessible from an app in an app server.
Since 1) involved user-configuration it was not an option.

There is actually a folder to which any Web app can write, the folder where the app is deployed (or at least my knowledge). The location of this folder can be found by calling:


ServletContext context = servletContext.getRealPath("/")


from a servlet. Since my app is a JAX-RS (RESTful) application I can obtain it by CDI (Contexts and Dependency Injection):

@Context
ServletContext servletContext;

/**
* Returns a representation of the EPCIS REST Adapter home resource according to the requested mime type
*
* @param context
* @return an instance of javax.ws.rs.core.Resource
*/
@GET
public Resource getRESTfulEPCIS(@Context UriInfo context) {
System.setProperty("sqlite.system.home", servletContext.getRealPath("/"));
RESTfulEPCISBusinessLogic logic = new RESTfulEPCISBusinessLogic();
return logic.getRESTfulEPCIS(context);
}


I then load the sqlite.system.home from my database manager class (which is not a Servlet) and use it as path in my database connection URI:


...
String sqliteHome = System.getProperty("sqlite.system.home");
...
private Connection getConnection() {
Connection connection = null;
try {
Class.forName(DRIVER);
connection = DriverManager.getConnection("jdbc:sqlite:" + sqliteHome + DB_NAME + ".db");
...


Note that for Apache Derby, you can make it even easier by simply setting the derby.system.home in the servlet class. Then, you do not need to read it manually from your database manager class as it is read automatically when loading the driver:

System.setProperty("derby.system.home", servletContext.getRealPath("/"));


HttpTransportSE androidHttpTransport = new HttpTransportSE(URL);
androidHttpTransport.debug = true;


and get a hold on the raw response from the service using:

String result = androidHttpTransport.responseDump;

sudo update-alternatives --config java

fuser -v -n tcp PORT

As a result your property file will be copied at the root of your packaged jar.