Hi Cedric,
I think that you have to bring two settings in JBoss :
1) remove exo-jboss/lib/endorsed/xml-apis.jar, as suggested by the readme.
This is because this library conflicts with the ones provided by JDK version
5 and higher. I think that you have already performed this step.
2) remove exo-jboss/server/default/lib/hibernate3.jar. They made some
changes in JBoss classloader and this library seems to conflict now with the
one provided in exoplatform.sar. We will fix this issue in the next major
version of eXo, where Hibernate will not be a dependency anymore. This is
similar to what Benjamin said about JSF in a previous post.
The manifest entry related exceptions you are seeing are harmless. In fact,
Maven 2 adds Class-Path entries in manifest.mf files. JBoss tries to check
them when deploying the jars and expects them to be located in the sar
archive. This is not the case for some jars, which are either brought by
JBoss, or not needed during run time. I prefer to consider those messages as
warnings. I haven't seen them when I used JBoss default log configuration.
Have you modified the log level in log4j.xml ? If you need to remove those
messages anyhow, there are at least two options to try :
- Move eXo Platform jars to exo-jboss/server/default/lib,
- Remove "manifest.mf" from eXo Platform jars.
HTH,
-Brice.
>
>
>
> -----Forwarded by Brice Revenant/FR/BULL on 01/04/2007 11:11AM -----
>
> To: exoplatform@objectweb.org
> From: cédric.briançon <cbrianco@gmail.com>
> Date: 30/03/2007 10:15AM
> Subject: Re: [exoplatform] Login problem for my Exoplatform config on
> Jboss
>
>
> 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@objectweb.org mailing list.
> >> To unsubscribe: mailto:exoplatform-unsubscribe@objectweb.org<exoplatform-unsubscribe@objectweb.org>
> >> For general help: mailto:sympa@objectweb.org?subject=help<sympa@objectweb.org?subject=help>
> >> ObjectWeb mailing lists service home page:
http://www.objectweb.org/wws> >>
> >
> >
> >
> >
> >
> >
> > --
> > You receive this message as a subscriber of the
> exoplatform@objectweb.org
> > mailing list.
> > To unsubscribe: mailto:exoplatform-unsubscribe@objectweb.org<exoplatform-unsubscribe@objectweb.org>
> > For general help: mailto:sympa@objectweb.org?subject=help<sympa@objectweb.org?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<
http://nabble.com/>
> .
>
>
>
> --
> You receive this message as a subscriber of the exoplatform@objectweb.org mailing list.
> To unsubscribe: mailto:exoplatform-unsubscribe@objectweb.org <exoplatform-unsubscribe@objectweb.org>
> For general help: mailto:sympa@objectweb.org?subject=help <sympa@objectweb.org?subject=help>
> ObjectWeb mailing lists service home page:
http://www.objectweb.org/wws>
>
--
Brice Revenant
eXo Platform SAS
--
You receive this message as a subscriber of the exoplatform@objectweb.org mailing list.
To unsubscribe: mailto:exoplatform-unsubscribe@objectweb.org
For general help: mailto:sympa@objectweb.org?subject=help
ObjectWeb mailing lists service home page:
http://www.objectweb.org/wws
Some parts of this message have been removed.
Learn more about Nabble's security policy.
