"WebServiceServlet" failed to preload on startup - weblogic.developer.interest.webservices.general(Archived)

Hi,
I work on a WebService project based on Weblogic 8.1SP3.
I generate my beans with the autotype task using a XSD.
Then I generate the web-services.xml descriptor with the source2wsdd task.
Here is a part of this XSD :
<i><xs:schema targetNamespace="com.edfgdf.a16.application.impl.disws.mapping"
     xmlns:xs="http://www.w3.org/2001/XMLSchema"
     xmlns:disws="com.edfgdf.a16.application.impl.disws.mapping"
     elementFormDefault="unqualified"
     attributeFormDefault="unqualified"
     version="0.1">
     <xs:include schemaLocation="New-Disws.xsd"/></i>
I have got a problem with the <xs:include> section.
The autotype task support the <xs:include> and generates all the beans from the New-Disws.xsd schema.
But when I start my server, I have this exception :
<21 oct. 2005 09 h 42 CEST> <Error> <HTTP> <BEA-101216> <Servlet: "WebServiceServlet" failed to preload on startup in Web application: "disws".
javax.servlet.ServletException: WebServiceServlet did not initialized properly.weblogic.webservice.server.ConfigException: Failed to add generated schema - with nested exception:
[weblogic.xml.schema.model.XSDException: Failed to resolve ./New-Disws.xsd - with nested exception:
[weblogic.xml.schema.model.XSDException: error parsing external schema from schemaLocation ./New-Disws.xsd - with nested exception:
[java.net.MalformedURLException: no protocol: ./New-Disws.xsd]]]
     at weblogic.webservice.server.servlet.WebServiceServlet.initLocal(WebServiceServlet.java:128)
     at weblogic.webservice.server.servlet.WebServiceServlet.init(WebServiceServlet.java:86)
     at javax.servlet.GenericServlet.init(GenericServlet.java:258)
     at weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1018)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:118)
     at weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:894)
     at weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:873)
     at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:812)
     at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3281)
     at weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3226)
     at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3207)
     at weblogic.servlet.internal.HttpServer.preloadResources(HttpServer.java:694)
     at weblogic.servlet.internal.WebService.preloadResources(WebService.java:483)
     at weblogic.servlet.internal.ServletInitService.resume(ServletInitService.java:30)
     at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:131)
     at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:966)
     at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:361)
     at weblogic.Server.main(Server.java:32)
I tried to change the "schemaLocation" property of the <xs:include> section by giving the url of a Apache server where I put the New-Disws.xsd file and it works. But I didn't achieve to start my server even if I put the XSD file in my war.
Can somebody help me on this problem ?
Thanx in advance
Thibaut 

Did anyone find any work around to this issue?? I am facing the same problem 

Hello,
I had the same in Webloginc 8.1SP4.
The trivial (but not obvious!) solution was to replace it by import command, like:
<xsd:import schemaLocation="AdslCustomerConfiguration.xsd"/>
I can do this manually, but if you need to do it automatically, then I recommend to write XSL transformation and use the <xslt> ant task.
WBR
Vaclav

Related

Jacorb and thin client, classpath issues

