[Installation, Configuration & DEPLOYMENT] - Multiple instances with multiple configurations
by viniciuscarvalho
Hello there! I've already ran multiple instances of jboss on the same machine, but I'm having problems trying to use multiple run.conf for those instances.
We are using 4.0.1sp1 in a Suse linux
We trigger the start using jboss_init_suse.sh
What I've did was to create multiple runXX.conf for each jboss_init_suseXX.sh
each jboss_init point to a server config, using a custom port according to the binding manager file. So far almost so good.
from run.sh :
| # Read an optional running configuration file
| if [ "x$RUN_CONF" = "x" ]; then
| RUN_CONF="$DIRNAME/run.conf"
| fi
| if [ -r "$RUN_CONF" ]; then
| . "$RUN_CONF"
| fi
|
So I tried to set the RUN_CONF on the jboss_init_suseXX, problem is that it is never read. I'm a total noob on unix shell scripts, what I'm trying to do is:
| DIRNAME=`dirname $0`
| RUN_CONF="$DIRNAME/run2.conf"
| export RUN_CONF
|
but it is not working. Another problem is regarding the stop, I'm only being able to stop it using -s hostname:port and not -n serverName, the second option throws an exception:
| Exception in thread "main" javax.management.MalformedObjectNameException: Key properties cannot be empty
| at javax.management.ObjectName.construct(ObjectName.java:467)
| at javax.management.ObjectName.<init>(ObjectName.java:1394)
| at org.jboss.Shutdown.main(Shutdown.java:164)
|
Any ideas on how can I solve this issues?
Regards
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068882#4068882
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068882
18Â years, 8Â months
[JBoss Messaging] - JBM and JAAS Client authentication
by sibreb
I was under the impression that JBoss Messaging worked with the JAAS ClientLoginModule described in the JBoss AS User Guide for remote messaging clients. I understood this to mean that it would not be necessary to pass a username and password to the connectionFactory.getConnection() method.
This seems to work for sending messages, but not for receiving messages.
I have the DefaultSecurityConfig set to:
| <security>
| <role name="guest" read="false" write="false" create="false"/>
| <role name="admin" read="true" write="true" create="true"/>
| </security>
|
In the destination queue, the SecurityConfig is set to:
| <security>
| <role name="admin" read="true" write="true" create="true"/>
| </security>
|
I have a client that does the following:
1) Perform a JAAS login using the ClientLoginModule
2) Obtain a connection factory from JNDI
3) Obtain a connection (without a username/password)
4) Obtain a transacted session
4) Send 5 messages to DEST
5) Commit the session
6) Set up a consumer for DEST
This fails at step 6 whith message:
| javax.jms.JMSSecurityException: User: null is not authorized to read from destination DEST
| at org.jboss.server.container.SecurityAspect.check(SecurityAspect.java:267)
| ....
|
If I obtain the connection with a username and password it works fine.
Can anyone provide any insight?
(Ultimately the intention is to use SSL and client certificates in place of a password)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068881#4068881
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068881
18Â years, 8Â months
[JBoss Seam] - Re: Seam 1.2.1, AS 4.2.1, @Restricted method gives NoClassDe
by SmokingAPipe
I put el-ri.jar in the WEB-INF/lib, and got the same "java.lang.NoClassDefFoundError: com/sun/el/ExpressionFactoryImpl".
I then put the el-ri.jar directly in the ear, and added it as a module in application.xml, and... it works! I tested it and it lets me run the restricted factory method. I then changed it from @Restrict("#{s:hasRole('admin')}") to @Restrict("#{s:hasRole('thisRoleDoesNotExist')}") , logged in as admin, and tried to access that factory, and got:
Authorization check failed for expression [#{s:hasRole('thisRoleDoesNotExst')}]
as I expected. So this fix seems to work, so far, and lets me keep working on this.
I'll be keeping my eyes open for Seam 1.2.2 or whatever, where hopefully this dependency will be gone.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068879#4068879
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068879
18Â years, 8Â months
[JBoss/Spring Integration] - Re: Jboss and Spring
by alesj
Like I said in the sticky, deploying Spring .war file/application is what Spring is all about - see their basic instructions. JBoss (Tomcat) in this case only serves as a web container.
What JBoss/Spring is about, is the integration with EJB3 or any AOP injection capable module.
"pedwards" wrote : but its still using 1.2.5 version of spring
|
Not true. There is not so new release that supports Spring 2.0.
"pedwards" wrote :
| So I need to know how to start spring application context from a war file.
|
See Spring instructions.
There must be Spring specific ServletContextListener defined in web.xml.
"pedwards" wrote : Please are you able to supply a simple war file example?
|
Any working .war should do.
JBoss (Tomcat) is a normal web container. ;-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4068876#4068876
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4068876
18Â years, 8Â months