EAR deployment from WLS 8.1 to WLS 9.0

Hi all
I've tried to do a one shot migration of my application developped with Workshop and WLS8.1 to WLS9.0.
I've used DDConverter to upgrade my deployment descriptors, but it seems I'm missing some points as every deployment try ends up with this error:
Unable to access the selected application.
javax.enterprise.deploy.spi.exceptions.InvalidModuleException: [J2EE Deployment SPI:260050]'weblogic.j2ee.descriptor.wl.WeblogicApplicationBeanDConfig' does not implement weblogic.deploy.api.spi.WebLogicDConfigBeanRoot, or cannot be instantiated: java.lang.IllegalArgumentException: dom4j-core,jdom,xml-apis,xerces,junit-Extension-Name
Can't see what is wrong with the new descriptors. Have anyone meet this exception? and is this kink of migration possible?
Thanks,
C.

Did this get resolved? I am having a similar issue deploying a webapp from WL8.1 to WL9.1. I am using the console to deploy the application. Any help would be greatly appreciated.
<May 11, 2006 10:15:38 AM CDT> <Error> <Deployer> <BEA-149205> <Failed to initia
lize the application 'ionegui' due to error weblogic.application.ModuleException
: Failed to load webapp: 'ionegui'.
weblogic.application.ModuleException: Failed to load webapp: 'ionegui'
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:285)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(Modu
leListenerInvoker.java:90)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(Depl
oymentCallbackFlow.java:318)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:26)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(Dep
loymentCallbackFlow.java:53)
Truncated. see log file for complete stacktrace
java.lang.IllegalArgumentException: dom4j-core,jdom,xml-apis,xerces,junit-Extens
ion-Name
at java.util.jar.Attributes$Name.<init>(Attributes.java:440)
at java.util.jar.Attributes.getValue(Attributes.java:99)
at weblogic.application.library.LibraryReferenceFactory.getOptPackRefere
nce(LibraryReferenceFactory.java:135)
at weblogic.application.internal.OptionalPackageProviderImpl.getOptional
Packages(OptionalPackageProviderImpl.java:36)
at weblogic.utils.classloaders.ClassFinderUtils.getOptionalPackages(Clas
sFinderUtils.java:140)
Truncated. see log file for complete stacktrace
>

Similar Messages

WLS 11 Policy migration during EAR deployment

We are installing an ADF 11g EAR into our development instance of WLS 10.3.1 and are seeing some strange behavior with the ADF policy migration. During the EAR install from either the WLS console, or using WLST scripts, the ear deployment appears to create entries in our domains system-jazn-data.xml file in the .../config/fmwconfig directory. The policies work fine when testing the application. Users in the various application roles see expected security behavior. If we then start and stop a completely different managed server from the console, the entries that were in the system-jazn-data.xml file disappear, but the our application security continues to work as expected. If we then bounce the server our ear is deployed to, the entries show up again in system-jazn-data.xml.
Can anyone explain this behavior and verify if this is expected?
Additional Information: We have followed the enterprise deployment guide when setting up our middleware home directory. We have the following directory structure:
/opt/oracle/admin/snidomain/aserver
/opt/oracle/admin/snidomain/mserver
The aserver directory contains the admin server and the mserver directory contains our managed servers. Each directory contains a config/fmwconfig subdirectory each containing a system-jazn-data.xml file. Each also contains a jps-config.xml file that specifies an XML policy provider pointing at "./system-jazn-data.xml". When we install an EAR that utilizes ADF security, the system-jazn-data.xml file in the mserver directory is updated during deployment, but the one in the aserver directory is not. Each recycle of a managed server appears to replace the contents of the system-jazn-data.xml file in the mserver directory.
Also, when I bring up Fusion Middleware Control and view the roles/policies of the ear, none are displayed in the UI. If I add a role/policy using Fusion Middleware Control, the new role/policy is placed in the system-jazn-data.xml file in the aserver directory, and the contents of the one in the mserver directory is completely replaced with the same contents as the one in the asever directory, overwriting the ones added during the deployment.

