Weblogic 11g custom LoginModule

Hello experts!
I have implemented a custom JAAS LoginModule, but I can't find any documentation how to register this module in WebLogic 11g (I think the server version is 10). Could you briefly explain how to do this or send some link?
Thank you in advance!

Hi,
You need to create a jaas.conf file referring to the LoginModule class as below.
Sample {
sample.module.SampleLoginModule required debug=true;
Then specify the below parameter in the server startup script.
-Djava.security.auth.login.config=<Pathto>jaas.config
For Ex:
set JAVA_OPTIONS=%JAVA_OPTIONS% -Djava.security.auth.login.config=<pathto>\jaas.config
Regards,
Andy.

Similar Messages

Weblogic custom loginModule

I developed a custom loginModule. It works fine except that I'm always getting FailedLoginException instead of ExpiredAccountException or other custom exceptions.
Anyone have an idea how to fix this ?

1) Is it possible to perform authentication via a
servlet which use � loginmodule (programatic way)
instead of using the weblogic security provider
(configuration way) ? If yes, have you any samples or
links?Yes, but on my opinion you should be able to use weblogic SSPs for implementing authentication. Look at the samples at the dev2dev. Read also the weblogic JavaDocs for the WLS 7.0 because some features are NOT DOCUMENTED ELSEWHERE. There is a class that does the authentication for you.
Most of these SSPI questions are discussed in the weblogic newsgroups, you should be able to find the answer there.
>
2) After authentication, how weblogic store
information about authentication and dont always
return to loginpage ?In a cookie.
>
3) I'v tried to used weblogic sample
(SimpleSampleAuthenticationProvider) but it doesn't
works. When I "create" it in administration console
it's always return an error like this :It seems like your provider is not in the classpath. Read the instructions which come with the sample providers.

Will jdev 11g support customer loginmodule DBTableOraDataSource?

Hi,
In jdev10132,custom loginmdule DBTableOraDataSource is very useful,but in 11g tp3 ,I did not find where I can define this with integrated oc4j,will 11g production release support this?And with 11g support Human Task ,which need more user info ,such as appoval chain,will It support these interesting function? If yes how to do this,if not which solution is recommondede?
Any advice are appreciate
lixinzh
2008/1/17

Hi,
yes it will support DBTableOraDataSource (and custom LoginModules in general) because its a part of the security architecture in OC4J. Does human task authenticate against the container using JavaEE? If yes then it can be authenticated, if not then you would need something else - I would assume it requires WS security
Frank

Custom Authorization Logic Using request.isUserInRole(role) in Weblogic 11g

Dear All,
I am using BlazeDS and its security feature LoginCommand to implement a secured endpoint in Weblogic 11g. Since BlazsDS's default implementation uses HTTP session but we do not want to use it, we would like to implement our own version of authentication and authorization. However we faced a problem on authorization part.
For authentication, we use weblogic.security.services.Authentication.login(username, password), which returns correctly. For authorization, we try to use HttpServletRequest.isUserInRole(role) to determine whether a user belongs to a target role, but it returns false.
When we trying to fix the problem, we add weblogic.servlet.security.ServletAuthentication.login(username, password, request, response) before weblogic.security.services.Authentication.login(username, password), which will add information on HTTP session. It makes the later authorization using HttpServletRequest.isUserInRole(role) return true.
We want to know:
1. How can we check if an account belongs to a target role without using HTTP session in web application?
2. After we call Authentication.login(username, password), anything we need to do to log out for releasing any resource used?
3. If request.isUserInRole(role) is the only possible way to check if an account belongs to a target role, how to check the reason why it returns false?
And here is how we set up user, group and role:
User (in WebLogic Admin Console) – demo_user with demo_grp
Group (in WebLogic Admin Console) – demo_grp with patent demo_grp1
Role (in weblogic-application.xml) – demo_role maps to demo_grp1
We set nothing in web.xml as we want to use the security feature provide by BlazeDS to secure an endpoint at method level.
Remarks:
For Authorization in BlazeDS, what we have is the authenticated user's principal, and the required role of the calling method:
public boolean doAuthorization(Principal principal, List roles);
Thanks In Advance,
Alex

You gotta specify your child table recon-field in the process definition mappings as a Key Field. Refer OOTB AD connector and check:
Process Definition -> AD User ->Reconciliation Field Mappings -> memberOf

