[JBoss Tools (users)] - Re: deployment error.Please try to resolve
by nasable
===============================================================================
.
JBoss Bootstrap Environment
.
JBOSS_HOME: C:\jboss-3.2.5\bin\\..
.
JAVA: D:\j2sdk1.4.2_04\bin\java
.
JAVA_OPTS: -Dprogram.name=run.bat
.
CLASSPATH: D:\j2sdk1.4.2_04\lib\tools.jar;C:\jboss-3.2.5\bin\\run.jar
.
===============================================================================
.
18:05:38,140 INFO [Server] Starting JBoss (MX MicroKernel)...
18:05:38,140 INFO [Server] Release ID: JBoss [WonderLand] 3.2.5 (build: CVSTag=
JBoss_3_2_5 date=200406251954)
18:05:38,156 INFO [Server] Home Dir: C:\jboss-3.2.5
18:05:38,156 INFO [Server] Home URL: file:/C:/jboss-3.2.5/
18:05:38,156 INFO [Server] Library URL: file:/C:/jboss-3.2.5/lib/
18:05:38,156 INFO [Server] Patch URL: null
18:05:38,156 INFO [Server] Server Name: default
18:05:38,156 INFO [Server] Server Home Dir: C:\jboss-3.2.5\server\default
18:05:38,156 INFO [Server] Server Home URL: file:/C:/jboss-3.2.5/server/default
/
18:05:38,171 INFO [Server] Server Data Dir: C:\jboss-3.2.5\server\default\data
18:05:38,203 INFO [Server] Server Temp Dir: C:\jboss-3.2.5\server\default\tmp
18:05:38,234 INFO [Server] Server Config URL: file:/C:/jboss-3.2.5/server/defau
lt/conf/
18:05:38,265 INFO [Server] Server Library URL: file:/C:/jboss-3.2.5/server/defa
ult/lib/
18:05:38,312 INFO [Server] Root Deployment Filename: jboss-service.xml
18:05:38,343 INFO [Server] Starting General Purpose Architecture (GPA)...
18:05:38,593 INFO [ServerInfo] Java version: 1.4.2_04,Sun Microsystems Inc.
18:05:38,625 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.4.2_04-b05
,Sun Microsystems Inc.
18:05:38,671 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
18:05:38,984 INFO [Server] Core system initialized
18:05:40,781 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour
ce:log4j.xml
18:05:41,015 INFO [WebService] Using RMI server codebase: http://oraclebomb1:80
83/
18:05:41,093 INFO [NamingService] Started jnpPort=1099, rmiPort=1098, backlog=5
0, bindAddress=/0.0.0.0, Client SocketFactory=null, Server SocketFactory=org.jbo
ss.net.sockets.DefaultSocketFactory@ad093076
18:05:55,843 INFO [RARMetaData] Loading JBoss Resource Adapter for JDBC 2 XA dr
ivers
18:05:55,843 INFO [RARMetaData] Required license terms present. See deployment
descriptor.
18:05:57,890 INFO [MailService] Mail Service bound to java:/Mail
18:05:58,328 INFO [Embedded] Catalina naming disabled
18:05:58,796 INFO [Http11Protocol] Initializing Coyote HTTP/1.1 on http-0.0.0.0
-8080
18:05:58,828 INFO [Catalina] Initialization processed in 438 ms
18:05:58,828 INFO [StandardService] Starting service jboss.web
18:05:58,828 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.0.2
6
18:05:58,843 INFO [StandardHost] XML validation disabled
18:05:58,875 INFO [Catalina] Server startup in 47 ms
18:05:58,921 WARN [DeploymentInfo] Only the root deployment can set the loader
repository, ingoring config=null
18:05:58,937 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=file:/C:/jb
oss-3.2.5/server/default/deploy/http-invoker.sar/invoker.war/
18:05:59,734 WARN [DeploymentInfo] Only the root deployment can set the loader
repository, ingoring config=null
18:05:59,750 INFO [TomcatDeployer] deploy, ctxPath=, warUrl=file:/C:/jboss-3.2.
5/server/default/deploy/jbossweb-tomcat50.sar/ROOT.war/
18:05:59,906 WARN [DeploymentInfo] Only the root deployment can set the loader
repository, ingoring config=null
18:05:59,921 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=file
:/C:/jboss-3.2.5/server/default/deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war
/
18:06:00,187 INFO [DefaultDS] Bound connection factory for resource adapter for
ConnectionManager 'jboss.jca:service=LocalTxCM,name=DefaultDS to JNDI name 'jav
a:/DefaultDS'
18:06:00,484 INFO [A] Bound to JNDI name: queue/A
18:06:00,546 INFO [B] Bound to JNDI name: queue/B
18:06:00,609 INFO [C] Bound to JNDI name: queue/C
18:06:00,656 INFO [D] Bound to JNDI name: queue/D
18:06:00,718 INFO [ex] Bound to JNDI name: queue/ex
18:06:00,796 INFO [testTopic] Bound to JNDI name: topic/testTopic
18:06:00,859 INFO [securedTopic] Bound to JNDI name: topic/securedTopic
18:06:00,906 INFO [testDurableTopic] Bound to JNDI name: topic/testDurableTopic
18:06:01,015 INFO [testQueue] Bound to JNDI name: queue/testQueue
18:06:01,125 INFO [UILServerILService] JBossMQ UIL service available at : /0.0.
0.0:8093
18:06:01,265 INFO [DLQ] Bound to JNDI name: queue/DLQ
18:06:01,343 INFO [JmsXA] Bound connection factory for resource adapter for Con
nectionManager 'jboss.jca:service=TxCM,name=JmsXA to JNDI name 'java:/JmsXA'
18:06:01,500 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=file:/C
:/jboss-3.2.5/server/default/deploy/jmx-console.war/
18:06:09,718 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=file:/C
:/jboss-3.2.5/server/default/tmp/deploy/tmp23858web-console.war/
18:06:10,250 INFO [EARDeployer] Init J2EE application: file:/C:/jboss-3.2.5/ser
ver/default/deploy/CHM_ear.ear/
18:07:12,531 INFO [EARDeployer] Init J2EE application: file:/C:/jboss-3.2.5/ser
ver/default/tmp/deploy/tmp23859CHM_ejb.jar-contents/CHM_ear.ear
18:08:54,796 WARN [DeploymentInfo] Only the root deployment can set the loader
repository, ingoring config=null
18:08:55,296 WARN [DeploymentInfo] Only the root deployment can set the loader
repository, ingoring config=null
18:08:55,656 INFO [EARDeployment] Registration is not done -> stop
18:08:55,703 ERROR [MainDeployer] could not create deployment: file:/C:/jboss-3.
2.5/server/default/deploy/CHM_ear.ear/
org.jboss.deployment.DeploymentException: Error during create of EARDeployment:
file:/C:/jboss-3.2.5/server/default/deploy/CHM_ear.ear/; - nested throwable: (ja
vax.management.InstanceAlreadyExistsException: jboss.j2ee:service=EARDeployment,
url='CHM_ear.ear' already registered.)
at org.jboss.deployment.DeploymentException.rethrowAsDeploymentException
(DeploymentException.java:39)
at org.jboss.deployment.EARDeployer.create(EARDeployer.java:270)
at org.jboss.deployment.MainDeployer.create(MainDeployer.java:790)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:644)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:608)
at sun.reflect.GeneratedMethodAccessor17.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.
java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:185)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy7.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymen
tScanner.java:304)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentS
canner.java:478)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.
doScan(AbstractDeploymentScanner.java:201)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(A
bstractDeploymentScanner.java:274)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanS
upport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMB
eanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.
java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:185)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceControl
ler.java:837)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:367)
at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.
java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:185)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:251)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:836)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:645)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:608)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:592)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.
java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:185)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:407)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:311)
at org.jboss.Main.boot(Main.java:145)
at org.jboss.Main$1.run(Main.java:399)
at java.lang.Thread.run(Thread.java:534)
Caused by: javax.management.InstanceAlreadyExistsException: jboss.j2ee:service=E
ARDeployment,url='CHM_ear.ear' already registered.
at org.jboss.mx.server.registry.BasicMBeanRegistry.add(BasicMBeanRegistr
y.java:703)
at org.jboss.mx.server.registry.BasicMBeanRegistry.registerMBean(BasicMB
eanRegistry.java:211)
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.
java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:61)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:53)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.
java:185)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.jav
a:1018)
at org.jboss.mx.server.MBeanServerImpl.registerMBean(MBeanServerImpl.jav
a:326)
at org.jboss.deployment.EARDeployer.create(EARDeployer.java:264)
... 65 more
18:09:02,015 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
Incompletely deployed packages:
org.jboss.deployment.DeploymentInfo@a8f70168 { url=file:/C:/jboss-3.2.5/server/d
efault/deploy/CHM_ear.ear/CHM_ejb.jar }
deployer: org.jboss.deployment.ClientDeployer@134263a
status: Created
state: CREATED
watch: file:/C:/jboss-3.2.5/server/default/deploy/CHM_ear.ear/CHM_ejb.jar
lastDeployed: 1205411935281
lastModified: 1205411772265
mbeans:
org.jboss.deployment.DeploymentInfo@fd5aec85 { url=file:/C:/jboss-3.2.5/server/d
efault/deploy/CHM_ear.ear/CHM_war.war/ }
deployer: org.jboss.web.tomcat.tc5.Tomcat5@1408a75
status: Created
state: CREATED
watch: file:/C:/jboss-3.2.5/server/default/deploy/CHM_ear.ear/CHM_war.war/WEB-
INF/web.xml
lastDeployed: 1205411935640
lastModified: 1205411674484
mbeans:
org.jboss.deployment.DeploymentInfo@e0c35e21 { url=file:/C:/jboss-3.2.5/server/d
efault/deploy/CHM_ear.ear/ }
deployer: org.jboss.deployment.EARDeployer@3caa4b
status: Deployment FAILED reason: Error during create of EARDeployment: file:/
C:/jboss-3.2.5/server/default/deploy/CHM_ear.ear/; - nested throwable: (javax.ma
nagement.InstanceAlreadyExistsException: jboss.j2ee:service=EARDeployment,url='C
HM_ear.ear' already registered.)
state: FAILED
watch: file:/C:/jboss-3.2.5/server/default/deploy/CHM_ear.ear/META-INF/applica
tion.xml
lastDeployed: 1205411935640
lastModified: 1205411550421
mbeans:
MBeans waiting for other MBeans:
ObjectName: jboss.web.deployment:war=CHM_war.war,id=1999556840
state: CREATED
I Depend On:
Depends On Me:
ObjectName: jboss.j2ee:service=EARDeployment,url='CHM_ear.ear'
state: CREATED
I Depend On:
Depends On Me:
ObjectName: jboss.web.deployment:war=CHM_war.war,id=-44372859
state: CREATED
I Depend On:
Depends On Me:
MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM:
ObjectName: jboss.j2ee:service=EARDeployment,url='CHM_ear.ear'
state: CREATED
I Depend On:
Depends On Me:
ObjectName: jboss.web.deployment:war=CHM_war.war,id=1999556840
state: CREATED
I Depend On:
Depends On Me:
ObjectName: jboss.web.deployment:war=CHM_war.war,id=-44372859
state: CREATED
I Depend On:
Depends On Me:
18:09:05,546 INFO [Server] JBoss (MX MicroKernel) [3.2.5 (build: CVSTag=JBoss_3
_2_5 date=200406251954)] Started in 3m:27s:203ms
18:09:05,656 INFO [Tomcat5] Saw org.jboss.system.server.started notification, s
tarting connectors
18:09:05,796 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-808
0
18:09:05,968 INFO [ChannelSocket] JK2: ajp13 listening on /0.0.0.0:8009
18:09:06,031 INFO [JkMain] Jk running ID=0 time=0/78 config=null
When i am trying to deploy CHM_ear.ear in JBoss 3.2.5 its giving me above error. If anyone knows why it is so please guide me.
thanks in advance.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136302#4136302
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4136302
18 years, 1 month
[JCA/JBoss] - Re: Stateless EJB calling WorkManager directly - legal?
by vickyk
"gsniderJBoss" wrote : How can I coordinate these transactions? Do I need an RA?
Ok after looking at this post again and Adrian's response I think you should set the Xid on the ExecutionContext , this will not create new transaction TX2. Oh you have done this and I did not read this , my bad :(
Here is the code from older TM which basically imports the Transaction from XId supplied to ExecutionContext
public void registerWork(Work work, Xid xid, long timeout) throws WorkCompletedException
| {
| if (trace)
| log.trace("registering work=" + work + " xid=" + xid + " timeout=" + timeout);
| try
| {
| TransactionImpl tx = importExternalTransaction(xid, timeout);
| tx.setWork(work);
| }
| catch (WorkCompletedException e)
| {
| throw e;
| }
| catch (Throwable t)
| {
| WorkCompletedException e = new WorkCompletedException("Error registering work", t);
| e.setErrorCode(WorkException.TX_RECREATE_FAILED);
| throw e;
| }
| if (trace)
| log.trace("registered work= " + work + " xid=" + xid + " timeout=" + timeout);
| }
http://anonsvn.jboss.org/repos/jbossas/branches/Branch_4_2/transaction/sr...
And this should also be handled in new TM(JbossTS) .
I need to see how to get the Xid , this is what will not be portable across the AS's .
"gsniderJBoss" wrote : But I cannot for the life of me get the Xid of the first transaction (TX1 above).
I think you should do this
1) Get the TransactionManger from jndi .
2) Call getTransaction() on [1]
3) This Transaction obtained from [2] should be able to give you the Xid , I can see the older TM having getXid() method.
http://anonsvn.jboss.org/repos/jbossas/branches/Branch_4_2/transaction/sr...
I need to find out how this can be done with Arjuna as 4.2.2 will have it , I will look at it . If you want to know about this quicker go to the Transaction forums Or dig code yourself if you are not lazy :)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136292#4136292
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4136292
18 years, 1 month
[Security & JAAS/JBoss] - GSSAPI - AUTHENTICATION
by marcello1975
HI,
I AM USING ACTIVE DIRECTORY TO AUTHENTICATE MY APPLICATION USERS.
I PUT LOGIN CONFIGURATION ON LOGIN-CONFIG.XML AND I AM USING LdapExtLoginModule AS BELLOW.
<application-policy name="AD">
<login-module code="org.jboss.security.auth.spi.LdapExtLoginModule" flag="sufficient">
<module-option name="java.naming.provider.url">ldap://srvspfs.softtek.com.br:389/</module-option>
<module-option name="java.naming.security.authentication">GSSAPI</module-option>
<module-option name="bindDN">cn=Wellington de Oliveira Ferro,ou=GASS,ou=SP,dc=softtek,dc=com,dc=br</module-option>
<module-option name="bindCredential">Turbo43!</module-option>
<module-option name="baseCtxDN">dc=softtek,dc=com,dc=br</module-option>
<module-option name="rolesCtxDN">ou=SP,dc=softtek,dc=com,dc=br</module-option>
<module-option name="baseFilter">(sAMAccountName={0})</module-option>
<module-option name="roleFilter">(member={1})</module-option>
</login-module>
</application-policy>
WHEN I AM USING java.naming.security.authentication AS simple, THERE IS NO PROBLEM. THE APPLICATION AUTHENTICATE OK.
BUT WHEN I TRY TO CHANGE THIS FOR SOME ENCRYPTED AND SAFE SECURITY LIKE (GSSAPI OR Digest-MD5) IT SIMPLY DOESNT WORK.
ANYBODY KNOWS HOW TO PUT IT WORKING?
THE MISSION IS TO GUARANTEE SAFE COMUNICATION BETWEEN JBOSS/JASS AND ACTIVE DIRECTORY.
THE LAST EXCEPTION IS:
Caused by: javax.security.auth.login.LoginException: Missing users.properties file.
BUT I AM NOT USING users.properties... i am going to autheticate in ldap server!!!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136290#4136290
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4136290
18 years, 1 month
[Security & JAAS/JBoss] - GSSAPI - AUTHENTICATION
by marcello1975
HI,
I AM USING ACTIVE DIRECTORY TO AUTHENTICATE MY APPLICATION USERS.
I PUT LOGIN CONFIGURATION ON LOGIN-CONFIG.XML AND I AM USING LdapExtLoginModule AS BELLOW.
<application-policy name="AD">
<login-module code="org.jboss.security.auth.spi.LdapExtLoginModule" flag="sufficient">
<module-option name="java.naming.provider.url">ldap://srvspfs.softtek.com.br:389/</module-option>
<module-option name="java.naming.security.authentication">GSSAPI</module-option>
<module-option name="bindDN">cn=Wellington de Oliveira Ferro,ou=GASS,ou=SP,dc=softtek,dc=com,dc=br</module-option>
<module-option name="bindCredential">Turbo43!</module-option>
<module-option name="baseCtxDN">dc=softtek,dc=com,dc=br</module-option>
<module-option name="rolesCtxDN">ou=SP,dc=softtek,dc=com,dc=br</module-option>
<module-option name="baseFilter">(sAMAccountName={0})</module-option>
<module-option name="roleFilter">(member={1})</module-option>
</login-module>
</application-policy>
WHEN I AM USING java.naming.security.authentication AS simple, THERE IS NO PROBLEM. THE APPLICATION AUTHENTICATE OK.
BUT WHEN I TRY TO CHANGE THIS FOR SOME ENCRYPTED AND SAFE SECURITY LIKE (GSSAPI OR Digest-MD5) IT SIMPLY DOESNT WORK.
ANYBODY KNOWS HOW TO PUT IT WORKING?
THE MISSION IS TO GUARANTEE SAFE COMUNICATION BETWEEN JBOSS/JASS AND ACTIVE DIRECTORY.
THE LAST EXCEPTION IS:
Caused by: javax.security.auth.login.LoginException: Missing users.properties file.
BUT I AM NOT USING users.properties... i am going to autheticate in ldap server!!!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136289#4136289
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4136289
18 years, 1 month