Administrative console not openning - Websphere

This is a discussion on Administrative console not openning - Websphere ; Map modules to application servers' I selected the new server. After that the Admin Console is not openning. From the systemout.log I found the following message 'Servlet Request Processor Exception: Virtual Host/WebGroup Not Found : The web group /admin has ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: Administrative console not openning

  1. Administrative console not openning

    Map modules to application servers' I selected the new server. After that the Admin Console is not openning. From the systemout.log I found the following message
    'Servlet Request Processor Exception: Virtual Host/WebGroup Not Found : The web group /admin has not been defined'

    Can anybody please help me.

    Thanks

  2. Re: Administrative console not openning

    shainv@gmail.com wrote:
    > Map modules to application servers' I selected the new server. After that the Admin Console is not openning. From the systemout.log I found the following message
    > 'Servlet Request Processor Exception: Virtual Host/WebGroup Not Found : The web group /admin has not been defined'
    >
    > Can anybody please help me.
    >
    > Thanks
    >

    What version of WebSphere? What new server? is this ND? What application
    did you map?
    Ken

  3. Re: Administrative console not openning

    What port are you using? What does your virtualhosts.xml look like? I believe it is under config/cells/cellname

  4. Re: Administrative console not openning

    Hello mmolden ,

    Thanks for your reply,
    I am using the port 9081
    I checked the virtualhosts.xml file and I found the following lines.


    .....









    .....






    I found from the Systemout.log file of 'server2' the following errors.

    1. "The operation on the context "java:comp/env/jdbc" cannot be completed. All contexts under java:comp/env are environment contexts and are read-only.
    [10/23/08 10:52:38:568 IST] 4910b538 Helpers W NMSV0610I: A NamingException is being thrown from a javax.naming.Context implementation. Details follow:
    Context implementation: com.ibm.ws.naming.java.javaURLContextRoot
    Context method: createSubcontext(Name)
    Context name: java:
    Target name: comp/env/jdbc
    Other data:
    Exception stack trace: javax.naming.OperationNotSupportedException: The operation on the context "java:comp/env/jdbc" cannot be completed. All contexts under java:comp/env are environment contexts and are read-only."

    2. " Error encountered binding the J2EE resource, soms, as java:comp/env/jdbc/somsOra from file://C:\Program Files\WebSphere\AppServer\config/cells/valglob0-0345/nodes/valglob0-0345/resources.xml
    javax.naming.OperationNotSupportedException: The operation on the context "java:comp/env/jdbc" cannot be completed. All contexts under java:comp/env are environment contexts and are read-only."

    3. "Failed to load KeyLocator SampleSenderEncryptionKeyLocator. The exception is java.lang.ExceptionInInitializerError: java.lang.SecurityException: Cannot set up certs for trusted CAs"

    ************************************************** **********
    in bundle com.ibm.ejs.resources.seriousMessages
    [10/23/08 10:53:34:301 IST] 4910b538 TraceNLS u No message text associated with key argument.number.too.large.at. in bundle com.ibm.ejs.resources.seriousMessages
    [10/23/08 10:53:34:301 IST] 4910b538 WebAppServlet E argument number too large at
    [10/23/08 10:53:34:332 IST] 4910b538 ApplicationMg A WSVR0221I: Application started: app1
    [10/23/08 10:53:37:442 IST] 4910b538 HttpTransport A SRVE0171I: Transport https is listening on port 9,081.
    [10/23/08 10:53:37:910 IST] 4910b538 RMIConnectorC A ADMC0026I: RMI Connector available at port 2815
    [10/23/08 10:53:38:160 IST] 4910b538 WsServer A WSVR0002I: Server server2 open for e-business, problems occurred during startup

+ Reply to Thread