[JCA/JBoss] - Re: DS files not being loaded when using wrapper - w2k3
by jaikiran
anonymous wrote : wrapper.java.additional.2=-Djboss.partition.name=Partition2
|
Is this an intentional setting you have done? When you start without this parameter from the command line, i guess this value is DefaultPartition. If you don't need this, then remove it from the wrapper.conf (and make sure, when you remove, you renumber those properties correctly).
anonymous wrote : wrapper.app.parameter.2=-bXX.XX.X.XX
Is this an actual value in that conf file? Or did you modify this while posting? 1) There should be a space separating the -b and the IP address (2) The IP address must be a valid one.
anonymous wrote : wrapper.app.parameter.3=-c default
Though this param suggests that you are starting the "default" server profile, when you start the service, are you sure the "default" profile is being started? You can look at the log file (boot.log and server.log) to see which profile is being started.
anonymous wrote : Ok, I apologize if this is the wrong forum
Looks like a jboss service configuration question than JCA, so Installation & Configuration forum http://www.jboss.com/index.html?module=bb&op=viewforum&f=61 would have been the right place :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199293#4199293
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199293
17 years, 3 months
[Security & JAAS/JBoss] - Re: Ejb3 security using properties file
by jaikiran
"rudreshtcs" wrote :
| It is working after server restart, my assumption on jboss was that, we need not restart the server, just create a ejb jar again and deploy.
|
JBoss caches the roles that have been assigned to a principal. So any changes to roles will not be visible till the cache is flushed. There's a way where the cache can be disabled, but that is not configured by default. So you needed the server restart. I will make a mention of this in a appropriate document for this tutorial.
"rudreshtcs" wrote :
| Meanwhile, just as every ejb3 beginner, even i have a doubt on calling stateful session bean, the example given for stateful works fine..but it gives the same result when i change the bean to stateless..
|
The SLSB too maintains a state, but for SLSB, its not guaranteed that multiple method invocations on the same proxy will finally result in a call to the same instance of the SLSB. On the other hand, for a SFSB, multiple invocations on the same proxy are guaranteed to result in a call to the same instance of SFSB.
I do see, for a beginner, it might be better to show a clear difference using some example. Let me see if i can modify the tutorial or maybe add a new one to illustrate this behaviour.
And yes, thanks for your inputs :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199292#4199292
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4199292
17 years, 3 months