[JBoss JIRA] Created: (JBAS-8036) create EntityManager error
by Dave Chen (JIRA)
create EntityManager error
--------------------------
Key: JBAS-8036
URL: https://jira.jboss.org/browse/JBAS-8036
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: JBoss 5.1.0 GA
Reporter: Dave Chen
create a new persistence unit programmatically and map it to a new datasource without redeploy or server restart.
We tried the following in a stateless session bean:
Map configOverrides = new HashMap();
EntityManagerFacotry emf = Persistence.createEntityManagerFactory("unit1", configOverrides);
But got exception:
javax.persistence.PersistenceException: [PersistenceUnit: unit1] Unable to build EntityManagerFactory
<persistence-unit name="unit1">
<jta-data-source>java:/dataSource1</jta-data-source>
<properties>
<property name="hibernate.dialect" value="org.hibernate.dialect.MySQLDialect"/>
<property name="hibernate.hbm2ddl.auto" value="update"/>
<property name="hibernate.show_sql" value="false"/>
</properties>
</persistence-unit>
08:17:58,204 ERROR [STDERR] javax.persistence.PersistenceException: [PersistenceUnit: defaultDataSource] Unable to build EntityManagerFactory
08:17:58,205 ERROR [STDERR] at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:677)
08:17:58,205 ERROR [STDERR] at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:126)
08:17:58,205 ERROR [STDERR] at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:52)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (JBAS-8078) HornetQ Initialization Takes 25% of AS Boot Time
by Richard Opalka (JIRA)
HornetQ Initialization Takes 25% of AS Boot Time
------------------------------------------------
Key: JBAS-8078
URL: https://jira.jboss.org/browse/JBAS-8078
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: JMS (HornetQ)
Affects Versions: 6.0.0.M4
Reporter: Richard Opalka
Assignee: Tim Fox
Fix For: 6.0.0.Final
This is the umbrella JIRA for all the future HornetQ boot time optimization fixes.
I was measuring AS boot times today. Here are the results.
-----------------------
Test Configuration
-----------------------
* AS TRUNK (https://svn.jboss.org/repos/jbossas/trunk -r 105792 default configuration)
* Sun JDK6 (java version "1.6.0_20")
* 64 Bit Linux OS (Linux opalka 2.6.32.12-115.fc12.x86_64 #1 SMP Fri Apr 30 19:46:25 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux)
* Intel Processor (Intel(R) Core(TM)2 CPU T7400 @ 2.16GHz)
-----------------------
AS trunk (with HornetQ) boot times:
-----------------------
Round 01 - 25s:723ms
Round 02 - 24s:260ms
Round 03 - 24s:626ms
Round 04 - 25s:345ms
Round 05 - 24s:510ms
Round 06 - 24s:458ms
Round 07 - 24s:904ms
Round 08 - 24s:885ms
Round 09 - 24s:367ms
Round 10 - 24s:817ms
Round 11 - 24s:815ms
Round 12 - 25s:174ms
Round 13 - 24s:758ms
Round 14 - 25s:260ms
Round 15 - 24s:692ms
-----------------------
Average - 24s:840ms
-----------------------
When I removed:
$JBOSS_HOME/server/default/deploy/hornetq/
$JBOSS_HOME/server/default/deployers/hornetq-deployers-jboss-beans.xml
-----------------------
AS trunk (without HornetQ) boot times:
-----------------------
Round 01 - 18s:379ms
Round 02 - 18s:399ms
Round 03 - 18s:837ms
Round 04 - 19s:274ms
Round 05 - 18s:506ms
Round 06 - 19s:102ms
Round 07 - 18s:981ms
Round 08 - 19s:138ms
Round 09 - 18s:565ms
Round 10 - 18s:439ms
Round 11 - 18s:586ms
Round 12 - 18s:330ms
Round 13 - 18s:855ms
Round 14 - 18s:545ms
Round 15 - 19s:210ms
-----------------------
Average - 18s:743ms
-----------------------
-----------
Conclusion:
-----------
24s:840ms = 100 % AS trunk boot
18s:743ms ~ 75 % AS trunk without HornetQ boot
---
6s:097ms ~ 25 % HornetQ boot
---
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (JBAS-8330) org.jboss.jdbc.HypersonicDatabase stopping HSQLDB 2.0 throws Exception
by Ondrej Medek (JIRA)
org.jboss.jdbc.HypersonicDatabase stopping HSQLDB 2.0 throws Exception
----------------------------------------------------------------------
Key: JBAS-8330
URL: https://jira.jboss.org/browse/JBAS-8330
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-5.1.0.GA
Environment: JBoss 5.1.0GA, HSQLDB 2.0
Reporter: Ondrej Medek
Priority: Minor
Hi,
I have tried a new HSQLDB 2.0 with JBoss 5.1.0GA. It works fine. Just the org.jboss.jdbc.HypersonicDatabase.stopStandaloneDatabase() throws an exception:
org.hsqldb.HsqlException: statement does not generate a result set
I guess the code:
statement.executeQuery(shutdownCommand);
should be replaced by
statement.executeUpdate(shutdownCommand);
(But i have not tried it, though).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (JBAS-8754) EAR that deploys fine to AS 5.0, 5.1 and I believe also earlier AS 6's now fails with weird error
by Max Andersen (JIRA)
EAR that deploys fine to AS 5.0, 5.1 and I believe also earlier AS 6's now fails with weird error
-------------------------------------------------------------------------------------------------
Key: JBAS-8754
URL: https://issues.jboss.org/browse/JBAS-8754
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 6.0.0.CR1
Reporter: Max Andersen
Assignee: Shelly McGowan
Priority: Blocker
As shown in JBIDE-7932 AS 6 CR1 will no longer deploy the ear's created by JBoss Tools seam tooling because it has an entry in its manifest.mf.
This is a regression and will mean that seam projects (and possibly other ear projects) created by JBoss Tools/JBoss Developer Studio will not work on AS 6 CR1
(but it will work on all previous AS versions)
I consider that a blocking regression.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years
[JBoss JIRA] Created: (JBCOMMON-118) Expose org.jboss.net.protocol.URLStreamHandlerFactory as a service provider for java.net.URLStreamHandlerFactory
by Krzysztof Maslak (JIRA)
Expose org.jboss.net.protocol.URLStreamHandlerFactory as a service provider for java.net.URLStreamHandlerFactory
----------------------------------------------------------------------------------------------------------------
Key: JBCOMMON-118
URL: https://issues.jboss.org/browse/JBCOMMON-118
Project: JBoss Common
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Components: common-core (2.x)
Reporter: Krzysztof Maslak
In JBoss AS7 each module uses ModularURLStreamHandlerFactory as the implementation for URLStreamHandlerFactory, which actually goes through the set of modules ( provided using jboss.protocol.handler.modules system property ) and locates all URLStreamHandlerFactory providers for the given module ( that are used to create URLStreamHandler ).
org.jboss.net.protocol.URLStreamHandlerFactory is a service provider for java.net.URLStreamHandlerFactory, it is shipped with org.jboss.commons-core.jar, but I haven't seen it registered nowhere as a service provider.
org.jboss.commons-core.jar is a part of org.jboss.common-core module in AS7.
Having there this service provider we will be able to pass the moduleId ( org.jboss.common-core ) as part of system property jboss.protocol.handler.modules, then ModularURLStreamHandlerFactory will do a lookup in our org.jboss.common-core module and try to find URLStreamHandler for the given protocol using default java mechanism.
At the moment AS7 is configured to handle protocols through VFSStreamHandlerFactory which delegates this to jboss-vfs, in case of unknown protocol it fails, instead it should also check protocol against build in java mechanism.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years