I've got an issue when calling an ejb that calls a corba service.
WL 8.l.5
Basically the problem is exactly as described in this thread; using t3 and weblogic.jar works, but any other combo fails.
http://forums.bea.com/bea/message.jspa?messageID=600019126&tstart=0
The server has a bootstrap classpath that looks like this:
-Xbootclasspath:%JACORB_HOME%\lib\jacorb.jar;%JACORB_HOME%\lib\concurrent-1.3.2.jar;%JACORB_HOME%\lib\avalon-framework-4.1.5.jar;%JACORB_HOME%\lib\antlr-2.7.2.jar;%JACORB_HOME%\lib\idl.jar;%JACORB_HOME%\lib\logkit-1.2.jar;%JAVA_HOME%\jre\lib\rt.jar;
Note, that the jacorb.jar is first in the classpath.
Now, if I put the rt.jar first in the classpath, the problem dissappears. So I reckon the problem is related to the org.omg.CORBA classes that is bundled with the jdk, vs the classes bundled with jacorb. However, the sun corba classes are supposedly out of date and covers a smaller subject of the corba spec. And I'd prefer to use the wlclient.jar rather than the fat weblogic.jar.
This is the stacktrace that appears on the server:
<03-May-2006 15:48:19 o'clock BST> <Warning> <RMI> <BEA-080005> <Exception thrown by rmi server: sending exception
org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0.
org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
at weblogic.corba.cos.naming.NamingContextImpl.resolve(NamingContextImpl.java:162)
at weblogic.corba.cos.naming.NamingContextImpl.resolve_str(NamingContextImpl.java:415)
at weblogic.corba.cos.naming.RootNamingContextImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:492)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:435)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:430)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
And this is what I get on the client:
Error creating bean with name 'priceService' defined in class path resource [properties/reports/Reports-service-client.xml]: Initialization of bean failed; nested exception is javax.naming.NamingException: Unhandled exception in lookup
javax.naming.NamingException: Unhandled exception in lookup [Root exception is weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested exception:
[org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]]
     at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
     at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:237)
     at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:171)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at org.springframework.jndi.JndiTemplate$1.doInContext(JndiTemplate.java:123)
     at org.springframework.jndi.JndiTemplate.execute(JndiTemplate.java:85)
     at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:121)
     at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:146)
     at org.springframework.jndi.JndiLocatorSupport.lookup(JndiLocatorSupport.java:86)
     at org.springframework.jndi.JndiObjectLocator.lookup(JndiObjectLocator.java:104)
     at org.springframework.ejb.access.AbstractRemoteSlsbInvokerInterceptor.lookup(AbstractRemoteSlsbInvokerInterceptor.java:93)
     at org.springframework.ejb.access.AbstractSlsbInvokerInterceptor.refreshHome(AbstractSlsbInvokerInterceptor.java:102)
     at org.springframework.ejb.access.AbstractSlsbInvokerInterceptor.afterPropertiesSet(AbstractSlsbInvokerInterceptor.java:90)
     at org.springframework.ejb.access.SimpleRemoteStatelessSessionProxyFactoryBean.afterPropertiesSet(SimpleRemoteStatelessSessionProxyFactoryBean.java:95)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1091)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:396)
     at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:233)
     at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:145)
     at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:277)
     at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:313)
     at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:87)
     at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:72)
     at org.springframework.test.AbstractSpringContextTests.loadContextLocations(AbstractSpringContextTests.java:135)
     at org.springframework.test.AbstractDependencyInjectionSpringContextTests.loadContextLocations(AbstractDependencyInjectionSpringContextTests.java:224)
     at org.springframework.test.AbstractSpringContextTests.getContext(AbstractSpringContextTests.java:115)
     at org.springframework.test.AbstractDependencyInjectionSpringContextTests.setUp(AbstractDependencyInjectionSpringContextTests.java:192)
     at junit.framework.TestCase.runBare(TestCase.java:125)
     at junit.framework.TestResult$1.protect(TestResult.java:106)
     at junit.framework.TestResult.runProtected(TestResult.java:124)
     at junit.framework.TestResult.run(TestResult.java:109)
     at junit.framework.TestCase.run(TestCase.java:118)
     at junit.framework.TestSuite.runTest(TestSuite.java:208)
     at junit.framework.TestSuite.run(TestSuite.java:203)
     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:478)
     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:344)
     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
Caused by: weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested exception:
[org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]
     at weblogic.corba.cos.naming.NamingContextAny_IIOP_WLStub.resolve_any(Unknown Source)
     at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:213)
     ... 34 more 
