NullPointerException in WebLogic JCABindingManager
While deploying an application known to have previously worked, I am encountering the following issue. Unfortunately, I do not have access to WLS source code which is makes diagnosing this issue impossible. Any pointers would be appreciated.
java -cp $WL_HOME/server/lib/weblogic.jar weblogic.version
WebLogic Server 10.3.1.0 Thu Jun 25 17:41:07 EDT 2009 1232752
<Jul 31, 2009 12:59:53 PM PDT> <Warning> <EJB> <BEA-010221> <The Message-Driven EJB: FooBarEndpoint is unable to bind to the JCA resource adapter: foo/bar. The Error was:
java.lang.NullPointerException
at weblogic.utils.bean.BeanInitializer.setValue(BeanInitializer.java:234)
at weblogic.utils.bean.BeanInitializer.initializeBean(BeanInitializer.java:174)
at weblogic.utils.bean.BeanInitializer.initializeBean(BeanInitializer.java:201)
at weblogic.ejb.container.internal.JCABindingManager.setActivationSpec(JCABindingManager.java:216)
at weblogic.ejb.container.internal.JCABindingManager.connect(JCABindingManager.java:115)
at weblogic.ejb.container.internal.MDConnectionManager.startConnectionPolling(MDConnectionManager.java:239)
at weblogic.ejb.container.manager.MessageDrivenManager.start(MessageDrivenManager.java:583)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.mdManagerStart(MessageDrivenBeanInfoImpl.java:1163)
at weblogic.ejb.container.deployer.MessageDrivenBeanInfoImpl.deployMessageDrivenBeans(MessageDrivenBeanInfoImpl.java:1115)
at weblogic.ejb.container.deployer.EJBDeployer.deployMessageDrivenBeans(EJBDeployer.java:1663)
at weblogic.ejb.container.deployer.EJBDeployer.start(EJBDeployer.java:1486)
at weblogic.ejb.container.deployer.EJBModule.start(EJBModule.java:601)
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.EarDeployment.activate(EarDeployment.java:53)
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)
That appears to be a bug in the console. Please contact [email protected]
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/
Similar Messages
-
NullPointerException from weblogic.i18ntools.l10ngen
Using the environment for the example server (on winNT)...
Go to \bea\wlserver6.1_beta\samples\examples\i18n\logging and run
build. The build go boom with the following stack track...
D:\bea\wlserver6.1_beta\samples\examples\i18n\logging>java weblogic.i18ntools.l1
0ngen -verbose -d d:\bea\wlserver6.1_beta\config\examples\clientclasses ..\msgca
t\I18nLog.xml ..\msgcat\I18nSimple.xml
Parsing catalog, D:\bea\wlserver6.1_beta\samples\examples\i18n\msgcat\fr\I18nLog
.xml
java.lang.NullPointerException
java.lang.NullPointerException
at weblogic.common.internal.PeerInfo.<init>(PeerInfo.java:25)
at weblogic.rjvm.LocalRJVM.<init>(LocalRJVM.java:130)
at weblogic.rjvm.LocalRJVM.getLocalRJVM(LocalRJVM.java:99)
at weblogic.i18ntools.L10nLookup$Logger.<init>(L10nLookup.java:282)
at weblogic.i18ntools.L10nLookup.<init>(L10nLookup.java:114)
at weblogic.i18ntools.L10nLookup.init(L10nLookup.java:70)
at weblogic.i18ntools.L10nLookup.getL10n(L10nLookup.java:58)
at weblogic.i18ntools.parser.LocaleLogMessage.validate(LocaleLogMessage.
java:65)
at weblogic.i18ntools.parser.LocaleMessageCatalog.validate(LocaleMessage
Catalog.java:240)
at weblogic.i18ntools.parser.LocaleCatalogParser.endDocument(LocaleCatal
ogParser.java:175)
at org.xml.sax.helpers.XMLReaderAdapter.endDocument(XMLReaderAdapter.java:286)
at weblogic.apache.xerces.parsers.SAXParser.endDocument(SAXParser.java:1
230)
at weblogic.apache.xerces.validators.common.XMLValidator.callEndDocument
(XMLValidator.java:1064)
at weblogic.apache.xerces.framework.XMLDocumentScanner$EndOfInputDispatc
her.dispatch(XMLDocumentScanner.java:1555)
at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocu
mentScanner.java:381)
at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:967)
at org.xml.sax.helpers.XMLReaderAdapter.parse(XMLReaderAdapter.java:223)
at weblogic.i18ntools.parser.LocaleCatalogParser.parse(LocaleCatalogPars
er.java:126)
at weblogic.i18ntools.l10ngen.parseIt(l10ngen.java:327)
at weblogic.i18ntools.l10ngen.buildLangOutputs(l10ngen.java:302)
at weblogic.i18ntools.l10ngen.generate(l10ngen.java:406)
at weblogic.i18ntools.l10ngen.run(l10ngen.java:423)
at weblogic.i18ntools.l10ngen.main(l10ngen.java:459)
java.lang.NullPointerException
weblogic.i18n.tools.GenException: Code gen exception: Parse failed for: D:\bea\w
lserver6.1_beta\samples\examples\i18n\logging\..\msgcat\fr\I18nLog.xmlLauren,
Actually, it does not appear as though the example itself is
broken. The example looks the same as the one that worked fine under
WLS 6.0. The example seems to expose a something that is broken (a
regression?) in the codegen tool or in the API.
Ben
On 20 Jun 2001 11:31:02 -0800, Lauren Wright <[email protected]> wrote:
>
Ben,
I forwarded your message to the appropriate group.
Would you mind reposting to the examples newsgroup?
Lauren
[email protected] (Ben Eng) wrote:
Using the environment for the example server (on winNT)...
Go to \bea\wlserver6.1_beta\samples\examples\i18n\logging and run
build. The build go boom with the following stack track...
D:\bea\wlserver6.1_beta\samples\examples\i18n\logging>java weblogic.i18ntools.l1
0ngen -verbose -d d:\bea\wlserver6.1_beta\config\examples\clientclasses
..\msgca
t\I18nLog.xml ..\msgcat\I18nSimple.xml
Parsing catalog, D:\bea\wlserver6.1_beta\samples\examples\i18n\msgcat\fr\I18nLog
..xml
java.lang.NullPointerException
java.lang.NullPointerException
at weblogic.common.internal.PeerInfo.<init>(PeerInfo.java:25)
at weblogic.rjvm.LocalRJVM.<init>(LocalRJVM.java:130)
at weblogic.rjvm.LocalRJVM.getLocalRJVM(LocalRJVM.java:99)
at weblogic.i18ntools.L10nLookup$Logger.<init>(L10nLookup.java:282)
at weblogic.i18ntools.L10nLookup.<init>(L10nLookup.java:114)
at weblogic.i18ntools.L10nLookup.init(L10nLookup.java:70)
at weblogic.i18ntools.L10nLookup.getL10n(L10nLookup.java:58)
at weblogic.i18ntools.parser.LocaleLogMessage.validate(LocaleLogMessage.
java:65)
at weblogic.i18ntools.parser.LocaleMessageCatalog.validate(LocaleMessage
Catalog.java:240)
at weblogic.i18ntools.parser.LocaleCatalogParser.endDocument(LocaleCatal
ogParser.java:175)
at org.xml.sax.helpers.XMLReaderAdapter.endDocument(XMLReaderAdapter.java:286)
at weblogic.apache.xerces.parsers.SAXParser.endDocument(SAXParser.java:1
230)
at weblogic.apache.xerces.validators.common.XMLValidator.callEndDocument
(XMLValidator.java:1064)
at weblogic.apache.xerces.framework.XMLDocumentScanner$EndOfInputDispatc
her.dispatch(XMLDocumentScanner.java:1555)
at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(XMLDocu
mentScanner.java:381)
at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:967)
at org.xml.sax.helpers.XMLReaderAdapter.parse(XMLReaderAdapter.java:223)
at weblogic.i18ntools.parser.LocaleCatalogParser.parse(LocaleCatalogPars
er.java:126)
at weblogic.i18ntools.l10ngen.parseIt(l10ngen.java:327)
at weblogic.i18ntools.l10ngen.buildLangOutputs(l10ngen.java:302)
at weblogic.i18ntools.l10ngen.generate(l10ngen.java:406)
at weblogic.i18ntools.l10ngen.run(l10ngen.java:423)
at weblogic.i18ntools.l10ngen.main(l10ngen.java:459)
java.lang.NullPointerException
weblogic.i18n.tools.GenException: Code gen exception: Parse failed for:
D:\bea\w
lserver6.1_beta\samples\examples\i18n\logging\..\msgcat\fr\I18nLog.xml -
Hi,
intermittently we are seeing this exception in the server log files on weblogic 6.1
sp2, I was wondering what the cause is:
java.lang.NullPointerException
at weblogic.servlet.logging.LogManagerHttp.log(LogManagerHttp.java:292)
at weblogic.servlet.internal.HttpServer.log(HttpServer.java:835)
at weblogic.servlet.internal.ServletResponseImpl.send(ServletResponseImpl.java:1002)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2209)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Did your C:\Lighthammer\Security\userdata\IlluminatorUsers.xml or other files in this directory get corrupted somehow?
If you've rebooted the box or bounced the ServletExec-xMII service, do you see anything in the SYSTEM level messages that are forced during the initialization sequence in either the Lighthammer General log or the LHSecurity General log that would give any indications to the problem?
Regards,
Jeremy -
NullPointerException in weblogic.jdbc.rmi.SerialConnection.createStatement()
Hello,
we are running WLS 6.1 SP2. The following code sometimes (rather rarely) throws
a NullPointerException:
Connection dbConnection = DBUtil.getDBConnection();//here we get the Connection
stmt = dbConnection.createStatement(ResultSet.TYPE_FORWARD_ONLY, ResultSet.CONCUR_UPDATABLE);//it's
where NPE happens
The error report says:
java.sql.SQLException:
java.lang.NullPointerException at
weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
So, I think, this is something in WebLogic's code... Is this a known issue (I
couldn't find a similar report in the newsgroup)? Is there a workaround?
regards,
VitalyVitaly Sourikov wrote:
"Vitaly Sourikov" <[email protected]> wrote:
The patches that we use with SP2 are
CR061106_61sp2.jar
CR072612_61sp2.jar
CR077919_61sp2.jar
As far as we know, those fixes (or some of them) were not introduced in SP4. Are
there new versions of the patches for SP4?I have found that all these bugs are fixed in sp4, so no patches are needed if you
upgrade to 6.1sp4.
Joe
>
>
regards,
Vitaly
Hi Joseph,
Thank you for the reply. Unfortunately, we cannot move to SP3 or SP4
- they have
conflicts with other patches from WebLogic we use. This error happens
rather rarely.
In most of cases this very stuff works. But it would be intresing to
have this
patch for diagnostics, in case of future failures. Would you send it
to me, please?
Thank you in advance,
Vitaly
Joseph Weinstein <[email protected]> wrote:
Vitaly Sourikov wrote:
Hello,
we are running WLS 6.1 SP2. The following code sometimes (rather rarely)throws
a NullPointerException:
Connection dbConnection = DBUtil.getDBConnection();//here we get theConnection
stmt = dbConnection.createStatement(ResultSet.TYPE_FORWARD_ONLY, ResultSet.CONCUR_UPDATABLE);//it's
where NPE happens
The error report says:
java.sql.SQLException:
java.lang.NullPointerException at
weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
So, I think, this is something in WebLogic's code... Is this a knownissue (I
couldn't find a similar report in the newsgroup)? Is there a workaround?Hi. The NPE is probably happening in the actual DBMS driver. What is
happening
is that the rmi driver is having to catch any non-SQLException, andthrow
a SQLException
with the message of the original exception. Unfortunately, the fullstacktrace
of the
original NPE is lost. If you want, I can send you a small diagnostic
patch, which will
just make the rmi object retain the whole original stacktrace in the
exception it throws,
and that will help lead to the real problem.
This may well be a bug that was fixed in sp3 or 4. Is it possible
for you to upgrade to
the latest stuff?
Joe
regards,
Vitaly -
NullPointerException is weblogic xml parser
We are using weblogic server 8.1 SP4 on HP Tru64.
A NullPointerException is happening when parsing documents. I tried to find the source code however could not match the source version with the line numbers. Is this a problem in the message? Or a bug in the parser?
<?xml version="1.0" encoding="UTF-8"?>
<ns0:notificationOfApprovalResponse xmlns:ns0="http://www.auspost.com.au/elms/xml/notificationofapproval/response" elmsMailingStatementId="775507" pricingStatementNumber="0070922517">
<notificationOfApprovalStatus>
<code>S</code>
<extendedCode>233</extendedCode>
<description>ORDER_HEADER_IN has been processed successfully VBAKKOM </description>
</notificationOfApprovalStatus>
</ns0:notificationOfApprovalResponse>
java.lang.NullPointerException
at weblogic.apache.xerces.util.XMLAttributesImpl.getName(XMLAttributesImpl.java:261)
at weblogic.apache.xerces.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:428)
at weblogic.apache.xerces.impl.XMLNamespaceBinder.handleStartElement(XMLNamespaceBinder.java:877)
at weblogic.apache.xerces.impl.XMLNamespaceBinder.startElement(XMLNamespaceBinder.java:569)
at weblogic.apache.xerces.impl.dtd.XMLDTDValidator.startElement(XMLDTDValidator.java:727)
at weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement(XMLDocumentFragmentScannerImpl.java:759)
at weblogic.apache.xerces.impl.XMLDocumentScannerImpl$ContentDispatcher.scanRootElementHook(XMLDocumentScannerImpl.java:957)
at weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1544)
at weblogic.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:329)
at weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:525)
at weblogic.apache.xerces.parsers.DTDConfiguration.parse(DTDConfiguration.java:581)
at weblogic.apache.xerces.parsers.XMLParser.parse(XMLParser.java:152)
at weblogic.apache.xerces.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1175)
at weblogic.xml.jaxp.WebLogicXMLReader.parse(WebLogicXMLReader.java:135)
at weblogic.xml.jaxp.RegistryXMLReader.parse(RegistryXMLReader.java:152)
at com.bea.xbean.store.Root$SaxLoader.load(Root.java:776)
at com.bea.xbean.store.Root.loadXml(Root.java:1077)
at com.bea.xbean.store.Root.loadXml(Root.java:1069)
at com.bea.xbean.store.Root.loadXml(Root.java:1089)
at com.bea.xbean.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:241)
at au.com.auspost.elms.xml.notificationofapproval.response.NotificationOfApprovalResponseDocument$Factory.parse(Unknown Source)WLS 6.1 is not yet certifed with JDK 1.4.
Venki wrote:
Hi,
Does weblogic ships it's own XML parser.
We tried parsing an XML document using JDK1.4(default XML parser) it all worked
well, but after deploying in weblogic container, the document didn't parse correctly.
We are using Weblogic 6.1 sp2.
Our weblogic runs on JDK1.4 so the JVM is same it's only the different parser
i guess.
Any comments , help thanx !
Venki--
Rajesh Mirchandani
Developer Relations Engineer
BEA Support -
NullPointerException in WebLogic while accessing web service from client
Hi all,
I have an SPML Web Service developed. The java class from WSDL was generated using wsdlc
<wsdlc srcWsdl="schema/oracle_ws_spmlv2.wsdl" destJwsDir="${classes.dir}" type="JAXWS" explode="true"/>
and then
<jwsc classpath="..." classpathref="wls.jars" srcdir="src/main" destdir="${classes.dir}" keepGenerated="yes">
<jws file="com/oracle/xmlns/idm/identity/webservice/spmlservice/SPMLService_SPMLServiceProviderSoapImpl.java" compiledWsdl="target/oracle_ws_spmlv2_wsdl.jar" type="JAXWS">
<WLHttpTransport contextPath="OIMSPMLWebService" serviceUri="${ear.deployed.name}" portName="SPMLServiceProviderSoap"/>
</jws>
</jwsc>
I have deployed the ear in WLS and generated the client classes.
<clientgen wsdl="http://${weblogic.host}:${weblogic.port}/OIMSPMLWebService/OIMspmlxsd?WSDL" destDir="${classes.dir}" type="JAXWS"/>
I run the client using java command from the terminal. First time, it runs fine. I get a valid response. But often, when I run it a second time, I get the following exception ... I need to undeploy and deploy the ear again. Any help will be appreciated!
Following error appears.
Error 500--Internal Server Error
java.lang.NullPointerException
at weblogic.wsee.jaxws.JAXWSDeployedServlet.init(JAXWSDeployedServlet.java:49)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
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.(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:521)
at weblogic.servlet.internal.ServletStubImpl.checkForReload(ServletStubImpl.java:452)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:232)
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)As a workaround I can start the application in debug mode, log into the Weblogic console and stop then restart the deployment and this issue goes away, sort of a pain but it does work.
-
NullPointerException in weblogic.wsee.bind.internal.FormQualifiedHelper.get
WL90, trying to access a web service as a client. Stubs generated using wl clientgen ant task. On trying to create the service object, I get thrown a null pointer exception deep within weblogic. Any ideas?
[junit] java.lang.NullPointerException
[junit] at weblogic.wsee.bind.internal.FormQualifiedHelper.getPropertyForElement(FormQualifiedHelper.java:131)
[junit] at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.processExceptionMappings(Deploytime109MappingHelper.java:266)
[junit] at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.buildTylar(Deploytime109MappingHelper.java:169)
[junit] at weblogic.wsee.bind.runtime.internal.RuntimeBindingsBuilderImpl.createRuntimeBindings(RuntimeBindingsBuilderImpl.java:93)
[junit] at weblogic.wsee.ws.WsBuilder.createRuntimeBindingProvider(WsBuilder.java:271)
[junit] at weblogic.wsee.ws.WsBuilder.buildService(WsBuilder.java:171)
[junit] at weblogic.wsee.ws.WsFactory.createClientService(WsFactory.java:48)
[junit] at weblogic.wsee.jaxrpc.ServiceImpl.init(ServiceImpl.java:144)
[junit] at weblogic.wsee.jaxrpc.ServiceImpl.<init>(ServiceImpl.java:112)
[junit] at com.xxx.yyy.soap.ProWeb_Impl.<init>(ProWeb_Impl.java:17)
[junit] at com.xxx.yyy.soap.ProWeb_Impl.<init>(ProWeb_Impl.java:13)Hi all,
I'm experiencing similar issues at the moment with Weblogic 9.2 MP2.
I generated stubs from WSDLs and try to call a WebService from a standalone client application. The weird thing is though, that if the same client code is executed from within the Weblogic container, everything works fine.
I get the following exception from the standalone app:
<WS data binding error>could not find schema type [the type follows here]
java.lang.IllegalStateException: no element named null
at weblogic.wsee.bind.runtime.internal.AnonymousTypeFinder$GlobalElementNode.getSchemaType(AnonymousTypeFinder.java:239)
at weblogic.wsee.bind.runtime.internal.AnonymousTypeFinder$GlobalElementNode.getTypeNode(AnonymousTypeFinder.java:249)
at weblogic.wsee.bind.runtime.internal.AnonymousTypeFinder.findSchemaType(AnonymousTypeFinder.java:120)
at weblogic.wsee.bind.runtime.internal.AnonymousTypeFinder.getTypeNamed(AnonymousTypeFinder.java:87)
at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.createBindingTypeFrom(Deploytime109MappingHelper.java:1045)
at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.processTypeMappings(Deploytime109MappingHelper.java:476)
at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.initBindingFileFrom109dd(Deploytime109MappingHelper.java:249)
at weblogic.wsee.bind.runtime.internal.Deploytime109MappingHelper.<init>(Deploytime109MappingHelper.java:161)
at weblogic.wsee.bind.runtime.internal.RuntimeBindingsBuilderImpl.createRuntimeBindings(RuntimeBindingsBuilderImpl.java:86)
at weblogic.wsee.ws.WsBuilder.createRuntimeBindingProvider(WsBuilder.java:379)
at weblogic.wsee.ws.WsBuilder.buildService(WsBuilder.java:236)
at weblogic.wsee.ws.WsFactory.createClientService(WsFactory.java:45)
at weblogic.wsee.jaxrpc.ServiceImpl.init(ServiceImpl.java:143)
at weblogic.wsee.jaxrpc.ServiceImpl.<init>(ServiceImpl.java:111)
I suspect this might be a problem with class loader but it's just a guess.
What's worth mentioning is that the same standalone app works fine when stubs are generated and executed using Weblogic 9.1 libraries.
Anyone managed to solve the problem?
Regards,
Rob
Edited by rzaczyns at 05/19/2008 6:39 AM -
Java.lang.NullPointerException when running weblogic on linux
Hi,
I installed the generic release of the Oracle WebLogic (wls1033_generic.jar) on my server (Ubuntu 64bit). When starting the application I am getting the following java exception. Is this a bug?
<Jun 22, 2010 9:29:51 AM EDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.NullPointerException
java.lang.NullPointerException
at weblogic.deploy.internal.adminserver.DeploymentManager.getPendingDeploymentsForEditLockOwner(DeploymentManager.java:360)
at weblogic.management.provider.internal.EditAccessImpl.removePendingUpdateTasks(EditAccessImpl.java:560)
at weblogic.management.provider.internal.EditAccessImpl.undoUnsavedChanges(EditAccessImpl.java:555)
at weblogic.management.provider.internal.EditAccessImpl.acquireLock(EditAccessImpl.java:264)
at weblogic.management.provider.internal.EditAccessImpl.startEdit(EditAccessImpl.java:289)
Truncated. see log file for complete stacktrace
>
<Jun 22, 2010 9:29:51 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Jun 22, 2010 9:29:51 AM EDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Jun 22, 2010 9:29:51 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>Are you running the process as the user that installed WebLogic and have write permissions in the domain directory?
How did you create the domain? -
Weblogic throws NullPointerException when using ServiceControl.setTimeout
We are invoking a SOAP service via a com.bea.control.ServiceControl that was generated from a WSDL (right click WSDL, Generate Service Control) using Weblogic 8.1.6.
SOAP service execution is successful using an http and https endpoint. However, when setting a timeout via ServiceControl.setTimeout(int millisecods) method, the Weblogic API is throwing a NullPointerException when using an https endpoint. When using an http endpoint with the setTimeout method execution is successful.
DEBUG com.bea.wlw.runtime.jws.call.SoapHttpCall [ExecuteThread: '10' for queue: 'weblogic.kernel.Default']: opening connection to https://[... edit removed ...]
DEBUG com.bea.wlw.runtime.jws.call.SoapHttpCall [ExecuteThread: '10' for queue: 'weblogic.kernel.Default']: Response generation exception
Throwable: java.lang.NullPointerException
Stack Trace:
java.lang.NullPointerException
at weblogic.net.http.HttpsClient.openWrappedSSLSocket(HttpsClient.java:455)
at weblogic.net.http.HttpsClient.openServer(HttpsClient.java:235)
at weblogic.net.http.HttpsClient.openServer(HttpsClient.java:389)
at weblogic.net.http.HttpsClient.<init>(HttpsClient.java:209)
at weblogic.net.http.HttpClient.New(HttpClient.java:228)
at weblogic.net.http.HttpsURLConnection.getHttpClient(HttpsURLConnection.java:246)
at weblogic.net.http.HttpsURLConnection.connect(HttpsURLConnection.java:217)
at weblogic.net.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:189)
at com.bea.wlw.runtime.jws.call.SoapHttpCall.invoke(SoapHttpCall.java:179)
at com.bea.wlw.runtime.jws.call.SoapHttpCall.invoke(SoapHttpCall.java:80)
at com.bea.wlw.runtime.core.control.ServiceControlImpl.invoke(ServiceControlImpl.jcs:1288)
at com.bea.wlw.runtime.core.control.ServiceControlImpl.invoke(ServiceControlImpl.jcs:1155)
at com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:377)
at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:433)
at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:406)
at com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:388)
DEBUG com.bea.wlw.runtime.jws.call.SoapFault [ExecuteThread: '10' for queue: 'weblogic.kernel.Default']: SoapFault exception throwable e
DEBUG com.bea.wlw.runtime.jws.call.SoapHttpCall [ExecuteThread: '10' for queue: 'weblogic.kernel.Default']: response code=0, responseMsg=null
DEBUG com.bea.wlw.runtime.jws.call.SoapHttpCall [ExecuteThread: '10' for queue: 'weblogic.kernel.Default']: closed connection to https://[... edit removed ...]
WARN WLW.INVOKE.[... edit removed ...] [ExecuteThread: '10' for queue: 'weblogic.kernel.Default']: Id=[... edit removed id ...] Method=[... edit removed method ...]; Failure=com.bea.control.ServiceControlException: SERVICE FAULT:
Code:java.lang.NullPointerException
String:null
Detail:
END SERVICE FAULT
ERROR [... edit removed ...]
[ExecuteThread: '10' for queue: 'weblogic.kernel.Default']: ServiceControlException
com.bea.control.ServiceControlException: SERVICE FAULT:
Code:java.lang.NullPointerException
String:null
Detail:
END SERVICE FAULT
at com.bea.wlw.runtime.core.control.ServiceControlImpl.invoke(ServiceControlImpl.jcs:1268)
at com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:377)
at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:433)
at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:406)
at com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:388)Thanks for the suggestion. But with -DUseSunHttpHandler=true the Weblogic API is throwing a ClassCastException with or without the timeout value set.
Failure=com.bea.control.ServiceControlException: SERVICE FAULT:
Code:java.lang.ClassCastException
String:null
Detail:
END SERVICE FAULT
ERROR: ServiceControlException
com.bea.control.ServiceControlException: SERVICE FAULT:
Code:java.lang.ClassCastException
String:null
Detail:
END SERVICE FAULT
at com.bea.wlw.runtime.core.control.ServiceControlImpl.invoke(ServiceControlImpl.jcs:1268)
at com.bea.wlw.runtime.core.dispatcher.DispMethod.invoke(DispMethod.java:377)
at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:433)
at com.bea.wlw.runtime.core.container.Invocable.invoke(Invocable.java:406)
at com.bea.wlw.runtime.jcs.container.JcsProxy.invoke(JcsProxy.java:388) -
NullPointerException when validating module *.jar using WebLogic Builder
Hi,
When using WebLogic Builder to validate module ceiba.jar, it shows the following errors. How to fix it? Thanks a lot. Attachment is the deployment descriptors.
Validating module ceiba.jar
Compiling input jar D:\gzdswebproject\gzdsweb\ceiba.jar
Processing input descriptor
ERROR: Error processing input descriptor
ERROR: Error from ejbc: null
java.lang.NullPointerException at weblogic.ejb20.deployer.SessionBeanInfoImpl.assignDefaultTXAttributesIfNecessary(SessionBeanInfoImpl.java:291) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeTransactionAttribute(MBeanDeploymentInfoImpl.java:807) at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:240) at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:415) at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:397) at weblogic.ejbc20.runBody(ejbc20.java:517) at weblogic.utils.compiler.Tool.run(Tool.java:146) at weblogic.utils.compiler.Tool.run(Tool.java:103) at weblogic.marathon.tasks.EJBCTask.runBackground(EJBCTask.java:140) at weblogic.tools.jellybeans.core.task.TaskThread.execute(TaskThread.java:127) at weblogic.tools.jellybeans.core.task.TaskThread.run(TaskThread.java:64)following is the ejb-jar.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<enterprise-beans>
<session>
<display-name>Bblm</display-name>
<ejb-name>Bblm</ejb-name>
<home>com.foresee.ceiba.bbxz.BblmHome</home>
<remote>com.foresee.ceiba.bbxz.Bblm</remote>
<ejb-class>com.foresee.ceiba.bbxz.BblmBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<session>
<display-name>Bbnr</display-name>
<ejb-name>Bbnr</ejb-name>
<home>com.foresee.ceiba.bbxz.BbnrHome</home>
<remote>com.foresee.ceiba.bbxz.Bbnr</remote>
<ejb-class>com.foresee.ceiba.bbxz.BbnrBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<session>
<display-name>Fjxx</display-name>
<ejb-name>Fjxx</ejb-name>
<home>com.foresee.ceiba.comm.FjxxHome</home>
<remote>com.foresee.ceiba.comm.Fjxx</remote>
<ejb-class>com.foresee.ceiba.comm.FjxxBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<session>
<display-name>Yhzxx</display-name>
<ejb-name>Yhzxx</ejb-name>
<home>com.foresee.ceiba.comm.YhzxxHome</home>
<remote>com.foresee.ceiba.comm.Yhzxx</remote>
<ejb-class>com.foresee.ceiba.comm.YhzxxBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<session>
<display-name>GsbsProcess</display-name>
<ejb-name>GsbsProcess</ejb-name>
<home>com.foresee.ceiba.gsbs.ejb.GsbsProcessHome</home>
<remote>com.foresee.ceiba.gsbs.ejb.GsbsProcess</remote>
<ejb-class>com.foresee.ceiba.gsbs.ejb.ejb.GsbsProcessBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<session>
<display-name>BGDJ</display-name>
<ejb-name>BGDJ</ejb-name>
<home>com.foresee.ceiba.swdj.bg.BGDJHome</home>
<remote>com.foresee.ceiba.swdj.bg.BGDJ</remote>
<ejb-class>com.foresee.ceiba.swdj.bg.BGDJBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<session>
<display-name>PersonalRegister</display-name>
<ejb-name>PersonalRegister</ejb-name>
<home>com.foresee.ceiba.swdj.gr.PersonalRegisterHome</home>
<remote>com.foresee.ceiba.swdj.gr.PersonalRegister</remote>
<ejb-class>com.foresee.ceiba.swdj.gr.PersonalRegisterBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<session>
<display-name>ProjectRegister</display-name>
<ejb-name>ProjectRegister</ejb-name>
<home>com.foresee.ceiba.swdj.xm.ProjectRegisterHome</home>
<remote>com.foresee.ceiba.swdj.xm.ProjectRegister</remote>
<ejb-class>com.foresee.ceiba.swdj.xm.ProjectRegisterBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<session>
<display-name>SqjlCjwtLm</display-name>
<ejb-name>SqjlCjwtLm</ejb-name>
<home>com.foresee.ceiba.sqjl.SqjlCjwtLmHome</home>
<remote>com.foresee.ceiba.sqjl.SqjlCjwtLm</remote>
<ejb-class>com.foresee.ceiba.sqjl.SqjlCjwtLmBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<session>
<display-name>SqjlCjwtNr</display-name>
<ejb-name>SqjlCjwtNr</ejb-name>
<home>com.foresee.ceiba.sqjl.SqjlCjwtNrHome</home>
<remote>com.foresee.ceiba.sqjl.SqjlCjwtNr</remote>
<ejb-class>com.foresee.ceiba.sqjl.SqjlCjwtNrBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<session>
<display-name>Xxlm</display-name>
<ejb-name>Xxlm</ejb-name>
<home>com.foresee.ceiba.xxfb.XxlmHome</home>
<remote>com.foresee.ceiba.xxfb.Xxlm</remote>
<ejb-class>com.foresee.ceiba.xxfb.XxlmBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<session>
<display-name>Xxnr</display-name>
<ejb-name>Xxnr</ejb-name>
<home>com.foresee.ceiba.xxfb.XxnrHome</home>
<remote>com.foresee.ceiba.xxfb.Xxnr</remote>
<ejb-class>com.foresee.ceiba.xxfb.XxnrBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
<session>
<display-name>ZCDJ</display-name>
<ejb-name>ZCDJ</ejb-name>
<home>com.foresee.ceiba.swdj.zc.ZCDJHome</home>
<remote>com.foresee.ceiba.swdj.zc.ZCDJ</remote>
<ejb-class>com.foresee.ceiba.swdj.zc.ZCDJBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Container</transaction-type>
</session>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>Bblm</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>Bbnr</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>Fjxx</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>Yhzxx</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>GsbsProcess</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>BGDJ</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>PersonalRegister</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>ProjectRegister</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>SqjlCjwtLm</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>SqjlCjwtNr</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>Xxlm</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>Xxnr</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
<container-transaction>
<method>
<ejb-name>ZCDJ</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar> -
NullPointerException while starting Weblogic server instance
Hi,
I am running Weblogic 7.0 SP1 on Windows 2000 SP3. I had configured a cluster
with a single server in it. With that set up the admin server & Weblogic server
instance started up fine. Both(admin & server instance) were run on the same machine.
Then I added another server(on a different to the cluster & tried to start the
local server instance after running the admin server. I get the following exception,
C:\bea7>C:\bea7\jdk131_03\bin\java -Djava.compiler=NONE -ms64m -mx64m -classpath
""C:\SBM742\conf;C:\SBM742\ebmsapps;C:\SBM\jar\inetmssql.jar;.;C:\bea7\weblogic
700\server\lib\weblogic_sp.jar;C:\bea7\weblogic700\server\lib\weblogic.jar;C:\SB
M742\jar\tools.jar;C:\SBM742\jar\log4j.jar;C:\SBM742\BizPulse\JMSFileStore;C:\SB
M742\BizPulse\jmsmaps;C:\SBM742\jar\castor-0.9.3-xml.jar;C:\SBM742\jar\jdbc-se2.
0.jar;C:\SBM742\jar\jta1.0.1.jar;C:\SBM742\jar\jakarta-regexp-1.2.jar;C:\SBM742\
jar\xerces-J_1.4.0.jar"" -Dweblogic.Name="MILPITAS" "-Dbea.home=C:\bea7" -Dweblo
gic.management.server="milpitas.savvion.com:18793" "-Djava.security.policy==C:\b
ea7\projects\sbm4.0\sbm.policy" -Dweblogic.ProductionModeEnabled=true -Dweblogic
.management.username="system" -Dweblogic.management.password="wlsysadmin" weblog
ic.Server
Starting WebLogic Server...
Connecting to http://milpitas.savvion.com:18793...
<Apr 30, 2003 12:10:33 PM PDT> <Notice> <Security> <090093> <No configuration
da
ta was found on server MILPITAS for realm CompatibilityRealm.>
<Apr 30, 2003 12:10:33 PM PDT> <Notice> <Security> <090082> <Security initializi
ng using realm CompatibilityRealm.>
<Apr 30, 2003 12:10:33 PM PDT> <Notice> <WebLogicServer> <000328> <Starting WebL
ogic Managed Server "MILPITAS" for domain "sbm4.0">
Starting Cluster Service...
<Apr 30, 2003 12:11:08 PM PDT> <Notice> <Cluster> <000138> <Listening for announ
cements from cluster sbm_cluster on 237.0.0.1:7001>
<Apr 30, 2003 12:11:08 PM PDT> <Notice> <Cluster> <000133> <Waiting to synchroni
ze with other running members of sbm_cluster>
<Apr 30, 2003 12:11:38 PM PDT> <Notice> <Cluster> <000134> <Discovered and synch
ronized with 1 other running members of sbm_cluster>
<Apr 30, 2003 12:11:39 PM PDT> <Emergency> <WebLogicServer> <000342> <Unable to
initialize the server: Fatal initialization exception
Throwable: java.lang.NullPointerException
java.lang.NullPointerException
at weblogic.transaction.internal.TransactionRecoveryService.getOrCreate(
TransactionRecoveryService.java:345)
at weblogic.transaction.internal.TransactionRecoveryService.deployAllTra
nsactionRecoveryServices(TransactionRecoveryService.java:390)
at weblogic.transaction.internal.TransactionRecoveryService.resume(Trans
actionRecoveryService.java:160)
at weblogic.transaction.internal.TransactionService.resume(TransactionSe
rvice.java:138)
at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:
61)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:806)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:295)
at weblogic.Server.main(Server.java:32)
>
The WebLogic Server did not start up properly.
Exception raised:
java.lang.NullPointerException
at weblogic.transaction.internal.TransactionRecoveryService.getOrCreate(
TransactionRecoveryService.java:345)
at weblogic.transaction.internal.TransactionRecoveryService.deployAllTra
nsactionRecoveryServices(TransactionRecoveryService.java:390)
at weblogic.transaction.internal.TransactionRecoveryService.resume(Trans
actionRecoveryService.java:160)
at weblogic.transaction.internal.TransactionService.resume(TransactionSe
rvice.java:138)
at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:
61)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:806)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:295)
at weblogic.Server.main(Server.java:32)
Reason: Fatal initialization exception
Throwable: java.lang.NullPointerException
java.lang.NullPointerException
at weblogic.transaction.internal.TransactionRecoveryService.getOrCreate(
TransactionRecoveryService.java:345)
at weblogic.transaction.internal.TransactionRecoveryService.deployAllTra
nsactionRecoveryServices(TransactionRecoveryService.java:390)
at weblogic.transaction.internal.TransactionRecoveryService.resume(Trans
actionRecoveryService.java:160)
at weblogic.transaction.internal.TransactionService.resume(TransactionSe
rvice.java:138)
at weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:
61)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:806)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:295)
at weblogic.Server.main(Server.java:32)
The local server instance doesn't start because of this. The other server added
to the cluster was to run on a different machine & was not started yet. If I remove
the other server the server instance starts up fine. I am attaching the config.xml(the
working version, without the second server).
This used to work in Weblogic 6.1.
Thanks,
Aejaz
[config.xml]
This is fixed in SP2.
Sree Bodapati wrote:
> This is probably fixed already please contact support@bea<DOT>com.
>
> /
> sree
>
> "Aejaz" <[email protected]> wrote in message
> news:[email protected]...
> >
> > Hi,
> >
> > I am running Weblogic 7.0 SP1 on Windows 2000 SP3. I had configured a
> cluster
> > with a single server in it. With that set up the admin server & Weblogic
> server
> > instance started up fine. Both(admin & server instance) were run on the
> same machine.
> > Then I added another server(on a different to the cluster & tried to start
> the
> > local server instance after running the admin server. I get the following
> exception,
> >
> >
> C:\bea7>C:\bea7\jdk131_03\bin\java -Djava.compiler=NONE -ms64m -mx64m -class
> path
> >
> ""C:\SBM742\conf;C:\SBM742\ebmsapps;C:\SBM\jar\inetmssql.jar;.;C:\bea7\weblo
> gic
> >
> 700\server\lib\weblogic_sp.jar;C:\bea7\weblogic700\server\lib\weblogic.jar;C
> :\SB
> >
> M742\jar\tools.jar;C:\SBM742\jar\log4j.jar;C:\SBM742\BizPulse\JMSFileStore;C
> :\SB
> >
> M742\BizPulse\jmsmaps;C:\SBM742\jar\castor-0.9.3-xml.jar;C:\SBM742\jar\jdbc-
> se2.
> >
> 0.jar;C:\SBM742\jar\jta1.0.1.jar;C:\SBM742\jar\jakarta-regexp-1.2.jar;C:\SBM
> 742\
> > jar\xerces-J_1.4.0.jar"" -Dweblogic.Name="MILPITAS"
> "-Dbea.home=C:\bea7" -Dweblo
> > gic.management.server="milpitas.savvion.com:18793"
> "-Djava.security.policy==C:\b
> >
> ea7\projects\sbm4.0\sbm.policy" -Dweblogic.ProductionModeEnabled=true -Dwebl
> ogic
> > management.username="system" -Dweblogic.management.password="wlsysadmin"
> weblog
> > ic.Server
> > Starting WebLogic Server...
> > Connecting to http://milpitas.savvion.com:18793...
> > <Apr 30, 2003 12:10:33 PM PDT> <Notice> <Security> <090093> <No
> configuration
> > da
> > ta was found on server MILPITAS for realm CompatibilityRealm.>
> > <Apr 30, 2003 12:10:33 PM PDT> <Notice> <Security> <090082> <Security
> initializi
> > ng using realm CompatibilityRealm.>
> > <Apr 30, 2003 12:10:33 PM PDT> <Notice> <WebLogicServer> <000328>
> <Starting WebL
> > ogic Managed Server "MILPITAS" for domain "sbm4.0">
> > Starting Cluster Service...
> > <Apr 30, 2003 12:11:08 PM PDT> <Notice> <Cluster> <000138> <Listening for
> announ
> > cements from cluster sbm_cluster on 237.0.0.1:7001>
> > <Apr 30, 2003 12:11:08 PM PDT> <Notice> <Cluster> <000133> <Waiting to
> synchroni
> > ze with other running members of sbm_cluster>
> > <Apr 30, 2003 12:11:38 PM PDT> <Notice> <Cluster> <000134> <Discovered and
> synch
> > ronized with 1 other running members of sbm_cluster>
> > <Apr 30, 2003 12:11:39 PM PDT> <Emergency> <WebLogicServer> <000342>
> <Unable to
> > initialize the server: Fatal initialization exception
> > Throwable: java.lang.NullPointerException
> > java.lang.NullPointerException
> > at
> weblogic.transaction.internal.TransactionRecoveryService.getOrCreate(
> > TransactionRecoveryService.java:345)
> > at
> weblogic.transaction.internal.TransactionRecoveryService.deployAllTra
> > nsactionRecoveryServices(TransactionRecoveryService.java:390)
> > at
> weblogic.transaction.internal.TransactionRecoveryService.resume(Trans
> > actionRecoveryService.java:160)
> > at
> weblogic.transaction.internal.TransactionService.resume(TransactionSe
> > rvice.java:138)
> > at
> weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:
> > 61)
> > at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:806)
> > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:295)
> > at weblogic.Server.main(Server.java:32)
> > >
> >
> ***************************************************************************
> > The WebLogic Server did not start up properly.
> > Exception raised:
> > java.lang.NullPointerException
> > at
> weblogic.transaction.internal.TransactionRecoveryService.getOrCreate(
> > TransactionRecoveryService.java:345)
> > at
> weblogic.transaction.internal.TransactionRecoveryService.deployAllTra
> > nsactionRecoveryServices(TransactionRecoveryService.java:390)
> > at
> weblogic.transaction.internal.TransactionRecoveryService.resume(Trans
> > actionRecoveryService.java:160)
> > at
> weblogic.transaction.internal.TransactionService.resume(TransactionSe
> > rvice.java:138)
> > at
> weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:
> > 61)
> > at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:806)
> > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:295)
> > at weblogic.Server.main(Server.java:32)
> > Reason: Fatal initialization exception
> > Throwable: java.lang.NullPointerException
> > java.lang.NullPointerException
> > at
> weblogic.transaction.internal.TransactionRecoveryService.getOrCreate(
> > TransactionRecoveryService.java:345)
> > at
> weblogic.transaction.internal.TransactionRecoveryService.deployAllTra
> > nsactionRecoveryServices(TransactionRecoveryService.java:390)
> > at
> weblogic.transaction.internal.TransactionRecoveryService.resume(Trans
> > actionRecoveryService.java:160)
> > at
> weblogic.transaction.internal.TransactionService.resume(TransactionSe
> > rvice.java:138)
> > at
> weblogic.t3.srvr.ServerLifeCycleList.resume(ServerLifeCycleList.java:
> > 61)
> > at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:806)
> > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:295)
> > at weblogic.Server.main(Server.java:32)
> >
> >
> ***************************************************************************
> >
> > The local server instance doesn't start because of this. The other server
> added
> > to the cluster was to run on a different machine & was not started yet. If
> I remove
> > the other server the server instance starts up fine. I am attaching the
> config.xml(the
> > working version, without the second server).
> >
> > This used to work in Weblogic 6.1.
> >
> > Thanks,
> > Aejaz
Rajesh Mirchandani
Developer Relations Engineer
BEA Support
-
Error in deploying the war file on to the weblogic server(6.1)
Hi,
I created the war file and tried to deploy it on the weblogic server 6.1 it is unable to deploy and is give these errors i am unable to find out the problem.Can any one help me out in finding why this is so.
Help will be appreciated
java.lang.NullPointerException
at weblogic.management.internal.MBeanProxy.getAttribute(MBeanProxy.java:253)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:187)
at $Proxy65.isDeployed(Unknown Source)
at weblogic.management.mbeans.custom.ApplicationManager.poll(ApplicationManager.java:744)
at weblogic.management.mbeans.custom.ApplicationManager.update(ApplicationManager.java:206)
at java.lang.reflect.Method.invoke(Native Method)
at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:636)
at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:621)
at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:359)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:468)
at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:209)
at $Proxy5.update(Unknown Source)
at weblogic.management.console.webapp._domain.__upload_app._jspService(__upload_app.java:149)
at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:241)
at weblogic.servlet.jsp.PageContextImpl.forward(PageContextImpl.java:112)
at weblogic.management.console.actions.ForwardAction.perform(ForwardAction.java:35)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:171)
at weblogic.management.console.actions.internal.ActionServlet.doPost(ActionServlet.java:85)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2495)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2204)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Thanks,
RejiHi jmendelak,
In the warfile i have jsp,servlets,java classes.
In my working directory i have jsp and html files and in web-inf folder i have a folder by name classes in which i have the servlets and java classes.
I made the war file and when i tried to deploy i was getting this error.
I had previously deployed this war file on weblogic6.1 it was working fine.
I have upgraded my operating sytem to Windows2000 professional from WinNT 4.0.I reinstalled the weblogic again and had set up the environment variables.
After going through the error could you find out the reason?Is it because some seeting is missing?
Raji -
How to deal with security when migrating application from weblogic 5.1 to weblogic 6.1?
Dear All,
I have one statement int weblogic 5.1 weblogic.propertis as follow,
weblogic.security.realmClass=com.tbcn.security.realm.TestRealm
but after converting to weblogic 6.1 there are no corresponding statement in
the file config.xml. And when i start the new application, error occured.
what should I do?
The error message is:
<2001/8/27 am 11:33:42> <Notice> <Management> <Loading configuration file
.\config\tbcn\config.xml
<2001/8/27 am 11:33:49> <Emergency> <Server> <Unable to initialize the
server: 'Fatal initializatio
Throwable: java.lang.NullPointerException
java.lang.NullPointerException
at
weblogic.security.SecurityService.initializeRealm(SecurityService.java:261)
at
weblogic.security.SecurityService.initialize(SecurityService.java:115)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:385)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised: java.lang.NullPointerException
java.lang.NullPointerException
at
weblogic.security.SecurityService.initializeRealm(SecurityService.java:261)
at
weblogic.security.SecurityService.initialize(SecurityService.java:115)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:385)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exceptionDear Satya,
My weblogic propertis file as follow,
# CORE PROPERTIES
# You should set these before you start the WebLogic Server the first time.
# If you need more instructions on individual properties in this
# section, check the same section in the Optional Properties, where
# we've left the long explanations. Or, better yet, go to our
# website and read all about properties, at:
# http://www.weblogic.com/docs51/admindocs/properties.html
# CORE SYSTEM PROPERTIES
# TCP/IP port number at which the WebLogic Server listens for connections
weblogic.system.listenPort=7001
# CORE SECURITY-RELATED PROPERTIES
# Read important information about security at:
# http://www.weblogic.com/docs51/admindocs/properties.html
# REQUIRED: The system password MUST be set in order to start the
# WebLogic Server. This password is case-sensitive, at least 8 characters.
# The username for the privileged user is ALWAYS "system".
# This username and password also includes httpd access (see
# HTTPD properties below).
weblogic.password.system=12345678
# RECOMMEND Set to 'everyone' if HTTPD is enabled
weblogic.allow.execute.weblogic.servlet=everyone
# Set individual ACLs to restrict access to HTTP-related resources,
# such as the Administration servlets.
# To make your own servlets generally available, follow this
# pattern (provide a weblogic.allow.execute) for your packages and
# set ACLs as appropriate.
# CORE SECURITY-RELATED PROPERTIES FOR SSL
# Read important information about SSL at:
# http://www.weblogic.com/docs51/classdocs/API_secure.html
# Enable SSL
# (default if property not defined is false)
weblogic.security.ssl.enable=true
# SSL listen port
weblogic.system.SSLListenPort=7002
# Servlets for SSL
# Authentication servlet for creating tokens for applets
weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationS
ervlet
# Limits number of unclaimed stored tokens
weblogic.security.certificateCacheSize=3
# Capture CA root of client servlet
weblogic.httpd.register.AdminCaptureRootCA=admin.AdminCaptureRootCA
# Certificates for SSL
# Name of acceptable CA roots
# For client authentication change value to a valid .pem file
#weblogic.security.clientRootCA=SecureServerCA.pem
# Server certificates for SSL
weblogic.security.certificate.server=democert.pem
weblogic.security.key.server=demokey.pem
weblogic.security.certificate.authority=ca.pem
# registration for certificate generator servlet
weblogic.httpd.register.Certificate=utils.certificate
weblogic.allow.execute.weblogic.servlet.Certificate=system
# CORE HTTPD ADMINISTRATIVE PROPERTIES
# True permits the HTTPD to run (default)
# Uncomment this property to disable HTTPD
#weblogic.httpd.enable=false
# If authentication is required, add username/password for each user
# who will be included in an ACL, as in this commented-out example:
#weblogic.password.peter=#8gjsL4*
# SYSTEM PROPERTIES
# System properties in this section are set to system defaults
# Performance pack. The shared library must be accessible from your
# PATH (NT) or from your shared library path (UNIX; the name of the
# variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
weblogic.system.nativeIO.enable=true
# Outputs logging information to the console as well as to the log file
weblogic.system.enableConsole=true
# Sets the directory or URL for the WebLogic Admin help pages
# The help pages are shipped in the "docs/adminhelp" directory, in the
# default document root in public_html
weblogic.system.helpPageURL=/weblogic/myserver/public_html/docs51/adminhelp/
# If you prefer to access the most recent help pages, you can do so online
# by commenting out the previous property and uncommenting this one:
#weblogic.system.helpPageURL=http://www.weblogic.com/docs51/adminhelp/
# Properties for tuning the server's performance
# Number of WebLogic Server execute threads.
weblogic.system.executeThreadCount=15
# Other optional system properties
# Limits size of weblogic.log (in K) and versions old log
weblogic.system.maxLogFileSize=1024
# Adjust minimum length of password
weblogic.system.minPasswordLen=8
# UNIX only: If running on port 80 on UNIX, enable the setUID program
#weblogic.system.enableSetUID=false
# UNIX only: Unprivileged user to setUID to after starting up
# WebLogic Server on port 80
#weblogic.system.nonPrivUser=nobody
# CLUSTER-SPECIFIC PROPERTIES
# Cluster-specific properties in this section are set to system defaults.
# CLUSTER USERS: Note that ALL Cluster-specific properties should be set
# in the per-cluster properties file ONLY.
# Time-to-live (number of hops) for the cluster's multicast messages
# (default 1, range 1-255).
#weblogic.cluster.multicastTTL=1
# Sets the load-balancing algorithm to be used between
# replicated services if none is specified. If not specified,
# round-robin is used.
#weblogic.cluster.defaultLoadAlgorithm=round-robin
# SERVER-SPECIFIC CLUSTER PROPERTIES
# Cluster-related properties in this section are set to system defaults.
# CLUSTER USERS: Note that these server-specific cluster-related properties
# should be set in the per-server properties file ONLY.
# Sets the weight of the individual server for the weight-based
load-balancing.
# Range is 0 - 100.
# Larger numbers increase the amount of traffic routed to this server.
#weblogic.system.weight=100
# SYSTEM STARTUP FILES - Examples
# CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
# objects should be registered in the per-server properties file.
# All other startup classes should be registered in the per-cluster
# properties file.
# For more info on writing and using startup file, see the
# Developers Guide "Writing a WebLogic Client application," at
# http://www.weblogic.com/docs51/classdocs/API_t3.html
# Register a startup class by giving it a virtual name and
# supplying its full pathname.
#weblogic.system.startupClass.[virtual_name]=[full_pathname]
# Add arguments for the startup class
#weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
# This example shows the entry for examples/t3client/StartupQuery.java
#weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
#weblogic.system.startupArgs.doquery=\
# query=select * from emp,\
# db=jdbc:weblogic:pool:demoPool
# SYSTEM SHUTDOWN FILES - Examples
# For more info on writing and using shutdown file, see the
# Developers Guide "Writing a WebLogic Client application," at
# http://www.weblogic.com/docs51/classdocs/API_t3.html
# Register a shutdown class by giving it a virtual name and
# supplying its full pathname.
#weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
# Add arguments for the shutdown class
#weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
# This example shows the entry for examples/t3client/ShutdownTest.java
#weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
#weblogic.system.shutdownArgs.ShutdownTest=\
# outfile=c:/temp/shutdown.log
# SECURITY-RELATED PROPERTIES FOR WORKSPACES
# For backward compatibility, the following entries disable Access
# Control on Workspaces
weblogic.allow.read.weblogic.workspace=everyone
weblogic.allow.write.weblogic.workspace=everyone
# JOLT FOR WEBLOGIC PROPERTIES
# These properties configure a BEA Jolt connection pool for use with
# the simpapp and bankapp examples, and register a servlet for use with
# with the simpapp example. The default server address provided here
# points to a public TUXEDO server that is hosted by BEA for use with
# this example.
# Servlet registration for simpapp example:
#weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServle
t
# Pool creation and cleanup
# note this example is set up to work with the public
# demo TUXEDO server available from BEA's website:
#weblogic.system.startupClass.demojoltpoolStart=\
# bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
#weblogic.system.startupArgs.demojoltpoolStart=\
# poolname=demojoltpool,\
# appaddrlist=//beademo1.beasys.com:8000,\
# failoverlist=//beademo1.beasys.com:8000,\
# minpoolsize=1,\
# maxpoolsize=3
#weblogic.system.shutdownClass.demojoltpoolStop=\
# bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
#weblogic.system.shutdownArgs.demojoltpoolStop=\
# poolname=demojoltpool
# WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
# The registrations enable a BEA IIOP connection pool and
# register servlets for use with the simpapp and university examples.
# Configure for your environment and uncomment to use.
# Uncommenting these properties requires WebLogic Enterprise Connectivity
# and an operating WebLogic Enterprise Server.
# Servlet registration for simpapp servlet example
#weblogic.httpd.register.SimpappServlet=\
# examples.wlec.servlets.simpapp.SimpappServlet
#weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
# Servlet registration for simpapp EJB example
# (You'll need to add the wlec_ejb_simpapp.jar to the
# weblogic.ejb.deploy property in this file.)
#weblogic.httpd.register.ejbSimpappServlet=\
# examples.wlec.ejb.simpapp.ejbSimpappServlet
#weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
# Pool creation and cleanup for the simpapp example
#weblogic.CORBA.connectionPool.simplepool=\
# appaddrlist=//wlehost:2468,\
# failoverlist=//wlehost:2468,\
# minpoolsize=2,\
# maxpoolsize=3,\
# username=wleuser,\
# userrole=developer,\
# domainname=simpapp
# Servlet registration for university Servlet example:
#weblogic.httpd.register.UniversityServlet=\
# examples.wlec.servlets.university.UniversityServlet
#weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
# Pool creation and cleanup for the University example:
#weblogic.CORBA.connectionPool.Univpool=\
# appaddrlist=//wlehost:2498,\
# failoverlist=//wlehost:2498,\
# minpoolsize=2,\
# maxpoolsize=3,\
# username=wleuser,\
# userrole=developer,\
# apppassword=wlepassword,\
# domainname=university
# WEBLOGIC FILE PROPERTIES
# Maps a volume name to a path, for client file read/write
#weblogic.io.fileSystem.[volumeName]=[fullPathName]
# WEBLOGIC JMS DEMO PROPERTIES
# CLUSTER USERS: Note that ALL JMS deployment should be done in the
# per-cluster properties file ONLY.
# You set up a JDBC connection pool if you want persistent messages
# (including durable subscriptions). To use JMS and EJBs in the same
# transaction, both must use the same JDBC connection pool. Uncomment
# the following property to use the default JDBC connection pool
# 'demo', which is defined in the Demo connection pool section of this file.
#weblogic.jms.connectionPool=demoPool
# The JMS Webshare example demonstrates how the ClientID for a
# durable subscriber is configured in the connection factory:
#weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
#weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
#weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
#weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
# The JMS trader example shows how to use JMS with an EJB. In addition
# to uncommenting the following properties, you must also set up and
# deploy the EJB example examples.ejb.basic.statelessSession.Trader in
# ejb_basic_statelessSession.jar to try out this JMS example:
#weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
#weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
#weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
#weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
# Registers the underlying servlet
#weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
# These properties are used with the ServerReceive JMS example,
# which demonstrates how to establish a JMS message consumer
# in a startup class:
#weblogic.system.startupClass.serverReceive=\
# examples.jms.startup.ServerReceive
#weblogic.system.startupArgs.serverReceive=\
# connectionFactory=javax.jms.TopicConnectionFactory,\
# topic=javax.jms.exampleTopic
# These properties are used with the PoolReceive JMS example,
# which demonstrates how to establish a pool of JMS message consumers
# in a startup class:
#weblogic.system.startupClass.poolReceive=\
# examples.jms.startup.PoolReceive
#weblogic.system.startupArgs.poolReceive=\
# connectionFactory=javax.jms.TopicConnectionFactory,\
# topic=javax.jms.exampleTopic
#weblogic.allow.create.weblogic.jms.ServerSessionPool=everyone
# WEBLOGIC RMI DEMO PROPERTIES
# CLUSTER USERS: Note that pinned RMI objects should be registered
# in the per-server properties file ONLY. All other RMI startup
# classes should be registered in the per-cluster properties file.
# Remote classes registered at startup after the pattern:
#weblogic.system.startupClass.[virtualName]=[fullPackageName]
# These examples can be compiled to see RMI in action. Uncomment to use:
#weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
#weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
#weblogic.system.startupClass.stock=examples.rmi.stock.StockServer
# WEBLOGIC EJB DEMO PROPERTIES
# CLUSTER USERS: Note that ALL EJB deployment should be done in the
# per-cluster properties file ONLY.
# See WebLogic Demo Connection Pool below for a connection pool
# to use with these examples.
# Deploys EJBeans. Uncomment the appropriate lines below and
# modify DBMS-related info and paths to match your particular installation:
# TBCN EJB PROPERTIES
weblogic.ejb.deploy=\
C:/weblogic/myserver/AccountSB.jar, \
C:/weblogic/myserver/AddressEntryDet.jar, \
C:/weblogic/myserver/AddressEntry.jar, \
C:/weblogic/myserver/Affiliate.jar, \
C:/weblogic/myserver/ContactPerson.jar, \
C:/weblogic/myserver/ContactSB.jar, \
C:/weblogic/myserver/Factory.jar, \
C:/weblogic/myserver/FactorySups.jar, \
c:/weblogic/myserver/LoginUsers.jar, \
c:/weblogic/myserver/Member.jar, \
c:/weblogic/myserver/MemberQuotaUsage.jar,\
c:/weblogic/myserver/MemberToCategory.jar,\
c:/weblogic/myserver/Organization.jar, \
c:/weblogic/myserver/Person.jar, \
c:/weblogic/myserver/QuotaType.jar,\
c:/weblogic/myserver/Registration.jar, \
c:/weblogic/myserver/TempAccounts.jar, \
c:/weblogic/myserver/TempDomain.jar, \
c:/weblogic/myserver/UserAccount.jar, \
c:/weblogic/myserver/UserRole.jar, \
c:/weblogic/myserver/BuyerProducts.jar, \
c:/weblogic/myserver/Catalog.jar, \
c:/weblogic/myserver/Categories.jar, \
c:/weblogic/myserver/CategoryToCategory.jar, \
c:/weblogic/myserver/CountryToCategory.jar, \
c:/weblogic/myserver/InvitedMember.jar, \
c:/weblogic/myserver/ProductOrigin.jar, \
c:/weblogic/myserver/ProductOtherFee.jar,\
c:/weblogic/myserver/ProductSups.jar, \
c:/weblogic/myserver/Products.jar,\
c:/weblogic/myserver/ProductToCategory.jar, \
c:/weblogic/myserver/SecondaryQcEntry.jar, \
c:/weblogic/myserver/CodeClass.jar,\
c:/weblogic/myserver/ConfirmationSB.jar, \
c:/weblogic/myserver/PurchasedPackage.jar,\
c:/weblogic/myserver/RejectReasonCode.jar, \
c:/weblogic/myserver/ServiceOrder.jar,\
c:/weblogic/myserver/ServiceOrderLog.jar,\
c:/weblogic/myserver/ServiceOrderState.jar,\
c:/weblogic/myserver/ServiceOrderType.jar,\
c:/weblogic/myserver/ServicePackageDetails.jar, \
c:/weblogic/myserver/ServicePackage.jar, \
c:/weblogic/myserver/ServicePayment.jar, \
c:/weblogic/myserver/ServiceReqSB.jar, \
c:/weblogic/myserver/TAM.jar, \
c:/weblogic/myserver/SubscriptionEB.jar, \
c:/weblogic/myserver/PostingCategoryEB.jar, \
c:/weblogic/myserver/PostingBrowsedEB.jar, \
c:/weblogic/myserver/PostingInfoEB.jar, \
c:/weblogic/myserver/TransactionLogEB.jar, \
c:/weblogic/myserver/PostingSB.jar
#weblogic.ejb.deploy=\
# d:/weblogic/myserver/ejb_basic_beanManaged.jar, \
# d:/weblogic/myserver/ejb_basic_containerManaged.jar, \
# d:/weblogic/myserver/ejb_basic_statefulSession.jar, \
# d:/weblogic/myserver/ejb_basic_statelessSession.jar, \
# d:/weblogic/myserver/ejb_extensions_finderEnumeration.jar, \
# d:/weblogic/myserver/ejb_extensions_readMostly.jar, \
# d:/weblogic/myserver/ejb_subclass.jar, \
# d:/weblogic/myserver/jolt_ejb_bankapp.jar
# Servlet used by the EJB basic beanManaged example
# Uncomment to use:
weblogic.httpd.register.beanManaged=\
examples.ejb.basic.beanManaged.Servlet
# Add a list of users (set the password with
weblogic.password.[username]=XXX)
# to set an ACL for this servlet:
#weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
#weblogic.password.user1=user1Password
#weblogic.password.user2=user2Password
# WEBLOGIC XML DEMO PROPERTIES
# These properties are required to run the XML examples.
# Uncomment to use.
# CLUSTER USERS: Note that ALL servlets should be set up
# in the per-cluster properties file ONLY.
#weblogic.httpd.register.StockServlet=examples.xml.http.StockServlet
# BizTalk example properties
#weblogic.jms.queue.tradeIncoming=biztalk.jms.tradeIncoming
#weblogic.jms.queue.tradeError=biztalk.jms.tradeError
#weblogic.httpd.register.BizTalkServer=examples.xml.biztalk.BizHttpProtocolA
dapter
#weblogic.httpd.initArgs.BizTalkServer=bizQueue=biztalk.jms.tradeIncoming
# WEBLOGIC ZAC DEMO PROPERTIES
# These registrations enable the ZAC Publish Wizard.
weblogic.zac.enable=true
# Set the publish root for a WebLogic Server. Edit and
# uncomment to use.
#weblogic.zac.publishRoot=d:/weblogic/zac
# Set an ACL for each package you publish. The [name] is
# the "Package name" you assign in the ZAC Publish Wizard.
# Publish a package, edit this property, and uncomment to use.
#weblogic.allow.read.weblogic.zac.[name]=[user list]
#weblogic.allow.write.weblogic.zac.[name]=system
# HTTPD ADMINISTRATIVE PROPERTIES
# Enables logging of HTTPD info in common log format and
# sets the log file name (default is "access.log" in "myserver")
weblogic.httpd.enableLogFile=true
weblogic.httpd.logFileName=access.log
# Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
weblogic.httpd.enableEvents=false
# Enables HTTP sessions
weblogic.httpd.session.enable=true
# Sets an optional cookie name. The default name is "WebLogicSession".
# Prior to version 4.0, the default was "TengahSession". To make
# this backward compatible with cookies generated from previous
# installations, you should set this property to "TengahSession".
# Uncomment this line and set this to any string of your choice,
# or comment out this property to use the default.
#weblogic.httpd.session.cookie.name=WebLogicSession
# MIME types
weblogic.httpd.mimeType.text/html=html,htm
weblogic.httpd.mimeType.image/gif=gif
weblogic.httpd.mimeType.image/jpeg=jpeg,jpg
weblogic.httpd.mimeType.application/pdf=pdf
weblogic.httpd.mimeType.application/zip=zip
weblogic.httpd.mimeType.application/x-java-vm=class
weblogic.httpd.mimeType.application/x-java-archive=jar
weblogic.httpd.mimeType.application/x-java-serialized-object=ser
weblogic.httpd.mimeType.application/octet-stream=exe
weblogic.httpd.mimeType.text/vnd.wap.wml=wml
weblogic.httpd.mimeType.text/vnd.wap.wmlscript=wmls
weblogic.httpd.mimeType.application/vnd.wap.wmlc=wmlc
weblogic.httpd.mimeType.application/vnd.wap.wmlscriptc=wmlsc
weblogic.httpd.mimeType.image/vnd.wap.wbmp=wbmp
# In seconds, the keep-alive for HTTP and HTTPS requests
weblogic.httpd.http.keepAliveSecs=60
weblogic.httpd.https.keepAliveSecs=120
# WEBLOGIC JDBC DRIVER PROPERTIES
# Enables JDBC driver logging and sets the file name for the log
# The weblogic.jdbc.logFile is placed in the per-server
# directory (default is "myserver")
weblogic.jdbc.enableLogFile=false
weblogic.jdbc.logFileName=jdbc.log
# WEBLOGIC JDBC CONNECTION POOL MANAGEMENT
# CLUSTER USERS: Note that ALL JDBC connection pools should be set up
# in the per-cluster properties file ONLY.
# For creating JDBC connection pools. This example shows a connection
# pool called "oraclePool" that allows 3 T3Users "guest," "joe," and "jill"
# to use 4 JDBC connections (with a potential for up to 10 connections,
# incremented by two at a time, with a delay of 1 second between each
# attempt to connect to the database), to an Oracle database server called
# "DEMO." If more than 4 connections are opened, after 15 minutes, unused
# connections are dropped from the pool until only 4 connections remain
open.
# Every 10 minutes, any unused connections in the pool are tested and
# refreshed if they are not viable.
#weblogic.jdbc.connectionPool.oraclePool=\
# url=jdbc:weblogic:oracle,\
# driver=weblogic.jdbc.oci.Driver,\
# loginDelaySecs=1,\
# initialCapacity=4,\
# maxCapacity=10,\
# capacityIncrement=2,\
# allowShrinking=true,\
# shrinkPeriodMins=15,\
# refreshMinutes=10,\
# testTable=dual,\
# props=user=SCOTT;password=tiger;server=DEMO
# Get more details on each argument for this property in the
# Administrators Guide on setting properties at:
# http://www.weblogic.com/docs51/admindocs/properties.html
# Set up ACLs for this connection pool with the following:
weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=everyone
# guest,joe,jill
#weblogic.allow.reset.weblogic.jdbc.connectionPool.oraclePool=\
# joe,jill
#weblogic.allow.shrink.weblogic.jdbc.connectionPool.oraclePool=\
# joe,jill
# This property is an ACL that specifies the users who can
# create dynamic connection pools:
#weblogic.jdbc.connectionPoolcreate.admin=joe,jill
# Read more about setting up and using connection pools in the
# developers guide for WebLogic JDBC at:
# http://www.weblogic.com/docs51/classdocs/API_jdbct3.html#T5a
# TBCN JDBC CONNECTION POOL MANAGEMENT
weblogic.jdbc.connectionPool.oraclePool=\
url=jdbc:oracle:thin:@202.109.102.151:1521:tbcn,\
driver=oracle.jdbc.driver.OracleDriver,\
loginDelaySecs=1,\
initialCapacity=2,\
maxCapacity=10,\
capacityIncrement=2,\
allowShrinking=true,\
shrinkPeriodMins=15,\
refreshMinutes=10,\
testTable=dual,\
props=user=tbcn;password=ca91768
weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=everyone
weblogic.jdbc.TXDataSource.oracleDataSource=oraclePool
weblogic.jdbc.DataSource.oracleReadOnlyDataSource=oraclePool
# WEBLOGIC DEMO CONNECTION POOL PROPERTIES
# CLUSTER USERS: Note that ALL JDBC connection pools should be set up
# in the per-cluster properties file ONLY.
# This connection pool uses the sample Cloudscape database shipped
# with WebLogic. Used by the EJBean, JHTML, JSP and JMS examples.
# Uncomment to use:
#weblogic.jdbc.connectionPool.demoPool=\
# url=jdbc:cloudscape:demo,\
# driver=COM.cloudscape.core.JDBCDriver,\
# initialCapacity=1,\
# maxCapacity=2,\
# capacityIncrement=1,\
# props=user=none;password=none;server=none
# Add a TXDataSource for the connection pool:
#weblogic.jdbc.TXDataSource.weblogic.jdbc.jts.demoPool=demoPool
# Add an ACL for the connection pool:
#weblogic.allow.reserve.weblogic.jdbc.connectionPool.demoPool=everyone
# WEBLOGIC HTTP SERVLET PROPERTIES
# CLUSTER USERS: Note that ALL servlets should be set up
# in the per-cluster properties file ONLY.
# WebLogic offers different types of servlets for various uses.
# Classpath servlet registration
# The ClasspathServlet is used to serve classes from
# the system CLASSPATH. It is used by applets to load
# classes they depend upon, and is registered against
# the virtual name 'classes' here by default. This means
# you should set your applet codebase to "/classes".
# You can register multiple virtual names for this servlet.
# Note that it can also be used to serve other
# resources/files from the system CLASSPATH.
# Don't confuse the ClasspathServlet with the ServletServlet. The
# ClasspathServlet is used for serving classes for client-side Java only.
# The ServletServlet is used to invoke unregistered servlets.
# See the Administrators Guide "Setting up WebLogic as an HTTP server"
# http://www.weblogic.com/docs51/admindocs/http.html#classfile for more
info.
weblogic.httpd.register.classes=weblogic.servlet.ClasspathServlet
# We also set an open ACL for everyone to call the ClasspathServlet
# so that applets work without requiring further changes.
weblogic.allow.execute.weblogic.servlet.classes=everyone
# File servlet registration
# FileServlet searches below the documentRoot for the requested file
# and serves it if found. If the requested file is a directory,
# FileServlet will append the defaultFilename to the requested path
# and serve that file if found.
weblogic.httpd.register.file=weblogic.servlet.FileServlet
weblogic.httpd.initArgs.file=defaultFilename=index.html
weblogic.httpd.indexFiles=zh_TW/index.htm
# ServerSideInclude servlet registration
# SSIServlet searches below the documentRoot for the
# requested .shtml file and serves it if found.
weblogic.httpd.register.*.shtml=weblogic.servlet.ServerSideIncludeServlet
# Example URL: http://localhost:7001/portside/welcome.shtml
# for the file /weblogic/myserver/public_html/portside/welcome.shtml
# PageCompileServlet (used by JHTML)
# See the information below under WebLogic JHTML
# JSPServlet (used by JSP)
# See the information below under WebLogic JSP
# ServletServlet registration
# Allows unregistered servlets in the servlet classpath (see Servlet
# reload properties below) to be r -
Error while parsing JSP with WebLogic 5.1/SP9/JDK 1.2.2
Hello everybody,
I get the error given below when calling a JSP in a WebLogic
application which seems to work fine in all other (non-JSP) parts:
java.lang.NullPointerException:
at weblogic.servlet.jsp.JspLexer.addSetPropertyValue(JspLexer.java:1432)
at weblogic.servlet.jsp.JspLexer.mXML_SET_PROPERTY(JspLexer.java,
Compiled Code)
at weblogic.servlet.jsp.JspLexer.mXML_THING(JspLexer.java:1726)
at weblogic.servlet.jsp.JspLexer.mTOKEN(JspLexer.java, Compiled Code)
at weblogic.servlet.jsp.JspLexer.nextToken(JspLexer.java, Compiled
Code)
at weblogic.servlet.jsp.JspLexer.parse(JspLexer.java, Compiled Code)
at weblogic.servlet.jsp.JspParser.doit(JspParser.java, Compiled Code)
at weblogic.servlet.jsp.JspParser.parse(JspParser.java:159)
at weblogic.servlet.jsp.Jsp2Java.outputs(Jsp2Java.java:109)
at weblogic.utils.compiler.CodeGenerator.generate(CodeGenerator.java,
Compiled Code)
at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java, Compiled
Code)
at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:227)
at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:115)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:915)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(ServletContextImpl.java:879)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(ServletContextManager.java:269)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(MuxableSocketHTTP.java:365)
at weblogic.socket.MuxableSocketHTTP.execute(MuxableSocketHTTP.java:253)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
Code)
I know that this error has been reported more than once in these
discussion groups, and all people who solved it say
- that it occurs only wen running WebLogic 5.1 with JDK 1.3 instead of
1.2.2
- that it may also be caused by bad jsp code
But in my case, it has to be another reason, because
- I am using jdk 1.2.2
- the same JSP file is running withour errors on WebLogic 6
I wonder if it could have something to do with the operating system:
the parsing error is produced on a Windows version of WL 5.1, while my
WL 6 which doesn't cause errors is running with Linux.
Many thanks in advance for any help,
Eckhard Beisswenger
Once again me!
After a long time, I stumbled by accident across the answer that solves the problem I described above. It is explained at
http://support.bea.com/application;JSESSIONID_WLCS_DEFAULT=2R2lzQfEBxFRMX2z0AxeU1Un3N1522I9fCIUI7GfjnjsiSYkPscz
The clue is that weblogic complains about corresponding get and set methods, when the type of the set methods parameter is different from the return type of the corresponding get method. Unfortunately, the weblogic lexer class gives only a NullPointerException without any hint.
-
Unable to deploy example 'banking' application on weblogic, please help...
Hi,
I have downloaded the example 'banking.zip' and have installed it.
I have followed all given steps in the tutorial, but I am unable to
see the login page.
I am also not able to see the ejb and web application descriptor file
from the admin console.
I have copied the banking directory to
'$WEBLOGIC\config\mydomain\applications'.
There are 3 directories under it
(1) ejb (containing meta-inf and examples directory. Meta-info
contains the descriptor .xml files)
(2) web (containing web-inf and html,jsp and image files. Web-inf
contains weblogic.xml and web.xml)
(3) Meta-Inf (containing the application.xml)
I get the 'Error 404--Not Found' error when I go to
http://localhost:8001/banking/login.html. (my server is running on
8001 port, i hope this doesn't matter)
When I try to edit the web application descriptor I get the following
error
java.lang.NullPointerException
at weblogic.management.console.utils.MBeans.getMBeanClassFor(MBeans.java:860)
at weblogic.management.console.actions.internal.ActionUtils.getAreaFor(ActionUtils.java:142)
at weblogic.management.console.actions.mbean.MBeanDescriptorFramesetAction.perform(MBeanDescriptorFramesetAction.java:133)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:167)
at weblogic.management.console.actions.internal.ActionServlet.doGet(ActionServlet.java:91)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2456)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2039)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Could someone please help me ? I am trying to deploy this in the
exploded form. My server is running in the development mode.
- Thanks in advance,
SonaliHi,
I was able to successfully deploy after installing
weblogic 6.1 SP2 (earlier I had SP1). Also, I had to make
changes in the BankAppServlet code since it tries to find the
bean with a different name than one specified in jndi-name.
- Thanks,
Sonali
[email protected] (Sonali Kale) wrote in message news:<[email protected]>...
Hi,
I have downloaded the example 'banking.zip' and have installed it.
I have followed all given steps in the tutorial, but I am unable to
see the login page.
I am also not able to see the ejb and web application descriptor file
from the admin console.
I have copied the banking directory to
'$WEBLOGIC\config\mydomain\applications'.
There are 3 directories under it
(1) ejb (containing meta-inf and examples directory. Meta-info
contains the descriptor .xml files)
(2) web (containing web-inf and html,jsp and image files. Web-inf
contains weblogic.xml and web.xml)
(3) Meta-Inf (containing the application.xml)
I get the 'Error 404--Not Found' error when I go to
http://localhost:8001/banking/login.html. (my server is running on
8001 port, i hope this doesn't matter)
When I try to edit the web application descriptor I get the following
error
java.lang.NullPointerException
at weblogic.management.console.utils.MBeans.getMBeanClassFor(MBeans.java:860)
at weblogic.management.console.actions.internal.ActionUtils.getAreaFor(ActionUtils.java:142)
at weblogic.management.console.actions.mbean.MBeanDescriptorFramesetAction.perform(MBeanDescriptorFramesetAction.java:133)
at weblogic.management.console.actions.internal.ActionServlet.doAction(ActionServlet.java:167)
at weblogic.management.console.actions.internal.ActionServlet.doGet(ActionServlet.java:91)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:265)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2456)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2039)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
Could someone please help me ? I am trying to deploy this in the
exploded form. My server is running in the development mode.
- Thanks in advance,
Sonali
Maybe you are looking for
-
Chart timestamp accelerating - why does this VI not work?
In fighting with TDMS files, I decided to experiment with a different approach to get what I need - a stripchart with a long history, that I can pause and scroll back through to look for anomolies. Came up with a clever (I thought) approach to it...
-
Moved photo library to external, space on internal drive did not change.
At the end of each year I like to move the current iPhoto library to an external hard drive to save space. The library get retitled Library 2007, Library 2008, etc. I do this to save space on my hard drive. My trusty iMac has only 80 gig hd (but that
-
Can anyone explain me the significance of replacement path?
hi all, Can anyone explain me replacement path - with text variables - with characteristics and - with formulas. Can anyone explain me with an example for each of those replacement path. And i heard abt replacement path for characteristics can
-
Hi everybody... i am new to the oracle. I got a Clone database with extension with ctl, dfb, dbc. May i know how to attach the database into my oracle . Clone was created in Oracle 10G R2 10.2.0.1 and Windows 2003 My System Configuration OS : Windows
-
Larger screen size video invitation
Is there a way to make ichat start with a larger video screen when invited by a buddy? In combination with autoaccept my mother just waits for my invitation and has not to enlarge the screen every time.