Reading SAML attributes inside BPEL on weblogic 11g

Hi,
My customer wants to access to SAML token attributes and username inside BPEL workflow on weblogic 11g.
This workflow is exposed as a webservice and is protected by attached policy.
My question is if it is possible to access SAML token attributes inside BPEL, is yes how to do it.
Thanks
Hubert

Is this what you are looking for??
http://lesterrebollos.blogspot.co.uk/2008/02/extracting-wsse-security-headers-from.html??
best regards Nicolas

Weblogic 11g

hi ,
Any one tried weblogic 11g ??
Chava

Thanks for your reply.
Here is my query
I have created template for weblogic 10g using weblogic 92 domain template it worked fine.
I noticed that weblogic 11g out there so I can use it. I have created same steps as I did for weblogic 92 - weblogic 10g for 11g
SOme how startPointBaseConsole.cmd\sg and startManagedWebLogic.cmd showing up in my domain deploeyment dir\bin folder
and also my custom startWebLogic.smd\sh files got overriden and I can't start weblogic now. Why those new files are showing up and why startWeblogic.cmd is getting overriden?
I have used package Installer and installed on only weblogic Server,admistration console and uddi didn't installl every thing else.

Oracle 11gR2 froms and reports And weblogic 11g

Hi,
I am new to Weblogic,we are using Oracle 11gR2 froms and reports and weblogic 11g. How can I deployee my reports in weblogic and where and what is the procedure.
thank you.

Its custom reports or standard ones?
If custom then are you developed as application?

Database connection error in Weblogic 11g

