Wls 8.1 sp5 - cannot deploy exploded archive anymore
Hi all,
I used to deploy exploded archive in development mode with wls 8.1 sp4. When browsing the file system, the console used to show a radio button to the left of folders which contained an exploded war.
Since I replace 8.1 sp4 with 8.1 sp5, this radio button does not appear anymore along folders that contain exploded war.
Is this a known issue ? Anyone reproduced the same behaviour ?
Thanks for letting me know of any workaround as this feature is really handy ...
Kind regards,
Regis
Dear Prasanth,
You're right; so what I did next was to rename my .jspx to .jsp, and this time round I hit this exception while accessing the index.jsp page, any idea what other stuffs I did to do?
Thanks for your help!
javax.servlet.jsp.JspException: Cannot find FacesContext
at javax.faces.webapp.UIComponentTag.doStartTag(UIComponentTag.java:405)
at com.sun.faces.taglib.jsf_core.ViewTag.doStartTag(ViewTag.java:105)
Similar Messages
-
Hi,
I am doing J2EE/Struts/EJB Development on Weblogic 8.1.
Have an EAR file with WAR file and bunch of EJB JARs inside that EAR.
I need to do a lot of changes and additions to the GUI,
which is mostly JSPs inside that WAR.
Probably the easiest way to do it would be by editing
JSPs deployed on Weblogic directly, however I can't do it,
because it explodes EAR, but not WAR file inside the EAR.
Is there a way of exploding WAR there [via console or Ant]?
Or can I make changes to JSPs in my build folders and somehow auto-deploy them on running Weblogic ? I've heard of wldeploy, but not sure how to use it for that.
[use Eclipse IDE]
Please help !
Thank you,
Oleg.This should work with exploded archives where an exploded ear contains one or more exploded j2ee modules. If the webapps are exploded then any change made to JSPs is automatically re-compiled the next time you refresh the browser.
exploded_ear/exploded_war/foo.jsp
/WEB-INF/web.xml
So in summary, using an exploded war should do the trick.
-- Nagesh -
Heya,
I'm upgrading our servers from SP4 to SP5 and found that the application scoped JDBC Pool/Data Source to SQL Server 2000 in my EAR will no longer deploy. I'm using the ant task wldeploy and I tried using the Admin Console. I keep getting a NullPointerException. All worked fine under SP4, so has anyone else had this problem? I can post the error trace/weblogic-application.xml file if it'll help...
Thanks,
AnnaAnna Veirauchs wrote:
Thank you for your time.
The Admin Server log has the following:
####<Oct 26, 2005 3:37:24 PM PDT> <Warning> <RMI> <****> <****> <ExecuteThread: '2' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-080003> <RuntimeException thrown by rmi server: weblogic.management.internal.AdminMBeanHomeImpl.getMBean(Ljavax.management.ObjectName;)
java.lang.NullPointerException.
java.lang.NullPointerException
at weblogic.management.internal.AdminMBeanHomeImpl.getMBean(AdminMBeanHomeImpl.java:245)Hi. At this point, I think official support should get involved.
Can you open a case with them? The exceptions aren't being generated
or at least reported from JDBC-related code, but if they can dig
more, it might end up in my court.
Joe
at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:492)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:435)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:430)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
####<Oct 26, 2005 3:37:24 PM PDT> <Info> <Deployer> <****> <****> <ExecuteThread: '1' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-149033> <failed application **** on ****>
####<Oct 26, 2005 3:37:25 PM PDT> <Info> <Management> <****> <****> <ExecuteThread: '2' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-140009> <Configuration changes for the domain have been saved to the repository.>
####<Oct 26, 2005 3:37:25 PM PDT> <Warning> <Deployer> <****> <****> <ExecuteThread: '2' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-149004> <Failures were detected while initiating Deploy task for application ****.>
####<Oct 26, 2005 3:37:25 PM PDT> <Debug> <Deployer> <****> <****> <ExecuteThread: '2' for queue: 'weblogic.admin.RMI'> <<WLS Kernel>> <> <BEA-149078> <Stack trace for message 149004
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: prepare failed for JDBCDataSource
Module: JDBCDataSource Error: java.lang.NullPointerException
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2484)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2396)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:883)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:591)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
================
The Managed Server log has:
####<Oct 26, 2005 3:37:24 PM PDT> <Info> <Deployer> <****> <****> <ExecuteThread: '0' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149059> <Module JDBCDataSource of application **** is transitioning from unprepared to prepared on server ****.>
####<Oct 26, 2005 3:37:24 PM PDT> <Info> <JDBC> <****> <****> <ExecuteThread: '0' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-001155> <The following exception has occurred:
java.lang.NullPointerException
at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:164)
at weblogic.management.internal.AdminMBeanHomeImpl_815_WLStub.getMBean(Unknown Source)
at weblogic.jdbc.common.internal.JDBCDataSourceFactory.createDataSource(JDBCDataSourceFactory.java:74)
at weblogic.jdbc.common.internal.JDBCModule.prepare(JDBCModule.java:140)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContainer.java:3149)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContainer.java:1590)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1234)
at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:1077)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer(SlaveDeployer.java:2530)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2480)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2396)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:883)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:591)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
Caused by: java.lang.NullPointerException
at weblogic.management.internal.AdminMBeanHomeImpl.getMBean(AdminMBeanHomeImpl.java:245)
at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:492)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:435)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:430)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:35)
... 2 more
####<Oct 26, 2005 3:37:24 PM PDT> <Info> <Deployer> <****> <****> <ExecuteThread: '0' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149061> <Module JDBCDataSource of application **** failed to transition from unprepared to prepared on server ****.>
####<Oct 26, 2005 3:37:25 PM PDT> <Error> <Deployer> <****> <****> <ExecuteThread: '0' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149201> <Failed to complete the deployment task with ID 3 for the application ****.
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: prepare failed for JDBCDataSource
Module: JDBCDataSource Error: java.lang.NullPointerException
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(SlaveDeployer.java:2484)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2396)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:883)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:591)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
--------------- nested within: ------------------
weblogic.management.ManagementException: - with nested exception:
[weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: prepare failed for JDBCDataSource
Module: JDBCDataSource Error: java.lang.NullPointerException
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDeployer.java:2413)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:883)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.java:591)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:500)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
====
My weblogic-application.xml is:
<!DOCTYPE weblogic-application PUBLIC '-//BEA Systems, Inc.//DTD WebLogic Application 8.1.0//EN' 'http://www.bea.com/servers/wls810/dtd/weblogic-application_2_0.dtd'>
<weblogic-application>
<jdbc-connection-pool>
<data-source-name>JDBCDataSource</data-source-name>
<connection-factory>
<connection-properties>
<user-name>******</user-name>
<password>******</password>
<url>jdbc:bea:sqlserver://10.10.10.99\\MYINSTANCE</url>
<driver-class-name>weblogic.jdbc.sqlserver.SQLServerDriver</driver-class-name>
<connection-params>
<parameter>
<param-name>databaseName</param-name>
<param-value>****</param-value>
</parameter>
</connection-params>
</connection-properties>
</connection-factory>
<pool-params>
<size-params>
<initial-capacity>10</initial-capacity>
<max-capacity>10</max-capacity>
<capacity-increment>2</capacity-increment>
<shrinking-enabled>true</shrinking-enabled>
<shrink-frequency-seconds>300</shrink-frequency-seconds>
<highest-num-waiters>100</highest-num-waiters>
<highest-num-unavailable>4</highest-num-unavailable>
</size-params>
<login-delay-seconds>1</login-delay-seconds>
<leak-profiling-enabled>false</leak-profiling-enabled>
<connection-check-params>
<table-name>SQL SELECT COUNT(*) FROM sysobjects</table-name>
<check-on-reserve-enabled>true</check-on-reserve-enabled>
<check-on-release-enabled>false</check-on-release-enabled>
<check-on-create-enabled>false</check-on-create-enabled>
<connection-reserve-timeout-seconds>30</connection-reserve-timeout-seconds>
<connection-creation-retry-frequency-seconds>360
</connection-creation-retry-frequency-seconds>
<inactive-connection-timeout-seconds>360
</inactive-connection-timeout-seconds>
<test-frequency-seconds>600</test-frequency-seconds>
</connection-check-params>
</pool-params>
<driver-params>
<prepared-statement>
<cache-size>10</cache-size>
<cache-type>LRU</cache-type>
</prepared-statement>
<row-prefetch-enabled>true</row-prefetch-enabled>
<row-prefetch-size>500</row-prefetch-size>
<stream-chunk-size>1024</stream-chunk-size>
</driver-params>
</jdbc-connection-pool>
</weblogic-application> -
Hello
Is it possible to deploy exploded ear in WLS 6.1 during the development ?
If yex, What is the structure of an exploded ear ?
Thank you for your help
Barrybarry wrote:
Hello
Is it possible to deploy exploded ear in WLS 6.1 during the development ?
Yes
If yex, What is the structure of an exploded ear ?
Same as an archived EAR that you unzipped.
-- Rob
Thank you for your help
Barry -
Problem in Deployment as Exploded archive
Hi All,
I am really saturated working on above. currently My application deploy as single .ear file. I need to deploy my application as exploded archive. for the same I have changed my deployment scripts which explode my ear file and .jar file inside .ear file in the applications dir of my domain. I also install weblogic as service. so then when I start the weblogic, it has got exception while deploying EJBmodule.
<Error> <Deployer> < BEA-149205> <failed to initialize the application myapplication due to err { module name : EJBS.jar,Error:exception preparing module:EJBModule
If someone has step-by-step process of deploying ear application as exploded in production please send it to me. I will be very thankful.
Apart from that I have few queries.
1. How workshop compile and build application. I know in normal case it uses wlwbuild but I would like in detail from where it gets information about what to build and how.
2. when workshop build the application, where all classes are stored on server (in devlopment mode)Did you find my experiments with the Oracle AS at http://blogs.sun.com/marcoscorner? Look at the navigation bar to fina all the pieces;-)
Maybe that gives you some hints.
Thanks,
-- Marco -
JSF 1.2 app is deployed only in exploded archive mode if JSF 2.0 facet used
Hi.
I'm developing JSF 1.2 + facelets application. The only way to configure eclipse WTP editors to properly handle xhtml pages is to install JSF 2.0 facet (there was facelets plugin before, but it was superseded by JSF 2.0 facet if I'm not mistaken). When application is deployed on WL, OEPE show message that JSF 2.0 applications can be deployed only in exploded archive mode.
Is there any way to make OEPE to believe that this application is based on JSF 1.2 (as really is)?
Regards,
Vadim.Hi, Ian.
You are stating that it's a JSF 2.0 app by selecting that facet - the tooling relies on your facet selection to determine what features are available.Thought as much. Determining which JSF implementation will be active at deployment time looks like very complicated task and facet version is a reliable source of such kind info. Sadly :)
What "eclipse WTP editors" are you trying to configure?"HTML editor". Without JSF 2.0 facet it doesn't handle JSF taglibs' namespaces and EL expressions content assist/navigation.
The other option is to install JBoss Tools richfaces support, but for various reasons I'd like not to.
After using exploded deployment for a week now I see that it is not that slow as I initially thought (at least for a small project): JSP/XHTML changes picked up, class methods reloaded. Manual republishing is still not as fast as in case of the splitsource deployment, but it don't call it often.
Thanks.
Edited by: user3269289 on Apr 8, 2011 2:34 AM -
WLS 10.3.5 : upload a Deployment Plan Archive
hi
Please consider the WebLogic Server 10.3.5 console "Summary of Deployments" page, where an "Install" button takes you to the first page of the "Install Application Assistant" which says "... If you cannot find your deployment files, upload your file(s) ..."
with a link to the page where you can select and upload a "Deployment Archive" and a "Deployment Plan Archive",
a shown in the screenshot at http://www.consideringred.com/files/oracle/img/2011/WLS1035-DeploymentPlanArchive.png
For this "Deployment Plan Archive" the page has a description that says
"A deployment plan is a configuration which can supplement the descriptors included in the deployment archive. A deployment will work without a deployment plan, but you can also upload a deployment plan archive now. This deployment plan archive will be a directory of configuration information packaged as a .jar file. See related links for additional information about deployment plans. "
So, there seems to be a difference between a deployment plan file (plan.xml) and a deployment plan archive (JAR file).
- (q1) Where can I find documentation on what such deployment plan archive (JAR file) should look like?
many thanks
Jan Verveckenfyi
In the context of service request 3-4667732128 I got this feedback:
"Deployment Plan Archive" Option that we have in WebLogic Console at Deployment Service is new feature added from 11G and currently not under full fledged implementation, so that's the reason its not documented in any of the Oracle Documentation.regards
Jan -
Can't get adf-faces-demo.war working on WLS 8.1 SP5
Did a search & found some others facing the same difficulties as I am, also followed some recommendations of using an exploded war instead of archive war, and also adding some JARs from Tomcat 5.5.* onto my classpath, but the demo still refuses to work on WLS 8.1 SP5.
Using the hyperlink http://127.0.0.1:7001/adf-faces-demo, I kept getting a blank page. And on my WLS console, I'm seeing these:
Mar 15, 2006 6:37:23 PM oracle.adfinternal.view.faces.webapp.ConfigParser parseConfigFile
INFO: ADF Faces is running in debug mode. Do not use in a production environment. See:/WEB-INF/adf-f
aces-config.xml
Could somebody help me with this?
Or WLS 8.1 totally doesn't work with JSF?Dear Prasanth,
You're right; so what I did next was to rename my .jspx to .jsp, and this time round I hit this exception while accessing the index.jsp page, any idea what other stuffs I did to do?
Thanks for your help!
javax.servlet.jsp.JspException: Cannot find FacesContext
at javax.faces.webapp.UIComponentTag.doStartTag(UIComponentTag.java:405)
at com.sun.faces.taglib.jsf_core.ViewTag.doStartTag(ViewTag.java:105) -
Deploying Enterprise Archive into weblogic 10.3.4.0 application server
Hi All,
I am trying to deploy enterprise archive into web-logic application server. This ear contains two modules. web service module and web application module.
This application was previously running on Apache tomcat server and now i am migrating to web-logic application server.
I am getting following error when deploying to the web-logic application server. Below exception.
For web service and web application, I am using Hibernate and Spring frameworks. Following are the dependencies of web service
[INFO] ------------------------------------------------------------------------
[INFO] Building WebServiceModule Maven Webapp 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @ MavenWebAppModule ---
[INFO] com.packt.maven:MavenWebAppModule:war:1.0-SNAPSHOT
[INFO] +- com.packt.maven:BusinessLogicModule:jar:1.0-SNAPSHOT:compile
[INFO] | +- com.packet.maven:DataPersistanceModule:jar:1.0-SNAPSHOT:compile
[INFO] | \- com.packt.maven:DataModelModule:jar:1.0-SNAPSHOT:compile
[INFO] +- com.packt.maven:WebServiceClientModule:jar:1.0-SNAPSHOT:compile
[INFO] +- org.apache.struts:struts2-core:jar:2.1.8:compile
[INFO] | +- com.opensymphony:xwork-core:jar:2.1.6:compile
[INFO] | | \- org.springframework:spring-test:jar:2.5.6:compile
[INFO] | +- org.freemarker:freemarker:jar:2.3.15:compile
[INFO] | +- ognl:ognl:jar:2.7.3:compile
[INFO] | +- commons-fileupload:commons-fileupload:jar:1.2.1:compile
[INFO] | \- commons-io:commons-io:jar:1.3.2:compile
[INFO] +- org.apache.struts:struts2-spring-plugin:jar:2.1.8:compile
[INFO] | +- org.springframework:spring-beans:jar:2.5.6:compile
[INFO] | +- org.springframework:spring-core:jar:2.5.6:compile
[INFO] | \- org.springframework:spring-context:jar:2.5.6:compile
[INFO] | \- aopalliance:aopalliance:jar:1.0:compile
[INFO] +- xml-apis:xml-apis:jar:1.0.b2:provided (scope not updated to compile)
[INFO] +- javassist:javassist:jar:3.12.1.GA:compile
[INFO] +- com.oracle:ojdbc6:jar:11.2.0:compile
[INFO] +- org.springframework:spring:jar:2.5.6:compile
[INFO] +- org.springframework:spring-web:jar:2.5.6:compile
[INFO] +- org.hibernate:hibernate:jar:3.2.7.ga:compile
[INFO] | +- net.sf.ehcache:ehcache:jar:1.2.3:compile
[INFO] | +- javax.transaction:jta:jar:1.0.1B:compile
[INFO] | \- asm:asm-attrs:jar:1.5.3:compile
[INFO] +- dom4j:dom4j:jar:1.6.1:compile
[INFO] +- commons-logging:commons-logging:jar:1.1.1:compile
[INFO] +- commons-collections:commons-collections:jar:3.2.1:compile
[INFO] +- cglib:cglib:jar:2.2:compile
[INFO] +- antlr:antlr:jar:2.7.7:compile
[INFO] +- asm:asm:jar:3.3:compile
[INFO] +- javax.xml.soap:saaj-api:jar:1.3.3:compile
[INFO] | \- javax.activation:activation:jar:1.1:compile
[INFO] +- com.sun.xml.messaging.saaj:saaj-impl:jar:1.3.4:compile
[INFO] | \- org.jvnet:mimepull:jar:1.4:compile
[INFO] \- junit:junit:jar:3.8.1:test (scope not updated to compile)
[INFO]
Following are the dependencies of maven web app module
[INFO] ------------------------------------------------------------------------
[INFO] Building MavenWebAppModule Maven Webapp 1.0-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @ WebServiceModule ---
[INFO] com.packt.maven:WebServiceModule:war:1.0-SNAPSHOT
[INFO] +- org.springframework:spring:jar:2.5.6:compile
[INFO] +- org.springframework:spring-web:jar:2.5.6:compile
[INFO] | +- org.springframework:spring-beans:jar:2.5.6:compile
[INFO] | +- org.springframework:spring-context:jar:2.5.6:compile
[INFO] | | \- aopalliance:aopalliance:jar:1.0:compile
[INFO] | \- org.springframework:spring-core:jar:2.5.6:compile
[INFO] +- xml-apis:xml-apis:jar:1.0.b2:provided (scope not updated to compile)
[INFO] +- javax:javaee-api:jar:6.0:provided
[INFO] +- junit:junit:jar:3.8.1:test (scope not updated to compile)
[INFO] +- com.oracle:ojdbc6:jar:11.2.0:compile
[INFO] +- org.hibernate:hibernate:jar:3.2.7.ga:compile
[INFO] | +- net.sf.ehcache:ehcache:jar:1.2.3:compile
[INFO] | +- javax.transaction:jta:jar:1.0.1B:compile
[INFO] | \- asm:asm-attrs:jar:1.5.3:compile
[INFO] +- dom4j:dom4j:jar:1.6.1:compile
[INFO] +- commons-logging:commons-logging:jar:1.1.1:compile
[INFO] +- commons-collections:commons-collections:jar:3.2.1:compile
[INFO] +- cglib:cglib:jar:2.2:compile
[INFO] +- antlr:antlr:jar:2.7.7:compile
[INFO] +- com.sun.xml.ws:jaxws-rt:jar:2.2.3:compile
[INFO] | +- javax.xml.ws:jaxws-api:jar:2.2.3:compile
[INFO] | | +- javax.xml.bind:jaxb-api:jar:2.2.2:compile
[INFO] | | \- org.glassfish:javax.annotation:jar:3.1-b35:compile
[INFO] | +- com.sun.xml.bind:jaxb-impl:jar:2.2.3-1:compile
[INFO] | +- com.sun.xml.messaging.saaj:saaj-impl:jar:1.3.8:compile
[INFO] | +- com.sun.xml.stream.buffer:streambuffer:jar:1.2:compile
[INFO] | +- org.codehaus.woodstox:wstx-asl:jar:3.2.1:compile
[INFO] | | \- stax:stax-api:jar:1.0.1:compile
[INFO] | +- org.jvnet.staxex:stax-ex:jar:1.4:compile
[INFO] | | \- javax.xml.stream:stax-api:jar:1.0-2:compile
[INFO] | +- com.sun.org.apache.xml.internal:resolver:jar:20050927:compile
[INFO] | +- org.jvnet:mimepull:jar:1.5:compile
[INFO] | +- com.sun.xml.ws:policy:jar:2.2.2:compile
[INFO] | | +- com.sun.xml.txw2:txw2:jar:20090102:compile
[INFO] | | \- com.sun.istack:istack-commons-runtime:jar:2.2.1:compile
[INFO] | +- org.glassfish.gmbal:gmbal-api-only:jar:3.1.0-b001:compile
[INFO] | | \- org.glassfish.external:management-api:jar:3.0.0-b012:compile
[INFO] | \- org.glassfish.ha:ha-api:jar:3.1.8:compile
[INFO] +- asm:asm:jar:3.3:compile
[INFO] \- org.jvnet.jax-ws-commons.spring:jaxws-spring:jar:1.8:compile
[INFO] +- javax.servlet:servlet-api:jar:2.5:compile
[INFO] +- org.apache.xbean:xbean-spring:jar:2.7:compile
[INFO] +- javax.jws:jsr181-api:jar:1.0-MR1:compile
[INFO] +- javax.xml.soap:saaj-api:jar:1.3:compile
[INFO] +- com.sun.xml.stream:sjsxp:jar:1.0:compile
[INFO] +- javax.annotation:jsr250-api:jar:1.0:compile
[INFO] \- javax.activation:activation:jar:1.1:compile
[INFO]
In my weblogic application configuration i have provided following configuration to load java from my applications first. Could anybody help me on this issue. Thanks in advance for anyhelp
<?xml version="1.0" encoding="UTF-8"?>
<wls:weblogic-application
xmlns:wls="http://xmlns.oracle.com/weblogic/weblogic-application"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://xmlns.oracle.com/weblogic/weblogic-application http://xmlns.oracle.com/weblogic/weblogic-application/1.0/weblogic-application.xsd http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/javaee_5.xsd">
<!--weblogic-version:10.3.1 -->
<wls:application-param>
<wls:param-name>webapp.encoding.default</wls:param-name>
<wls:param-value>UTF-8</wls:param-value>
</wls:application-param>
<wls:prefer-application-packages>
<wls:package-name>antlr.*</wls:package-name>
</wls:prefer-application-packages>
</wls:weblogic-application>
Exception.......
SEVERE: Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.sun.xml.ws.transport.http.servlet.SpringBinding#0' defined in ServletContext resourcepring/config/SpringBeans.xml]: Cannot create inner bean '(inner bean)' of type [org.jvnet.jax_ws_commons.spring.SpringService] while setting bean property 'service'; nested exceramework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)': FactoryBean threw exception on object creation; nested exception is java.lang.Linkageaint violation: when resolving field "DATETIME" the class loader (instance of weblogic/utils/classloaders/ChangeAwareClassLoader) of the referring class, javax/xml/datatype/Datahe class loader (instance of <bootloader>) for the field's resolved type, javax/xml/namespace/QName, have different Class objects for that type
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveInnerBean(BeanDefinitionValueResolver.java:230)
at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:122)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1245)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1010)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:472)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:409)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:380)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:264)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:261)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:185)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:429)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:728)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:380)
at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:255)
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199)
at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1872)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
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:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
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)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name '(inner bean)': FactoryBean threw exception on object creation; nested exceptiogeError: loader constraint violation: when resolving field "DATETIME" the class loader (instance of weblogic/utils/classloaders/ChangeAwareClassLoader) of the referring class, jtatypeConstants, and the class loader (instance of <bootloader>) for the field's resolved type, javax/xml/namespace/QName, have different Class objects for that type
Edited by: user8643895 on Apr 14, 2013 3:42 AMThis forum is about iAS. For weblogic go to: WebLogic Server - General
-
How the diference " publish as a virtual application vs an exploded archive" ?
how the diference " publish as a virtual application vs an exploded archive" ?
Hi,
The following documentation describes the difference between virtual vs exploded archive deployment.
http://docs.oracle.com/cd/E13222_01/wls/docs103/deployment/deployunits.html
FYI: In OEPE, you can select the deployment option on Server Properties window. Here are the steps to switch between Virtual/Exploded archive deployment:
> In Server view, right click on server configuration | select "Properties"
> Expand WebLogic | and select "Publishing" to modify the mode
-Ram -
Oracle Forms 11gR2 - Cannot deploy locally from within Forms
I cannot deploy locally from within forms. The server is up and running and I can deploy the form by putting the correct URL in the address line of the browser window. When I try to deploy from within forms it comes up with some crazy URL that differs everytime.
This is what the URL should be and this works from the browser:
http://machinename:7002/forms/frmservlet?form=WRD608ADMIN_11g.fmx&userid=&otherparams=useSDI=yes
Here is one of the URLs it came up with when I try to run it from within Forms:
http://localhost:60231/lysVL2VjqT33znjfvLwanktVRxTIc6dEwVeRNXXRmhYU2qjf
Localhost is always there, but the rest varies.
In Forms, I have the Preferences, Runtime set to:
http://machinename:7002/forms/frmservlet
Where machine name is my PC, it is the same for this address as the URL above that works directly from the browser.
So what am I missing?
Thank you in advance.Generally speaking, it is discouraged to manually edit any of the configuration files if they are managed by WLS Console or EM. In this case, default.env is managed by EM. Therefore, changes to the file should be done through EM. If however, you want to alter the file manually, the following is likely the best way to accomplish this:
1. Stop the WLS Admin Server and Node Manager
2. Locate the proper file you wish to edit. By proper I mean, there are several copies of most config files. Most of the config files found in the Oracle Home are actually template files and are not used at runtime. Altering these will not give you the change you want. The default.env you want would be here (assuming Windows)
C:\Oracle\Middleware\user_projects\domains\ClassicDomain\config\fmwconfig\servers\WLS_FORMS\applications\formsapp_11.1.2\config
If you are using a "Development" installation type, the above path will reflect AdminServer instead of WLS_FORMS. Remember that Development installations are not for multi-user purposes. Production deployments require the "Deployment" installation type, which can also include the Builders.
Do NOT make any changes yet.
3. Once you find the correct file, create a backup copy. Then open the file for edit (not the backup).
4. Make the desired changes and save.
5. Restart Node Manager and Admin Server if you plan to use them.
For more information about using EM to manage your configuration, refer to the product documentation:
http://docs.oracle.com/cd/E38115_01/doc.111210/e24477/configure.htm#CHDCCGHI -
Cannot deploy SOA composite to a managed server
My problem: cannot deploy SOA composite to a managed server.
The following is what I did:
1. I created a domain "devDomain". admin server is created automatically for me.
*2. I created a manged server (soa_server1) on my domain after.*
2. started the admin server
3. started soa_server1
4. see both servers in WLS control, both server state=running
5. see both server in EM console, both server status are up
6. in JDev(11.1.1.5.0), created an application server connection, and tested the connection successfully
7. when I tried to deploy my composite from JDev, I selected the application server connection, on step "SOA servers", it only lists AdminServer.
8. Then I tried to deploy the composite from EM by right-click soa_server1, but "SOA deployment" is not in the list.
My guess: there should be some libraries or other resources applied to soa_server1 before it could accept soa deployment. What are these libraries/resources?
I tried to target all 10 libraries under the path "oracle.soa." to soa_server1, and checked the config.xml and found the file was updated correcly, reboot my pc, restarted the servers, but still face the same problem.
My environment is weblogic 10.3.5.
Basically, my question is:
after a domain is created and admin server is there, if I want to add a managed server which will host soa composites, what should I do to configure the managed server?
Edited by: wiky on Jul 20, 2011 11:39 AMHow can I add new code to a clustered environment without causing an outage. Right
> now I have to deploy the new code using the admin server to both managed
servers.
> My question is if I pull one managed server out of the cluster, add new
code and
> test it, how do I add this one managed server back to the cluster that is
referencing
> the old code without causing an outage for the site?
This is something addressed much better in the 7.0 release.
Peace,
Cameron Purdy
Tangosol, Inc.
Clustering Weblogic? You're either using Coherence, or you should be!
Download a Tangosol Coherence eval today at http://www.tangosol.com/
"William" <[email protected]> wrote in message
news:3cc9847a$[email protected]..
>
-
Cannot deploy "Hello World" application using SAP NW CE 7.1
Hello,
I am having problems deploying a simple application to NW CE 7.1 (Welcome application
from NWDS tutorial).
I try to deploy from the NWDS. When I am executing "Deploy new archive
and run" I am asked for user and password.
According to the documentation I give following credentials:
SAP NetWeaver Application Server (e.g. for deploying applications)
username: Administrator
password: <your master password>
However after typing that I get immediate error in NWDS.
ConnectionException,cause=[ERROR CODE DPL.DCAPI.1144] NamingException.Cannot get initial context.Reason: Exception during getInitialContext operation. Cannot establish connection to the remote server.
Then the browser opens with following URL: http://localhost:50100/webdynpro/dispatcher/local/Welcome/WelcomeAPP?SAPtestId=38 and the following stack trace is shown.
"Application error occurred during the request procession."
Details: com.sap.tc.webdynpro.services.sal.core.DispatcherException: The requested deployable object 'local/Welcome' is not deployed on the server. Please check the used URL for typos.
at com.sap.tc.webdynpro.clientserver.task.Task.getDeployableObject(Task.java:364)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.initApplicationDeployableObjectPart(RequestManager.java:539)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.initTask(RequestManager.java:477)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doInitWdEnvironment(RequestManager.java:150)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:205)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.delegateToRequestManager(AbstractExecutionContextDispatcher.java:205)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.DispatchHandlerForRequestManager.doService(DispatchHandlerForRequestManager.java:38)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.AbstractDispatchHandler.service(AbstractDispatchHandler.java:116)
at com.sap.engine.services.servlets_jsp.server.deploy.impl.module.IRequestDispatcherImpl.dispatch(IRequestDispatcherImpl.java:93)
at com.sap.tc.webdynpro.serverimpl.wdc.sessionctx.ExecutionContextDispatcher.dispatchToRequestManager(ExecutionContextDispatcher.java:140)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:93)
at com.sap.tc.webdynpro.serverimpl.core.sessionctx.AbstractExecutionContextDispatcher.dispatch(AbstractExecutionContextDispatcher.java:105)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doContent(AbstractDispatcherServlet.java:87)
at com.sap.tc.webdynpro.serverimpl.core.AbstractDispatcherServlet.doGet(AbstractDispatcherServlet.java:54)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:66)
at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:32)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:431)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:289)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:376)
at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:85)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:160)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:67)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60)
at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29)
at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12)
at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:71)
at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:309)
at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.run(Processor.java:222)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:152)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:247)
Caused by: com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Failed to create deployable object 'local/Welcome' since it is not a Web Dynpro object.
at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.getDeployableObject(DeployableObjectFactory.java:87)
at com.sap.tc.webdynpro.services.sal.deployment.core.DeployableObjectInternal.getDeployableObjectInternal(DeployableObjectInternal.java:37)
at com.sap.tc.webdynpro.clientserver.task.Task.getDeployableObject(Task.java:362)
... 43 more
Caused by: com.sap.tc.webdynpro.spi.WebDynproRuntimeException: No Web Dynpro application (deployable object) with name local/Welcome exists.
at com.sap.engine.services.webdynpro.WebDynproRuntimeServiceImpl.getDeployableObject(WebDynproRuntimeServiceImpl.java:254)
at com.sap.tc.webdynpro.serverimpl.wdc.deployment.DeployableObjectFactory.getDeployableObject(DeployableObjectFactory.java:85)
... 45 more
Please help.
Best regards.
PawełHi!
For some reason, I am not able to deploy my application again (although it worked for a couple of weeks now)....
The error is:
com.sap.ide.eclipse.deployer.api.APIException: ConnectionException,cause=[ERROR CODE DPL.DCAPI.1144] NamingException.Cannot get initial context.
Reason: Exception while trying to get InitialContext.
at com.sap.ide.eclipse.deployer.dc.DCClientImpl.<init>(DCClientImpl.java:70)
at com.sap.ide.eclipse.deployer.dc.DCClientFactoryImpl.createClient(DCClientFactoryImpl.java:142)
at com.sap.ide.eclipse.deployer.DeployerPlugin.getClient(DeployerPlugin.java:195)
at com.sap.ide.eclipse.sdm.threading.DeployThreadManager.deploy(DeployThreadManager.java:359)
at com.sap.ide.eclipse.sdm.SDMManager.deployArchives(SDMManager.java:149)
at com.sap.ide.j2ee.wtpserver.engineadapter.SapDeployer.deployArchives(SapDeployer.java:30)
at com.sap.ide.j2ee.wtpserver.engineadapter.SAPPublisher$DeployRunnable.run(SAPPublisher.java:302)
at java.lang.Thread.run(Thread.java:595)
Caused by: com.sap.engine.services.dc.api.ConnectionException: [ERROR CODE DPL.DCAPI.1144] NamingException.Cannot get initial context.
Reason: Exception while trying to get InitialContext.
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:189)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.<init>(SessionImpl.java:115)
at com.sap.engine.services.dc.api.session.impl.SessionFactoryImpl.newSession(SessionFactoryImpl.java:30)
at com.sap.engine.services.dc.api.impl.ClientFactoryImpl.createClient(ClientFactoryImpl.java:74)
at com.sap.ide.eclipse.deployer.dc.DCClientImpl.<init>(DCClientImpl.java:67)
... 7 more
Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is com.sap.engine.interfaces.cross.DestinationException: cannot establish connection with any of the available instances:
localhost:50004 Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection to host: 10.18.206.83 and port: 50004]
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:488)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:166)
... 11 more
Caused by: com.sap.engine.interfaces.cross.DestinationException: cannot establish connection with any of the available instances:
localhost:50004 Reason: com.sap.engine.services.rmi_p4.P4IOException: Cannot open connection to host: 10.18.206.83 and port: 50004
at com.sap.engine.interfaces.cross.Destination.getNextAvailableBroker(Destination.java:59)
at com.sap.engine.interfaces.cross.Destination.getRemoteBroker(Destination.java:35)
at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:352)
... 16 more [ERROR: 01.02.2009 10:15:13 /userOut/daView_category (eclipse.UserOutLocation) [Thread[Thread-27,5,main]] ]
Please help! -
WLS 9.2: Error to deploy a MDB on MQ
Hi,
I want to migrate an WLS 8.1 SP5 application to WLS 9.2. My application have a MDB who process messages on MQ Series 6.1.
I write a "StartupClass" to register connection factory and destination classes in WebLogic JNDI and a simple MDB to process messages.
This simply application works fine on WLS 8.1 SP5 and not in WLS 9.2. The error is:
####<Mar 6, 2008 10:13:41 AM MET> <Info> <EJB> <dfsn4e01> <G6R1_ln_AUTO_1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1204794821030> <BEA-010008> <EJB Deploying file: erdv_mdbmq.jar>
####<Mar 6, 2008 10:13:41 AM MET> <Info> <Deployer> <dfsn4e01> <G6R1_ln_AUTO_1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1204794821708> <BEA-149060> <Module erdv_mdbmq.jar of application erdv_mdbmq successfully transitioned from STATE_NEW to STATE_PREPARED on server G6R1_ln_AUTO_1.>
####<Mar 6, 2008 10:13:42 AM MET> <Info> <Deployer> <dfsn4e01> <G6R1_ln_AUTO_1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1204794822365> <BEA-149059> <Module erdv_mdbmq.jar of application erdv_mdbmq is transitioning from STATE_PREPARED to STATE_ADMIN on server G6R1_ln_AUTO_1.>
####<Mar 6, 2008 10:13:42 AM MET> <Info> <Deployer> <dfsn4e01> <G6R1_ln_AUTO_1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1204794822794> <BEA-149061> <Module erdv_mdbmq.jar of application erdv_mdbmq failed to transition from STATE_PREPARED to STATE_ADMIN on server G6R1_ln_AUTO_1.>
####<Mar 6, 2008 10:13:42 AM MET> <Error> <Deployer> <dfsn4e01> <G6R1_ln_AUTO_1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1204794822802> <BEA-149231> <Unable to set the activation state to true for the application 'erdv_mdbmq'.
weblogic.application.ModuleException: Exception activating module: EJBModule(erdv_mdbmq)
Unable to deploy EJB: MonitorMsgDriven from erdv_mdbmq.jar:
Error getting JMSServer member info
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:422)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:181)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:358)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:52)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:186)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
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)
Error getting JMSServer member info NestedException Message is :com.ibm.mq.jms.MQQueue
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1286)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1050)
at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1270)
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:405)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:381)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:71)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:63)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:181)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:358)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:52)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:186)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
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)
>
####<Mar 6, 2008 10:13:42 AM MET> <Info> <Deployer> <dfsn4e01> <G6R1_ln_AUTO_1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1204794822813> <BEA-149059> <Module erdv_mdbmq.jar of application erdv_mdbmq is transitioning from STATE_PREPARED to STATE_NEW on server G6R1_ln_AUTO_1.>
####<Mar 6, 2008 10:13:42 AM MET> <Debug> <J2EE> <dfsn4e01> <G6R1_ln_AUTO_1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1204794822840> <BEA-160058> <Warning : BindingTransactionSynchronizationRegistry still exists for Context :EventContext (app/ejb/erdv_mdbmq.jar#MonitorMsgDriven/comp). Unbinding it.>
####<Mar 6, 2008 10:13:42 AM MET> <Info> <Deployer> <dfsn4e01> <G6R1_ln_AUTO_1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1204794822854> <BEA-149060> <Module erdv_mdbmq.jar of application erdv_mdbmq successfully transitioned from STATE_PREPARED to STATE_NEW on server G6R1_ln_AUTO_1.>
This is a bug of Weblogic 9.2?
Thank you.
Sorry for my poor english.Did you try upgrading to MQ 6 at the same time? One possible problem is that some IBM MQ 6.0 jars (not sure if all of them) only support the JMS 1.1 API, so you might need WebLogic patches on top of 9.2 if you run into problems or use an older MQ jar that supports the 1.0.2 JMS API (such as one from MQ 5).
This was an unanticipated problem on our part, as the JMS specification is extremely clear that a JMS 1.1 compliant jar must also support the typed JMS 1.0.2 APIs.
Tom
PS. It is unlikely that you need to use a startup class. See
http://ibswings.blogspot.com/2008/02/integrating-mq-broker-6-with-bea.html
and
http://edocs.bea.com/wls/docs92/jms/interop.html
for more info. -
Hello!
I need to deploy a war file extracted into a custom folder. Is it possible in WEB AS to point the deployment to a particular folder of our choice instead of deploying the WAR/EAR file?
Thanks
/RayHi Ray,
applications on Web AS are deployed in the database, and the corresponding binaries are synchronized to the file system from the DB. Hence, you cannot point the deployment to a custom directory.
Anyway, why do you need that? Usually, exploded deployment is needed for development environment for the sake of quick update of the changed files? Is that your requirement also? If so, you could try using the Single File Update function of the Web AS Deploy service to update single files in your application. For details, see Deploying exploded EAR in WAS 6.40 thread.
Hope that helps a bit.
Maybe you are looking for
-
JDBCPersistenceManagerFactory and JNDI
Hi, I'm currently working on kodo v2.2.1. I have a problem if I use kodo with jndi. Everything is working fine if I just create a JDBCPersistenceManagerFactory with new JDBCPersistenceManagerFactory() save it in jndi and access it later under th
-
Also, I want to add Schema tags to the Muse master page copy, particularly serviceArea tags, but I'm not seeing the elements in Dreamweaver. Where are elements from the master found in Dreamweaver?
-
Problem with client side printing
hi , am using struts and jasper reports on my project, now i was having problem that whenever i try to print the report , the printer dialogue box was appearing on server machine, i want it on client end, how to solve this problem, please any one kno
-
Import playlist to create new library - Possible?
My daughter and I sync two iPods off one computer. Here are the instructions on how to do this: http://support.apple.com/kb/HT1495 We are currently using Method 2: ie, her ipod syncs to a certain playlist. Now she wants to set up her own separate lib
-
hello' Need help on retrieving data into a single from tables on separate databases each has its own username and password . Thanks