Problem while Deploying application in weblogic admin console

Hi all,
Recently i got an issue while deploying application through weblogic admin console,
I have logged in the weblogic console and clicked on the deployment option, i got the page of install the application, then i have click the install option, i was getting the page of blank white screen. checking the log file of the admin server i cannot find any error. The admin server was running state was ok. before many times i have done deploying application in the same weblogic admin console.
My weblogic 10.3 was running in windows 2008 r2
Kindly need a help to resolve this problem ASAP.
Regards,
Rakhi

Hi sir,
thanks for ur reply.. but while troubleshooting on this issue i am facing another problem,
The weblogic server is running on windows os box, i have stop the weblogic admin server from the windows services and again started the weblogic admin server, the server was running in proper state and i have open the console and try the same thing clicking on the deployment and install options but the same issue i faced. getting the white blank screen, while trying to refresh the page i cannot get the weblogic console waiting for long time also. again after restarting the server i can get the weblogic console.
Then i have tried in another way, i removed the window services and started the weblogic server from command prompt,after starting the server i have opened the admin console and click on the deployment and install option, it is working fine. i tried the same for many times its working fine. but while starting from windows services the problem i was facing same as blank white screen,
Kindly give me a perfect resolution on this issue. because i was so confused on this part.
Regards,
Rakhi..

Similar Messages

While deploying application in weblogic 10.3 getting following eror

while deploying app into weblogic 10.3 getting following taglib errors please any one cane ensure this....
An error occurred during activation of changes, please see the log for details.
weblogic.application.ModuleException:
Substituted for the exception weblogic.servlet.jsp.CompilationException which lacks a String contructor, original message - footer.jsp:1:5: Invalid tag library. <%@ taglib uri="/WEB-INF/struts-html-el.tld" prefix="html" %> ^----^ footer.jsp:1:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-html-el.tld" prefix="html" %> ^----^ footer.jsp:1:5: Invalid tag library. <%@ taglib uri="/WEB-INF/struts-html-el.tld" prefix="html" %> ^----^ footer.jsp:1:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-html-el.tld" prefix="html" %> ^----^ footer.jsp:2:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/core" prefix="c" %> ^----^ footer.jsp:2:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/core" prefix="c" %> ^----^ footer.jsp:3:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/fmt" prefix="fmt" %> ^----^ footer.jsp:3:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/fmt" prefix="fmt" %> ^----^ footer.jsp:4:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-tiles-el.tld" prefix="tiles" %> ^----^ footer.jsp:4:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-tiles-el.tld" prefix="tiles" %> ^----^ tabset.jsp:1:5: Invalid tag library. <%@ taglib uri="/WEB-INF/struts-tiles-el.tld" prefix="tiles" %> ^----^ tabset.jsp:1:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-tiles-el.tld" prefix="tiles" %> ^----^ tabset.jsp:1:5: Invalid tag library. <%@ taglib uri="/WEB-INF/struts-tiles-el.tld" prefix="tiles" %> ^----^ tabset.jsp:1:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-tiles-el.tld" prefix="tiles" %> ^----^ tabset.jsp:2:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/core" prefix="c" %> ^----^ tabset.jsp:2:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/core" prefix="c" %> ^----^ tabset.jsp:3:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/fmt" prefix="fmt" %> ^----^ tabset.jsp:3:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/fmt" prefix="fmt" %> ^----^ connection.jsp:1:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-html-el.tld" prefix="html" %> ^----^ connection.jsp:1:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-html-el.tld" prefix="html" %> ^----^ connection.jsp:2:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/core" prefix="c" %> ^----^ connection.jsp:2:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/core" prefix="c" %> ^----^ connection.jsp:3:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/fmt" prefix="fmt" %> ^----^ connection.jsp:3:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="http://java.sun.com/jstl/fmt" prefix="fmt" %> ^----^ connection.jsp:4:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-tiles-el.tld" prefix="tiles" %> ^----^ connection.jsp:4:5: No tag library could be found with this URI. Possible causes could be that the URI is incorrect, or that there were errors during parsing of the .tld file. <%@ taglib uri="/WEB-INF/struts-tiles-el.tld" prefix="tiles" %> ^----^ connection.jsp:5:5: Invalid tag library. <%@ taglib uri="/WEB-INF/tb-tags.tld" prefix="tb"%> ^----^ connection.jsp:5:5

Hi Pratik,
Would suggest you to create a "*wlfullclient.jar*" by going through the below link and add it in your weblogic workshop and then try to deploy your application. Also it is always recommended that you should compile the old application again with the new JDK version your new weblogic sever is using.
Tpoic:*Creating a wlfullclient.jar for JDK 1.6 client applications*
http://download.oracle.com/docs/cd/E15051_01/wls/docs103/client/jarbuilder.html#wp1078098
Hope this would help you.
Regards,
Ravish Mody

Getting error while deploying application in weblogic server 9.2