We are installing an ADF 11g EAR into our development instance of WLS 10.3.1 and are seeing some strange behavior with the ADF policy migration. During the EAR install from either the WLS console, or using WLST scripts, the ear deployment appears to create entries in our domains system-jazn-data.xml file in the .../config/fmwconfig directory. The policies work fine when testing the application. Users in the various application roles see expected security behavior. If we then start and stop a completely different managed server from the console, the entries that were in the system-jazn-data.xml file disappear, but the our application security continues to work as expected. If we then bounce the server our ear is deployed to, the entries show up again in system-jazn-data.xml.
Can anyone explain this behavior and verify if this is expected?
Additional Information: We have followed the enterprise deployment guide when setting up our middleware home directory. We have the following directory structure:
/opt/oracle/admin/snidomain/aserver
/opt/oracle/admin/snidomain/mserver
The aserver directory contains the admin server and the mserver directory contains our managed servers. Each directory contains a config/fmwconfig subdirectory each containing a system-jazn-data.xml file. Each also contains a jps-config.xml file that specifies an XML policy provider pointing at "./system-jazn-data.xml". When we install an EAR that utilizes ADF security, the system-jazn-data.xml file in the mserver directory is updated during deployment, but the one in the aserver directory is not. Each recycle of a managed server appears to replace the contents of the system-jazn-data.xml file in the mserver directory.
Also, when I bring up Fusion Middleware Control and view the roles/policies of the ear, none are displayed in the UI. If I add a role/policy using Fusion Middleware Control, the new role/policy is placed in the system-jazn-data.xml file in the aserver directory, and the contents of the one in the mserver directory is completely replaced with the same contents as the one in the asever directory, overwriting the ones added during the deployment.

!!! Jsp compilation error in deploying : in migrating from WLS 8.1 to 9.2

Hi,
We are trying to migrate a .war file from WLS 8.1 to WLS 9.2. After other changes are done, while deploying the .war file in in WLS 9.2 we are getting errors for a jsp file:
1> Syntax error near 'import' ^-------------------^
2> at Line 6 ;The qualifier of this name is a package,which cannot contain methods ^---------------------^
the jsp is simple one & goes like this:: (this jsp file also included in another jsp file .... not sure if this causing the problem ?)
<%@ page import="com.src.config.ConfigurationManager" %> // this class is properly present in /WEb-INF/classes/com/src/config/ .... causing error 1
<%
String sRequestURI = request.getRequestURI();
String sBaseURI = sRequestURI.substring(0, sRequestURI.lastIndexOf("/"));
ConfigurationManager configMan = ConfigurationManager.getInstance(); // Line 6 .. causing error 2
String sOraRoot = configMan.getProperty("OraRoot");
%>
any help please !!
Edited by: user10284044 on Dec 10, 2008 10:54 PM

Hi,
You can get rid of JSP version specific problems by using the following weblogic.xml file:-
<weblogic-web-app>
<jsp-descriptor>
<jsp-param>
<param-name>backwardCompatible</param-name>
<param-value>true</param-value>
</jsp-param>
</jsp-descriptor>
<weblogic-web-app>
It will also confirm if the error you are seeing is due to JSP version differences in 8.1 and 9.x.
Regards.

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.

Enterprise application conversion problem from WLS 10.3.0 to WLS 10.3.2

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


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

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

Migrating apps from WLS 10.3.0 to SOA Suite 11g-- WLS 10.3.3

Hi,
We want to migrate our apps from WLS 10.3.0 to SOA Suite 11g-->WLS 10.3.3. While deploying the apps on WLS 10.3.3 (SOA Suite Domain 11g), it is throwing exception as below. This exception is common for almost all apps. Kindly help.
Caused by: weblogic.utils.compiler.ToolFailureException: Unable to load your custom module provider's module-factory-class com.bea.wlw.runtime.descriptor.module.ConfigModuleFactory
at weblogic.application.compiler.FlowDriver.handleStateChangeException(FlowDriver.java:53)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:37)
at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:96)
at weblogic.application.compiler.AppMerge.runBody(AppMerge.java:157)
at weblogic.utils.compiler.Tool.run(Tool.java:158)
at weblogic.utils.compiler.Tool.run(Tool.java:115)
at weblogic.application.compiler.AppMerge.merge(AppMerge.java:169)
... 67 more
Caused by: weblogic.management.DeploymentException: Unable to load your custom module provider's module-factory-class com.bea.wlw.runtime.descriptor.module.ConfigModuleFactory
at weblogic.application.internal.flow.CustomModuleHelper.loadModuleFactory(CustomModuleHelper.java:82)
at weblogic.application.internal.flow.CustomModuleHelper.initFactories(CustomModuleHelper.java:52)
at weblogic.application.utils.CustomModuleManager.createScopedCustomModules(CustomModuleManager.java:119)
at weblogic.application.utils.CustomModuleManager.<init>(CustomModuleManager.java:39)
at weblogic.application.compiler.WARModule.merge(WARModule.java:466)
at weblogic.application.compiler.flow.MergeModuleFlow.compile(MergeModuleFlow.java:23)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:96)
at weblogic.application.compiler.ReadOnlyEarMerger.merge(ReadOnlyEarMerger.java:49)
at weblogic.application.compiler.flow.AppMergerFlow.mergeInput(AppMergerFlow.java:88)
at weblogic.application.compiler.flow.AppMergerFlow.compile(AppMergerFlow.java:41)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
... 72 more

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

