2 Replies Latest reply on Feb 24, 2009 11:06 AM by dimitris

    cannot deploy : Invalid Flag

       

      23:20:47,218 INFO [TomcatDeployment] deploy, ctxPath=/, vfsUrl=ROOT.war
      23:20:47,281 INFO [TomcatDeployment] deploy, ctxPath=/jmx-console, vfsUrl=jmx-console.war
      23:20:47,375 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
      
      *** CONTEXTS IN ERROR: Name -> Error
      
      jboss-web-policy -> java.lang.IllegalArgumentException: Invalid control flag: REQUÄ°RED
      
      jboss-ejb-policy -> java.lang.IllegalArgumentException: Invalid control flag: REQUÄ°RED
      
      
      23:20:47,375 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080
      23:20:47,390 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-localhost%2F127.0.0.1-8009
      23:20:47,406 INFO [ServerImpl] JBoss (Microcontainer) [5.0.0.GA (build: SVNTag=JBoss_5_0_0_GA date=200812042120)] Started in 2m:9s:969ms
      23:21:52,906 INFO [TomcatDeployment] deploy, ctxPath=/ilkJSF, vfsUrl=ilkJSF.war
      23:21:53,109 INFO [StandardContext] The listener "com.sun.faces.config.ConfigureListener" is already configured for this context. The duplicate definition has been ignored.
      23:21:53,546 ERROR [STDERR] 07.Şub.2009 23:21:53 org.zkoss.zk.ui.sys.ConfigParser parseConfigXml:125
      INFO: Loading system default
      23:21:53,687 ERROR [STDERR] 07.Şub.2009 23:21:53 org.zkoss.zk.ui.sys.ConfigParser parse:216
      INFO: Parsing jndi:/localhost/ilkJSF/WEB-INF/zk.xml
      23:21:55,187 WARN [HDScanner] Failed to process changes
      org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
      
      *** CONTEXTS IN ERROR: Name -> Error
      
      jboss-web-policy -> java.lang.IllegalArgumentException: Invalid control flag: REQUÄ°RED
      
      jboss-ejb-policy -> java.lang.IllegalArgumentException: Invalid control flag: REQUÄ°RED
      
      
       at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:863)
       at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:665)
       at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:293)
       at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:221)
       at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
       at java.util.concurrent.FutureTask$Sync.innerRunAndReset(Unknown Source)
       at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
       at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(Unknown Source)
       at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(Unknown Source)
       at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
       at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
       at java.lang.Thread.run(Unknown Source)


      REQUIRED has a letter uppercase of i (in Turkish alphabet). Can it be from regional settings? Using Windows Xp Pro Turkish, Turkish regional settings. (Used also -javaD option for UTF-8 support)

        • 1. Re: cannot deploy : Invalid Flag

          I get the same error. (Vista Business, Turkish regional settings. JVM 1.5, JBOSS AS 5.0)

          I have searched all documents under JBOSS_HOME for capital letters but found none. I wonder where this configuration is coming from.


          *** CONTEXTS IN ERROR: Name -> Error
          
          jboss-web-policy -> java.lang.IllegalArgumentException: Invalid control flag: REQU¦RED
          
          jboss-ejb-policy -> java.lang.IllegalArgumentException: Invalid control flag: REQU¦RED
          
          


          • 2. Re: cannot deploy : Invalid Flag
            dimitris

            You probably have some invalid characters inside your own configuration files.

            Search for .xml file containing "REQU" in your deployments.