Henric Larsson <> writes:
I don't think you can replace the core CORBA classes like this.
andy
I've got an issue when calling an ejb that calls a corba service.
WL 8.l.5
Basically the problem is exactly as described in this thread; using t3 and weblogic.jar works, but any other combo fails.
http://forums.bea.com/bea/message.jspa?messageID=600019126&tstart=0
The server has a bootstrap classpath that looks like this:
-Xbootclasspath:%JACORB_HOME%\lib\jacorb.jar;%JACORB_HOME%\lib\concurrent-1.3.2.jar;%JACORB_HOME%\lib\avalon-framework-4.1.5.jar;%JACORB_HOME%\lib\antlr-2.7.2.jar;%JACORB_HOME%\lib\idl.jar;%JACORB_HOME%\lib\logkit-1.2.jar;%JAVA_HOME%\jre\lib\rt.jar;
Note, that the jacorb.jar is first in the classpath.
Now, if I put the rt.jar first in the classpath, the problem dissappears. So I reckon the problem is related to the org.omg.CORBA classes that is bundled with the jdk, vs the classes bundled with jacorb. However, the sun corba classes are supposedly out of date and covers a smaller subject of the corba spec. And I'd prefer to use the wlclient.jar rather than the fat weblogic.jar.
This is the stacktrace that appears on the server:
<03-May-2006 15:48:19 o'clock BST> <Warning> <RMI> <BEA-080005> <Exception thrown by rmi server: sending exception
org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0.
org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
at weblogic.corba.cos.naming.NamingContextImpl.resolve(NamingContextImpl.java:162)
at weblogic.corba.cos.naming.NamingContextImpl.resolve_str(NamingContextImpl.java:415)
at weblogic.corba.cos.naming.RootNamingContextImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:492)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:435)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:430)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:35)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
And this is what I get on the client:
Error creating bean with name 'priceService' defined in class path resource [properties/reports/Reports-service-client.xml]: Initialization of bean failed; nested exception is javax.naming.NamingException: Unhandled exception in lookup
javax.naming.NamingException: Unhandled exception in lookup [Root exception is weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested exception:
[org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]]
     at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
     at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:237)
     at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:171)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at org.springframework.jndi.JndiTemplate$1.doInContext(JndiTemplate.java:123)
     at org.springframework.jndi.JndiTemplate.execute(JndiTemplate.java:85)
     at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:121)
     at org.springframework.jndi.JndiTemplate.lookup(JndiTemplate.java:146)
     at org.springframework.jndi.JndiLocatorSupport.lookup(JndiLocatorSupport.java:86)
     at org.springframework.jndi.JndiObjectLocator.lookup(JndiObjectLocator.java:104)
     at org.springframework.ejb.access.AbstractRemoteSlsbInvokerInterceptor.lookup(AbstractRemoteSlsbInvokerInterceptor.java:93)
     at org.springframework.ejb.access.AbstractSlsbInvokerInterceptor.refreshHome(AbstractSlsbInvokerInterceptor.java:102)
     at org.springframework.ejb.access.AbstractSlsbInvokerInterceptor.afterPropertiesSet(AbstractSlsbInvokerInterceptor.java:90)
     at org.springframework.ejb.access.SimpleRemoteStatelessSessionProxyFactoryBean.afterPropertiesSet(SimpleRemoteStatelessSessionProxyFactoryBean.java:95)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1091)
     at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:396)
     at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:233)
     at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:145)
     at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:277)
     at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:313)
     at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:87)
     at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:72)
     at org.springframework.test.AbstractSpringContextTests.loadContextLocations(AbstractSpringContextTests.java:135)
     at org.springframework.test.AbstractDependencyInjectionSpringContextTests.loadContextLocations(AbstractDependencyInjectionSpringContextTests.java:224)
     at org.springframework.test.AbstractSpringContextTests.getContext(AbstractSpringContextTests.java:115)
     at org.springframework.test.AbstractDependencyInjectionSpringContextTests.setUp(AbstractDependencyInjectionSpringContextTests.java:192)
     at junit.framework.TestCase.runBare(TestCase.java:125)
     at junit.framework.TestResult$1.protect(TestResult.java:106)
     at junit.framework.TestResult.runProtected(TestResult.java:124)
     at junit.framework.TestResult.run(TestResult.java:109)
     at junit.framework.TestCase.run(TestCase.java:118)
     at junit.framework.TestSuite.runTest(TestSuite.java:208)
     at junit.framework.TestSuite.run(TestSuite.java:203)
     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:478)
     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:344)
     at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196)
Caused by: weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with nested exception:
[org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]
     at weblogic.corba.cos.naming.NamingContextAny_IIOP_WLStub.resolve_any(Unknown Source)
     at weblogic.corba.j2ee.naming.ContextImpl.lookup(ContextImpl.java:213)
     ... 34 more 
