[Security & JAAS/JBoss] - Re: Multiple SSL Connectors
by aiko85
Oh, sorry, here's the server.xml code:
|
| <Connector port="18443" address="localhost" maxThreads="100"
| minSpareThreads="5" strategy="ms" maxSpareThreads="15" scheme="https"
| emptySessionPath="true" SSLEnabled="true"
| secure="true" clientAuth="false"
| keystoreFile="${jboss.server.home.dir}/conf/ssl-server.jks"
| keystorePass="password"
| truststoreFile="${jboss.server.home.dir}/conf/ssl-server-truststore.jks"
| truststorePass="password"
| sslProtocol="TLS"/>
|
| <Connector port="18444" address="localhost" maxThreads="100"
| minSpareThreads="5" strategy="ms" maxSpareThreads="15" scheme="https"
| emptySessionPath="true" SSLEnabled="true"
| secure="true" clientAuth="true"
| keystoreFile="${jboss.server.home.dir}/conf/ssl-server-n.jks"
| keystorePass="password"
| truststoreFile="${jboss.server.home.dir}/conf/ssl-server-truststore-n.jks"
| truststorePass="password"
| sslProtocol="TLS"/>
|
|
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162872#4162872
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162872
17 years, 9 months
[JBoss Messaging] - problem with creating Queue with JbossAS 5 Beta4 !
by Nouredine13
Hello,
I try to create a Queue on JBoss 5, so I added the following line to file:destinations-service.xml situated in deploy/messaging directory:
<mbean code = "org.jboss.jms.server.destination.QueueService"
name = "jboss.messaging.destination: service = Queue, name = jms / Ping"
xmbean-dd = "xmdesc / Queue-xmbean.xml">
@ org.jboss.system.deployers.managed.ManagementObjectClass (code = org.jboss.jms.server.destination.QueueServiceMO) </ annotation>
<depends optional-attribute-name="ServerPeer"> jboss.messaging: service = ServerPeer </ depends>
jboss.messaging: service = PostOffice </ depends>
</ mbean>
after that, i've the following error message at the startup of JBossAS 5.0.0 Beta4:
2008-07-07 14:37:22,075 ERROR [org.jboss.messaging.util.ExceptionUtil] Queue[/queue/jms/Ping, name=jms/Ping] startService
javax.naming.NameNotFoundException: jms not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:542)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:550)
at org.jnp.server.NamingServer.getObject(NamingServer.java:556)
at org.jnp.server.NamingServer.rebind(NamingServer.java:165)
at org.jnp.server.NamingServer.rebind(NamingServer.java:168)
at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:518)
at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:482)
at org.jboss.jms.server.DestinationJNDIMapper.registerDestination(DestinationJNDIMapper.java:142)
at org.jboss.jms.server.destination.QueueService.startService(QueueService.java:134)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:299)
at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.interceptor.AbstractInterceptor.invoke(AbstractInterceptor.java:138)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at org.jboss.mx.interceptor.ModelMBeanOperationInterceptor.invoke(ModelMBeanOperationInterceptor.java:140)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:90)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:184)
at $Proxy5.start(Unknown Source)
at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:42)
at org.jboss.system.microcontainer.StartStopLifecycleAction.installAction(StartStopLifecycleAction.java:37)
at org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
at org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
at org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
at org.jboss.system.microcontainer.ServiceControllerContext.install(ServiceControllerContext.java:255)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
at org.jboss.system.ServiceController.doChange(ServiceController.java:659)
at org.jboss.system.ServiceController.start(ServiceController.java:431)
at org.jboss.system.deployers.ServiceDeployer.start(ServiceDeployer.java:150)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:108)
at org.jboss.system.deployers.ServiceDeployer.deploy(ServiceDeployer.java:46)
at org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:65)
at org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:169)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:853)
at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:874)
at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:794)
at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:327)
at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1309)
at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:734)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:862)
at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:784)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:622)
at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:411)
at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:498)
at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:506)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.loadProfile(ProfileServiceBootstrap.java:246)
at org.jboss.system.server.profileservice.ProfileServiceBootstrap.start(ProfileServiceBootstrap.java:131)
at org.jboss.bootstrap.AbstractServerImpl.start(AbstractServerImpl.java:408)
at org.jboss.Main.boot(Main.java:208)
at org.jboss.Main$1.run(Main.java:534)
at java.lang.Thread.run(Thread.java:595)
2008-07-07 14:37:22,076 DEBUG [org.jboss.jms.server.destination.QueueService] Started jboss.messaging.destination:service=Queue,name=jms/Ping
but at the end we can see the line put in bold that jms/Ping is started!
so, somone have an idea to solve this.
Best Regards.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162849#4162849
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162849
17 years, 9 months
[JBoss Messaging] - Re: Not able to connect to remote Queue through Bridge
by jmesnil
"jjacobwip" wrote : Hi,
|
|
| | <mbean code="org.jboss.jms.jndi.JMSProviderLoader"
| | name="jboss.messaging:service=JMSProviderLoader,name=LocalJMSProvider">
| | <attribute name="ProviderName">LocalJMSProvider</attribute>
| | <attribute name="ProviderAdapterClass">org.jboss.jms.jndi.JNDIProviderAdapter</attribute>
| | <attribute name="QueueFactoryRef">XAConnectionFactory</attribute>
| | <attribute name="TopicFactoryRef">XAConnectionFactory</attribute>
| | <attribute name="Properties">
| | java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory
| | java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces
| | java.naming.provider.url=${jboss.bind.address:localhost}:1100
| | </attribute>
| | </mbean>
| |
|
|
One thing you could try is to prepend java:/ to your FactoryRefs.
e.g.:
| <attribute name="QueueFactoryRef">java:/XAConnectionFactory</attribute>
|
hope it helps,
jeff
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162841#4162841
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162841
17 years, 9 months
[Installation, Configuration & DEPLOYMENT] - Re: How to authenticate to the JBoss server from a desktop (
by Marcos_APS
Hello, Jaikiran!
First of all, I'm sorry for the delay in replying to your post. That was because I almost don't use internet on weekends, and even though I used it I couldn't do anything to answer your post as all my environment to test the application is set where I work.
Second, thank you very much for your detailed explanation about what could be happening in my application. Thank you for having the patience to produce tests to simulate what could be wrong. When you asked me if I was securing my application I didn't realised that you could be talking about something like the @RolesAllowed and @SecurityDomain annotations. I said I was using jboss.xml, but I wasn't. I was meaning jboss-web.xml. That was just a typographical error I made.
When I make the changes to secure the application (applying the annotations above) the application worked correctly as your tests showed. Indeed, I was going to really secure that application, but I hadn't done that yet because I thought that it would have not changed anything related with the authentication method that we were using.
So, now when I supply I user with the correct role, it can call the right bean methods, otherwise an security exception is throw.
So, once again, Jaikiran, thank you very much for your patience and answers in this discussion to solve the problems that I was having with my desktop application. As I said, that was of paramount importance to me.
Marcos
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4162824#4162824
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4162824
17 years, 9 months