Weblogic.management.ApplicationException in Enterprise Application?

Hi guys,
I deployed one Enterprise Application in weblogic server 8.1. It shows the following Exception..
Exception:weblogic.management.ApplicationException: activate failed for jasmine.jar Module: jasmine.jar Error: Exception activating module: EJBModule(jasmine.jar,status=PREPARED) Unable to deploy EJB: ProductBean from jasmine.jar:
[EJB:011020]The database table: products does not contain the columns: orderLineItemID. Please consult your database mappings in the weblogic-cmp-rdbms.xml deployment descriptor and ensure these match your database schema.
Database Table are follows.
create table products (productID varchar(64), name varchar(64), basePrice numeric(18), description varchar(64));
create table orderLineItems( orderLineItemID varchar(64),productID varchar(64), orderID varchar(64),quantity int, discount numeric(18));
<u><b>weblogic-cmp-rdbms-jar.xml file</b></u>
<weblogic-rdbms-relation>
<relation-name>OrderBean_customer-CustomerBean</relation-name>
<weblogic-relationship-role>
<relationship-role-name>CustomerBean_null-Has-OrderBean_customer</relationship-role-name>
<relationship-role-map>
<column-map>
<foreign-key-column>OrderBean_orderID</foreign-key-column>
<key-column>orderID</key-column>
</column-map>
</relationship-role-map>
</weblogic-relationship-role>
</weblogic-rdbms-relation>
<weblogic-rdbms-relation>
<relation-name>OrderLineItemBean_order-OrderBean</relation-name>
<weblogic-relationship-role>
<relationship-role-name>OrderBean_null-Has-OrderLineItemBean_order</relationship-role-name>
<relationship-role-map>
<column-map>
<foreign-key-column>OrderLineItemBean_orderLineItemID</foreign-key-column>
<key-column>orderLineItemID</key-column>
</column-map>
</relationship-role-map>
</weblogic-relationship-role>
</weblogic-rdbms-relation>
<weblogic-rdbms-relation>
<relation-name>OrderLineItemBean_product-ProductBean</relation-name>
<weblogic-relationship-role>
<relationship-role-name>ProductBean_null-Has-OrderLineItemBean_product</relationship-role-name>
<relationship-role-map>
<column-map>
<foreign-key-column>OrderLineItemBean_orderLineItemID</foreign-key-column>
<key-column>orderLineItemID</key-column>
</column-map>
</relationship-role-map>
</weblogic-relationship-role>
</weblogic-rdbms-relation>
<pre></pre>
Pls give me a solution to this exception.
Regards
Priya

Similar Messages

Unable to deploy EJB - weblogic,management.ApplicationException

I am getting the following error when i deploy an ear file in WL 7.0 with MySQL
at the backend
There is one entity bean and one servlet in the application.
can any body tell what mistake i could be making ?
thanks in advance
-vasanth
error log
=====
weblogic.management.ApplicationException: Prepare failed. Task Id = null
Module Name: titan_ejbs.jar, Error: Exception preparing module: EJBModule(titan_ejbs.jar,status=NEW)
Unable to deploy EJB: titan_ejbs.jar from titan_ejbs.jar:
java.lang.NullPointerException
     at weblogic.ejb20.deployer.CompositeMBeanDescriptor.getPersistenceUseIdentifier(CompositeMBeanDescriptor.java:1446)
     at weblogic.ejb20.deployer.CMPInfoImpl.<init>(CMPInfoImpl.java:104)
     at weblogic.ejb20.deployer.EntityBeanInfoImpl.<init>(EntityBeanInfoImpl.java:135)
     at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl.java:349)
     at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:438)
     at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:165)
     at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:151)
     at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
     at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
     at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
     at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
     at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
     at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
     at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
     at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
     at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
     at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
     at weblogic.Server.main(Server.java:32)
     at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155)
     at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
     at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
     at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
     at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
     at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
     at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
     at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
     at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
     at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
     at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
     at weblogic.Server.main(Server.java:32)
TargetException:
Unable to deploy EJB: titan_ejbs.jar from titan_ejbs.jar:
java.lang.NullPointerException
     at weblogic.ejb20.deployer.CompositeMBeanDescriptor.getPersistenceUseIdentifier(CompositeMBeanDescriptor.java:1446)
     at weblogic.ejb20.deployer.CMPInfoImpl.<init>(CMPInfoImpl.java:104)
     at weblogic.ejb20.deployer.EntityBeanInfoImpl.<init>(EntityBeanInfoImpl.java:135)
     at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl.java:349)
     at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:438)
     at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:165)
     at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:151)
     at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
     at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
     at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
     at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
     at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
     at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
     at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
     at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
     at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
     at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
     at weblogic.Server.main(Server.java:32)
     at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155)
     at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
     at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
     at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
     at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
     at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
     at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
     at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
     at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
     at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
     at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
     at weblogic.Server.main(Server.java:32)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:744)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
     at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
     at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
     at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
     at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)

