Anonymous | Login | Signup for a new account | 12-17-2024 11:54 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0002648 | [Resin] | minor | always | 05-05-08 06:50 | 05-08-08 11:31 | ||||
Reporter | ferg | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | Platform | |||||
Status | closed | OS | |||||||
Projection | none | OS Version | |||||||
ETA | none | Fixed in Version | 3.1.7 | Product Version | |||||
Product Build | |||||||||
Summary | 0002648: hibernate/webbeans init order | ||||||||
Description |
(rep by wesley) I've set logging to "finer" and found datasource being initialized after AmberContainer parsing persistence.xml. After some tracing, I think the issue is also an order problem. After resin server initialized, it began to init the webapp, at the order below: 1. Look at persistence.xml and try to init an AmberContainer. 2. Parse resin-web.xml to init DataSource, JCA connectors, EJBs and Singletons. Note, at the first step method getJtaDataSource() of com.caucho.amber.cfg.PersistenceUnitConfig will be called. It tried to find a DataSource in JNDI and failed, because a DataSource will be available in JNDI until the 2nd step finished. |
||||||||
Steps To Reproduce | |||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
28 total queries executed. 25 unique queries executed. |