This is the driver who threw the exception, not the JBoss. So, the problem is with the system setup.
Some snippets from SQL Server docs:
"To use insensitive scrollable cursors, and perform client-side sorting of
some DatabaseMetaData ResultSets, all code bases must have access to
temporary files. If access to temporary files is not available, the driver
may throw an exception indicating that it is unable to set up a static
For JDK 1.1 environments, access to "current working directory" must be
For Java 2 environments, access to the temporary directory specified by the
VM configuration must be granted.
The following is an example of permissions being granted for the C:\TEMP
// permissions granted to all domains
// Permission to create and delete temporary files.
// Adjust the temporary directory for your environment.
permission java.io.FilePermission "C:\\TEMP\\-", "read,write,delete";
I modified the file "C:\java\JBuilderX\jdk1.4\jre\lib\security\java.policy" inserting the permissions that you talked about. But does not work yet.
Is this the correct file?
Actually we have server.policy file that by default grants all permissions.
Is the user on behalf of which you run JBoss able to execute DDL using the driver (outside JBoss)?
Yes. The user on behalf of which we run Jboss is able to excute DDL using the driver.
Is this problem can be regarded with integration of JBuilder 10 and JBoss 3.2.3?
Frankly, I don't know. Maybe there is some other cause. This is what I found in the net.