Cluster environment with Deployment Plan losing variable values

Hi all,
Our environment uses Weblogic Server 10.2, with 2 Managed Servers in Cluster, in Feisty Fawn Ubuntu.
Our app has a bunch of variables configured in the web.xml with custom values, most of which are endpoint and JDBC related. Our web.xml has some default values in these variables, and we created a Deployment Plan to change these values in deployment-time.
The problem is that, after a random amount of time, the cluster is "losing" these configurations. At first, everything goes fine, but then, we start receiving errors because the endpoint being used is not the Deployment Plan's anymore, but the one from web.xml. It's completely random, and come and go without notice.
Is there a known bug about this? Is this a configuration issue?
Any help would be appreciated!
Thanks,
Francisco

Are you redeploying the applications at all?
Francisco Cavedon wrote:
Hi all,
Our environment uses Weblogic Server 10.2, with 2 Managed Servers in Cluster, in Feisty Fawn Ubuntu.
Our app has a bunch of variables configured in the web.xml with custom values, most of which are endpoint and JDBC related. Our web.xml has some default values in these variables, and we created a Deployment Plan to change these values in deployment-time.
The problem is that, after a random amount of time, the cluster is "losing" these configurations. At first, everything goes fine, but then, we start receiving errors because the endpoint being used is not the Deployment Plan's anymore, but the one from web.xml. It's completely random, and come and go without notice.
Is there a known bug about this? Is this a configuration issue?
Any help would be appreciated!
Thanks,
Francisco

Similar Messages

Weblogic 10.3 - changing jndi-name with deployment plan fails

I was trying to alter the global jndi name of a stateless ejb by using a deployment plan, but can't get it to work.
- to be able to replace it later on with a deployment plan, I specify a jndi-name in weblogic-ejb-jar.xml (so I do not use the @mappedName)
e.g.
<?xml version="1.0" encoding="UTF-8"?>
<weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/10.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/10.0 http://www.bea.com/ns/weblogic/10.0/weblogic-ejb-jar.xsd">
 <weblogic-enterprise-bean>
 <ejb-name>ExampleService</ejb-name>
 <enable-call-by-reference>true</enable-call-by-reference>
 <stateless-session-descriptor>
 <business-interface-jndi-name-map>
 <business-remote>com.example.ExampleServiceRemote</business-remote>
 <jndi-name>com.example.ExampleService#com.example.ExampleServiceRemote</jndi-name>
 </business-interface-jndi-name-map>
 </stateless-session-descriptor>
 </weblogic-enterprise-bean>
</weblogic-ejb-jar>
- during deployment I specify a deploymentPlan with following content:
<variable-definition>
<variable>
<name>ejb_jndiname_ExampleService</name>
<value>ExampleService</value>
</variable>
</variable-definition>
<module-override>
<module-name>ExampleService.jar</module-name>
<module-type>ejb</module-type>
<module-descriptor external="true">
<root-element>weblogic-ejb-jar</root-element>
<uri>meta-inf/weblogic-ejb-jar.xml</uri>
<variable-assignment>
<name>ejb_jndiname_ExampleService</name>
<xpath>/weblogic-ejb-jar/weblogic-enterprise-bean/\[ejb-name="ExampleService"\]/stateless-session-descriptor/business-interface-jndi-name-map/\[business-remote="com.example.ExampleServiceRemote"\]/jndi-name</xpath>
<operation>replace</operation>
</variable-assignment>
</module-descriptor>
</module-override>
- after deployment, the original jndi-name ("com.example.ExampleService#com.example.ExampleServiceRemote") is active in the jndi tree instead of "ExampleService"
p.s. When I specified the jndi-name in weblogic-ejb.jar.xml as
 <weblogic-enterprise-bean>
 <ejb-name>ExampleService</ejb-name>
 <enable-call-by-reference>true</enable-call-by-reference>
 <jndi-name>com.example.ExampleService#com.example.ExampleServiceRemote</jndi-name>
 </weblogic-enterprise-bean>