Add a <persistence-use> element to weblogic-ejb-jar.xml deployment descriptor.
<persistence>
<persistence-use>
<type-identifier>WebLogic_CMP_RDBMS</type-identifier>
<type-version>5.1.0</type-version>
<type-storage>META-INF/weblogic-cmp-jar.xml</type-storage>
</persistence-use>
</persistence>
"vasanth" <[email protected]> wrote:
>
I am getting the following error when i deploy an ear file in WL 7.0
with MySQL
at the backend
There is one entity bean and one servlet in the application.
can any body tell what mistake i could be making ?
thanks in advance
-vasanth
error log
=====
weblogic.management.ApplicationException: Prepare failed. Task Id = null
Module Name: titan_ejbs.jar, Error: Exception preparing module: EJBModule(titan_ejbs.jar,status=NEW)
Unable to deploy EJB: titan_ejbs.jar from titan_ejbs.jar:
java.lang.NullPointerException
     at weblogic.ejb20.deployer.CompositeMBeanDescriptor.getPersistenceUseIdentifier(CompositeMBeanDescriptor.java:1446)
     at weblogic.ejb20.deployer.CMPInfoImpl.<init>(CMPInfoImpl.java:104)
     at weblogic.ejb20.deployer.EntityBeanInfoImpl.<init>(EntityBeanInfoImpl.java:135)
     at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl.java:349)
     at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:438)
     at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:165)
     at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:151)
     at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
     at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
     at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
     at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
     at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
     at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
     at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
     at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
     at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
     at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
     at weblogic.Server.main(Server.java:32)
     at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155)
     at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
     at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
     at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
     at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
     at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
     at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
     at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
     at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
     at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
     at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
     at weblogic.Server.main(Server.java:32)
TargetException:
Unable to deploy EJB: titan_ejbs.jar from titan_ejbs.jar:
java.lang.NullPointerException
     at weblogic.ejb20.deployer.CompositeMBeanDescriptor.getPersistenceUseIdentifier(CompositeMBeanDescriptor.java:1446)
     at weblogic.ejb20.deployer.CMPInfoImpl.<init>(CMPInfoImpl.java:104)
     at weblogic.ejb20.deployer.EntityBeanInfoImpl.<init>(EntityBeanInfoImpl.java:135)
     at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl.java:349)
     at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:438)
     at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:165)
     at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:151)
     at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
     at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
     at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
     at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
     at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
     at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
     at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
     at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
     at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
     at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
     at weblogic.Server.main(Server.java:32)
     at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155)
     at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:332)
     at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
     at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
     at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
     at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
     at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
     at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
     at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
     at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
     at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
     at weblogic.Server.main(Server.java:32)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:744)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490)
     at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServerLifeCycleImpl.java:150)
     at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
     at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
     at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)

Weblogic.management.ApplicationException

I am trying to deploy a .war file , which use to work perfectly fine in weblogic
6.1 . While deploying it in weblogic7.0 i am getting following error
weblogic.management.ApplicationException: No modules to prepare on ahfServerfor
application named antAhf1
Start server side stack trace:
weblogic.management.ApplicationException: No modules to prepare on ahfServerfor
application named antAhf1
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:536)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1056)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:724)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)
End server side stack trace
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:536)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1056)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:724)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:152)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:133)

Your application is configured for session replication in weblogic.xml. See http://e-docs.bea.com/wls/docs81/webapp/sessions.html for more information.
From the error message, it appears that you don't have a cluster. You'll either have to build a cluster or remove the session persistence stuff from weblogic.xml.
Mike
Weblogic/J2EE Security Blog: http://monduke.com

Error deploying EAR - weblogic.management.ApplicationException:None

Hello,
When deploying a EAR, I get the following exception:
[Deployer:149033]preparing application esb on <xxx-admin>
[Deployer:149033]failed application esb on <xxx-admin>
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application esb on <xxx-admin>.: Exception:weblogic.management.ApplicationException: None
Nested Exception:
java.lang.RuntimeException: Failed to deploy process <ProcessName.jpd>. Internal error.
at com.bea.wli.management.WLIAppListener.checkProject(WLIAppListener.java:194)
at com.bea.wli.management.WLIAppListener.initializingApplication(WLIAppListener.java:130)
at weblogic.j2ee.ListenerInvocationAction.run(ListenerInvocationAction.java:42)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.j2ee.J2EEApplicationContainer.notifySecureListener(J2EEApplicationContainer.java:4721)
at weblogic.j2ee.J2EEApplicationContainer.notify(J2EEApplicationContainer.java:4706)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:986)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2602)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2552)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2474)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
I am not able to get anything out this. Can someone help me please?
Thanks.
Prabhu

