2 Replies Latest reply on Jul 27, 2006 3:26 PM by Antoine Herzog

    jar in .sar lib : bug or normal behavior ?

    Antoine Herzog Master


      I have a strange behaviour.
      with Jboss 4.0.4 and Portal 2.4.0 CR2.

      I deploy my portal in a main XXX.sar folder, with a XXX.sar/lib sub folder.
      This is for the services (like my own url mapper like portal:commandFactory=CMSObject, etc...) of my portal, and also there are some .war sub folders, for the portlets.

      this is like the main jboss-portal.sar with the lib folder and all the .war folder of jboss portal.

      When I put the jar file : portal-common-lib.jar
      in the deploy/XXX.sar/lib folder, and then start jboss, I have an error (which does not seem related to adding this jar).

      When I take the jar away (with jboss shutdown), jboss starts smoothly... no error

      21:04:58,109 INFO [Server] Core system initialized
      21:04:59,656 INFO [WebService] Using RMI server codebase: http://pca64:8083/
      21:04:59,671 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
      21:04:59,875 INFO [NamingService] JNDI bootstrap JNP=/, RMI=/, backlog=50,
      no client SocketFactory, Server SocketFactory=class org.jboss.net.sockets.DefaultSocketFactory
      21:05:02,656 INFO [AspectDeployer] Deployed AOP: file:/C:/serveurs/jboss-4.0.4/server/shwa/deploy/j
      21:05:04,765 ERROR [MainDeployer] Could not create deployment: file:/C:/serveurs/jboss-4.0.4/server/
      org.jboss.deployment.DeploymentException: - nested throwable: (java.lang.reflect.UndeclaredThrowable
       at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:196)
       at org.jboss.system.ServiceController.install(ServiceController.java:226)
       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:155)
       at org.jboss.mx.server.Invocation.dispatch(Invocation.java:94)
       at org.jboss.mx.server.Invocation.invoke(Invocation.java:86)
       at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
       at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:659)
       at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
       at $Proxy4.install(Unknown Source)
       at org.jboss.deployment.SARDeployer.create(SARDeployer.java:249)
       at org.jboss.deployment.MainDeployer.create(MainDeployer.java:953)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:807)
       at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:771)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

      and many others error follow, all related to deploying modules...

      It does the same with another jar I need : portal-core-lib.jar

      it seems that it does not like having the same jars in two lib folder, even if they are exactly the same.

      is this "normal" ?
      (I am not very familiar with deployement rules)

      It look strange because the error does not say anything about the jar...
      only that the jar "is distrurbing" deployements of many other things...

      how can I use classes from JBoss Portal in my services and portlets, and tell JBoss where it can find the class def ?