[
https://issues.apache.org/jira/browse/OFBIZ-5216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wei Zhang updated OFBIZ-5216:
-----------------------------
Attachment: screen.png
postgresql-9.0-801.jdbc4.jar
jtds-1.2.5.jar
entityengine.xml
OFBIZ-5216.zip
Hi Adrian,
Please do as following steps to reproduce this issue.
1. Save the attached entityengine.xml to \framework\entity\config and overwrite
the existing one.
2. Save the attached jtds-1.2.5.jar and postgresql-9.0-801.jdbc4.jar to
framework\entity\lib\jdbc
3. Unzip attached OFBIZ-5216.zip and save it to hot-deploy
4. Run "and start-debug", you should be able to get the blocked screen like
attached screen.png.
My environment is Windows 8, jdk1.6.0_37, MSSQL 2005 and postgres 9.1
Please feel free to let me know if you have any question.
Thanks,
Wei
> The thread is locked at DBCPConnectionFactory.getConnection() when connects
> to multiple databases
> -------------------------------------------------------------------------------------------------
>
> Key: OFBIZ-5216
> URL: https://issues.apache.org/jira/browse/OFBIZ-5216
> Project: OFBiz
> Issue Type: Bug
> Components: framework
> Affects Versions: SVN trunk
> Reporter: Wei Zhang
> Assignee: Adrian Crum
> Priority: Blocker
> Fix For: SVN trunk
>
> Attachments: entityengine.xml, jtds-1.2.5.jar, OFBIZ-5216.zip,
> postgresql-9.0-801.jdbc4.jar, screen.png
>
>
> I connected 5 databases, ofbiz, ofbiz_olap, ofbiz_tenant and 2 MSSQL
> databases of myself. Three ofbiz databases were created in Postgres. But the
> the thread will locked at DBCPConnectionFactory.getConnection() when OFBiz
> was starting.
> And I　changed
> public Connection getConnection(GenericHelperInfo helperInfo, JdbcElement
> abstractJdbc) throws SQLException, GenericEntityException
> to
> public synchronized Connection getConnection(GenericHelperInfo
> helperInfo, JdbcElement abstractJdbc) throws SQLException,
> GenericEntityException
> it then works.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