Hello Everyone,
I am new to this forum and Weblogic. I am in the process of migrating a big application from Weblogic 8.1 to Weblogic 11g. I am facing a issue with JDBC Commit. I am getting following exception while trying to commit
####<Feb 18, 2010 1:11:51 PM EST> <Debug> <JTAPropagate> <PPXP2CE951B506> <AdminServer> <ExecuteThread: '1' for queue: 'weblogic.socket.Muxer'> <<WLS Kernel>> <3de6adeed2d219bd:-1c9bd9a6:126e245ecb6:-7fff-0000000000000010> <1266516711438> <BEA-000000> <java.lang.Exception: DEBUG: receiveRequest, tx=Xid=BEA1-0000957A69A07E5F133C(16499456),Status=Active,numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=0,seconds left=300,XAServerResourceInfo[demoPool_cashlinkdomain]=(ServerResourceInfo[demoPool_cashlinkdomain]=(state=ended,assigned=none),xar=demoPool,re-Registered = false),SCInfo[cashlinkdomain+AdminServer]=(state=active),properties=({}),local properties=({weblogic.jdbc.jta.demoPool=[autoCommit=false,enabled=true,isXA=true,isJTS=false,vendorID=0,connUsed=true,doInit=false,'null',destroyed=false,poolname=demoPool,appname=null,moduleName=null,connectTime=187,dirtyIsolationLevel=false,initialIsolationLevel=2,infected=false,lastSuccessfulConnectionUse=1266516711423,secondsToTrustAnIdlePoolConnection=10,currentUser=java.lang.Exception
at weblogic.jdbc.common.internal.ConnectionEnv.setup(ConnectionEnv.java:310)
at weblogic.common.resourcepool.ResourcePoolImpl.reserveResource(ResourcePoolImpl.java:344)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:433)
at weblogic.jdbc.common.internal.ConnectionPool.reserve(ConnectionPool.java:316)
at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:93)
at weblogic.jdbc.common.internal.ConnectionPoolManager.reserve(ConnectionPoolManager.java:61)
at weblogic.jdbc.jta.DataSource.getXAConnectionFromPool(DataSource.java:1584)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1357)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:438)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:395)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:355)
at com.mycompany.res.services.util.DatabaseHelper.getConnection(DatabaseHelper.java:109)
at com.mycompany.res.services.util.DatabaseHelper.getConnection(DatabaseHelper.java:46)
at com.mycompany.res.services.security.ejb.LoginManagerEJB.login(LoginManagerEJB.java:64)
at com.mycompany.res.services.security.ejb.LoginManagerEJB_z7om1c_EOImpl.login(LoginManagerEJB_z7om1c_EOImpl.java:573)
at com.mycompany.res.services.security.ejb.LoginManagerEJB_z7om1c_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
,currentThread=Thread[[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)',5,Pooled Threads],lastUser=null,currentError=null,currentErrorTimestamp=null,JDBC4Runtime=true,supportStatementPoolable=true,needRestoreClientInfo=false,defaultClientInfo={},supportIsValid=true]}),CoordinatorURL=AdminServer+10.240.15.248:7001+cashlinkdomain+t3+)
at weblogic.transaction.internal.TxDebug.debugStack(TxDebug.java:60)
at weblogic.transaction.internal.TransactionManagerImpl.receiveRequest(TransactionManagerImpl.java:1366)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:287)
at weblogic.rmi.cluster.ClusterableServerRef.dispatch(ClusterableServerRef.java:242)
at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:1138)
at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:1020)
at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:240)
at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:882)
at weblogic.rjvm.MsgAbbrevJVMConnection.dispatch(MsgAbbrevJVMConnection.java:453)
at weblogic.rjvm.t3.MuxableSocketT3.dispatch(MuxableSocketT3.java:322)
at weblogic.socket.BaseAbstractMuxableSocket.dispatch(BaseAbstractMuxableSocket.java:298)
at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:105)
at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)
at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)
What is going wrong with this?
I get the following error every time Weblogic is trying to do database connection check
####<Feb 18, 2010 1:35:40 PM EST> <Debug> <JTA2PC> <PPXP2CE951B506> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <BEA1-028CACE03896> <3de6adeed2d219bd:-1c9bd9a6:126e245ecb6:-7fff-00000000000000c6> <1266518140849> <BEA-000000> <BEA1-028CACE03896: JDBC Internal: TX[BEA1-028CACE03896] committing-->committed
java.lang.Exception: DEBUG
     at weblogic.transaction.internal.TransactionImpl.setState(TransactionImpl.java:1711)
     at weblogic.transaction.internal.ServerTransactionImpl.setCommitted(ServerTransactionImpl.java:2945)
     at weblogic.transaction.internal.ServerTransactionImpl.globalRetryCommit(ServerTransactionImpl.java:2737)
     at weblogic.transaction.internal.ServerTransactionImpl.globalCommit(ServerTransactionImpl.java:2657)
     at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:285)
     at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
     at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:286)
     at weblogic.jdbc.common.internal.ConnectionEnv.testInternal(ConnectionEnv.java:734)
     at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:704)
     at weblogic.jdbc.common.internal.ConnectionEnv.test(ConnectionEnv.java:487)
     at weblogic.common.resourcepool.ResourcePoolImpl.testResource(ResourcePoolImpl.java:2260)
     at weblogic.common.resourcepool.ResourcePoolImpl.checkResource(ResourcePoolImpl.java:1601)
     at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1507)
     at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1496)
     at weblogic.common.resourcepool.ResourcePoolImpl.testUnusedResources(ResourcePoolImpl.java:1942)
     at weblogic.common.resourcepool.ResourcePoolImpl.access$800(ResourcePoolImpl.java:40)
     at weblogic.common.resourcepool.ResourcePoolImpl$ResourcePoolMaintanenceTask.timerExpired(ResourcePoolImpl.java:2368)
     at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
     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)
Edited by: user12640178 on Feb 18, 2010 10:36 AM
Edited by: user12640178 on Feb 18, 2010 10:38 AM

Priya,
Thank you so much for your response. I did test my database source from console and on the console it reported the test was successful, where in the admin logs has same exception logs. I did try creating a non XA connection and it did not have these errors. But my application did raise same exception while doing transaction.
The application has around 250 EJB's that are written long ago and they all comply to EJB 1.1 spec. I am in the process of investigating the level of support for EJB 1.1 in Weblogic 11g.
- Kasi

Taking long time to start when weblogic 11g admin server

Hi
When I ran following command in linux 64-bit environmnt to start weblogic 11g admin server, it is taking such a long time (some time it is taking one and half hour, some time it is taking 24 hours and still showing work under process)
$HOME/Middleware/user_projects/domains/soa_domain/startWebLogic.sh -Dweblogic.management.username=weblogic -Dweblogic.management.password=weblogic$123 > server.log &
Please help me out.
Linux OS 64-bit installaed
Weblogic 11g server (64-bit) installed
SOA SUIT 11g (64-bit) Installed
SYStem COnfiguration:
RAM 4 GB
HDD 160 GB (Single Partition)
Core 2 duo Processor
Thanks
Phani

