You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Craig Johannsen <cj...@shaw.ca> on 2004/11/16 06:40:16 UTC
Geronimo :: Derby :: Connector compile error
Doing a maven m:build in a clean geronimo directory, I checked that a
recent tranql-connector-1.0-SNAPSHOT.jar has been downloaded into the
.maven repository. Yet the build fails because the
org.apache.geronimo.derby.connector.DerbyXAManagedConnectionFactory.setExceptionSorterClass
function is not found. Maybe this is related to Aaron's problem "TranQL
DB Problem in M3" (14 Nov 04) where he couldn't load the
ExceptionSorterClass. I have a "deja vu" feeling about this one --
we've seen it before?
+----------------------------------------
| Executing default Geronimo :: Derby :: Connector
| Memory: 32M/48M
+----------------------------------------
Attempting to download tranql-connector-1.0-SNAPSHOT.jar.
war:install:
build:end:
[copy] Copying 1 file to /home/craigj/geronimo/etc
Plugin 'maven-deploy-plugin' in project 'Geronimo :: Derby :: Connector'
is not available
build:start:
default:
rar:init:
rar:rar:
java:prepare-filesystem:
java:compile:
[depend] Deleted 0 out of date files in 0 seconds
[echo] Compiling to
/home/craigj/geronimo/modules/derby-connector/target/classes
[javac] Compiling 1 source file to
/home/craigj/geronimo/modules/derby-connector/target/classes
/home/craigj/geronimo/modules/derby-connector/src/java/org/apache/geronimo/derby/connector/DerbyXAManagedConnectionFactory.java:15:
cannot resolve symbol
symbol : method setExceptionSorterClass (java.lang.String)
location: class
org.apache.geronimo.derby.connector.DerbyXAManagedConnectionFactory
setExceptionSorterClass(NoExceptionsAreFatalSorter.class.getName());
^
1 error
BUILD FAILED
File......
/home/craigj/.maven/cache/maven-multiproject-plugin-1.3.1/plugin.jelly
Element... maven:reactor
Line...... 217
Column.... 9
Unable to obtain goal [default] --
/home/craigj/.maven/cache/maven-java-plugin-1.4/plugin.jelly:53:48:
<ant:javac> Compile failed; see the compiler error output for details.
Total time: 13 minutes 44 seconds
Finished at: Mon Nov 15 20:45:55 PST 2004
============================================================
Here is the offending code in DerbyXAManagedConnectionFactory:
public DerbyXAManagedConnectionFactory() throws
IllegalAccessException, InstantiationException, ClassNotFoundException {
super(new EmbeddedXADataSource());
setExceptionSorterClass(NoExceptionsAreFatalSorter.class.getName());
}
In the parent class of DerbyXAManagedConnectionFactory,
AbstractXADataSourceMCF, there is a getExceptionSorterClass, but not a
setExceptionSorterClass, although there is this function:
public void setExceptionSorter(ExceptionSorter exceptionSorter) {
this.exceptionSorter = exceptionSorter;
}
Re: Geronimo :: Derby :: Connector compile error
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
Actually, it looks like I checked in a change to add the deployer
a little while ago. So perhaps you hadn't done a full rebuild since then
or something. In any case, the very latest builds should start the
runtime deployer by default.
Aaron
On Tue, 16 Nov 2004, Craig Johannsen wrote:
> Thanks, Aaron. That worked.
>
> The server was started with:
> java -jar $GERONIMO_HOME/bin/server.jar org/apache/geronimo/DebugConsole
> org/apache/geronimo/RuntimeDeployer
>
> The Hello session bean was deployed with:
> java -jar $GERONIMO_HOME/bin/deployer.jar --user system --password
> manager deploy hello.jar
>
> Which resulted in the server reporting:
> 14:09:11,322 INFO [LocalConfigStore:config-store] Installed
> configuration hello in location 74
> 14:09:11,400 INFO [ConfigurationManagerImpl] Loaded Configuration
> geronimo.config:name="hello"
> 14:09:11,967 INFO [Configuration] Started configuration hello
> 14:09:12,172 INFO [GenericEJBContainer] GenericEJBContainer
> 'geronimo.server:EJBModule=hello,J2EEApplication=null,J2EEServer=geronimo,j2eeType=StatelessSessionBean,name=Hello'started
>
> cj
>
> Aaron Mulder wrote:
>
> > The deployer hierarchy was changed but unfortunately now no
> >deployer is started by default. I think if you add
> >org/apache/geronimo/RuntimeDeployer to the server command line then the
> >deployer should work again.
> >
> >Aaron
> >
> >On Tue, 16 Nov 2004, Craig Johannsen wrote:
> >
> >
> >
>
>
Re: Geronimo :: Derby :: Connector compile error
Posted by Craig Johannsen <cj...@shaw.ca>.
Thanks, Aaron. That worked.
The server was started with:
java -jar $GERONIMO_HOME/bin/server.jar org/apache/geronimo/DebugConsole
org/apache/geronimo/RuntimeDeployer
The Hello session bean was deployed with:
java -jar $GERONIMO_HOME/bin/deployer.jar --user system --password
manager deploy hello.jar
Which resulted in the server reporting:
14:09:11,322 INFO [LocalConfigStore:config-store] Installed
configuration hello in location 74
14:09:11,400 INFO [ConfigurationManagerImpl] Loaded Configuration
geronimo.config:name="hello"
14:09:11,967 INFO [Configuration] Started configuration hello
14:09:12,172 INFO [GenericEJBContainer] GenericEJBContainer
'geronimo.server:EJBModule=hello,J2EEApplication=null,J2EEServer=geronimo,j2eeType=StatelessSessionBean,name=Hello'started
cj
Aaron Mulder wrote:
> The deployer hierarchy was changed but unfortunately now no
>deployer is started by default. I think if you add
>org/apache/geronimo/RuntimeDeployer to the server command line then the
>deployer should work again.
>
>Aaron
>
>On Tue, 16 Nov 2004, Craig Johannsen wrote:
>
>
>
Re: Geronimo :: Derby :: Connector compile error
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
The deployer hierarchy was changed but unfortunately now no
deployer is started by default. I think if you add
org/apache/geronimo/RuntimeDeployer to the server command line then the
deployer should work again.
Aaron
On Tue, 16 Nov 2004, Craig Johannsen wrote:
> Thanks, David.
>
> maven m:update m:build worked with just a few hiccups. Had to go into
> derby-connector and run "maven" to build the rar.
>
> Some security tests that were failing yesterday succeeded today.
>
> My Hello session bean doesn't deploy to the running server using the
> following command:
> java -jar $GERONIMO_HOME/bin/deployer.jar --user system --password
> manager deploy hello.jar
> The deployer reports:
> Deployment failed
> Server reports: No deployer present in kernel
>
> Manually specifying org/apache/geronimo/DeployerSystem in the server
> startup command doesn't seem to help.
>
> The hello.jar had previously been deployed successfully using the command:
> java -jar $GERONIMO_HOME/bin/deployer.jar distribute hello.jar
> It subsequently runs OK.
>
> Cheers,
> Craig
>
> David Jencks wrote:
>
> > We had some classloader problems with the original handling of the
> > exception sorters, and it looks like perhaps only a partial fix got
> > applied.
> >
> > I've just updated both the geronimo derby-connector and
> > tranql-connector with a version I like. If you rebuild both it
> > should work.
> >
> > I can't remember what our process on this is supposed to be. Should
> > I update the openejb maven repo by hand with the updated tranql
> > connector jar or is this done automatically?
> >
> > thanks
> > david jencks
> >
>
>
Re: Geronimo :: Derby :: Connector compile error
Posted by Craig Johannsen <cj...@shaw.ca>.
Thanks, David.
maven m:update m:build worked with just a few hiccups. Had to go into
derby-connector and run "maven" to build the rar.
Some security tests that were failing yesterday succeeded today.
My Hello session bean doesn't deploy to the running server using the
following command:
java -jar $GERONIMO_HOME/bin/deployer.jar --user system --password
manager deploy hello.jar
The deployer reports:
Deployment failed
Server reports: No deployer present in kernel
Manually specifying org/apache/geronimo/DeployerSystem in the server
startup command doesn't seem to help.
The hello.jar had previously been deployed successfully using the command:
java -jar $GERONIMO_HOME/bin/deployer.jar distribute hello.jar
It subsequently runs OK.
Cheers,
Craig
David Jencks wrote:
> We had some classloader problems with the original handling of the
> exception sorters, and it looks like perhaps only a partial fix got
> applied.
>
> I've just updated both the geronimo derby-connector and
> tranql-connector with a version I like. If you rebuild both it
> should work.
>
> I can't remember what our process on this is supposed to be. Should
> I update the openejb maven repo by hand with the updated tranql
> connector jar or is this done automatically?
>
> thanks
> david jencks
>
Re: Geronimo :: Derby :: Connector compile error
Posted by David Jencks <dj...@gluecode.com>.
We had some classloader problems with the original handling of the
exception sorters, and it looks like perhaps only a partial fix got
applied.
I've just updated both the geronimo derby-connector and
tranql-connector with a version I like. If you rebuild both it should
work.
I can't remember what our process on this is supposed to be. Should I
update the openejb maven repo by hand with the updated tranql connector
jar or is this done automatically?
thanks
david jencks
On Nov 15, 2004, at 10:01 PM, sissonj@insession.com wrote:
> It looks like it may be related to Alan's recent change..
> http://nagoya.apache.org/eyebrowse/ReadMsg?
> listName=scm@geronimo.apache.org&msgNo=5663
>
> Seems that org.tranql.connector.jdbc.AbstractXADataSourceMCF.java
> hasn't
> been changed to have a setExceptionSorterClass method. Currently it
> has:
>
> public String getExceptionSorterClass() {
> return exceptionSorter.getClass().getName();
> }
>
> public void setExceptionSorter(ExceptionSorter exceptionSorter) {
> this.exceptionSorter = exceptionSorter;
> }
>
> John
>
> Craig Johannsen <cj...@shaw.ca> wrote on 16/11/2004 04:40:16 PM:
>
>> Doing a maven m:build in a clean geronimo directory, I checked that a
>> recent tranql-connector-1.0-SNAPSHOT.jar has been downloaded into the
>> .maven repository. Yet the build fails because the
>> org.apache.geronimo.derby.connector.DerbyXAManagedConnectionFactory.
>> setExceptionSorterClass
>> function is not found. Maybe this is related to Aaron's problem
>> "TranQL
>
>> DB Problem in M3" (14 Nov 04) where he couldn't load the
>> ExceptionSorterClass. I have a "deja vu" feeling about this one --
>> we've seen it before?
>>
>> +----------------------------------------
>> | Executing default Geronimo :: Derby :: Connector
>> | Memory: 32M/48M
>> +----------------------------------------
>> Attempting to download tranql-connector-1.0-SNAPSHOT.jar.
>>
>> war:install:
>>
>>
>> build:end:
>>
>> [copy] Copying 1 file to /home/craigj/geronimo/etc
>> Plugin 'maven-deploy-plugin' in project 'Geronimo :: Derby ::
>> Connector'
>
>> is not available
>> build:start:
>>
>> default:
>> rar:init:
>>
>> rar:rar:
>> java:prepare-filesystem:
>>
>> java:compile:
>> [depend] Deleted 0 out of date files in 0 seconds
>> [echo] Compiling to
>> /home/craigj/geronimo/modules/derby-connector/target/classes
>> [javac] Compiling 1 source file to
>> /home/craigj/geronimo/modules/derby-connector/target/classes
>> /home/craigj/geronimo/modules/derby-
>>
> connector/src/java/org/apache/geronimo/derby/connector/
> DerbyXAManagedConnectionFactory.
>> java:15:
>> cannot resolve symbol
>> symbol : method setExceptionSorterClass (java.lang.String)
>> location: class
>> org.apache.geronimo.derby.connector.DerbyXAManagedConnectionFactory
>> setExceptionSorterClass(NoExceptionsAreFatalSorter.class.getName());
>> ^
>> 1 error
>>
>> BUILD FAILED
>> File......
>> /home/craigj/.maven/cache/maven-multiproject-plugin-1.3.1/plugin.jelly
>> Element... maven:reactor
>> Line...... 217
>> Column.... 9
>> Unable to obtain goal [default] --
>> /home/craigj/.maven/cache/maven-java-plugin-1.4/plugin.jelly:53:48:
>> <ant:javac> Compile failed; see the compiler error output for details.
>> Total time: 13 minutes 44 seconds
>> Finished at: Mon Nov 15 20:45:55 PST 2004
>> ============================================================
>> Here is the offending code in DerbyXAManagedConnectionFactory:
>> public DerbyXAManagedConnectionFactory() throws
>> IllegalAccessException, InstantiationException,
>> ClassNotFoundException {
>> super(new EmbeddedXADataSource());
>> setExceptionSorterClass(NoExceptionsAreFatalSorter.class.getName());
>> }
>>
>> In the parent class of DerbyXAManagedConnectionFactory,
>> AbstractXADataSourceMCF, there is a getExceptionSorterClass, but not a
>> setExceptionSorterClass, although there is this function:
>> public void setExceptionSorter(ExceptionSorter exceptionSorter) {
>> this.exceptionSorter = exceptionSorter;
>> }
>>
>>
>>
>
Re: Geronimo :: Derby :: Connector compile error
Posted by si...@insession.com.
It looks like it may be related to Alan's recent change..
http://nagoya.apache.org/eyebrowse/ReadMsg?listName=scm@geronimo.apache.org&msgNo=5663
Seems that org.tranql.connector.jdbc.AbstractXADataSourceMCF.java hasn't
been changed to have a setExceptionSorterClass method. Currently it has:
public String getExceptionSorterClass() {
return exceptionSorter.getClass().getName();
}
public void setExceptionSorter(ExceptionSorter exceptionSorter) {
this.exceptionSorter = exceptionSorter;
}
John
Craig Johannsen <cj...@shaw.ca> wrote on 16/11/2004 04:40:16 PM:
> Doing a maven m:build in a clean geronimo directory, I checked that a
> recent tranql-connector-1.0-SNAPSHOT.jar has been downloaded into the
> .maven repository. Yet the build fails because the
> org.apache.geronimo.derby.connector.DerbyXAManagedConnectionFactory.
> setExceptionSorterClass
> function is not found. Maybe this is related to Aaron's problem "TranQL
> DB Problem in M3" (14 Nov 04) where he couldn't load the
> ExceptionSorterClass. I have a "deja vu" feeling about this one --
> we've seen it before?
>
> +----------------------------------------
> | Executing default Geronimo :: Derby :: Connector
> | Memory: 32M/48M
> +----------------------------------------
> Attempting to download tranql-connector-1.0-SNAPSHOT.jar.
>
> war:install:
>
>
> build:end:
>
> [copy] Copying 1 file to /home/craigj/geronimo/etc
> Plugin 'maven-deploy-plugin' in project 'Geronimo :: Derby :: Connector'
> is not available
> build:start:
>
> default:
> rar:init:
>
> rar:rar:
> java:prepare-filesystem:
>
> java:compile:
> [depend] Deleted 0 out of date files in 0 seconds
> [echo] Compiling to
> /home/craigj/geronimo/modules/derby-connector/target/classes
> [javac] Compiling 1 source file to
> /home/craigj/geronimo/modules/derby-connector/target/classes
> /home/craigj/geronimo/modules/derby-
>
connector/src/java/org/apache/geronimo/derby/connector/DerbyXAManagedConnectionFactory.
> java:15:
> cannot resolve symbol
> symbol : method setExceptionSorterClass (java.lang.String)
> location: class
> org.apache.geronimo.derby.connector.DerbyXAManagedConnectionFactory
> setExceptionSorterClass(NoExceptionsAreFatalSorter.class.getName());
> ^
> 1 error
>
> BUILD FAILED
> File......
> /home/craigj/.maven/cache/maven-multiproject-plugin-1.3.1/plugin.jelly
> Element... maven:reactor
> Line...... 217
> Column.... 9
> Unable to obtain goal [default] --
> /home/craigj/.maven/cache/maven-java-plugin-1.4/plugin.jelly:53:48:
> <ant:javac> Compile failed; see the compiler error output for details.
> Total time: 13 minutes 44 seconds
> Finished at: Mon Nov 15 20:45:55 PST 2004
> ============================================================
> Here is the offending code in DerbyXAManagedConnectionFactory:
> public DerbyXAManagedConnectionFactory() throws
> IllegalAccessException, InstantiationException, ClassNotFoundException {
> super(new EmbeddedXADataSource());
> setExceptionSorterClass(NoExceptionsAreFatalSorter.class.getName());
> }
>
> In the parent class of DerbyXAManagedConnectionFactory,
> AbstractXADataSourceMCF, there is a getExceptionSorterClass, but not a
> setExceptionSorterClass, although there is this function:
> public void setExceptionSorter(ExceptionSorter exceptionSorter) {
> this.exceptionSorter = exceptionSorter;
> }
>
>
>