and the replace in the deployment plan as
<variable-assignment>
<name>ejb_jndiname_SecurityService</name>
<xpath>/weblogic-ejb-jar/weblogic-enterprise-bean/\[ejb-name="ExampleService"\]/jndi-name</xpath>
<operation>replace</operation>
</variable-assignment>
the replacement does work (checked by verifying the jndi-name within the deployed ear using the console), but the problem then is that the jndi-name does not appear in the jndi tree (that's why I tried the <business-interface-jndi-name-map>)
Any ideas?
Kind regards,
Ben
Edited by: user11230128 on 4-jun-2009 7:42

After a Service Request and some trial and error, I got it to work after adding the following part in each 'jar module override' section of the deployment plan:
<module-descriptor external="false">
<root-element>ejb-jar</root-element>
<uri>META-INF/ejb-jar.xml</uri>
</module-descriptor>
Apparantly this is needed even though there is no ejb-jar.xml in the jar.
So the deployment plan has to be something like:
<variable-definition>
<variable>
<name>ejb_jndiname_ExampleService</name>
<value>ExampleService</value>
</variable>
</variable-definition>
<module-override>
<module-name>ExampleService.jar</module-name>
<module-type>ejb</module-type>
<module-descriptor external="false">
<root-element>weblogic-ejb-jar</root-element>
<uri>meta-inf/weblogic-ejb-jar.xml</uri>
<variable-assignment>
<name>ejb_jndiname_ExampleService</name>
<xpath>/weblogic-ejb-jar/weblogic-enterprise-bean/[ejb-name="ExampleService"]/stateless-session-descriptor/business-interface-jndi-name-map/[business-remote="com.example.ExampleServiceRemote"]/jndi-name</xpath>
<operation>replace</operation>
</variable-assignment>
</module-descriptor>
<module-descriptor external="false">
<root-element>ejb-jar</root-element>
<uri>META-INF/ejb-jar.xml</uri>
</module-descriptor>
</module-override>
...

Update jta-datasource property with deployment plan

hi,
weblogic server needs the jta data source as a vendor parameter into the persistence xml? right?
looks like:
<properties>
<property name="eclipselink.target-server" value="WebLogic_10" />
<property name="javax.persistence.jtaDataSource" value="mysql" />
</properties>
so now i want to change the value (in my case mysql) to another with a deployment plan... but how does this work? i cannot change the attributes of the tag with my deployment plan, can i?
my Deployment plan looks like:
<variable-definition>
<variable>
<name>DataSource</name>
<value>mysqltest</value>
</variable>
</variable-definition>
<module-descriptor external="false">
<root-element>persistence</root-element>
<uri>META-INF/persistence.xml</uri>
<variable-assignment>
<name>JDBCDataSource</name>
<xpath>/persistence/persistence-unit[name="serverpool"]/properties/property[name="javax.persistence.jtaDataSource"]</xpath>
</variable-assignment>
</module-descriptor>
but after this my application dont work because the persistence xml isnt correct.
so how can i change the attribte value of the tag property of my persistence.xm to change the jta-datasource of my application?
thank you

Firstly, I would validate with support that deployment plans cover the persistence.xml deployment descriptor. Someone else has encountered issues with deployment plans before and I believe they are only supported on certain types of deployment descriptor files. See this previous post:
Problem with hibernate, JPA, and deployment plan
Secondly even if it is supported, your XPATH is incorrect for the variable assignment. I'm not exactly sure what it would be since you're replacing an attribute value as opposed to the contents of an element itself, but it would look more like this:
/persistence/persistence-unit/properties/property[@name='javax.persistence.jtaDataSource']@value
But I'm sure that's wrong. I'm not sure I've seen an example that replaces an attribute value, the ones I've seen are usually a node value.

Remote deploys from Windows to Linux fail with deployment plans on WLS 10.0

Hi there,
We're using WLS 10.0.1 running in a RHEL environment (actually CentOS release 4.7 for development), and attempting to perform remote deploys from Windows work stations using the weblogic.Deployer ant task.
It works fine when not using deployment plans, or when performing a remote deploy from a unix based work station such as a Mac. However, introducing a deployment plan causes a failure only when run from Windows.
The log trace follows:
weblogic.Deployer -debug -remote -verbose -upload -noexit -name obpservices -source C:\work\obf\ver4.0\services\target\obpservices.war -targets obEnterpriseServer -adminurl t3://wlsdev:7001 -user weblogic -password ******** -redeploy -plan C:\work\obf\ver4.0\services/src/runtime/deployment-plans/steves-deployment-plan.xml
weblogic.Deployer invoked with options: -debug -remote -verbose -upload -noexit -name obpservices -source C:\work\obf\ver4.0\services\target\obpservices.war -targets obEnterpriseServer -adminurl t3://wlsdev:7001 -user weblogic -redeploy -plan C:\work\obf\ver4.0\services/src/runtime/deployment-plans/steves-deployment-plan.xml
[WebLogicDeploymentManagerImpl.<init>():103] : Constructing DeploymentManager for J2EE version V1_4 deployments
[WebLogicDeploymentManagerImpl.getNewConnection():146] : Connecting to admin server at wlsdev:7001, as user weblogic
[ServerConnectionImpl.getEnvironment():288] : setting environment
[ServerConnectionImpl.getEnvironment():291] : getting context using t3://wlsdev:7001
[ServerConnectionImpl.getMBeanServer():239] : Connecting to MBeanServer at service:jmx:t3://wlsdev:7001/jndi/weblogic.management.mbeanservers.domainruntime
[ServerConnectionImpl.getMBeanServer():239] : Connecting to MBeanServer at service:jmx:t3://wlsdev:7001/jndi/weblogic.management.mbeanservers.runtime
[DomainManager.resetDomain():36] : Getting new domain
[DomainManager.resetDomain():39] : Using pending domain: false
[MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@359df4
[MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.TargetCache@359df4
[MBeanCache.addNotificationListener():96] : Adding notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@375edb
[MBeanCache.addNotificationListener():103] : Added notification listener for weblogic.deploy.api.spi.deploy.mbeans.ModuleCache@375edb
[ServerConnectionImpl.initialize():171] : Connected to WLS domain: obportal_domain
[ServerConnectionImpl.setRemote():482] : Running in remote mode
[ServerConnectionImpl.init():161] : Initializing ServerConnection : [email protected]9a
[BasicOperation.dumpTmids():691] : Incoming tmids:
[BasicOperation.dumpTmids():693] : {Target=obEnterpriseServer, WebLogicTargetType=server, Name=obpservices}, targeted=true
[RedeployOperation.setupPaths():86] : in place redeploy: false from moduleArchive: C:\work\obf\ver4.0\services\target\obpservices.war
[RedeployOperation.setupPaths():95] : redeploy src path: C:\work\obf\ver4.0\services\target\obpservices.war
[BasicOperation.deriveAppName():140] : appname established as: obpservices
<20/10/2009 10:47:57 AM EST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating redeploy operation for application, obpservices [archive: C:\work\obf\ver4.0\services\target\obpservices.war], to obEnterpriseServer .>
[ServerConnectionImpl.upload():658] : Uploaded app to /opt/bea/user_projects/domains/obportal_domain/servers/AdminServer/upload/obpservices
[BasicOperation.dumpTmids():691] : Incoming tmids:
[BasicOperation.dumpTmids():693] : {Target=obEnterpriseServer, WebLogicTargetType=server, Name=obpservices}, targeted=true
[BasicOperation.loadGeneralOptions():608] : Delete Files:false
Timeout :3600000
Targets:
obEnterpriseServer
ModuleTargets={}
SubModuleTargets={}
Files:
null
Deployment Plan: \opt\bea\user_projects\domains\obportal_domain\servers\AdminServer\upload\obpservices\plan\steves-deplo
yment-plan.xml
App root: \opt\bea\user_projects\domains\obportal_domain\servers\AdminServer\upload\obpservices
App config: \opt\bea\user_projects\domains\obportal_domain\servers\AdminServer\upload\obpservices\plan
Deployment Options: {isRetireGracefully=true,isGracefulProductionToAdmin=false,isGracefulIgnoreSessions=false,rmiGracePeriod=-1,retireTimeoutSecs=-1,undeployAllVersions=false,archiveVersion=null,planVersion=null,isLibrary=false,libSpecVersion=null,libImplVersion=null,stageMode=null,clusterTimeout=3600000,altDD=null,altWlsDD=null,name=obpservices,securityModel=null,securityValidationEnabled=false,versionIdentifier=null,isTestMode=false,forceUndeployTimeout=0,defaultSubmoduleTargets=true,timeout=0}
[BasicOperation.execute():425] : Initiating redeploy operation for app, obpservices, on targets:
[BasicOperation.execute():427] : obEnterpriseServer
[RedeployOperation.initializeTask():55] : Starting task with path: \opt\bea\user_projects\domains\obportal_domain\servers\AdminServer\upload\obpservices\app\obpservices.war
java.io.FileNotFoundException: \opt\bea\user_projects\domains\obportal_domain\servers\AdminServer\upload\obpservices\plan\steves-deployment-plan.xml (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at weblogic.deploy.internal.adminserver.operations.AbstractOperation.parsePlan(AbstractOperation.java:1027)
at weblogic.deploy.internal.adminserver.operations.AbstractOperation.execute(AbstractOperation.java:133)
at weblogic.management.deploy.internal.DeployerRuntimeImpl$2.run(DeployerRuntimeImpl.java:816)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.management.deploy.internal.DeployerRuntimeImpl.performDeployerActions(DeployerRuntimeImpl.java:810)
at weblogic.management.deploy.internal.DeployerRuntimeImpl.redeploy(DeployerRuntimeImpl.java:568)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at weblogic.management.jmx.modelmbean.WLSModelMBean.invoke(WLSModelMBean.java:443)
at com.sun.jmx.mbeanserver.DynamicMetaDataImpl.invoke(DynamicMetaDataImpl.java:213)
at com.sun.jmx.mbeanserver.MetaDataImpl.invoke(MetaDataImpl.java:220)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.invoke(DefaultMBeanServerInterceptor.java:815)
at com.sun.jmx.mbeanserver.JmxMBeanServer.invoke(JmxMBeanServer.java:784)
at weblogic.management.mbeanservers.domainruntime.internal.FederatedMBeanServerInterceptor.invoke(FederatedMBeanServerInterceptor.java:248)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:153)
at weblogic.management.mbeanservers.internal.SecurityMBeanMgmtOpsInterceptor.invoke(SecurityMBeanMgmtOpsInterceptor.java:63)
at weblogic.management.jmx.mbeanserver.WLSMBeanServerInterceptorBase.invoke(WLSMBeanServerInterceptorBase.java:153)
at weblogic.management.mbeanservers.internal.SecurityInterceptor.invoke(SecurityInterceptor.java:443)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor$10.run(AuthenticatedSubjectInterceptor.java:377)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.management.mbeanservers.internal.AuthenticatedSubjectInterceptor.invoke(AuthenticatedSubjectInterceptor.java:375)
at weblogic.management.jmx.mbeanserver.WLSMBeanServer.invoke(WLSMBeanServer.java:310)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1408)
at javax.management.remote.rmi.RMIConnectionImpl.access$100(RMIConnectionImpl.java:81)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1245)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1348)
at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:782)
at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:479)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:475)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:59)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:1016)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
[ServerConnectionImpl.close():334] : Closing DM connection
[ServerConnectionImpl.close():354] : Unregistered all listeners
[ServerConnectionImpl.closeJMX():374] : Closed JMX connection
[ServerConnectionImpl.closeJMX():386] : Closed Runtime JMX connection
[ServerConnectionImpl.closeJMX():398] : Closed Edit JMX connection
Note the file path that cannot be found: "\opt\bea\user_projects\domains\obportal_domain\servers\AdminServer\upload\obpservices\plan\steves-deployment-plan.xml ".
Of course this file does actually exist when the correct path separators are used.
Is this a bug? Is there anything we can do about it? The chances of us upgrading WLS are very remote unfortunately.
Thanks in advance,
Steve C