How much memory have you configured for the servers?
When the memory (Xmx and Xms - JVM parameters) is too small start-up times can get long.
I saw that you have SOA environment. To tune your environment this link might help: http://middlewaremagic.com/weblogic/?p=6040

Error while deploying web-determinations in 10gR3 & weblogic 11g

Hi,
I am installing OPA 10.0.1 for configuring Siebel connector, for this on Linux I am deploying web-determinations & determination-server on 10gR3.
I was able to successfully deploy determination-server and I am facing error while deploying web-determinations
I am facing below error when accessing web-determinations URL after deploying in 10gR3 ( 10.1.3.3 ).
===================
500 Internal Server Error
Servlet error: An exception occurred. The current application deployment descriptors do not allow for including it in this response. Please consult the application log for details
===================
No error is being logged in while application logs.
I also tried deploying in weblogic 11g (10.3.1) and I have below error ,
===================
[HTTP:101216]Servlet: "WebDeterminationsServlet" failed to preload on startup in Web application: "web-determinations.war". com.oracle.determinations.interview.engine.exceptions.EngineConfigurationException: No rulebase directory specified at com.oracle.determinations.interview.engine.local.FileRulebaseService.<init>(FileRulebaseService.java:49) at com.oracle.determinations.interview.engine.local.LocalInterviewEngine.initialise(LocalInterviewEngine.java:91) at com.oracle.determinations.interview.engine.local.LocalInterviewEngine.<init>(LocalInterviewEngine.java:34) at com.oracle.determinations.interview.engine.InterviewEngineFactory.createInstance(InterviewEngineFactory.java:19) at com.oracle.determinations.web.platform.servlet.WebDeterminationsServletContext.init(WebDeterminationsServletContext.java:163) at com.oracle.determinations.web.platform.servlet.WebDeterminationsServletContext.<init>(WebDeterminationsServletContext.java:91) at com.oracle.determinations.web.platform.servlet.WebDeterminationsServlet.init(WebDeterminationsServlet.java:51) at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321) at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121) at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64) at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58) at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48) at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:521) at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1913) at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1887) at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1805) at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3041) at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1374) at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:452) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200) at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117) at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60) at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:629) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:206) at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:40) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:140) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:106) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844) at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253) at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
=====================
Pls let us know any configuration needs to be done.
Pls advise.

Hey Suni,
It appears that there is a section missing out of the current installation guide for Web Determinations. The reason you're getting that error is because you are deploying to application to WebLogic which doesn't expand the war by default so you need to configure the rulebase loader. Before you add proceed with the steps in the install guide you need to:
# Unpack the web-determinations.war file
# Copy the rulebases you wish to install to <webroot>/WEB-INF/classes/rulebases
# Edit the following setting in the application.properties file (<webroot>/WEB-INF/classes/configuration):
load.rulebase.from.classpath =true
rulebase.path =rulebases# Repack the war file
# Proceed with the installation steps as set out in the installation guide
I'll have the installation guide fixed and updated as soon as possible.
Thanks,
Kristy

Error while deployment of CMP 2.0 bean on weblogic 11g