I've been discussing this issue on the jacorb mailing list, and they suggest that replacing the ORB in weblogic is a bad idea. I've done this by passing the following to the java vm in the weblogic startup script:
-Dorg.omg.CORBA.ORBClass=org.jacorb.orb.ORB
-Dorg.omg.CORBA.ORBSingletonClass=org.jacorb.orb.ORBSingleton
Given that it doesn't work I assume my configuration breaks weblogic, but I just need confirmation. Also, in what way is corba used internally by weblogic when looking up EJB's? 
Henric Larsson <> writes:
The thin-client uses RMI-IIOP which uses the WebLogic ORB. In theory
you should be able to use your own orb in ORB.init() and still use the
WLS singleton ORB without breaking WebLogic. That's the way its
supposed to work, but I've never tested it and have found that many
orbs have an overly-incestuous relationship with their singleton. But
specifying these pieces on the command-line will definitely break
RMI-IIOP.
YMMV
andy
I've been discussing this issue on the jacorb mailing list, and they suggest that replacing the ORB in weblogic is a bad idea. I've done this by passing the following to the java vm in the weblogic startup script:
-Dorg.omg.CORBA.ORBClass=org.jacorb.orb.ORB
-Dorg.omg.CORBA.ORBSingletonClass=org.jacorb.orb.ORBSingleton
Given that it doesn't work I assume my configuration breaks weblogic, but I just need confirmation. Also, in what way is corba used internally by weblogic when looking up EJB's? 
Ok, thanks for your help.
I've got it working with the weblogic orb instead, but I need to use jacorb for corba QoS so I need to come up with another solution.
Is there any best practices or recommended ways of using jacorb with weblogic? 
Henric Larsson <> writes:
Can you try my previous suggestion of specifying jacorb in ORB.init()? Or are there class
collisions in the core CORBA classes?
andy
Ok, thanks for your help.
I've got it working with the weblogic orb instead, but I need to use jacorb for corba QoS so I need to come up with another solution.
Is there any best practices or recommended ways of using jacorb with weblogic? 
Ok, I've tried the following in ORB.init(). And removed the bootstrap classpath entries and -D options for speciying orb.
'ORBInitRef.NameService' -> 'corbaloc:iiop:xxxxxxxxxxx:5353/NameService'
'jacorb.compactTypecodes' -> '0'
'jacorb.connection.client.pending_reply_timeout' -> '2000'
'jacorb.interop.chunk_custom_rmi_valuetypes' -> 'on'
'jacorb.interop.strict_check_on_tc_creation' -> 'on'
'jacorb.naming.noping' -> 'on'
'jacorb.naming.purge' -> 'on'
'jacorb.outbuf_size' -> '2048'
'jacorb.security.access_decision' -> 'org.jacorb.security.level2.AccessDecisionImpl'
'jacorb.security.principal_authenticator' -> 'org.jacorb.security.level2.PrincipalAuthenticatorImpl'
'org.omg.CORBA.ORBClass' -> 'org.jacorb.orb.ORB'
'org.omg.PortableInterceptor.ORBInitializerClass.standard_init' -> 'org.jacorb.orb.standardInterceptors.IORInterceptorInitializer'
But I get the following exception on the server:
uk.co.igindex.service.NotFound: IDL:uk/co/igindex/service/NotFound:1.0
at uk.co.igindex.service.NotFoundHelper.read(NotFoundHelper.java:38)
at uk.co.igindex.service._QuotePriceServiceStub.getByEpic(_QuotePriceServiceStub.java:164)
at uk.co.igindex.priceservice.service.price.corba.managed.FinancialManagedPriceService.fetchPrice(FinancialManagedPriceService.java:148)
... 14 more
I found this document that mentions some kind of weblogic adapter for Corba and which contains an example of using jacorb. But I'm not quite sure if I can use this adapter thing to solve my problem. Any ideas?
http://edocs.bea.com/wladapters/corba/docs811/pdf/install.pdf 
I've made a mistake that I just realized so ignore the exception in my last post.
I do get it to work now when specifying the orb in ORB.init()
However, In order for jacorb to load properly I must modify the bootstrap classpath like this:
set JAVA_OPTIONS=%JAVA_OPTIONS% -Xbootclasspath:%JAVA_HOME%\jre\lib\rt.jar;%JACORB_HOME%\lib\jacorb.jar;%JACORB_HOME%\lib\concurrent-1.3.2.jar;%JACORB_HOME%\lib\avalon-framework-4.1.5.jar;%JACORB_HOME%\lib\antlr-2.7.2.jar;%JACORB_HOME%\lib\idl.jar;%JACORB_HOME%\lib\logkit-1.2.jar;
If I just add i to the normal CLASSPATH I get a ClassNotFoundException: org.jacorb.orb.ORB 
Henric Larsson <> writes:
I've made a mistake that I just realized so ignore the exception in my last post.
I do get it to work now when specifying the orb in ORB.init()
However, In order for jacorb to load properly I must modify the bootstrap classpath like this:
set JAVA_OPTIONS=%JAVA_OPTIONS% -Xbootclasspath:%JAVA_HOME%\jre\lib\rt.jar;%JACORB_HOME%\lib\jacorb.jar;%JACORB_HOME%\lib\concurrent-1.3.2.jar;%JACORB_HOME%\lib\avalon-framework-4.1.5.jar;%JACORB_HOME%\lib\antlr-2.7.2.jar;%JACORB_HOME%\lib\idl.jar;%JACORB_HOME%\lib\logkit-1.2.jar;
If I just add i to the normal CLASSPATH I get a ClassNotFoundException: org.jacorb.orb.ORBHmmn, putting stuff in the bootclasspath is a little dicey. Many of
these classes will need to be in the system classpath to work. If you
are using a web app or ejb jar you could try putting some of the
libraries in the lib dir (or use the domain lib dir).
andy 
Yes, I resolved the issue by doing that.
I put all jacorb libs in the EAR file, and specified which orb to use in the properties for ORB.init()
Everything works as expected now.
Thank you.