HI prabhusethuraman,
We have an error than seems the same error that you has before, the stack trace when we deploy the whorkshop application that is this one:
[java] Initiated Task: [7] [Deployer:149026]Deploy application q99j on integracion.
[java] Task 7 failed: [Deployer:149026]Deploy application q99j on integracion.
[java] Deployment failed on Cluster integracion
[java] Exception:weblogic.management.ApplicationException: None
[java] Nested Exception:
[java] java.lang.RuntimeException: Failed to deploy process /q99jdummyDynamicRouterProcess/com/ejie/notifications/Q99jNotificationsP.jpd. Internal error.
[java]      at com.bea.wli.management.WLIAppListener.checkProject(Lcom.bea.wli.management.processmanifest.ProcessManifestDocument$ProcessManifest$Project;Lweblogic.application.ApplicationLifecycleEvent;)Z(WLIAppListener.java:194)
[java]      at com.bea.wli.management.WLIAppListener.initializingApplication(Lweblogic.application.ApplicationLifecycleEvent;)V(WLIAppListener.java:130)
[java]      at weblogic.j2ee.ListenerInvocationAction.run()Ljava.lang.Object;(ListenerInvocationAction.java:42)
[java]      at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic.security.subject.AbstractSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(Optimized Method)
[java]      at weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.internal.AuthenticatedSubject;Lweblogic.security.acl.internal.AuthenticatedSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(SecurityManager.java:118)
[java]      at weblogic.j2ee.J2EEApplicationContainer.notifySecureListener(ILweblogic.application.ApplicationLifecycleListener;)V(J2EEApplicationContainer.java:4721)
[java]      at weblogic.j2ee.J2EEApplicationContainer.notify(I)V(J2EEApplicationContainer.java:4706)
[java]      at weblogic.j2ee.J2EEApplicationContainer.prepare(Ljava.lang.String;[Lweblogic.management.configuration.ComponentMBean;[Ljava.lang.String;)V(J2EEApplicationContainer.java:1006)
[java]      at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer()V(SlaveDeployer.java:2444)
[java]      at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer()Z(SlaveDeployer.java:2394)
[java]      at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2310)
[java]      at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
[java]      at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
[java]      at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
[java]      at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
[java]      at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
[java]      at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
[java]      at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
[java] java.lang.Exception: Delta :26 ErrorMessage :
Can you say us the solution that you found in your case ?
Thanks,
Carmel.

Weblogic.management.ApplicationException: - Internal Error

Hello,
When deploying a EAR, I get the following exception:
[Deployer:149033]preparing application esb on <xxx-admin>
[Deployer:149033]failed application esb on <xxx-admin>
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application esb on <xxx-admin>.: Exception:weblogic.management.ApplicationException: None
Nested Exception:
java.lang.RuntimeException: Failed to deploy process <ProcessName.jpd>. Internal error.
at com.bea.wli.management.WLIAppListener.checkProject(WLIAppListener.java:194)
at com.bea.wli.management.WLIAppListener.initializingApplication(WLIAppListener.java:130)
at weblogic.j2ee.ListenerInvocationAction.run(ListenerInvocationAction.java:42)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at weblogic.j2ee.J2EEApplicationContainer.notifySecureListener(J2EEApplicationContainer.java:4721)
at weblogic.j2ee.J2EEApplicationContainer.notify(J2EEApplicationContainer.java:4706)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:986)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2602)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2552)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2474)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
I m working on Weblogic 8.1.2 Integration domain. When I delete all the Wli_process_* tables, I m able to deploy the ear and it runs fine for a few days, after which it again starts giving the Internal Error and I m forced to delete the tables and restart the server.
Does anyone have any idea about this? the cause?
Is there some alternative solution of getting rid of it?
Thanks in Advance,
Looking forward to quick replies
ak

I think the deployment fails because you might have inflight processes
running. And it succeds after you delete the in-process data.
It will be worthwhile to investigate "Internal Error " rather then the
re-deployment workaround.
~ Veerendra
"AK Tiwari" <[email protected]> wrote in message
news:18418117.1103279949606.JavaMail.root@jserv5...
Hello,
When deploying a EAR, I get the following exception:
[Deployer:149033]preparing application esb on <xxx-admin>
[Deployer:149033]failed application esb on <xxx-admin>
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy
application esb on <xxx-admin>.:
Exception:weblogic.management.ApplicationException: None
Nested Exception:
java.lang.RuntimeException: Failed to deploy process <ProcessName.jpd>.
Internal error.
at
com.bea.wli.management.WLIAppListener.checkProject(WLIAppListener.java:194)
at
com.bea.wli.management.WLIAppListener.initializingApplication(WLIAppListener.java:130)
at
weblogic.j2ee.ListenerInvocationAction.run(ListenerInvocationAction.java:42)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:317)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
at
weblogic.j2ee.J2EEApplicationContainer.notifySecureListener(J2EEApplicationContainer.java:4721)
at
weblogic.j2ee.J2EEApplicationContainer.notify(J2EEApplicationContainer.java:4706)
at
weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:986)
at
weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2602)
at
weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2552)
at
weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2474)
at
weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:798)
at
weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:507)
at
weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:465)
at
weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
I m working on Weblogic 8.1.2 Integration domain. When I delete all the
Wli_process_* tables, I m able to deploy the ear and it runs fine for a
few days, after which it again starts giving the Internal Error and I m
forced to delete the tables and restart the server.
Does anyone have any idea about this? the cause?
Is there some alternative solution of getting rid of it?
Thanks in Advance,
Looking forward to quick replies
ak

Having problems starting Weblogic Managed Server

Hi,
I am new to WebLogic and I was looking at the webservices examples in samples dir and I took the example and just moved it to one of my currently deployed Web Application folder and changed the dir strutcure instead of the samples dir strutcure, compiled and deployed as standalone Application(not as part of my currently deployed Web App). It worked fine.
Then since there would be a need for reuse of lot of the current Web App. in the web services we are trying to implement, I tried to put the ear that got created in the WEB-INF/lib of the currently deployed exploded dir. It was pretty dumb to put the ear there, just thought, worst case it wont work, I thought I could pull the ear out of there. But seems like this changed the entire config.xml and ever since that my admin server got changed to myserver, I corrected all the problems with the admin server and admin server and node server they come up just fine. When trying to bring up Managed server, I get the following excpetion
Jul 16, 2004 4:00:37 PM EDT> <Debug> <HTTP> <BEA-101158> <Exception thrown while loading epic_dev: java.lang.NullPointerException
java.lang.NullPointerException
     at weblogic.utils.enumerations.FileEnumeration.getNextFile(FileEnumeration.java:155)
     at weblogic.utils.enumerations.FileEnumeration.hasMoreFiles(FileEnumeration.java:102)
     at weblogic.utils.enumerations.FileEnumeration.hasMoreElements(FileEnumeration.java:134)
     at weblogic.utils.jars.ExplodedJarFile$1.hasNext(ExplodedJarFile.java:112)
     at weblogic.utils.classloaders.ExtractionHelper.extractClassFiles(ExtractionHelper.java:117)
     at weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebAppServletContext.java:5119)
     at weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:4991)
     at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:560)
     at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:511)
     at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:594)
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:623)
     at weblogic.j2ee.J2EEApplicationContainer.prepareWebModule(J2EEApplicationContainer.java:2896)
     at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1532)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:822)
     at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3085)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:930)
     at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:398)
     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:230)
     at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
     at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
     at weblogic.Server.main(Server.java:32)
