Articles, notes and random thoughts on Software Development and Technology
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)
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.
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>
Here’s a quick summary of specific issues and workarounds I’ve run into so far:
This appears to be something removed in the node.js Windows installer. If you create the npm dir in the location above, this fixes this issue, and/or running the node.js prompt with admin privs in Windows. Covered here.
Error: ENOENT, no such file or directory 'c:\[some path]\package.json'“The Angular.JS tutorial steps don’t mention that you need to cd into the cloned angular-phonecat dir after you’ve grabbed it from github. Maybe this would be obvious if you’re already familiar with node.js and npm, but cd’ing into the cloned tutorial dir fixes this issue for me. Similar to this issue.
I’m not sure if this was because something was already running on port 8000 on my Windows box, but similar to the comments on the logged comments here, if you follow the steps to edit the package.json file, you can change the bind address and/or port before starting the server. Changing from 8000 to 8080 seemed to fix it for me.