Issues with Deployment to WLS Running on Virtual Box

Hi
JDeveloper 11.1.1.6, BPM 11.1.1.6, WLS 10.3.6
I just installed the SOA & BPM Development VM 11.1.1.6 available at http://www.oracle.com/technetwork/middleware/soasuite/learnmore/vmsoa-172279.html
Domain selected : dev_bpm_spaces
My Host OS is : Windows 7 Prof 64bit (Total 16GB Ram)
Memory allocated to VM : 8GB, Processors : 4
I am able to install everything, start the servers and access the consoles.
Everything looks fine.
But when I am trying to Deploy a BPM Application to the WLS in the VM, I am getting the below Exception. (Tried to Deploy from Local JDeveloper)
When I see the WLS Console -> Servers, I see the following servers.
AdminServer, bam_server1, UCM_server1, WC_Collaboration, WC_Spaces, IBR_server1
First, I started only the AdminServer and tried to Deploy the BPM Application, and I was getting the errors shown at the end.
Then I started the bam_server1, UCM_server1, WC_Collaboration, WC_Spaces servers on the VM and tried to deploy again. Then I got the error only for IBR_server1.
I cannot see the server IBR_server1 in the 'VM Control Center', but it is only shown in the WLS Console Servers.
So I tried to start the IBR_server1 from the WLS Console. I got the following errors
------For server IBR_server1, the Node Manager associated with machine LocalMachine is not reachable.
------All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed.
So my doubts are as follows
1. Only AdminServer is not enough to Deploy the BPM Applications? Why is it trying to connect to other servers while deploying?
When I created a separate Domain manually (local machine - not the VM), only with AdminServer I was able to deploy BPM Applications.
2. If IBR_server1 is also required, how can I start it?
3. I could not see the Node Manager start script in the VM (in the same folder where the start scripts for WLS are present : /home/oracle/bin)
Deployment Exception Logs
[03:51:51 PM] Deploying Application...
[03:51:54 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application BookRequest on AdminServer.: [Deployer:149145]Unable to contact 'bam_server1'. Deployment is deferred until 'bam_server1' becomes available.; nested exception is:
     java.rmi.UnknownHostException: Could not discover administration URL for server 'bam_server1'.
[03:51:54 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application BookRequest on AdminServer.: [Deployer:149145]Unable to contact 'UCM_server1'. Deployment is deferred until 'UCM_server1' becomes available.; nested exception is:
     java.rmi.UnknownHostException: Could not discover administration URL for server 'UCM_server1'.
[03:51:54 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application BookRequest on AdminServer.: [Deployer:149145]Unable to contact 'IBR_server1'. Deployment is deferred until 'IBR_server1' becomes available.; nested exception is:
     java.rmi.UnknownHostException: Could not discover administration URL for server 'IBR_server1'.
[03:51:54 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application BookRequest on AdminServer.: [Deployer:149145]Unable to contact 'WC_Collaboration'. Deployment is deferred until 'WC_Collaboration' becomes available.; nested exception is:
     java.rmi.UnknownHostException: Could not discover administration URL for server 'WC_Collaboration'.
[03:51:54 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application BookRequest on AdminServer.: [Deployer:149145]Unable to contact 'WC_Spaces'. Deployment is deferred until 'WC_Spaces' becomes available.; nested exception is:
     java.rmi.UnknownHostException: Could not discover administration URL for server 'WC_Spaces'.
[03:51:54 PM] [Deployer:149193]Operation 'deploy' on application 'BookRequest' has failed on 'AdminServer'
[03:51:54 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application BookRequest on AdminServer.: .
[03:51:54 PM] Weblogic Server Exception: weblogic.application.ModuleException:
[03:51:54 PM] Caused by: weblogic.common.ResourceException: weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: Listener refused the connection with the following error:
ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
[03:51:54 PM] See server logs or server console for more details.
[03:51:54 PM] weblogic.application.ModuleException:
[03:51:54 PM] Taskflow deployment failed to deploy to server. Remote deployment failed
[03:51:54 PM] #### Deployment incomplete. ####
[03:51:54 PM] Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
Thanks for any help
Regards
Sameer

Hi Vlad
Thank you for your response.
I did deploy the BPM Application to only AdminServer. Infact only AdminServer was shown in the JDeveloper Deployment Wizard.
Even then during the Deployment, I think it is somehow trying to connect to the other servers from AdminServer.
So I copied my BPM Application code from my local Windows to Linux in VM and deployed from JDeveloper in Linux with only AdminServer running.
It was still giving the same error.
Then I started all the Servers and Deployed the BPM Application from the JDeveloper in Linux, then it got Deployed Successfully.
Coming to the issue of the ORA-12505, I have Oracle DB Installed on my local system and is running on the same port 1521 as that of database in Linux in the VM.
I think that is that causing the issue. When I deploy from local JDeveloper, it is trying to connect to the local database which is on same port but different SID.
So it was giving that error.
So my learnings are
1. All the servers in the domain 'dev_bpm_spaces' should be running for deploying the applications.
2. We should deploy it from the Linux, expecially when we have local database server running.
3. I understand that the ports mapping between the linux and windows is already configured in the VM, but sometimes the BPM workspace is not accessible from the local windows.
So it is better to use the Linux for development, deployment and testing.
Thanks and Regards
Sameer

Call EJB in WLS 7.0SP2 from WLS 5.1 SP13

Hello,
I am trying to call an EJB deployed on WLS 7.0SP2 from a WLS 5.1 SP13.
There are issues from 19 Dec 2002 in "weblogic.developer.interest.rmi-iiop" newsgroup
that are supossed to established a summary on this interoperability. The solution
seems to be the same as the interoperability between WLS 6.1SP2 and WLS5.1SP12
with I have been working for several months. I have followed the steps (EJB generated
with "weblogic.ejbc -iiop" in WLS 7.0 and client classes generated with "weblogic.ejbc
-iiop -clienteJar" in WLS5.1) but the only result I obtain is the following exception.
Has anybody really invoked EJBs between this two WLS versions with IIOP?.
javax.naming.NamingException: Unhandled error in lookup. Root exception is java.lang.NullPointerException
at javax.naming.NameImpl.<init>(NameImpl.java:250) at javax.naming.CompositeName.<init>(CompositeName.java:223)
at weblogic.iiop.IIOPInvocationHandlerImpl.getClusteredStub(IIOPInvocationHandlerImpl.java:150)
at weblogic.iiop.IIOPInvocationHandlerImpl.resolveObject(IIOPInvocationHandlerImpl.java:114)
at weblogic.iiop.IIOPReplacer.resolveObject(IIOPReplacer.java:375) at weblogic.iiop.AbstractMsgInput.readRemote(AbstractMsgInput.java:185)
at weblogic.iiop.AbstractMsgInput.readObject(AbstractMsgInput.java:156) at weblogic.cos.naming.NamingContext_WLStub.resolve(NamingContext_WLStub.java:122)
at weblogic.jndi.cosnaming.IIOPInitialContextServer.lookup(IIOPInitialContextServer.java:109)
at javax.naming.InitialContext.lookup(InitialContext.java:345) at jsp_servlet._jsp.__test._jspService(__test.java:108)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:120)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:138)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:946)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:910)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:277)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:403)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:285)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
Thanks for any help,
Rosa