>
<Jul 16, 2004 4:00:37 PM EDT> <Info> <Deployer> <BEA-149061> <Module epic_dev of application appsdirepic_dev_dir failed to transition from unprepared to prepared on server betsy_dev.>
<Jul 16, 2004 4:00:37 PM EDT> <Error> <Deployer> <BEA-149205> <Failed to initialize the application appsdirepic_dev_dir due to error weblogic.management.ApplicationException: prepare failed for epic_dev
Module Name: epic_dev, Error: Could not load epic_dev: java.lang.NullPointerException
weblogic.management.ApplicationException: prepare failed for epic_dev
Module Name: epic_dev, Error: Could not load epic_dev: java.lang.NullPointerException
     at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1555)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1188)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1031)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:822)
     at weblogic.management.deploy.slave.SlaveDeployer$Application.prepare(SlaveDeployer.java:3085)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareAllApplications(SlaveDeployer.java:930)
     at weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:398)
     at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:230)
     at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
     at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:964)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:359)
     at weblogic.Server.main(Server.java:32)
>
Could someone help me with resolving this.(This is only the dev machine, I played thannkfully!).
And also would like to get suggestions on setting up the new webserverces that we are trying to do. If I need to reuse lot of class files from current appl., how do i go about implementing this webservice? Should this be part of the existing application? or Web service could be a separate application and somehow we could look at the web app which is in the same domain.
Any help is appreciated.
Thanks
Anna

There was an access problem in the application I was trying to deploy and it had nothing to do with EAR file, once the access problem is taken care of, I could deploy the app just fine.

Weblogic deploying an already deployed application!

Hi,
These are the following errors that I get. This is an already deployed application so not sure why weblogic deploys it again. This does not happen in all the machines.
Can someone tell me why it is doing this and how to make the application come up?
This is the error that I get when logging into the application:
Error 503--Service Unavailable
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.5.4 503 Service Unavailable
The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay may be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
Webserver console errors:
Unable to deploy EJB: jar from jar:
Compiler failed executable.exec(java.lang.String[javac, -nowarn, -classpath, D:\bea\user_projects\ESMdomain\t
mp_ejbSramamoorthy7001myserver\-au306wtcrywq;D:\bea\user_projects\ESMdomain\applications\esm.ear\jar;D:\bea\j
dk131_06\jre\lib\rt.jar;D:\bea\jdk131_06\jre\lib\i18n.jar;D:\bea\jdk131_06\jre\lib\sunrsasign.jar;D:\bea\jdk1
31_06\jre\classes;D:\bea\jdk131_06\jre\lib\tools.jar;D:/bea/weblogic700\server\lib\weblogic_sp.jar;D:/bea/web
logic700\server\lib\weblogic.jar;D:\bea\jdk131_06\jre\jre\lib\rt.jar;JAVA_HOME\lib\dt.jar;D:/bea/weblogic700/
server/lib/mbeantypes/wlManagement.jar;D:/bea/weblogic700/server/lib/mbeantypes/ESMSecurityProviders.jar;D:/b
ea/user_projects/ESMdomain/applications/esmconfig;D:/bea/user_projects/ESMdomain/applications/esm.ear/jar;D:/
bea/user_projects/ESMdomain/esmlib/avalon.jar;D:/bea/user_projects/ESMdomain/esmlib/batik.jar;D:/bea/user_pro
jects/ESMdomain/esmlib/bsh-1.2b7.jar;D:/bea/user_projects/ESMdomain/esmlib/comm.jar;D:/bea/user_projects/ESMd
omain/esmlib/multipartrequest.jar;D:/bea/user_projects/ESMdomain/esmlib/crimson.jar;D:/bea/user_projects/ESMd
omain/esmlib/fop.jar;D:/bea/user_projects/ESMdomain/esmlib/gnu-regexp-1.1.4.jar;D:/bea/user_projects/ESMdomai
n/esmlib/jdom.jar;D:/bea/user_projects/ESMdomain/esmlib/oracle.jar;D:/bea/user_projects/ESMdomain/esmlib/repo
rting.jar;D:/bea/user_projects/ESMdomain/esmlib/xerces.jar, -d, tmp_ejbSramamoorthy7001myserver\-au306wtcrywq
, @C:\DOCUME~1\SRAMAM~1\LOCALS~1\Temp\compileList29351.tmp])
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:249)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:344)
at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490
at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServer
LifeCycleImpl.java:150)
at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
<Jul 29, 2004 11:44:23 AM EDT> <Error> <Deployer> <149231> <The slave deployer was unable to set the activati
on state to true for the application appsdiresm_ear-0
weblogic.management.ApplicationException: activate failed forwar
Module Name: war, Error: weblogic.j2ee.DeploymentException: Could not setup environment - with nested excepti
on:
[weblogic.deployment.EnvironmentException: Could not resolve ejbLink: RackManager]
TargetException:
Unable to deploy EJB: jar from jar:Error 503--Service Unavailable
Thanks in advance and any help will be greatly appreciated!
Message was edited by sssd at Jul 29, 2004 10:56 AM