Servlet failed with NullPointerException in weblogic 8.1 portal cluster

Hi All,
I am having weblogic 8.1 cluster server with two managed server. If i restart my primary managed server and click on any popup window link i am getting follwing error. But if i am accessing application from other than pop up link it is working properly.
<Nov 4, 2009 7:15:52 AM PST> <Error> <HTTP> <BEA-101020> <ServletContext(id=9998762,name=*******,context-path=/******) Servlet failed with Exception
java.lang.NullPointerException
at com.bea.wlw.netui.pageflow.FlowController.valueUnbound(FlowController.java:2078)
at com.bea.wlw.netui.pageflow.PageFlowController.valueUnbound(PageFlowController.java:592)
at com.bea.wlw.netui.pageflow.internal.DeferredSessionStorageHandler.setAttribute(DeferredSessionStorageHandler.java:136)
at com.bea.wlw.netui.pageflow.PageFlowUtils.setCurrentActionResolver(PageFlowUtils.java:597)
at com.bea.wlw.netui.pageflow.PageFlowUtils.setCurrentPageFlow(PageFlowUtils.java:572)
at com.bea.wlw.netui.pageflow.PageFlowController.persistInSession(PageFlowController.java:162)
at com.bea.wlw.netui.pageflow.FlowControllerFactory.getPageFlow(FlowControllerFactory.java:428)
at com.bea.wlw.netui.pageflow.FlowControllerFactory.getPageFlow(FlowControllerFactory.java:129)
at com.bea.wlw.netui.pageflow.FlowControllerFactory.getPageFlow(FlowControllerFactory.java:111)
at com.bea.wlw.netui.pageflow.FlowControllerFactory.getPageFlowForRequest(FlowControllerFactory.java:70)
at com.bea.wlw.netui.pageflow.PageFlowUtils.ensureCurrentPageFlow(PageFlowUtils.java:463)
at com.bea.wlw.netui.pageflow.PageFlowJspFilter.doFilter(PageFlowJspFilter.java:193)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:7053)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3902)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2756)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)
Any path forward to tackle this issue.
Thanks!!!!
Regards,
SandeepK 
whats your replication setting - if you havent replicated then this wont work? Have you verified the replication is successful by perhaps printing out session values for the same session on both managed servers?
If yes
Is this only happening for this one link or any link , popup or otherwise or for anything?
Is the servlet with the name blanked out your servlet or BEA's?
Looks to be something that you probably need to take up with Oracle support since I cant see any of your code coming into it?
regards
deepak 
Hi deepak,
Session settings
1) All session variable are serialized.
2)<session-param>
<param-name>PersistentStoreType</param-name>
<param-value>replicated_if_clustered</param-value>
</session-param>
I am having 2 managed server. If request is going to first managed server session object are being printed on managed server one logs only not to second managed server logs. is it okay? or it should get printed on both logs.
This problem is happening for all not only for links. I have modified (put some system.out) the Global.app but i am not getting any logs from there.
Blanked out thing is my application name nothing else.
How to start debugging it.
Regards,
SandeepK 
If its only happening on particular links that you probably need to contact Oracle Support , Im dont know what else you could try.. 
Hello Sandeep,
Are you running on the latest service pack for WLP 8.1? This may have been fixed in one of the later service packs.
If you're on the latest service pack, Deepak is right- contact Oracle support.
Kevin 
Hi Kevin,
I am having 8.1 SP6.
Regards,
SandeepK 
Hi,
I my case the same error is coming when session replication is happening. This is happening only for some links and not for all links. Any suggestions please?
<Dec 6, 2011 5:13:49 PM GMT+05:30> <Error> <HTTP> <BEA-101020> <[ServletContext(id=5816641,name=Abc,context-path=/Abc)] Servlet failed with Exception
java.lang.NullPointerException
     at com.bea.wlw.netui.pageflow.FlowController.valueUnbound(FlowController.java:2078)
     at com.bea.wlw.netui.pageflow.PageFlowController.valueUnbound(PageFlowController.java:592)
     at com.bea.wlw.netui.pageflow.internal.DeferredSessionStorageHandler.setAttribute(DeferredSessionStorageHandler.java:136)
     at com.bea.wlw.netui.pageflow.PageFlowUtils.setCurrentActionResolver(PageFlowUtils.java:597)
     at com.bea.wlw.netui.pageflow.PageFlowUtils.setCurrentPageFlow(PageFlowUtils.java:572)
     at com.bea.wlw.netui.pageflow.PageFlowController.persistInSession(PageFlowController.java:162)
     at com.bea.wlw.netui.pageflow.FlowControllerFactory.getPageFlow(FlowControllerFactory.java:428)
     at com.bea.wlw.netui.pageflow.FlowControllerFactory.getFlowController(FlowControllerFactory.java:233)
     at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor.processActionCreate(PageFlowRequestProcessor.java:144)
     at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:268)
     at com.bea.wlw.netui.pageflow.PageFlowRequestProcessor.process(PageFlowRequestProcessor.java:691)
     at com.bea.wlw.netui.pageflow.AutoRegisterActionServlet.process(AutoRegisterActionServlet.java:527)
     at com.bea.wlw.netui.pageflow.PageFlowActionServlet.process(PageFlowActionServlet.java:152)
     at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:507)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1077)
     at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:465)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:28)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
     at arq.component.trail.taglib.OriginalRequestFilter.doFilter(OriginalRequestFilter.java:45)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:27)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:7053)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3902)
     at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2773)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:224)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:183)

Deployment descriptor /WEB-INF/url-template-config.xml malformed

Hi all
I installed weblogic 9.1 in existing environment replacing weblogic 8.1.
i changed config.xml and deployment descriptor.
after starting the server following exceptions are throwing.
<May 8, 2006 2:25:58 AM PDT> <Error> <netuix> <BEA-423103> <[] Deployment descriptor /WEB-INF/url-template-config.xml malformed.>
javax.servlet.ServletException: error: The document is not a url-template-config#http://www.bea.com/servers/weblogic/url-template-config/8.0: document element namespace mismatch expected "http://www.bea.com/servers/weblogic/url-template-config/8.0" got "http://www.bea.com/servers/weblogic/url-template-config/9.0"
     at com.bea.netuix.servlets.manager.AppDescriptor.loadDescriptor(AppDescriptor.java:860)
     at com.bea.netuix.servlets.manager.SingleFileServlet.init(SingleFileServlet.java:99)
     at javax.servlet.GenericServlet.init(GenericServlet.java:256)
     at weblogic.servlet.AsyncInitServlet.initDelegate(AsyncInitServlet.java:94)
     at weblogic.servlet.internal.WebAppServletContext$AsyncInitRequest.run(WebAppServletContext.java:1641)
     at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:179)
Caused by: com.bea.xml.XmlException: error: The document is not a url-template-config#http://www.bea.com/servers/weblogic/url-template-config/8.0: document element namespace mismatch expected "http://www.bea.com/servers/weblogic/url-template-config/8.0" got "http://www.bea.com/servers/weblogic/url-template-config/9.0"
     at com.bea.xbean.store.Locale.verifyDocumentType(Locale.java:452)
     at com.bea.xbean.store.Locale.autoTypeDocument(Locale.java:357)
     at com.bea.xbean.store.Locale.parseToXmlObject(Locale.java:1273)
     at com.bea.xbean.store.Locale.parseToXmlObject(Locale.java:1257)
     at com.bea.xbean.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:345)
     at com.bea.netuix.servlets.manager.types.url_template_config.UrlTemplateConfigDocument$Factory.parse(UrlTemplateConfigDocument.java:216)
     at com.bea.netuix.servlets.manager.AppDescriptor.loadUrlTemplates(AppDescriptor.java:741)
     at com.bea.netuix.servlets.manager.AppDescriptor.loadDescriptor(AppDescriptor.java:847)
     ... 7 more
Please mention the remedy to get rid of it. 
Hello, The error listed is due to a mismatch between a descriptor in the administration console and one of it's frameworks it's using (i.e. the framework expects a slightly different descriptor). The error itself won't cause the console to stop working.
To get rid of it you can go the following routes:
1) Work with support to request an fix
2) Update to 9.2
3) Configure your log4j settings in WLS to not emit the message.
The last one doesn't really fix it, but will not print the error which is harmless (but ugly).
HTH,
Mike

WebLogic - JCA - SAP - sapjra.rar

Hi,
I am trying to deploy sapjra.rar (which I have downloaded from SAP and successfully deployed to JBoss and SAP Web As 6.4) to my Weblogic 7sp2 server, but I get the following error message... Does anybody have ever tried this?
Thank you
Dov
weblogic.management.ApplicationException: Prepare failed. Task Id = 3
{
Module Name: sapjra, Error: weblogic.xml.process.XMLProcessingException: PAction[2535149](.connector.resourceadapter.authentication-mechanism.authentication-mechanism-type.) must be one of the values: BasicPassword - with nested exception:
[weblogic.xml.process.SAXValidationException: PAction[2535149](.connector.resourceadapter.authentication-mechanism.authentication-mechanism-type.) must be one of the values: BasicPassword]
}
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:720)
     at weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java:555)
     at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1062)
     at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:730)
     at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread

Newly installed Service Registry gets Error 500 - Updates to config files..

Newly installed Service Registry gets "Error 500--Internal Server Error - Updates to config files not supported" when opening web page http://localhost:7001/registry/uddi/web. Deployment screen in WLS Console has a check mark in the health check column. 
Did you do post install steps after installation i.e.
a) Create JDBC data source with jndi name as jdbc/registryDS in WLS console and point to UDDI schema
b) Add JAAS config in JAVA_OPTIONS in setDomainEnv.sh as follows:
-Djava.security.auth.login.config=/<Oracle_HOME>/registry103/conf/jaas.config
c) Bounce WLS. 
I performed all the post install tasks and discovered that I am getting an error during the completion of WLS initialization. Error is included below.
java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method "com.idoox.wsdl.DefinitionImpl.getMessage(Ljavax/xml/namespace/QName;)Ljavax/wsdl/Message;" the class loader (instance of weblogic/utils/classloaders/ChangeAwareClassLoader) of the current class, com/idoox/wsdl/DefinitionImpl, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for interface javax/wsdl/Definition have different Class objects for the type javax/xml/namespace/QName used in the signature
Notice, two class loaders:
weblogic/utils/classloaders/ChangeAwareClassLoader
sun/misc/Launcher$AppClassLoader
So, like URL (http://stackoverflow.com/questions/244482/how-to-deal-with-linkageerrors-in-java) mentions, if a class is loaded by Class Loader #1 and passed to an object created by Class Loader #2, this exception is going to be thrown.
####<Sep 3, 2009 9:11:43 AM MDT> <Error> <HTTP> <w2wz3lcw05> <AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1251990703468> <BEA-101017> <[ServletContext#5399772[app:registry module:registry.war path:/registry spec-version:2.5], request: weblogic.servlet.internal.ServletRequestImpl#ab1c28[
GET /registry/uddi/inquiry/wsdl HTTP/1.1
User-Agent: Java1.6.0_11
Accept: text/html, image/gif, image/jpeg, */*; q=.2
Connection: Keep-Alive
]] Root cause of ServletException.
java.lang.LinkageError: loader constraint violation in interface itable initialization: when resolving method "com.idoox.wsdl.DefinitionImpl.getMessage(Ljavax/xml/namespace/QName;)Ljavax/wsdl/Message;" the class loader (instance of weblogic/utils/classloaders/ChangeAwareClassLoader) of the current class, com/idoox/wsdl/DefinitionImpl, and the class loader (instance of sun/misc/Launcher$AppClassLoader) for interface javax/wsdl/Definition have different Class objects for the type javax/xml/namespace/QName used in the signature
     at com.idoox.wsdl.factory.WSDLFactoryImpl.newDefinition(WSDLFactoryImpl.java:60)
     at com.idoox.wsdl.xml.WSDLReaderImpl.parseDefinitions(WSDLReaderImpl.java:419)
     at com.idoox.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:309)
     at com.idoox.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:272)
     at com.idoox.wsdl.xml.WSDLReaderImpl.readWSDL(WSDLReaderImpl.java:198)
     at com.idoox.wsdl.util.WSDLUtil.readWSDL(WSDLUtil.java:126)
     at com.systinet.wasp.admin.PackageRepositoryImpl.validateServicesNamespaceAndName(PackageRepositoryImpl.java:885)
     at com.systinet.wasp.admin.PackageRepositoryImpl.registerPackage(PackageRepositoryImpl.java:807)
     at com.systinet.wasp.admin.PackageRepositoryImpl.updateDir(PackageRepositoryImpl.java:611)
     at com.systinet.wasp.admin.PackageRepositoryImpl.updateDir(PackageRepositoryImpl.java:643)
     at com.systinet.wasp.admin.PackageRepositoryImpl.update(PackageRepositoryImpl.java:553)
     at com.systinet.wasp.admin.PackageRepositoryImpl.init(PackageRepositoryImpl.java:242)
     at com.idoox.wasp.ModuleRepository.loadModules(ModuleRepository.java:198)
     at com.systinet.wasp.WaspImpl.boot(WaspImpl.java:383)
     at org.systinet.wasp.Wasp.init(Wasp.java:151)
     at com.systinet.transport.servlet.server.Servlet.init(Unknown Source)
     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.ServletStubImpl.execute(ServletStubImpl.java:235)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:202)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3588)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2200)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2106)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1428)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) 
