I've been unhappy with the Subclipse Subversion plug-in for Eclipse. I'm going to try another plug-in: Subversive.
... until the collector arrives ...
From time to time, Eclipse throws an OutOfMemoryError, complaining that it is out of PERM GEN space. A bit of reading reveals that PERM GEN space is used as a garbage collection generation space for permanent objects -- such as pieces of classes that are never unloaded. You can get this error if you load lots of classes. To increase the size of the PERM GEN space, use:
The default is 64m.
If you are running Tomcat as a service, you will not be able to attach to it using JConsole using the 'local' protocol. You must configure it to accept remote connections, e.g.
This recipe does not perform any authentication. Also, I found out that if you have any -X Java options, they must appear last. When I tried to put the various -D settings listed above after the -X options, Tomcat (and presumably the JVM) quietly ignored them all.
When updating, ALDSP generates SQL statements like
UPDATE MY_TABLE SET MY_COLUMN='NEW VALUE' WHERE MY_ID='PRIMARY KEY' AND MY_COLUMN='OLD VALUE'
and inspects the update count to see whether a concurrency error has occurred. The set of columns that are checked in this way can be either all columns in the SDO object, only the modified columns, or a set of user-specified columns. However, it turns out that ALDSP will quietly drop columns of data types that are difficult to compare for equality. At time of writing, this set reasonably includes BLOB, CLOB, LONGVARBINARY, LONGVARCHAR, VARBINARY, and BINARY. Just as reasonably, but perhaps unintuitively, it also includes FLOAT and DOUBLE.
The list of troublesome data types was gleaned from the methods getUpdateSql() and canBeIncluded() in the class com.bea.ld.dsmediator.update.SQLGenerator.
See also the exchange on this topic in BEA's newsgroups.
- ► 2012 (27)
- ► 2011 (8)
- ► 2010 (25)
- ► 2009 (51)
- ► 2008 (78)
- ► 2007 (94)
- ▼ May 2006 (5)
- ► 2005 (58)
- ► 2004 (68)
- ► 1999 (10)