Just tried to start up Parallels and got an error message that the Parallels service could not start – the link to this article says this is due to the last OS X update, and there’s a link to a download for an update to Parallels to address the issue.
Mounting Atari ST floppies on Ubuntu
I’m transferring some apps downloaded for my Atari ST (don’t ask) to floppies that are formatted with 80 tracks and 8 or 9 sectors, on double density disks (formatted on the ST). From what I understand these are MS-DOS readable but not exactly FAT format. Anyway, they don’t seem to mount by default on Ubuntu as it doesn’t know what format they are, but forcing a mount with this seems to work:
sudo udisks --mount /dev/fd0
seems to do the job (tip from here)
Updating log4j 1.x to 2.x
I’ve used Log4J 1.x for ages, and not even realized that the 1.x code line is not maintained any more, it seems all the activity is on 2.x as the latest maintained version of the framework.
To move from 1.x to 2.x, there’s a few changes:
If you’re using Maven for your dependencies, replace
<dependency> <groupId>log4j</groupId> <artifactId>log4j</artifactId> <version>1.2.15</version> </dependency>
with
<dependency> <groupId>org.apache.logging.log4j</groupId> <artifactId>log4j-core</artifactId> <version>2.0.2</version> </dependency> <dependency> <groupId>org.apache.logging.log4j</groupId> <artifactId>log4j-api</artifactId> <version>2.0.2</version> </dependency>
The API has changed from:
org.apache.log4j.Logger
and
Logger.getLogger()
to
org.apache.logging.log4j.Logger
and
org.apache.logging.log4j.LogManager.getLogger()
Sample xml config – use filename log4j2.xml instead of log4j.xml (or log4j.properties):
<?xml version=”1.0″ encoding=”UTF-8″?>
<Configuration>
<Appenders>
<Console name=”STDOUT” target=”SYSTEM_OUT”>
<PatternLayout pattern=”%C – %m%n”/>
</Console>
</Appenders>
<Loggers>
<Logger name=”example.logger.name” level=”debug”/>
<Root level=”debug”>
<AppenderRef ref=”STDOUT”/>
</Root>
</Loggers>
</Configuration>
Additional useful info here.
Adding a JMS Queue to Wildfly 8.x
The messaging subsystem in Wildfly is enabled in the standalone-full.xml config (not standalone.xml).
To add a new queue, search for <subsystem xmlns=”urn:jboss:domain:messaging:2.0″>, and then within the <hornetq-server> section, add a new <jms-destinations> if it doesn’t exist already, and define your queue name and JNDI lookup:
<jms-destinations>
<jms-queue name="exampleQueue">
<entry name="jms/queue/example"/>
<entry name="java:jboss/exported/jms/queue/example"/>
</jms-queue>
</jms-destinations>