This is something you should definitely file an Oracle support ticket for. It's entirely possible there's a patch for this.

Losing variable values between functions...

hi!
I'm trying to do something simple in actionscript as simple as this:
- Create a variable: var urlVideo:String;
- Use that variable inside a function and give it a value: urlVideo = videoElemento.url.text();
- Then create a new variable and give it the urlVideo value: var url:String = urlVideo;
My problem is that urlVideo loses it's value
Why is that happening?
Here's my code:
var idVideo:String = "12";
var urlVideo:String;
var xmlPath:String = "videos.xml";
var xml:XML;
var loader = new URLLoader();
loader.load(new URLRequest(xmlPath));
loader.addEventListener(Event.COMPLETE, xmlLoaded);
function xmlLoaded(e:Event):void
if ((e.target as URLLoader) != null )
xml = new XML(e.target.data);
xml.ignoreWhitespace = true;
getVideo(xml);
function getVideo(videosInput:XML):void
var listaVideos:XMLList = videosInput.Video;
for each (var videoElemento:XML in listaVideos)
if(videoElemento.id.text() == idVideo)
urlVideo = videoElemento.url.text();
trace(urlVideo); //has a value
break;
var url:String = urlVideo; //the urlVideo values is null !!
What am i doing wrong?
Can anyone help me?

