Unable to deploy after undeploy...

Hello there,
I have a OC4J 10.1.3.4 Standalone instance installed here, and when I first deploy my app everything goes right. But after undeploying it I'm unable to deploy it again. An exception is thrown when my app tries to instantiate my persistence unit. So I'm (almost) pretty sure that it is something about about the managed data source that I use. Probably is not being released...
How do I manage to solve that? Is there a correct sequence that I have to follow in order to release the data source? A friend of mine told me that I should stop the app before uninstalling it. But this didn't work...
Any help would be great.
Thanks,
Bruno.

sorry i just notice you're using standalone version. can you see any errors/stack trace in your command-line console? can you post the exception stack trace?
Edited by: rhp on Aug 4, 2010 1:49 PM

Similar Messages

Unable to deploy or undeploy with Ant on Oracle ESB

Hello all,
I'm want to use Ant to deploy my SOA applications, instead of right clicking and choosing 'Register with ESB' for each of the applications in what is currently a suite of 46 and still growing.
However, when I try to undeploy, I get an error:
BUILD FAILED
C:\source\NeoZESBV2\SOA_deploy\build.xml:80: oracle.tip.esb.client.ClientException: Unexpected end of file from server
at oracle.tip.esb.client.HttpClient.invoke(HttpClient.java:118)
at oracle.tip.esb.client.impl.ConsoleClientImpl.perform(ConsoleClientImpl.java:148)
at oracle.tip.esb.client.impl.ConsoleClientImpl.<init>(ConsoleClientImpl.java:71)
at oracle.tip.esb.client.ConsoleClientFactory.getConsoleClient(ConsoleClientFactory.java:32)
at oracle.tip.esb.client.anttasks.ESBSystemTask.undeploy(ESBSystemTask.java:66)
at oracle.tip.esb.client.anttasks.ESBSystemTask.undeploy(ESBSystemTask.java:96)
at oracle.tip.esb.client.anttasks.UndeployESBEntitiesTask.execute(UndeployESBEntitiesTask.java:188)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:390)
at org.apache.tools.ant.Target.performTasks(Target.java:411)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1397)
at org.apache.tools.ant.Project.executeTarget(Project.java:1366)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1249)
at org.apache.tools.ant.Main.runBuild(Main.java:801)
at org.apache.tools.ant.Main.startAnt(Main.java:218)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
Caused by: java.net.SocketException: Unexpected end of file from server
at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:769)
at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:632)
at sun.net.www.http.HttpClient.parseHTTPHeader(HttpClient.java:766)
at sun.net.www.http.HttpClient.parseHTTP(HttpClient.java:632)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1072)
at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:373)
at oracle.tip.esb.client.HttpClient.postAndReceive(HttpClient.java:138)
at oracle.tip.esb.client.HttpClient.invoke(HttpClient.java:114)
... 22 more
I decided to look into this later and undeployed manually -- it's just 4 systems. But upon deploying, I hit another error:
deploy:
[echo] Deploying from C:\source\NeoZESBV2\SOA-001_CGP_SOA-003_OAP
[deployESBProjects] 11-nov-2010 10:52:06 org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
[deployESBProjects] INFO: I/O exception (java.net.SocketException) caught when processing request: Software caused connection abort: socket write error
[deployESBProjects] 11-nov-2010 10:52:06 org.apache.commons.httpclient.HttpMethodDirector executeWithRetry
[deployESBProjects] INFO: Retrying request
[deployESBProjects] Deployment Failed ...Check if server is running
[deployESBProjects] org.apache.commons.httpclient.ProtocolException: Unbuffered entity enclosing request can not be repeated.
[deployESBProjects]      at org.apache.commons.httpclient.methods.EntityEnclosingMethod.writeRequestBody(EntityEnclosingMethod.java:487)
[deployESBProjects]      at org.apache.commons.httpclient.HttpMethodBase.writeRequest(HttpMethodBase.java:2114)
[deployESBProjects]      at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1096)
[deployESBProjects]      at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:398)
[deployESBProjects]      at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171)
[deployESBProjects]      at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397)
[deployESBProjects]      at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323)
[deployESBProjects]      at oracle.tip.esb.client.anttasks.DeploymentHelper.deploy(DeploymentHelper.java:103)
[deployESBProjects]      at oracle.tip.esb.client.anttasks.DeploymentHelper.deploy(DeploymentHelper.java:159)
[deployESBProjects]      at oracle.tip.esb.client.anttasks.ESBProjectTask.deploy(ESBProjectTask.java:107)
[deployESBProjects]      at oracle.tip.esb.client.anttasks.DeployESBProjectsTask.execute(DeployESBProjectsTask.java:103)
[deployESBProjects]      at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
[deployESBProjects]      at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
[deployESBProjects]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[deployESBProjects]      at java.lang.reflect.Method.invoke(Method.java:597)
[deployESBProjects]      at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
[deployESBProjects]      at org.apache.tools.ant.Task.perform(Task.java:348)
[deployESBProjects]      at org.apache.tools.ant.Target.execute(Target.java:390)
[deployESBProjects]      at org.apache.tools.ant.Target.performTasks(Target.java:411)
[deployESBProjects]      at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1397)
[deployESBProjects]      at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
[deployESBProjects]      at org.apache.tools.ant.Project.executeTargets(Project.java:1249)
[deployESBProjects]      at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:442)
[deployESBProjects]      at org.apache.tools.ant.taskdefs.SubAnt.execute(SubAnt.java:302)
[deployESBProjects]      at org.apache.tools.ant.taskdefs.SubAnt.execute(SubAnt.java:221)
[deployESBProjects]      at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
[deployESBProjects]      at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
[deployESBProjects]      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[deployESBProjects]      at java.lang.reflect.Method.invoke(Method.java:597)
[deployESBProjects]      at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
[deployESBProjects]      at org.apache.tools.ant.Task.perform(Task.java:348)
[deployESBProjects]      at org.apache.tools.ant.Target.execute(Target.java:390)
[deployESBProjects]      at org.apache.tools.ant.Target.performTasks(Target.java:411)
[deployESBProjects]      at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1397)
[deployESBProjects]      at org.apache.tools.ant.Project.executeTarget(Project.java:1366)
[deployESBProjects]      at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
[deployESBProjects]      at org.apache.tools.ant.Project.executeTargets(Project.java:1249)
[deployESBProjects]      at org.apache.tools.ant.Main.runBuild(Main.java:801)
[deployESBProjects]      at org.apache.tools.ant.Main.startAnt(Main.java:218)
[deployESBProjects]      at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
[deployESBProjects]      at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
[subant] Exiting C:\source\NeoZESBV2\SOA-001_CGP_SOA-003_OAP\build.xml.
And now I'm stuck. I understand what the errors mean, but I don't know how to proceed. I checked the credentials and they're okay -- the same as used by jDeveloper.
Any pointers would be greatly appreciated.
Edited by SQB on 22-nov-2010 15:09: Formatting error messages.
Edited by SQB on 22-nov-2010 15:12: Undoing formatting of the stacktraces since it forces the right side of the page off the screen.