Hi,
These are the following errors that I get. This is an already deployed application so not sure why weblogic deploys it again. This does not happen in all the machines.
Can someone tell me why it is doing this and how to make the application come up?
This is the error that I get when logging into the application:
Error 503--Service Unavailable
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.5.4 503 Service Unavailable
The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay may be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
Webserver console errors:
Unable to deploy EJB: jar from jar:
Compiler failed executable.exec(java.lang.String[javac, -nowarn, -classpath, D:\bea\user_projects\ESMdomain\t
mp_ejbSramamoorthy7001myserver\-au306wtcrywq;D:\bea\user_projects\ESMdomain\applications\esm.ear\jar;D:\bea\j
dk131_06\jre\lib\rt.jar;D:\bea\jdk131_06\jre\lib\i18n.jar;D:\bea\jdk131_06\jre\lib\sunrsasign.jar;D:\bea\jdk1
31_06\jre\classes;D:\bea\jdk131_06\jre\lib\tools.jar;D:/bea/weblogic700\server\lib\weblogic_sp.jar;D:/bea/web
logic700\server\lib\weblogic.jar;D:\bea\jdk131_06\jre\jre\lib\rt.jar;JAVA_HOME\lib\dt.jar;D:/bea/weblogic700/
server/lib/mbeantypes/wlManagement.jar;D:/bea/weblogic700/server/lib/mbeantypes/ESMSecurityProviders.jar;D:/b
ea/user_projects/ESMdomain/applications/esmconfig;D:/bea/user_projects/ESMdomain/applications/esm.ear/jar;D:/
bea/user_projects/ESMdomain/esmlib/avalon.jar;D:/bea/user_projects/ESMdomain/esmlib/batik.jar;D:/bea/user_pro
jects/ESMdomain/esmlib/bsh-1.2b7.jar;D:/bea/user_projects/ESMdomain/esmlib/comm.jar;D:/bea/user_projects/ESMd
omain/esmlib/multipartrequest.jar;D:/bea/user_projects/ESMdomain/esmlib/crimson.jar;D:/bea/user_projects/ESMd
omain/esmlib/fop.jar;D:/bea/user_projects/ESMdomain/esmlib/gnu-regexp-1.1.4.jar;D:/bea/user_projects/ESMdomai
n/esmlib/jdom.jar;D:/bea/user_projects/ESMdomain/esmlib/oracle.jar;D:/bea/user_projects/ESMdomain/esmlib/repo
rting.jar;D:/bea/user_projects/ESMdomain/esmlib/xerces.jar, -d, tmp_ejbSramamoorthy7001myserver\-au306wtcrywq
, @C:\DOCUME~1\SRAMAM~1\LOCALS~1\Temp\compileList29351.tmp])
at weblogic.ejb20.ejbc.EJBCompiler.doCompile(EJBCompiler.java:249)
at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:344)
at weblogic.ejb20.deployer.EJBDeployer.runEJBC(EJBDeployer.java:489)
at weblogic.ejb20.deployer.EJBDeployer.compileEJB(EJBDeployer.java:819)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1268)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:232)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:1570)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:737)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:458)
at weblogic.management.deploy.slave.SlaveDeployer.prepareAllStagedApplications(SlaveDeployer.java:490
at weblogic.management.deploy.slave.SlaveDeployer.initialize(SlaveDeployer.java:253)
at weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.initialize(DeploymentManagerServer
LifeCycleImpl.java:150)
at weblogic.t3.srvr.ServerLifeCycleList.initialize(ServerLifeCycleList.java:54)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:782)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
<Jul 29, 2004 11:44:23 AM EDT> <Error> <Deployer> <149231> <The slave deployer was unable to set the activati
on state to true for the application appsdiresm_ear-0
weblogic.management.ApplicationException: activate failed forwar
Module Name: war, Error: weblogic.j2ee.DeploymentException: Could not setup environment - with nested excepti
on:
[weblogic.deployment.EnvironmentException: Could not resolve ejbLink: RackManager]
TargetException:
Unable to deploy EJB: jar from jar:Error 503--Service Unavailable
Thanks in advance and any help will be greatly appreciated!
Message was edited by sssd at Jul 29, 2004 10:56 AM

Error while deploying enterprise application on weblogic 11gr1(10.3.3)

Hi folks,
I got an error while starting an .ear file(ALRuleBean).
weblogic.management.ManagementException: [Deployer:149188]No application named 'ALRuleBean' exists for operation start. Operation can not be performed until server is restarted.
Please help me.

Hi,
Probably you have made some changes and trying to start the application.
Can you try to restart the servers where the application has been targeted and start the server.
If possible provide us the complete stack trace from the server logs, which will help us to know what exacting issue is.
Good Day!!
~Ashish

How to manage large database records in enterprise application

Hi All,
I am working on a large enterprise application relating to Capital Market. I am working in Java and with its extended technology. I am facing one critical problem which needs solution from your side. I have a database table which contains approximately more than 5 millions of records, I want to display the records with proper pagination. Here I am using Hibernate for database related stuffs. I am using a query which contains a join query to load the records. After the query the filtered records come to approcimately 80,000. I am unable to make proper pagination, everytime for next or previous set of 10 records I hit the database which is a time consuming affair. I do not know what I will do , should I cache the data for pagination. Everytime I load more than 80,000 records, think that in an web based application, the no of users are 5000, then how to manage. I need core java level solution not in the JSP level. Please help me in this regard.