Hello,
I am trying to call an EJB deployed on WLS 7.0SP2 from a WLS 5.1 SP13.
There are issues from 19 Dec 2002 in "weblogic.developer.interest.rmi-iiop" newsgroup
that are supossed to established a summary on this interoperability. The solution
seems to be the same as the interoperability between WLS 6.1SP2 and WLS5.1SP12
with I have been working for several months. I have followed the steps (EJB generated
with "weblogic.ejbc -iiop" in WLS 7.0 and client classes generated with "weblogic.ejbc
-iiop -clienteJar" in WLS5.1) but the only result I obtain is the following exception.
Has anybody really invoked EJBs between this two WLS versions with IIOP?.
javax.naming.NamingException: Unhandled error in lookup. Root exception is java.lang.NullPointerException
at javax.naming.NameImpl.<init>(NameImpl.java:250) at javax.naming.CompositeName.<init>(CompositeName.java:223)
at weblogic.iiop.IIOPInvocationHandlerImpl.getClusteredStub(IIOPInvocationHandlerImpl.java:150)
at weblogic.iiop.IIOPInvocationHandlerImpl.resolveObject(IIOPInvocationHandlerImpl.java:114)
at weblogic.iiop.IIOPReplacer.resolveObject(IIOPReplacer.java:375) at weblogic.iiop.AbstractMsgInput.readRemote(AbstractMsgInput.java:185)
at weblogic.iiop.AbstractMsgInput.readObject(AbstractMsgInput.java:156) at weblogic.cos.naming.NamingContext_WLStub.resolve(NamingContext_WLStub.java:122)
at weblogic.jndi.cosnaming.IIOPInitialContextServer.lookup(IIOPInitialContextServer.java:109)
at javax.naming.InitialContext.lookup(InitialContext.java:345) at jsp_servlet._jsp.__test._jspService(__test.java:108)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27) at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:120)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:138)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:946)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:910)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:277)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:403)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:285)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:130)
Thanks for any help,
Rosa

