Recently, I had to write code to compute bias estimation for climate change data, and one of the key stats used in computing bias estimation along with its summary statistics is: the t-distribution cumulative probability density function, or tcdf for short.

In Java land, we are fortunate to have the Apache Commons Math library, which allows computation of tcdf and inverse-tcdf:
http://commons.apache.org/math/userguide/distribution.html 

Something like the following, using Apache Commons Math, will allow calculation of an inverse tcdf:

TDistribution t = new TDistributionImpl(degreeOfFreedom);
a = (t.inverseCumulativeProbability(0.975))


One can get the error: xterm-color: Unknown terminal type

The solution to this problem is to identify the terminal types supported on the remote machine.

In my case, it was vt100

Steps (on remote machine running Solaris):

> export TERM=vt100

> vi anyfile.txt

success!

“unable to open ‘/Applications/Adobe Flash Builder Burrito/sdks/4.5.0/frameworks/libs/player/9.0″

The key is to add a compiler argument like: “-target-player=10.1". For library projects, we have to set a compiler argument since the Flex GUI does not allow for specifying flash player versions.

Check out this post for the full directions: http://opensource.adobe.com/wiki/display/flexsdk/Targeting+Flash+Player+10

Java code:

Properties emailProps = new Properties();
emailProps.setProperty("mail.host", "<YOUR_SMTP_HOST>");
emailProps.setProperty("mail.debug", "true");

Session session = Session.getInstance(emailProps);
Message msg = new MimeMessage(session);


try {
msg.setSubject("<YOUR MESSAGE>");
msg.setSentDate(new Date());
msg.setFrom(InternetAddress.parse("<FROM_ADDRESS>")[0]);
msg.setRecipient(Message.RecipientType.TO,
InternetAddress.parse("<TO_ADDRESS>", false)[0]);
msg.setText(<YOUR_MESSAGE_TEXT>);
Transport.send(msg);
} catch (MessagingException e) {
e.printStackTrace();
}

Exception I was getting:
javax.mail.NoSuchProviderException: Unable to locate provider for protocol: smtp

Solution:
Include the following dependencies (maven2 example):

<dependency>
<groupId>org.apache.geronimo.javamail</groupId>
<artifactId>geronimo-javamail_1.4_mail</artifactId>
<version>1.8.1</version>
</dependency>
<dependency>
<groupId>org.apache.geronimo.specs</groupId>
<artifactId>geronimo-activation_1.1_spec</artifactId>
<version>1.1</version>
</dependency>


Here it is:

lsof -i tcp:<PORT> -Fp|tr -d p

Enjoy!


var xmlNode:XML = <node attr1="this is a test"/>
if (String(xmlNode.@attr1).length > 0)
trace("Attr1 exists");
else
trace("No Attr1 exists");

My setup:

• Snow Leopard 10.6
• Firefox 3.6.13
• Flash Player 10 debugger version
• Tomcat 6

Solution:

• Restart tomcat
• Redeploy web-application
• Shutdown and restart web-browser

• Phone call < 5 min
• Browser usage < 15 min
• Idle rest of time

It’s indeed strange that the “Android OS” is taking up the majority of battery resources and/or CPU time. Unfortunately, I can’t run ‘top’ and find out the exact process taking up CPU time, but needless to say this isn’t looking good.

The below is the shutdown issue I was facing:

> $CATALINA_HOME/bin/shutdown.sh
Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 9999; nested exception is:
java.net.BindException: Address already in use

A work-around (bad one by the way) was to just kill the catalina process:
> ps -A | grep catalina
> kill <port number>

However, I finally figured it out. Turns out switching on jmxremote (Java remote console memory monitoring) within catalina.sh was to blame. I’m not using remote monitoring anymore, so I just removed the following red entry from $CATALINA_HOME/bin/catalina.sh JAVA_OPTS line:

JAVA_OPTS=”$JAVA_OPTS -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=9999 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager”

Try that and see if it works!

In your pom.xml, within the plugins section, add the following:


<plugin>
<artifactId>maven-assembly-plugin</artifactId>
<version>2.2</version>
<configuration>
<descriptorRefs>
<descriptorRef>jar-with-dependencies</descriptorRef>
</descriptorRefs>
</configuration>
<executions>
<execution>
<id>make-assembly</id>
<phase>package</phase>
<goals>
<goal>single</goal>
</goals>
</execution>
</executions>
</plugin>


Call: mvn package, this will produce two jars, one with dependencies and one without.