The contents of my ESBMetadataMigrationTaskdefs.xml:<project name="ESBMetadataMigrationTaskdefs"
         xmlns="antlib:org.apache.tools.ant">

<property name="esbdeployment.home"
            value="../lib/ESB"/>
<property name="commons.home"
            value="../lib"/>
<property name="jaxb.home"
            value="../lib"/>
<property name="soa.suite.home"
            value="C:/Program Files/Oracle/jDeveloper/"/>
<property name="lib.esb.metadatamigration"
            value="${esbdeployment.home}/ESBMetadataMigration.jar"/>
<property name="lib.commons.httpclient"
            value="${commons.home}/commons-httpclient-3.1.jar"/>
<property name="lib.commons.logging"
            value="${commons.home}/commons-logging-1.1.1.jar"/>
<property name="lib.commons.codec"
            value="${commons.home}/commons-codec-1.4.jar"/>
<property name="lib.esb.oraesb"
            value="${soa.suite.home}/integration/esb/lib/oraesb.jar"/>
<property name="lib.jaxb.activation"
            value="${soa.suite.home}/j2ee/home/lib/activation.jar"/>
<property name="lib.jaxb.api"
            value="${soa.suite.home}/adfp/lib/jaxb-api.jar"/>
<property name="lib.jaxb.jsr.api"
            value="${soa.suite.home}/integration/lib/jsr173_1.0_api.jar"/>
<property name="lib.jaxb.impl"
            value="${soa.suite.home}/adfp/lib/jaxb-impl.jar"/>
<property name="lib.xmlparser"
            value="${soa.suite.home}/lib/xmlparserv2.jar"/>

<dirname property="imported.basedir"
           file="${ant.file.ESBMetadataMigrationTaskdefs}"/>
<taskdef resource="oracle/tip/esb/client/anttasks/antlib.xml">
    <classpath>
      <pathelement location="${lib.esb.metadatamigration}"/>
      <pathelement location="${lib.commons.httpclient}"/>
      <pathelement location="${lib.commons.logging}"/>
      <pathelement location="${lib.commons.codec}"/>
      <pathelement location="${lib.esb.oraesb}"/>
      <pathelement location="${lib.jaxb.activation}"/>
      <pathelement location="${lib.jaxb.api}"/>
      <pathelement location="${lib.jaxb.jsr.api}"/>
      <pathelement location="${lib.jaxb.impl}"/>
      <pathelement location="${lib.xmlparser}"/>
    </classpath>
</taskdef>
</project>When running -verbose, I get no complaints about jars not found or anything. Output from that is:Apache Ant version 1.8.1 compiled on April 30 2010
Trying the default build file: build.xml
Buildfile: C:\source\NeoZESBV2\SOA_deploy\build.xml
Detected Java version: 1.6 in: C:\Program Files\Java\jdk1.6.0_17\jre
Detected OS: Windows XP
parsing buildfile C:\source\NeoZESBV2\SOA_deploy\build.xml
      with URI = file:/C:/source/NeoZESBV2/SOA_deploy/build.xml
Project base dir set to: C:\source\NeoZESBV2\SOA_deploy
parsing buildfile jar:file:/C:/Program%20Files/Oracle/jDeveloper/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
      with URI = jar:file:/C:/Program%20Files/Oracle/jDeveloper/ant/lib/ant.jar!/org/apache/tools/ant/antlib.xml
      from a zip file
[property] Loading C:\source\NeoZESBV2\SOA_deploy\build.properties
Importing file C:\source\NeoZESBV2\SOA_deploy\copy.scriptdef.xml
      from C:\source\NeoZESBV2\SOA_deploy\build.xml
parsing buildfile C:\source\NeoZESBV2\SOA_deploy\copy.scriptdef.xml
      with URI = file:/C:/source/NeoZESBV2/SOA_deploy/copy.scriptdef.xml
Importing file C:\source\NeoZESBV2\SOA_deploy\ESBMetadataMigrationTaskdefs.xml
      from C:\source\NeoZESBV2\SOA_deploy\build.xml
