[svn:bz-trunk] 5034: Avoid the NPE during server shutdown.

Revision: 5034
Author: [email protected]
Date: 2009-02-22 05:59:29 -0800 (Sun, 22 Feb 2009)
Log Message:
Avoid the NPE during server shutdown.
Modified Paths:
blazeds/trunk/modules/core/src/flex/messaging/factories/JavaFactory.java

I am modifying the correct httpd.conf file on the server, it just doesn't seem to work. - If I put the rewrite rules in the <Directory /> the rewrite works but it adds /Library/WebServer/Documents to the URL.
I also tried putting the rewrite rules in <IfModule mod_rewrite.c> but that did not work either.
mod_rewrite is enabled and running on the server.
I will post the rewrite rules again in the code brackets. Sorry for the long post. - If some one can try them out on their Leopard Server to see if they can get them to work, it would be much appreciated. Again, these work on my Leopard Client but I can't get them to work on Server.
-- The httpd.conf file posted above is just the default conf file found in /private/etc/apache2/
<code>
RewriteEngine On
Options +FollowSymLinks
RewriteRule ^(.+)/$ http://%{HTTP_HOST}$1 [R=301, L]
RewriteCond %{THE_REQUEST} ^GET\ ([^\?]+)\.php(.*)\ HTTP
RewriteRule (.+)\.php(.*)$ $1$2 [R, L]]
RewriteCond %{THE_REQUEST} ^GET\ ([^\?]+)\.asp(.*)\ HTTP
RewriteRule (.+)\.asp(.*)$ $1$2 [R, L]]
RewriteCond %{THE_REQUEST} ^GET\ ([^\?]+)\.aspx(.*)\ HTTP
RewriteRule (.+)\.aspx(.*)$ $1$2 [R, L]]
RewriteCond %{THE_REQUEST} ^GET\ ([^\?]+)\.htm.(.)\ HTTP
RewriteRule (.+)\.htm.(.)$ $1$2 [R, L]]
RewriteCond %{THE_REQUEST} ^GET\ ([^\?]+)\.cfm(.*)\ HTTP
RewriteRule (.+)\.cfm(.*)$ $1$2 [R, L]]
RewriteCond %{THE_REQUEST} ^GET\ ([^\?]+)\.bak(.*)\ HTTP
RewriteRule (.+)\.bak(.*)$ $1$2 [R, L]]
RewriteCond %{THE_REQUEST} ^GET\ ([^\?]+)\.inc(.*)\ HTTP
RewriteRule (.+)\.inc(.*)$ $1$2 [R, L]]
RewriteCond %{THE_REQUEST} ^GET\ ([^\?]+)\..(.)\ HTTP
RewriteRule (.+)\..(.)$ $1$2 [R, L]]
<code>