The above post is correct providing the way you displayed the code in your original post is the same way you have it in your program
function getVideo(videosInput:XML):void
var listaVideos:XMLList = videosInput.Video;
for each (var videoElemento:XML in listaVideos)
if(videoElemento.id.text() == idVideo)
urlVideo = videoElemento.url.text();
trace(urlVideo); //has a value
break;
var url:String = urlVideo; this line occurs outside the function which means that until getVideo is called urlVideo will always be null because its never set until getVideo actualy gives it a value.
zeroskillz method will set the url to play right inside the function which is a good way to organize.. keep behaviors together.
now if you placed url= urlvideo before the end of the function you would have seen a trace like thus:
function getVideo(videosInput:XML):void
var listaVideos:XMLList = videosInput.Video;
for each (var videoElemento:XML in listaVideos)
if(videoElemento.id.text() == idVideo)
urlVideo = videoElemento.url.text();
trace(urlVideo); //has a value
break;
var url:String = urlVideo //has value

Overriding spring configuration in J2EE deployment plan?

I would like some suggestions on how to solve this problem:
Background:
We are developing an application with a web interface and a couple of EJB's, which will be deployed on WebLogic 9.2. We are using Spring 1.2.8. We are using a ContextSingletonBeanfactoryLocator to have a shared application context between the web app and the EJB's.
We have some configuration values (server names, URLs, directories etc), which we would like to modify at deployment time, depending on the environment (local/dev/test/uat/prod). However, we definitely do not want to build different .ear files for each environment.
The problem:
The normal way to do this (when not using spring) is to place these in a deployment descriptor (e.g. web.xml or ejb-jar.xml) and then override them with a deployment plan at deployment time. But a deployment plan cannot override values in an arbitrary file (such as applicationContext.xml)
Approach A:
I use a PropertyPlaceholderConfigurer or similar to load an "c:\myapp.environment.properties" file, which was placed in the filesystem outside of the ear, and which was different in all environments. This is simple to implement, but in a distributed environment with many servers and many applications, it will be a pain to maintain this file.
Approach B:
Much like approach A, but put the property file in a separate application library and load it from the classpath. Then maintain a different version of this app library for each environment. This makes it simpler to ensure it's deployed to all managed servers - but it's a bit more complicated to maintain.
Approach C:
Use an extended ContextLoaderListener servlet so that it automatically deployed a PropertyPlaceholderConfigurer bean which expanded all context-params. E.g.
<pre>

<context-param>
<param-name>remoteServerName</param-name>
<param-value>myRemoteServerInDev</param-value>
</context-param>
<context-param>
<param-name>fileDirectory</param-name>
<param-value>c:\files</param-value>
</context-param>
<listener>
<listener-class>
dk.pfa.ConfiguringContextLoaderListener
</listener-class>
</listener>
</pre>
In my applicationContext.xml, I would then have <property name="serverName" value="${remoteServerName}"/>
For production, I could override the web.xml in the deployment plan to set remoteServerName to "prodRemoteServer".
The problem is that I cannot be sure that this servlet actually gets to configure the shared application context - an EJB may initialise first.
I could put similar logic in each and every EJB, using <env-entry> in ejb-jar.xml instead of <context-param> in web.xml. This seems to invite trouble, since I would then have to ensure that the deployment plan had overridden values for all these entries as well .
Finally I have the option of making an application lifecycle listener class - but that cannot access the web.xml, ejb-jar.xml or any other deployment-plan-overridable files, where I can put user-defined values .
So what is the best practice? Or just a reasonable approach?
Surely, I cannot be the first to face this problem, but if somebody has solved it, they forgot to mention it to Google

I would vote for A or B

Using Optimistic Concurrency in a cluster environment