Hi timdsmith,
did you find a solution to this? I face the same problem, installed Service Registry 10.3 on WebLogic 10.3.1 & Database 11g with no errors. deployment went fine. When I try to acces console I get the same error message:
Error 500--Internal Server Error
org.idoox.wasp.WaspInternalException: java.lang.RuntimeException: Updates to config files not supported
Thx 
Hi user8631539,
Haven't found a resolution yet. Will post one if I do and you can do the same.
Thanks 
Yes, I have yet another casualty on this. I have seen a few similar topics on this...but they all seem to relate to using OC4J and not WLS. 
The problem was trying to install UDDI Registry in a weblogic container with SOA modules deployes.. If you install the uddi registry in a plain empty weblogic every thing will be ok.. There must be some conflic between soa jar libraries versions.. 
Please do check the following thread for exact behaviour of issue
OSR Installation to weblogic cluster
Any suggestions... i have compatible versions of OSR and Weblogic 11g (11.1.1.2 versions) and dedicated instance and domain for OSR only.
Still it keeps giving me the same error
]] Root cause of ServletException.
java.lang.ExceptionInInitializerError
     at com.systinet.wasp.admin.PackageRepositoryImpl.validateServicesNamespaceAndName(PackageRepositoryImpl.java:885)
     at com.systinet.wasp.admin.PackageRepositoryImpl.registerPackage(PackageRepositoryImpl.java:807)
     at com.systinet.wasp.admin.PackageRepositoryImpl.updateDir(PackageRepositoryImpl.java:611)
Caused By: java.lang.RuntimeException: Cannot instantiate WSDLFactory:WSDLException: faultCode=CONFIGURATION_ERROR: Problem instantiating factory implementation.: com.idoox.wsdl.factory.WSDLFactoryImpl
     at com.idoox.wsdl.util.WSDLUtil.<clinit>(WSDLUtil.java:75)
And upon restart of server and the registry application
]] Root cause of ServletException.
org.idoox.wasp.WaspInternalException: java.lang.RuntimeException: Updates to config files not supported
at com.systinet.wasp.WaspImpl.boot(WaspImpl.java:399)
at org.systinet.wasp.Wasp.init(Wasp.java:151)

Categories

Resources