Im getting below error in production in weblogic 9.2 server.
####<Jan 27, 2010 8:17:02 PM AST> <Error> <Deployer> <hpw2k3los01> <LOSWebServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1264612622151> <BEA-149205> <Failed to initialize the application 'NCB_LOS' due to error weblogic.management.DeploymentException: Exception occured while downloading files.
weblogic.management.DeploymentException: Exception occured while downloading files
     at weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload(AppDataUpdate.java:43)
     at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56)
     at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:98)
     at weblogic.deploy.internal.targetserver.BasicDeployment.prepareDataUpdate(BasicDeployment.java:663)
     at weblogic.deploy.internal.targetserver.BasicDeployment.stageFilesForStatic(BasicDeployment.java:706)
     at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:100)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:38)
     at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:177)
     at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
     at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: '192.168.50.5', port: '80'
     at weblogic.net.http.HttpClient.openServer(HttpClient.java:320)
     at weblogic.net.http.HttpClient.openServer(HttpClient.java:375)
     at weblogic.net.http.HttpClient.<init>(HttpClient.java:149)
     at weblogic.net.http.HttpClient.New(HttpClient.java:245)
     at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:160)
     at weblogic.deploy.service.datatransferhandlers.HttpDataTransferHandler.getDataAsStream(HttpDataTransferHandler.java:75)
     at weblogic.deploy.service.datatransferhandlers.DataHandlerManager$RemoteDataTransferHandler.getDataAsStream(DataHandlerManager.java:153)
     at weblogic.deploy.internal.targetserver.datamanagement.AppDataUpdate.doDownload(AppDataUpdate.java:39)
     at weblogic.deploy.internal.targetserver.datamanagement.DataUpdate.download(DataUpdate.java:56)
     at weblogic.deploy.internal.targetserver.datamanagement.Data.prepareDataUpdate(Data.java:98)
     at weblogic.deploy.internal.targetserver.BasicDeployment.prepareDataUpdate(BasicDeployment.java:663)
     at weblogic.deploy.internal.targetserver.BasicDeployment.stageFilesForStatic(BasicDeployment.java:706)
     at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:100)
     at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:38)
     at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:177)
     at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
     at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
     at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
     at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
     at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
     at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
This error is intermittent and comes during deployment.Once we get this error we have restart the server.
Can someone please tell what is the cause of this error?
we dont have any server with Ip '192.168.50.5' as mentioned in the error message.and what exactly is the server trying to download here?
Edited by: user12537931 on Jan 31, 2010 4:09 AM

Hi,
How are you trying to deploy your application on the Server...Using Admin Console...or Using any Script Like WLDeployer?
The issue seems to be related to Http protocol in port 80.
Are you sure that in your Production environment there is not firewall blocking issue...on port 80...?
Some firewall settings rejects any existing connection to be opened for a long time....If your application takes some time, then please check that the firewall doesn't disconnect the existing connection until the deployment time gets over.
<font color=red>Note: </font>Sometimes this kind of issue happens when we try to deploy our application on WebLogic Server...at that time based on the XSD informations available in our DeploymentDescriptors...the Server tries to download those DTDs from the mentioned URIs....
Example:
web.xml has some entries like:
<!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/dtd/web-app_2_3.dtd">
In above case if the Firewall of our production environment Blocks any request to pass through Port 80 (default Http Port) then we get such exceptions.
http://middlewaremagic.com/weblogic/?p=802
Thanks
Jay SenSharma
http://middlewaremagic.com/weblogic (Middleware Magic Is Here)

Problem while deploying BPMN to Weblogic

I am trying to deploy a reasonably complex Oracle BPM application (BPMN) to Weblogic 10.3.4 server installed on RHLinux 5. The issue is I am getting a connection timeout exception in the deployment log and hence the deployment fails.
After googling through, I tried to increase the timeout value of JTA through weblogic console but this did not help.
Following is the deployment log in jDeveloper:
[11:44:33 PM] Preparing to send HTTP request for deployment [11:44:33 PM] Creating HTTP connection to host:localhost, port:7001 [11:44:33 PM] Sending internal deployment descriptor [11:44:33 PM] Sending archive - sca_BPM_rev1.0.jar [12:03:43 AM] Connection to the server timed out. Please check the server log for problems or increase the timeout value. [12:03:43 AM] Error deploying archive sca_BPM_rev1.0.jar to partition "default" on server AdminServer [http://localhost:7001] [12:03:43 AM] HTTP error code returned [-1] [12:03:43 AM] No error message is returned from the server. [12:03:43 AM] Error deploying archive sca_BPM_rev1.0.jar to partition "default" on server AdminServer [http://localhost:7001] [12:03:43 AM] #### Deployment incomplete. ####
Error log from Weblogic Console:
May 19, 2011 12:11:28 AM PDT Error oracle.soa.bpel.engine BEA-000000 Unable to activate process IntraFirmTransfer javax.ejb.EJBException: Transaction Rolledback.: weblogic.transaction.internal.TimedOutException: Transaction timed out after 303 seconds BEA1-0E886C94EA7C131B76F3 at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1748) at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1591) at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1911) at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1501) at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35) at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207) at weblogic.work.ExecuteThread.run(ExecuteThread.java:176) ; nested exception is: weblogic.transaction.internal.TimedOutException: Transaction timed out after 303 seconds BEA1-0E886C94EA7C131B76F3 at weblogic.ejb.container.internal.EJBRuntimeUtils.throwEJBException(EJBRuntimeUtils.java:154) at weblogic.ejb.container.internal.BaseLocalObject.postInvoke1(BaseLocalObject.java:595) at weblogic.ejb.container.internal.BaseLocalObject.__WL_postInvokeTxRetry(BaseLocalObject.java:455) at weblogic.ejb.container.internal.SessionLocalMethodInvoker.invoke(SessionLocalMethodInvoker.java:52) at oracle.bpm.bpmn.engine.ejb.impl.BPMNServerManagerBean_6gbx7k_ICubeServerManagerLocalBeanImpl.deployComponent(Unknown Source) at oracle.fabric.CubeServiceEngine.load(CubeServiceEngine.java:885)
Can someone throw some hints at the possible causes ?