Hi,
In weblogic 8.1 sp3 cluster environment, I deployed CMP Entity Beans with the following settings:
In weblogic-ejb-jar.xml:
<entity-cache>
<concurrency-strategy>OptimistÂic</concurrency-strategy>
<cache-between-transactions>trÂue</cache-between-transactionsÂ>
</entity-cache>
In weblogic-cmp-rdbms-jar.xml:
<verify-columns>Version</verifÂy-columns>
<optimistic-column>VERSION</opÂtimistic-column>
And I deployed the CMP Entity beans into a cluster which has two managed servers.
When I only do findByPrimaryKey, on both managed servers, the cache-between-transaction functions well and only call ejbLoad() when it first loads that Entity Bean Instance.
However, If I do any updates to this bean, the performance change. After the updates, I issued a lot findByPrimaryKey calls for this bean to test. If the call reach the managed server where the update for the
bean happens, it is fine and still perform like cache-between-transaction. But if the call reach other managed servers, the ejbLoad() get called for that bean in every transactions; and cache-between-transaction seems to be disabled on the other managed servers since the updates.
I test this senario a lot of times and the problem is very consistant. According to my understanding, the other managed servers should only do ejbLoad() at the first time after the updates happened, and the transactions after that shouldn't call ejbLoad everytime.
Does anyone encounter the same problem like this? And is there anyway to optimize it?
Thanks!!

Did you figure out how to do this? We ended up having to track the number of sessions using the service and close it only when there were none. However, this did not solve the problem completely. There seems to be a conflict when running our servlet app (which uses PAPI) on different machines talking to the same BPM. A thread on one machine opens, uses, closes a session and service while a thread on another machine opens a session and in the middle of using it, it dies.

OSB Polling in Cluster Environiment

Hi ,
I created a OSB Poller which will read data from DB. When I test it in a single server it is working fine but when I move it to cluster environment with two managed servers it is polling Twice from the DB and the reports are generating twice . I have changed the JCA Property <Lock>lock-no-wait</Lock> even then it is polling twice. Any solution Please ?

Hi:
Maybe this link can be useful
http://javaoraclesoa.blogspot.com.au/2012/04/polling-with-dbadapter-in-clustered.html
Regards,
RK
Edited by: RK.. on Dec 16, 2012 7:54 PM
Edited by: RK.. on Dec 16, 2012 7:55 PM

Changing the listener port number in a cluster environment

Hello,
I have an Oracle 10g database on a Windows cluster environment with Oracle Fail safe. I am trying to change the default listener port number - these are the steps I have done to change the port number:
1) Take the listener offline via Oracle Fail safe
2) stop the original listener from the command line
3) change the port number in the listener.ora file & save
4) start the original listener
5) bring the listener online in Fail safe
6) register the listener in the database with ALTER SYSTEM SET LOCAL_LISTENER....
After all this, when i check the status of the listener via lsnrctl, i see that the new port number is used, however in the Fail safe administrator, I still see the default port 1521. How do I go about changing the port number so that Fail safe also registers the change?

I did troubleshooting to verify the group, but this just changed the port number back to the default in the listener.ora & tnsnames.ora.
So I did all the steps again to change the port number from the default to another - via lsnrctl status, i see that the new port number is being used, I can also log in to the database via Toad using the new port number, in v$parameter i see that the local_listener is registered on the new port number....only under the Fail Safe manager, the port number (under listener parameter) has not changed....it still shows the default port number. Anyone know how to change this???

File polling in cluster environment

We have a cluster environment with two servers(say, osb_server1 and osb_server2) and a proxy service is configured with file polling using HAfileAdapter.
When executing this service immediately after activation, for first time, the server “osb_server2” throws error as,
Caused By: BINDING.JCA-11042
File deletion failed.
File deletion failed.
File : /**Path**/filename.txt as it does not exist. could not be deleted.
But for consecutive attempts, the osb proxy service is processed by “osb1_server1” and we are not getting the above mentioned error.
In short, We face the issue as below only when executing first time after “Activate” session but the consecutive attempts doesn’t throw error.
Why such error occurs when executing in cluster environment?
Thanks in advance.

try to use the file protocol provided by osb.And select the polling server as on eof the managed server.

Replacing web.xml values with a deployment plan. Not working on WL 10.3.2

Hi All-
I am trying to replace a value from web.xml with one in a weblogic deployment plan. I deployed the application on WL 10.3.2 and used the deployment plan below. No matter what I do it doesn't seem to want to take the value.
web.xml:
<?xml version = '1.0' encoding = 'windows-1252'?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
<context-param>
<param-name>TokenGroup</param-name>
<param-value>oldvalue</param-value>
</context-param>
</web-app>
Deployment Plan:
<?xml version='1.0' encoding='UTF-8'?>
<deployment-plan xmlns="http://xmlns.oracle.com/weblogic/deployment-plan"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://xmlns.oracle.com/weblogic/deployment-plan http://xmlns.oracle.com/weblogic/deployment-plan/1.0/deployment-plan.xsd"
global-variables="false">
<application-name>APPName</application-name>
<variable-definition>
<variable>
<name>TokenGroup</name>
<value>Key123456</value>
</variable>
</variable-definition>
<module-override>
<module-name>APPName.war</module-name>
<module-type>war</module-type>
<module-descriptor external="false">
<root-element>web-app</root-element>
<uri>WEB-INF/web.xml</uri>
<variable-assignment>
<name>TokenGroup</name>
<xpath>/web-app/context-param/[param-name="TokenGroup"]/param-value</xpath>
<operation>replace</operation>
</variable-assignment>
</module-descriptor>
</module-override>
</deployment-plan>
I've also tried other formats for the xpath such as:
/web-app/context-param/{param-name="TokenGroup"}/param-value
/web-app/context-param[param-name="TokenGroup"]/param-value
Any ideas why this doesnt work?
Thanks,
Joe

