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

JMS exception when Weblogic 8 starts up

  1. MyEclipse Archived
    2.  > 
  2. Application Servers and Deployment
Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • December 9, 2004 at 9:08 am #220761 Reply

    rrosales
    Member

    Hi,

    When I start the Weblogib 8 server from MyEclipse I get JMS exceptions. I tried all I can think of to get rid of it but am having no success. When I run the startWeblogic.cmd directly the JMS exceptions do not occur. So it must be something with the startup facilities within MyEclipse that I am probably not setting. Could you please help me with this? Or is it something else??

    Thanks,
    Roy

    Here is the console output:

    <Dec 9, 2004 9:03:14 AM CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.4.2_04-b05 from Sun Microsystems Inc.>
    <Dec 9, 2004 9:03:14 AM CST> <Info> <Configuration Management> <BEA-150016> <This server is being started as the administration server.>
    <Dec 9, 2004 9:03:14 AM CST> <Info> <Management> <BEA-141107> <Version: WebLogic XMLX Module 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic Server 8.1 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic Server 8.1 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic Server 8.1 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic Server 8.1 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973 >
    <Dec 9, 2004 9:03:15 AM CST> <Notice> <Management> <BEA-140005> <Loading domain configuration from configuration repository at C:\bea\user_projects\domains\mydomain\config.xml.>
    <Dec 9, 2004 9:03:20 AM CST> <Notice> <Log Management> <BEA-170019> <The server log file C:\bea\user_projects\domains\mydomain\myserver\myserver.log is opened. All server side log events will be written to this file.>
    <Dec 9, 2004 9:03:23 AM CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Dec 9, 2004 9:03:23 AM CST> <Notice> <WebLogicServer> <BEA-000327> <Starting WebLogic Admin Server “myserver” for domain “mydomain”>
    <Dec 9, 2004 9:03:33 AM CST> <Error> <JMS> <BEA-040368> <The following exception has occurred:

    java.lang.InstantiationError: weblogic.jms.common.DestinationImpl
    at weblogic.jms.backend.BEDestination.initialize(BEDestination.java:761)
    at weblogic.jms.backend.BEDestination.initialize(BEDestination.java:301)
    at weblogic.jms.backend.BackEnd.createDestination(BackEnd.java:1949)
    at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:667)
    at weblogic.jms.JMSService.addJMSServer(JMSService.java:2228)
    at weblogic.jms.JMSService.addDeployment(JMSService.java:2012)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:331)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:591)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:569)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:731)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:710)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:484)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:985)
    at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:943)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
    at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
    at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7351)
    at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
    at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
    at weblogic.Server.main(Server.java:32)
    >
    <Dec 9, 2004 9:03:33 AM CST> <Error> <JMS> <BEA-040122> <Failed to deploy JMS Server “WSStoreForwardInternalJMSServermyserver” due to weblogic.jms.common.JMSException: Error initializing JMSServer WSStoreForwardInternalJMSServermyserver.
    weblogic.jms.common.JMSException: Error initializing JMSServer WSStoreForwardInternalJMSServermyserver
    at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:754)
    at weblogic.jms.JMSService.addJMSServer(JMSService.java:2228)
    at weblogic.jms.JMSService.addDeployment(JMSService.java:2012)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:331)
    at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:591)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:569)
    at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:241)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:731)
    at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:710)
    at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:484)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1557)
    at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1525)
    at weblogic.management.internal.RemoteMBeanServerImpl.private_invoke(RemoteMBeanServerImpl.java:985)
    at weblogic.management.internal.RemoteMBeanServerImpl.invoke(RemoteMBeanServerImpl.java:943)
    at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:946)
    at weblogic.management.internal.MBeanProxy.invokeForCachingStub(MBeanProxy.java:481)
    at weblogic.management.configuration.ServerMBean_Stub.updateDeployments(ServerMBean_Stub.java:7351)
    at weblogic.management.deploy.slave.SlaveDeployer.updateServerDeployments(SlaveDeployer.java:1304)
    at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:347)
    at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
    at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
    at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
    at weblogic.Server.main(Server.java:32)
    Caused by: java.lang.InstantiationError: weblogic.jms.common.DestinationImpl
    at weblogic.jms.backend.BEDestination.initialize(BEDestination.java:761)
    at weblogic.jms.backend.BEDestination.initialize(BEDestination.java:301)
    at weblogic.jms.backend.BackEnd.createDestination(BackEnd.java:1949)
    at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:667)
    … 27 more
    >
    DEBUG:FileUtil:Thu Dec 09 09:03:55 CST 2004:Load SysEnvConfig.propertiesfrom classpath
    DEBUG:FileUtil:::Thu Dec 09 09:03:55 CST 2004:trying to Load SysEnvConfig.propertiesfrom com.ual.env dir
    [INFO] Loading validation rules file from ‘/WEB-INF/validator-rules.xml’ <org.apache.struts.validator.ValidatorPlugIn:initResources> <2004-12-09 09:03:57,655> <main>
    [INFO] Loading validation rules file from ‘/WEB-INF/validation.xml’ <org.apache.struts.validator.ValidatorPlugIn:initResources> <2004-12-09 09:03:57,670> <main>
    [INFO] Loading validation rules file from ‘/WEB-INF/validation-purchase.xml’ <org.apache.struts.validator.ValidatorPlugIn:initResources> <2004-12-09 09:03:57,670> <main>
    [INFO] Tiles definition factory loaded for module ”. <org.apache.struts.tiles.TilesPlugin:initDefinitionsFactory> <2004-12-09 09:03:58,577> <main>
    [INFO] Loading validation rules file from ‘/WEB-INF/validator-rules.xml’ <org.apache.struts.validator.ValidatorPlugIn:initResources> <2004-12-09 09:03:58,702> <main>
    [INFO] Loading validation rules file from ‘/WEB-INF/validation.xml’ <org.apache.struts.validator.ValidatorPlugIn:initResources> <2004-12-09 09:03:58,702> <main>
    [INFO] Loading validation rules file from ‘/WEB-INF/validation-purchase.xml’ <org.apache.struts.validator.ValidatorPlugIn:initResources> <2004-12-09 09:03:58,702> <main>
    [INFO] Factory already exists for module ‘/secure’. The factory found is from module ”. No new creation. <org.apache.struts.tiles.TilesPlugin:initDefinitionsFactory> <2004-12-09 09:03:58,983> <main>
    <Dec 9, 2004 9:03:59 AM CST> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server “myserver” for domain “mydomain” running in Development Mode>
    <Dec 9, 2004 9:03:59 AM CST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    <Dec 9, 2004 9:03:59 AM CST> <Notice> <WebLogicServer> <BEA-000355> <Thread “ListenThread.Default” listening on port 7001, ip address *.*>

    December 9, 2004 at 10:15 am #220765 Reply

    Scott Anderson
    Participant

    Roy,

    It’s likely that your startup script has been modified to add additional libraries. Please open it and check the line that looks like:
    <pre>
    set CLASSPATH=%JAVA_HOME%\lib\tools.jar;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar;%CLASSPATH%
    </pre>

    The MyEclipse connector uses this same setup by default. If yours is different and contains addtional libraries you’ll need to add them to the classpath that the connector uses. Information on how to do that is located in the Application Server Quickstart, available in the Documentation section here:
    http://www.myeclipseide.com/ContentExpress-display-ceid-67.html

  • Author
    Posts
Viewing 2 posts - 1 through 2 (of 2 total)
Reply To: JMS exception when Weblogic 8 starts up

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