· We tried to set the below configurations, but still we are getting same error.
i. Increased timeout-seconds to 3600 sec in <Oracle Admin console> >>--> Services >>-->JTA.
ii. Increased timeout-secounds to 3600 sec in OracleBPMWorspace >>-->Coniguration.
iii. Increased Stuck-Thread Max Time to 14400 sec in Servers>> admin-server >>-->configuration >>-->tuning.
· Previously the JDeveloper was running in local linux box and weblogic server is running in remote location(@ US). So we thought this may be because of network latency error. Then moved the BPMN project to “weblogic” box itself, still no progre
AdminServer.log
==============
####<May 24, 2011 6:52:22 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-1B1982B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-00000000000010ed> <1306245142257> <BEA-000000> <[MethodDescriptor] MethodDescriptor: Method: getAllDrivers() Transaction attribute: TX_REQUIRED Isolation Level: No Isolation Level Set Tx Timeout: 7200000>
####<May 24, 2011 6:52:22 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-1B1982B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-00000000000010ed> <1306245142257> <BEA-000000> <[MethodDescriptor] needsSecurityCheck: true>
####<May 24, 2011 6:52:22 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-1B1982B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-00000000000010ed> <1306245142257> <BEA-000000> <[MethodDescriptor] subject: principals=[]>
####<May 24, 2011 6:52:22 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-1B1982B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-00000000000010ed> <1306245142258> <BEA-000000> <[MethodDescriptor] Access Allowed.
>
####<May 24, 2011 6:52:28 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1B2D82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-00000000000010f9> <1306245148697> <BEA-000000> <[MethodDescriptor] MethodDescriptor: Method: recordUsage(java.lang.String, java.util.Map, java.util.Set) Transaction attribute: TX_REQUIRED Isolation Level: No Isolation Level Set Tx Timeout: 7200000>
####<May 24, 2011 6:52:28 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1B2D82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-00000000000010f9> <1306245148697> <BEA-000000> <[MethodDescriptor] needsSecurityCheck: true>
####<May 24, 2011 6:52:28 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1B2D82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-00000000000010f9> <1306245148697> <BEA-000000> <[MethodDescriptor] subject: principals=[OracleSystemUser, OracleSystemGroup]>
####<May 24, 2011 6:52:28 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1B2D82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-00000000000010f9> <1306245148698> <BEA-000000> <[MethodDescriptor] Access Allowed.
>
####<May 24, 2011 6:52:29 AM PDT> <Info> <EJB> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1B2D82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-00000000000010f9> <1306245149483> <BEA-010227> <EJB Exception occurred during invocation from home or business: weblogic.ejb.container.internal.StatelessEJBHomeImpl@faf85c7 threw exception: oracle.mds.exception.MDSRuntimeException: The transaction is no longer active - status: 'Rolled back. [Reason=Unknown]'. No further JDBC access is allowed within this transaction.>
####<May 24, 2011 6:52:59 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1B8382B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000111c> <1306245179748> <BEA-000000> <[MethodDescriptor] MethodDescriptor: Method: recordUsage(java.lang.String, java.util.Map, java.util.Set) Transaction attribute: TX_REQUIRED Isolation Level: No Isolation Level Set Tx Timeout: 7200000>
####<May 24, 2011 6:52:59 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1B8382B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000111c> <1306245179749> <BEA-000000> <[MethodDescriptor] needsSecurityCheck: true>
####<May 24, 2011 6:52:59 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1B8382B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000111c> <1306245179749> <BEA-000000> <[MethodDescriptor] subject: principals=[OracleSystemUser, OracleSystemGroup]>
####<May 24, 2011 6:52:59 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1B8382B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000111c> <1306245179749> <BEA-000000> <[MethodDescriptor] Access Allowed.
>
####<May 24, 2011 6:53:00 AM PDT> <Info> <EJB> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1B8382B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000111c> <1306245180538> <BEA-010227> <EJB Exception occurred during invocation from home or business: weblogic.ejb.container.internal.StatelessEJBHomeImpl@faf85c7 threw exception: oracle.mds.exception.MDSRuntimeException: The transaction is no longer active - status: 'Rolled back. [Reason=Unknown]'. No further JDBC access is allowed within this transaction.>
####<May 24, 2011 6:53:22 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-1BC882B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000113b> <1306245202257> <BEA-000000> <[MethodDescriptor] MethodDescriptor: Method: getAllDrivers() Transaction attribute: TX_REQUIRED Isolation Level: No Isolation Level Set Tx Timeout: 7200000>
####<May 24, 2011 6:53:22 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-1BC882B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000113b> <1306245202258> <BEA-000000> <[MethodDescriptor] needsSecurityCheck: true>
####<May 24, 2011 6:53:22 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-1BC882B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000113b> <1306245202258> <BEA-000000> <[MethodDescriptor] subject: principals=[]>
####<May 24, 2011 6:53:22 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-1BC882B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000113b> <1306245202258> <BEA-000000> <[MethodDescriptor] Access Allowed.
>
####<May 24, 2011 6:53:30 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1BE282B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-0000000000001149> <1306245210805> <BEA-000000> <[MethodDescriptor] MethodDescriptor: Method: recordUsage(java.lang.String, java.util.Map, java.util.Set) Transaction attribute: TX_REQUIRED Isolation Level: No Isolation Level Set Tx Timeout: 7200000>
####<May 24, 2011 6:53:30 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1BE282B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-0000000000001149> <1306245210805> <BEA-000000> <[MethodDescriptor] needsSecurityCheck: true>
####<May 24, 2011 6:53:30 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1BE282B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-0000000000001149> <1306245210805> <BEA-000000> <[MethodDescriptor] subject: principals=[OracleSystemUser, OracleSystemGroup]>
####<May 24, 2011 6:53:30 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1BE282B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-0000000000001149> <1306245210805> <BEA-000000> <[MethodDescriptor] Access Allowed.
>
####<May 24, 2011 6:53:31 AM PDT> <Info> <EJB> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1BE282B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-0000000000001149> <1306245211595> <BEA-010227> <EJB Exception occurred during invocation from home or business: weblogic.ejb.container.internal.StatelessEJBHomeImpl@faf85c7 threw exception: oracle.mds.exception.MDSRuntimeException: The transaction is no longer active - status: 'Rolled back. [Reason=Unknown]'. No further JDBC access is allowed within this transaction.>
####<May 24, 2011 6:54:01 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1C3D82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000116e> <1306245241862> <BEA-000000> <[MethodDescriptor] MethodDescriptor: Method: recordUsage(java.lang.String, java.util.Map, java.util.Set) Transaction attribute: TX_REQUIRED Isolation Level: No Isolation Level Set Tx Timeout: 7200000>
####<May 24, 2011 6:54:01 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1C3D82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000116e> <1306245241862> <BEA-000000> <[MethodDescriptor] needsSecurityCheck: true>
####<May 24, 2011 6:54:01 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1C3D82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000116e> <1306245241862> <BEA-000000> <[MethodDescriptor] subject: principals=[OracleSystemUser, OracleSystemGroup]>
####<May 24, 2011 6:54:01 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1C3D82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000116e> <1306245241862> <BEA-000000> <[MethodDescriptor] Access Allowed.
>
####<May 24, 2011 6:54:02 AM PDT> <Info> <EJB> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1C3D82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000116e> <1306245242648> <BEA-010227> <EJB Exception occurred during invocation from home or business: weblogic.ejb.container.internal.StatelessEJBHomeImpl@faf85c7 threw exception: oracle.mds.exception.MDSRuntimeException: The transaction is no longer active - status: 'Rolled back. [Reason=Unknown]'. No further JDBC access is allowed within this transaction.>
####<May 24, 2011 6:54:22 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-1C7D82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000118b> <1306245262257> <BEA-000000> <[MethodDescriptor] MethodDescriptor: Method: getAllDrivers() Transaction attribute: TX_REQUIRED Isolation Level: No Isolation Level Set Tx Timeout: 7200000>
####<May 24, 2011 6:54:22 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-1C7D82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000118b> <1306245262257> <BEA-000000> <[MethodDescriptor] needsSecurityCheck: true>
####<May 24, 2011 6:54:22 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-1C7D82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000118b> <1306245262257> <BEA-000000> <[MethodDescriptor] subject: principals=[]>
####<May 24, 2011 6:54:22 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-1C7D82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-000000000000118b> <1306245262258> <BEA-000000> <[MethodDescriptor] Access Allowed.
>
####<May 24, 2011 6:54:32 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1C9B82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-0000000000001199> <1306245272915> <BEA-000000> <[MethodDescriptor] MethodDescriptor: Method: recordUsage(java.lang.String, java.util.Map, java.util.Set) Transaction attribute: TX_REQUIRED Isolation Level: No Isolation Level Set Tx Timeout: 7200000>
####<May 24, 2011 6:54:32 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1C9B82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-0000000000001199> <1306245272915> <BEA-000000> <[MethodDescriptor] needsSecurityCheck: true>
####<May 24, 2011 6:54:32 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1C9B82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-0000000000001199> <1306245272915> <BEA-000000> <[MethodDescriptor] subject: principals=[OracleSystemUser, OracleSystemGroup]>
####<May 24, 2011 6:54:32 AM PDT> <Debug> <EjbDeployment> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1C9B82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-0000000000001199> <1306245272915> <BEA-000000> <[MethodDescriptor] Access Allowed.
>
####<May 24, 2011 6:54:33 AM PDT> <Info> <EJB> <lxdm400m7> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <OracleSystemUser> <BEA1-1C9B82B49881131B76F3> <a87f0f61cd89079b:379ed2f9:1302218cba3:-8000-0000000000001199> <1306245273701> <BEA-010227> <EJB Exception occurred during invocation from home or business: weblogic.ejb.container.internal.StatelessEJBHomeImpl@faf85c7 threw exception: oracle.mds.exception.MDSRuntimeException: The transaction is no longer active - status: 'Rolled back. [Reason=Unknown]'. No further JDBC access is allowed within this transaction.>