After the query the filtered records come to approcimately 80,000. I am unable to
make proper pagination,Just a thought. If you display 50 per page, that's 1600 pages. Say it takes the user
15 seconds to read the page: total 400min=6 2/3 hours and probably a bad case of RSI.
The proper pagination would possibly be no pagination.

How do I configure an enterprise application using Weblogic 10 wlconfig

Hi All,
I am converting an installer from WL8 to WL10. We use wlconfig to configure our EAR in wl8 with several wlconfig commands. These don't seem to work though when attempting to use wl10. The following error comes up more often than not and does not seem to be appropriate to what is actually happening.
Unable to create new bean of type WebAppComponent for pcidomain_new:Name=GenPortal,Type=Application:missing create method
I have searched the Weblogic Documentation and have found only general information on how to use wlconfig with a simple example that does not touch on application deployment. I have also found an MBean Reference but am unclear as to how to marry the two.
It would be really great if someone knew where I might find a concrete example of creating an Enterprise application using WL10.
Here is the current wlconfig task that we use successfully in weblogic 8.
${server-mbean} is read in earlier with a wlconfig query command.
          <wlconfig url="t3://${env.COMPUTERNAME}:${weblogic_port}" username="${weblogic_username}" password="${weblogic_password}">
               <create type="Application" name="GenPortal" property="GenPortalApp">
                    <set attribute="Path" value="${domain_home}/${domain_name}/applications/GenPortal.ear" />
                    <set attribute="StagingMode" value="nostage" />
                    <set attribute="TwoPhase" value="true" />
                    <create type="WebAppComponent" name="GenPortal">
                         <set attribute="Targets" value="${server-mbean}" />
                         <set attribute="URI" value="GenPortalWebApp.war" />
                    </create>
                    <create type="EJBComponent" name="GenPortalEJB">
                         <set attribute="Targets" value="${server-mbean}" />
                         <set attribute="URI" value="GenPortalEJB.jar" />
                    </create>
                    <create type="EJBComponent" name="BidEvaluatorEJB">
                         <set attribute="Targets" value="${server-mbean}" />
                         <set attribute="URI" value="BidEvaluatorEJB.jar" />
                    </create>
                    <create type="EJBComponent" name="BidFormulatorEJB">
                         <set attribute="Targets" value="${server-mbean}" />
                         <set attribute="URI" value="BidFormulatorEJB.jar" />
                    </create>
                    <create type="EJBComponent" name="ConfiguratorEJB">
                         <set attribute="Targets" value="${server-mbean}" />
                         <set attribute="URI" value="ConfiguratorEJB.jar" />
                    </create>
                    <create type="EJBComponent" name="ISOCommunicationEJB">
                         <set attribute="Targets" value="${server-mbean}" />
                         <set attribute="URI" value="ISOCommunicationEJB.jar" />
                    </create>
                    <create type="EJBComponent" name="LMPManagerEJB">
                         <set attribute="Targets" value="${server-mbean}" />
                         <set attribute="URI" value="LMPManagerEJB.jar" />
                    </create>
                    <create type="EJBComponent" name="ScriptCalcEJB">
                         <set attribute="Targets" value="${server-mbean}" />
                         <set attribute="URI" value="ScriptCalcEJB.jar" />
                    </create>
                    <create type="EJBComponent" name="SettlementEJB">
                         <set attribute="Targets" value="${server-mbean}" />
                         <set attribute="URI" value="SettlementEJB.jar" />
                    </create>
               </create>
               <create type="StartupClass" name="PCI_Initializer">
                    <set attribute="Targets" value="${server-mbean}" />
                    <set attribute="ClassName" value="com.pci.gtdw.bean.Initialize" />
                    <set attribute="Arguments" value="port=${weblogic_port},user=background,password=${background_user_password},debug=false,loggerLevel=debug" />
               </create>
               <set mbean="${domain_name}:Name=${domain_name},Type=JTA" attribute="TimeoutSeconds" value="1200" />
          </wlconfig>
As I mentioned earlier right now this fails with when trying to create the WebAppComponent as seen in the error message above.
Thanks for any help you can provide.

Here's a couple ideas:
1. Easier, but with non-deterministic response time:   Wire the button up to one of your I/O pins and poll it. When you detect the button, issue a software call to stop the pulse train. If the duration of the button press may be short compared to your polling rate, then wire it to a counter source pin and perform edge counting. When you poll any value > 0, the press has happened. (Sometimes the value may be >1 if the switch has "bounce").
2. Trickier, but with deterministic hardware timing: Configure another counter, call it counter B, for triggered pulse generation. Wire/configure the button as the trigger. Make sure that the "high time" of the pulse is long enough to let your software respond, if needed.   Also configure your original continuous pulse train counter to use Ctr B's output as a "pause trigger", specifying to pause when high.   When the button is pressed, counter B will fire a pulse and that pulse will inhibit your original counter's pulse generation. In short, the pulses will stop until counter B's pulse has completed its full duration. Your software can monitor for this series of events and stop the original counter task if needed.
-Kevin P.

How to deploy DAC enterprise application on WebLogic Server

hi,
i have installed DAC server on Linux machine and DAC client on windows machine. I can able to log in to DAC by stand alone mode and
Currently we are unable to login to the DAC 11g client by FMW(Web mode)
To login into DAC client by FMW mode we need to deploy DAC enterprise application on WebLogic Server, could anybody help how to deploy DAC enterprise application on weblogic server ?
Thanks in advance..
Vinoth

