PROBLEM VIRTUAL SERVER GLASSFISH

Hi I have problems setting up virtual servers, for example my page www.pagina.com
when configuring the virtual server
id = page.com
host = page.com, www.page.com
the problem is that I read the index.html page.com the docroot www.page.com but works well, I read the war and runs it, the problem is when you have no "www"
any idea?
i am from argentina , thanks.

Are you using Web Server or Application Server? If you are using Glassfish Application Server, then please write to Java.net GlassFish Forum located at [http://forums.java.net/jive/forum.jspa?forumID=56|http://forums.java.net/jive/forum.jspa?forumID=56]

Similar Messages

  • Problem with virtual Server

    We are trying to fix a problem where a URL is only supposed to be visible from the company intranet, not the internet as a whole.
    We have created a virtual server on the same system that is listening on a different port (1443 instead of 443) . However despite various changes to the server.xml such as changing the docroot, disabling or removing WEBAPP entries etc, the server behaves exactly the same on port 1443 as it does on port 443.
    If I could make it display ANYTHING differently it would be a start. Any assistance is appreciated.

    Care to share your non-working server.xml file?

  • Virtual Server problem

    We are having a problem with the wrong pages being displayed
    for a new virtual server that has just been setup on one of our
    existing servers. if I request index.cfm from the new virtual
    server, I get index.cfm from the existing virtual server. HTML
    pages are displayed correctly, and so are pages from the second
    virtual server that do not have the same name as a file on the
    first.
    The symptoms are exactly as described in
    this technote, but the
    catch is that "Cache web server paths" is already unchecked in CF
    Administrator (and the setting in jrun.xml is also correct).
    Does anyone know of any other causes of this problem (and
    hopefully a solution)?
    Thanks
    Tim

    For the benefit of anyone else with the same problem, we
    solved this by following the steps described at
    http://www.bloginblack.de/archives/000120.cfm
    English
    translation)

  • Virtual Server Conversion problem

    Hello Team,
    I am facing a problem where my virtual server IP is translated wrongly on the Cisco 7604 router. The TCP connection related is dropped due to this IP. I checked the vserver configuration and found that the TCP drop could be due to Idle 10 config on the serverfarm config. I am attaching the running configuration along with the problems we are facing:
    1. Node X sends “Keep Alive” message on TCP session to Node Y.
    2. Router converts real IP address of Node X to virtual IP address.
    However, although virtual IP address should be “172.20.40.20”, Router converts it to “10.129.120.7x”.
    6. Node Y receives “Keep Alive” message on TCP session from “10.129.120.7x”. However the source IP address is abnormal as the TCP session so Node Y discards this “Keep Alive”.
    7. Router detects that Node Y has never responded to Node X against “Keep Alive”. As the result, router Resets the TCP session.
    8. Due to the above, all TCP sessions are disconnected.
    The Running Config is attached for reference.
    Regards
    Hemanth

    Hi Glenn,
    According to your description, my understanding is that you could not access site pages after doing a virtual migration using VMware Converter.
    Please run the PowerShell command below on the VMware vSphere 5.5 v10 machine:
    psconfigui.exe –cmd setup –runbysetup
    There are two similar posts for your reference:
    https://social.technet.microsoft.com/Forums/en-US/7f903e1d-4965-4d4a-87e7-114f43bd4501/sharepoint-2010-the-trial-period-for-this-product-has-expired
    http://retrohack.com/sharepoint-2010-trial-period-expired/
    If this issue still exists, please check the log file to find more information about this issue. The path of the log file is: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS.
    Best Regards,
    Wendy
    Wendy Li
    TechNet Community Support

  • Virtual Server Logging Problem

    I'm currently using Sun Application Server 9. I've created a virtual server together with a new listener on a port 8081. I have two problems here:
    1) The website on the virtual server runs fine. And I've coded System.out.println on several servlets for assisting purposes. My problem is that, i can't see those message printed on the server.log by System.out.println.
    2) The same copy of WAR file has been deployed to the virtual server which it's able to perform JDBC functions in default server. Thing turns funny when the same WAR file that runs on the virtual server is unable to perform the JDBC functions.
    Can't figure out why. Please help me.
    Thanks!

    There are two kinds of virutal servers - IP/Socket/Port based, and URLHost based.
    You created a IP/Socket/Port based virtual server. Instead, you should look for the URLHost fiend in the virtual server pages and change it to reflect the correct DNS name it should respond to. Make sure this VS (and the default) are both attached to the port 80 listen socket.

  • Problem with NetBeans & Glassfish

    Hi
    I have done the "Simple Web Application Using a MySQL Database" tutorial. I got it to work with NetBeans 6.0. I then desicied to upgrade to 6.1 (uninstalled 6.0 and the Glassfish). After installation a run the application again with the following error (the four last lines):
    Starting Sun Java System Application Server 9.1_02 (build b04-fcs) ...
    MBeanServer started: com.sun.enterprise.interceptor.DynamicInterceptor
    CORE5098: AS Socket Service Initialization has been completed.
    CORE5076: Using [Java HotSpot(TM) Client VM, Version 1.5.0_12] from [Sun Microsystems Inc.]
    SEC1002: Security Manager is OFF.
    F:/Program/glassfish-v2ur2/domains/domain1/config/.__com_sun_appserv_pid
    ADM0001:SunoneInterceptor is now enabled
    SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.
    WEB0114: SSO is disabled in virtual server [server]
    WEB0114: SSO is disabled in virtual server [__asadmin]
    ADM1079: Initialization of AMX MBeans started
    ADM1504: Here is the JMXServiceURL for the Standard JMXConnectorServer: [service:jmx:rmi:///jndi/rmi://192.168.0.167:8686/jmxrmi]. This is where the remote administrative clients should connect using the standard JMX connectors
    ADM1506: Status of Standard JMX Connector: Active = [true]
    WEB0302: Starting Sun-Java-System/Application-Server.
    JBIFW0010: JBI framework ready to accept requests.
    WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 8080
    WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 8181
    WEB0712: Starting Sun-Java-System/Application-Server HTTP/1.1 on 4848
    SMGT0007: Self Management Rules service is enabled
    Application server startup complete.
    SEC5046: Audit: Authentication refused for [admin].
    Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for admin.
    SEC5046: Audit: Authentication refused for [admin].
    Web login failed: Login failed: javax.security.auth.login.LoginException: Failed file login for admin.
    I'm abel to log in onto the Glassfish server from the admin tool. But it seams that i can't logg in from the application. How do I handel this problem?
    Best regards
    Jonas
    Edited by: Lun on May 4, 2008 1:12 AM
    Edited by: Lun on May 4, 2008 1:14 AM
    Edited by: Lun on May 4, 2008 1:16 AM
    Edited by: Lun on May 4, 2008 1:18 AM
    Edited by: Lun on May 4, 2008 5:29 AM

    Im using "+JSF 1.1.02 Ri Run time suport -deprecated+", that library dont need to be include in the project becouse glashfish support it, (I thing)
    And I add Myfaces 1.2.2 with Tomahawk 1.1.6, becouse I need a jscookmenu, and tomahawk bring it. and Glassfish v2

  • Startup Problems Application Server on Fedora Core 5

    Greetings All;
    Little background information
    router ip address: 192.168.1.1
    web server ip address: 192.168.1.101 (outside: dcrumb.homeip.net)
    installed from ip address: 192.168.1.100
    using jdk-1.5.0_07
    here are my applicable firewall rules:
    -A RH-Firewall-1-INPUT -m state state NEW -m tcp -p tcp dport 4848 -j ACCEPT
    -A RH-Firewall-1-INPUT -m state state NEW -m tcp -p tcp dport 8080 -j ACCEPT
    -A RH-Firewall-1-INPUT -m state state NEW -m tcp -p tcp dport 8181 -j ACCEPT
    -A RH-Firewall-1-INPUT -m state state NEW -m tcp -p tcp dport 8686 -j ACCEPT
    I've also forwarded these ports in my Linksys router
    Here are my error messages:
    [#|2006-06-14T22:30:13.251-0400|INFO|sun-appserver-pe8.2|javax.enterprise.tools.launcher|_ThreadID=10;|
    /usr/share/jdk1.5.0_07/bin/java
    -client
    -Xmx512m
    -XX:NewRatio=2
    -Dcom.sun.aas.defaultLogFile=/opt/SUNWappserver/domains/domain1/logs/server.log
    -Djava.endorsed.dirs=/opt/SUNWappserver/lib/endorsed
    -Djava.security.policy=/opt/SUNWappserver/domains/domain1/config/server.policy
    -Djava.security.auth.login.config=/opt/SUNWappserver/domains/domain1/config/login.conf
    -Dsun.rmi.dgc.server.gcInterval=3600000
    -Dsun.rmi.dgc.client.gcInterval=3600000
    -Djavax.net.ssl.keyStore=/opt/SUNWappserver/domains/domain1/config/keystore.jks
    -Djavax.net.ssl.trustStore=/opt/SUNWappserver/domains/domain1/config/cacerts.jks
    -Djava.ext.dirs=/usr/share/jdk1.5.0_07/jre/lib/ext:/opt/SUNWappserver/domains/domain1/lib/ext:/opt/SUNWappserver/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
    -Dorg.xml.sax.parser=org.xml.sax.helpers.XMLReaderAdapter
    -Ddomain.name=domain1
    -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=/opt/SUNWappserver/domains/domain1
    -Djavax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
    -Dcom.sun.aas.domainName=domain1
    -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=/opt/SUNWappserver/config
    -Djava.library.path=/usr/share/jdk1.5.0_07/jre/lib/i386/client:/usr/share/jdk1.5.0_07/jre/lib/i386/client:/usr/share/jdk1.5.0_07/jre/lib/i386:/usr/share/jdk1.5.0_07/jre/../lib/i386:/opt/SUNWappserver/lib:/usr/lib/lwp:/opt/SUNWappserver/lib:/usr/lib/lwp:/usr/share/jdk1.5.0_07/jre/lib/i386/client:/usr/share/jdk1.5.0_07/jre/lib/i386:/usr/share/jdk1.5.0_07/jre/../lib/i386:/opt/SUNWappserver/lib:/opt/SUNWappserver/lib:/opt/SUNWappserver/lib:
    -Dcom.sun.aas.instanceName=server
    -Dcom.sun.aas.processLauncher=SE
    -cp
    /usr/share/jdk1.5.0_07/lib/tools.jar:/opt/SUNWappserver/lib/appserv-rt.jar:/opt/SUNWappserver/lib/admin-cli.jar:/opt/SUNWappserver/lib/jax-qname.jar:/opt/SUNWappserver/lib/appserv-cmp.jar:/opt/SUNWappserver/lib/jaxrpc-impl.jar:/opt/SUNWappserver/lib/commons-launcher.jar:/opt/SUNWappserver/lib/jmxremote_optional.jar:/opt/SUNWappserver/lib/j2ee-svc.jar:/opt/SUNWappserver/lib/commons-logging.jar:/opt/SUNWappserver/lib/mail.jar:/opt/SUNWappserver/lib/dom.jar:/opt/SUNWappserver/lib/appserv-jstl.jar:/opt/SUNWappserver/lib/jaxr-impl.jar:/opt/SUNWappserver/lib/j2ee.jar:/opt/SUNWappserver/lib/jsf-api.jar:/opt/SUNWappserver/lib/jsf-impl.jar:/opt/SUNWappserver/lib/saaj-api.jar:/opt/SUNWappserver/lib/appserv-upgrade.jar:/opt/SUNWappserver/lib/jaxr-api.jar:/opt/SUNWappserver/lib/xsdlib.jar:/opt/SUNWappserver/lib/saaj-impl.jar:/opt/SUNWappserver/lib/rmissl.jar:/opt/SUNWappserver/lib/relaxngDatatype.jar:/opt/SUNWappserver/lib/xercesImpl.jar:/opt/SUNWappserver/lib/xalan.jar:/opt/SUNWappserver/lib/appserv-admin.jar:/opt/SUNWappserver/lib/appserv-ext.jar:/opt/SUNWappserver/lib/jaxrpc-api.jar:/opt/SUNWappserver/lib/activation.jar:/opt/SUNWappserver/lib/jmxremote.jar:/opt/SUNWappserver/lib/install/applications/jmsra/imqjmsra.jar:/opt/SUNWappserver/imq/lib/jaxm-api.jar:/opt/SUNWappserver/imq/lib/fscontext.jar:/opt/SUNWappserver/lib/ant/lib/ant.jar
    com.sun.enterprise.server.PEMain
    start
    display|#]
    [#|2006-06-14T22:30:29.526-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [/opt/SUNWappserver/imq/bin].|#]
    [#|2006-06-14T22:30:29.537-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5098: AS Socket Service Initialization has been completed.|#]
    [#|2006-06-14T22:30:33.433-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.|#]
    [#|2006-06-14T22:30:33.461-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]
    [#|2006-06-14T22:30:34.381-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]
    [#|2006-06-14T22:30:37.708-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server server|#]
    [#|2006-06-14T22:30:37.769-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server __asadmin|#]
    [#|2006-06-14T22:30:41.921-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: all interfaces/3700"|#]
    [#|2006-06-14T22:30:44.285-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: all interfaces/3820"|#]
    [#|2006-06-14T22:30:44.322-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: all interfaces/3920"|#]
    [#|2006-06-14T22:30:49.383-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [3700]|#]
    [#|2006-06-14T22:31:15.145-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1079: Initialization of AMX MBeans successful|#]
    [#|2006-06-14T22:31:17.679-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: TimerBean; containerId: 75388332422004736|#]
    [#|2006-06-14T22:31:19.824-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]
    [#|2006-06-14T22:31:19.826-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]
    [#|2006-06-14T22:31:20.540-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: MEJBBean; containerId: 75388332902776832|#]
    [#|2006-06-14T22:31:21.303-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]
    [#|2006-06-14T22:31:21.542-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Sun-Java-System/Application-Server.|#]
    [#|2006-06-14T22:31:21.995-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [__default-admingui] in virtual server [__asadmin] at []|#]
    [#|2006-06-14T22:31:22.758-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|#]
    [#|2006-06-14T22:31:23.256-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [__asadmin] at [web1]|#]
    [#|2006-06-14T22:31:23.306-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [__asadmin] at [asadmin]|#]
    [#|2006-06-14T22:31:23.320-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|#]
    [#|2006-06-14T22:31:23.350-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]|#]
    [#|2006-06-14T22:31:23.931-0400|INFO|sun-appserver-pe8.2|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server|#]
    [#|2006-06-14T22:31:33.650-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Non-Blocking Mode|#]
    [#|2006-06-14T22:31:33.651-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 8080|#]
    [#|2006-06-14T22:31:33.720-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 8080|#]
    [#|2006-06-14T22:31:34.266-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Blocking Mode|#]
    [#|2006-06-14T22:31:34.268-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 8181|#]
    [#|2006-06-14T22:31:34.290-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 8181|#]
    [#|2006-06-14T22:31:34.523-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Non-Blocking Mode|#]
    [#|2006-06-14T22:31:34.524-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 4848|#]
    [#|2006-06-14T22:31:34.546-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 4848|#]
    [#|2006-06-14T22:31:35.616-0400|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Service [email protected]3 cannot be started! : com.sun.appserv.server.ServerLifecycleException: Cannot bind to URL [rmi://dcrumb.homeip.net:8686/management/rmi-jmx-connector]: javax.naming.NoPermissionException [Root exception is java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
            java.rmi.AccessException: Registry.Registry.bind disallowed; origin /192.168.1.1 is non-local host]|#]
    [#|2006-06-14T22:31:35.619-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://dcrumb.homeip.net:8686/management/rmi-jmx-connector]: javax.naming.NoPermissionException [Root exception is java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
            java.rmi.AccessException: Registry.Registry.bind disallowed; origin /192.168.1.1 is non-local host]
    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)
    Caused by: java.io.IOException: Cannot bind to URL [rmi://dcrumb.homeip.net:8686/management/rmi-jmx-connector]: javax.naming.NoPermissionException [Root exception is java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
            java.rmi.AccessException: Registry.Registry.bind disallowed; origin /192.168.1.1 is non-local host]
    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)
    ... 3 more
    Caused by: javax.naming.NoPermissionException [Root exception is java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
            java.rmi.AccessException: Registry.Registry.bind disallowed; origin /192.168.1.1 is non-local host]
    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)
    ... 5 more
    Caused by: java.rmi.ServerException: RemoteException occurred in server thread; nested exception is:
    java.rmi.AccessException: Registry.Registry.bind disallowed; origin /192.168.1.1 is non-local host
    at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:385)
    at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
    at sun.rmi.transport.Transport$1.run(Transport.java:153)
    at java.security.AccessController.doPrivileged(Native Method)
    at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
    at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
    at java.lang.Thread.run(Thread.java:595)
    at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:247)
    at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:223)
    at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:343)
    at sun.rmi.registry.RegistryImpl_Stub.bind(Unknown Source)
    at com.sun.jndi.rmi.registry.RegistryContext.bind(RegistryContext.java:116)
    ... 9 more
    Caused by: java.rmi.AccessException: Registry.Registry.bind disallowed; origin /192.168.1.1 is non-local host
    at sun.rmi.registry.RegistryImpl.checkAccess(RegistryImpl.java:223)
    at sun.rmi.registry.RegistryImpl.bind(RegistryImpl.java:119)
    at sun.rmi.registry.RegistryImpl_Skel.dispatch(Unknown Source)
    at sun.rmi.server.UnicastServerRef.oldDispatch(UnicastServerRef.java:375)
    at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:240)
    at sun.rmi.transport.Transport$1.run(Transport.java:153)
    at java.security.AccessController.doPrivileged(Native Method)
    at sun.rmi.transport.Transport.serviceCall(Transport.java:149)
    at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:466)
    at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:707)
    at java.lang.Thread.run(Thread.java:595)
    |#]
    [#|2006-06-14T22:31:35.629-0400|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Server Startup failed. Exiting...|#]
    [#|2006-06-14T22:31:35.630-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Server shutdown in progress...|#]
    [#|2006-06-14T22:31:35.639-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)
    |#]
    |#]
    [#|2006-06-14T22:31:35.642-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0303: Stopping Sun-Java-System/Application-Server.|#]
    [#|2006-06-14T22:31:35.665-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 8080|#]
    [#|2006-06-14T22:31:35.708-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 8181|#]
    [#|2006-06-14T22:31:35.728-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 4848|#]
    [#|2006-06-14T22:31:36.657-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5051: Shutting down all J2EE applications ...|#]
    [#|2006-06-14T22:31:36.675-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5122:EJB Timer Service shutdown at [2006/06/14 22:31:36]|#]
    [#|2006-06-14T22:31:36.676-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE 5060 :  Stopping all J2EE Connector 1.5 Compliant resource adapters ...|#]
    [#|2006-06-14T22:31:36.686-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.resourceadapter|_ThreadID=10;|RAR7094: __xa shutdown successfully.|#]
    [#|2006-06-14T22:31:36.687-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE 5061 : Resource adapters Stop() Complete|#]
    [#|2006-06-14T22:31:36.688-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5052: Application shutdown complete.|#]
    [#|2006-06-14T22:31:38.281-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5025: JMS service shutting down.|#]
    [#|2006-06-14T22:31:39.375-0400|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5026: JMS service shutdown complete.|#]
    [#|2006-06-14T22:31:39.376-0400|SEVERE|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Server stopped due to Server startup failure.|#]
    [#|2006-06-14T22:31:39.452-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=11;|sending notification to server...server|#]
    [#|2006-06-14T22:31:39.482-0400|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=11;|Server shutdown complete.|#]
    Does anybody have any suggestions?
    Many thanks,
    Best,
    --Dave
    Message was edited by CrumbDav
    I did some more research and looked in my domain.xml file and came across this. Not sure if it helps any:
    - <configs>
    - <config dynamic-reconfiguration-enabled="true" name="server-config">
    - <http-service>
    <http-listener acceptor-threads="5" address="0.0.0.0" blocking-enabled="false" default-virtual-server="server" enabled="true" family="inet" id="http-listener-1" port="8080" security-enabled="false" server-name="" xpowered-by="true" />
    <http-listener acceptor-threads="5" address="0.0.0.0" blocking-enabled="false" default-virtual-server="server" enabled="true" family="inet" id="http-listener-2" port="8181" security-enabled="true" server-name="" xpowered-by="true" />
    <http-listener acceptor-threads="5" address="0.0.0.0" blocking-enabled="false" default-virtual-server="__asadmin" enabled="true" family="inet" id="admin-listener" port="4848" security-enabled="false" server-name="" xpowered-by="true" />
    - <virtual-server hosts="${com.sun.aas.hostName}" http-listeners="http-listener-1,http-listener-2" id="server" log-file="${com.sun.aas.instanceRoot}/logs/server.log" state="on">
    <property name="docroot" value="${com.sun.aas.instanceRoot}/docroot" />
    <property name="accesslog" value="${com.sun.aas.instanceRoot}/logs/access" />
    </virtual-server>
    - <virtual-server default-web-module="admingui" hosts="${com.sun.aas.hostName}" http-listeners="admin-listener" id="__asadmin" log-file="${com.sun.aas.instanceRoot}/logs/server.log" state="on">
    <property name="docroot" value="${com.sun.aas.instanceRoot}/docroot" />
    <property name="accesslog" value="${com.sun.aas.instanceRoot}/logs/access" />
    </virtual-server>
    </http-service>
    - <iiop-service client-authentication-required="false">
    <orb max-connections="1024" message-fragment-size="1024" use-thread-pool-ids="thread-pool-1" />
    <iiop-listener address="0.0.0.0" enabled="true" id="orb-listener-1" port="3700" security-enabled="false" />
    - <iiop-listener address="0.0.0.0" enabled="true" id="SSL" port="3820" security-enabled="true">
    <ssl cert-nickname="s1as" client-auth-enabled="false" ssl2-enabled="false" ssl3-enabled="true" tls-enabled="true" tls-rollback-enabled="true" />
    </iiop-listener>
    - <iiop-listener address="0.0.0.0" enabled="true" id="SSL_MUTUALAUTH" port="3920" security-enabled="true">
    <ssl cert-nickname="s1as" client-auth-enabled="true" ssl2-enabled="false" ssl3-enabled="true" tls-enabled="true" tls-rollback-enabled="true" />
    </iiop-listener>
    </iiop-service>

    Nope - it's not supported. It is useable though ...
    The problem is that the Fedora series uses cutting edge technology. The Fedora technology cycles every 6-9 months.
    Oracle likes things very stable. So Oracle builds a clean copy using a specific set of APIs at a specific release of the kernel, the glibc and so on. They chose the commercial releases which cycle every 18-24 months - in part so they can get people trained to provide support.
    Due to the nature of Linux, you CAN install the correct APIs and get it to work and many of the free distros. Just don't expect Oracle to provide assistance or support. (After all, where do they stop - there are hundreds of free distros, and even more when you count the 'objsolete but still running' ones.)
    If you really want to proceed, then you need to read up the cookbook sites from experts such as Ivan Kartik (http://ivan.kartik.sk/) or Werner Puschitz (http://www.puschitz.com) As long as you realize that the install is NOT recommended for production.

  • Business connector server on Virtual Server

    Hi,
    Currently our 4.6 release Business Connector servers running on Windows NT Operating system. We would like to upgrade them to BC release 4.7 on Windows 2000 operating system on Virtual servers.
    Are there any known issues/disadvantages if we install Business connector servers on Virtual Server rather than a Physical server?
    These virtual servers will be in the same domain as that of SAP systems. Host names of the upgraded Virtual servers will be same as the current production BC hosts.
    Thanks,
    Srini

    Technical Data
    These functions are:
    Changed, new, deleted
    For Release
       Software Component
    ·        Component: SAP Business Connector (external)
    ·        Release: 4.7
    Assignment to Application Component
    BC-MID-BUS (SAP Business Connector)
    Country Setting
    Valid for all countries
    Use
    The following information provides you with an overview of the new features in SAP BC Release 4.7: It also tells you about incompatible changes that you need to know about before performing an upgrade.
    SAP BC 4.7 is based on Integration Server 4.6 from webMethods. However, the SAP BC elements in Integration Server 4.6 have been redeveloped (see below for details).
    Features
    Additional Functions in SAP BC Developer
    As well as SAP BC Administrator GUI, you can now use SAP BC Developer to perform typical development tasks.  You do not need administrator authorizations in SAP BC Developer to do this. For example, with SAP BC 4.7 you can use SAP Lookup to generate elements for the Developer.  This enables you to gather information about function modules, structures (tables), BAPIs and IDocs in an SAP system, and then generate outbound maps or records for these objects directly.
    SAP BC Developer contains a new menu, SAP, which contains the following functions:
    ·        Look up a function module and generate an outbound map
    ·        Look up a structure definition and generate a record.
    ·        Lookup a business object.
    ·        Look up an IDoc and creating a Record.
    ·        Browser for Function Maps.
    In addition, the Developer now also supports the following actions:
    ·        Generate an SAP inbound map if you want an SAP system to run a service in SAP BC.
    ·        Generate an SAP outbound map to execute a function module in an SAP system.
    ·        Generate a record based on an SAP ABAP Dictionary structure.
    ·        Generate a record based on an SAP IDoc.
    SAP BC Developer now also supports a proxy bypass list. This means that you no longer need to define whether a connection runs through a proxy; instead, the bypass list performs this task.
    New Public Services on SAP BC Server
    pub.string:gzip
    Compresses the specified input string and generates a check total (optional). For measurements or for statistical purposes, the lengths of the zipped and unzipped strings are provided as output.
    ·        pub.string:ungzip
    Decompresses a specified input string, which was compressed with pub.string:gzip, and verifies the check total (optional).
    ·        pub.string:numericParse
    Analyzes a number in accordance with a given number pattern.
    ·        pub.math:randomLong
    Generates a pseudo random number and sends its string representation in a pipeline variable. You can use this number as a universal identifier with an acceptable level of security, as long as it is used in non-distributed scenarios and for a small number of variables.
    ·        pub.file:head
    Shows the start of a given file.
    ·        pub.file:tail
    Shows the end of a given file.
    ·        pub.flow:sleep
    Puts the current service into sleep mode for the specified period (in seconds).
    Restructuring of the WmPartners Package
    The WmPartners package in SAP BC Server has been completely restructured and now offers the following enhancements:
    ·        Improved status information in the messages displayed in the Transaction Store and the Audit Log. This solves a range of problems, such as incorrect status information being displayed by IDocs.
    ·        Improved search and sort options for transactions in the file system of the Message Store. In the Transactions menu, SAP BC Administrator GUI offers you a new option, Message Store Query Settings, which enables you to select and delete transactions. In Release 4.7, the Message Store can also be displayed on separate pages, which makes it easier to edit large numbers of transactions.
    ·        Improved search and sort options for Routing Rules. In the Routing Rules menu, SAP BC Administrator GUI offers you a new option, Routing Rule Filter Settings, which enables you to restrict the number of routing rules that are displayed, and to sort the display. The filter accepts all combinations of characters, and the placeholders '*' (string of characters) and  '?' (one character). This makes it easier to sort and search for routing rules, especially if you need to process a large number of communication partners and message types.
    ·        Forwarding the "Confirm Event" tRFC (triggered by an SAP system) to the next receiver (for the following transports: B2B Service, ALE (R/3 IDoc), and XML (only if another SAP BC is the receiver)) and triggering "Confirm Event" from an external client. Both of these cases can be significant if the final receiver is an SAP system. In this case, "Confirm Event" removes the transaction ID from the ARFCRSTATE table, which can improve system performance significantly when a large number of tRFCs are being processed.
    Support for Distributed Statistic Records (DSRs)
    SAP BC has supported the generation of DSRs since Release 4.7  DSRs enable you to monitor the performance of each SAP system and its components. In this way, you can check how much system load is produced by each individual component, and how many resources are being used. This enables you to identify "performance leaks" and optimize system performance.
    The DSR support integrated in SAP BC also allows you to measure the total retention period of a process in SAP BC. To evaluate the DSRs, you require additional SAP software, including specific versions of the SAP Solution Manager, and the RFC Library. The exact requirements are still being defined.
    The details will be published in SAP Note 620418. You can find a link to this SAP Note on the SAP BC download page at http://service.sap.com/sbc-download.
    SAP BC Server Core Enhancements
    ·        Reverse Invoke
    The reverse invoke protocol has been enhanced and now allows you to forward more information, such as IP addresses.
    If, for example, an application fails because a connection is broken, and other working connections exist, the connection is checked using a ping.
    From now on, the internal server can open or reopen a defined number of connections, if necessary.
    A document is generated for any exceptions on the internal server.
    ·        Email Listener
    New Features in the Email Listener
    ¡        Reprocessing of invalid mails for IMAP Server
    ¡        Processed mails selected as "unread" if they have not been deleted.
    You can also specify whether mails with exceptions are deleted or not.
    ·        Update Manager
    The Update Manager manages fixes and patches for the upgrade of an SAP BC Server. Previously , the Update Manager allowed a fix to set other fixes as obsolete, using the updateVoidList field in the update.cnf file of the fix. An obsolete fix is not shown in classpath, but up to now the Update Manager has not been able to give a fix in classpath priority ahead of this other fix. The Update Manager has now been enhanced to support these fix priorities:  The update.cnf file in the fix now contains an updatePrecedeList field.
    Incompatible Changes
    SAP BC Delivery Without JVM
    The Windows Version of SAP BC 4.7 is no longer delivered with a Java Virtual Machine (JVM). The SAP BC 4.7 Installation Guide describes the JVMs that are supported.
    See also
    For more information, see the documentation on the SAP Business Connector, under
    ·        http://service.sap.com/connectors (SAP Business Connector  ® SAP Business Connector in Detail  ® Documentation).

  • IPlanet Web Server & Glassfish not takeover session from stoped instance?

    I have 3 Physical Machine
    1> server hostname is 'linuxgf175'(192.168.1.175) main cluster control (DAS) and Install iPlanet Webserver with gflb-configurator
    2> server hostname is 'linuxgf170'(192.168.1.170) server for node1(n1) has Instance1 (i1)
    3> server hostname is 'linuxgf180'(192.168.1.180) server for node2(n2) has Instance2 (i2)
    1. I was install iPlanet Web Server to same DAS machine. (192.168.1.175)
    2. And create Server Certificates request.
    Certificate Details
    Nickname cert-linuxgf175
    Subject CN=linuxgf175
    Issuer Self Signed
    Key Type RSA
    Key Size (bits) 1024
    Valid From April 18, 2011 7:30:09 PM ICT
    Valid Till April 18, 2012 7:30:09 PM ICT
    Fingerprint CE:D8:5E:97:DB:56:89:00:56:A7:0F:EB:0D:D4:4A:06
    Serial Number 00:94:26:11:AB
    Server Name linuxgf175
    (Picture : http://s138.photobucket.com/albums/q262/madoatz/?action=view&current=iPl... )
    3. And create new http-listenser (SSL for communicate with DAS port 8082 )
    (Picture : http://s138.photobucket.com/albums/q262/madoatz/?action=view&current=iPl... )
    4. And import cert file(s1as.rfc) to glassfish-lbconfigurator wizard. (run lb-configure command #java -jar glassfish-lbconfigulator.jar )
    I was exported that file like this command :
    keytool -export -rfc -alias s1as -keystore /usr/glassfish3/glassfish/domains/domain1/config/keystore.jks -file ./s1as.rfc
    5. Create and Apply http-lb to DAS domain success !! :)
    asadmin> create-http-lb devicehost linuxgf175 deviceport 8082 --target c1 cluster_lb
    Enter admin user name> admin
    Enter admin password for user "admin">
    Command create-http-lb executed successfully.
    asadmin>
    asadmin> apply-http-lb-changes cluster_lb
    Enter admin user name> admin
    Enter admin password for user "admin">
    Command apply-http-lb-changes executed successfully.
    6. Deploy "clusterjsp.ear" Application to Cluster c1 with avalibilityenable=true
    deploy success
    (Picture : http://s138.photobucket.com/albums/q262/madoatz/?action=view&current=iPl... )
    7.try to open application , use browser open to iPlanet webserver success
    http://192.168.1.175:80/clusterjsp
    ## But, It can not handle session between instance (i1) and Instance 2 (i2)
    i input some data session into instance (i1)
    HttpSession Information:
    Served From Server: 192.168.1.175
    Server Port Number: 80
    Executed From Server: linuxgf170
    Executed Server IP Address: 127.0.0.1
    Session ID: 3ed17253ef55fb5d37203a738e2b
    Session Created: Thu Apr 21 00:20:08 ICT 2011
    Last Accessed: Thu Apr 21 00:20:08 ICT 2011
    Session will go inactive in 1800 seconds
    INPUT : test1 = test1
    INPUT : test2 = test2
    after that try to stop Instance (i1) linuxgf170
    come back to browser and refesh button. It's change route display to instance i2 (linuxgf180)
    HttpSession Information:
    Served From Server: 192.168.1.175
    Server Port Number: 80
    Executed From Server: linuxgf180
    Executed Server IP Address: 127.0.0.1
    Session ID: 3ee66ddd60498d68660a55fadcc5
    Session Created: Thu Apr 21 00:21:34 ICT 2011
    Last Accessed: Thu Apr 21 00:21:34 ICT 2011
    Session will go inactive in 1800 seconds
    BUT INPUT DATA is not display ?? I loss...session.
    Please sir.... please see image url and help clarify T_T
    Can direct contect to me for more help Thank you very much for best support.
    [email protected]
    skype : mr_lalit

    More iPlanet startup log....
    [root@linuxgf175 webserver7]# cd admin-server/
    [root@linuxgf175 admin-server]# cd bin/
    [root@linuxgf175 bin]# ./startserv
    Oracle iPlanet Web Server 7.0.9 B07/04/2010 01:31
    info: CORE3016: daemon is running as super-user
    info: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.6.0_20] from [Sun Microsystems Inc.]
    info: WEB0100: Loading web module in virtual server [admin-server] at [admingui]
    info: WEB0100: Loading web module in virtual server [admin-server] at [jmxconnector]
    info: HTTP3072: admin-ssl-port: https://linuxgf175:8989 ready to accept requests
    info: CORE3274: successful server startup
    [root@linuxgf175 bin]# cd ../../
    [root@linuxgf175 webserver7]# pwd
    /usr/glassfish3/webserver7
    [root@linuxgf175 webserver7]# cd https-linuxgf175/
    [root@linuxgf175 https-linuxgf175]# cd bin/
    [root@linuxgf175 bin]# ./startserv
    Oracle iPlanet Web Server 7.0.9 B07/04/2010 01:31
    info: reports: Initializing lbplugin BuildId: GlassFish 3.1 load-balancer plugin b05
    info: CORE5076: Using [Java HotSpot(TM) Server VM, Version 1.6.0_20] from [Sun Microsystems Inc.]
    config: , name-trans-passthrough reports: init-passthrough has not been called
    config: , name-trans-passthrough reports: init-passthrough has not been called
    config: , name-trans-passthrough reports: init-passthrough has not been called
    warning: reports: lb.configurator: XML_VALIDATOR_WARNING: Cookies will not be rewritten by web server. All cookie updates will be handled by application server. If you are using older version of application server, then failover will not work.
    warning: reports: lb.configurator: Preferred failover instance feature is enabled.
    warning: reports: lb.runtime: RNTM2019: Daemon http://linuxgf170:28080 has been intialized.
    warning: reports: lb.runtime: RNTM2019: Daemon https://linuxgf170:28181 has been intialized.
    warning: reports: lb.runtime: RNTM2019: Daemon http://linuxgf180:28080 has been intialized.
    warning: reports: lb.runtime: RNTM2019: Daemon https://linuxgf180:28181 has been intialized.
    warning: reports: lb.runtime: RNTM2019: Daemon http://linuxgf170:28081 has been intialized.
    warning: reports: lb.runtime: RNTM2019: Daemon https://linuxgf170:28182 has been intialized.
    info: HTTP3072: http-listener-1: http://linuxgf175:80 ready to accept requests
    info: HTTP3072: http-listener-ssl: https://linuxgf175:8090 ready to accept requests
    info: CORE3274: successful server startup
    [root@linuxgf175 bin]#

  • "Cluster is incorrectly configured on the virtual server." re-add server

    Took a server out of a pool, then later went to re-add. /OVS/ mounts fine on the server, but when I go to VM Mangler, it throws the following errors:
    "OVM-1011 Oracle VM Server sonorx3 operation HA Check Prerequisite failed: failed: <Exception: ha_check_shared_storage_mount failed: <Exception: srv('sonorx3'). failed! => <Exception: Cluster is incorrectly configured on the virtual server.> ."
    In /var/log/ovs-agent/ovs_operation.log on the host that fails to join, I see:
    "StackTrace:
    File "/opt/ovs-agent-2.2/OVSXHA.py", line 99, in check_shared_storage_mount
    raise Exception("Cluster is incorrectly configured on the virtual server.")"
    What step is missing here?

    I've tried re-doing ovs-makerepo.
    Google doesn't know anything about the problem (other than this thread here, which it has already indexed).
    What gives?

  • Problem with Server Pool

    Hello,
    I have an pool of physical servers at the company that supports the production environment of virtual servers.
    This pool have 4 (0, 1, 2 and 3) domain servers.
    I recently had a problem with the OVS-AGENT, and had to restart the whole pool.
    After that, all virtual servers I start at the pool, using the VM Manager, always start at the same domain server, the domain number 3.
    When I force the start using xm create, I can start the virtual server at domain server 0, 1 and 2 too.
    The live migration only works with the shell command (xm migrate -l), using the VM Manager simple do nothing.
    I try to force an especific virtual machine to run at an especific node, using Placement Policy at VM Manager, but when I try to start the server, this error occurs:
    Start - /OVS/running_pool/441_n_psgl04
    PowerOn Failed : Result - failed:errcode=20000, errmsg=No enough memory to run vm(/OVS/running_pool/441_n_psgl04), required memory=16384.
    StackTrace:
    File "/opt/ovs-agent-2.3/OVSSiteVM.py", line 124, in start_vm
    raise e
    Any idea what's happening? Is that some problem with the ovs-agent's database? How can I fix that with minimum of outage of the virtual servers?
    I'm really concerned about this problem because this weekend we had a stop on the network that caused the restart of the cluster, and when the servers came back, all virtual servers started up on the same physical server, which caused a lack of resources.
    Thanks for your help, and sorry about my poor english!

    843474 wrote:
    PowerOn Failed : Result - failed:errcode=20000, errmsg=No enough memory to run vm(/OVS/running_pool/441_n_psgl04), required memory=16384.You don't have enough memory on the target server to start this guest. So, you need to work out why you don't have enough memory or why Oracle VM Manager isn't seeing all your servers. Check to see if all the servers are listed as "Active" on the servers tab of Oracle VM Manager. Also, you can try and restore the ovs-agent database to the entire pool by clicking the "Restore" button on the Server Pools tab.

  • Distiller 8 Server issue on a Virtual Server

    We had distiller Server V8 running on a windows 2003 3 server and had no known problems.  We had that server virtualized and we are beginning to see an issue and wonder if it is related.  We have multiple watched folders receiving .ps files from two different sources.  We are seeing files from one one "in" source being distilled into the "out" folder of the other source, renamed the name of one of the files that should be in the other source.
    To explain..file named "a1.ps" from source "a", place in the "a" in folder is being renamed file "B1" and showing up in the "B" out folder.
    Is there an issue with Distiller Server 8 running on a Virtualized Server?

    HI,
    Oracle is provided two documents for OAS install in Solaris (32bit and 64bit).
    Here I am providing both documents.
    http://docs.oracle.com/cd/B31017_01/solx86.1013/install.pdf --- Oracle app server install 32bit
    http://docs.oracle.com/cd/B31017_01/sol.1013/install.pdf -- orcle app server install 64bit
    Award points it is useful.
    Thanks,
    satya

  • Can I install Adobe Connect version 8 on a virtual server?

    Hi everyone.  We are looking to upgrade our version of Adobe Connect and to put it on a virtual server.  Our current enviornment Adobe Connect v8 on a physical server.
    Is this possible?
    Is it supported?
    Has anyone done this and has experienced no problems?
    thank you in advance everyone.
    scott

    Hey Scott,
    Many customers today run Adobe Connect 8 virtually on WinSrv 2008 64-bit.  First make sure you read the page link below that details our tech specifications and that your server is compliant. 
    http://www.adobe.com/products/adobeconnect/tech-specs.html
    Also, you will want to discuss where your DB will reside (on that same virtual or a separate one).  The biggest improvement you will see is with performance.  The speed of the server alone is enough to upgrade.  Microsoft definitely made some improvements there...
    I am assuming you know all the usual WinSrv settings such as Domain, etc...so will not discuss those here..
    Regards,
    Scott@Adobe

  • Conversion from physical to virtual server

    Our server technology group wants to convert our physical
    server that contains the RoboEngine to a virtual server (using ESX
    VMware). We are using RoboHelp 5 to publish WebHelp to the
    RoboEngine. Has anyone else converted from a physical to a virtual
    server? If so, could you tell me about any problems you
    encountered?
    Thanks,
    Liz

    Hello Nelson, 
    There are quite lot of things in TMG which are dependent on Hardware.
    If you want to migrate from physical to virtual server, you can follow the steps here which are recommended/supported way of doing it.
    Though this article is for ISA to TMG migration, still you can follow the same steps for Physcial to Virtual migration.
    http://technet.microsoft.com/en-us/library/dd440994.aspx
    Please let us know, how it goes!

  • Virtual Server fails to compile JSP pages -repeat

    I'm running iWS 6.0 SP2 using jdk 1.3
    I have 4 virtual servers defined each serving out HTML pages and everything runs fine.
    I'm building a 5th VS and I need it to support JSPs and nothing works...
    I've turned on all the debugging and trace features I can find but, nothing helps me resolve the fact
    that the JSPC can not locate the index.jsp file.
    Below is a copy of the JSP1x error found in the errors file:
    [12/Aug/2002:18:19:27] info (14254): Service(): uri=/index.jsp cgiScriptName=/index.jsp token=null cached=false
    [12/Aug/2002:18:19:27] info (14254): Internal Info: loading servlet /index.jsp
    [12/Aug/2002:18:19:27] info (14254): JSP: This is a jsp 1.x file
    [12/Aug/2002:18:19:27] info (14254): JSP: Before JSP1x compiler.compile, servletName = /index.jsp servletPath = /bto/appl/netserver/PROD/BUSINESSWARE/public_html/index.jsp & dir = ../ClassCacheclasspath = ../ClassCache
    [12/Aug/2002:18:19:27] info (14254): JSP11 Log:Package name is: _jsps
    [12/Aug/2002:18:19:27] info (14254): JSP11 Log:Class file name is: /bto/appl/iplanet/servers/https-TE-Production/config/../ClassCache/_jsps/_index_jsp.class
    [12/Aug/2002:18:19:27] info (14254): JSP11 Log:Java file name is: /bto/appl/iplanet/servers/https-TE-Production/config/../ClassCache/_jsps/_index_jsp.java
    [12/Aug/2002:18:19:27] info (14254): JSP11 Log:Class name is: indexjsp
    [12/Aug/2002:18:19:27] info (14254): JSP: JSP1x compiler threw exception
    java.io.FileNotFoundException: /bto/appl/netserver/PROD/MBDB/public_html/index.jsp
    at org.apache.jasper.compiler.JspReader.pushFile(JspReader.java:187)
    at org.apache.jasper.compiler.JspReader.<init>(JspReader.java:253)
    at org.apache.jasper.compiler.JspReader.createJspReader(JspReader.java:259)
    at org.apache.jasper.compiler.Compiler.compile(Compiler.java:164)
    at com.iplanet.server.http.servlet.NSServletEntity.load(NSServletEntity.java:252)
    at com.iplanet.server.http.servlet.NSServletEntity.update(NSServletEntity.java:173)
    at com.iplanet.server.http.servlet.NSServletRunner.Service(NSServletRunner.java:416)
    [12/Aug/2002:18:19:27] warning (14254): Internal error: Failed to get GenericServlet. (uri=/index.jsp,SCRIPT_NAME=/index.jsp)
    Based on the above information I notice a few things that seem to not follow the documentation.
    First the JSPC is looking for a file in MBDB/html even thought the original index.jsp file is
    part of the BUSINESSWARE virtual machine
    Second the ClassCache files do not follow the documented naming convention
    jsps/VS id/uriid ...
    Thanks in advance for your assistance.

    Not related to the problem but you shouldn't really be using JDK 1.3 (use JDK 1.3.1 if you need to use JDK 1.3+). As for the problem, the problem seems to be you don't seem to be ling web application. Could you add a web application with context root as "/" for the virtual server and I am positive this problem should go away.

Maybe you are looking for