Log4j Error while deploying application in weblogic

Hi All,
I am deploying one web application in weblogic, which uses log4j jar file to write logs. But ahile deploying it shows the following error in weblogic console.
Please help on this.
log4j:ERROR A "org.apache.log4j.RollingFileAppender" object is not assignable to a "org.apache.log4j.Appender" variable.
log4j:ERROR The class "org.apache.log4j.Appender" was loaded by
log4j:ERROR [sun.misc.Launcher$AppClassLoader@169e11] whereas object of type
log4j:ERROR "org.apache.log4j.RollingFileAppender" was loaded by [weblogic.utils.classloaders.ChangeAwareClassLoader@169baee finder: weblogic.utils.classloaders.CodeGenClassFinder@44c4a4 annotation: Server@Server].
log4j:ERROR Could not instantiate appender named "log".
log4j:WARN No appenders could be found for logger (com.servion.citigreece.util.LoggerUtil).
log4j:WARN Please initialize the log4j system properly.
Thanks & Regards,
Raja Mohammed.

Seems like a classic case of having log4j both in the war and the app-server's own libraries.
At least in JBoss this would be fixed by making sure that common/lib's log4j jar is being used (or alternatively, removing that and using the one in the war, but that might not go as smooth).

Error while deploying application to weblogic 10.3

