Hong,
thank you for your ideas. I do not have to use a derby database in my case,
this error message should not bother me. The required datasource
"jdbc_smsrouter"
which should be used in my .ear application is already created via the admin
console (and I could successfully "ping" the connection).
I think the problem is, that GF does not yet process the sun-xxx.xml files
contained
within my .ear package (because I don't see them in the "descriptors" tab) -
that seems
to be the source of my problem.
hans
****************
http://hanzz.zapto.org
****************
> -----Ursprüngliche Nachricht-----
> Von: Hong.Zhang_at_Sun.COM [mailto:Hong.Zhang_at_Sun.COM]
> Gesendet: Mittwoch, 11. Oktober 2006 15:25
> An: users_at_glassfish.dev.java.net
> Betreff: Re: Problem when deploying EJB2.1 (CMP) .ear to glassfish
>
> Hi, Hans
> The error message seems to indicate that you didn't start
> derby database server (its default listening port is 1527).
> "jdbc/_default" is a default datasource that comes with the
> glassfish installation, so the server needs to connect to it too.
> Now for the datasource jdbc_smsrouter you used in your
> application, you will need to creat a datasource by this name
> with the server before you try to deploy the application. But
> that should be a separate problem from the error message you
> are seeing..
>
>
> - Hong
>
> Hans Prueller wrote:
>
> > Hi together,
> >
> > meanwhile I can successfully deploy my j2ee1.4 application to
> > glassfish, unfortunately I did not succeed in configurating
> a working
> > database access for the CMP beans.
> >
> > On deployment, the following message is logged into server.log:
> >
> >
> [#|2006-10-11T07:58:16.218+0200|WARNING|sun-appserver-pe9.1|javax.ente
> >
> rprise.resource.resourceadapter|_ThreadID=11;_ThreadName=Thread-31;Con
> > nection could not be allocated because: java.net.ConnectException :
> > Error opening socket to server localhost on port 1527 with message :
> > Connection refused: no further
> >
> information;_RequestID=5adceee8-665a-4419-82a4-34b8de2d8d06;|R
> AR5114 :
> > Error allocating connection : [Connection could not be allocated
> > because: java.net.ConnectException : Error opening socket to server
> > localhost on port 1527 with message : Connection refused:
> no further
> > information]|#]
> >
> >
> [#|2006-10-11T07:58:16.218+0200|WARNING|sun-appserver-pe9.1|ja
vax.enterprise.resource.jdo.codegen.ejb|_ThreadID=11;_ThreadName=Thread-31;_
RequestID=> 5adceee8-665a-4419-82a4-34b8de2d8d06;|JDO76611:
> > Cannot connect to database via JNDI name 'jdbc/__default':
> > java.sql.SQLException: Connection could not be allocated because:
> > java.net.ConnectException : Error opening socket to server
> localhost
> > on port 1527 with message : Connection refused: no further
> > information.|#]
> >
> > It seems that GlassFish attempts to use a connected with a
> JNDI name
> > "jdbc/__default". This is strange because the ejb-jar.jar
> file (within
> > the .ear) does contain a sun-ejb-jar.xml file, in which I
> configured
> > the following:
> >
> >
> > <cmp-resource>
> >
> > <jndi-name>jdbc_smsrouter</jndi-name>
> >
> > </cmp-resource>
> >
> >
> >
> > So if I understood that right, GF should try to use the
> jdbc_smsrouter
> > JNDI name and not jdbc/__default. On the GF Admin console I can see
> > the
> >
> > deployed application, on the tab "Descriptors" I do only see the
> > application.xml, ejb-jar.xml and web.xml - the sun-XXX .xml
> specific
> > descriptors are
> >
> > missing here - so I am not sure if glassfish parsed them on
> deployment.
> >
> >
> >
> > Any tips?
> >
> >
> >
> > Hans
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>