Advertisement

01.30.2008 at 06:24AM PST, ID: 23122761
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!
8.0

Error During Config.xml parsing

Asked by madhuthetom in BEA WebLogic Application Server, Extensible Markup Language (XML), J2EE

Tags:

I am trying to port an application from weblogic 81. to 9.2 . I have migrated the application, I am having 2 issues which is preventing me from completing the migration

Issue 1:

In the server console I get this exception.

<Jan 29, 2008 5:22:13 PM EST> <Error> <Management> <BEA-141244> <Schema validation errors while parsing C:\bea\user_projects\domains\forexware\config\config.xml - Type 'T=fip-authenticatorType@http://www.bea.com/ns/weblogic/90/sec
urity/extension' is not derived from 'T=authentication-providerType@http://www.bea.com/ns/weblogic/90/security' in element realm@http://www.bea.com/ns/weblogic/920/domain>
<Jan 29, 2008 5:22:13 PM EST> <Error> <Management> <BEA-141244> <Schema validation errors while parsing C:\bea\user_projects\domains\forexware\config\config.xml - Type 'T=fip-authorizerType@http://www.bea.com/ns/weblogic/90/securi
ty/extension' is not derived from 'T=authorizerType@http://www.bea.com/ns/weblogic/90/security' in element realm@http://www.bea.com/ns/weblogic/920/domain>



Issue 2:

javax.naming.NoPermissionException: User AZ1003A does not have permission on weblogic.fip.jms to perform list operation. [Root exception is javax.naming.NoPermissionException: User AZ1003A does not have permission on weblogic.fip.jms to perform list operation.]
      at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:211)
      at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:338)
      at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)
      at weblogic.jndi.internal.ServerNamingNode_922_WLStub.list(Unknown Source)
      at weblogic.jndi.internal.WLContextImpl.list(WLContextImpl.java:191)
      at javax.naming.InitialContext.list(InitialContext.java:395)
      at fip.utils.core.jndi.ContextParser.getAvailableServerIds(ContextParser.java:48)
      at fip.utils.core.serviceholder.impl.RemoteServiceProvider.findServerIds(RemoteServiceProvider.java:235)
      at fip.utils.core.serviceholder.impl.RemoteServiceProvider.<init>(RemoteServiceProvider.java:62)
      at fip.ui.common.utier.FIPClientSyncApplication.establishConnection(FIPClientSyncApplication.java:311)
      at fip.ui.common.utier.FIPClientSyncApplication.createApplication(FIPClientSyncApplication.java:245)
      at fip.ui.b.i.init(i.java:86)
      at UIApplication.main(UIApplication.java:68)
      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 fip.ui.updatemgmt.aptget.Launcher.<init>(Launcher.java:80)
      at fip.ui.updatemgmt.aptget.AptGet.launch(AptGet.java:1239)
      at fip.ui.updatemgmt.aptget.AptGet.init(AptGet.java:362)
      at fip.ui.updatemgmt.aptget.AptGet.<init>(AptGet.java:158)
      at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
      at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
      at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
      at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
      at fip.ui.updatemgmt.apt.UM.aptget(UM.java:176)
      at fip.ui.updatemgmt.apt.UM.<init>(UM.java:75)
      at fip.ui.updatemgmt.apt.UM.main(UM.java:59)
Caused by: javax.naming.NoPermissionException: User AZ1003A does not have permission on weblogic.fip.jms to perform list operation.
      at weblogic.jndi.internal.ServerNamingNode.checkPermission(ServerNamingNode.java:415)
      at weblogic.jndi.internal.ServerNamingNode.checkList(ServerNamingNode.java:390)
      at weblogic.jndi.internal.ServerNamingNode.listThis(ServerNamingNode.java:157)
      at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:627)
      at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:643)
      at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:643)
      at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:643)
      at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
      at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:550)
      at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:224)
      at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:440)
      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:436)
      at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:58)
      at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:975)
      at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
      at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)


Please suggest me if you have any idea abt these exception. I have been working with this for 2 days now, but no resultStart Free Trial
 
Keywords: Error During Config.xml parsing
Title
1 PAR Protocol
2 par file
3 Par files
4 Par. Query
5 weblogic deployment
6 PAR utility for newbie
 
Loading Advertisement...
 
[+][-]01.30.2008 at 09:00AM PST, ID: 20778708

View this solution now by starting your 30-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: BEA WebLogic Application Server, Extensible Markup Language (XML), J2EE
Tags: Weblogic 9.2 Migration issues
Sign Up Now!
Solution Provided By: bpmurray
Participating Experts: 1
Solution Grade: A
 
 
[+][-]08.29.2008 at 07:43AM PDT, ID: 22345902

Experts Exchange has a courteous staff of administrators who help members get the most out of the website by means of administrative comments like this one.

Start your 30-day free trial to view this Administrative Comment or ask the Experts your question.

 
[+][-]09.02.2008 at 05:23PM PDT, ID: 22373012

Experts Exchange has a courteous staff of administrators who help members get the most out of the website by means of administrative comments like this one.

Start your 30-day free trial to view this Administrative Comment or ask the Experts your question.

 
 
Loading Advertisement...
20081112-EE-VQP-44 / EE_QW_2_20070628