Hello!
I am getting below error while deploying my portal application in weblogic 10.3 server. The application code was migrated in weblogic workshop from version 8.1 SP3. I believe I might be missing some reference of library. If anyone can point out the library or any other solution it would be great!
<BEA-149265> <Failure occurred in the execution of deployment request with ID '1285178452009' for task '2'. Error is: 'java.lang.ClassNotFoundException: com.bea.content.paging.IPagedList'
java.lang.ClassNotFoundException: com.bea.content.paging.IPagedList
     at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:283)
     at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:256)
     at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:54)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
     at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:176)
     at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:35)
     at java.lang.Class.getDeclaredMethods0(Native Method)
     at java.lang.Class.privateGetDeclaredMethods(Class.java:2427)
     at java.lang.Class.getDeclaredMethods(Class.java:1791)
     at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getMethods(BaseJ2eeAnnotationProcessor.java:996)
     at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getMethods(BaseJ2eeAnnotationProcessor.java:984)
     at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.processJ2eeAnnotations(BaseJ2eeAnnotationProcessor.java:98)
     at weblogic.j2ee.dd.xml.J2eeAnnotationProcessor.processJ2eeAnnotations(J2eeAnnotationProcessor.java:37)
     at weblogic.servlet.internal.WebAnnotationProcessorImpl.processServlets(WebAnnotationProcessorImpl.java:228)
     at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:211)
     at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:107)
     at weblogic.servlet.internal.WebAppServletContext.processAnnotations(WebAppServletContext.java:1288)
     at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:413)
     at weblogic.servlet.internal.WebAppServletContext.<init>(WebAppServletContext.java:457)
     at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:414)
     at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:910)
     at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364)
     at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
     at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
     at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
     at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)

Hi Pratik,
Would suggest you to create a "*wlfullclient.jar*" by going through the below link and add it in your weblogic workshop and then try to deploy your application. Also it is always recommended that you should compile the old application again with the new JDK version your new weblogic sever is using.
Tpoic:*Creating a wlfullclient.jar for JDK 1.6 client applications*
http://download.oracle.com/docs/cd/E15051_01/wls/docs103/client/jarbuilder.html#wp1078098
Hope this would help you.
Regards,
Ravish Mody

Changes need to made while deploying Application from WebLogic 8.1 to 10.0