Similar Messages

  • Trying to create test project, and get NPE during server startup

    Hi
    I am trying to create simple test project using JSF RI (usually use myfaces), but I am getting a couple of NPE's during server startup.
    I am using :
    jetty (maven plugin)
    jsf 1.2_03
    facelets 1.1.12
    I am probably missing something simple, but I just can't figure it out.
    My web.xml:
    <?xml version = '1.0' encoding = 'ISO-8859-1'?>
    <web-app  xmlns="http://java.sun.com/xml/ns/j2ee"
              xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
              xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
              version="2.4">
         <context-param>
              <param-name>facelets.REFRESH_PERIOD</param-name>
              <param-value>2</param-value>
         </context-param>
         <context-param>
            <param-name>facelets.LIBRARIES</param-name>
            <param-value>
                /WEB-INF/tomahawk.taglib.xml
            </param-value>
        </context-param>
         <context-param>
              <param-name>facelets.DEVELOPMENT</param-name>
              <param-value>true</param-value>
         </context-param>
         <context-param>
             <param-name>javax.faces.STATE_SAVING_METHOD</param-name>
             <param-value>client</param-value>
             <!--param-value>server</param-value-->
           </context-param>
         <context-param>
              <param-name>javax.faces.DEFAULT_SUFFIX</param-name>
              <param-value>.xhtml</param-value>
         </context-param>
         <context-param>
              <param-name>javax.faces.CONFIG_FILES</param-name>
              <!-- /WEB-INF/faces-config.xml loaded by default -->
            <param-value>
                   /WEB-INF/faces-config.xml,/WEB-INF/faces-beans.xml,/WEB-INF/faces-nav.xml
              </param-value>
         </context-param>
         <!-- JSF 1.2 RI specifc -->
         <!-- Listener implementation to handle web application lifecycle events -->
         <listener>
              <listener-class>
                   com.sun.faces.application.WebappLifecycleListener
              </listener-class>
         </listener>
         <listener>
              <listener-class>
                   com.sun.faces.config.ConfigureListener
              </listener-class>
         </listener>
         <context-param>
              <description>
                Set this flag to true if you want the JavaServer Faces
                Reference Implementation to validate the XML in your
                faces-config.xml resources against the DTD.  Default
                value is false.
            </description>
              <param-name>com.sun.faces.validateXml</param-name>
            <param-value>false</param-value>
        </context-param>
        <context-param>
             <description>
                Set this flag to true if you want the JavaServer Faces
                Reference Implementation to verify that all of the application
                objects you have configured (components, converters,
                renderers, and validators) can be successfully created.
                Default value is false.
            </description>
            <param-name>com.sun.faces.verifyObjects</param-name>
            <param-value>true</param-value>
        </context-param>
         <!-- Faces Servlet -->
         <servlet>
              <servlet-name>faces</servlet-name>
              <servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
              <load-on-startup>1</load-on-startup>
         </servlet>
         <!-- Faces Servlet Mappings -->
         <servlet-mapping>
              <servlet-name>faces</servlet-name>
              <url-pattern>*.jsf</url-pattern>
         </servlet-mapping>
         <welcome-file-list>
              <welcome-file>index.html</welcome-file>
         </welcome-file-list>
    </web-app>My faces-config.xml :
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE faces-config PUBLIC "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN"
                                  "http://java.sun.com/dtd/web-facesconfig_1_1.dtd">
    <faces-config>
         <application>
               <!-- view-handler>
                    org.rcfaces.core.internal.facelets.FaceletViewHandler
             </view-handler-->
              <view-handler>com.sun.facelets.FaceletViewHandler</view-handler>
              <locale-config>
                   <default-locale>en</default-locale>
              </locale-config>
         </application>
    </faces-config>My Stack traces :
    INFO: Initializing Sun's JavaServer Faces implementation (1.2_03-b09-FCS) for context '/test'
    2007-01-23 15:41:57.351::WARN:  failed ContextHandler@964130{/test,file:/C:/code/tests/rcfacesTest/src/main/webapp/}
    java.lang.NullPointerException
            at com.sun.faces.application.ApplicationAssociate.getInstance(ApplicationAssociate.java:171)
            at com.sun.faces.application.WebappLifecycleListener.handleAttributeEvent(WebappLifecycleListener.java:221)
            at com.sun.faces.application.WebappLifecycleListener.attributeReplaced(WebappLifecycleListener.java:211)
            at org.mortbay.jetty.handler.ContextHandler$Context.setAttribute(ContextHandler.java:1317)
            at com.sun.faces.config.ConfigureListener$ApplicationMap.put(ConfigureListener.java:1885)
            at com.sun.faces.renderkit.RenderKitUtils.loadSunJsfJs(RenderKitUtils.java:1076)
            at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:468)
            at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:450)
            at org.mortbay.jetty.servlet.Context.startContext(Context.java:124)
            at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1136)
            at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:420)
            at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
            at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
            at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
            at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:120)
            at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
            at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
            at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
            at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:119)
            at org.mortbay.jetty.Server.doStart(Server.java:221)
            at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
            at org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:134)
            at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:327)
            at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:272)
            at org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:177)
            at org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:183)
            at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
            at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
            at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
            at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
            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.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
            at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
            at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
            at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
    2007-01-23 15:41:57.367::WARN:  failed ContextHandlerCollection@91b9b0
    java.lang.NullPointerException
            at com.sun.faces.application.ApplicationAssociate.getInstance(ApplicationAssociate.java:171)
            at com.sun.faces.application.WebappLifecycleListener.handleAttributeEvent(WebappLifecycleListener.java:221)
            at com.sun.faces.application.WebappLifecycleListener.attributeReplaced(WebappLifecycleListener.java:211)
            at org.mortbay.jetty.handler.ContextHandler$Context.setAttribute(ContextHandler.java:1317)
            at com.sun.faces.config.ConfigureListener$ApplicationMap.put(ConfigureListener.java:1885)
            at com.sun.faces.renderkit.RenderKitUtils.loadSunJsfJs(RenderKitUtils.java:1076)
            at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:468)
            at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:450)
            at org.mortbay.jetty.servlet.Context.startContext(Context.java:124)
            at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1136)
            at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:420)
            at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
            at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
            at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
            at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:120)
            at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
            at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
            at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
            at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:119)
            at org.mortbay.jetty.Server.doStart(Server.java:221)
            at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
            at org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:134)
            at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:327)
            at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:272)
            at org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:177)
            at org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:183)
            at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
            at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
            at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
            at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
            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.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
            at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
            at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
            at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
    2007-01-23 15:41:57.367::WARN:  failed HandlerCollection@1360c93
    java.lang.NullPointerException
            at com.sun.faces.application.ApplicationAssociate.getInstance(ApplicationAssociate.java:171)
            at com.sun.faces.application.WebappLifecycleListener.handleAttributeEvent(WebappLifecycleListener.java:221)
            at com.sun.faces.application.WebappLifecycleListener.attributeReplaced(WebappLifecycleListener.java:211)
            at org.mortbay.jetty.handler.ContextHandler$Context.setAttribute(ContextHandler.java:1317)
            at com.sun.faces.config.ConfigureListener$ApplicationMap.put(ConfigureListener.java:1885)
            at com.sun.faces.renderkit.RenderKitUtils.loadSunJsfJs(RenderKitUtils.java:1076)
            at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:468)
            at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:450)
            at org.mortbay.jetty.servlet.Context.startContext(Context.java:124)
            at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1136)
            at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:420)
            at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
            at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
            at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
            at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:120)
            at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
            at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
            at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
            at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:119)
            at org.mortbay.jetty.Server.doStart(Server.java:221)
            at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
            at org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:134)
            at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:327)
            at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:272)
            at org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:177)
            at org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:183)
            at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
            at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
            at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
            at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
            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.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
            at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
            at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
            at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
    2007-01-23 15:41:57.523::INFO:  Started SelectChannelConnector @ 0.0.0.0:8080
    2007-01-23 15:41:57.523::WARN:  failed Server@188f506
    java.lang.NullPointerException
            at com.sun.faces.application.ApplicationAssociate.getInstance(ApplicationAssociate.java:171)
            at com.sun.faces.application.WebappLifecycleListener.handleAttributeEvent(WebappLifecycleListener.java:221)
            at com.sun.faces.application.WebappLifecycleListener.attributeReplaced(WebappLifecycleListener.java:211)
            at org.mortbay.jetty.handler.ContextHandler$Context.setAttribute(ContextHandler.java:1317)
            at com.sun.faces.config.ConfigureListener$ApplicationMap.put(ConfigureListener.java:1885)
            at com.sun.faces.renderkit.RenderKitUtils.loadSunJsfJs(RenderKitUtils.java:1076)
            at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:468)
            at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:450)
            at org.mortbay.jetty.servlet.Context.startContext(Context.java:124)
            at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1136)
            at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:420)
            at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
            at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
            at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
            at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:120)
            at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
            at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
            at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
            at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:119)
            at org.mortbay.jetty.Server.doStart(Server.java:221)
            at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
            at org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:134)
            at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:327)
            at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:272)
            at org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:177)
            at org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:183)
            at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
            at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
            at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
            at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
            at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
            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.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
            at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
            at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
            at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
    [INFO] Jetty server exiting.Thanks,
    Mike

    This has been fixed in the RI head. Hopefully we'll be able to get a 1.2_04 out shortly.
    Please download a nightly from the RI project site and give that a shot.

  • [svn:fx-trunk] 12883: Remove the skin classes from the halo theme project to avoid redundancy with the airframework /framework swcs.

    Revision: 12883
    Revision: 12883
    Author:   [email protected]
    Date:     2009-12-12 15:53:50 -0800 (Sat, 12 Dec 2009)
    Log Message:
    Remove the skin classes from the halo theme project to avoid redundancy with the airframework/framework swcs.
    QE notes: No
    Doc notes: No
    Bugs: SDK-24293
    Reviewer: Glenn
    Tests run: Checkintests, smattering of Halo and AIR mustella tests
    Is noteworthy for integration: Yes
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-24293
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/framework/src/FrameworkClasses.as
        flex/sdk/trunk/frameworks/projects/halo/build.xml
    Added Paths:
        flex/sdk/trunk/frameworks/projects/framework/src/mx/skins/halo/WindowBackground.as
    Removed Paths:
        flex/sdk/trunk/frameworks/projects/halo/assets/
        flex/sdk/trunk/frameworks/projects/halo/src/HaloClasses.as
        flex/sdk/trunk/frameworks/projects/halo/src/mx/skins/

  • [svn:bz-trunk] 20587: update the echoService destination name to qa.axis. EchoService to avoid a name conflict in ria package.

    Revision: 20587
    Revision: 20587
    Author:   [email protected]
    Date:     2011-03-03 14:11:37 -0800 (Thu, 03 Mar 2011)
    Log Message:
    update the echoService destination name to qa.axis.EchoService to avoid a name conflict in ria package.
    Modified Paths:
        blazeds/trunk/qa/apps/qa-regress/WEB-INF/flex/proxy-config.mods.xml
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/dataTypesTest/p roxy-config.xml

  • [svn:bz-trunk] 21661: Avoid calling throwNotSubscribedException() from inside synchronized blocks to prevent potential issues acquiring the lock .

    Revision: 21661
    Revision: 21661
    Author:   [email protected]
    Date:     2011-07-21 06:21:07 -0700 (Thu, 21 Jul 2011)
    Log Message:
    Avoid calling throwNotSubscribedException() from inside synchronized blocks to prevent potential issues acquiring the lock.
    Checkin-Tests: Pass
    QA: Yes
    Doc: No
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/client/FlexClient.java

  • [svn:fx-trunk] 11314: add the empty properties file to svn to fix the build .properties

    Revision: 11314
    Author:   [email protected]
    Date:     2009-10-30 10:38:34 -0700 (Fri, 30 Oct 2009)
    Log Message:
    add the empty properties file to svn to fix the build.properties
    QE notes: 
    Doc notes:
    Bugs: fix the build
    Reviewer: Pete
    Tests run: checkintests
    Is noteworthy for integration: no
    Added Paths:
        flex/sdk/trunk/frameworks/projects/playerglobal/bundles/de_DE/empty.properties
        flex/sdk/trunk/frameworks/projects/playerglobal/bundles/fr_FR/empty.properties
        flex/sdk/trunk/frameworks/projects/playerglobal/bundles/ja_JP/empty.properties
        flex/sdk/trunk/frameworks/projects/playerglobal/bundles/ru_RU/empty.properties
        flex/sdk/trunk/frameworks/projects/playerglobal/bundles/zh_CN/empty.properties

    Thats good news.

  • [svn:bz-trunk] 18694: Checkin the JUnit test that was left behind in the previous check-in.

    Revision: 18694
    Revision: 18694
    Author:   [email protected]
    Date:     2010-11-18 04:45:52 -0800 (Thu, 18 Nov 2010)
    Log Message:
    Checkin the JUnit test that was left behind in the previous check-in.
    Modified Paths:
        blazeds/trunk/modules/core/test/src/flex/messaging/io/amfx/DeserializationConfirmation.ja va

    Noise on line problem now solved, here are my new stats - not really a great improvement over what I was getting intermittently, but at least now it seems pretty constant. Do you think this will improve over time or is there anything else that can be done to make things faster?
    ADSL line status
    Connection information
    Line state
    Connected
    Connection time
    2 days, 21:09:44
    Downstream
    1,344 Kbps
    Upstream
    448 Kbps
    ADSL settings
    VPI/VCI
    0/38
    Type
    PPPoA
    Modulation
    ITU-T G.992.1
    Latency type
    Interleaved
    Noise margin (Down/Up)
    15.1 dB / 14.0 dB
    Line attenuation (Down/Up)
    62.0 dB / 31.5 dB
    Output power (Down/Up)
    16.4 dBm / 12.3 dBm
    Loss of Framing (Local)
    0
    Loss of Signal (Local)
    0
    Loss of Power (Local)
    0
    FEC Errors (Down/Up)
    9383 / 504
    CRC Errors (Down/Up)
    180 / N/A
    HEC Errors (Down/Up)
    N/A / 284
    Error Seconds (Local)
    110
    BT wholesale perfomance test is giving me the following:-
    Download  Speed
    0.9 Mbps
    0 Mbps
    1 Mbps
    Max Achievable Speed
     Download speedachieved during the test was - 0.9 Mbps
     For your connection, the acceptable range of speeds is 0.2 Mbps-1 Mbps.
     Additional Information:
     Your DSL Connection Rate :1.34 Mbps(DOWN-STREAM), 0.45 Mbps(UP-STREAM)
     IP Profile for your line is - 1 Mbps

  • [svn:bz-trunk] 21327: Updated the sample destination config to show the new "none" value for cluster-message-routing

    Revision: 21327
    Revision: 21327
    Author:   [email protected]
    Date:     2011-06-02 08:51:22 -0700 (Thu, 02 Jun 2011)
    Log Message:
    Updated the sample destination config to show the new "none" value for cluster-message-routing
    Modified Paths:
        blazeds/trunk/resources/config/messaging-config.xml

    Thanks Carlo for your reply.
    I have read again the link and you are correct that in using the preferred command together with localhost under POTS dial-peer, I can now select which correct path to choose for my outbound calls. I'm just not very strong with dial-peer and translation rules at the moment.
    I will try this solution during the weekend and let you know. But it would have been better if there was a sample configuration for this option.

  • [svn:bz-trunk] 11030: Tweak the deserialization of ASObjects to treat an empty string for the type of an object as null .

    Revision: 11030
    Author:   [email protected]
    Date:     2009-10-20 11:35:02 -0700 (Tue, 20 Oct 2009)
    Log Message:
    Tweak the deserialization of ASObjects to treat an empty string for the type of an object as null. It appears that there is some logic in the LC remoting code that relies on a non-null class name to always exist. This change reverts to the old behavior of not allowing empty string as a value for the ASObject.namedType.
    This should fix bug 2448442 and its duplicates caused by the recent serialization changes.
    I don't think this is the perfect fix. Pending further investigation, a better fix would be either:
    a. If it's OK to assume that empty string should always mean null for the type of the ASObject, the code that enforces it should be in the setter/getter inside ASObject and not in the deserializer.
    b. ASObject doesn't guarantee that a named type exists or is valid. In that sense an empty string is as bad as some random characters that cannot be a valid class name in java, so depending on how disruptive it may be, the fix should be in any logic that uses ASObject.getType().
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/io/amf/AbstractAmfInput.java

    Hi Pavan,
    "In your payload there is no namespace prefix for the elements under PayloadHeader element."
    Yes, you are right - but this message is standard AQ Adapter Header message - it's not defined by me. I just used message which was automatically added to my project when I have defined AQ Adapter.
    "In your process is the default namespace is same as namespace value of tns ??"
    Do you mean targetNamespace? If yes it's different as it points to process "targetNamespace="http://xmlns.oracle.com/PF_SOA_jws/PF_APPS/APPS_PROCESS" (names of application and process have changed as I try different ways to do that)
    ns1 is: xmlns:ns1="http://xmlns.oracle.com/pcbpel/adapter/aq/PF_SOA/PF_APPS/PO_AQ"
    "another thing is tns and ns1 should have same values.."
    When I create a variable of header type, namespace ns1 is automatically created for it. I set it as property of receive activity. When process is instantiated on the serwer I get the error in which you can see that namespace is tns.
    Maybe I'm doing something wrong but I don't see how I could fix this in my process.
    You can see that the message I get on the server has nothing in common with the application/project/process names. Is it possible to define such variable?
    Regards
    Pawel
    PS:
    In Transformation xsl file, both variables (source and target) has tns namespace for Header and PayloadHeader, and no namespace for subfields.
    Edited by: pawel.fidelus on 2010-01-05 02:37

  • [svn:fx-trunk] 9407: Reordering the if-statement in isMeasureFixed() exposed that hostFormat can be null when measure() is called if styles changed and measure is done before the next commitProperties .

    Revision: 9407
    Author:   [email protected]
    Date:     2009-08-19 15:11:34 -0700 (Wed, 19 Aug 2009)
    Log Message:
    Reordering the if-statement in isMeasureFixed() exposed that hostFormat can be null when measure() is called if styles changed and measure is done before the next commitProperties.  This states test exposed this.
    We should rethink if we want to clear hostFormat rather than have a hostFormatChanged flag.  If there is no hostFormat at measure then it has to be fixed because there is no line break format to check for auto-size.
    QE notes:
    Doc notes:
    Bugs: SDK-22779
    Reviewer: Gordon
    Tests run: checkintests
    Is noteworthy for integration: no
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-22779
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/RichEditableText.as

    Oh my god, it is too long! You definitely check out types, casting and especially ODP.Net (it does everything for you)... etc. They can help you to simplify your code. I do not have enough time to copy paste it to Studio and understand and solve your issue, so I got title of your message as your main question.
    In Oracle, you can create an autonumber field by using sequences object. This is really useful when you need to create a unique number to act as a primary key.
    Basically you can create a sequence simply typing;
    CREATE SEQUENCE MY_SEQUENCE;
    now you have a sequence called "MY_SEQUENCE"... Then, I advice you select a number from sequence;
    select MY_SEQUENCE.nextval from dual;
    I said I advice actually kinda must, although it called sequence, I cannot be sequential. Do not even try to predict the value. You can be sure that it is unique number so you can use it.
    Then insert you record and use that number part of your primary key. I think that's it. Have fun.

  • [svn:bz-trunk] 17772: Update the url in the tests to use a relative path instead of the default localhost : 8400 so that the tests can pass on appservers other than the default Tomcat .

    Revision: 17772
    Revision: 17772
    Author:   [email protected]
    Date:     2010-09-20 15:02:50 -0700 (Mon, 20 Sep 2010)
    Log Message:
    Update the url in the tests to use a relative path instead of the default localhost:8400 so that the tests can pass on appservers other than the default Tomcat.
    Modified Paths:
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationFalseTest/Remoting_NetConnectionTest.mxml
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationTrueTest/Remoting_NetConnectionTest.mxml

    Revision: 17772
    Revision: 17772
    Author:   [email protected]
    Date:     2010-09-20 15:02:50 -0700 (Mon, 20 Sep 2010)
    Log Message:
    Update the url in the tests to use a relative path instead of the default localhost:8400 so that the tests can pass on appservers other than the default Tomcat.
    Modified Paths:
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationFalseTest/Remoting_NetConnectionTest.mxml
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/EnforceEndpointValidation/Enforc eEndpointValidationTrueTest/Remoting_NetConnectionTest.mxml

  • [svn:bz-trunk] 15217: Bug: BLZ-508 - If server receives message for an unknown destination it shouldn ' t include the destination name in the error message sent back to the client .

    Revision: 15217
    Revision: 15217
    Author:   [email protected]
    Date:     2010-04-05 03:43:36 -0700 (Mon, 05 Apr 2010)
    Log Message:
    Bug: BLZ-508 - If server receives message for an unknown destination it shouldn't include the destination name in the error message sent back to the client.
    QA: Yes
    Doc: No
    Checkintests: Pass
    Details: Changed the error message to not include destination id. I'm also checking in a few minor fixes I had locally.
    Ticket Links:
        http://bugs.adobe.com/jira/browse/BLZ-508
    Modified Paths:
        blazeds/trunk/modules/common/src/flex/messaging/errors.properties
        blazeds/trunk/modules/core/src/flex/messaging/MessageBroker.java
        blazeds/trunk/modules/core/src/flex/messaging/cluster/JGroupsCluster.java

    Thanx Mete, yeah i did...
    but i solved it some other way... not entirely sure this was
    it though as i was doing a lot of things at once...
    it was fds.swc... possibly it was out of date or missing.

  • [svn:fx-trunk] 16385: -removed the utilities package target since it' s not used any longer - at least what is contained in this target.

    Revision: 16385
    Revision: 16385
    Author:   [email protected]
    Date:     2010-06-01 13:32:35 -0700 (Tue, 01 Jun 2010)
    Log Message:
    -removed the utilities package target since it's not used any longer - at least what is contained in this target.  I believe this was a leftover from flex 2 days.
    -fix up the packaging targets to ensure they are being properly built.  I removed depends="temp-clean" and inserted antcall target="temp-clean" because a target gets executed only once, even when more than one target depends on it. 
    QE notes:
    Doc notes: no
    Bugs: no
    Reviewer: Guarav
    Tests run: no
    Is noteworthy for integration: no
    Modified Paths:
        flex/sdk/trunk/build.xml

    http://blogs.adobe.com/jkost/2014/06/installing-the-2014-release-of-creative-cloud.html
    -This messages says (at least some) CC 2014 programs use NEW plugins https://forums.adobe.com/thread/1499663
    -so do not uninstall the older CC programs if you use plugins in your programs until you are sure you have plugins that work in CC2014
    If you are sure you don't need the old CC programs
    -http://helpx.adobe.com/creative-cloud/help/install-apps.html to install or uninstall

  • [svn:bz-trunk] 22429: Adding the default fallback of serializer and deserializer classes to amf deserializer and amf serializer

    Revision: 22429
    Revision: 22429
    Author:   [email protected]
    Date:     2011-09-07 08:04:46 -0700 (Wed, 07 Sep 2011)
    Log Message:
    Adding the default fallback of serializer and deserializer classes to amf deserializer and amf serializer
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/io/SerializationContext.java

  • [svn:fx-trunk] 10602: -include the flex-sdk-description in the mpl package

    Revision: 10602
    Author:   [email protected]
    Date:     2009-09-25 14:27:02 -0700 (Fri, 25 Sep 2009)
    Log Message:
    -include the flex-sdk-description in the mpl package
    bug: sdk-22539
    -fix up the build.xml that we include in the packaged sdk.  This has no bearing on building the sdk, but only when someone wants to rebuild the swcs from within a packaged sdk.
    bug:sdk-23302
    Ticket Links:
        http://bugs.adobe.com/jira/browse/sdk-22539
        http://bugs.adobe.com/jira/browse/sdk-23302
    Modified Paths:
        flex/sdk/trunk/build.xml
        flex/sdk/trunk/frameworks/build_framework.xml

