I put a simple test class to lookup the java:/DefaultDS and it failed as
well. It seems more of a JNDI naming issue, so I'll post a new thread in the
JNDI forum.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4257495#4257495
Reply to the post :
Hi, i'm getting exactly same error trying to deploy an SCA sample (from tuscany
sca 1.4 ) in a Jboss AS 4.2.3, HAVE YOU FOUND THE SOLUTION?
Anyone has a succesfull instalation of tuscany SCA 1.x version deployed on
jboss x ?
there is the trace:
2009-09-28 16:20:43,996 ERROR
So I created a test EAR that contains only one simple Servlet that looks up the
DataSource using the JNDI name to verify that the problem is with JNDI lookup.
This time it worked just fine. I am guessing that my problem is related to the
EAR. I'll post my updates after I examine the EAR
So apparently the default allocationSize is 50 instead of 1. Changing it to 1
has resolved the issue.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4257507#4257507
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4257507
You will need to use a shared file system like NFS in a clustered environment.
Thats the only way the data stored on the file system will be in sync.
without the synchronization, on fail over when a new node takes over as master,
it will just read data from its local file system which does not
Tanx Peter!
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4257516#4257516
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4257516
___
jboss-user mailing list
Describe your environment:
JBoss Portal 2.6.4 - GA
Downloaded from jboss.org
JBoss AS Version (comes with the bundle)
Tomcat (other details cannot locate)
KUbuntu
I included a CMS in my page and when I log in as user, not as admin, the CMS
cannot be viewed and this message displays.
Access
Hi
We have never tested JBM with different versions working in a cluster, or JBoss
MQ mixed with JBM.
I suggest you use one version of JBM in the cluster.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4257518#4257518
Reply to the post :
Hi,
Thanks for the update.
I have seen joram's comments.
As Joram mentioned this should make the exception gone away but as long as you
do not update to console 1.2 you won't be able to see the process instances and
tasks.
Is console 1.2 part of jbpm 4.2 release ?
Can I get it separately
101 - 109 of 109 matches
Mail list logo