follow this doc http://docs.oracle.com/cd/E35287_01/fusionapps.7964/e14849.pdf
mark if it helps

Enterprise application conversion problem from WLS 10.3.0 to WLS 10.3.2

Hi all,
I'm posting this just to document a problem I had when converting an Enterprise Application from WLS 10.3.0 across to WLS 10.3.2 environment.
Upon deployment of the application I was getting this error:
Caused By: weblogic.descriptor.BeanAlreadyExistsException: Bean already exists: "weblogic.j2ee.descriptor.wl.ApplicationParamBeanImpl@b720894d(/ApplicationParams[webapp.encoding.default])"
     at weblogic.descriptor.internal.ReferenceManager.registerBean(ReferenceManager.java:227)
     at weblogic.j2ee.descriptor.wl.WeblogicApplicationBeanImpl.setApplicationParams(WeblogicApplicationBeanImpl.java:560)
     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:597)
     at com.bea.staxb.runtime.internal.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:48)
     at com.bea.staxb.runtime.internal.RuntimeBindingType$BeanRuntimeProperty.setValue(RuntimeBindingType.java:536)
     at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType$QNameRuntimeProperty.fillCollection(AttributeRuntimeBindingType.java:381)
     at com.bea.staxb.runtime.internal.MultiIntermediary.getFinalValue(MultiIntermediary.java:52)
     at com.bea.staxb.runtime.internal.AttributeRuntimeBindingType.getFinalObjectFromIntermediary(AttributeRuntimeBindingType.java:140)
     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalBindingType(UnmarshalResult.java:200)
     at com.bea.staxb.runtime.internal.UnmarshalResult.unmarshalDocument(UnmarshalResult.java:169)
     at com.bea.staxb.runtime.internal.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:65)
     at weblogic.descriptor.internal.MarshallerFactory$1.createDescriptor(MarshallerFactory.java:150)
     at weblogic.descriptor.BasicDescriptorManager.createDescriptor(BasicDescriptorManager.java:323)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescriptorBeanFromReader(AbstractDescriptorLoader2.java:788)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescriptorBean(AbstractDescriptorLoader2.java:409)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBeanWithoutPlan(AbstractDescriptorLoader2.java:759)
     at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescriptorBean(AbstractDescriptorLoader2.java:768)
     at weblogic.application.ApplicationDescriptor.getWeblogicApplicationDescriptor(ApplicationDescriptor.java:329)
     at weblogic.application.internal.EarDeploymentFactory.findOrCreateComponentMBeans(EarDeploymentFactory.java:181)
     at weblogic.application.internal.MBeanFactoryImpl.findOrCreateComponentMBeans(MBeanFactoryImpl.java:48)
     at weblogic.application.internal.MBeanFactoryImpl.createComponentMBeans(MBeanFactoryImpl.java:110)
     at weblogic.application.internal.MBeanFactoryImpl.initializeMBeans(MBeanFactoryImpl.java:76)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationMBean(MBeanConverter.java:88)
     at weblogic.management.deploy.internal.MBeanConverter.createApplicationForAppDeployment(MBeanConverter.java:66)
     at weblogic.management.deploy.internal.MBeanConverter.setupNew81MBean(MBeanConverter.java:314)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.compatibilityProcessor(ActivateOperation.java:81)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.setupPrepare(AbstractOperation.java:295)
     at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:97)
     at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:747)
     at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1216)
     at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:250)
     at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
     at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
It turns out this was an issue with the META-INF/weblogic-application.xml having duplicate entries for the "webapp.encoding.default" parameter.
This obviously got duplicated when my app was re-imported into the Eclipse OPEP environment for WLS 10.3.2
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-application xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-application" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/javaee_5.xsd http://xmlns.oracle.com/weblogic/weblogic-application http://xmlns.oracle.com/weblogic/weblogic-application/1.0/weblogic-application.xsd">


<wls:application-param>
<wls:param-name>webapp.encoding.default</wls:param-name>
<wls:param-value>UTF-8</wls:param-value>
</wls:application-param>
<wls:application-param>
<wls:param-name>webapp.encoding.default</wls:param-name>
<wls:param-value>UTF-8</wls:param-value>
</wls:application-param>
</wls:weblogic-application>
Removing the duplicate entry resolved this problem.
I hope this helps anyone else that experiences this issue.
Regards,
Paul

Below link might be helpful.
http://kr.forums.oracle.com/forums/thread.jspa?threadID=1049509&tstart=0
Regards,
Anandraj
http://weblogic-wonders.com/

Deploying multiple versions of an enterprise application

hi,
trying to find a solution to deploy several versions of an enterprise
application i came up with the following considerations. i would highly
appreciate feedback on which method would be feasable and the issues
involved.
o version specific jndi names
creating a separate deployment descriptor for each version of the
enterprise application and binding each ejb to a different jndi name.
utilize jndi enc mappings to keep the application code unaffected.
the following deployment descriptor excerpt shows the relevant parts of
the weblogic-ejb-jar.xml for "versions01". each further version would
have different jndi names and jndi enc mappings.
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>SomeEJB</ejb-name>
<local-jndi-name>version01/SomeHomeLocal</local-jndi-name> 
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>AnotherEJB<ejb-name>
<reference-descriptor>
<ejb-ref-name>ejb/SomeHomeLocal</ejb-ref-name>
<jndi-name>version01/SomeHomeLocal</jndi-name> 
</reference-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
is it possible to deploy the same classes with different jndi names? are
there any issues concerning the internal handling of weblogic
(classloading, classpath, ...)? can multiple versions be deployed from
the same source directory structure (hence is weblogic creating it's own
copy of class files during deployment by copying them into the domain
configuration directory)?
o multiple managed servers
configuring multiple managed servers and deploying each version of the
enterprise application to it's own server instance.
o built in support
does bea weblogic server provide some built in version support that
allows the deployment of multiple versions of the same enterprise
application within a single server instance? are there any deployment
tools that help to generate version specific deployment descriptors?
thanks in advance
best regards
erich liebmann