Hi,
I am not able to deploy my CMP 2.0 bean on Weblogic 11g. There are two JVM available in weblogic 11g.
1) Java(TM) SE Runtime Environment (build 1.6.0_22-b04)
2) Oracle JRockit(R) (build R28.1.1-14-139783-1.6.0_22-20101206-0241-windows-ia32, compiled mode)
When we are using "Oracle JRockit(R) (build R28.1.1-14-139783-1.6.0_22-20101206-0241-windows-ia32, compiled mode)" And deploying the CMP bean then we got the Error as below:
D:\Oracle\Middleware\wlserver_10.3\server\bin>java weblogic.appc -verbose C:\temp\Jproject.ear\DefinitionWizardBean.jar
Created working directory: C:\DOCUME~1\cxp\LOCALS~1\Temp\1\appcgen_1309496813354_DefinitionWizardBean.jar
<01-Jul-2011 06:06:57 o'clock BST> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element persis
tence in the deployment descriptor in C:\temp\Jproject.ear\DefinitionWizardBean.jar/META-INF/weblogic-ejb-jar.xml. A vers
ion attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of
the Weblogic Server will reject descriptors that do not specify the JEE version.>
java.lang.NoClassDefFoundError: EntityBean
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632)
at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:343)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:302)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:296)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
at weblogic.ejb.container.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:510)
at weblogic.ejb.container.deployer.BeanInfoImpl.<init>(BeanInfoImpl.java:242)
at weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.<init>(ClientDrivenBeanInfoImpl.java:156)
at weblogic.ejb.container.deployer.EntityBeanInfoImpl.<init>(EntityBeanInfoImpl.java:115)
at weblogic.ejb.container.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl.java:695)
at weblogic.ejb.container.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:558)
at weblogic.ejb.container.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:236)
at weblogic.ejb.container.ejbc.EJBCompiler.getStandAloneDeploymentInfo(EJBCompiler.java:1185)
at weblogic.ejb.container.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:156)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:439)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:396)
at weblogic.application.compiler.AppcUtils.compileEJB(AppcUtils.java:316)
at weblogic.application.compiler.EJBModule.compile(EJBModule.java:128)
at weblogic.application.compiler.flow.SingleModuleCompileFlow.proecessModule(SingleModuleCompileFlow.java:18)
at weblogic.application.compiler.flow.SingleModuleFlow.compile(SingleModuleFlow.java:36)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)
at weblogic.application.compiler.EJBCompiler.compile(EJBCompiler.java:29)
at weblogic.application.compiler.flow.AppCompilerFlow.compileInput(AppCompilerFlow.java:112)
at weblogic.application.compiler.flow.AppCompilerFlow.compile(AppCompilerFlow.java:37)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)
at weblogic.application.compiler.Appc.runBody(Appc.java:203)
at weblogic.utils.compiler.Tool.run(Tool.java:158)
at weblogic.utils.compiler.Tool.run(Tool.java:115)
at weblogic.application.compiler.Appc.main(Appc.java:262)
at weblogic.appc.main(appc.java:14)
EntityBean
But I use JVM " Java(TM) SE Runtime Environment (build 1.6.0_22-b04) " and deploying CMP bean then i got error as below:
D:\Oracle\Middleware\wlserver_10.3\server\bin>d:\Oracle\Middleware\jdk160_21\bin\java weblogic.appc -verbose C:\temp\Tr
ading.ear\DefinitionWizardBean.jar
Created working directory: C:\DOCUME~1\cxp\LOCALS~1\Temp\1\appcgen_1309496852057_DefinitionWizardBean.jar
<01-Jul-2011 06:07:35 o'clock BST> <Warning> <Munger> <BEA-2156203> <A version attribute was not found in element persis
tence in the deployment descriptor in C:\temp\Jproject.ear\DefinitionWizardBean.jar/META-INF/weblogic-ejb-jar.xml. A vers
ion attribute is required, but this version of the Weblogic Server will assume that the JEE5 is used. Future versions of
the Weblogic Server will reject descriptors that do not specify the JEE version.>
java.lang.ClassNotFoundException: EntityBean
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632)
at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:343)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:302)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:296)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:179)
at weblogic.ejb.container.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:510)
at weblogic.ejb.container.deployer.BeanInfoImpl.<init>(BeanInfoImpl.java:242)
at weblogic.ejb.container.deployer.ClientDrivenBeanInfoImpl.<init>(ClientDrivenBeanInfoImpl.java:156)
at weblogic.ejb.container.deployer.EntityBeanInfoImpl.<init>(EntityBeanInfoImpl.java:115)
at weblogic.ejb.container.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl.java:695)
at weblogic.ejb.container.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(MBeanDeploymentInfoImpl.java:558)
at weblogic.ejb.container.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:236)
at weblogic.ejb.container.ejbc.EJBCompiler.getStandAloneDeploymentInfo(EJBCompiler.java:1185)
at weblogic.ejb.container.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:156)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:439)
at weblogic.ejb.container.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:396)
at weblogic.application.compiler.AppcUtils.compileEJB(AppcUtils.java:316)
at weblogic.application.compiler.EJBModule.compile(EJBModule.java:128)
at weblogic.application.compiler.flow.SingleModuleCompileFlow.proecessModule(SingleModuleCompileFlow.java:18)
at weblogic.application.compiler.flow.SingleModuleFlow.compile(SingleModuleFlow.java:36)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)
at weblogic.application.compiler.EJBCompiler.compile(EJBCompiler.java:29)
at weblogic.application.compiler.flow.AppCompilerFlow.compileInput(AppCompilerFlow.java:112)
at weblogic.application.compiler.flow.AppCompilerFlow.compile(AppCompilerFlow.java:37)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:69)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)
at weblogic.application.compiler.Appc.runBody(Appc.java:203)
at weblogic.utils.compiler.Tool.run(Tool.java:158)
at weblogic.utils.compiler.Tool.run(Tool.java:115)
at weblogic.application.compiler.Appc.main(Appc.java:262)
at weblogic.appc.main(appc.java:14)
EntityBean
Please assist me regarding above error
Thanks,
Amritesh
Edited by: 869636 on 01-Jul-2011 00:49