JCA Classpath - How to use library from rar instead of from WLS

We have a stand-alone resource adapter that uses the apache commons net library, and relies on features added in version 2.0.
When we deploy to WLS 10.3.2, we get a class loading error when invoking the adapter. Method org.apache.commons.net.ftp.FTPClient.setConnectTimeout(T)V is not found.
WLS 10.3.2 includes an older version of the library: com.bea.core.apache.commons.net_1.0.0.0_1-4-1.jar.
Despite paclkaging the proper version (2.2) in our rar, the older and incompatible 1.4.1 version from the system classpath is used.
Is there a way to use the version packaged in our stand-alone rar file? I have seen a way to do this for a war file (prefer-web-inf-classes in deployment descriptor).
O know we could to modify the system classpath in the weblogic startup scripts to use the newer library. We prefer not to do this, since we don't know how WLS uses the library internally, and what might be affected by a different version.

unfortunately, standalone adapter has not prefer-web-inf-classes or similar feature support.

JMS Bridge from WLS to OAS not working; automatic redirection to JMS Port

We have setup a JMS Bridge inbetween Weblogic Server 10.3.0 and Oracle App Server 10.1.3. In our test environment it is working fine. But, in LIVE, we are facing a problem. Firewall is there inbetween OAS and WLS.
1. OAS Admin port 6003, is blocked by firewall. So, from outside environment we can't connect to this port.
2. OAS Port 12401 (RMI Port) is not-blocked
3. OAS Port 12601 (JMS Port) is blocked by firewall
4. We created credential "JMS_USER" while configuring QueueConnFactory at OAS end and used it while setting up WLS JMS Bridge
We are using ormi://172.24.255.59:12401/default as Provider URL from Weblogic while creating JMS Bridge.
Problem
========
While connecting from WLS we are getting the following error from WLS end:
javax.jms.JMSException: Unable to create a connection to "apgst366/172.24.255.59:12,601" as user "JMS_USER".
     at com.evermind.server.jms.JMSUtils.make(JMSUtils.java:1050)
     at com.evermind.server.jms.JMSUtils.toJMSException(JMSUtils.java:1130)
     at com.evermind.server.jms.EvermindConnection.<init>(EvermindConnection.java:132)
     at com.evermind.server.jms.EvermindQueueConnection.<init>(EvermindQueueConnection.java:71)
Question
=========
1) We are requesting for 12401; then why the JMS Port 12601 is being referred?
2) Is there any automatic redirection from OAS end?
3) Will unblocking the 12601 port by Firewall help?
Please help me, as this has become a burning issue for us.
Thanks in advance.

