« Return to Thread: Login problem for my Exoplatform config on Jboss

Re: Login problem for my Exoplatform config on Jboss

by vetalok :: Rate this Message:

Reply to Author | View in Thread

Some parts of this message have been removed. Learn more about Nabble's security policy.
try to delete
xalan*.jar and jaxp-ri.jar
from
D:\java\exo-working\exo-jboss\server\default\deploy\exoplatform.sar\
instead of copiyng xalan :)

2007/3/30, Vitaliy Obmanjuk <vetalok@...>:
Hello cédric.briançon,

Try to do the following:
1. Deploy jboss.
2. Copy xalan-2.7.0.jar into
D:\java\exo-working\exo-jboss\server\default\deploy\exoplatform.sar\
3. Go to
D:\java\exo-working\exo-jboss\server\default\lib\
delete all hibernate*.jar.
4. Start jboss.
5. Tell me the result :)

2007/3/30, cédric.briançon <cbrianco@...>:

In fact the compile process works well with maven2, the deployment too.
But when I launch my jboss server, I get an enormous log file, where I can
see that some jars seem to lake ...
The error are like this one :
2007-03-29 13:05:00,671 DEBUG [org.jboss.deployment.MainDeployer] new
manifest entry for sdi at exo-jcr.frameworks.web-1.5.jar entry is
drools-smftest-2.0.jar
2007-03-29 13:05:00,687 DEBUG [org.jboss.deployment.MainDeployer] The
manifest entry in
file:/C:/Exoplatform/exo-working/exo-jboss/server/default/deploy/exoplatform.sar/exo-jcr.frameworks.web-1.5.jar
references URL
file:/C:/Exoplatform/exo-working/exo-jboss/server/default/deploy/exoplatform.sar/drools-smftest-2.0.jar
which could not be opened, entry ignored
2007-03-29 13:05:00,687 DEBUG [org.jboss.util.NestedThrowable]
org.jboss.util.NestedThrowable.parentTraceEnabled=true
2007-03-29 13:05:00,687 DEBUG [org.jboss.util.NestedThrowable]
org.jboss.util.NestedThrowable.nestedTraceEnabled=false
2007-03-29 13:05:00,687 DEBUG [org.jboss.util.NestedThrowable ]
org.jboss.util.NestedThrowable.detectDuplicateNesting=true
org.jboss.deployment.DeploymentException: url
file:/C:/Exoplatform/exo-working/exo-jboss/server/default/deploy/exoplatform.sar/drools-smftest-2.0.jar
could not be opened, does it exist?
        at org.jboss.deployment.DeploymentInfo.<init>(DeploymentInfo.java:175)
        [...]

I try to regroup all laking jars error message to only keep the file path :
file:/C:/Exoplatform/exo-working/exo-jboss/server/default/deploy/exoplatform.sar/xercesImpl-2.6.2.jar
exo-jboss/server/default/deploy/exoplatform.sar/velocity-dep-1.4.jar
exo-jboss/server/default/deploy/exoplatform.sar/xml- resolver-1.1.jar
exo-jboss/server/default/deploy/exoplatform.sar/xdoclet-hibernate-module-1.2.3.jar
exo-jboss/server/default/deploy/exoplatform.sar/commons-beanutils-1.7.0.jar
exo-jboss/server/default/deploy/exoplatform.sar/xjavadoc- 1.0.3.jar
exo-jboss/server/default/deploy/exoplatform.sar/exo-platform.test.framework-2.0.3.jar
exo-jboss/server/default/deploy/exoplatform.sar/dom4j-1.6.1.jar
exo-jboss/server/default/deploy/exoplatform.sar/ehcache- 1.1.jar
exo-jboss/server/default/deploy/exoplatform.sar/xdoclet-xdoclet-module-1.2.jar
exo-jboss/server/default/deploy/exoplatform.sar/xdoclet-1.2.3.jar
exo-jboss/server/default/deploy/exoplatform.sar/xml-apis-1.0.b2.jar
exo-jboss/server/default/deploy/exoplatform.sar/jibx-bind-1.0.jar
exo-jboss/server/default/deploy/exoplatform.sar/commons-logging-1.0.4.jar
exo-jboss/server/default/deploy/exoplatform.sar/xmldb-api-20021118.jar
exo-jboss/server/default/deploy/exoplatform.sar/mail-1.3.3.jar
exo-jboss/server/default/deploy/exoplatform.sar/cglib-2.1_3.jar
exo-jboss/server/default/deploy/exoplatform.sar/bcel-5.1.jar
exo-jboss/server/default/deploy/exoplatform.sar/castor- 0.9.7.jar
exo-jboss/server/default/deploy/exoplatform.sar/junit-3.8.1.jar
exo-jboss/server/default/deploy/exoplatform.sar/jmock-1.0.1.jar
exo-jboss/server/default/deploy/exoplatform.sar/commons-codec-1.2.jar
exo-jboss/server/default/deploy/exoplatform.sar/drools- smftest-2.0.jar
exo-jboss/server/default/deploy/exoplatform.sar/commons-digester-1.7.jar
exo-jboss/server/default/deploy/exoplatform.sar/velocity-dep-1.4.jar
exo-jboss/server/default/deploy/exoplatform.sar/xml-resolver-1.1.jar
exo-jboss/server/default/deploy/exoplatform.sar/commons-beanutils-1.7.0.jar
exo-jboss/server/default/deploy/exoplatform.sar/servlet-api-2.3.jar
[...]