What is the jee version you have on that server? are the environment variables correctly set?

OC4J 10.1.2 to Weblogic 11g (10.3.5) xmlparserv2.jar dependency

I am trying to upgrade from OC4J 10.1.2 to Weblogic 11g (10.3.5).
I used the smartupgrade tool and it has highlighted some required modifications before upgrading.
For example:
<snip>
Rule: Oracle Private Dependencies
Category: api
Priority: required
Complexity: high
Reason: xxx.admin.ejb.AdminCtrl.jar contains the following unsupported Oracle dependencies:
AdminCtrlBean.class on [oracle.xml.parser.v2.DOMParser (orasaaj.jar), oracle.xml.parser.v2.XMLParseException (orasaaj.jar), oracle.xml.parser.v2.XMLDocument (orasaaj.jar)]
Advice: To ensure the proper functioning of deployed applications, features that depend upon the identified API need to discontinue using the identified unpublished Oracle API.
Implication: Features associated with the identified API may be broken, or the application itself may not function properly if at all because they depend upon unpublished Oracle dependencies.
</snip>
I want to follow the 'Advice', but I'm not sure what the best method is for correcting this issue.
Should I move away from the xmlparserv2.jar for xml processing?
If yes, what is the recommended replacement for xmlparserv2.jar in Weblogic 11g?
Any help, guidance or pointers are greatly appreciated.
Thank you.
Edited by: loopy1 on May 29, 2012 11:42 AM

When migrating to weblogic from oc4j, you should discontinue use of the Oracle xml parser. Use the standard java sdk parser.
This code snip:
StringReader sr = new StringReader(xmlString.toString());
DOMParser parser = new DOMParser();
parser.parse(sr);
Document doc = parser.getDocument();
Is converted to this code snip:
DocumentBuilderFactory dbf = DocumentBuilderFactory.newInstance();
DocumentBuilder db = dbf.newDocumentBuilder();
StringReader sr = new StringReader(Sparameters);
InputSource is = new InputSource(sr);
Document doc = db.parse(is);
I found this information in this documentation:
http://docs.oracle.com/cd/E13222_01/wls/docs103/xml/programming.html#wp1069856
I hope this is helpful to someone.
S

Regarding Error in weblogic 11g deployment

The following Error occured when i deploy my Application in WEBLOGIC 11G Please can anyone help me for resolving this Urgent Issue..
Error occurred while processing weblogic-rdbms-bean.xml file: ‘fileName‘. Encountered an unexpected version of XML file. Make sure that your weblogic-rdbms-bean.xml file is the correct version (e.g. a common error is to use a 6.0.0 CMP20 cmp xml file on a 5.1.0 CMP11 Bean).EJB Name:com.foursoft.elog.chargeBasis.ejb.cmp.chargeBasisBean.XML processor:'Weblogic.ejb.container.cmp.rdbms.weblogicCmp20Loader_WLS810'

The following Error occured when i deploy my Application in WEBLOGIC 11G Please can anyone help me for resolving this Urgent Issue..
Error occurred while processing weblogic-rdbms-bean.xml file: ‘fileName‘. Encountered an unexpected version of XML file. Make sure that your weblogic-rdbms-bean.xml file is the correct version (e.g. a common error is to use a 6.0.0 CMP20 cmp xml file on a 5.1.0 CMP11 Bean).EJB Name:com.foursoft.elog.chargeBasis.ejb.cmp.chargeBasisBean.XML processor:'Weblogic.ejb.container.cmp.rdbms.weblogicCmp20Loader_WLS810'

Deploying ADF Webapplication (10.1.3) to Weblogic 11g (10.3.4)

