[Persistence, JBoss/CMP, Hibernate, Database] - newbie: em.flush() is locking a select statement
by mars1412
I just noticed following issue, that I can't understand.
I change some properties on myEntity and set a breakpoint before
entityManager.flush();
In a command window I start sqlcmd (MS-Sql Servers commandline interface) and select the entity that I am about to change.
select * from MyEntity where id = 1;
This works as expected.
Then in the debugger I execute the flush() statement (only this single line).
When I now try to do the same select in my command window, the select blocks until I resume my debugging session!
As soon as the debugged transaction is committed, the select in the command window resumes and gives me the results.
What is going on here??
How can the update-statement in my debugging session block a select (!) statement in another transaction (that even exists in another process)?
If I issued another update in the command window this behaviour would be ok. But not for a select, where I only read the data.
I hope someone can enlighten me.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137978#4137978
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137978
18 years, 1 month
[Installation, Configuration & DEPLOYMENT] - Re: jsf for jboss 4.2
by BGrand
Hi !
Same problem for me... I added your context-param code in my web.xml file, but I still have the same error message when deploying the application in JBoss...
09:14:03,310 WARN [JBossJSFConfigureListener] MyFaces JSF implementation found! This version of JBoss AS ships with the java.net implementation of JSF. There are known issues when mixing JSF implementations. This warning does not apply to MyFaces component libraries such as Tomahawk. However, myfaces-impl.jar and myfaces-api.jar should not be used without disabling the built-in JSF implementation. See the JBoss wiki for more details.
My configuration: JBossAS 4.2.2.GA, myfaces-api-1.1.1.jar and myfaces-impl-1.1.1.jar bundled in the EAR.
Maybe, is it possible to disable the JBossAS built-in implementation of JSF directly in JBossAS, or to replace it by MyFaces' one ?
if someone has enougth experience with this to help me, I will appreciate very much, and even if you have only ideas about this :)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137968#4137968
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137968
18 years, 1 month
[EJB 3.0] - Re: Dynamic deployment for EJB3 component
by FrankTheTank
Actually you can change the names to whatever you want.
They just have to match in the areas I have listed below.
Check your [database]-ds.xml (located in your deploy dir) and look for a tag <jndi-name>SomeName</jndi-name>.
That is the name under which the datasource registers itself.
That name is also used in the persistence.xml located under .
<jta-data-source>java:/SomeName</jta-data-source>
Just make sure the two names are the same (copy & paste it .. trust me ;) ).
Or, maybe I am not getting it. Just to verify the setup:
You have a [database]-ds.xml in your deploy directory and a persistance.xml in your [project]/META-INF/ dir.
It is also probably also just have two *-ds.xmls in your deploy directory giving you access to the database. Just tried it and at least they both register themselves.
You can even have a per-database-level in the *-ds.xml.
Make sure the file name and the JNDI names are different then the first.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4137964#4137964
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4137964
18 years, 1 month