Yes, I do see all sun-XXX.xml if I deploy our test app in the GF admin,
so please check logs for other warnings.
But what might be wrong - the sun-ejb-jar.xml version is set to
sun-ejb-jar_2_0-0.dtd, which is quite old. Our test uses
<!DOCTYPE sun-ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Sun ONE Application
Server 8.0 EJB 2.1//EN"
"
http://www.sun.com/software/sunone/appserver/dtds/sun-ejb-jar_2_1-0.dtd">
Check if it makes a difference.
thanks,
-marina
Hans Prueller wrote:
> thank you for your help.
>
> find the application descriptors attached to this mail.
>
> can you tell me if I should see the sun-XXX.xml files in the GF Admin
> console? If not, it would be good if these are added to the admin console
> view because this should ease error search...
>
> thanks in advance,
> hans
>
> PS: the sun-cmp-mappings.xml is only for testing reasons, it's not complete
> yet.
>
> ****************
>
> http://hanzz.zapto.org
>
> ****************
>
>
>
>>-----Ursprüngliche Nachricht-----
>>Von: Marina.Vatkina_at_Sun.COM [mailto:Marina.Vatkina_at_Sun.COM]
>>Gesendet: Mittwoch, 11. Oktober 2006 09:27
>>An: users_at_glassfish.dev.java.net
>>Betreff: Re: Problem when deploying EJB2.1 (CMP) .ear to glassfish
>>
>>Hi Hans,
>>
>>This is strange. Can you send us the sun-ejb-jar.xml?
>>
>>thanks,
>>-marina
>>
>>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
>>
>>
>>------------------------------------------------------------------------
>>
>><?xml version="1.0" encoding="UTF-8"?>
>><!DOCTYPE sun-ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Sun ONE Application Server 7.0 EJB 2.0//EN" "http://www.sun.com/software/sunone/appserver/dtds/sun-ejb-jar_2_0-0.dtd">
>>
>><!-- Generated by XDoclet -->
>>
>><sun-ejb-jar>
>>
>> <!--
>> To add any role mappings, add an Unparsed XML Entity file to your XDoclet
>> merge directory called sunone-role-mappings.ent that contains the
>> <role-mapping> elements.
>> <!ELEMENT role-mapping (role-name, role-impl)>
>> <!ELEMENT role-impl (group*, user*)>
>> N.B. This is an Unparsed XML Entity file, rather than an XML Document,
>> since if there are multiple mappings it will not be well-formed.
>> -->
>>
>> <enterprise-beans>
>>
>> <ejb>
>> <ejb-name>MessageRouterBean</ejb-name>
>>
>> <ejb-ref>
>> <ejb-ref-name>ejb/Subscriber</ejb-ref-name>
>> <jndi-name>SubscriberBeanLocal</jndi-name>
>> </ejb-ref>
>>
>> <ejb-ref>
>> <ejb-ref-name>ejb/Instance</ejb-ref-name>
>> <jndi-name>InstanceBeanLocal</jndi-name>
>> </ejb-ref>
>>
>> <ejb-ref>
>> <ejb-ref-name>ejb/RejectedMessage</ejb-ref-name>
>> <jndi-name>RejectedMessageBeanLocal</jndi-name>
>> </ejb-ref>
>>
>> <ejb-ref>
>> <ejb-ref-name>ejb/MtMessage</ejb-ref-name>
>> <jndi-name>MtMessageBeanLocal</jndi-name>
>> </ejb-ref>
>>
>> <ejb-ref>
>> <ejb-ref-name>ejb/MoMessage</ejb-ref-name>
>> <jndi-name>MoMessageBeanLocal</jndi-name>
>> </ejb-ref>
>>
>> <ejb-ref>
>> <ejb-ref-name>ejb/MailService</ejb-ref-name>
>> <jndi-name>MailServiceBeanLocal</jndi-name>
>> </ejb-ref>
>>
>> </ejb>
>>
>> <ejb>
>> <ejb-name>RejectedMessageBean</ejb-name>
>>
>> <cmp>
>>
>> </cmp>
>>
>> </ejb>
>>
>> <ejb>
>> <ejb-name>MoMessageBean</ejb-name>
>>
>> <cmp>
>>
>> </cmp>
>>
>> </ejb>
>>
>> <ejb>
>> <ejb-name>MailServiceBean</ejb-name>
>>
>> <resource-ref>
>> <res-ref-name>mail/MailSession</res-ref-name>
>> <jndi-name></jndi-name>
>>
>> </resource-ref>
>>
>> </ejb>
>>
>> <ejb>
>> <ejb-name>SubscriberBean</ejb-name>
>>
>> <cmp>
>>
>> </cmp>
>>
>> </ejb>
>>
>> <ejb>
>> <ejb-name>InstanceBean</ejb-name>
>>
>> <cmp>
>>
>> </cmp>
>>
>> </ejb>
>>
>> <ejb>
>> <ejb-name>DataManagerBean</ejb-name>
>>
>> <ejb-ref>
>> <ejb-ref-name>ejb/Subscriber</ejb-ref-name>
>> <jndi-name>SubscriberBeanLocal</jndi-name>
>> </ejb-ref>
>>
>> <ejb-ref>
>> <ejb-ref-name>ejb/Instance</ejb-ref-name>
>> <jndi-name>InstanceBeanLocal</jndi-name>
>> </ejb-ref>
>>
>> <ejb-ref>
>> <ejb-ref-name>ejb/RejectedMessage</ejb-ref-name>
>> <jndi-name>RejectedMessageBeanLocal</jndi-name>
>> </ejb-ref>
>>
>> <ejb-ref>
>> <ejb-ref-name>ejb/MtMessage</ejb-ref-name>
>> <jndi-name>MtMessageBeanLocal</jndi-name>
>> </ejb-ref>
>>
>> <ejb-ref>
>> <ejb-ref-name>ejb/MoMessage</ejb-ref-name>
>> <jndi-name>MoMessageBeanLocal</jndi-name>
>> </ejb-ref>
>>
>> </ejb>
>>
>> <ejb>
>> <ejb-name>MtMessageBean</ejb-name>
>>
>> <cmp>
>>
>> </cmp>
>>
>> </ejb>
>>
>> <!--
>> To add any persistence manager descriptors, put an XML Document named
>> sunone-pm-descriptors.xml in your XDoclet merge directory containing the
>> <pm-descriptors> element.
>> -->
>>
>> <cmp-resource>
>> <jndi-name>jdbc_smsrouter</jndi-name>
>> </cmp-resource>
>>
>> </enterprise-beans>
>></sun-ejb-jar>
>>
>>
>>------------------------------------------------------------------------
>>
>><?xml version="1.0" encoding="UTF-8"?>
>><sun-cmp-mappings>
>><sun-cmp-mapping>
>> <schema>SMSRouter</schema>
>> <entity-mapping>
>> <ejb-name>InstanceBean</ejb-name>
>> <table-name>InstanceBean_</table-name>
>> <cmp-field-mapping>
>> <field-name>id</field-name>
>> <column-name>InstanceBean_.id_</column-name>
>> </cmp-field-mapping>
>> <cmp-field-mapping>
>> <field-name>type</field-name>
>> <column-name>InstanceBean_.type_</column-name>
>> </cmp-field-mapping>
>> <cmp-field-mapping>
>> <field-name>host</field-name>
>> <column-name>InstanceBean_.host_</column-name>
>> </cmp-field-mapping>
>> <cmp-field-mapping>
>> <field-name>port</field-name>
>> <column-name>InstanceBean_.port_</column-name>
>> </cmp-field-mapping>
>> <cmp-field-mapping>
>> <field-name>servletPath</field-name>
>> <column-name>InstanceBean_.servletPath_</column-name>
>> </cmp-field-mapping>
>> <cmp-field-mapping>
>> <field-name>username</field-name>
>> <column-name>InstanceBean_.username_</column-name>
>> </cmp-field-mapping>
>> <cmp-field-mapping>
>> <field-name>pass</field-name>
>> <column-name>InstanceBean_.pass_</column-name>
>> </cmp-field-mapping>
>> <cmp-field-mapping>
>> <field-name>comment</field-name>
>> <column-name>InstanceBean_.comment_</column-name>
>> </cmp-field-mapping>
>> <cmp-field-mapping>
>> <field-name>address</field-name>
>> <column-name>InstanceBean_.address_</column-name>
>> </cmp-field-mapping>
>> <cmr-field-mapping>
>> <cmr-field-name>subscribers</cmr-field-name>
>> <column-pair>
>> <column-name>InstanceBean_.id_</column-name>
>> <column-name>SubscriberBean_.InstanceBean_id_</column-name>
>> </column-pair>
>> <fetched-with>
>> <none/>
>> </fetched-with>
>> </cmr-field-mapping>
>> </entity-mapping>
>> <entity-mapping>
>> <ejb-name>SubscriberBean</ejb-name>
>> <table-name>SubscriberBean_</table-name>
>> <cmp-field-mapping>
>> <field-name>id</field-name>
>> <column-name>SubscriberBean_.id_</column-name>
>> </cmp-field-mapping>
>> <cmp-field-mapping>
>> <field-name>comment</field-name>
>> <column-name>SubscriberBean_.comment_</column-name>
>> </cmp-field-mapping>
>> <cmr-field-mapping>
>> <cmr-field-name>instance</cmr-field-name>
>> <column-pair>
>> <column-name>SubscriberBean_.InstanceBean_id_</column-name>
>> <column-name>InstanceBean_.id_</column-name>
>> </column-pair>
>> <fetched-with>
>> <none/>
>> </fetched-with>
>> </cmr-field-mapping>
>> </entity-mapping>
>>
>></sun-cmp-mapping>
>></sun-cmp-mappings>
>>
>>
>>------------------------------------------------------------------------
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
>>For additional commands, e-mail: users-help_at_glassfish.dev.java.net