Hello All,
I have a web application built using jsp, struts framework and ADF business component. Currently it's deployed on oracle application server. I have requirement where it needs to be deployed on Weblogic 11g (10.3.4. or higher)
Current version of Jdeveloper/ADF we are using is 10.1.3.
According to support matrix, Oracle JDeveloper 11g Application Server Certification Matrix
its possible to deploy applicaiton developed in 10.1.3 to weblogic 10.3.4. Thats what oracle says as per above link.
Is this correct? Has anyone tried it before?
I followed the steps mentioned at Deploying The SRDemo ADF Sample Application on WebLogic Servers and installed ADF runtime as per Installing ADF Runtime Library on Third-Party Application Servers
However when trying to deploy EAR file, I am getting classnot found exception for ADF/Classes.
<30-jan-2014 0:38:51 uur CET> <Error> <HTTP> <BEA-101165> <Could not load user defined filter in web.xml: ServletContext@29344664[app:ivfwebapp module:/ivfwebapp path:/ivfwebapp spe
java.lang.ClassNotFoundException: oracle.adf.model.servlet.ADFBindingFilter
        at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
        at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
        at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
        Truncated. see log file for complete stacktrace
>
<30-jan-2014 0:38:51 uur CET> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1391038730677' for task '0'. Error is: 'weblogic.appl
weblogic.application.ModuleException:
        at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
        at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
        at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
        at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
        Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: oracle.adf.model.servlet.ADFBindingFilter
        at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
        at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
        at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
        Truncated. see log file for complete stacktrace
>
<30-jan-2014 0:38:51 uur CET> <Error> <Deployer> <BEA-149202> <Encountered an exception while attempting to commit the 1 task for the application 'ivfwebapp'.>
<30-jan-2014 0:38:51 uur CET> <Warning> <Deployer> <BEA-149004> <Failures were detected while initiating deploy task for application 'ivfwebapp'.>
<30-jan-2014 0:38:51 uur CET> <Warning> <Deployer> <BEA-149078> <Stack trace for message 149004
weblogic.application.ModuleException:
        at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1510)
        at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
        at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
        at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
        at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
        Truncated. see log file for complete stacktrace
Caused By: java.lang.ClassNotFoundException: oracle.adf.model.servlet.ADFBindingFilter
        at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:297)
        at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:270)
        at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:64)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
        Truncated. see log file for complete stacktrace
>
I created ADF directory under WLS home and copied required ADF related jars under lib and jlib folder. Do I have to perform any more steps.
It's also mentioned on Deploying The SRDemo ADF Sample Application on WebLogic Servers
Class not found on oracle/adf classes when deploying the application
Verify that the setupadf.cmd file can be located by the WebLogic starting script.
Verify that you started the right domain with the right startup script.
Where can I find this cmd file and what needs to be in there? I am new to weblogic area. Can you please provide more details on this?
My question to ADF experts - Is it possible to deploy web application with ADF business component (only ADF BC) 10.1.3 to Weblogic 10.3.4?
If yes, could you please guide on how to accomplish it?
Note that application has ADF BC only no adf faces or jsf.
Thanks in advance.
Kind regards
Amol Relkar

Hello Shay,
Thanks you for your quick response.
Yes, my application works fine in embeded OC4J in Jdeveloper 10.1.3.
It also runs well on Oracle applicaition server v9.0.4.3.0 which there on test environment.
Current JDeveloper (10.1.3) doesn''t support weblogic 10.3.4 it seems, so I couldn't use ADF Runtime Installer wizard, when I do so it says - Selected directory is not a web logic home directory. So I followed steps manually mentioned in the same link - Installing ADF Runtime Library on Third-Party Application Servers
Basically I copied all mentioned jar files under <Weblogic_home>\ADF\lib and <Weblogic_home>\ADF\jlib
This is the correct way right?
If not could you please elaborate more on this.
Note: I have just ADF BC in my applicaiton no faces stuff.
Thanks in advance,
Kind Regards
Amol Relkar

Weblogic 11g Error

