[JBoss Eclipse IDE (users)] - Re: Cannot add J2EE Server
by chuckharris
So i decided to start with a fresh eclipse and jboss ide. For the most part, generating a bottom up web service is working as expected. However, when i generate the web service and then test it, "-c default,all,minimal" is entered in the program arguments so the deployment fails:
17:50:19,484 INFO [Server] Core system initialized
Failed to boot JBoss:
org.jboss.deployment.DeploymentException: url file:/C:/packages/jboss-4.0.1sp1/server/default,all,minimal/conf/jboss-service.xml could not be opened, does it exist?
at org.jboss.deployment.DeploymentInfo.(DeploymentInfo.java:175)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:737)
I have changed it to "-c all" several times and it changes back whenever i start the server when generating a web service. I removed the "-c default,all,minimal" from eclipse\plugins\org.eclipse.jst.server.generic.serverdefinitions_1.0.0.v200603162041\servers\jboss323.serverdef and jboss.serverdef (using 4.01sp1) but it still changes it in the server config. Any idea how to get the -c all to stick.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974073#3974073
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974073
19 years, 7 months
[JBossCache] - Re: Hibernate/Cache conceptual mismatch
by otaylor
Hmmm, dug around in this some more and it turns out that (the non-optimistic) Hibernate TreeCache glue *is* still literally using putFailFast, even in latest CVS. Looking at the details of the behavior bundle, I'm not sure it could be switched over without some adiditional work.
Isolated from parent transaction:
putFailFast: Doesn't provide, Hibernate suspends its transaction itself before calling into the TreeCache. (There's a bug here, the suspended transaction leaks onto the invocation context used for putFailFast, so putFailFast creates its locks owned by the suspended transaction!)
FAIL_SILENTLY: Provides automatically
Replicates asynchronously even if the cache is REPL_SYNC
putFailFast: Provides (hacked into the ReplicationInterceptor)
FAIL_SILENTLY: Doesn't provide. Maybe could be a separate option?
Lock failure immediate without waiting for a lock timeout:
putFailFast: Provides
FAIL_SILENTLY: Doesn't provide (??? Am I missing something?)
Lock failure ignored:
putFailFast: Doesn't provide; for local failure, caller can catch TimeoutException. failure on (async) replication is logged at level ERROR.
FAIL_SILENTLY: Provides, sort of. Except for the one particular case of JBCACHE-767 (now) silent isn't very silent... it logs at level INFO.
For the short term I'm going to see if I can come up with fixes for the two putFailFast bugs noted above (leak of locks onto suspended transaction, ERROR logging on replication).
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3974070#3974070
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3974070
19 years, 7 months