Can anybody please help me?

Migration from WLS 10.0 MP1 to WLS 10.0 MP2

Hello there,
We need to migrate our applications from WLS 10.0 MP1 to WLS 10.0 MP2. Could you please give us an url to download a workshop version that includes WebLogic Portal and WLS 10.0.2?
I've been looking for an installer on the web, but in the Oracle web sites, haven't found any BEA products older versions.
Thanks & Regards
Franco Utreras G.

Hello,
There are 2 options for legacy Weblogic installer download:
Option1: If you have an Oracle Metalink account, you could login and go to Metalink doc ID - 763603.1 which is the "BEA Release Archive". From here you can download the historical BEA releases.
You get the following releases that can be downloaded from here.
Oracle Weblogic Server - Version: 6.1 to 10.3
Oracle JRockit - Version: 7.0 to R27.6
Option2: Login to: https://Metalink.oracle.com
Go to tab: Patches & Updates
Quick Links to: Latest Patchsets, Mini Packs and Maintenance Packs
Patch Bundles for Individual Products or Components
Select BEA Weblogic Platform
Select the WebLogic Main version and SP version
Then you should see the download screen.
HTH
Regards
RC2
http://crkthoughts.blogspot.com

How to reference sapjco from EAR deployment descriptors

Hello techies,
I´ve set up an EJB to use the JCo RFC Provider Service of the J2EE engine. Connection from R3 to EJB works but as soon as the EJB gets invoked, I get the error 'incompatible bean type - no processFunction found' from the RFCDefaultRequestHandler.invokeBean(..., JCO.Function) method.
The reason is clear to me - the JCO.Function class is loaded by different class loaders and thus the method parameters don´t match.
I´ve read in earlier postings that it is neccessary to reference the JCO in the module project and the ear deployment descriptor. That´s where my question begins.
How do I reference the JCO in the module project (what´s that?)? I think it has to do with the EJB jar, doesn´t it?
In the DeployTool I found a way how to set a reference to a library in the menu deploy-->libraries. But I am not sure what to specify here. I entered 'sapjco', since I saw an entry in the managers/library.txt file. Is that correct?
Any hints are welcome!
Regards,
Jan

Jan,
you can set the reference to the EAR project using the reference.txt file that exists in the /managers folder.
In the library.txt file set a path which is reference to sapjco.jar files..like
library JCO sapjco.jar
in the refernce.txt add the JCO referece to the EAR project...like
reference Project library:JCO
where Project here is the name of your EAR file..
Ravi

Hostname in Traps from WLS

Hi Sanjeev
Wish you and everyone in this forum a Very Happy Newyear
Well,to my problem now...
When I receive the traps from WLS for shutdown or restart,the hostname is displayed as localhost
and not the actual hostname.This happens when the traps go to Openview on Unix.But when the same
traps are directed to Openview on NT,it displays the actual hostname.Any clues why.....
I have checked the DNS and the host file and the entries are okay.Also in the SNMP Agent script I have
changed the URL from localhost to the actual hostname.But still it doesn't seems to work..
As always,thanks in advance for any solution...
regards
robert

Hi Sanjeev
Sorry for the delay in replying, I struggled with the problem and then shelved the Unix project and stuck
to Openview for NT.
Well regarding thescenario.
It is like this, if A is the WLS machine and B the Openview for NT and C the OV for Unix.
The trap from A is displayed with te proper hostname on B(OV for NT) and as localhost on C(OV for Unx).
This was the case with all the machines in the place of A.I was using four WLS machines and it all
gave the same output.
Thanks..
Robert
"Sanjeev Chopra" <[email protected]> wrote:
I have heard of this problem earlier also, however i don't think it has been
verified yet.
BTW, the scenarios you have described below for UNIX and NT - is the snmp
agent running on some third machine or in both cases the agent and openview
are running on the same machine.
M Robert Prakash <[email protected]> wrote in message
news:3a59c7eb$[email protected]..
Hi Sanjeev
Wish you and everyone in this forum a Very Happy Newyear
Well,to my problem now...
When I receive the traps from WLS for shutdown or restart,the hostname isdisplayed as localhost
and not the actual hostname.This happens when the traps go to Openview onUnix.But when the same
traps are directed to Openview on NT,it displays the actual hostname.Anyclues why.....
I have checked the DNS and the host file and the entries are okay.Also inthe SNMP Agent script I have
changed the URL from localhost to the actual hostname.But still itdoesn't seems to work..
As always,thanks in advance for any solution...
regards
robert

