Publicité
+ Répondre à la discussion
Affichage des résultats 1 à 3 sur 3
  1. #1
    Candidat au titre de Membre du Club
    Inscrit en
    juillet 2004
    Messages
    57
    Détails du profil
    Informations forums :
    Inscription : juillet 2004
    Messages : 57
    Points : 14
    Points
    14

    Par défaut JONAS : Erreur au démarrage (pb de déclaration d'une application web)

    Bonjour à tous,

    Je suis en train de migrer une application depuis Tomcat 5.5.25 seul (sans Jonas) vers Jonas 4.9.2 (avec Tomcat 5.5.26), dans notre environnement de développement Windows XP SP2.

    J'ai installé Jonas 4.9.2, généré grâce à la commande ant create_jonasbase un environnement pour mon JONAS_BASE.

    Jonas démarre correctement, la console d'administration est accessible. Tout est OK.

    Ensuite, je veux déclarer mon application. Afin de ne pas "gêner" les autres applications, j'ai déclaré une nouvel élement <service> (pour avoir un port spécifique, un répertoire où il n'y aurait que mon appli, ...).

    J'ai donc inséré dans le fichier server.xml les déclarations suivantes extraites de ma conf Tomcat 5.5.25 qui marchait parfaitement.

    Code :
    1
    2
    3
    4
    5
    6
    7
    8
    9
     
      <Service name="IHM">
        <Connector port="8080" enableLookups="false"/>
        <Engine name="Catalina" defaultHost="localhost">
          <Host name="localhost" appBase="webApp" autoDeploy="false">
            <Context path="" docBase=""/>
          </Host>
        </Engine>
      </Service>
    Lors du démarrage, tout se passe d'abord bien.
    Mon application est bien reconnue, la servlet d'initialisation s'exécute bien, les messages "*** Initialisation IHM en cours ....*** Initialisation IHM terminee ***" le démontrent."

    Code :
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    33
    34
    35
    36
    37
    38
    39
    40
    41
    42
    43
    44
    45
    46
    47
    48
    49
    50
    51
    52
    53
    54
    55
     
    JONAS_ROOT is set to C:\appft\JONAS_4_9_2
    JONAS_BASE is set to F:\IHM_JONAS\Moteur_Jonas
    2009-01-28 10:44:18,549 : Server.<init> : JVM used is 1.5.0_12 version of Java HotSpot(TM) Client VM-1.5.0_12-b04/Sun Mi
    crosystems Inc. vendor on Windows XP 5.1/x86 OS.
    2009-01-28 10:44:18,596 : PolicyProvider.init : Using JOnAS PolicyConfigurationFactory provider and JOnAS Policy provide
    r
    2009-01-28 10:44:21,018 : NameServiceManager.startNonStartedNS : Name service for jrmp is started on port 1099
    2009-01-28 10:44:21,065 : ServiceManager.startRegistry : registry service started
    2009-01-28 10:44:21,721 : JmxServiceImpl.doStart : JMX security is DISABLED
    2009-01-28 10:44:21,721 : ServiceManager.startJmx : jmx service started
    2009-01-28 10:44:22,783 : Current.<init> : JOTM 2.0.11
    2009-01-28 10:44:22,815 : Current.setDefaultRecovery : Jotm Recovery= false
    2009-01-28 10:44:22,846 : ServiceManager.startServices : jtm service started
    2009-01-28 10:44:22,986 : HsqlDBServiceImpl.doStart : Starting HSQLDB server 1.8.0 on port 9001
    2009-01-28 10:44:24,252 : HsqlDBServiceImpl.doStart : HSQLDB server started.
    2009-01-28 10:44:24,299 : HsqlDBServiceImpl.doStart : Dropping and adding user 'jonas' with password 'jonas'.
    2009-01-28 10:44:24,315 : ServiceManager.startServices : db service started
    2009-01-28 10:44:24,455 : DataBaseServiceImpl.createDataSource : Mapping ConnectionManager jdbc:hsqldb:hsql://localhost:
    9001/db_jonas on jdbc_1
    2009-01-28 10:44:24,487 : ServiceManager.startServices : dbm service started
    2009-01-28 10:44:25,206 : ServiceManager.startServices : security service started
    2009-01-28 10:44:26,550 : Rar.processRar : F:\IHM_JONAS\Moteur_Jonas\rars\autoload\JOnAS_jdbcCP.rar available
    2009-01-28 10:44:26,722 : Rar.processRar : F:\IHM_JONAS\Moteur_Jonas\rars\autoload\JOnAS_jdbcDM.rar available
    2009-01-28 10:44:26,862 : Rar.processRar : F:\IHM_JONAS\Moteur_Jonas\rars\autoload\JOnAS_jdbcDS.rar available
    2009-01-28 10:44:27,003 : Rar.processRar : F:\IHM_JONAS\Moteur_Jonas\rars\autoload\JOnAS_jdbcXA.rar available
    2009-01-28 10:44:27,581 : Rar.processRar : Starting deployment of F:\IHM_JONAS\Moteur_Jonas\rars\autoload\joram_for_jona
    s_ra.rar
    2009-01-28 10:44:27,675 : JoramAdapter.<init> : JORAM adapter instantiated.
    2009-01-28 10:44:27,784 : JoramAdapter.start : JORAM adapter starting deployment...
    2009-01-28 10:44:27,784 : JoramAdapter.start :   - Collocated JORAM server is starting...
    2009-01-28 10:44:28,816 : JoramAdapter.start :   - Collocated JORAM server has successfully started.
    2009-01-28 10:44:28,816 : JoramAdapter.start :   - Reading the provided admin file: joramAdmin.xml
    2009-01-28 10:44:29,300 : JoramAdapter.start :   - Reading the provided admin file: joramAdminExport.xml
    2009-01-28 10:44:29,300 : JoramAdapter.start : joramAdminExport.xml not found.
    2009-01-28 10:44:29,316 : JoramAdapter.start : Server port is 16010
    2009-01-28 10:44:29,316 : JoramAdapter.start : JORAM adapter 4.3.33 successfully deployed.
    2009-01-28 10:44:29,519 : Rar.processRar : F:\IHM_JONAS\Moteur_Jonas\rars\autoload\joram_for_jonas_ra.rar available
    2009-01-28 10:44:29,535 : ServiceManager.startServices : resource service started
    2009-01-28 10:44:29,551 : ServiceManager.startServices : ejb service started
    2009-01-28 10:44:29,847 : ServiceManager.startServices : ws service started
    2009-01-28 10:44:31,770 : Http11BaseProtocol.init : Initializing Coyote HTTP/1.1 on http-8080
    2009-01-28 10:44:31,770 : Http11BaseProtocol.init : Initializing Coyote HTTP/1.1 on http-9000
    2009-01-28 10:44:31,848 : JAASRealm.setContainer : Set JAAS app name jonas
    2009-01-28 10:44:31,864 : StandardService.start : Starting service IHM
    2009-01-28 10:44:31,879 : StandardEngine.start : Starting Servlet Engine: Apache Tomcat/5.5.26
    2009-01-28 10:44:31,879 : StandardHost.start : XML validation disabled
    Sun Microsystems Inc. / Java HotSpot(TM) Client VM / 1.5.0_12-b04
    Produits : Xerces-J 2.7.1 / Xalan Java 2.6.0
     
    *** Initialisation IHM en cours ....
    Classe de instanceDocumentBuilderFactory : org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
    Classe de instanceTransformerFactory : org.apache.xalan.processor.TransformerFactoryImpl
    ..
    *** Initialisation IHM terminee ***
    Mais après, tout se précipite :
    Code :
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    33
    34
    35
    36
    37
    38
    39
    40
    41
    42
    43
    44
    45
    46
    47
    48
    49
    50
    51
    52
    53
    54
    55
    56
    57
    58
    59
    60
    61
    62
    63
    64
    65
     
    2009-01-28 10:44:54,589 : Http11BaseProtocol.start : Starting Coyote HTTP/1.1 on http-8080
    2009-01-28 10:44:54,729 : StandardService.start : Starting service Tomcat-JOnAS
    2009-01-28 10:44:54,729 : StandardEngine.start : Starting Servlet Engine: Apache Tomcat/5.5.26
    2009-01-28 10:44:54,792 : StandardHost.start : XML validation disabled
    2009-01-28 10:44:54,807 : Http11BaseProtocol.start : Starting Coyote HTTP/1.1 on http-9000
    2009-01-28 10:44:54,948 : StoreLoader.load : Find registry server-registry.xml at classpath resource
    2009-01-28 10:44:55,854 : Server.start : Erreur JOnAS : Incapable de demarrer le serveur 'jonas'.  Exception: java.lang.
    Exception: org.objectweb.jonas.service.ServiceException : Cannot init/start service 'web': Problems when invoking start:
     java.lang.IllegalArgumentException: addChild:  Child name '' is not unique: org.objectweb.jonas.service.ServiceExceptio
    n : Problems when invoking start: java.lang.IllegalArgumentException: addChild:  Child name '' is not unique
    JOnAS halting
    ArrÛt du serveur JOnAS 'jonas'
    2009-01-28 10:44:55,854 : Server.stop : Le serveur JOnAS 'jonas' a ÚtÚ arrÛtÚ
     
    F:\IHM_JONAS\Moteur_Jonas\scripts>2009-01-28 10:45:00,903 : JoramAdapter.stop : JORAM adapter stopping...
    2009-01-28 10:45:01,418 : JoramAdapter.stop : JORAM adapter successfully stopped.
    Exception during execution of org.objectweb.jonas.server.Server : Error in Server start
    java.lang.Exception: Error in Server start
            at org.objectweb.jonas.server.Server.start(Server.java:653)
            at org.objectweb.jonas.server.Server.main(Server.java:199)
            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.objectweb.jonas.server.Bootstrap.main(Bootstrap.java:97)
    Caused by: java.lang.Exception: org.objectweb.jonas.service.ServiceException : Cannot init/start service 'web': Problems
     when invoking start: java.lang.IllegalArgumentException: addChild:  Child name '' is not unique: org.objectweb.jonas.se
    rvice.ServiceException : Problems when invoking start: java.lang.IllegalArgumentException: addChild:  Child name '' is n
    ot unique
            at org.objectweb.jonas.server.Server$1.run(Server.java:617)
    Caused by: org.objectweb.jonas.service.ServiceException : Cannot init/start service 'web': Problems when invoking start:
     java.lang.IllegalArgumentException: addChild:  Child name '' is not unique: org.objectweb.jonas.service.ServiceExceptio
    n : Problems when invoking start: java.lang.IllegalArgumentException: addChild:  Child name '' is not unique
            at org.objectweb.jonas.service.ServiceManager.startServices(ServiceManager.java:339)
            at org.objectweb.jonas.server.Server$1.run(Server.java:579)
    Caused by: org.objectweb.jonas.service.ServiceException : Problems when invoking start: java.lang.IllegalArgumentExcepti
    on: addChild:  Child name '' is not unique
            at org.objectweb.jonas.web.wrapper.catalina55.CatalinaJWebContainerServiceWrapper.invoke(CatalinaJWebContainerSe
    rviceWrapper.java:165)
            at org.objectweb.jonas.web.wrapper.catalina55.CatalinaJWebContainerServiceWrapper.start(CatalinaJWebContainerSer
    viceWrapper.java:528)
            at org.objectweb.jonas.service.ServiceManager.startServices(ServiceManager.java:336)
            ... 1 more
    Caused by: java.lang.IllegalArgumentException: addChild:  Child name '' is not unique
            at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:750)
            at org.apache.catalina.core.ContainerBase.access$000(ContainerBase.java:122)
            at org.apache.catalina.core.ContainerBase$PrivilegedAddChild.run(ContainerBase.java:144)
            at java.security.AccessController.doPrivileged(Native Method)
            at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:738)
            at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544)
            at org.objectweb.jonas.web.catalina55.CatalinaJWebContainerServiceImpl.doRegisterWar(CatalinaJWebContainerServic
    eImpl.java:570)
            at org.objectweb.jonas.web.AbsJWebContainerServiceImpl.registerWar(AbsJWebContainerServiceImpl.java:867)
            at org.objectweb.jonas.web.AbsJWebContainerServiceImpl.doStart(AbsJWebContainerServiceImpl.java:393)
            at org.objectweb.jonas.web.catalina55.CatalinaJWebContainerServiceImpl.doStart(CatalinaJWebContainerServiceImpl.
    java:297)
            at org.objectweb.jonas.service.AbsServiceImpl.start(AbsServiceImpl.java:80)
            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.objectweb.jonas.web.wrapper.catalina55.CatalinaJWebContainerServiceWrapper.invoke(CatalinaJWebContainerSe
    rviceWrapper.java:157)
            ... 3 more
    Le service IHM (mon appli) semble démarrer, c'est le service "Tomcat-JOnAS" qui tombe en erreur.

    Comment déclarer mon appli pour que tout fonctionne ?

    Merci d'avance.

    Ci-dessous, le fichier server.xml initial
    Code :
    1
    2
    3
    4
    5
    6
    7
    8
    9
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20
    21
    22
    23
    24
    25
    26
    27
    28
    29
    30
    31
    32
    33
    34
    35
    36
    37
    38
    39
    40
    41
    42
    43
    44
    45
    46
    47
    48
    49
    50
    51
    52
    53
    54
    55
    56
    57
    58
    59
    60
    61
    62
    63
    64
    65
    66
    67
    68
    69
    70
    71
    72
    73
    74
    75
    76
    77
    78
    79
    80
    81
    82
    83
    84
    85
    86
    87
    88
    89
    90
    91
    92
    93
    94
    95
    96
    97
    98
    99
    100
    101
    102
    103
    104
    105
    106
    107
    108
    109
    110
    111
    112
    113
    114
    115
    116
    117
    118
    119
    120
    121
    122
    123
    124
    125
    126
    127
    128
    129
    130
    131
    132
    133
    134
    135
    136
    137
    138
    139
    140
    141
    142
    143
    144
    145
    146
    147
    148
    149
    150
    151
    152
    153
    154
    155
    156
    157
    158
    159
    160
    161
    162
    163
    164
    165
    166
    167
    168
    169
    170
    171
    172
    173
    174
    175
    176
    177
    178
    179
    180
    181
    182
    183
    184
    185
    186
    187
    188
    189
    190
    191
    192
    193
    194
    195
    196
    197
    198
    199
    200
    201
    202
    203
    204
    205
    206
    207
    208
    209
    210
    211
    212
    213
    214
    215
    216
    217
    218
    219
    220
    221
    222
    223
    224
    225
    226
    227
    228
    229
    230
    231
    232
    233
    234
    235
    236
    237
    238
    239
    240
    241
    242
    243
    244
    245
    246
    247
    248
    249
    250
    251
    252
    253
    254
    255
    256
    257
    258
    259
    260
    261
    262
    263
    264
    265
    266
    267
    268
    269
    270
    271
    272
    273
    274
    275
    276
    277
    278
    279
    280
    281
    282
    283
    284
    285
    286
    287
    288
    289
    290
    291
    292
    293
    294
    295
    296
    297
    298
    299
    300
    301
    302
    303
    304
    305
    306
    307
    308
    309
    310
    311
    312
    313
    314
    315
    316
    317
    318
    319
    320
    321
    322
    323
    324
    325
    326
    327
    328
    329
    330
    331
    332
    333
    334
    335
    336
    337
    338
    339
    340
    341
    342
    343
    344
    345
    346
    347
    348
    349
    350
     
    <?xml version='1.0' encoding='utf-8'?>
     
    <!--
     - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
     - Tomcat 5.5 server.xml file with some configuration steps for JOnAS already done.
     -   Realm already set
     -   Examples with a JOnASStandardContext context.
     -
     - $Id: server.xml 7934 2006-01-25 15:43:30Z sauthieg $
     - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
     -->
     
    <!-- Note that component elements are nested corresponding to their
         parent-child relationships with each other -->
     
    <!-- A "Server" is a singleton element that represents the entire JVM,
         which may contain one or more "Service" instances.  The Server
         listens for a shutdown command on the indicated port.
     
         Note:  A "Server" is not itself a "Container", so you may not
         define subcomponents such as "Valves" or "Loggers" at this level.
     -->
     
    <Server>
     
     
      <!-- Comment these entries out to disable JMX MBeans support used for the
           administration web application -->
      <!-- APR listener : uncomment this listener to enable autodection
           of APR and HTTP connector using APR
       <Listener className="org.apache.catalina.core.AprLifecycleListener" />
      -->
      <Listener className="org.apache.catalina.mbeans.ServerLifecycleListener" />
      <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
      <Listener className="org.apache.catalina.storeconfig.StoreConfigLifecycleListener"/>
     
      <!-- No Global JNDI resources. Use JOnAS resources -->
      <GlobalNamingResources>
      </GlobalNamingResources>
     
      <!-- A "Service" is a collection of one or more "Connectors" that share
           a single "Container" (and therefore the web applications visible
           within that Container).  Normally, that Container is an "Engine",
           but this is not required.
     
           Note:  A "Service" is not itself a "Container", so you may not
           define subcomponents such as "Valves" or "Loggers" at this level.
       -->
     
      <!-- Define the Tomcat Stand-Alone Service -->
      <Service name="Tomcat-JOnAS">
     
        <!-- A "Connector" represents an endpoint by which requests are received
             and responses are returned.  Each Connector passes requests on to the
             associated "Container" (normally an Engine) for processing.
     
             By default, a non-SSL HTTP/1.1 Connector is established on port 8080.
             You can also enable an SSL HTTP/1.1 Connector on port 8443 by
             following the instructions below and uncommenting the second Connector
             entry.  SSL support requires the following steps (see the SSL Config
             HOWTO in the Tomcat 5 documentation bundle for more detailed
             instructions):
             * If your JDK version 1.3 or prior, download and install JSSE 1.0.2 or
               later, and put the JAR files into "$JAVA_HOME/jre/lib/ext".
             * Execute:
                 %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)
                 $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA  (Unix)
               with a password value of "changeit" for both the certificate and
               the keystore itself.
     
             By default, DNS lookups are enabled when a web application calls
             request.getRemoteHost().  This can have an adverse impact on
             performance, so you can disable it by setting the
             "enableLookups" attribute to "false".  When DNS lookups are disabled,
             request.getRemoteHost() will return the String version of the
             IP address of the remote client.
        -->
     
     
        <!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 9000 -->
        <Connector port="9000" maxHttpHeaderSize="8192"
                   maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
                   enableLookups="false" redirectPort="9043" acceptCount="100"
                   connectionTimeout="20000" disableUploadTimeout="true" />
        <!-- Note : To disable connection timeouts, set connectionTimeout value
         to 0 -->
     
    	<!-- Note : To use gzip compression you could set the following properties :
     
    			   compression="on"
    			   compressionMinSize="2048"
    			   noCompressionUserAgents="gozilla, traviata"
    			   compressableMimeType="text/html,text/xml"
    	-->
     
        <!-- Define a SSL Coyote HTTP/1.1 Connector on port 9043 -->
        <!--
        <Connector port="9043" maxHttpHeaderSize="8192"
                   maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
                   enableLookups="false" disableUploadTimeout="true"
                   acceptCount="100" scheme="https" secure="true"
                   clientAuth="false" sslProtocol="TLS" />
        -->
     
     
       <!-- Define an AJP 1.3 Connector on port 8009
        <Connector port="8009"
                   enableLookups="false" redirectPort="9043" protocol="AJP/1.3" />
        -->
     
        <!-- Define a Proxied HTTP/1.1 Connector on port 8082 -->
        <!-- See proxy documentation for more information about using this. -->
        <!--
        <Connector port="8082"
                   maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
                   enableLookups="false" acceptCount="100" connectionTimeout="20000"
                   proxyPort="80" disableUploadTimeout="true" />
        -->
     
        <!-- An Engine represents the entry point (within Catalina) that processes
             every request.  The Engine implementation for Tomcat stand alone
             analyzes the HTTP headers included with the request, and passes them
             on to the appropriate Host (virtual host). -->
     
        <!-- You should set jvmRoute to support load-balancing via AJP ie :
        <Engine name="Standalone" defaultHost="localhost" jvmRoute="jvm1">
        -->
     
        <!-- Define the top level container in our container hierarchy -->
        <Engine name="jonas" defaultHost="localhost">
          <!-- The request dumper valve dumps useful debugging information about
               the request headers and cookies that were received, and the response
               headers and cookies that were sent, for all requests received by
               this instance of Tomcat.  If you care only about requests to a
               particular virtual host, or a particular application, nest this
               element inside the corresponding <Host> or <Context> entry instead.
     
               For a similar mechanism that is portable to all Servlet 2.4
               containers, check out the "RequestDumperFilter" Filter in the
               example application (the source for this filter may be found in
               "$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters").
     
               Request dumping is disabled by default.  Uncomment the following
               element to enable it. -->
          <!--
          <Valve className="org.apache.catalina.valves.RequestDumperValve"/>
          -->
     
          <!-- Because this Realm is here, an instance will be shared globally -->
     
          <!-- This Realm uses the JOnAS resource memrlm_1
               defined by JONAS_BASE/conf/jonas-realm.xml file -->
          <Realm className="org.objectweb.jonas.security.realm.web.catalina55.JACC" resourceName="memrlm_1" />
     
          <!-- Note that the validation can be turned on/off in JOnAS configuration
               So, in order to avoid to make the validation twice, it's recommended
               to let the validation to off.
               Add the following attributes if you want to turn XML validation
               on. Remember to comment the Host element above. -->
          <!-- Define the default virtual host -->
          <Host name="localhost" debug="0" appBase="webapps"
           unpackWARs="false" autoDeploy="false"
           deployOnStartup="false" deployXML="false">
     
            <!-- Defines a cluster for this node,
                 By defining this element, means that every manager will be changed.
                 So when running a cluster, only make sure that you have webapps in there
                 that need to be clustered and remove the other ones.
                 A cluster has the following parameters:
     
                 className = the fully qualified name of the cluster class
     
                 name = a descriptive name for your cluster, can be anything
     
                 mcastAddr = the multicast address, has to be the same for all the nodes
     
                 mcastPort = the multicast port, has to be the same for all the nodes
     
                 mcastBindAddr = bind the multicast socket to a specific address
     
                 mcastTTL = the multicast TTL if you want to limit your broadcast
     
                 mcastSoTimeout = the multicast readtimeout
     
                 mcastFrequency = the number of milliseconds in between sending a "I'm alive" heartbeat
     
                 mcastDropTime = the number a milliseconds before a node is considered "dead" if no heartbeat is received
     
                 tcpThreadCount = the number of threads to handle incoming replication requests, optimal would be the same amount of threads as nodes
     
                 tcpListenAddress = the listen address (bind address) for TCP cluster request on this host,
                                    in case of multiple ethernet cards.
                                    auto means that address becomes
                                    InetAddress.getLocalHost().getHostAddress()
     
                 tcpListenPort = the tcp listen port
     
                 tcpSelectorTimeout = the timeout (ms) for the Selector.select() method in case the OS
                                      has a wakup bug in java.nio. Set to 0 for no timeout
     
                 printToScreen = true means that managers will also print to std.out
     
                 expireSessionsOnShutdown = true means that
     
                 useDirtyFlag = true means that we only replicate a session after setAttribute,removeAttribute has been called.
                                false means to replicate the session after each request.
                                false means that replication would work for the following piece of code: (only for SimpleTcpReplicationManager)
                                <%
                                HashMap map = (HashMap)session.getAttribute("map");
                                map.put("key","value");
                                %>
                 replicationMode = can be either 'pooled', 'synchronous' or 'asynchronous'.
                                   * Pooled means that the replication happens using several sockets in a synchronous way. Ie, the data gets replicated, then the request return. This is the same as the 'synchronous' setting except it uses a pool of sockets, hence it is multithreaded. This is the fastest and safest configuration. To use this, also increase the nr of tcp threads that you have dealing with replication.
                                   * Synchronous means that the thread that executes the request, is also the
                                   thread the replicates the data to the other nodes, and will not return until all
                                   nodes have received the information.
                                   * Asynchronous means that there is a specific 'sender' thread for each cluster node,
                                   so the request thread will queue the replication request into a "smart" queue,
                                   and then return to the client.
                                   The "smart" queue is a queue where when a session is added to the queue, and the same session
                                   already exists in the queue from a previous request, that session will be replaced
                                   in the queue instead of replicating two requests. This almost never happens, unless there is a
                                   large network delay.
            -->
            <!--
                When configuring for clustering, you also add in a valve to catch all the requests
                coming in, at the end of the request, the session may or may not be replicated.
                A session is replicated if and only if all the conditions are met:
                1. useDirtyFlag is true or setAttribute or removeAttribute has been called AND
                2. a session exists (has been created)
                3. the request is not trapped by the "filter" attribute
     
                The filter attribute is to filter out requests that could not modify the session,
                hence we don't replicate the session after the end of this request.
                The filter is negative, ie, anything you put in the filter, you mean to filter out,
                ie, no replication will be done on requests that match one of the filters.
                The filter attribute is delimited by ;, so you can't escape out ; even if you wanted to.
     
                filter=".*\.gif;.*\.js;" means that we will not replicate the session after requests with the URI
                ending with .gif and .js are intercepted.
     
                The deployer element can be used to deploy apps cluster wide.
                Currently the deployment only deploys/undeploys to working members in the cluster
                so no WARs are copied upons startup of a broken node.
                The deployer watches a directory (watchDir) for WAR files when watchEnabled="true"
                When a new war file is added the war gets deployed to the local instance,
                and then deployed to the other instances in the cluster.
                When a war file is deleted from the watchDir the war is undeployed locally
                and cluster wide
            -->
     
            <!--
            <Cluster className="org.apache.catalina.cluster.tcp.SimpleTcpCluster"
                     managerClassName="org.apache.catalina.cluster.session.DeltaManager"
                     expireSessionsOnShutdown="false"
                     useDirtyFlag="true"
                     notifyListenersOnReplication="true">
     
                <Membership
                    className="org.apache.catalina.cluster.mcast.McastService"
                    mcastAddr="228.0.0.4"
                    mcastPort="45564"
                    mcastFrequency="500"
                    mcastDropTime="3000"/>
     
                <Receiver
                    className="org.apache.catalina.cluster.tcp.ReplicationListener"
                    tcpListenAddress="auto"
                    tcpListenPort="4001"
                    tcpSelectorTimeout="100"
                    tcpThreadCount="6"/>
     
                <Sender
                    className="org.apache.catalina.cluster.tcp.ReplicationTransmitter"
                    replicationMode="pooled"
                    ackTimeout="15000"/>
     
                <Valve className="org.apache.catalina.cluster.tcp.ReplicationValve"
                       filter=".*\.gif;.*\.js;.*\.jpg;.*\.png;.*\.htm;.*\.html;.*\.css;.*\.txt;"/>
     
                <Deployer className="org.apache.catalina.cluster.deploy.FarmWarDeployer"
                          tempDir="/tmp/war-temp/"
                          deployDir="/tmp/war-deploy/"
                          watchDir="/tmp/war-listen/"
                          watchEnabled="false"/>
            </Cluster>
            -->
     
     
     
            <!-- Normally, users must authenticate themselves to each web app
                 individually.  Uncomment the following entry if you would like
                 a user to be authenticated the first time they encounter a
                 resource protected by a security constraint, and then have that
                 user identity maintained across *all* web applications contained
                 in this virtual host. -->
            <!--
            <Valve className="org.apache.catalina.authenticator.SingleSignOn" />
            -->
     
            <!-- Access log processes all requests for this virtual host.  By
                 default, log files are created in the "logs" directory relative to
                 $CATALINA_HOME.  If you wish, you can specify a different
                 directory with the "directory" attribute.  Specify either a relative
                 (to $CATALINA_HOME) or absolute path to the desired directory.
            -->
            <!--
            <Valve className="org.apache.catalina.valves.AccessLogValve"
                     directory="logs"  prefix="localhost_access_log." suffix=".txt"
                     pattern="common" resolveHosts="false"/>
            -->
     
            <!-- Access log processes all requests for this virtual host.  By
                 default, log files are created in the "logs" directory relative to
                 $CATALINA_HOME.  If you wish, you can specify a different
                 directory with the "directory" attribute.  Specify either a relative
                 (to $CATALINA_HOME) or absolute path to the desired directory.
                 This access log implementation is optimized for maximum performance,
                 but is hardcoded to support only the "common" and "combined" patterns.
            -->
            <!--
            <Valve className="org.apache.catalina.valves.FastCommonAccessLogValve"
                     directory="logs"  prefix="localhost_access_log." suffix=".txt"
                     pattern="common" resolveHosts="false"/>
            -->
            <!-- Access log processes all requests for this virtual host.  By
                 default, log files are created in the "logs" directory relative to
                 $CATALINA_HOME.  If you wish, you can specify a different
                 directory with the "directory" attribute.  Specify either a relative
                 (to $CATALINA_HOME) or absolute path to the desired directory.
                 This access log implementation is optimized for maximum performance,
                 but is hardcoded to support only the "common" and "combined" patterns.
     
                 This valve use NIO direct Byte Buffer to asynchornously store the
                 log.
            -->
            <!--
            <Valve className="org.apache.catalina.valves.ByteBufferAccessLogValve"
                     directory="logs"  prefix="localhost_access_log." suffix=".txt"
                     pattern="common" resolveHosts="false"/>
            -->
     
          </Host>
     
        </Engine>
     
      </Service>
     
    </Server>

  2. #2
    Membre VIP Avatar de kalysto
    Profil pro Guillaume Sauthier
    Développeur
    Inscrit en
    mars 2003
    Messages
    442
    Détails du profil
    Informations personnelles :
    Nom : Guillaume Sauthier
    Localisation : France, Isère (Rhône Alpes)

    Informations professionnelles :
    Activité : Développeur

    Informations forums :
    Inscription : mars 2003
    Messages : 442
    Points : 510
    Points
    510

    Par défaut

    Desolé pour le délai ...

    Hmmm, ce n'est pas un cas habituel ca
    Alors, sans garanties que ca marche, vous pourriez essayer de specifier, dans le jonas-web.xml le nom du Host sur lequel deployer la webapp.

  3. #3
    Membre Expert
    Avatar de hasalex
    Homme Profil pro Alexis Hassler
    Inscrit en
    janvier 2009
    Messages
    810
    Détails du profil
    Informations personnelles :
    Nom : Homme Alexis Hassler
    Âge : 44
    Localisation : France, Rhône (Rhône Alpes)

    Informations forums :
    Inscription : janvier 2009
    Messages : 810
    Points : 1 070
    Points
    1 070

    Par défaut

    Je tente ma chance, mais sans garantie : est-ce que le path="" ne serait pas déjà pris par l'application ROOT ?

Liens sociaux

Règles de messages

  • Vous ne pouvez pas créer de nouvelles discussions
  • Vous ne pouvez pas envoyer des réponses
  • Vous ne pouvez pas envoyer des pièces jointes
  • Vous ne pouvez pas modifier vos messages
  •