Hi,
We are having our appliction deployed on weblogic 8.1 and now as weblogic 10.0 has been released ,we need to deploy it on 10.0
We are using ANT for building our application and is a three tier application. The front tier is mostly jsp's , html, xslt's etc the middle tier is mostly driven by ejb's and then sql server as the third tier.
Before going to work ,i need a list of specification need to be changed while deploying.It would be a great help to me if somebody lists all the changes i need to make for Weblogic 10.0.
Thanks
__Mukul

Hi,
Thanks a lot for the reply. Max i have migrated jvm as well as deployed my application on wls 10 but it does not seem to recognize the application . After starting the wls10 server it shows insufficient memroy exception as well.
There are lots of changes in the domain directory structure. Like config.xml file is now placed in config folder and the server that u define while configuration is now placed inside a server folder so its kind of hard to figure out what and where exactly the files should be placed and what changes are needed in the config.xml file itself.
Please let me know if you have some suggestion.
Mukul.

Error while deploying application on weblogic server

Hi,
I have created webservice and deployed on weblogic server.
Earlier it was working fine. I added some logger and trying to redeploy it.
But it gives following error.
Weblogic Server Exception: java.lang.NoSuchMethodException: deploy(java.lang.String,java.lang.String,java.lang.String,weblogic.management.deploy.DeploymentData,java.lang.String,java.lang.Boolean,) for com.bea:Name=DeployerRuntime,Type=DeployerRuntime
[12:46:48 AM] See server logs or server console for more details.
[12:46:48 AM] java.lang.NoSuchMethodException: deploy(java.lang.String,java.lang.String,java.lang.String,weblogic.management.deploy.DeploymentData,java.lang.String,java.lang.Boolean,) for com.bea:Name=DeployerRuntime,Type=DeployerRuntime
[12:46:49 AM] #### Deployment incomplete. ####
[12:46:49 AM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
Can anybody help me out..
Thanks in advance.

Hi,
I am newbie for web service Need your help.
I am having well developed webservice project with apache cxf 2.2.3 and working fine on Weblogic server 10.3
But After migration from 10.3 to 10.3.4 Facing below problem.
While calling call back service of third party it is giving warning messages like
12 Apr, 2011 5:42:36 PM weblogic.wsee.jaxws.framework.policy.advertisementimpl.AdvertisementHelperImpl registerExtension
WARNING: Registering oracle.j2ee.ws.wsdl.extensions.addressing.AddressingExtensionRegistry extension failed; java.lang.NoSuchMethodException: oracle.j2ee.ws.wsdl.extensions.addressing.AddressingExtensionRegistry*.registerSerializersAndTypes()*12 Apr, 2011 5:42:36 PM weblogic.wsee.jaxws.spi.WLSServiceDelegate addWsdlDefinitionFeature
SEVERE: Failed to create WsdlDefinitionFeature for wsdl location: http://serverName:port/WSDLURL, error: com.sun.xml.ws.wsdl.parser.InaccessibleWSDLException, message: 2 counts of InaccessibleWSDLException.
I tried Below solutions
1. I added com.oracle.ws.orawsdl_1.3.0.0.jar file in web service application provided the required clssess to resolve the issue. Now getting below exceptions
But getting Exception related org.apache.cxf.wsdl.WSDLManager as it is referenced from my beans.xml import some xml file from cxf 2.2.3.jar and due to
above jar, the WSDL4J.jar is not getting deployed and throwing getElementType() menthod not found exception while creating bean class for Webservice.
2. Now I just rename this jar file so that I can expose WSDL, But getting below exception after calling call back servic
12 Apr, 2011 5:42:36 PM weblogic.wsee.jaxws.framework.policy.advertisementimpl.AdvertisementHelperImpl registerExtension
WARNING: Registering oracle.j2ee.ws.wsdl.extensions.addressing.AddressingExtensionRegistry extension failed; java.lang.NoSuchMethodException: oracle.j2ee.ws.wsdl.extensions.addressing.AddressingExtensionRegistry.registerSerializersAndTypes*(com.ibm.wsdl.extensions.PopulatedExtensionRegistry)*12 Apr, 2011 5:42:36 PM weblogic.wsee.jaxws.spi.WLSServiceDelegate addWsdlDefinitionFeature
SEVERE: Failed to create WsdlDefinitionFeature for wsdl location: http://serverName:port/WSDLURL, error: com.sun.xml.ws.wsdl.parser.InaccessibleWSDLException, message: 2 counts of InaccessibleWSDLException.
After investingation I found that in cxf 2.2.3.jar there are some classes which are also present in com.oracle.ws.orawsdl_1.3.0.0.jar.
now in this case deployer is able to find out the call but signature is getting mismatch, because com.ibm.wsdl.extensions.PopulatedExtensionRegistry is referred from cxf2.2.3.jar file.
Looking for your response.
Thanks In Advance.

Error when deploy application on weblogic's console(weblogic 10 on AIX)

?:|
After successfully start weblogic,I access console and select "Deployment".While I click "Finish" after choose the application named "ls_app", an error appears as follow.
- Messages
The deployment has not been installed.
java.lang.NullPointerException
The log information from weblogic is as follow::-(
Failures were detected while initiating distribute task for application 'ls_app'. Error is: ''
WARN [PageFlowRequestProcessor] Struts module is configured to use com.bea.console.internal.ConsolePageFlowRequestProcessor as the request processor, but the <controller> element does not contain a <set-property> for "controllerClass".
Page Flow actions in this module may not be handled correctly.
Please help on this issue.Thanks!!:-)

I have in log:
2009.26.3 20:12:52 oracle.adfinternal.controller.faces.lifecycle.JSFLifecycleImp
l setLifecycleContextBuilder
WARNING: ADFc: Replacing the ADF Page Lifecycle implementation with 'oracle.adfi
nternal.controller.application.model.JSFDataBindingLifecycleContextBuilder'.
2009.26.3 20:12:52 oracle.adfinternal.controller.util.model.AdfmInterface initia
lize
INFO: ADFc: BindingContext is present, using ADFm APIs for DataControlFrames.
2009.26.3 20:12:52 oracle.adfinternal.controller.metadata.provider.MdsMetadataRe
sourceProvider <init>
INFO: ADFc: Controller caching of MDS metadata resources ENABLED.
2009.26.3 20:12:52 oracle.adf.controller.internal.metadata.MetadataService$Boots
trap add
INFO: ADFc: Loading bootstrap metadata from '/WEB-INF/adfc-config.xml'.
2009.26.3 20:12:54 oracle.adf.share.security.providers.jps.CSFCredentialStore fe
tchCredential
WARNING: Unable to locate the credential for key AUGI in D:\bea\user_projects\do
mains\base_domain\config\oracle.
2009.26.3 20:12:54 oracle.adf.share.jndi.ReferenceStoreHelper throwPartialResult
Exception
WARNING: Incomplete connection information
Edited by: Debuger on Mar 26, 2009 11:18 AM

Getting below errors while deploying application in Weblogic 10.3

Unable to access the selected application.
Exception in AppMerge flows' progression
Exception in AppMerge flows' progression
VALIDATION PROBLEMS WERE FOUND problem: cvc-complex-type.2.4a: Expected elements 'servlet-class@http://java.sun.com/xml/ns/javaee jsp-file@http://java.sun.com/xml/ns/javaee' instead of 'display-name@http://java.sun.com/xml/ns/javaee' here in element servlet@http://java.sun.com/xml/ns/javaee:<null> problem: cvc-complex-type.2.4a: Expected elements 'servlet-class@http://java.sun.com/xml/ns/javaee jsp-file@http://java.sun.com/xml/ns/javaee' instead of 'description@http://java.sun.com/xml/ns/javaee' here in element servlet@http://java.sun.com/xml/ns/javaee:<null>

Hi Pratik,
Would suggest you to create a "*wlfullclient.jar*" by going through the below link and add it in your weblogic workshop and then try to deploy your application. Also it is always recommended that you should compile the old application again with the new JDK version your new weblogic sever is using.
Tpoic:*Creating a wlfullclient.jar for JDK 1.6 client applications*
http://download.oracle.com/docs/cd/E15051_01/wls/docs103/client/jarbuilder.html#wp1078098
Hope this would help you.
Regards,
Ravish Mody

Problem while deploying application in web logic

Hi,
i have an web application with servlets running fine in tomcat 5.1.12, but when i copy the same foldet to web logic and i run i gives an error, i create a domain of my name, and i kept the folder in weblogic, user _projects--> applications folder, but while accessing from the browser i got an error. so please rectify my error.
Babji..

I don't use web logic so I can't help you. But if you post whatever error message you are referring to into your thread, someone who uses web logic might have a better idea as to how to respond. Additionally I suspect there may be some differences in the configuration settings between Tomcat and web logic, you might look into that. But I have no idea.

Error while deploying application with WebLogic server

Hi,
I use Jdeveloper 11g and created and ADF application which i want to deploy with WebLogic Server.But i have an error which is :
"There was a failure when processing annotations for application C:\...\xxx.war. Please make sure that the annotations are valid. The error is oracle.adf.library.webapp.ResourceServlet "
Plz help me.
Thx

I am receiving same message for simple servlet. Running JDev11g build 5166 and embedded WLS 10.3. Servlet used to deploy to embedded WLS and ran fine. Recently running newly created servlets produces error message as in this thread.
Investigation turned up the fact that the class file for the servlet was not deployed to the context-root (o.j2ee\drs) on the server. Copying the class file from the mywork project folder to the context-root folder (o.j2ee\drs) permitted the servlet to run.
Don't know if this is the cause of what you are experiencing but it may assist in your investigation! I have not figured out why the class file for servlets does not deploy to server despite the fact that the log file shows war and ear files were deployed. As it turns out, the war file does not have the class file in it so something is wrong before the war file is created.
Cheers!

Error while deploying application in Weblogic D7B7A

Unable to access the selected application.
Message icon - Error Exception in AppMerge flows' progression
Message icon - Error Exception in AppMerge flows' progression
Message icon - Error error in opening zip file with : /scratch/rramani/view_storage/rramani_jazn-changes-12/.jdev_user_home/system11.1.1.1.32.53.68/DefaultDomain/servers/DefaultServer/upload/EarHcmTalent.ear
Message icon - Error error in opening zip file with : /scratch/rramani/view_storage/rramani_jazn-changes-12/.jdev_user_home/system11.1.1.1.32.53.68/DefaultDomain/servers/DefaultServer/upload/EarHcmTalent.ear
I dont see any other error in the logs
can some one please help?

Hi Rajeev,
Am too getting the same error, can u tl me if i has been cleared or not .
provide the solution if it is cleared.

Problem while deploying ADF application to standalone WLS server

Hi,
I am facing a problem while deploying ADF application to standalone WLS Server.
Following is the error message that I am getting.
[07:24:03 PM] ---- Deployment started. ----
[07:24:03 PM] Target platform is (Weblogic 10.3).
[07:24:07 PM] Retrieving existing application information
[07:24:08 PM] Running dependency analysis...
[07:24:08 PM] Building...
[07:24:13 PM] Deploying 2 profiles...
[07:24:14 PM] Wrote Web Application Module to D:\WorkSpace3\DashboardUi\deploy\Dashboard.war
[07:24:14 PM] Wrote Enterprise Application Module to D:\WorkSpace3\deploy\Dashboard.ear
[07:24:14 PM] Deploying Application...
[07:24:22 PM] [Deployer:149191]Operation 'deploy' on application 'Dashboard' is initializing on 'msDevServer1'
[07:24:27 PM] [Deployer:149193]Operation 'deploy' on application 'Dashboard' has failed on 'msDevServer1'
[07:24:27 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application Dashboard on msDevServer1.: .
[07:24:27 PM] Weblogic Server Exception: weblogic.application.ModuleException:
[07:24:27 PM] Caused by: weblogic.common.ResourceException: DataSource DashboardDb already exists
[07:24:27 PM] See server logs or server console for more details.
[07:24:27 PM] weblogic.application.ModuleException:
[07:24:27 PM] #### Deployment incomplete. ####
[07:24:27 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)Any suggestion how to fix this.
Thanks
Ajay

I logged into console and browsed to 'Home >Summary of JDBC Data Sources' but not able to locate DashboardDb. Please let me know where to find DashboardDB on wls console.
Also, please let me know how to configure the app to not to auto-deploy JDBC data sources

Problem deploying applications in weblogic 9.0..... please help

Hi ...
i'm facing a problem while uploading any applciation into weblogic server..
this is the error it gives
<Jul 26, 2006 11:48:39 AM MDT> <Error> <J2EE Deployment SPI> <BEA-260101> <Parameter may not be null.
java.lang.NullPointerException at weblogic.deploy.api.internal.utils.ConfigHelper.checkParam(ConfigHelper.java:126) at weblogic.deploy.api.model.WebLogicDeployableObject.getEntry(WebLogicDeployableObject.java:434) at weblogic.deploy.api.model.WebLogicDeployableObject.getDDStream(WebLogicDeployableObject.java:256) at weblogic.deploy.api.model.WebLogicDeployableObject.setupDDBeanRoot(WebLogicDeployableObject.java:209) at weblogic.deploy.api.model.WebLogicDeployableObject.getDDBeanRootInternal(WebLogicDeployableObject.java:202)
Truncated. see log file for complete stacktrace
I'm not sure how to fix this.. please help.. its urgent..
Thanks in advance..

We discovered that BEA uses a directory named "autodeploy". By dropping our Jackrabbit 1.1 RAR file (resource adapter), BEA would auto-deploy it. No need to deal with the buggy WebLogic Admin console.
Needed to add the weblogic-ra.xml file to the META-INF directory, and set it up properly. Re-jar it all up as a .rar file, then copy it to the autodeploy directory. The other step is to make sure that the target repository directory exists (I pre-created [bea_home]/jackrabbit/ directory), and that the repository.xml file is already there before you deploy your .rar. Then start up the sample portal server, and the rar file will deploy as a resource adapter. To see it, go into the main server console, click on Deployments > Monitoring > Resource Adapters > Outbound Connection Pools. Jackrabbit should show up there.
This was the directory in which we dropped our RAR for testing:
[bea_home]/weblogic92/samples/domains/portal/autodeploy
Start the sample portal server at:
Windows
[bea_home]/weblogic92/samples/domains/portal/bin/startWebLogic.cmd
UNIX
[bea_home]/weblogic92/samples/domains/portal/bin/startWebLogic.sh
NOTE: This didn't end our headaches. Now we're dealing with Jackrabbit creating connections and never releasing them. Hundreds and hundreds of connections, until it runs out of its connection pool. Hideous. But that's a problem for another thread.
Message was edited by:
LanceZechinato

Problem while Deploying application in weblogic admin console

Similar Messages

Maybe you are looking for