"web.xml"
<?xml version='1.0' encoding='WINDOWS-1252'?>
<web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<context-param>
<param-name>name</param-name>
<param-value>Joe</param-value>
</context-param>
<context-param>
<param-name>password</param-name>
<param-value>password</param-value>
</context-param>
<servlet>
<servlet-name>ParameterServlet</servlet-name>
<servlet-class>ParameterServlet</servlet-class>
</servlet>
<servlet-mapping>
<servlet-name>ParameterServlet</servlet-name>
<url-pattern>/ParameterServlet</url-pattern>
</servlet-mapping>
</web-app>
ParameterServlet
import java.io.IOException;
import javax.servlet.ServletConfig;
import javax.servlet.ServletContext;
import javax.servlet.ServletException;
import javax.servlet.ServletOutputStream;
import javax.servlet.http.HttpServlet;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
public class ParameterServlet extends HttpServlet {
private String dbName = "";
private String dbPassword = "";
public void init(ServletConfig config) throws ServletException {
super.init(config);
ServletContext context = getServletContext();
dbName = context.getInitParameter("name");
dbPassword = context.getInitParameter("password");
public void doGet(HttpServletRequest req, HttpServletResponse res)
throws IOException {
ServletOutputStream out = res.getOutputStream();
res.setContentType("text/html");
out.println("<html><head><title>Basic Servlet</title></head>");
out.println("<body>Database username is " + dbName);
out.println(" Database password is " + dbPassword + "");
out.println("</body></html>");
"Plan.xml"
<?xml version='1.0' encoding='UTF-8'?>
<deployment-plan xmlns="http://xmlns.oracle.com/weblogic/deployment-plan" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/deployment-plan http://xmlns.oracle.com/weblogic/deployment-plan/1.0/deployment-plan.xsd" global-variables="false">
<application-name>virtual</application-name>
<variable-definition>
<variable>
 <name>name</name>
 <value>akshay1</value>
 </variable>
 <variable>
 <name>password</name>
 <value>koul1</value>
 </variable>
</variable-definition>
<module-override>
<module-name>virtual</module-name>
<module-type>war</module-type>
<module-descriptor external="false">
<root-element>web-app</root-element>
<uri>WEB-INF/web.xml</uri>
 <variable-assignment>
 <name>name</name>
 <xpath>/web-app/context-param/[param-name="name"]/param-value</xpath>
 <operation>replace</operation>
 </variable-assignment>
 <variable-assignment>
 <name>password</name>
 <xpath>/web-app/context-param/[param-name="password"]/param-value</xpath>
 <operation>replace</operation>
 </variable-assignment>
</module-descriptor>
</module-override>
<config-root>C:\DOCUME~1\user\LOCALS~1\Temp\user\.\config\deployments\virtual\plan</config-root>
</deployment-plan>
It works for me... I think your "web.xml" is causing the issue.
Try replacing
<?xml version = '1.0' encoding = 'windows-1252'?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app>
with
<?xml version='1.0' encoding='WINDOWS-1252'?>
<web-app xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
Hope this helps.
-Akshay

Best practice: Deployment plan for cluster environment

Hi All,
I want to know, which way is the best practice for preparing and deploying new configuration for WLS-cluster environment. How can I plan a simultan deployment of ALL of nodes, with out single point of failure?
Regards,
Moh

Hi All,
I get the Answer as followed:
When you deploy an application OR redeploy an application, the deployment is initiated from the Admin Server and it it initiated on all targets (managed servers in the cluster) at the same time based on targets (which is expected to be cluster).
We recommend that applications should be targeted to a cluster instead of individual servers whenever a cluster configuration is available.
So, as long as you target the application to the cluster, the admin server will initiate the deployment on all the servers in a cluster at the same type, so application is in sync on all servers.
Hope that answers your queries. If not, please let me know what exactly you mean by synchronization.
Regards,
Moh

Working with xpath attribute values in WLS 12c deployment plans

I'm trying to use a deployment plan to adjust the hibernate.dialect property in persistence.xml
persistence.xml
<property name="hibernate.dialect" value="org.hibernate.dialect.DerbyDialect" />
but whenever I attempt to refer to attributes in xpath using the usual @ sign, I get an XPathLexer barf.
plan.xml
<variable>
 <name>dialect</name>
 <value xsi:nil="false">org.hibernate.dialect.Oracle10gDialect</value>
</variable>
 <variable-assignment>
 <name>dialect</name>
 <xpath>/persistence/persistence-unit[@name="DPLV1PU"]/properties/property[@name="hibernate.dialect"]/@value</xpath>
 <operation>replace</operation>
 </variable-assignment>
I receive:
Error loading the persistence descriptor META-INF/persistence.xml from the module DPLV1EJB.jar. See the following stack trace for nested errors: weblogic.application.descriptor.DeploymentPlanException: [Munger:2156213]An error occurred while parsing the specifed XPath "/persistence/persistence-unit[@name="DPLV1PU"]/properties/property[@name="hibernate.dialect"]/@value" : line 1:31: unexpected char: '@'.
line 1:31: unexpected char: '@'
at weblogic.application.descriptor.parser.XPathLexer.nextToken(XPathLexer.java:148)
It seems wrong that I can't use a basic xpath feature like the @ to refer to an attribute here. Nor does the alternative axis syntax attribute:: work.
It's almost like there isn't a real XPath implementation under there.

Hi Chris,
I remember an earlier discussion along these lines... I haven't tested this myself, but the docs do say this:
Generic File Loading Overrides
This feature allows you to place application-specific files to be overridden into a new optional subdirectory (named /AppFileOverrides) in the existing plan directory structure. The presence or absence of this new optional subdirectory controls whether file overrides are enabled for the deployment. If this subdirectory is present, an internal ClassFinder is added to the front of the application and module classloaders for the deployment. As a result, the file override hierarchy rules follow the existing classloader and resource loading rules and behaviors for applications. For more information on WebLogic Server application classloading, see WebLogic Server Application Classloading in Developing Applications for Oracle WebLogic Server.
It seems to me that this would be the way to customise the bc4j.xcfg in the deployment plan. In the 10g days, I did this by building my EARs using ANT - I had several bc4j.xcfg files sitting in a separate directory, and each of my targets (dev/test/qa/prod) used the appropriate bc4j.xcfg to build the EAR. I did do a bit of research, and I didn't find anything obvious that would let you use a deployment plan directly for changing bc4j.xcfg - you cannot use the WLS console to change any of the properties (if you could do it via a deployment plan directly, I would expect to find the option there).
Sorry for the rambling post which doesn't give you any definitive answers, but it's just a brain dump at this point.
John

How do I change the context-root of a web app with a deployment plan?

I've been trying to figure this out for several hours.
I'm deploying a .ear file which sets the context root for the single web application it deploys in its application.xml deployment descriptor:
<application>
<display-name>MyApp</display-name>
<module>
<web>
<web-uri>MyAppViewControler.war</web-uri>
<context-root>MyApp</context-root>
</web>
</module>
</application>
I want to change the context-root from /MyApp to something else when deploying the ear file. It seemed to me that using a deployment plan was the way to do this. But when I use this plan:
<deployment-plan>
<application-name>MyApp<application-name>
<variable-definition>
<variable>
<name>NEWCONTEXTROOT</name>
<value>foobar</value>
</variable>
</variable-definition>
<module-override>
<module-name>MyApp</module-name>
<module-type>ear</module-type>
<module-descriptor external="false">
<root-element>application</root-element>
<uri>META-INF/application.xml</uri>
<variable-assignment>
<name>NEWCONTEXTROOT</name>
<xpath>/application/module/web/context-root</xpath>
</variable-assignment>
</module-descriptor>
</module-override>
</deployment-plan>
I get an error:
weblogic.descriptor.DescriptorException: VALIDATION PROBLEMS WERE FOUND
/bea/user_projects/domains/devod1/nullplan.xml:0: problem: cvc-complex-type.2.4a: Expected element 'web-uri@http://java.sun.com/xml/ns/javaee' instead of 'context-root@http://java.sun.com/xml/ns/javaee' here in element web@http://java.sun.com/xml/ns/javaee:<nullplan.xml>
I looked at http://e-docs.bea.com/wls/docs103/pdf/deployment.pdf which says:
"You cannot use a deployment plan to change the context-root in an application.xml
file. However, if an application is deployed as a library, you can either change the
context-root through an weblogic-application.xml file or use the deployment plan
to change the context-root in an weblogic-application.xml file."
I don't understand what this means. I'm not deploying my application as a library.
Does anyone know how to change the context-root for an application?
Any help would be greatly appreciated!

Hi James,
I am quite new to Welogic if i am wrong please correct me.I have re-deployed my application (.war) with this Plan.xml
<?xml version='1.0' encoding='UTF-8'?>
<deployment-plan xmlns="http://www.bea.com/ns/weblogic/deployment-plan" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/deployment-plan http://www.bea.com/ns/weblogic/deployment-plan/1.0/deployment-plan.xsd" global-variables="false">
<application-name>BrowserR08.003</application-name>
*<variable-definition>*
* <variable>*
* <name>CONTEXTROOT</name>*
* <value>BrowserWeb/servlet/BrowserServlet</value>*
* </variable>*
* </variable-definition>*
<module-override>
<module-name>BrowserWeb.war</module-name>
<module-type>war</module-type>
<module-descriptor external="true">
<root-element>weblogic-web-app</root-element>
<uri>WEB-INF/weblogic.xml</uri>
<hash-code>1231953167814</hash-code>
*<variable-assignment>*
* <name>CONTEXTROOT</name>*
* <xpath>/weblogic-web-app/context-root</xpath>*
* <operation>add</operation>*
* </variable-assignment>*
</module-descriptor>
<module-descriptor external="false">
<root-element>web-app</root-element>
<uri>WEB-INF/web.xml</uri>
</module-descriptor>
<module-descriptor external="true">
<root-element>wldf-resource</root-element>
<uri>META-INF/weblogic-diagnostics.xml</uri>
</module-descriptor>
</module-override>
<config-root>/export/home1/tecapp/BrowserR08.003/plan</config-root>
</deployment-plan>
I do not know wether i will require the other module descriptor definition in this Plzn.xml. Now when I go to following link.
Deployments --> MyApp --> Testing
It gives me following url as a test page:
http://localhost:7001/BrowserWeb/servlet/BrowserServlet
as soon as i click on to the above link it redirects me to following.
http://localhost:7001/BrowserWeb/servlet/BrowserServlet/servlet/BrowserServlet
Same if i remove these context-root part my normal Testing menu shows me following link as my webapp access path
http://localhost:7001/BrowserWeb <-- My war file name is BrowserWeb.war so it is default name of my deployed application if i am not wrong
and as soon as i click on above link it redirects me to the following one.
http://localhost:7001/BrowserWeb/servlet/BrowserServlet
It means application server know that my full web access page is with '*servlet/BrowserServlet*' because its adding it in both the cases.
What I want is a constant URL whcih does not change?
Hope this helps :)

Error when deploying EAR in OC4J 10.1.3.0.0 with a deployment plan

Hello!
I try to deploy an ear file specifying a deployment plan generated from web interface using command line utilities. I try to use both admin_client.jar and oracle ant task and still get the same error. When i remove deployment plan argument, the application is successfully deployed.... Any Idea?
My server:
OC4J 10.1.3.0.0 on an AIX server
The error raised during deployment:
[MyServer] 08/04/07 12:46:56 Notification ==>Application Deployer for MyApp STARTS.
[MyServer] 08/04/07 12:46:56 Notification ==>Copy the archive to /oracle/product/j2ee/home/applications/MyApp.ear
[MyServer] 08/04/07 12:46:56 Notification ==>Initialize /oracle/product/j2ee/home/applications/MyApp.ear begins...
[MyServer] 08/04/07 12:46:56 Notification ==>Unpacking MyApp.ear
[MyServer] 08/04/07 12:46:57 Notification ==>Done unpacking MyApp.ear
[MyServer] 08/04/07 12:46:57 Notification ==>Unpacking ic.war
[MyServer] 08/04/07 12:46:59 Notification ==>Done unpacking ic.war
[MyServer] 08/04/07 12:46:59 Notification ==>Initialize /oracle/product/j2ee/home/applications/MyApp.ear end
s...
[MyServer] 08/04/07 12:46:59 Notification ==>Starting application : MyApp
[MyServer] 08/04/07 12:46:59 Notification ==>Initializing ClassLoader(s)
[MyServer] 08/04/07 12:46:59 Notification ==>Initializing EJB container
[MyServer] 08/04/07 12:46:59 Notification ==>Loading connector(s)
[MyServer] 08/04/07 12:47:00 Notification ==>Starting up resource adapters
[MyServer] 08/04/07 12:47:00 Notification ==>Initializing EJB sessions
[MyServer] 08/04/07 12:47:00 Notification ==>Committing ClassLoader(s)
[MyServer] 08/04/07 12:47:00 Notification ==>Initialize ic begins...
[MyServer] 08/04/07 12:47:00 Notification ==>Initialize ic ends...
[MyServer] 08/04/07 12:47:00 Notification ==>Started application : MyApp
[MyServer] 08/04/07 12:47:00 Notification ==>Binding web application(s) to site default-web-site begins...
[MyServer] 08/04/07 12:47:00 Notification ==>Binding ic web-module for application MyApp to site default-web-site under context root ic
[MyServer] 70/01/01 00:00:00 Notification ==>Error deserializing return-value: unexpected reset; nested exception is:
java.io.StreamCorruptedException: unexpected reset
[Summary] There are total 1 instances in the operation.
[Summary] Operation failed on MyServer
[Summary] Operation on cluster FAILED since 1 instanced failed!
Here my deployment plan generated by the Application Server Control Console
moduleType=ear
applicationID=MyApp
bindWebApp=default-web-site
parent=default
moduleID=.
doctype=orion-application
<?xml version="1.0" encoding="UTF-8"?>
<orion-application xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/sch
ema/orion-application-10_0.xsd">
</orion-application>
moduleID=myapp.war
doctype=orion-web-app
<?xml version="1.0" encoding="UTF-8"?>
<orion-web-app xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://xmlns.oracle.com/oracleas/schema/
orion-web-10_0.xsd" context-root="myapp">
<resource-ref-mapping name="jdbc/ds" location="jdbc/myapp/ds">
</resource-ref-mapping>
<web-app-class-loader>
</web-app-class-loader>
</orion-web-app>
My Command line to deploy the application
java -jar admin_client.jar deployer:cluster:opmn://MyServer/home oc4jadmin XXXXX -deploy -file ~/MyApp.ear -deploymentName MyApp -deploymentPlan ~/myapp_plan.dat
Ant file used to deploy
<project name="Deploy EAR in OC4J" default="deploy-ear" basedir="." xmlns:oracle="antlib:oracle">
<property name="server.host" value="MyServer"/>
<property name="server.user" value="oc4jadmin"/>
<property name="server.password" value="XXXXXX"/>
<property name="deploy.filepath" value="/home/myhome/MyApp.ear"/>
<property name="deploy.deployname" value="MyApp"/>
<property name="deploy.logpath" value="${basedir}/deploy-ear.log"/>
<property name="deploy.planpath" value="/home/myhome/myapp_plan.dat"/>
<property name="deploy.uri" value="deployer:cluster:opmn://${server.host}/home"/>
<target name="deploy-ear">
<oracle:deploy
deployerUri="${deploy.uri}"
userId="${server.user}"
password="${server.password}"
file="${deploy.filepath}"
deploymentName="${deploy.deployname}"
bindAllWebApps="default-web-site"
deploymentPlan="${deploy.planpath}"
logFile="${deploy.logpath}"/>
</target>
</project>
Thanks
Message was edited by:
Olivier MARTIN

If you're using OC4J standalone, use the latest available OC4J, 10.1.3.3.
If you're using a manage OC4J, ie. Application Server, upgrade to the latest available version and upgrade your JDK. The provided JDK might be outdated.
--olaf

Cluster environment with Deployment Plan losing variable values

Similar Messages

Maybe you are looking for