Revised - Deployment server problem   HELP!!

Hi,Pls. tell me how to implement failover support using deployment services:I have following s/w:1) One Analytic Server & Admin Console & Spreadsheet services.2) Deployment Server( Without LIcense Key) & console.3) I have made connection pool & assigned a cluster to it.4)Cluster consist of two copies of sample/basic application.4)Admin Console is able to connect to deploymentserver.5)Deployment Server is able to connect to Analytic Database. 6)Which clients can I use to connect to Deployment Server. & how(Spreadsheets etc.)Any kind of help is most welcomed.Thanks a lot.Ravinder

First, are you using the 'classic' Excel addin or Essbase Spreadsheet Services? The classic Excel addin is not 'Essbase Deployment Services' aware.Tim TowApplied OLAP, Inc

Similar Messages

  • APP Server Problem - HELP!!!!

    I've read all the previous postings and can't resolve this after a week of re-installs, deleting files, PATH, Environment Variable changes, etc. Can someone please provide definitive advice on this? I'm installing on XP for now. Server Log File is as follows:
    Thanks,
    Jeremy
    [#|2007-03-18T11:31:37.703-0400|WARNING|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop.  Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components.  |#]
    [#|2007-03-18T11:31:37.718-0400|INFO|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|
    C:/Sun/java\bin\java
    -client
    -XX:PermSize=32m
    -XX:MaxPermSize=128m
    -XX:+CMSPermGenSweepingEnabled
    -XX:+CMSClassUnloadingEnabled
    -Xmx512m
    -XX:NewRatio=2
    -Dcom.sun.aas.defaultLogFile=C:/Sun/SunAppServer8/domains/creator/logs/server.log
    -Djava.endorsed.dirs=C:/Sun/SunAppServer8/lib/endorsed
    -Djava.security.policy=C:/Sun/SunAppServer8/domains/creator/config/server.policy
    -Djava.security.auth.login.config=C:/Sun/SunAppServer8/domains/creator/config/login.conf
    -Dsun.rmi.dgc.server.gcInterval=3600000
    -Dsun.rmi.dgc.client.gcInterval=3600000
    -Djavax.net.ssl.keyStore=C:/Sun/SunAppServer8/domains/creator/config/keystore.jks
    -Djavax.net.ssl.trustStore=C:/Sun/SunAppServer8/domains/creator/config/cacerts.jks
    -Djava.ext.dirs=C:/Sun/java/jre/lib/ext;C:/Sun/SunAppServer8/domains/creator/lib/ext;C:/Sun/SunAppServer8/derby/lib
    -Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
    -Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
    -Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
    -Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
    -Dcom.sun.enterprise.taglisteners=jsf-impl.jar
    -Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
    -Dcom.sun.aas.configName=server-config
    -Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
    -Ddomain.name=creator
    -Djmx.invoke.getters=true
    -Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
    -Dcom.sun.aas.promptForIdentity=true
    -Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
    -Dcom.sun.aas.instanceRoot=C:/Sun/SunAppServer8/domains/creator
    -Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
    -Dcom.sun.aas.domainName=creator
    -Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
    -Dproduct.name=Sun-Java-System/Application-Server
    -Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
    -Dcom.sun.aas.configRoot=C:/Sun/SunAppServer8/config
    -Djava.library.path=C:\Sun\java\jre\bin\client;C:\Sun\SunAppServer8\lib;C:\Sun\SunAppServer8\lib;C:\Sun\java\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\SunAppServer8\lib;C:\Sun\SunAppServer8\bin;C:\Sun\SunAppServer8\lib;C:\Sun\SunAppServer8\bin;C:\Sun\SunAppServer8\bin;C:\Sun\SunAppServer8\bin;C:\oraclexe\app\oracle\product\10.2.0\server\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\Common Files\Roxio Shared\DLLShared\;C:\Program Files\QuickTime\QTSystem\
    -Dcom.sun.aas.instanceName=server
    -Dcom.sun.aas.processLauncher=SE
    -cp
    C:/Sun/java/lib/tools.jar;C:/Sun/SunAppServer8/lib/appserv-rt.jar;C:/Sun/SunAppServer8/lib\activation.jar;C:/Sun/SunAppServer8/lib\admin-cli.jar;C:/Sun/SunAppServer8/lib\appserv-admin.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_es.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_fr.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_ja.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_ko.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_zh.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_zh_CN.jar;C:/Sun/SunAppServer8/lib\appserv-cmp.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_es.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_fr.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_ja.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_ko.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_zh.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_zh_CN.jar;C:/Sun/SunAppServer8/lib\appserv-env.jar;C:/Sun/SunAppServer8/lib\appserv-ext.jar;C:/Sun/SunAppServer8/lib\appserv-jstl.jar;C:/Sun/SunAppServer8/lib\appserv-rt_es.jar;C:/Sun/SunAppServer8/lib\appserv-rt_fr.jar;C:/Sun/SunAppServer8/lib\appserv-rt_ja.jar;C:/Sun/SunAppServer8/lib\appserv-rt_ko.jar;C:/Sun/SunAppServer8/lib\appserv-rt_zh.jar;C:/Sun/SunAppServer8/lib\appserv-rt_zh_CN.jar;C:/Sun/SunAppServer8/lib\appserv-upgrade.jar;C:/Sun/SunAppServer8/lib\commons-launcher.jar;C:/Sun/SunAppServer8/lib\commons-launcher_es.jar;C:/Sun/SunAppServer8/lib\commons-launcher_fr.jar;C:/Sun/SunAppServer8/lib\commons-launcher_ja.jar;C:/Sun/SunAppServer8/lib\commons-launcher_ko.jar;C:/Sun/SunAppServer8/lib\commons-launcher_zh.jar;C:/Sun/SunAppServer8/lib\commons-launcher_zh_CN.jar;C:/Sun/SunAppServer8/lib\commons-logging.jar;C:/Sun/SunAppServer8/lib\deployhelp_es.jar;C:/Sun/SunAppServer8/lib\deployhelp_fr.jar;C:/Sun/SunAppServer8/lib\deployhelp_ja.jar;C:/Sun/SunAppServer8/lib\deployhelp_ko.jar;C:/Sun/SunAppServer8/lib\deployhelp_zh.jar;C:/Sun/SunAppServer8/lib\deployhelp_zh_CN.jar;C:/Sun/SunAppServer8/lib\dom.jar;C:/Sun/SunAppServer8/lib\driveradapter.jar;C:/Sun/SunAppServer8/lib\j2ee-svc.jar;C:/Sun/SunAppServer8/lib\j2ee.jar;C:/Sun/SunAppServer8/lib\j2ee_es.jar;C:/Sun/SunAppServer8/lib\j2ee_fr.jar;C:/Sun/SunAppServer8/lib\j2ee_ja.jar;C:/Sun/SunAppServer8/lib\j2ee_ko.jar;C:/Sun/SunAppServer8/lib\j2ee_zh.jar;C:/Sun/SunAppServer8/lib\j2ee_zh_CN.jar;C:/Sun/SunAppServer8/lib\jax-qname.jar;C:/Sun/SunAppServer8/lib\jaxr-api.jar;C:/Sun/SunAppServer8/lib\jaxr-impl.jar;C:/Sun/SunAppServer8/lib\jaxrpc-api.jar;C:/Sun/SunAppServer8/lib\jaxrpc-impl.jar;C:/Sun/SunAppServer8/lib\jdic_0_9.jar;C:/Sun/SunAppServer8/lib\jmxremote.jar;C:/Sun/SunAppServer8/lib\jmxremote_optional.jar;C:/Sun/SunAppServer8/lib\jsf-api.jar;C:/Sun/SunAppServer8/lib\jsf-impl.jar;C:/Sun/SunAppServer8/lib\mail.jar;C:/Sun/SunAppServer8/lib\PEtray.jar;C:/Sun/SunAppServer8/lib\relaxngDatatype.jar;C:/Sun/SunAppServer8/lib\rmissl.jar;C:/Sun/SunAppServer8/lib\saaj-api.jar;C:/Sun/SunAppServer8/lib\saaj-impl.jar;C:/Sun/SunAppServer8/lib\smbase.jar;C:/Sun/SunAppServer8/lib\smdb2.jar;C:/Sun/SunAppServer8/lib\sminformix.jar;C:/Sun/SunAppServer8/lib\smoracle.jar;C:/Sun/SunAppServer8/lib\smresource.jar;C:/Sun/SunAppServer8/lib\smspy.jar;C:/Sun/SunAppServer8/lib\smsqlserver.jar;C:/Sun/SunAppServer8/lib\smsybase.jar;C:/Sun/SunAppServer8/lib\smutil.jar;C:/Sun/SunAppServer8/lib\xalan.jar;C:/Sun/SunAppServer8/lib\xercesImpl.jar;C:/Sun/SunAppServer8/lib\xsdlib.jar;C:/Sun/SunAppServer8/lib/install/applications/jmsra/imqjmsra.jar;C:/Sun/SunAppServer8/imq/lib/jaxm-api.jar;C:/Sun/SunAppServer8/imq/lib/fscontext.jar;C:/Sun/SunAppServer8/lib/ant/lib/ant.jar
    com.sun.rave.tray.RavePEMain
    start
    display
    native|#]
    [#|2007-03-18T11:31:46.921-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [C:\Sun\SunAppServer8\imq\bin].|#]
    [#|2007-03-18T11:31:46.937-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5098: AS Socket Service Initialization has been completed.|#]
    [#|2007-03-18T11:31:47.531-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0046:The Platform MBeanServer is available. It will be used to register Application Server MBeans. Platform MBeans will also be available for browsing while using standard JMX Console.|#]
    [#|2007-03-18T11:31:47.546-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
    [#|2007-03-18T11:31:47.812-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
    [#|2007-03-18T11:31:48.296-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server server|#]
    [#|2007-03-18T11:31:48.296-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server __asadmin|#]
    [#|2007-03-18T11:31:48.984-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.corba.ee.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: 127.0.0.1/24700"|#]
    [#|2007-03-18T11:31:49.281-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.corba.ee.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: 127.0.0.1/22060"|#]
    [#|2007-03-18T11:31:49.281-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.corba.ee.S1AS-ORB.rpc.transport|_ThreadID=10;|"IOP00710299: (INTERNAL) Successfully created IIOP listener on the specified host/port: 127.0.0.1/22061"|#]
    [#|2007-03-18T11:31:50.015-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [24700]|#]
    [#|2007-03-18T11:31:53.203-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1079: Initialization of AMX MBeans successful|#]
    [#|2007-03-18T11:31:53.515-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Selecting file C:\Sun\SunAppServer8\lib\install\applications\MEjbApp.ear for autodeployment.|#]
    [#|2007-03-18T11:31:55.718-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [MEjbApp]|#]
    [#|2007-03-18T11:31:55.734-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans ...|#]
    [#|2007-03-18T11:31:55.781-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [MEjbApp]|#]
    [#|2007-03-18T11:31:56.000-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 1688 msec, Total EJB Compiler Module Time: 63 msec, Portion spent EJB Compiling: 3%
    Breakdown of EJBC Module Time: Total Time for EJBC: 63 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 47 msec (74%),
    |#]
    [#|2007-03-18T11:31:56.093-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = MEjbApp|#]
    [#|2007-03-18T11:31:56.203-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- reference-added MEjbApp]|#]
    [#|2007-03-18T11:31:56.281-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
    [#|2007-03-18T11:31:56.296-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy MEjbApp]|#]
    [#|2007-03-18T11:31:56.437-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: MEJBBean; containerId: 76954462832623616|#]
    [#|2007-03-18T11:31:56.562-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
    [#|2007-03-18T11:31:56.562-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
    [#|2007-03-18T11:31:56.562-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : C:\Sun\SunAppServer8\lib\install\applications\MEjbApp.ear.|#]
    [#|2007-03-18T11:31:56.578-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Selecting file C:\Sun\SunAppServer8\lib\install\applications\__ejb_container_timer_app.ear for autodeployment.|#]
    [#|2007-03-18T11:31:56.875-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC - START of EJBC for [__ejb_container_timer_app]|#]
    [#|2007-03-18T11:31:59.890-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans ...|#]
    [#|2007-03-18T11:31:59.906-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC - END of EJBC for [__ejb_container_timer_app]|#]
    [#|2007-03-18T11:32:00.046-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 3468 msec, Total EJB Compiler Module Time: 3031 msec, Portion spent EJB Compiling: 87%
    Breakdown of EJBC Module Time: Total Time for EJBC: 3031 msec, CMP Generation: 594 msec (19%), Java Compilation: 2359 msec (77%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 16 msec (0%),
    |#]
    [#|2007-03-18T11:32:00.109-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = __ejb_container_timer_app|#]
    [#|2007-03-18T11:32:00.156-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- reference-added __ejb_container_timer_app]|#]
    [#|2007-03-18T11:32:00.187-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
    [#|2007-03-18T11:32:00.203-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent -- deploy __ejb_container_timer_app]|#]
    [#|2007-03-18T11:32:00.343-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: TimerBean; containerId: 76954463102959616|#]
    [#|2007-03-18T11:32:00.656-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
    [#|2007-03-18T11:32:00.656-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
    [#|2007-03-18T11:32:00.656-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]
    [#|2007-03-18T11:32:00.656-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : C:\Sun\SunAppServer8\lib\install\applications\__ejb_container_timer_app.ear.|#]
    [#|2007-03-18T11:32:00.656-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Sun-Java-System/Application-Server.|#]
    [#|2007-03-18T11:32:00.718-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [__default-admingui] in virtual server [__asadmin] at []|#]
    [#|2007-03-18T11:32:00.796-0400|WARNING|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
    [#|2007-03-18T11:32:00.890-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [__asadmin] at [web1]|#]
    [#|2007-03-18T11:32:00.906-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [__asadmin] at [asadmin]|#]
    [#|2007-03-18T11:32:00.921-0400|WARNING|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0500: default-locale attribute of locale-charset-info element has been deprecated and is being ignored. Use default-charset attribute of parameter-encoding element instead|#]
    [#|2007-03-18T11:32:00.953-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [com_sun_web_ui] in virtual server [__asadmin] at [com_sun_web_ui]|#]
    [#|2007-03-18T11:32:01.062-0400|INFO|sun-appserver-pe8.2|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server|#]
    [#|2007-03-18T11:32:02.656-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Non-Blocking Mode|#]
    [#|2007-03-18T11:32:02.656-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 29080|#]
    [#|2007-03-18T11:32:02.671-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 29080|#]
    [#|2007-03-18T11:32:02.734-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Blocking Mode|#]
    [#|2007-03-18T11:32:02.734-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 22043|#]
    [#|2007-03-18T11:32:02.734-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 22043|#]
    [#|2007-03-18T11:32:02.781-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Non-Blocking Mode|#]
    [#|2007-03-18T11:32:02.781-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0703: Initializing Sun-Java-System/Application-Server-PE HTTP/1.1 on 25848|#]
    [#|2007-03-18T11:32:02.781-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0712: Starting Sun-Java-System/Application-Server-PE HTTP/1.1 on 25848|#]
    [#|2007-03-18T11:33:02.968-0400|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Service com.sun.enterprise.admin.server.core.JmxConnectorLifecycle@1a428d5 cannot be started! : com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://192.168.61.2:29686/management/rmi-jmx-connector]: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
         java.net.SocketTimeoutException: Read timed out]|#]
    [#|2007-03-18T11:33:02.968-0400|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5071: An error occured during initialization
    com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://192.168.61.2:29686/management/rmi-jmx-connector]: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
         java.net.SocketTimeoutException: Read timed out]
         at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onStartup(JmxConnectorLifecycle.java:104)
         at com.sun.enterprise.server.ApplicationServer.onStartup(ApplicationServer.java:300)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:294)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
         at com.sun.rave.tray.RavePEMain.main(RavePEMain.java:37)
    Caused by: java.io.IOException: Cannot bind to URL [rmi://192.168.61.2:29686/management/rmi-jmx-connector]: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
         java.net.SocketTimeoutException: Read timed out]
         at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:814)
         at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:431)
         at com.sun.enterprise.admin.jmx.remote.server.JmxConnectorServerDriver.startConnectorServer(JmxConnectorServerDriver.java:177)
         at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onStartup(JmxConnectorLifecycle.java:95)
         ... 4 more
    Caused by: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
         java.net.SocketTimeoutException: Read timed out]
         at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:122)
         at com.sun.jndi.toolkit.url.GenericURLContext.bind(GenericURLContext.java:208)
         at javax.naming.InitialContext.bind(InitialContext.java:359)
         at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:635)
         at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:427)
         ... 6 more
    Caused by: java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
         java.net.SocketTimeoutException: Read timed out
         at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:274)
         at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:171)
         at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:306)
         at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
         at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:116)
         ... 10 more
    Caused by: java.net.SocketTimeoutException: Read timed out
         at com.sun.enterprise.server.ss.ASInputStream.waitForSelect(ASInputStream.java:123)
         at com.sun.enterprise.server.ss.ASInputStream.read(ASInputStream.java:81)
         at com.sun.enterprise.server.ss.ASInputStream.read(ASInputStream.java:73)
         at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
         at java.io.BufferedInputStream.read(BufferedInputStream.java:235)
         at java.io.DataInputStream.readByte(DataInputStream.java:241)
         at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:215)
         ... 14 more
    |#]
    [#|2007-03-18T11:33:02.968-0400|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Server Startup failed. Exiting...|#]
    [#|2007-03-18T11:33:02.968-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Server shutdown in progress...|#]
    [#|2007-03-18T11:33:02.968-0400|WARNING|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5061: Exception :
    com.sun.appserv.server.ServerLifecycleException
         at com.sun.enterprise.admin.server.core.JmxConnectorLifecycle.onShutdown(JmxConnectorLifecycle.java:122)
         at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:414)
         at com.sun.enterprise.server.PEMain.run(PEMain.java:317)
         at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
         at com.sun.rave.tray.RavePEMain.main(RavePEMain.java:37)
    |#]
    [#|2007-03-18T11:33:02.968-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0303: Stopping Sun-Java-System/Application-Server.|#]
    [#|2007-03-18T11:33:02.968-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 29080|#]
    [#|2007-03-18T11:33:02.968-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 22043|#]
    [#|2007-03-18T11:33:02.968-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0713: Stopping Sun-Java-System/Application-Server-PE HTTP/1.1 on 25848|#]
    [#|2007-03-18T11:33:03.125-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5051: Shutting down all J2EE applications ...|#]
    [#|2007-03-18T11:33:03.140-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5122:EJB Timer Service shutdown at [2007/03/18 11:33:03]|#]
    [#|2007-03-18T11:33:03.140-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE 5060 :  Stopping all J2EE Connector 1.5 Compliant resource adapters ...|#]
    [#|2007-03-18T11:33:03.140-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7094: __xa shutdown successfully.|#]
    [#|2007-03-18T11:33:03.140-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE 5061 : Resource adapters Stop() Complete|#]
    [#|2007-03-18T11:33:03.140-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5052: Application shutdown complete.|#]
    [#|2007-03-18T11:33:03.656-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5025: JMS service shutting down.|#]
    [#|2007-03-18T11:33:03.890-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5026: JMS service shutdown complete.|#]
    [#|2007-03-18T11:33:03.890-0400|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Server stopped due to Server startup failure.|#]
    [#|2007-03-18T11:38:11.046-0400|WARNING|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|LAUNCHER005:Spaces in your PATH have been detected. The PATH must be consistently formated (e.g. C:\Program Files\Java\jdk1.5.0\bin; ) or the Appserver may not be able to start and/or stop.  Mixed quoted spaces in your PATH can cause problems, so the launcher will remove all double quotes before invoking the process. The most reliable solution would be to remove all spaces from your path before starting the Appservers components.  |#]
    [#|2007-03-18T11:38:11.046-0400|INFO|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|
    C:/Sun/java\bin\java
    -client
    -XX:PermSize=32m
    -XX:MaxPermSize=128m
    -XX:+CMSPermGenSweepingEnabled
    -XX:+CMSClassUnloadingEnabled
    -Xmx512m
    -XX:NewRatio=2
    -Dcom.sun.aas.defaultLogFile=C:/Sun/SunAppServer8/domains/creator/logs/server.log
    -Djava.endorsed.dirs=C:/Sun/SunAppServer8/lib/endorsed
    -Djava.security.policy=C:/Sun/SunAppServer8/domains/creator/config/server.policy
    -Djava.security.auth.login.config=C:/Sun/SunAppServer8/domains/creator/config/login.conf
    -Dsun.rmi.dgc.server.gcInterval=3600000
    -Dsun.rmi.dgc.client.gcInterval=3600000
    -Djavax.net.ssl.keyStore=C:/Sun/SunAppServer8/domains/creator/config/keystore.jks
    -Djavax.net.ssl.trustStore=C:/Sun/SunAppServer8/domains/creator/config/cacerts.jks
    -Djava.ext.dirs=C:/Sun/java/jre/lib/ext;C:/Sun/SunAppServer8/domains/creator/lib/ext;C:/Sun/SunAppServer8/derby/lib
    -Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
    -Djavax.management.builder.initial=com.sun.enterprise.admin.server.core.jmx.AppServerMBeanServerBuilder
    -Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
    -Dcom.sun.enterprise.taglibs=appserv-jstl.jar,jsf-impl.jar
    -Dcom.sun.enterprise.taglisteners=jsf-impl.jar
    -Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
    -Dcom.sun.aas.configName=server-config
    -Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
    -Ddomain.name=creator
    -Djmx.invoke.getters=true
    -Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
    -Dcom.sun.aas.promptForIdentity=true
    -Dorg.xml.sax.driver=com.sun.org.apache.xerces.internal.parsers.SAXParser
    -Dcom.sun.aas.instanceRoot=C:/Sun/SunAppServer8/domains/creator
    -Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
    -Dcom.sun.aas.domainName=creator
    -Djava.util.logging.manager=com.sun.enterprise.server.logging.ServerLogManager
    -Dproduct.name=Sun-Java-System/Application-Server
    -Dcom.sun.enterprise.overrideablejavaxpackages=javax.faces,javax.servlet.jsp.jstl,javax.xml.bind,javax.help
    -Dcom.sun.aas.configRoot=C:/Sun/SunAppServer8/config
    -Djava.library.path=C:\Sun\java\jre\bin\client;C:\Sun\SunAppServer8\lib;C:\Sun\SunAppServer8\lib;C:\Sun\java\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\Sun\SunAppServer8\lib;C:\Sun\SunAppServer8\bin;C:\Sun\SunAppServer8\lib;C:\Sun\SunAppServer8\bin;C:\Sun\SunAppServer8\bin;C:\Sun\SunAppServer8\bin;C:\oraclexe\app\oracle\product\10.2.0\server\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\Common Files\Roxio Shared\DLLShared\;C:\Program Files\QuickTime\QTSystem\
    -Dcom.sun.aas.instanceName=server
    -Dcom.sun.aas.processLauncher=SE
    -cp
    C:/Sun/java/lib/tools.jar;C:/Sun/SunAppServer8/lib/appserv-rt.jar;C:/Sun/SunAppServer8/lib\activation.jar;C:/Sun/SunAppServer8/lib\admin-cli.jar;C:/Sun/SunAppServer8/lib\appserv-admin.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_es.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_fr.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_ja.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_ko.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_zh.jar;C:/Sun/SunAppServer8/lib\appserv-assemblytool_zh_CN.jar;C:/Sun/SunAppServer8/lib\appserv-cmp.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_es.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_fr.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_ja.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_ko.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_zh.jar;C:/Sun/SunAppServer8/lib\appserv-cmp_zh_CN.jar;C:/Sun/SunAppServer8/lib\appserv-env.jar;C:/Sun/SunAppServer8/lib\appserv-ext.jar;C:/Sun/SunAppServer8/lib\appserv-jstl.jar;C:/Sun/SunAppServer8/lib\appserv-rt_es.jar;C:/Sun/SunAppServer8/lib\appserv-rt_fr.jar;C:/Sun/SunAppServer8/lib\appserv-rt_ja.jar;C:/Sun/SunAppServer8/lib\appserv-rt_ko.jar;C:/Sun/SunAppServer8/lib\appserv-rt_zh.jar;C:/Sun/SunAppServer8/lib\appserv-rt_zh_CN.jar;C:/Sun/SunAppServer8/lib\appserv-upgrade.jar;C:/Sun/SunAppServer8/lib\commons-launcher.jar;C:/Sun/SunAppServer8/lib\commons-launcher_es.jar;C:/Sun/Sun

    Hi,
    Seems you are having socket time out exception. I use to get the same while deploying on XP with (640MB RAM) but able to re-run after freeing some memory. Creator needs optimally atleast 1GB RAM. You have not mentioned your machine RAM...
    It might just help..
    dr.am mohan rao

  • Strange HTTP/Web Server Problem - HELP ~~~~~~~

    HI all,
    I would like to seek help from you - the apple expert!
    I received my mac mini server and immediate want to setup a web/http server. I encountered one very strange problem that only the mac mini server itself can access the http server page but not all other machines in the same internal network. I tried to troubleshoot and so simplify the setting as follow
    Here is my setting
    - The Web Server service is ON
    - I closed all the built in web services (wiki, cal, blogs, webmail) for troubleshoot
    - I created a "Custom Sites" with 192.168.11.9:8080 <- this is my mac mini ip
    - Ensured the /Library/WebServer/Sites/192.168.11.9 got right permission
    When i open IE in my window vista laptop, type in address "http://192.168.11.9:8080", it doesn't work. Is there anything i need to config so that other machine (Win OS) in the internal network can also access the http server in my mac mini?
    Thank you very much.
    A newbies in mini

    ...and in your do/while loop think what happens when read() does return -1. You still write the entire buffer. You should do something like this instead:
        while (true) {
            int count = in.read(buf);
            if (count == -1)
                break;
           out.write(buf, 0, count);
        }

  • Deployment server problem

    Hi,I have made a cluster of two applications(both copies of each other) , both of which reside on same analytic server. I have assigned this cluster to a connection pool. But when I access one application throuch excel addin client & make one application offline which I am accessing, deployment servers do not swith over to other application. Can some one pls. suggest me where I may have mistaken.Thanks a lot,Ravinder.

    First, are you using the 'classic' Excel addin or Essbase Spreadsheet Services? The classic Excel addin is not 'Essbase Deployment Services' aware.Tim TowApplied OLAP, Inc

  • I have a big problem :( why is it i cant update my ipod touch 2g into ios 4! im using the latest version of itunes and everytime i click "update" it stucks on the "contacting server" please help :( i want to update it now

    i have a big problem why is it i cant update my ipod touch 2g into ios 4! im using the latest version of itunes and everytime i click "update" it stucks on the "contacting server" please help i want to update it now

    Maybe here:
    iTunes for Windows: iTunes cannot contact the iPhone, iPad, or iPod software update server

  • Problem in starting deployment server

    Hello and hope all are fine,
    I know I have already started a thread for this issue, but as it is almost urgent for me I have to post another thread again:
    While trying to start my deployment server progress bar stops advancing and a message indicates that the server is started but could not be pinged.
    I hope somebuddy can help,
    Thank you so much.
    P.S. here is final section of my server.log file:
    #|2004-05-18T19:19:15.202+0430|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5035: Timed out after 60000 milliseconds while trying to verify if the JMS service startup succeeded.|#]
    [#|2004-05-18T19:19:15.202+0430|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5037: Check permissions of MQ instance directory D:\Program Files\Sun\Creator\SunAppServer8\imq\var\instances|#]
    [#|2004-05-18T19:19:15.202+0430|INFO|sun-appserver-pe8.0.0_01|javax.enterprise.resource.jms|_ThreadID=10;|JMS5036: More details may be available in the log file for the JMS service broker instance imqbroker. Please refer to the JMS provider documentation for the exact location of this log file.|#]
    [#|2004-05-18T19:19:15.202+0430|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|CORE5061: Exception :
    com.sun.appserv.server.ServerLifecycleException: [C4003]: Error occurred on connection creation [127.0.0.1:7676]. - cause: java.net.ConnectException: Connection refused: connect
    at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:415)
    at com.sun.enterprise.jms.JmsProviderLifecycle.onShutdown(JmsProviderLifecycle.java:433)
    at com.sun.enterprise.server.ApplicationServer.onShutdown(ApplicationServer.java:400)
    at com.sun.enterprise.server.PEMain.run(PEMain.java:233)
    at com.sun.enterprise.server.PEMain.main(PEMain.java:172)
    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:324)
    at org.apache.commons.launcher.ChildMain.run(ChildMain.java:269)
    Caused by: com.sun.messaging.jms.JMSException: [C4003]: Error occurred on connection creation [127.0.0.1:7676]. - cause: java.net.ConnectException: Connection refused: connect
    at com.sun.messaging.jmq.jmsclient.ExceptionHandler.getJMSConnectException(ExceptionHandler.java:233)
    at com.sun.messaging.jmq.jmsclient.ExceptionHandler.handleConnectException(ExceptionHandler.java:180)
    at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:172)
    at com.sun.messaging.jmq.jmsclient.PortMapperClient.init(PortMapperClient.java:97)
    at com.sun.messaging.jmq.jmsclient.PortMapperClient.<init>(PortMapperClient.java:50)
    at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPConnectionHandler.<init>(TCPConnectionHandler.java:53)
    at com.sun.messaging.jmq.jmsclient.protocol.tcp.TCPStreamHandler.openConnection(TCPStreamHandler.java:102)
    at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnectionOld(ConnectionInitiator.java:271)
    at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:107)
    at com.sun.messaging.jmq.jmsclient.ConnectionInitiator.createConnection(ConnectionInitiator.java:92)
    at com.sun.messaging.jmq.jmsclient.ProtocolHandler.init(ProtocolHandler.java:562)
    at com.sun.messaging.jmq.jmsclient.ProtocolHandler.<init>(ProtocolHandler.java:1102)
    at com.sun.messaging.jmq.jmsclient.ConnectionImpl.openConnection(ConnectionImpl.java:1741)
    at com.sun.messaging.jmq.jmsclient.ConnectionImpl.init(ConnectionImpl.java:588)
    at com.sun.messaging.jmq.jmsclient.ConnectionImpl.<init>(ConnectionImpl.java:274)
    at com.sun.messaging.jmq.jmsclient.UnifiedConnectionImpl.<init>(UnifiedConnectionImpl.java:33)
    at com.sun.messaging.jmq.jmsclient.QueueConnectionImpl.<init>(QueueConnectionImpl.java:32)
    at com.sun.messaging.ConnectionFactory.createQueueConnection(ConnectionFactory.java:72)
    at com.sun.messaging.jmq.admin.jmsspi.JMSAdminImpl.pingProvider(JMSAdminImpl.java:734)
    at com.sun.enterprise.jms.JmsProviderLifecycle.waitForJmsProvider(JmsProviderLifecycle.java:324)
    at com.sun.enterprise.jms.JmsProviderLifecycle.checkProviderStartup(JmsProviderLifecycle.java:384)
    ... 9 more
    Caused by: java.net.ConnectException: Connection refused: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305)
    at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158)
    at java.net.Socket.connect(Socket.java:452)
    at java.net.Socket.connect(Socket.java:402)
    at java.net.Socket.<init>(Socket.java:309)
    at java.net.Socket.<init>(Socket.java:124)
    at com.sun.messaging.jmq.jmsclient.PortMapperClient.readBrokerPorts(PortMapperClient.java:152)
    ... 27 more
    |#]
    [#|2004-05-18T19:19:15.233+0430|WARNING|sun-appserver-pe8.0.0_01|javax.enterprise.system.tools.admin|_ThreadID=10;|core.tmp_folder_deletion_failed|#]
    [#|2004-05-18T19:19:15.233+0430|SEVERE|sun-appserver-pe8.0.0_01|javax.enterprise.system.core|_ThreadID=10;|Server stopped due to Server startup failure.|#]

    This looks like the JMS service was unable to start. Some times the system process occupies the port assigned to JMS and JMS tries to run on the same port.
    Try to shutdown the IDE and machine and then restart. Everything should work fine then.

  • Pls help me(sql server problem)

    Im using sql server 2000
    i had 2 database servers
    'srv1', 'srv2'
    in srv1 had 'db1' database
    first create a user called 'db1usr1' with read and write previlages only(not dbowner)
    then take backup of 'db1' as 'db1bakup'
    then u hav to restore the 'db1bakup' in srv2 as 'db2'
    then u have 2 login in the 'srv2' machine as 'db1usr1'
    here is the problem : it is(db1usr1) not logged in srv2 machine through query analyser

    You're asking about a sql server problem on an Oracle forum?
    Don't you think a sql server forum would be a more appropriate place for your question?

  • HELP -- Tim Tow, one more query. Deployment Server.

    Sir, I have made cluster on single analytic server also, by putting two copies of same app. on one analytic server in a cluster.(i.e. Only one analytic server is used to cluster 2 applications). Still failover support is not tested. For client, in my lab I used Deployment Server console to connect to deployment server,(i.e. application was taken offline using deployment console.Is it correct way to test failover support. I did not used spreadsheets.Pls. suggest where I have mistaken.Thank You,Ravinder.

    Still failover support is not tested.<<I would probably test it by:1. setting up a test with 2 Essbase Spreadsheet Services clients; write a simple macro that does 10000 retrieves in a loop.2. confirm that the both applications in the cluster are being used when the macros are running.3. go into app mgr (or eas) and take one of your apps in the cluster 'offline' (ex. uncheck 'Allow Commands' and 'Allow Connects').4. see if your macros continue to function vs the one database in the cluster still enabled.BTW, it has been years since I have done this; we had to do something like this when we earned the 'Platinum' Certification for our ActiveOLAP for Essbase product from Hyperion.Tim TowApplied OLAP, Inc

  • Deploy Java problem

    Dear All
    Please help me,I deployed Java but It is problem,I executed with "SAP Note Number: 1006640 Not active container webdynpro during deployment" but still problem
    Start updating EAR file...
    08/07/19 11:21:00 -  start-up mode is lazy
    08/07/19 11:21:00 -  EAR file updated successfully for 125ms.
    08/07/19 11:21:00 -  Start deploying ...
    08/07/19 11:21:00 -  EAR file uploaded to server for 94ms.
    08/07/19 11:21:01 -  ERROR: Not deployed. Deploy Service returned ERROR:
                         java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/bi_alv_common.ear.
                         Reason: None of the available containers recognized the components of application sap.com/bialvcommon; it is not possible to make deploy.
                              at com.sap.engine.services.deploy.server.DeployServiceImpl.deploy(DeployServiceImpl.java:572)
                              at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1555)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:319)
                              at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
                              at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
                              at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
                              at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
                              at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
                              at java.security.AccessController.doPrivileged(Native Method)
                              at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
                              at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
                         For detailed information see the log file of the Deploy Service.
    08/07/19 11:21:01 -  ***********************************************************
    Jul 19, 2008 11:21:01... Info: End of log messages of the target system.
    Jul 19, 2008 11:21:01... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
    Jul 19, 2008 11:21:01... Error: Aborted: development component 'bi/alv/common'/'sap.com'/'MAIN_APL70VAL_C'/'1077259'/'0', grouped by software component 'BI-WDALV'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.15.0.20080218054927''/'0':
    Caught exception during application deployment from SAP J2EE Engine's deploy service:
    java.rmi.RemoteException: Error occurred while deploying ear file ./temp/deploy/work/deploying/bi_alv_common.ear.
    Reason: None of the available containers recognized the components of application sap.com/bialvcommon; it is not possible to make deploy.
    (message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)
    Jul 19, 2008 11:21:01... Info: Starting to save the repository
    Jul 19, 2008 11:21:02... Info: Finished saving the repository
    Jul 19, 2008 11:21:02... Info: Starting: Initial deployment: Selected software component 'BI-WDALV'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.15.0.20080218054927''/'0' will be deployed.
    Jul 19, 2008 11:21:02... Error: Aborted: software component 'BI-WDALV'/'sap.com'/'MAIN_APL70VAL_C'/'1000.7.00.15.0.20080218054927''/'0':
    Failed deployment of SDAs:
    development component 'bi/alv/common'/'sap.com'/'MAIN_APL70VAL_C'/'1077259'/'0' : aborted
    Please, look at error logs above for more information!
    Jul 19, 2008 11:21:02... Info: Starting to save the repository
    Jul 19, 2008 11:21:03... Info: Finished saving the repository
    Jul 19, 2008 11:21:03... Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
    Jul 19, 2008 11:21:03... Error: -
    At least one of the Deployments failed -
    Thanks

    what is your current support pack level?
    target level?
    if your curredt level is 6, 7 or 8 and target level is 11, 12, or 13
    read this note "978042"
    regards,

  • Deployment Server Error

    Hy all,
    i have a problem with my Instalation. i have installed the deployment server,enterprise server, Html server, i have created my installation plan, but when i run installation workbench i get the following error:
    "Connection to Planner-900 has been lost" and i can not finish my plan. :(
    i have searched the logs and found "ora-03114 end of channel communication" can anyone please help!
    Thanx!

    Problem Solved ;)
    Edited by: PilotRO on 30.10.2009 01:03

  • How to add a project to the deployment components under deployment server

    Hi,
    When I run one of my projects in JSC, I got following error message:
    "application NeuronBank is already deployed on other targets. Please use create-application-ref command to create reference to the specified target; requested operation cannot be completed."
    So I checked the Deployed Components under Deployment Server, and my project is not listed there. I think that this might cause my problem. But I have no idea why this can happen? Can I add my project into this list and How?
    Thanks,

    Check the following threads
    http://forum.sun.com/jive/thread.jspa?forumID=123&threadID=56901
    http://forum.sun.com/jive/thread.jspa?forumID=123&threadID=64307

  • How to fix "server problem" error message when trying to use PhoneGap build service.

    I have a site that is now optimized for mobile devices and want to use the PhoneGap Build service in Dreamweaver CS6 to make a native app.  Unfortunately, I keep getting the "We seem to be having server problems." error message when I try to create a new project.  I did notice that the configuration file was created at the site root.  I've seen a few other similar threads on this, but no solution.  I've checked on any firewall issues (none) and know that the PhoneGap server is not down.  The problem is on my end.
    Thanks,
    Loren

    Not an answer to the server problem, but I have posted the PhoneGap Build process here: http://forums.adobe.com/message/4669054#4669054. It might help anyone still having problems.

  • Windows Server 2012 "standard" or "datacenter" as a Deployment Server, which one??

    As the question states. I am Certified ESDT/EDA (MCITP), MCSA Windows 7, working on my Windows Server 2008 MCSA. We are hybrid, Novel/Windows environment and make our move to Windows, so my actual work with a windows environment (other then Desktop
    support) is limited.  I have been tasked with building a Deployment Server, we have Windows Server 2008R2, but I requested Windows Server 2012R2, (only because it is the latest, greatest), most current version.  I have "not" done much "hands
    on", all my experience has been down in Virtual Environment, (at home).  So which would be the best version to use as a deployment server, our network administrator as provided me with a 6 Terabyte server for imaging, (we are 'finally' moving
    away from Novell "zenworks").   Any assistance, additional information would be appreciated.  
    Christopher Espinoza MCDST(XP), MCITP(Win7)

    As Muhammad says, with WS2012 or WS2012R2, there is no feature/functional difference between STD or DC editions (the difference is only related to the virtualisation rights).
    For setting up deployment services, MDT is generally recommended, as MDT organises and glues together the native/raw features for you:
    http://technet.microsoft.com/en-US/windows/dn475741.aspx
    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

  • [Fwd: Starting Managed server problem ......]

    Forwarding to the security news group...
    -------- Original Message --------
    Subject: Starting Managed server problem ......
    Date: 1 Jun 2004 23:02:53 -0700
    From: Sameer <barsatkiraat2001>
    Newsgroups: weblogic.developer.interest.management
    Hi All,
    I need you guy's help in this regard, that I am using solaris 8 and
    installed Weblogic8.1 Server.
    My Scenario is;
    Have configured Admin Server and Managed server with nodemanager on one
    unix machine.
    So, what am facing the problem;
    I am not able to get run Managed server after starting the nodemanager
    and admin server, getting the error in nodemanager logs that is :
    <Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <Security> <BEA-090482>
    <BAD_CERTIFICATE alert was received from PortalQA - 10.12.10.94. Check
    the peer to determine why it rejected the certificate chain (trusted CA
    configuration, hostname verification). SSL debug tracing may be required
    to determine the exact reason the certificate was rejected.>
    And in Admin Server logs it's saying;
    <Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <Security> <BEA-090504>
    <Certificate chain received from PortalQA - 10.12.10.94 failed hostname
    verification check. Certificate contained AdminQA but check expected
    PortalQA>
    The WebLogic Server did not start up properly.
    Exception raised:
    'weblogic.management.configuration.ConfigurationException: Due to faulty
    SSL configuration, this server is unable to establish a connection to
    the node manager.'
    <Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <NodeManager> <BEA-300038>
    <The node manager is unable to monitor this server. Could not create an
    SSL connection to the node manager. Reason :
    [Security:090504]Certificate chain received from PortalQA - 10.12.10.94
    failed hostname verification check. Certificate contained AdminQA but
    check expected PortalQA>
    Reason: weblogic.management.configuration.ConfigurationException: Due to
    faulty SSL configuration, this server is unable to establish a
    connection to the node manager.
    <Jun 2, 2004 9:44:26 AM GMT 04:00> <Emergency> <WebLogicServer>
    <BEA-000342> <Unable to initialize the server:
    weblogic.management.configuration.ConfigurationException: Due to faulty
    SSL configuration, this server is unable to establish a connection to
    the node manager.>
    If some one can help me, I do appreciate in all due respect.
    Sameer.

    Hello Satya/All,
    I'm also experiencing the exact problem you are facing. It would be great if
    somebody could help in this regard at the earliest.
    Thanks, senthil
    Satya Ghattu <[email protected]> wrote:
    Forwarding to the security news group...
    -------- Original Message --------
    Subject: Starting Managed server problem ......
    Date: 1 Jun 2004 23:02:53 -0700
    From: Sameer <barsatkiraat2001>
    Newsgroups: weblogic.developer.interest.management
    Hi All,
    I need you guy's help in this regard, that I am using solaris 8 and
    installed Weblogic8.1 Server.
    My Scenario is;
    Have configured Admin Server and Managed server with nodemanager on one
    unix machine.
    So, what am facing the problem;
    I am not able to get run Managed server after starting the nodemanager
    and admin server, getting the error in nodemanager logs that is :
    <Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <Security> <BEA-090482>
    <BAD_CERTIFICATE alert was received from PortalQA - 10.12.10.94. Check
    the peer to determine why it rejected the certificate chain (trusted
    CA
    configuration, hostname verification). SSL debug tracing may be required
    to determine the exact reason the certificate was rejected.>
    And in Admin Server logs it's saying;
    <Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <Security> <BEA-090504>
    <Certificate chain received from PortalQA - 10.12.10.94 failed hostname
    verification check. Certificate contained AdminQA but check expected
    PortalQA>
    The WebLogic Server did not start up properly.
    Exception raised:
    'weblogic.management.configuration.ConfigurationException: Due to faulty
    SSL configuration, this server is unable to establish a connection to
    the node manager.'
    <Jun 2, 2004 9:44:26 AM GMT 04:00> <Warning> <NodeManager> <BEA-300038>
    <The node manager is unable to monitor this server. Could not create
    an
    SSL connection to the node manager. Reason :
    [Security:090504]Certificate chain received from PortalQA - 10.12.10.94
    failed hostname verification check. Certificate contained AdminQA but
    check expected PortalQA>
    Reason: weblogic.management.configuration.ConfigurationException: Due
    to
    faulty SSL configuration, this server is unable to establish a
    connection to the node manager.
    <Jun 2, 2004 9:44:26 AM GMT 04:00> <Emergency> <WebLogicServer>
    <BEA-000342> <Unable to initialize the server:
    weblogic.management.configuration.ConfigurationException: Due to faulty
    SSL configuration, this server is unable to establish a connection to
    the node manager.>
    If some one can help me, I do appreciate in all due respect.
    Sameer.

  • Photoshop CS2: name server problem: Is there a solution?

    Hi!
    I have Photoshop CS2. I can't start the program anymore because of the already well known name server problem... (DEAR ADOBE!! HOW COULD YOU!!! )
    Now, what can I do? As far as I know I purchased the software for an unlimited amount of time (thanks to the fact that there weren't any clouds, halleluja!)
    Can anybody help me, please? Is there a way "around"?
    Thanks a lot!!!
    Christiane

    Error: Activation Server Unavailable | CS2, Acrobat 7, Audition 3

Maybe you are looking for

  • How do I change a serial number for FCP Studio entered in error

    I recently had to reinstall everything and I used the serial number for a co-worker's software by mistake. I have the right serial number, but when I try to re-install, the pane for entering the serial number never comes up and I end up with the same

  • How can I buy Snow Leopard in Russia?

    I have MacBookPro '13 bought in 2008. MacOS is Leopard. Now I would like to upgrade to Snow Leopard, since Lion is too 'heavy' for my computer (I work with graphics a lot). However, no Apple reseller in St.Petersburg (Russia) would sell me Snow Leopa

  • I can not e-mail pictures from iPhoto

    Hello, I am using iPhoto (9.4.1) on my iMac (OS X 10.8.2) and my default mail program is Outlook (14.2.4). A few weeks ago it was possible to mark pictures in iPhoto, to click on the mail icon and Outlook would open a message with the attached pictur

  • Auto update GUI from server

    Goodmorning, i have installed over server "SAP Setup Administrator server" for mantain a gui with centralized deployment. I do some upgrade to packages. For put this new version of package i see in documentation that i must insert an "SAP Automatic s

  • NI 9219 and 22k Ohm Thermistors

    Hi all, Is there any chance to read thermistors more than 10K ? In particular I have to use 12 22K ohm thermistors. Thank you in advance, Pets