hi,
trying to find a solution to deploy several versions of an enterprise
application i came up with the following considerations. i would highly
appreciate feedback on which method would be feasable and the issues
involved.
o version specific jndi names
creating a separate deployment descriptor for each version of the
enterprise application and binding each ejb to a different jndi name.
utilize jndi enc mappings to keep the application code unaffected.
the following deployment descriptor excerpt shows the relevant parts of
the weblogic-ejb-jar.xml for "versions01". each further version would
have different jndi names and jndi enc mappings.
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>SomeEJB</ejb-name>
<local-jndi-name>version01/SomeHomeLocal</local-jndi-name> 
</weblogic-enterprise-bean>
<weblogic-enterprise-bean>
<ejb-name>AnotherEJB<ejb-name>
<reference-descriptor>
<ejb-ref-name>ejb/SomeHomeLocal</ejb-ref-name>
<jndi-name>version01/SomeHomeLocal</jndi-name> 
</reference-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
is it possible to deploy the same classes with different jndi names? are
there any issues concerning the internal handling of weblogic
(classloading, classpath, ...)? can multiple versions be deployed from
the same source directory structure (hence is weblogic creating it's own
copy of class files during deployment by copying them into the domain
configuration directory)?
o multiple managed servers
configuring multiple managed servers and deploying each version of the
enterprise application to it's own server instance.
o built in support
does bea weblogic server provide some built in version support that
allows the deployment of multiple versions of the same enterprise
application within a single server instance? are there any deployment
tools that help to generate version specific deployment descriptors?
thanks in advance
best regards
erich liebmann

Which services should be moved to a new SharePoint Enterprise Application server?

Our farm is currently a WFE and a SQL server. I've been tasked with creating a new SP Enterprise Application/Search server.
Which services should be moved? This is what's currently listed in Services on Server:
Access Database Service Started Stop
Application Registry Service Started Stop
Business Data Connectivity Service Started Stop
Central Administration Started Stop
Claims to Windows Token Service Started Stop
Document Conversions Launcher Service Stopped Start
Document Conversions Load Balancer Service Stopped Start
Excel Calculation Services Started Stop
Lotus Notes Connector Stopped Start
Managed Metadata Web Service Started Stop
Microsoft SharePoint Foundation Incoming E-Mail Started Stop
Microsoft SharePoint Foundation Sandboxed Code Service Stopped Start
Microsoft SharePoint Foundation Subscription Settings Service Stopped Start
Microsoft SharePoint Foundation Web Application Started Stop
Microsoft SharePoint Foundation Workflow Timer Service Started Stop
PerformancePoint Service Started Stop
Search Query and Site Settings Service Started Stop
Secure Store Service Started Stop
SharePoint Foundation Search Stopped Start
SharePoint Server Search Started Stop
User Profile Service Started Stop
User Profile Synchronization Service Started Stop
Visio Graphics Service Started Stop
Web Analytics Data Processing Service Started Stop
Web Analytics Web Service Started Stop
Word Automation Services Started Stop

Take a look at http://www.microsoft.com/en-us/download/details.aspx?id=37000. It should help you decide where it is most appropriate to locate services.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

The Oracle MapViewer brings the WebLogic Managed Server to crash

Problem Description: The Oracle MapViewer brings the WebLogic Managed Server to crash, when we call a GetMap-Request with wrong Coordinates.
This was found out for the SRS=EPSG:25833. Example:
http://igdb-qm-svra1.blva.bayern.de:8080/mapviewer/wms?
REQUEST=getMap&
Version=1.1.1&
LAYERS=&
FORMAT=image/png&
TRANSPARENT=false&
STYLES=&
Datasource=igvert_alkis_wms&
basemap=AT_WMS_TN-KOMPLETT&
SRS=EPSG:25833&
BBOX=3.32358690717E7,5529425.0143,3.32369088846E7,5530464.8272&
WIDTH=500&
HEIGHT=500&
With the Enterprise Manager was also evaluated during and after a crash of Server the SQL-Statements.
If the SQL statements executed on the database itself, it takes a few seconds after a correct answer returns.
I know that have the look for the EPSG coordinate as follows:
BBOX=235869.071700,5529425.014300,236908.884600,5530464.827200&
My question therefore: Why are these coordinates by the Oracle MapViewer approved and not caught? An Request with incorrect
coordinates goes into a StuckThreads and then the ManagedServer crashed.
In the appendix you will find the evaluation of the Enterprise Manager.
I have tested the request with two different versions of Oracle MapViewer (Ver11_1_1_5_B110527 and Ver11_B100426). In both the same problem occurs on.
I have also filed an SR.
Best Regards
Kerstin

Hi,
Can you confirm that you're trying to setup a managed server on another machine using the pack/unpack commands ?
You might to want to take a look at that post.
Clustering of 2 Physical server
Hope that helps !
Regards

Weblogic.management.ApplicationException in Enterprise Application?

Similar Messages

Maybe you are looking for