10 Replies Latest reply on Nov 5, 2012 10:13 AM by Radoslav Husar

    Farming Service Help - jboss 5.1

    Raju Nue Newbie

      Following error throwing when trying to deploy application as Farming service in Jboss5.1

       

      2011-09-28 05:38:07,883 WARN  [org.jboss.system.server.profileservice.hotdeploy.HDScanner] (HDScanner) Scan failed

      java.lang.IllegalArgumentException: Null base

       

      Please help me how to resolve this

        • 1. Re: Farming Service Help - jboss 5.1
          Wolf-Dieter Fink Master

          Any other information, e.g. stacktrace?

          Do you drop a application EAR into the farming directory or what do you meant by 'deploy application as Farming service'?

          How do you configure JBoss? do you use the 'all' configuration and what do you have changed?

          • 2. Re: Farming Service Help - jboss 5.1
            Raju Nue Newbie

            I have dropped app.war folder ( exploaded web folder structure ) in farm directory of all configuration.  And i have used all configuration but i didn't changes any configuration in jboss.  And the start scripts are below given:

             

            ./run.sh -c all1 -g Partition -u 239.255.100.100 -b 'ServerIP' -Djboss.messaging.ServerPeerID=0 -Djboss.service.binding.set=ports-01

             

            ./run.sh -c all2 -g Partition -u 239.255.100.100 -b 'ServerIP' -Djboss.messaging.ServerPeerID=1 -Djboss.service.binding.set=ports-02

            • 3. Re: Farming Service Help - jboss 5.1
              Wolf-Dieter Fink Master

              Do you have any additional information within the logfile?

               

              Also is a deploy without any cluster sucessful, you might use the default configuration?

              I suppose it can be an issue apart from clustering.

              • 4. Re: Farming Service Help - jboss 5.1
                Raju Nue Newbie

                Thanks for your reply.

                 

                But as per document farming is enabled on all configuraiton,  because of that I am trying all instead of default configuration.

                 

                and coming to cluster,  let me go back and see.

                • 5. Re: Farming Service Help - jboss 5.1
                  Wolf-Dieter Fink Master

                  My idea is to check whether the deploy works without farming. The deploy scanner will be the same regardless you use default or all configuration.

                  If the same problem is without farming maybe you get a different error or stacktrace that helps.

                  • 6. Re: Farming Service Help - jboss 5.1
                    Raju Nue Newbie

                    without farming the deployment is working fine and i am able to access the application.

                     

                    Here I am providing the full exception for your reference:

                     

                    Node 1 Exception trace:

                     

                    2011-09-28 06:12:10,297 WARN  [org.jboss.system.server.profileservice.hotdeploy.HDScanner] (HDScanner) Scan failed

                    java.lang.IllegalArgumentException: Null toCopy

                        at org.jboss.system.server.profileservice.repository.clustered.metadata.RepositoryContentMetadata.<init>(RepositoryContentMetadata.java:97)

                        at org.jboss.profileservice.cluster.repository.DefaultRepositoryClusteringHandler$RpcTarget.initiateSynchronization(DefaultRepositoryClusteringHandler.java:997)

                        at sun.reflect.GeneratedMethodAccessor293.invoke(Unknown Source)

                        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

                        at java.lang.reflect.Method.invoke(Method.java:597)

                        at org.jgroups.blocks.MethodCall.invoke(MethodCall.java:331)

                        at org.jboss.ha.framework.server.ClusterPartition$RpcHandler.handle(ClusterPartition.java:2313)

                        at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:637)

                        at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:545)

                        at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:368)

                        at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.up(MessageDispatcher.java:775)

                        at org.jgroups.JChannel.up(JChannel.java:1336)

                        at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:454)

                        at org.jgroups.protocols.pbcast.FLUSH.up(FLUSH.java:490)

                        at org.jgroups.protocols.pbcast.STATE_TRANSFER.up(STATE_TRANSFER.java:153)

                        at org.jgroups.protocols.FRAG2.up(FRAG2.java:188)

                        at org.jgroups.protocols.FC.up(FC.java:473)

                        at org.jgroups.protocols.pbcast.GMS.up(GMS.java:821)

                        at org.jgroups.protocols.VIEW_SYNC.up(VIEW_SYNC.java:192)

                        at org.jgroups.protocols.pbcast.STABLE.up(STABLE.java:233)

                        at org.jgroups.protocols.UNICAST.up(UNICAST.java:328)

                        at org.jgroups.protocols.pbcast.NAKACK.handleMessage(NAKACK.java:895)

                        at org.jgroups.protocols.pbcast.NAKACK.up(NAKACK.java:708)

                        at org.jgroups.protocols.BARRIER.up(BARRIER.java:136)

                        at org.jgroups.protocols.VERIFY_SUSPECT.up(VERIFY_SUSPECT.java:167)

                        at org.jgroups.protocols.FD.up(FD.java:284)

                        at org.jgroups.protocols.FD_SOCK.up(FD_SOCK.java:328)

                        at org.jgroups.protocols.MERGE2.up(MERGE2.java:144)

                        at org.jgroups.protocols.Discovery.up(Discovery.java:264)

                        at org.jgroups.protocols.PING.up(PING.java:273)

                        at org.jgroups.protocols.TP$ProtocolAdapter.up(TP.java:2319)

                        at org.jgroups.protocols.TP.passMessageUp(TP.java:1253)

                        at org.jgroups.protocols.TP.access$100(TP.java:50)

                        at org.jgroups.protocols.TP$IncomingPacket.handleMyMessage(TP.java:1830)

                        at org.jgroups.protocols.TP$IncomingPacket.run(TP.java:1809)

                        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

                        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

                        at java.lang.Thread.run(Thread.java:662)

                     

                    Node 2 trace:

                     

                    2011-09-28 05:38:07,883 WARN  [org.jboss.system.server.profileservice.hotdeploy.HDScanner] (HDScanner) Scan failed

                    java.lang.IllegalArgumentException: Null base

                        at org.jboss.system.server.profileservice.repository.clustered.sync.AbstractContentModificationGenerator.getModificationList(AbstractContentModificationGenerator.java:55)

                        at org.jboss.profileservice.cluster.repository.DefaultRepositoryClusteringHandler.getLocalModifications(DefaultRepositoryClusteringHandler.java:554)

                        at org.jboss.profileservice.cluster.repository.DefaultRepositoryClusteringHandler.synchronizeContent(DefaultRepositoryClusteringHandler.java:319)

                        at org.jboss.system.server.profileservice.repository.clustered.ClusteredDeploymentRepository.getModifiedDeployments(ClusteredDeploymentRepository.java:429)

                        at org.jboss.system.server.profile.repository.AbstractProfile.getModifiedDeployments(AbstractProfile.java:128)

                        at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:375)

                        at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:294)

                        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)

                        at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)

                        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)

                        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)

                        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)

                        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)

                        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)

                        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)

                        at java.lang.Thread.run(Thread.java:662)

                    • 7. Re: Farming Service Help - jboss 5.1
                      Radoslav Husar Master

                      Hi Raju, exploded archives were not supported in 4.x and in 5.1 (where they were added) might have not been very well tested, can you try to use a single file instead of exploded deployment?

                      • 8. Re: Farming Service Help - jboss 5.1
                        Raju Nue Newbie

                        It is supporting folder directory structure as well,  but we need to create the base directory (  application directory ) on the other nodes.

                        • 9. Re: Farming Service Help - jboss 5.1
                          priyakpandey Newbie

                          Hi Raju,

                           

                          What do you mean by creating base directory?

                           

                          I am trying to setup cluster on linux with jboss 5.1. Currently I am tying to setup two node cluster.

                          I am trying to deploy war in exploded format (farm deployment strategy).

                          Node1 server starts properly and the application gets deployed without any issue. I can access the webpage successfully.

                          When I start node2 I get 'Null Base' exception. When i look at the content under farm dir, I see that the required folders gets created at the server startup but files are not copied

                           

                          When you say we have to create base directory on the other nodes of the cluster what does it exactly mean?

                          Let us assume for e.g. my applicaiton has following structure,

                          sample.war

                               - dir1

                                - dir2

                                -WEB-INF

                                    -lib

                                     -classes

                                         -com

                                              -sample

                                                   -test

                                                        -Test.class

                                - aa.xhtml

                                -bb.xhtml

                           

                          Help would be greately appreciated.

                          Thanking You.

                          • 10. Re: Farming Service Help - jboss 5.1
                            Radoslav Husar Master

                            As I said earlier, these are not well tested thus not recommended.

                             

                            I believe Raju meant creating a directory in farm/<application directory> on all cluster nodes.