Some of these jars are linked to an xml processing, and I have deleted the
jars in the jboss-4.0.3SP1/lib/endorsed directory, as explained at this page
: http://docs.exoplatform.org/exo-documents/exo.site/developer/build.html .
Could it be linked ?
Why these laking jars are not present in the deployment directory ?

Best regards,
Cédric B.


FLORENT.TROLAT wrote:
>
> My litle experience :
> When problems appear :
>
> check serveur is down
> fix server conf on maven settings.xml v2.x profile (JBOSS for you)
> recompile mvn clean install
> redeploy mvn -f exo-product-nana -Dclean
> verify errors
> run serveur.

>
> I've tried with tomcat and Jonas, sorry no experience with JBOSS, but
> when I try to change server if I don't follow the previous process,
> troubles happened.
>
> Good luck.
>
> Florent
>
>
> cédric.briançon a écrit :
>> Hi eXo Platform list,
>>
>> I've compiled with maven2 the exo-ecm project (version 1.2 exoplatform
>> v2.x)
>> to use it on a Jboss application server.
>> I try to log in with the user "exoadmin", but I get an error message-box
>> "User not registered or invalid password" with the following error in the
>> Jboss console :
>> 15:08:20,921 ERROR [eXo]  - [security] error while trying to login
>> javax.security.auth.login.LoginException: Authentication failed
>>         at
>> org.exoplatform.services.security.jaas.BasicLoginModule.login (BasicLoginModule.java:117)
>>
>>         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
>> javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
>>         at
>> javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
>>         at
>> javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
>>         at java.security.AccessController.doPrivileged(Native Method)
>>         at
>> javax.security.auth.login.LoginContext.invokePriv (LoginContext.java:680)
>>         at
>> javax.security.auth.login.LoginContext.login(LoginContext.java:579)
>>         at
>> org.jboss.security.plugins.JaasSecurityManager.defaultLogin (JaasSecurityManager.java:572)
>>
>>         at
>> org.jboss.security.plugins.JaasSecurityManager.authenticate(JaasSecurityManager.java:506)
>>
>>         at
>> org.jboss.security.plugins.JaasSecurityManager.isValid (JaasSecurityManager.java:315)
>>
>>         at
>> org.jboss.web.tomcat.security.JBossSecurityMgrRealm.authenticate(JBossSecurityMgrRealm.java:230)
>>
>>         at
>> org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:256)
>>
>>         at
>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java :391)
>>
>>         at
>> org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
>>
>>         at
>> org.apache.catalina.core.StandardHostValve.invoke (StandardHostValve.java:126)
>>
>>         at
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
>>
>>         at
>> org.apache.catalina.core.StandardEngineValve.invoke (StandardEngineValve.java:107)
>>
>>         at
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
>>
>>         at
>> org.apache.coyote.http11.Http11Processor.process (Http11Processor.java:856)
>>
>>         at
>> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
>>
>>         at
>> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
>>
>>         at
>> org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
>>

>>         at java.lang.Thread.run(Thread.java:595)
>>
>> I get the same authentification error when I try to create a new user.
>> Same problem of login when I deploy the exo-portal project on Jboss.
>> My workstation :
>> - Windows XP
>> - jdk 1.5.0_11
>> - Jboss 4.0.3SP1
>> - an up-to-date exoplatform project v2.x from svn
>> - mvn 2.0.4
>>
>> Thanks for your attention,
>> Cédric B.
>>
>> ------------------------------------------------------------------------
>>
>>
>> --
>> You receive this message as a subscriber of the
>> exoplatform@... mailing list.

>> To unsubscribe: mailto:exoplatform-unsubscribe@...
>> For general help: mailto:sympa@...?subject=help
>> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>>
>
>
>
>
>
>
> --
> You receive this message as a subscriber of the exoplatform@...
> mailing list.
> To unsubscribe: mailto:exoplatform-unsubscribe@...
> For general help: mailto: sympa@... ?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>

--
View this message in context: http://www.nabble.com/Login-problem-for-my-Exoplatform-config-on-Jboss-tf3480289.html#a9749096
Sent from the eXo Platform mailing list archive at Nabble.com.




--
You receive this message as a subscriber of the exoplatform@... mailing list.
To unsubscribe: mailto: exoplatform-unsubscribe@...
For general help: mailto:sympa@...?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws




--
Best regards,
Vitaliy



--
Best regards,
Vitaliy

--
You receive this message as a subscriber of the exoplatform@... mailing list.
To unsubscribe: mailto:exoplatform-unsubscribe@...
For general help: mailto:sympa@...?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

 « Return to Thread: Login problem for my Exoplatform config on Jboss