Hello ,
We are having an Spring based application which was running in weblogic 8.1 , we are migrating to weblogic 11g .
I created all the configurations in 11g as it was in 8.1 . But I am getting a set of errors as shown below while deploying the application.
Error while deploying
•     Substituted for missing class org.springframework.beans.FatalBeanException - Can't resolve reference to bean 'prixcarAdapter' while setting property 'messageHandler' on bean 'ftpAdapter';
•     nested exception is: org.springframework.beans.FatalBeanException: Can't resolve reference to bean 'prixcarGateway' while setting property 'gateway' on bean 'prixcarAdapter';
•     nested exception is: org.springframework.beans.FatalBeanException: Can't resolve reference to bean 'jmsPrixcarConnectionFactory' while setting property 'connectionFactory' on bean 'prixcarGateway';
•     nested exception is: org.springframework.beans.FatalBeanException: afterPropertiesSet() on bean with name 'jmsPrixcarConnectionFactory' threw exception;
•     nested exception is: javax.naming.NameNotFoundException: Unable to resolve 'PrixcarConnectionFactory'. Resolved ''; remaining name 'PrixcarConnectionFactory'
Log file error
The Message-Driven EJB: PRIXCAR_IMPORT_GATEWAY_QUEUE is unable to connect to the JMS destination: jms.PrixcarDamageQueue. The Error was: javax.naming.NameNotFoundException: Unable to resolve 'jms.PrixcarDamageQueue'. Resolved 'jms'; remaining name 'PrixcarDamageQueue' at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139) at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252) at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182) at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206) at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214) at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254) at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393) at javax.naming.InitialContext.lookup(InitialContext.java:392) at weblogic.jms.common.CDS$2.run(CDS.java:222) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:216) at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.createMDManagers(MessageDrivenBeanInfoImpl.java:1295) at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.activate(MessageDrivenBeanInfoImpl.java:1092) at weblogic.ejb.container.deployer.EJBDeployer.activate(EJBDeployer.java:1324) at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:480) at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:227) at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:415) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:75) at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:67) at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83) at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409) at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:54) at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161) at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844) at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253) at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java
In the spring xml I have configured the bean as shown below
<bean id="jmsPrixcarQueue" class="org.springframework.jndi.JndiObjectFactoryBean">
<property name="jndiName"><value>jms.PrixcarDamageQueue</value></property>
<property name="inContainer"><value>false</value></property>
</bean>
<bean id="jmsPrixcarConnectionFactory" class="org.springframework.jndi.JndiObjectFactoryBean">
<property name="jndiName"><value>jms.PrixcarConnectionFactory</value></property>
<property name="inContainer"><value>false</value></property>
</bean>
And in weblogic-ejb-jar.xml it is as shown below
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 8.1.0 EJB//EN"
"http://www.oracle.com/technology/weblogic/weblogic-ejb-jar/1.1/weblogic-ejb-jar.xsd">
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>PRIXCAR_IMPORT_GATEWAY_QUEUE</ejb-name>
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>1</max-beans-in-free-pool>
<initial-beans-in-free-pool>1</initial-beans-in-free-pool>
</pool>
<destination-jndi-name>jms.PrixcarDamageQueue</destination-jndi-name>
</message-driven-descriptor>
<enable-call-by-reference>True</enable-call-by-reference>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
I configured jms modules in weblogic 11g server console with the jndi names
jms.PrixcarDamageQueue
jms.PrixcarConnectionFactory
Please let us know the reason for this error also the doctype for 11g in weblogic-ejb-jar.xml above.
Edited by: user13295341 on Jun 15, 2010 5:21 AM

Jay and Maxence , I tried what you guys said by removing the jms. and using only PrixcarDamageQueue and PrixcarConnectionFactory but still I am getting an error like Namenotfound as shown below,
The Message-Driven EJB: PRIXCAR_IMPORT_GATEWAY_QUEUE is unable to connect to the JMS destination: PrixcarDamageQueue. The Error was: javax.naming.NameNotFoundException: Unable to resolve 'PrixcarDamageQueue'. Resolved ''; remaining name 'PrixcarDamageQueue' at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139) at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252) at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182) at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206) at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254) at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:393) at javax.naming.InitialContext.lookup(InitialContext.java:392) at weblogic.jms.common.CDS$2.run(CDS.java:222) at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363) at weblogic.jms.common.CDS.getDDMembershipInformation(CDS.java:216) at
My doubt is will queue be displayed in JNDI tree ?? I mean there is a JNDI tree in weblogic admin screen and I am getting only the PrixcarConnectionFactory in that and not the PrixcarDamageQueue , may be thats why its showing "unable to connect to the JMS ???" Please advice.....
I changed both the xml's and the JNDI names in the admin screen.

Weblogic 11g custom LoginModule

Similar Messages

Maybe you are looking for