> this usually means that you have problem with some transaction locking the
> record you access
It shouldn't because the client is not getting the initialcontext either.
And its just one client accessing the bean once(only selects) and then
quits.
It seems like i can restart the client several times if i do it repeatedly,
if i wait for e.g. a minute, it freeze. The DD is below.
/Jon
***** DD *******
<?xml version="1.0" encoding="Cp1252"?>
<ejb-jar>
<enterprise-beans>
<entity>
<display-name>TagIssuerCodeBean</display-name>
<ejb-name>TagIssuerCode</ejb-name>
<home>tags.tagissuercode.TagIssuerCodeHome</home>
<remote>tags.tagissuercode.TagIssuerCode</remote>
<ejb-class>tags.tagissuercode.TagIssuerCodeBean</ejb-class>
<persistence-type>Bean</persistence-type>
<prim-key-class>tags.tagissuercode.TagIssuerCodePK</prim-key-class>
<reentrant>False</reentrant>
<primkey-field>tagIssuerId,tagCountryId</primkey-field>
<resource-ref>
<description>Reference to Sybase ASE</description>
<res-ref-name>SybaseDB</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
</entity>
</enterprise-beans>
</ejb-jar>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