Maybe you are looking for

  • What is the best way to set up one family imac with multiple iphones?

    We basically have one imac that we all use (one user account). We also have our own iphones with our own apple id. What i would like to get my head around is setting up each iphone individually to use itunes.(i.e music, videos, contacts). It seems th

  • How do I export existing Siebel employees to my LDAP directory?

    All; I have a fully-functional Siebel implementation using an LDAP directory server; I can create new employees, and they are migrated to the LDAP server without any problem. Unfortunately, I'm using a pre-populated Siebel database with roughly 250 e

  • Change Report Encoding

    Hello guys, i have a problem with a report and the encoding. We have to read a file with special characters like ñ or º. The system is a CRM unicode, we tried with ENCODING DEFAULT and also with IGNORING CONVERSION ERRORS, but after to read we have t

  • Rentals Tab for 12.0.1.26 version

    Hi just upgraded to 12.0.1.26 and have also rented my first movie. Can anyone tell me where the Rentals tab is that other forum talk about....totally new to this so it is bound to be me. Any help appreciated. Thanks

  • SQL Server services accounts using Managed Service Accounts

    Hi guys, Need your feedback on something, is it wiser to use Managed Service Accounts or normal domain accounts to run SQL Server services? MSA's only work in a single computer, so for every environment I would need to create a new set of sql service