facebook
  1. MyEclipse Archived
    2.  > 
  2. Application Servers and Deployment

Problem configuring myeclipse App servers

  1. MyEclipse Archived
    2.  > 
  2. Application Servers and Deployment
Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • February 24, 2006 at 4:55 pm #247330 Reply

    rahulgup
    Member

    Hi,
    I have Sun Java System Application Server 8.2 installed and am trying to use myeclipse to start/stop/deploy on the server. I am using myeclipse 4.0. I have set the server root directory and everything. When trying to start the server from within myeclipse, I get a lot of NullPointerExceptions. What could be the problem?

    I also tried the same with WebLogic 9.1. That also gives errors and am not able to deploy web application from eclipse. The list of application servers in myeclipse shows Sun App Server 8.1 and WebLogic 9. Could the server versions be an issue?

    I will appreciate your help as I am new to myeclipse and am stuck.

    Thanks.

    February 24, 2006 at 5:53 pm #247334 Reply

    Riyad Kalla
    Member

    Can you paste the result of MyEclipse > About > Configuration Summary for us?

    February 24, 2006 at 7:39 pm #247345 Reply

    rahulgup
    Member

    Configuration summary is pasted below:

    ——————————————————————————————–
    *** Date: Fri Feb 24 19:34:50 GMT-06:00 2006

    *** System properties:
    OS=WindowsXP
    OS version=5.1
    Java version=1.5.0_04

    *** MyEclipse details:
    MyEclipse Enterprise Workbench

    Version: 4.1.0 GA
    Build id: 20060122-4.1-GA

    *** Eclipse details:
    Eclipse SDK

    Version: 3.1.0
    Build id: I20050627-1435

    Eclipse Platform

    Version: 3.1.0
    Build id: I20050627-1435

    Eclipse RCP

    Version: 3.1.0
    Build id: I20050627-1435

    Eclipse Java Development Tools

    Version: 3.1.0
    Build id: I20050627-1435

    Eclipse Plug-in Development Environment

    Version: 3.1.0
    Build id: I20050627-1435

    Eclipse Project SDK

    Version: 3.1.0
    Build id: I20050627-1435

    Eclipse startup command=-os
    win32
    -ws
    win32
    -arch
    x86
    -launcher
    C:\Documents and Settings\Rahul Gupta\Desktop\JAVA\eclipse\eclipse.exe
    -name
    Eclipse
    -showsplash
    600
    -exitdata
    42c_60
    -vm
    C:\WINDOWS\system32\javaw.exe
    ——————————————————————————————–

    February 24, 2006 at 9:21 pm #247346 Reply

    Riyad Kalla
    Member

    Can you paste the exceptions you are getting for Sun App Server? and separately for WL 9.1?

    February 25, 2006 at 9:57 am #247359 Reply

    rahulgup
    Member

    Sun App server gives out the following error:

    —————————————————-
    [#|2006-02-25T09:44:47.156-0600|WARNING|sun-appserver-pe8.2|javax.enterprise.system.stream.err|_ThreadID=10;|java.util.logging.ErrorManager: 0: Error In Setting Initial Loglevel|#]

    [#|2006-02-25T09:44:47.234-0600|WARNING|sun-appserver-pe8.2|javax.enterprise.system.stream.err|_ThreadID=10;|
    java.lang.NullPointerException
    at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigModel(ServerBeansFactory.java:59)
    at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigBean(ServerBeansFactory.java:96)
    at com.sun.enterprise.server.logging.ServerLogManager.getConfiguredLogLevel(ServerLogManager.java:391)
    at com.sun.enterprise.server.logging.ServerLogManager$1.run(ServerLogManager.java:117)
    at java.security.AccessController.doPrivileged(Native Method)
    at com.sun.enterprise.server.logging.ServerLogManager.internalInitializeLogger(ServerLogManager.java:98)
    at com.sun.enterprise.server.logging.ServerLogManager.initializeLogger(ServerLogManager.java:88)
    at com.sun.enterprise.server.logging.BaseLogManager.doInitializeLogger(BaseLogManager.java:108)
    at com.sun.enterprise.server.logging.BaseLogManager.addLogger(BaseLogManager.java:157)
    at java.util.logging.Logger.getLogger(Logger.java:231)
    at sun.rmi.runtime.Log$LoggerLogFactory.createLog(Log.java:154)
    at sun.rmi.runtime.Log.getLog(Log.java:121)
    at sun.rmi.server.UnicastRef.<clinit>(UnicastRef.java:39)
    at java.rmi.server.RemoteServer.<clinit>(RemoteServer.java:97)
    at com.sun.enterprise.admin.server.core.channel.AdminChannel.createServerObject(AdminChannel.java:216)
    at com.sun.enterprise.admin.server.core.channel.AdminChannel.createRMIChannel(AdminChannel.java:74)
    at com.sun.enterprise.admin.server.core.AdminChannelLifecycle.onInitialization(AdminChannelLifecycle.java:43)
    at com.sun.enterprise.server.ss.ASLazyKernel.initializeAdminService(ASLazyKernel.java:134)
    at com.sun.enterprise.server.ss.ASLazyKernel.startASSocketServices(ASLazyKernel.java:51)
    at com.sun.enterprise.server.PEMain.run(PEMain.java:274)
    at com.sun.enterprise.server.PEMain.main(PEMain.java:220)
    |#]

    [#|2006-02-25T09:44:47.250-0600|WARNING|sun-appserver-pe8.2|javax.enterprise.system.stream.err|_ThreadID=10;|
    at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigModel(ServerBeansFactory.java:59)|#]

    [#|2006-02-25T09:44:47.250-0600|WARNING|sun-appserver-pe8.2|javax.enterprise.system.stream.err|_ThreadID=10;|
    at com.sun.enterprise.config.serverbeans.ServerBeansFactory.getConfigBean(ServerBeansFactory.java:96)|#]

    [#|2006-02-25T09:44:47.296-0600|WARNING|sun-appserver-pe8.2|javax.enterprise.system.stream.err|_ThreadID=10;|
    at com.sun.enterprise.server.logging.ServerLogManager.getConfiguredLogLevel(ServerLogManager.java:391)|#]

    [#|2006-02-25T09:44:47.296-0600|WARNING|sun-appserver-pe8.2|javax.enterprise.system.stream.err|_ThreadID=10;|
    at com.sun.enterprise.server.logging.ServerLogManager$1.run(ServerLogManager.java:117)|#]

    [#|2006-02-25T09:44:47.312-0600|WARNING|sun-appserver-pe8.2|javax.enterprise.system.stream.err|_ThreadID=10;|
    at java.security.AccessController.doPrivileged(Native Method)|#]

    [#|2006-02-25T09:44:47.312-0600|WARNING|sun-appserver-pe8.2|javax.enterprise.system.stream.err|_ThreadID=10;|
    at com.sun.enterprise.server.logging.ServerLogManager.internalInitializeLogger(ServerLogManager.java:98)|#]

    [#|2006-02-25T09:44:47.328-0600|WARNING|sun-appserver-pe8.2|javax.enterprise.system.stream.err|_ThreadID=10;|
    at com.sun.enterprise.server.logging.ServerLogManager.initializeLogger(ServerLogManager.java:88)|#]

    [#|2006-02-25T09:44:47.359-0600|WARNING|sun-appserver-pe8.2|javax.enterprise.system.stream.err|_ThreadID=10;|
    at com.sun.enterprise.server.logging.BaseLogManager.doInitializeLogger(BaseLogManager.java:108)|#]

    [#|2006-02-25T09:44:47.359-0600|WARNING|sun-appserver-pe8.2|javax.enterprise.system.stream.err|_ThreadID=10;|
    at com.sun.enterprise.server.logging.BaseLogManager.addLogger(BaseLogManager.java:157)|#]

    ————————————————————–


    I was able to get the Weblogic 9.1 server to start and stop using from myeclipse. The problem was that it uses some instrumentation classes defined in JDK 1.5 and I was using JDK 1.4.3. However, looks like it does not start the PointBase database server along with the app server. Following is the entire trace log during startup:

    ——————————-
    <Feb 25, 2006 9:54:04 AM GMT-06:00> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.5.0_04-b05 from Sun Microsystems Inc.>
    <Feb 25, 2006 9:54:06 AM GMT-06:00> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.1 Mon Dec 12 19:26:33 EST 2005 689178 >
    <Feb 25, 2006 9:54:10 AM GMT-06:00> <Info> <WebLogicServer> <BEA-000215> <Loaded License : C:\BEA\license.bea>
    <Feb 25, 2006 9:54:10 AM GMT-06:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Feb 25, 2006 9:54:10 AM GMT-06:00> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <Feb 25, 2006 9:54:10 AM GMT-06:00> <Notice> <Log Management> <BEA-170019> <The server log file C:\BEA\weblogic91\samples\domains\wl_server\servers\examplesServer\logs\examplesServer.log is opened. All server side log events will be written to this file.>
    <Feb 25, 2006 9:54:12 AM GMT-06:00> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Feb 25, 2006 9:54:15 AM GMT-06:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
    <Feb 25, 2006 9:54:15 AM GMT-06:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Feb 25, 2006 9:54:17 AM GMT-06:00> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool “examples-demo”: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9092.>
    <Feb 25, 2006 9:54:18 AM GMT-06:00> <Error> <Deployer> <BEA-149205> <Failed to initialize the application ‘examples-demo’ due to error weblogic.application.ModuleException: .
    weblogic.application.ModuleException:
    at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:257)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
    Truncated. see log file for complete stacktrace
    weblogic.common.ResourceException: weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9092.
    at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:238)
    at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1049)
    at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:977)
    at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:207)
    at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1135)
    Truncated. see log file for complete stacktrace
    >
    <Feb 25, 2006 9:54:20 AM GMT-06:00> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool “examples-demoXA”: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9092.>
    <Feb 25, 2006 9:54:23 AM GMT-06:00> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool “examples-demoXA”: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9092.>
    <Feb 25, 2006 9:54:24 AM GMT-06:00> <Error> <Deployer> <BEA-149205> <Failed to initialize the application ‘examples-demoXA’ due to error weblogic.application.ModuleException: .
    weblogic.application.ModuleException:
    at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:257)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
    Truncated. see log file for complete stacktrace
    weblogic.common.ResourceException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9092.
    at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:166)
    at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1049)
    at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:977)
    at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:207)
    at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1135)
    Truncated. see log file for complete stacktrace
    >
    <Feb 25, 2006 9:54:26 AM GMT-06:00> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool “examples-demoXA-2”: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9092.>
    <Feb 25, 2006 9:54:27 AM GMT-06:00> <Error> <Deployer> <BEA-149205> <Failed to initialize the application ‘examples-demoXA-2’ due to error weblogic.application.ModuleException: .
    weblogic.application.ModuleException:
    at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:257)
    at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:90)
    at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:318)
    at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
    at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:53)
    Truncated. see log file for complete stacktrace
    weblogic.common.ResourceException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9092.
    at weblogic.jdbc.common.internal.XAConnectionEnvFactory.createResource(XAConnectionEnvFactory.java:166)
    at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1049)
    at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:977)
    at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:207)
    at weblogic.jdbc.common.internal.ConnectionPool.doStart(ConnectionPool.java:1135)
    Truncated. see log file for complete stacktrace
    >
    <Feb 25, 2006 9:54:28 AM GMT-06:00> <Error> <Store> <BEA-280061> <The persistent store “exampleJDBCStore” could not be deployed: weblogic.store.PersistentStoreException: Can’t find JDBC DataSource examples-dataSource-demoPool: javax.naming.NameNotFoundException: Unable to resolve ‘examples-dataSource-demoPool’. Resolved ”; remaining name ‘examples-dataSource-demoPool’
    weblogic.store.PersistentStoreException: Can’t find JDBC DataSource examples-dataSource-demoPool: javax.naming.NameNotFoundException: Unable to resolve ‘examples-dataSource-demoPool’. Resolved ”; remaining name ‘examples-dataSource-demoPool’
    at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:105)
    at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:184)
    at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:162)
    at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:57)
    at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:235)
    Truncated. see log file for complete stacktrace
    javax.naming.NameNotFoundException: Unable to resolve ‘examples-dataSource-demoPool’. Resolved ”; remaining name ‘examples-dataSource-demoPool’
    at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1123)
    at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:250)
    at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:204)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:267)
    Truncated. see log file for complete stacktrace
    >
    <Feb 25, 2006 9:54:28 AM GMT-06:00> <Warning> <Management> <BEA-141197> <The deployment of exampleJDBCStore failed.
    weblogic.management.DeploymentException:
    at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:60)
    at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:235)
    at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:133)
    at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:596)
    at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:457)
    Truncated. see log file for complete stacktrace
    javax.naming.NameNotFoundException: Unable to resolve ‘examples-dataSource-demoPool’. Resolved ”; remaining name ‘examples-dataSource-demoPool’
    at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1123)
    at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:250)
    at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
    at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:204)
    at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:267)
    Truncated. see log file for complete stacktrace
    >
    <Feb 25, 2006 9:54:28 AM GMT-06:00> <Error> <JMS> <BEA-040123> <Failed to start JMS Server “examplesJMSServer” due to weblogic.management.DeploymentException: The persistent store “exampleJDBCStore” does not exist.
    weblogic.management.DeploymentException: The persistent store “exampleJDBCStore” does not exist
    at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:272)
    at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:173)
    at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:235)
    at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:133)
    at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:596)
    Truncated. see log file for complete stacktrace
    >
    <Feb 25, 2006 9:54:28 AM GMT-06:00> <Warning> <Management> <BEA-141197> <The deployment of examplesJMSServer failed.
    weblogic.management.DeploymentException: Internalrror activating the JMS Server examplesJMSServer: weblogic.management.DeploymentException: The persistent store “exampleJDBCStore” does not exist
    at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:187)
    at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:235)
    at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:133)
    at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:596)
    at weblogic.management.internal.DeploymentHandlerHome.activateInitialDeployments(DeploymentHandlerHome.java:457)
    Truncated. see log file for complete stacktrace
    weblogic.management.DeploymentException: The persistent store “exampleJDBCStore” does not exist
    at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:272)
    at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:173)
    at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:235)
    at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:133)
    at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:596)
    Truncated. see log file for complete stacktrace
    >
    <Feb 25, 2006 9:54:28 AM GMT-06:00> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application ‘examples-jms’.
    weblogic.application.ModuleException: ERROR: Could not activate examples-jms!exampleQueue
    at weblogic.jms.backend.BEDestinationRuntimeDelegate.activate(BEDestinationRuntimeDelegate.java:238)
    at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1704)
    at weblogic.jms.module.JMSModule$EntityState.setState(JMSModule.java:1654)
    at weblogic.jms.module.JMSModule$EntityState.access$100(JMSModule.java:1595)
    at weblogic.jms.module.JMSModule.activate(JMSModule.java:340)
    Truncated. see log file for complete stacktrace
    weblogic.messaging.kernel.KernelException: The Messaging Kernel examplesJMSServer has not yet been opened
    at weblogic.messaging.kernel.internal.KernelImpl.checkOpened(KernelImpl.java:191)
    at weblogic.messaging.kernel.internal.DestinationImpl.activate(DestinationImpl.java:279)
    at weblogic.messaging.kernel.internal.QueueImpl.activate(QueueImpl.java:1520)
    at weblogic.messaging.kernel.internal.DestinationImpl.resume(DestinationImpl.java:263)
    at weblogic.messaging.kernel.internal.QueueImpl.resume(QueueImpl.java:1689)
    Truncated. see log file for complete stacktrace
    >

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    After the server has booted, your browser should
    automatically launch and point to the
    BEA WebLogic Server Samples Introduction Page
    running on this server. If your browser fails to launch,
    point your browser to the following URL:
    “http://68.117.136.242:7001/examplesWebApp/index.jsp&#8221;
    Note: On Unix-based systems, browser defaults to Netscape.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    <Feb 25, 2006 9:54:38 AM GMT-06:00> <Notice> <Log Management> <BEA-170027> <The server initialized the domain log broadcaster successfully. Log messages will now be broadcasted to the domain log.>
    <Feb 25, 2006 9:54:38 AM GMT-06:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
    <Feb 25, 2006 9:54:38 AM GMT-06:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
    <Feb 25, 2006 9:54:40 AM GMT-06:00> <Notice> <Security> <BEA-090171> <Loading the identity certificate and private key stored under the alias DemoIdentity from the jks keystore file C:\BEA\weblogic91\server\lib\DemoIdentity.jks.>
    <Feb 25, 2006 9:54:40 AM GMT-06:00> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\BEA\weblogic91\server\lib\DemoTrust.jks.>
    <Feb 25, 2006 9:54:40 AM GMT-06:00> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\BEA\jdk150_04\jre\lib\security\cacerts.>
    <Feb 25, 2006 9:54:40 AM GMT-06:00> <Notice> <Server> <BEA-002613> <Channel “Default[1]” is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, http.>
    <Feb 25, 2006 9:54:40 AM GMT-06:00> <Notice> <Server> <BEA-002613> <Channel “DefaultSecure” is now listening on 68.117.136.242:7002 for protocols iiops, t3s, ldaps, https.>
    <Feb 25, 2006 9:54:40 AM GMT-06:00> <Notice> <Server> <BEA-002613> <Channel “Default” is now listening on 68.117.136.242:7001 for protocols iiop, t3, ldap, http.>
    <Feb 25, 2006 9:54:40 AM GMT-06:00> <Notice> <Server> <BEA-002613> <Channel “DefaultSecure[1]” is now listening on 127.0.0.1:7002 for protocols iiops, t3s, ldaps, https.>
    <Feb 25, 2006 9:54:40 AM GMT-06:00> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server “examplesServer” for domain “wl_server” running in Development Mode>
    <Feb 25, 2006 9:54:40 AM GMT-06:00> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
    <Feb 25, 2006 9:54:40 AM GMT-06:00> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    ————————————————

    February 25, 2006 at 11:32 am #247366 Reply

    Riyad Kalla
    Member

    Do you need to start pointbase externally first?

    As far as Sun APp Server, I just installed version 8.2 right now, set it up using the Sun App Server 8.1 connector and started it and it started up fine:

    [#|2006-02-25T10:31:25.608-0700|INFO|sun-appserver-pe8.2|javax.enterprise.resource.jms|_ThreadID=10;|JMS5023: JMS service successfully started. Instance Name = imqbroker, Home = [D:\Java\sunappserver-8.2\imq\bin].|#]

    [#|2006-02-25T10:31:25.608-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|CORE5098: AS Socket Service Initialization has been completed.|#]

    [#|2006-02-25T10:31:26.280-0700|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-02-25T10:31:26.280-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM0001:MBeanServer initialized successfully|#]

    [#|2006-02-25T10:31:26.843-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.security|_ThreadID=10;|SEC1143: Loading policy provider com.sun.enterprise.security.provider.PolicyWrapper.|#]

    [#|2006-02-25T10:31:27.436-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server server|#]

    [#|2006-02-25T10:31:27.452-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Created virtual server __asadmin|#]

    [#|2006-02-25T10:31:28.421-0700|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-02-25T10:31:28.421-0700|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-02-25T10:31:28.421-0700|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-02-25T10:31:29.311-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.transaction|_ThreadID=10;|JTS5014: Recoverable JTS instance, serverId = [3700]|#]

    [#|2006-02-25T10:31:33.452-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1079: Initialization of AMX MBeans successful|#]

    [#|2006-02-25T10:31:33.843-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Selecting file D:\Java\sunappserver-8.2\lib\install\applications\MEjbApp.ear for autodeployment.|#]

    [#|2006-02-25T10:31:34.530-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC – START of EJBC for [MEjbApp]|#]

    [#|2006-02-25T10:31:34.546-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans …|#]

    [#|2006-02-25T10:31:34.577-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC – END of EJBC for [MEjbApp]|#]

    [#|2006-02-25T10:31:34.796-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 813 msec, Total EJB Compiler Module Time: 47 msec, Portion spent EJB Compiling: 5%
    Breakdown of EJBC Module Time: Total Time for EJBC: 47 msec, CMP Generation: 0 msec (0%), Java Compilation: 0 msec (0%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 31 msec (65%),
    |#]

    [#|2006-02-25T10:31:34.905-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = MEjbApp|#]

    [#|2006-02-25T10:31:35.030-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent — reference-added MEjbApp]|#]

    [#|2006-02-25T10:31:35.139-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]

    [#|2006-02-25T10:31:35.171-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent — deploy MEjbApp]|#]

    [#|2006-02-25T10:31:35.624-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: MEJBBean; containerId: 74769281487798272|#]

    [#|2006-02-25T10:31:35.796-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [MEjbApp] loaded successfully!|#]

    [#|2006-02-25T10:31:35.796-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]

    [#|2006-02-25T10:31:35.811-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : D:\Java\sunappserver-8.2\lib\install\applications\MEjbApp.ear.|#]

    [#|2006-02-25T10:31:35.811-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Selecting file D:\Java\sunappserver-8.2\lib\install\applications\__ejb_container_timer_app.ear for autodeployment.|#]

    [#|2006-02-25T10:31:36.030-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5109: EJBC – START of EJBC for [__ejb_container_timer_app]|#]

    [#|2006-02-25T10:31:39.124-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|Processing beans …|#]

    [#|2006-02-25T10:31:39.124-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|DPL5110: EJBC – END of EJBC for [__ejb_container_timer_app]|#]

    [#|2006-02-25T10:31:39.202-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|Total Deployment Time: 3359 msec, Total EJB Compiler Module Time: 3094 msec, Portion spent EJB Compiling: 92%
    Breakdown of EJBC Module Time: Total Time for EJBC: 3094 msec, CMP Generation: 844 msec (27%), Java Compilation: 2172 msec (70%), RMI Compilation: 0 msec (0%), JAX-RPC Generation: 0 msec (0%),
    |#]

    [#|2006-02-25T10:31:39.264-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|deployed with moduleid = __ejb_container_timer_app|#]

    [#|2006-02-25T10:31:39.343-0700|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]|#]

    [#|2006-02-25T10:31:39.405-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]

    [#|2006-02-25T10:31:39.436-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1041:Sent the event to instance:[ApplicationDeployEvent — deploy __ejb_container_timer_app]|#]

    [#|2006-02-25T10:31:39.608-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|Instantiated container for: ejbName: TimerBean; containerId: 74769281785790464|#]

    [#|2006-02-25T10:31:40.061-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.ejb|_ThreadID=10;|EJB5109:EJB Timer Service started successfully for datasource [jdbc/__TimerPool]|#]

    [#|2006-02-25T10:31:40.061-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.core.classloading|_ThreadID=10;|LDR5010: All ejb(s) of [__ejb_container_timer_app] loaded successfully!|#]

    [#|2006-02-25T10:31:40.061-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1042:Status of dynamic reconfiguration event processing:[success]|#]

    [#|2006-02-25T10:31:40.061-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.deployment|_ThreadID=10;|[AutoDeploy] Successfully autodeployed : D:\Java\sunappserver-8.2\lib\install\applications\__ejb_container_timer_app.ear.|#]

    [#|2006-02-25T10:31:40.077-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0302: Starting Sun-Java-System/Application-Server.|#]

    [#|2006-02-25T10:31:40.155-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [__default-admingui] in virtual server [__asadmin] at [/]|#]

    [#|2006-02-25T10:31:40.233-0700|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-02-25T10:31:40.343-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [adminapp] in virtual server [__asadmin] at [/web1]|#]

    [#|2006-02-25T10:31:40.374-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|WEB0100: Loading web module [admingui] in virtual server [__asadmin] at [/asadmin]|#]

    [#|2006-02-25T10:31:40.374-0700|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-02-25T10:31:40.389-0700|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-02-25T10:31:40.577-0700|INFO|sun-appserver-pe8.2|org.apache.catalina.core.StandardEngine|_ThreadID=10;|Starting Servlet Engine: Sun-Java-System/Application-Server|#]

    [#|2006-02-25T10:31:42.452-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Non-Blocking Mode|#]

    [#|2006-02-25T10:31:42.452-0700|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-02-25T10:31:42.499-0700|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-02-25T10:31:42.608-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Blocking Mode|#]

    [#|2006-02-25T10:31:42.608-0700|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-02-25T10:31:42.608-0700|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-02-25T10:31:42.671-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.container.web|_ThreadID=10;|Initializing Grizzly Non-Blocking Mode|#]

    [#|2006-02-25T10:31:42.671-0700|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-02-25T10:31:42.671-0700|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-02-25T10:31:42.952-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1504: Here is the JMXServiceURL for the Standard JMXConnectorServer: [service:jmx:rmi:///jndi/rmi://rsk:8686/jmxrmi]. This is where the remote administrative clients should connect using the standard JMX connectors|#]

    [#|2006-02-25T10:31:42.952-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.tools.admin|_ThreadID=10;|ADM1506: Status of Standard JMX Connector: Active = [true]|#]

    [#|2006-02-25T10:31:42.999-0700|INFO|sun-appserver-pe8.2|javax.enterprise.system.core|_ThreadID=10;|Application server startup complete.|#]

    SO there could be something wrong with your Sun APp Server install, try installing it again to another directory clean and try that.

  • Author
    Posts
Viewing 6 posts - 1 through 6 (of 6 total)
Reply To: Problem configuring myeclipse App servers

You must be logged in to post in the forum log in