Check the testsuites.
There are a lot of simple JMS code in there.
Suggestions :
Use the JBoss logger function, instead of the crap System.out.println(...)
such as :
| class declaration {
| private static Logger log = Logger.getLogger(this.class);
|
| methode {
|
Firstly, I am using the all configuration (haven't tried this yet in any other
configurations). And I am accessing a Stateful Session Bean from a web app. It works
good before hot deploy of the ejb, but throws ClassCastException after hot deploy of
the ejb.
This code is the code to access
Buy more hardware :-)
/G
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3838721#3838721
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3838721
---
This SF.Net email is
BTW, this is with JBoss 3.2.4.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3838723#3838723
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3838723
---
This SF.Net email
What is the total query time in the 2 examples given?
You will have an overhead from java compared to
plsql before the actual query is processed on the DB and after the query is finished
and the result is transfered back to your application. For very small queries you
could end up with this
Are you using data sources? If so, make sure you
close them when you have finished using them.
check and double check.
This error occurs when you exhaust the connection pool. Larger pool will only buy you
some more time.
/G
View the original post :
JCA uses the pooling mechanisms. If you implement a JCA 1.0 connector then you will
have pooling like you do on datasources.
Datasource is just a special case of a JCA connector.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3838726#3838726
Reply to the post
My apologies, I submitted the original post from another computer earlier today and
didn't have a corresponding stack trace readily available. This reply includes an
actual stack trace for the exception.
I don't have TRACE level logging to provide because I have not been able to reproduce
the
Write your own DeploymentSorter.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3838730#3838730
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3838730
---
This SF.Net
I had the same problem. All you have to do is upon role update, Flush the
JAASSecurityManger's cache. This will force the the principal to go through the login
module again, populating all the new roles.
View the original post :
Thanks for the pointer.
Looking at the test suite code come with the jboss-3.2.2 source, most of the test is
looking up ConnectionFactory through localhost rather than through remote server. They
didn't help in my case.
Further look at the code of org.jboss.mq.server.JMSDestinationManager
Is there any relationship between the authentication I have to use for JMS
(TopicConnection.createTopicConnection(user,pass)) and the authentication I use to
access my beans (LoginContext.login()) or do we have two separate security domains
each of which has to be setup and managed differently?
gudmundsonsc wrote : Write your own DeploymentSorter.
You certainly can do this. Having done it I can't say I recommend it. The way we went
was to maintain a global deployment ordering list and sort based on that. It is a pain
in the ass to maintain this.
Using the PrefixDeploymentSorter is
Turned out to be a bright beginning of the day! Searched this forum on 'HelloServer'
and saw a post suggesting to try ctx.lookup(HelloWorldServer) in place of
ctx.lookup(ejb/HelloWorldServer). The program worked, but would someone be able to
throw some light on why it worked without ejb?
JBoss 3.2.3 - Updated my system with 3.2.4 - will try.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3838736#3838736
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3838736
101 - 115 of 115 matches
Mail list logo
