JRegexpTester

Logged In: YES
user_id=1094733

Hello,

I will change the message adding a better explanation and I
will improve the code with your advice. T
hat will be into the next release.

Thank you.

Cheers, Alain.

Logged In: YES
user_id=314806

Alain,

You are right, the problem is in multiple HSQLDB. I have
HSQLDB 1.8.0.1 already running in "HSQL Database Engine
Server" mode under Tomcat with "sa" and "". Killing Tomcat
and removing that application from Tomcat can JRegexpTester
to run.

Hmmm, but this is not good solution ;-) HSQLDB has "HSQL
Database Engine In-Memory" and "HSQL Database Engine
Standalone" modes (see HSQLDB documentation), which can
prevent such colision AFAIK. You are also using quite
ancient (old) version of HSQLDB - 1.7.1, which maybe does
not allow suggested aproaches.

JRegexpTester is nice tool anyway. Thank You for it.

Stepan

Logged In: YES
user_id=1094733

Hello Stepan,

This problem occurs during the hsqldb connection (
src/JRegexpTester.java) when an "sqlexception" is thrown.
This part of code can perhaps be improved. I have used
hsqldb as simple as possible ( no password, default
user "sa") in order to save all contexts. I am using windows
XP "family" at home too.

Try to kill all bachgroung JVMs on your PC (processes
= "javaw.exe" after a simple control+alt+del) and relaunch
JRegexpTester that will be perhaps enough.

Cheers, Alain.

try {
conn = DriverManager.getConnection
("jdbc:hsqldb:testregexp", // filenames
"sa", // username
""); // password
} catch (SQLException e1) {
JOptionPane optionPane = new JOptionPane(
"JRegexpTester is running yet, this process will shutdown !",
JOptionPane.ERROR_MESSAGE,
JOptionPane.DEFAULT_OPTION);
optionPane.createDialog(frame2, "Alert").show();
frame2.dispose();
System.exit(1);
}