WLS 6.1 Webapp using EJB from WLS 9.0

I have a WLS 6.1.7 based webapp that currently accesses an EJB deployed to WLS 8.1.5. I just tried upgrading the 8.1 server to 9.0.0. I was able to deploy the EJB just fine but the 6.1.7 based webapp is giving me the following error:
javax.naming.CommunicationException. Root exception is
weblogic.socket.UnrecoverableConnectException: [Login failed: 'Incompatible version:Incompatible versions - this server: '9.0.0' client: '6.1.7.0']
at weblogic.socket.Login.checkLoginSuccess(Login.java:77)
at weblogic.rjvm.t3.T3JVMConnection.connect(T3JVMConnection.java:273)
at weblogic.rjvm.t3.T3JVMConnection.createConnection(T3JVMConnection.java:325)
at weblogic.rjvm.Protocol.createConnection(Protocol.java:206)
at weblogic.rjvm.ConnectionManager.findOrCreateConnection(ConnectionManager.java:1121)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:373)
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:274)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:222)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:189)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:186)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:157)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:309)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:213)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:149)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:660)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:241)
at javax.naming.InitialContext.init(InitialContext.java:217)
at javax.naming.InitialContext.<init>(InitialContext.java:193)
The Initial Context is being created with the following properties:
java.naming.provider.url=t3://localhost:7001
java.naming.factory.initial=weblogic.jndi.WLInitialContextFactory
java.naming.security.principal=system
java.naming.security.credentials=xxxx
Is there a way to get WLS 6.1 to talk to WLS 9.0?
Thanks,
Rick

I believe the constraint is communicating within 2 releases. ie 6.0 can talk to 7.0 and 8.1, but 9.0 is 3 releases away.
That being said, you can double-check this with [email protected]
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/

Excessive LDAP Queries from WLS 6.0 SP2 RP3

We have an application served from WLS 6.0. Our current version of WLS is:
Service Pack 2 05/24/2001 11:55:28 #117037 RP3 for 6.0 SP2 02/21/2002 17:46:45
#167070
WLS has been configured to query an LDAP server for user authentication. The issue
we are experiencing is that WLS performs the LDAP query on EVERY page load in
the application. This is resulting in excessive calls to the LDAP server, and
increased response times.
We have attempted to change the caching realm settings such that the cache is
refreshed every 15 minutes as follows:
<CachingRealm AuthenticationCacheSize="601"
AuthenticationCacheTTLPositive="900" BasicRealm="X_LDAP"
CacheCaseSensitive="true" GroupMembershipCacheTTL="900"
Name="X_CACHE" UserCacheSize="601" UserCacheTTLPositive="900"/>
This has not improved the situation. What else could be causing the excessive
calls? How can we reduce the number of calls?
thanks
Bavini

"Bavini Naidoo" <[email protected]> wrote in message
news:3fc741c1$[email protected]..
>
We have an application served from WLS 6.0. Our current version of WLS is:
Service Pack 2 05/24/2001 11:55:28 #117037 RP3 for 6.0 SP2 02/21/200217:46:45
#167070
WLS has been configured to query an LDAP server for user authentication.The issue
we are experiencing is that WLS performs the LDAP query on EVERY page loadin
the application. This is resulting in excessive calls to the LDAP server,and
increased response times.
We have attempted to change the caching realm settings such that the cacheis
refreshed every 15 minutes as follows:
<CachingRealm AuthenticationCacheSize="601"
AuthenticationCacheTTLPositive="900" BasicRealm="X_LDAP"
CacheCaseSensitive="true" GroupMembershipCacheTTL="900"
Name="X_CACHE" UserCacheSize="601" UserCacheTTLPositive="900"/>
This has not improved the situation. What else could be causing theexcessive
calls? How can we reduce the number of calls?
Turn on weblogic.security.ldaprealm.verbose and see if the debugging output
indicates
the operation that the ldap realm is performing.

EAR deployment from WLS 8.1 to WLS 9.0

Similar Messages

Maybe you are looking for