Follow-up:
Remove all binding= definitions and use Tomahawk 1.1.6 then everything works
OK with JSF RI 1.2 as shipped with JBoss 4.2.0
Dave
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4100133#4100133
Reply to the post :
One 'bug'
Using an AJAX app based on http://www.zkoss.org, redeploy app, refresh page -
Tomcat/JAAS/whoever redirects to the last AJAX URL and not the URL in the
browser address bar. So the user just sees an empty AJAX response.
One Problem and related Solution
FORM login should allow the
jhalliday: Sorry about the late response. I added the following to
jbossjta-properties.xml
property name=com.arjuna.ats.jta.allowMultipleLastResources value=true/
as the first child element of
properties depends=arjuna name=jta
which I assume is the correct place (the documentation does not say
I cannot reproduce it either - it works!
This is strange since it failed twice previously and all I did now was
re-enable the code that previously failed. I hope it was simply a typo.
Thank you for your patience and help
Dave
View the original post :
Interesting read
http://www.jboss.com/index.html?module=bbop=viewtopict=95617postdays=0postorder=ascstart=0
unfortunately I still have no idea how to set this 'bad' option.
One use-case the above thread seems to ignore is 10 independant
completely-ignorant-of-each-other applications each with
Where is the JBossTS config file? I do not see 'allowMultipleLastResources' as
a MBean property on TransactionManagerService.
Extra work: the phrase This is transactionally unsafe and should not be relied
on implies that we should modify our legacy systems to use XA transactions and
not depend
Forgot to say, my duplicates are in a t:dataTable (plus jscookmenu support is
broken).
MyFaces and Tomahawk had ID generation 'compatibility issues' with JSF RI in
the past, which
https://issues.apache.org/jira/browse/MYFACES-1010 indicates needs a fix in the
JSF RI. All this occured around
OK - but not without extra work on our side.
We do not use, nor do we need, two-phase-commit. Why is JBoss 'forcing' us in
that direction by labeling the fast in-memory transaction manager as
deprecated (org.jboss.tm.TransactionManagerService in jboss-service.xml) ?
Dave
View the original
Just in the rare case that someone at JBoss cares.
Upgrading to 4.2.0 has been a thoroughly unpleasant experience.
1. JSF 1.2 does not work with MyFaces Tomahawk 1.1.4 or 1.1.5
http://www.jboss.com/index.html?module=bbop=viewtopict=108746
All JBoss says about this is that Tomahawk 'should work'.
Our Oracle is old (9.0.1.2) and I am pushing for an upgrade (could take a
while). I read on Oracle's JDBC site that 9.2 allows local and XA transactions
to be mixed.
In any case we do not need XA transactions, we have a single server which only
needs local transactions and all the code is
I had several problems with XA, namely:
1. JDBC commit() calls failed with 'use XA commit instead' exceptions in Oracle
9i OCI drivers.
2. After clicking around in a few apps we would get (cannot remember the exact
message) 'unable to reuse connection, transaction outstanding' on a pooled
All our 10 datasources are local-tx-datasource but it appears JBossTS (default
transaction manager in 4.2.0) only allows 1 local-tx-datasource (not simple to
find this out), you need to convert to xa-datasource.
This should be in the release notes (I can find no reference).
However, converting
I get duplicate IDs in my apps when using JBoss 4.2.0.GA with Tomahawk 1.1.5 +
Facelets 1.1.12 added.
None of my pages assign an ID, the duplicates are all of the generated kind.
Commenting out parts of the page just causes the duplicate to occur somewhere
else. Sometimes refreshing the page
I have had problems with this particular Web-App page before. It used to cause
'CompilerThread' errors in the JVM (causing the JVM to exit) before I
rearranged the EJB loading order. I cannot find my original bulletin board post
about the CompilerThread issue (do JBoss purge old posts?).
My
Configuring a
valid-connection-checker-class-nameorg.jboss.resource.adapter.jdbc.vendor.OracleValidConnectionChecker/valid-connection-checker-class-name
sometimes causes a
OutOfMemoryError: unable to create new native thread caused by
oracle.jdbc.dbaccess.DBAccess.pingDatabase
This has
Thanks for the quick answer.
The server is not under heavy load, we have seen this problem just after
startup when no more than 2 or 3 users are active.
Admittedly 2 users are using a EJB3-heavy (i.e. lots of bean cross references,
fetch joins etc) page simultaenously.
We have had problems
I'm trying.
One thing that does not help is that server.log gets wiped out (i.e emptied or
overwritten) when this error happens and JBoss restarts. All I have to work on
is the console output.
Dave
View the original post :
FYI
http://www.jboss.com/index.html?module=bbop=viewtopict=94692
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3988732#3988732
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3988732
You need to choose the 'EJB' configuration when installing, not 'all'.
Doing so creates a 'ejb3.deployer' directory under deploy.
Dave
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3975675#3975675
Reply to the post :
Is there a reason why version numbers are not included in all JAR, SAR, EAR.
?AR filenames.
For example you have the following:
antlr-2.7.6.jar
bsh-1.3.0.jar
ehcache-1.1.jar
quartz-all-1.5.2.jar
but all other JARs have no version number.
What about SARs etc. Why not:
20 matches
Mail list logo
