[JBossWS] - Re: Question on Basic WS Authentication
by mjhammel
Alessio:
In JBOSS 4.0.5GA I dropped crunch-login-config-service.xml and crunch-login-config.xml into server/default/conf in order to enable a DB based authentication. This worked fine. In 4.2.2GA it doesn't appear that crunch-login-config-service.xml is being seen. The only way to get crunch-login-config.xml to be read is to manually put it into login-config.xml. Am I missing something or is this a change to 4.2.2GA that I'll just have to live with?
Here are the contents of the two files:
crunch-login-config-service.xml
<?xml version="1.0" encoding="UTF-8"?>
| <!DOCTYPE server>
|
| <server>
|
| <mbean code="org.jboss.security.auth.login.DynamicLoginConfig" name="jboss:service=DynamicLoginConfig">
| <attribute name="AuthConfig">crunch-login-config.xml</attribute>
| <depends optional-attribute-name="LoginConfigService">jboss.security:service=XMLLoginConfig</depends>
| <depends optional-attribute-name="SecurityManagerService">jboss.security:service=JaasSecurityManager</depends>
| </mbean>
|
| </server>
crunch-login-config.xml
<?xml version='1.0'?>
| <!DOCTYPE policy PUBLIC
| "-//JBoss//DTD JBOSS Security Config 3.0//EN"
| "http://www.jboss.org/j2ee/dtd/security_config.dtd">
|
| <!--
| Crunch Security Realm Configuration.
| This file defines how authentication is determined for access to pages.
| This file gets copied to $JBOSS_HOME/server/default/conf by the Ant build.
| -->
|
| <policy>
|
| <application-policy name = "CrunchDBRealm">
| <authentication>
| <login-module code = "org.jboss.security.auth.spi.DatabaseServerLoginModule" flag = "required">
| <module-option name = "unauthenticatedIdentity">guest</module-option>
| <module-option name = "dsJndiName">java:/CrunchDS</module-option>
| <module-option name = "principalsQuery">SELECT password FROM subscriber WHERE username=?</module-option>
| <module-option name = "rolesQuery">SELECT CRUNCHROLES.ROLENAME, 'Roles' FROM CRUNCHROLES, SUBSCRIBER WHERE SUBSCRIBER.USERNAME=? AND CRUNCHROLES.USERGUID=SUBSCRIBER.GUID</module-option>
| </login-module>
| </authentication>
| </application-policy>
|
| </policy>
|
Again, in 4.2.2GA if I copy everything between and in the crunch-login-config.xml into login-config.xml then authentication works as it's supposed to. But I'd rather just drop in my own config without mucking with the JBOSS default config, if that's still possible.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123136#4123136
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123136
17 years, 8 months
[JBossWS] - org.jboss.cache.lock.TimeoutException: failure acquiring loc
by anatk
Hi
I am using pojo cache. When I try to write to the data base I get a exception. It happens while there is no one else writing or reading to the cache and it happens consistently only on 64b machines. When I do it on 32b machine it never happens.
The exception is as follows:
2008-01-23 17:32:57,560 ERROR [com.bevents.engine.engineserver.server.EngineServerImpl] org.jboss.cache.lock.TimeoutException: failure acquiring lock: fqn=/EVENTS/20/d1-0;d2-0;d3-0;d4-0;d5-1;d7-2;d10-0;d11-3;d12-2;d13-1, caller=Thread[RMI TCP Connection(37)-192.168.10.201,5,RMI Runtime], lock=write owner=GlobalTransaction::81 (org.jboss.cache.lock.LockStrategyReadCommitted@4d402172)
org.jboss.cache.lock.TimeoutException: failure acquiring lock: fqn=/EVENTS/20/d1-0;d2-0;d3-0;d4-0;d5-1;d7-2;d10-0;d11-3;d12-2;d13-1, caller=Thread[RMI TCP Connection(37)-192.168.10.201,5,RMI Runtime], lock=write owner=GlobalTransaction::81 (org.jboss.cache.lock.LockStrategyReadCommitted@4d402172)
at org.jboss.cache.lock.IdentityLock.acquire(IdentityLock.java:528)
at org.jboss.cache.interceptors.PessimisticLockInterceptor$LockManager.acquire(PessimisticLockInterceptor.java:579)
at org.jboss.cache.interceptors.PessimisticLockInterceptor.acquireNodeLock(PessimisticLockInterceptor.java:393)
at org.jboss.cache.interceptors.PessimisticLockInterceptor.lock(PessimisticLockInterceptor.java:329)
at org.jboss.cache.interceptors.PessimisticLockInterceptor.invoke(PessimisticLockInterceptor.java:187)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
at org.jboss.cache.interceptors.NotificationInterceptor.invoke(NotificationInterceptor.java:32)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
at org.jboss.cache.interceptors.TxInterceptor.handleNonTxMethod(TxInterceptor.java:298)
at org.jboss.cache.interceptors.TxInterceptor.invoke(TxInterceptor.java:131)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
at org.jboss.cache.interceptors.CacheMgmtInterceptor.invoke(CacheMgmtInterceptor.java:81)
at org.jboss.cache.interceptors.Interceptor.invoke(Interceptor.java:76)
at org.jboss.cache.interceptors.InvocationContextInterceptor.invoke(InvocationContextInterceptor.java:62)
at org.jboss.cache.CacheImpl.invokeMethod(CacheImpl.java:3939)
at org.jboss.cache.CacheImpl.get(CacheImpl.java:1441)
at org.jboss.cache.CacheImpl.get(CacheImpl.java:1415)
Does anyone have any idea what can be the cause for this excpetion?
hanks in advance,
Anat
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123040#4123040
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123040
17 years, 8 months
[JBossWS] - Deploying a client on JbossAs
by Vincent321
Dears,
I get the following exception while invoking my webservice client on jbossAs inside a webapp.
java.lang.LinkageError: loader constraints violated when linking javax/xml/namespace/QName class
Seems that this class is contained inside stax-api.jar inside my web-inf/lib.
If I remove that jar, I got this exception :
javax.xml.stream.FactoryConfigurationError: Provider com.bea.xml.stream.MXParserFactory not found
| at javax.xml.stream.FactoryFinder.newInstance(FactoryFinder.java:72)
| at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:176)
| at javax.xml.stream.FactoryFinder.find(FactoryFinder.java:92)
| at javax.xml.stream.XMLInputFactory.newInstance(XMLInputFactory.java:136)
| at com.sun.xml.ws.api.streaming.XMLStreamReaderFactory.<clinit>(XMLStreamReaderFactory.java:36)
| at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.createReader(RuntimeWSDLParser.java:786)
| at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.resolveWSDL(RuntimeWSDLParser.java:236)
| at com.sun.xml.ws.wsdl.parser.RuntimeWSDLParser.parse(RuntimeWSDLParser.java:107)
| at com.sun.xml.ws.client.WSServiceDelegate.parseWSDL(WSServiceDelegate.java:226)
|
Any help will be very appreciated.
Thanks a lot
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4122992#4122992
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4122992
17 years, 8 months