parsing buildfile C:\source\NeoZESBV2\SOA_deploy\ESBMetadataMigrationTaskdefs.xml
      with URI = file:/C:/source/NeoZESBV2/SOA_deploy/ESBMetadataMigrationTaskdefs.xml
parsing buildfile jar:file:/C:/source/NeoZESBV2/lib/ESB/ESBMetadataMigration.jar!/oracle/tip/esb/client/anttasks/antlib.xml
      with URI = jar:file:/C:/source/NeoZESBV2/lib/ESB/ESBMetadataMigration.jar!/oracle/tip/esb/client/anttasks/antlib.xml
      from a zip file
Build sequence for target(s) `undeploy' is [init, undeploy]
Complete build sequence is [init, undeploy, prepare, clean_build_xml, post_build_cleanup, deploy_all, deploy, ]
init:
     [echo] Target ESB:   zlm-esbob
     [echo] ESB soort:    ontwikkel_test
     [echo] Productie:    nee
     [echo] ABZ Audascan: demo
     [echo] ABZ overig:   demo
undeploy:
[undeployESBEntities] Undeploying specified ESB Systems
[undeployESBEntities]       guid=<7A4142808A9D11DFBF8C9DA3034837B5> ...after which the error occurs.
I found no useful logging on the server; is there any specific place I should look and may have overlooked?
Edited by: SQB on 24-nov-2010 9:57 (formatting)

Unable to deploy after added adf binding

I want to call a BPEL process from Java so I added a adf binding as detailed in this article
http://blogs.oracle.com/jaylee/2009/08/invoking_composite_from_javajs.html
But when I deployed it using JDeveloper 11.1.1.2, I got the below error
Error during composite deployment: oracle.fabric.common.FabricDeploymentException: oracle.fabric.common.FabricException: Update Failed: Binding component failed to register Metadata types with SDO provider.: Cannot read WSDL "{http://xmlns.oracle.com/LineItem/LineItemProcessEventList}LineItemProcessEventList" from Metadata Manager.: Update Failed: Binding component failed to register Metadata types with SDO provider.: Cannot read WSDL "{http://xmlns.oracle.com/LineItem/LineItemProcessEventList}LineItemProcessEventList" from Metadata Manager..
I tried it with other BPEL processes and it worked fine. Only this one has this issue.
Do you have any ideas?

sorry i just notice you're using standalone version. can you see any errors/stack trace in your command-line console? can you post the exception stack trace?
Edited by: rhp on Aug 4, 2010 1:49 PM

Unable to deploy example 'banking' application on weblogic, please help...

Hi,
I have downloaded the example 'banking.zip' and have installed it.
I have followed all given steps in the tutorial, but I am unable to
see the login page.
I am also not able to see the ejb and web application descriptor file
from the admin console.
I have copied the banking directory to
'$WEBLOGIC\config\mydomain\applications'.
There are 3 directories under it
(1) ejb (containing meta-inf and examples directory. Meta-info
contains the descriptor .xml files)
(2) web (containing web-inf and html,jsp and image files. Web-inf
contains weblogic.xml and web.xml)
(3) Meta-Inf (containing the application.xml)
I get the 'Error 404--Not Found' error when I go to
http://localhost:8001/banking/login.html. (my server is running on
8001 port, i hope this doesn't matter)
When I try to edit the web application descriptor I get the following
error
java.lang.NullPointerException
     at weblogic.management.console.utils.MBeans.getMBeanClassFor(MBeans.java:860)
     at weblogic.management.console.actions.internal.ActionUtils.getAreaFor(ActionUtils.java:142)
     at weblogic.management.console.actions.mbean.MBeanDescriptorFramesetAction.perform(MBeanDescriptorFramesetAction.java:133)
     at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:167)
     at weblogic.management.console.actions.internal.ActionServlet.doGet(ActionServlet.java:91)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2456)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2039)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Could someone please help me ? I am trying to deploy this in the
exploded form. My server is running in the development mode.
- Thanks in advance,
Sonali

Hi,
I was able to successfully deploy after installing
weblogic 6.1 SP2 (earlier I had SP1). Also, I had to make
changes in the BankAppServlet code since it tries to find the
bean with a different name than one specified in jndi-name.
- Thanks,
Sonali
[email protected] (Sonali Kale) wrote in message news:<[email protected]>...
Hi,
I have downloaded the example 'banking.zip' and have installed it.
I have followed all given steps in the tutorial, but I am unable to
see the login page.
I am also not able to see the ejb and web application descriptor file
from the admin console.
I have copied the banking directory to
'$WEBLOGIC\config\mydomain\applications'.
There are 3 directories under it
(1) ejb (containing meta-inf and examples directory. Meta-info
contains the descriptor .xml files)
(2) web (containing web-inf and html,jsp and image files. Web-inf
contains weblogic.xml and web.xml)
(3) Meta-Inf (containing the application.xml)
I get the 'Error 404--Not Found' error when I go to
http://localhost:8001/banking/login.html. (my server is running on
8001 port, i hope this doesn't matter)
When I try to edit the web application descriptor I get the following
error
java.lang.NullPointerException
     at weblogic.management.console.utils.MBeans.getMBeanClassFor(MBeans.java:860)
     at weblogic.management.console.actions.internal.ActionUtils.getAreaFor(ActionUtils.java:142)
     at weblogic.management.console.actions.mbean.MBeanDescriptorFramesetAction.perform(MBeanDescriptorFramesetAction.java:133)
     at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:167)
     at weblogic.management.console.actions.internal.ActionServlet.doGet(ActionServlet.java:91)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2456)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2039)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Could someone please help me ? I am trying to deploy this in the
exploded form. My server is running in the development mode.
- Thanks in advance,
Sonali

Unable to deploy a bean

I create the jar file as follows:
java -cp D:\bea\wlserver6.1lib\weblogic.jar weblogic.ejbc -compiler javac D:\working\icechill\classes\ScipBeans.jar D:\bea\wlserver6.1\config\mydomain\applications\ScipBeans.jar
After that I start my weblogic6.1 server and no error is thrown on the screen.
But when I check for the deployed beans, it clearly says that my bean is not deployed:
ScipBeans <UNDEPLOYED>, source: .\config\mydomain\applications components: ScipB
eans
I am not able to do a lookup of my Home object since it is not deployed.
Any help is greatly appreciated. Thanks.

Sai,
I would like you to check a couple of things.
1. Check the process by which you are making the jar file. I had posted this sometime back too :
Make sure that you have followed the steps for making the jar file correctly. For
example if you are working under a folder like
c:\bea\wlserver6.0\samples\examples\ejb\basic\entity ...and the package name is
like examples.ejb.basic.entity make sure that you are making the Naked jar file
from under c:\bea\wlserver6.0\examples ...something like :
c:\bea\wlserver6.0\samples> jar -cvf examples\ejb\basic\entity\lsNkaed.jar
examples\ejb\basic\entity\*.class
c:\bea\wlserver6.0\samples> cd examples\ejb\basic\entity
c:\bea\wlserver6.0\samples\examples\ejb\basic\entity>jar -uvf lsNaked.jar
META-INF\
c:\bea\wlserver6.0\samples\examples\ejb\basic\entity>java weblogic.ejbc
lsNaked.jar entityEJB.jar
2. How are you deploying the bean? If you are using the AutoDeployment (and copying the jar file under the applications directory before you start the weblogic) feature then make
sure that you are running in Development mode. This can be checked in your startweblogic script.
3. If you are deploying from the browser console then make sure that the target is selected.
4. If you still are having problems , although I'll doubt that, change the logging level from the browser console to "Info" from the default setting which is "Error", and check the
stack trace.
Thanks,
Sai S Prasad wrote:
I create the jar file as follows:
java -cp D:\bea\wlserver6.1lib\weblogic.jar weblogic.ejbc -compiler javac D:\working\icechill\classes\ScipBeans.jar D:\bea\wlserver6.1\config\mydomain\applications\ScipBeans.jar
After that I start my weblogic6.1 server and no error is thrown on the screen.
But when I check for the deployed beans, it clearly says that my bean is not deployed:
ScipBeans <UNDEPLOYED>, source: .\config\mydomain\applications components: ScipB
eans
I am not able to do a lookup of my Home object since it is not deployed.
Any help is greatly appreciated. Thanks.--
Apurb Kumar

Error Exception activating module: EJBModule(p13n_ejb.jar) Unable to deploy

Dears ,
i'm facing this exception when try to activate changes after portal Ear deployment please help ???
Message icon - Error An error occurred during activation of changes, please see the log for details.
Message icon - Error Exception activating module: EJBModule(p13n_ejb.jar) Unable to deploy EJB: TrackedAnonymous from p13n_ejb.jar: Internal error: Cannot obtain XAConnection weblogic.common.resourcepool.ResourceDeadException: Pool portalDataSource has been disabled because of hanging connection tests, cannot allocate resources to applications. We waited 10010 milliseconds. A typical test has been taking 1209 at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1540) at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1496) at weblogic.common.resourcepool.ResourcePoolImpl.reserveResourceInternal(ResourcePoolImpl.java:375) at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:332) at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:433) at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:316) at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:93) at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:61) at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:1584) at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1357) at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:438) at weblogic.jdbc.jta.DataSource.connect(DataSource.java:395) at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:355) at weblogic.ejb.container.cmp.rdbms.RDBMSPersistenceManager.getConnection(RDBMSPersistenceManager.java:4028) at weblogic.ejb.container.cmp.rdbms.RDBMSPersistenceManager.verifyDatabaseType(RDBMSPersistenceManager.java:4250) at weblogic.ejb.container.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:261) at weblogic.ejb.container.manager.BaseEntityManager.setupPM(BaseEntityManager.java:300) at weblogic.ejb.container.manager.BaseEntityManager.setup(BaseEntityManager.java:249) at weblogic.ejb.container.manager.DBManager.setup(DBManager.java:172) at weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1166) at weblogic.ejb.container.deployer.EntityBeanInfoImpl.activate(EntityBeanInfoImpl.java:238) at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1324) at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:480) at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227) at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:415) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:75) at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:67) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409) at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844) at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253) at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67) 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)
Message icon - Error Substituted for missing class Internal error - Cannot obtain XAConnection weblogic.common.resourcepool.ResourceDeadException: Pool portalDataSource has been disabled because of hanging connection tests, cannot allocate resources to applications. We waited 10010 milliseconds. A typical test has been taking 1209

Hi
As per the below stack trace, looks like the root cause is for some reasons, portal framework Datasources (connection pools) are not able to connect to the Database having portal schema. Make sure that before you deploy, if possible test all the Datasources from weblogic admin console to make sure they are able to communicate with backend portal db schema. There should be a TestConnection for each portal datasource. Or may be there is some network issue preventing access to this database. Once db is connected properly and connection pool testing is fine, then deploy your portal EAR.
"...Cannot obtain XAConnection weblogic.common.resourcepool.ResourceDeadException: Pool portalDataSource has been disabled because of hanging connection tests, cannot allocate resources to applications. We waited 10010 milliseconds..."
HTH
Ravi Jegga

EJBs still bound even after undeploying application

Hi,
I am using WebLogic 10.0 MP2 notice that if I undeploy an ear containing Stateless Session EJBs there are still entries for these EJBs in the JNDI server tree. The entries look like <name of Bean>#<full package name of Bean>.
I am undeploying using the WebLogic Console (Deployments->Delete) and see in the log that the deployment goes from STATE_PREPARED to STATE_NEW.
I can fix the issue by deleting the EJBCompilerCache directory but would like to know why they don't get removed as part of the undeploy.
Thanks for any help
Mandy

Hi,
Not I'm not using the autodeploy directory, I am uploading from my local machine to the uploads/ directory.
I don't seem to get any problems when I redeploy the application in a single server but on a cluster I get this issue..
<01-Dec-2010 23:04:35 o'clock GMT> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '129124****2336' for task '19'. Error is: 'weblogic.application.ModuleException: Exception activating module: EJBModule(sampleejbs-ejb-0.0.1-SNAPSHOT.jar)
Unable to deploy EJB: JmsAPIConnPoolSonicJmsStatelessSessionBean from sampleejbs-ejb-0.0.1-SNAPSHOT.jar:
[EJB:011008]Unable to bind EJB Home Interface to the JNDI name: sampleejbs-ear-0sampleejbs-ejb-0_0_1-SNAPSHOT_jarJmsAPIConnPoolSonicJmsStatelessSessionBean_HOME.
javax.naming.NameAlreadyBoundException: sampleejbs-ear-0sampleejbs-ejb-0_0_1-SNAPSHOT_jarJmsAPIConnPoolSonicJmsStatelessSessionBean_HOME is already bound; remaining name ''and this:
<01-Dec-2010 23:04:35 o'clock GMT> <Error> <Cluster> <BEA-000123> <Conflict start: You tried to bind an object under the name WLPooledWLJmsStatelessSessionBean#com.xx.xxx.test.samples.JmsMessageSender in the JNDI tree. The object from -769998****8669S:xxx05bb01-wl01:[7021,7021,-1,-1,-1,-1,-1]:jcrxxbus1:xxx05bb01-bus1 is non-clusterable, and you have tried to bind more than once from two or more servers. Such objects can only be deployed from one server.>Any ideas much appreciated!
Many thanks
Mandy

Unable to deploy EJB: TrackedAnonymous from p13n_ejb.jar:

Hi,
I installed the weblogic portal 10.3.2 and configured the domain to use oracle express edition 11g. After configuring the domain, i got the error saying the weblogic server could not start because of tables does not exist. so i changed the database.properties and executed the create_db.cmd to create the tables and the server is started now.
when i tried to deploy the weblogic portal application, i got the following error,
<Aug 10, 2010 12:35:57 PM IST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Aug 10, 2010 12:37:44 PM IST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1281424006937' for task '0'. Error is: 'weblogic.application.ModuleException: Exception activating module: EJBModule(p13n_ejb.jar)
Unable to deploy EJB: TrackedAnonymous from p13n_ejb.jar:
[EJB:011028]The DataSource with the JNDI name: weblogic.jdbc.jts.commercePool could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
weblogic.application.ModuleException: Exception activating module: EJBModule(p13n_ejb.jar)
Unable to deploy EJB: TrackedAnonymous from p13n_ejb.jar:
[EJB:011028]The DataSource with the JNDI name: weblogic.jdbc.jts.commercePool could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
     at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:501)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:415)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:75)
     Truncated. see log file for complete stacktrace
Caused By: [EJB:011028]The DataSource with the JNDI name: weblogic.jdbc.jts.commercePool could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
     at weblogic.ejb.container.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:251)
     at weblogic.ejb.container.manager.BaseEntityManager.setupPM(BaseEntityManager.java:300)
     at weblogic.ejb.container.manager.BaseEntityManager.setup(BaseEntityManager.java:249)
     at weblogic.ejb.container.manager.DBManager.setup(DBManager.java:172)
     at weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1166)
     Truncated. see log file for complete stacktrace
>
<Aug 10, 2010 12:37:44 PM IST> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application 'MyPortalEAR'.>
<Aug 10, 2010 12:37:44 PM IST> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'MyPortalEAR'.>
<Aug 10, 2010 12:37:44 PM IST> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException: Exception activating module: EJBModule(p13n_ejb.jar)
Unable to deploy EJB: TrackedAnonymous from p13n_ejb.jar:
[EJB:011028]The DataSource with the JNDI name: weblogic.jdbc.jts.commercePool could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
     at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:501)
     at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:415)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
     at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:75)
     Truncated. see log file for complete stacktrace
Caused By: [EJB:011028]The DataSource with the JNDI name: weblogic.jdbc.jts.commercePool could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
     at weblogic.ejb.container.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:251)
     at weblogic.ejb.container.manager.BaseEntityManager.setupPM(BaseEntityManager.java:300)
     at weblogic.ejb.container.manager.BaseEntityManager.setup(BaseEntityManager.java:249)
     at weblogic.ejb.container.manager.DBManager.setup(DBManager.java:172)
     at weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:1166)
     Truncated. see log file for complete stacktrace
>
<Aug 10, 2010 12:37:56 PM IST> <Warning> <Deployer> <BEA-149252> <No deployment 'MyPortalEAR' found for Operation stop.>
Please guide me to resolve this issue.
Thanks a lot,
Suresh
Edited by: user5701346 on Aug 10, 2010 10:34 PM

I changed target for DataSource from AdminServer to my managed Server. That solved the problem.

Reg: Unable to deploy .ear file in weblogic 9.0

Hi,
I am a developer worked with Weblogic 6.0 and we are planning to upgrade to WLS9.0. But after installation and successful configuration of domain, we are unable to deploy the.ear file.
Thanks in advance
Here is the erroe message:
Messages
Unable to access the selected application.
[J2EE Deployment SPI:260101]Parameter may not be null. java.lang.NullPointerException at weblogic.deploy.api.internal.utils.ConfigHelper.checkParam(ConfigHelper.java:126) at weblogic.deploy.api.tools.ModuleInfo.createModuleInfo(ModuleInfo.java:82) at weblogic.deploy.api.tools.SessionHelper.getModuleInfo(SessionHelper.java:559) at com.bea.console.actions.app.install.Flow.appSelected(Flow.java:433) 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:585) at org.apache.beehive.netui.pageflow.FlowController.invokeActionMethod(FlowController.java:812) at org.apache.beehive.netui.pageflow.FlowController.getActionMethodForward(FlowController.java:751) at org.apache.beehive.netui.pageflow.FlowController.internalExecute(FlowController.java:434) at org.apache.beehive.netui.pageflow.PageFlowController.internalExecute(PageFlowController.java:245) at org.apache.beehive.netui.pageflow.FlowController.execute(FlowController.java:316) at org.apache.beehive.netui.pageflow.internal.FlowControllerAction.execute(FlowControllerAction.java:48) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:484) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processActionPerform(PageFlowRequestProcessor.java:1948) at com.bea.console.internal.ConsolePageFlowRequestProcessor.processActionPerform(ConsolePageFlowRequestProcessor.java:184) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:274) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.processInternal(PageFlowRequestProcessor.java:590) at org.apache.beehive.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:840) at org.apache.beehive.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:607) at org.apache.beehive.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:135) at com.bea.console.internal.ConsoleActionServlet.process(ConsoleActionServlet.java:241) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507) at com.bea.console.internal.ConsoleActionServlet.doGet(ConsoleActionServlet.java:130) at org.apache.beehive.netui.pageflow.PageFlowUtils.strutsLookup(PageFlowUtils.java:927) at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.executeAction(ScopedContentCommonSupport.java:571) at com.bea.portlet.adapter.scopedcontent.ScopedContentCommonSupport.processActionInternal(ScopedContentCommonSupport.java:122) at com.bea.portlet.adapter.scopedcontent.PageFlowStubImpl.processAction(PageFlowStubImpl.java:98) at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:149) at com.bea.netuix.servlets.controls.content.NetuiContent.raiseScopedAction(NetuiContent.java:108) at com.bea.netuix.servlets.controls.content.NetuiContent.handlePostbackData(NetuiContent.java:223) at com.bea.netuix.nf.ControlLifecycle$2.visit(ControlLifecycle.java:169) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:290) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:300) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:300) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:300) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:300) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:300) at com.bea.netuix.nf.ControlTreeWalker.walkRecursive(ControlTreeWalker.java:300) at

Hello,
I try to deploy an ear file (contains jar and war files) in Oracle Application server in linux, but the time is so long. The same file I deploy in a OAS in windows and the deploy time was 2 minutes, but in linux I leave the hole night and the session close and the deploy in unable.
I don't know if I need configure an especial option in the OAS in Linux, how I can load my ear file.
The OAS in windows was installed with oc4j options only, but the OAS in linux was full installation
Please help me....
Thanks.

Unable to deploy

Hi Everyone.
I am running a weblogic cluster with an administrative server and two managed servers on one machine and two managed servers on the other.When i try to deploy the application to the cluster,i get the following error
[Deployer:149033]preparing application saba on ServerOne
[Deployer:149033]preparing application saba on RemoteServerThree
[Deployer:149033]preparing application saba on RemoteServerFour
[Deployer:149033]preparing application saba on ServerTwo
[Deployer:149033]failed application saba on ServerOne
[Deployer:149034]An exception occurred for task [Deployer:149026]Deploy application saba on sabacluster.:
Exception:weblogic.management.ApplicationException: prepare failed for saba_EJB.jar
Module: saba_EJB.jar Error: Exception preparing module: EJBModule(saba_EJB.jar,status=NEW)
Unable to deploy EJB: ./ServerOne/stage/saba/saba_EJB.jar from saba_EJB.jar:
[EJB:010106]EJB : PersistenceMetadataManager .Unable to initialize method info for remote or home interface. The error is java.lang.NoClassDefFoundError: com/saba/exception/SabaException
at java.lang.Class.getDeclaredMethods0(Native Method)
at java.lang.Class.privateGetDeclaredMethods(Class.java(Compiled Code))
at java.lang.Class.privateGetPublicMethods(Class.java(Compiled Code))
at java.lang.Class.getMethods(Class.java:909)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.initializeMethodInfos(ClientDrivenBeanInfoImpl.java:1249)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.<init>(ClientDrivenBeanInfoImpl.java:272)
at weblogic.ejb20.deployer.SessionBeanInfoImpl.<init>(SessionBeanInfoImpl.java:74)
at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl.java:367)
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:548)
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:232)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1324)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2513)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2463)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2379)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java(Compiled Code))
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java(Compiled Code))
. NestedException Message is :com/saba/exception/SabaException
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.initializeMethodInfos(ClientDrivenBeanInfoImpl.java:1255)
at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.<init>(ClientDrivenBeanInfoImpl.java:272)
at weblogic.ejb20.deployer.SessionBeanInfoImpl.<init>(SessionBeanInfoImpl.java:74)
at weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl.java:367)
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:548)
at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:232)
at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1324)
at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:498)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3142)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1583)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1070)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2513)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2463)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2379)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java(Compiled Code))
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java(Compiled Code))
Please help :-)

Hmm, hard to tell. I use RHEL 4 a lot and that never happened to me.
Could you check $AS_HOME/opmn/logs/default_group~home~default_group~1.log for lines with Undeploy?
--olaf

Unable to deploy single SERVERCORE component using telnet?

Hi,
As continued to the discussion of "
Undeploying .SCA/ .SDA / .EAR / .WAR files on J2EE servers on Netweaver release 7.1 and higher"
I am trying to deploy one of the CORE component "SERVERCORE" using "TELNET" on my SAP NW7.3 EHP1 System but getting error that " SCA's aborted"
and unable to deploy the component. Please help me to get out of this.

Hi Chandra,
Sorry i did not understand your last reply. When you load all the core SCAs (put them into and folder) and then trigger the telnet option, the tool itself will take care of the dependencies and deploy the SCAs in the correct manner.
What was the error you were getting when you tried this?
You mentioned:
Did same using telnet as mentioned you and didn't update SPS to latest.
still they showing same as previous.
Does that mean that the deployment went fine, but still system info etc. shows old values? This is VERY strange. You can get the latest list from the configtool. Just check the attached screenshot for an example.
If this still shows old version, please run the force bootstrap once:
1)
Stop the j2ee server. Under cluster directory (/usr/sap/<SID>/J<nr>/cluster) rename server0 and subsequent nodes to ".old" respectively. The intention here is to create a backup of the existing files. Do not rename the bootstrap folder as this is needed for the sync process.
2)
Change bootstrap.properties file to ensure it has element.resynch=force as per SAP note 710663.
3)
Restart the J2EE Engine. The new server folders should be created during the bootstrapping and this is a time consuming process as all the contents of the server nodes will be syched with the DB content.
4)
Remove the element.resynch=force property or change it to element.resynch=detect which is the default setting.
Regards,
Hemanth

Unable to Deploy an ASO Essbase cube in EPMA

Hi All,
I am having issues while deploying an ASO essbase cube application in EPMA.
1.Have created a new Essbase ASO cube application
2.Created an basic outline about 10 dimensions
3.Validated it successfully
4.When i deploy it starts the initiation and after sometime it comes up with Below Error message
Detail: Initiating product Action
Generating Headers and callback information
Posting Product request
Connection timed out: Connect
I have created an Empty ASO application and selected the sot order..It validates fine, But unable to Deploy..same error message

This issue is seen only with IBM JDK 1.6 (any SR) because, IBM packages the xerces version 2.9 as a part of $IBM_JDK_HOME/jre/lib/xml.jar.
I think/understand that, your application is also packaging a xerces impl jar(different version otherthan xerces version 2.9) in WEB-INF/lib of you application.
So, to make sure that the WebLogic Server uses the xerces impl jar that has been packaged, you are trying to use the filtered classloader in weblogic-application.xml
But the filtered classloader would not have any effect, since, the IBM JDK packaged xerces parsers would also be with the same package structure. So, I think you should try with setting the following in WEB-INF/weblogic.xml inside the <weblogic-web-app> tag.
<container-descriptor>
<prefer-web-inf-classes>true</prefer-web-inf-classes>
</container-descriptor>
I think this should work with WLS 11gR1PS2 (WLS 10.3.3).

Unable to deploy apps to SharePoint: "Operation took too long"

Hi, I am currently developing a SharePoint application. Until recently I was able to deploy my application without any issues. However, I have been unable to deploy any custom application to SharePoint over the last couple of days. Installation of custom
applications now seems to hang for about 15 minutes before the server responds with an error message "The operation took too long." I am perplexed, as the deployment process has been working fine made I have made no major changes to my application.
Please let me know if you have any ideas!
Thanks

Hi Venktesh,
Thanks for your prompt response.
Sorry I should have mentioned this earlier.
I am getting error at this line...
p_clob := p_clob || UTL_RAW.cast_to_varchar2 (UTL_ENCODE.base64_encode (DBMS_LOB.SUBSTR (l_bfile, ncurrent_pointer, l_step)));
This loop runs for around 5 times i.e. 5000 * 4 = 20000 and then errors out after that.
If size of my image is below 23000, it works fine.
Still do you think it is related to BFILE. Actually BFILE operation works successfully for around 4 times.

Unable to deploy from Eclipse - Runner class cannot be initialized

Hello
two days ago, I installed the newest versions of Glassfish Tools together with the newest Eclipse Luna SR1
when trying to deploy, I am getting the following error message:
org.glassfish.tools.ide.admin.CommandException: Cannot initialize Runner class
at org.glassfish.tools.ide.admin.AdminFactory.newRunner(AdminFactory.java:180)
at org.glassfish.tools.ide.admin.AdminFactoryHttp.getRunner(AdminFactoryHttp.java:110)
at org.glassfish.tools.ide.admin.ServerAdmin.exec(ServerAdmin.java:75)
at oracle.eclipse.tools.glassfish.GlassfishServerBehaviourDelegate.publishDeployedDirectory(GlassfishServerBehaviourDelegate.java:608)
at oracle.eclipse.tools.glassfish.GlassfishV4ServerBehavior.publishModuleForGlassFishV3(GlassfishV4ServerBehavior.java:96)
at oracle.eclipse.tools.glassfish.GlassfishV4ServerBehavior.publishModule(GlassfishV4ServerBehavior.java:56)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1091)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1183)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:987)
at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3157)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
the same application works if deployed directly to the glassfish server
I did all the suggestions as mentioned in Unable to deploy app form Eclipse Luna on Glassfish 4.0 or 4.1 with JDK8 but without success.
Does anybody has an idea what the problem could be and how to track it down?
Thanks a lot!

Hello Kostas
Thanks a lot for your help and hints! I am running Windows 7 64 Bit
I had Java 8, once with Release 20 and once with Release 25, installed - and thought that I pointed all to the newest version.
What helped in the end was to
- deinstall all Javas
- reboot
- installed newest JDK, without the "Public JRE"
- reboot
- set JAVA_HOME and appended the Java-bin-dir to the path-Variable
- reboot
- installed a fresh version of Glassfish
- configured a new Glassfish-Server on Eclipse
-> and now it runs perfectly!
Thanks again for your work and hints!

Unable to deploy Web App in Exploded format

Using WLS 6.1 sp2, I am unable to deploy a web application successfully using the
web app "ora" from http://www.thejspbook.com/examples.jspbook.zip. I've moved
the /ora directory under the /WEB-INF/applications directory.
The error I am getting is:
java.lang.reflect.InvocationTargetException: weblogic.management.DistributedManagementException:
Distributed Management [1 exceptions]
     at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:543)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy9.addDeployment(Unknown Source)
     at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
     at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
     at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
     at $Proxy18.setTargets(Unknown Source)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
     at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
     at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
     at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2503)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Distributed update exception
- remote object: efs-developer3:Location=efsserver,Name=efsserver,Type=ServerConfig
- remote server: weblogic.management.internal.RemoteMBeanServerImpl@5420eb
- actionName: addDeployment
- params: [Ljava.lang.Object;@10c03e
- signature: [Ljava.lang.String;@3d4a20
Distributed update exception
- remote object: efs-developer3:Location=efsserver,Name=efsserver,Type=ServerConfig
- remote server: weblogic.management.internal.RemoteMBeanServerImpl@5420eb
java.lang.StringIndexOutOfBoundsException: String index out of range: -1
     at java.lang.String.substring(String.java:1525)
     at weblogic.servlet.internal.WebAppHelper.resolveManifestName(WebAppHelper.java:476)
     at weblogic.servlet.internal.WebAppHelper.extractClassFiles(WebAppHelper.java:232)
     at weblogic.servlet.internal.WebAppServletContext.extractClassFiles(WebAppServletContext.java:3415)
     at weblogic.servlet.internal.WebAppServletContext.setDocroot(WebAppServletContext.java:3384)
     at weblogic.servlet.internal.WebAppServletContext.init(WebAppServletContext.java:862)
     at weblogic.servlet.internal.WebAppServletContext.(WebAppServletContext.java:815)
     at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:428)
     at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
     at weblogic.j2ee.Application.addComponent(Application.java:163)
     at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
     at weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:76)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy34.addWebDeployment(Unknown Source)
     at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeployment(WebServerMBean_CachingStub.java:1121)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:315)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy9.addDeployment(Unknown Source)
     at weblogic.management.internal.DynamicMBeanImpl.updateDeployments(DynamicMBeanImpl.java:1516)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:895)
     at weblogic.management.internal.DynamicMBeanImpl.setAttribute(DynamicMBeanImpl.java:847)
     at weblogic.management.internal.ConfigurationMBeanImpl.setAttribute(ConfigurationMBeanImpl.java:295)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1356)
     at com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
     at weblogic.management.internal.MBeanProxy.setAttribute(MBeanProxy.java:322)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:204)
     at $Proxy18.setTargets(Unknown Source)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.console.info.FilteredMBeanAttribute.doSet(FilteredMBeanAttribute.java:92)
     at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:135)
     at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
     at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2503)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
--------------- nested within: ------------------
weblogic.j2ee.DeploymentException: Could not load ora - with nested exception:
[java.lang.StringIndexOutOfBoundsException: String index out of range: -1]
     at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:431)
     at weblogic.j2ee.WebAppComponent.deploy(WebAppComponent.java:74)
     at weblogic.j2ee.Application.addComponent(Application.java:163)
     at weblogic.j2ee.J2EEService.addDeployment(J2EEService.java:117)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
     at weblogic.management.mbeans.custom.WebServer.addWebDeployment(WebServer.java:76)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy34.addWebDeployment(Unknown Source)
     at weblogic.management.configuration.WebServerMBean_CachingStub.addWebDeployment(WebServerMBean_CachingStub.java:1121)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:315)
     at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:144)
     at java.lang.reflect.Method.invoke(Native Method)
     at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
     at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.ConfigurationMBeanImpl.updateConfigMBeans(ConfigurationMBeanImpl.java:491)
     at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:361)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
     at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
     at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
     at $Proxy9.--------------- nested within: ------------------
weblogic.management.console.utils.SetException: An error occurred while updating
Targets-Server on Proxy for efs-developer3:Application=ora,Name=ora,Type=WebAppComponent
- with nested exception:
[java.lang.reflect.InvocationTargetException - with target exception:
[weblogic.management.DistributedManagementException: Distributed Management [1
exceptions]]]
     at weblogic.management.console.actions.mbean.DoEditMBeanAction.perform(DoEditMBeanAction.java:151)
     at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
     at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2503)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Any help is appreciated.
Thanks,
Dennis

you are probably using a older version of 6.1. please use the latest service pack. Service Packs are mostly bug fix releases and they are safe to be upgraded even on production systems. Please note - we always recommend using the latest service pack
http://www.sun.com/download/products.xml?id=47d5d3eb

Unable to deploy after undeploy...

Similar Messages

Maybe you are looking for