Java no segments* file found (Solr)

You will receive that error from Solr when you (for example) have removed the index data, but not the index folder itself. Simply remote the folder that are supposed to contain the index data, and Solr will then recreate the folder, and the data when you start a indexing job. 🙂

Development Java

The hierarchy of the type Foo is inconsistent

You can get the error:

The hierarchy of the type *classname* is inconsistent

If you are trying to compile a class that requires another class not available. Normally due to compilation errors in the dependent classes. So fix the classes needed by the main class and try again.


Hint: “org.apache.jasper.JasperException: java.lang.NumberFormatException”

Getting the exception “org.apache.jasper.JasperException: java.lang.NumberFormatException” when developing a JavaEE-app?

If you are basing yourself on data from a query, make shure that you are doing a SELECT against the table name and NOT the individual fields!


A hint for the “Object foo is not a known entity type” errors from Glassfish

As a JavaEE-codemonkey you have perhaps noticed this error:

java.lang.IllegalArgumentException: Object: Ting@193c227 is not a known entity type.

This will occur when you have redeployed an app f.ex through Eclipse to Glassfish, the Glassfish server has not quite understood that it`s time to update its version, so what you need to do then is to simply restart the server (or domain).

Java Linux

One possible solution for Glassfish cluster node-agent startup problems

Just a quick hint for those of you who are experiencing problem with getting node-agents up and running in a Glassfish cluster.

If the problem is that the asadmin start-agent command simply times out/uses a long time to start, and even possibly returning a filenotfoundexception. The problem could be as simple as a firewall blocking traffic to/from the master-node. A quick way to check it is to simply disable the FW.

Note that if the master-node does not see the node-agent status, it is also caused by FW-issues, fix the FW and then restart the node-agent(s), then it all should work like a charm!