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.xml

Lauren,
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

Similar Messages

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.

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 exception

Dear 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

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,
Vitaly

Vitaly 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 from generated code? (WLS81SP2)

We are receiving an NPE, and looks like it is coming from
the generated code. Most oddly, it is intermittent; repeating the operation that causes the error often succeeds. Any thoughts? Here is the stack trace:
2005-09-12 17:21:31.273 | payprocess.ProcessBatch:process | EJB Exception: ; nested exception is:
     javax.ejb.TransactionRolledbackLocalException: EJB Exception: ; nested exception is: javax.ejb.TransactionRolledbackLocalException: EJB Exception: ; nested exception is: java.lang.NullPointerException
java.rmi.RemoteException: EJB Exception: ; nested exception is:
     javax.ejb.TransactionRolledbackLocalException: EJB Exception: ; nested exception is: javax.ejb.TransactionRolledbackLocalException: EJB Exception: ; nested exception is: java.lang.NullPointerException
     at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:284)
     at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:244)
     at org.ecmc.nib.batch.session.PaymentProcessFacade_blomzu_EOImpl_812_WLStub.processPayments(Unknown Source)
     at org.ecmc.nib.batch.payprocess.ProcessPaymentsHelper.queryFredTransPosted(ProcessPaymentsHelper.java:72)
     at org.ecmc.nib.batch.payprocess.ProcessBatch.checkForPayments(ProcessBatch.java:206)
     at org.ecmc.nib.batch.payprocess.ProcessBatch.process(ProcessBatch.java:133)
     at org.ecmc.common.batch.AbstractBatchJob.startBatch(AbstractBatchJob.java:40)
     at org.ecmc.nib.batch.payprocess.ProcessPayments.main(ProcessPayments.java:71)
Caused by: javax.ejb.TransactionRolledbackLocalException: EJB Exception: ; nested exception is: javax.ejb.TransactionRolledbackLocalException: EJB Exception: ; nested exception is: java.lang.NullPointerException
     at weblogic.ejb20.internal.EJBRuntimeUtils.throwTransactionRolledbackLocal(EJBRuntimeUtils.java:248)
     at weblogic.ejb20.internal.BaseEJBLocalHome.handleSystemException(BaseEJBLocalHome.java:247)
     at weblogic.ejb20.internal.BaseEJBLocalObject.postInvoke(BaseEJBLocalObject.java:327)
     at org.ecmc.nib.batch.session.RouterFacade_s27p4a_ELOImpl.route(RouterFacade_s27p4a_ELOImpl.java:57)
     at org.ecmc.nib.batch.session.PaymentProcessFacadeBean.processPayments(PaymentProcessFacadeBean.java:38)
     at org.ecmc.nib.batch.session.PaymentProcessFacade_blomzu_EOImpl.processPayments(PaymentProcessFacade_blomzu_EOImpl.java:46)
     at org.ecmc.nib.batch.session.PaymentProcessFacade_blomzu_EOImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
     at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

Oops, sorry about that, grabbed the stack trace from the wrong spot; the correct trace is below:
####<Sep 12, 2005 5:21:31 PM CDT> <Info> <EJB> <wlsprd2.ecmc.lan> <ms1> <ExecuteThread: '20' for queue: 'weblogic.kernel.Default'> <PMT_PROCESS> <BEA1-593B17F9A1A85E2AA270> <BEA-010051> <EJB Exception occurred during invocation from home: org.ecmc.nib.model.LoanCancelFacade_fy2xso_HomeImpl@184a0b7 threw exception: java.lang.NullPointerException
java.lang.NullPointerException
>
####<Sep 12, 2005 5:21:31 PM CDT> <Info> <EJB> <wlsprd2.ecmc.lan> <ms1> <ExecuteThread: '20' for queue: 'weblogic.kernel.Default'> <PMT_PROCESS> <BEA1-593B17F9A1A85E2AA270> <BEA-010051> <EJB Exception occurred during invocation from home: [email protected]89 threw exception: javax.ejb.TransactionRolledbackLocalException: EJB Exception: ; nested exception is: java.lang.NullPointerException
javax.ejb.TransactionRolledbackLocalException: EJB Exception: ; nested exception is: java.lang.NullPointerException
java.lang.NullPointerException
javax.ejb.TransactionRolledbackLocalException: EJB Exception: ; nested exception is: java.lang.NullPointerException
     at weblogic.ejb20.internal.EJBRuntimeUtils.throwTransactionRolledbackLocal(EJBRuntimeUtils.java:248)
     at weblogic.ejb20.internal.BaseEJBLocalHome.handleSystemException(BaseEJBLocalHome.java:247)
     at weblogic.ejb20.internal.BaseEJBLocalObject.postInvoke(BaseEJBLocalObject.java:327)
     at org.ecmc.nib.model.LoanCancelFacade_fy2xso_ELOImpl.localGetLoanPlacementStatusTypCd(LoanCancelFacade_fy2xso_ELOImpl.java:228)
     at org.ecmc.nib.batch.session.payprocess.CheckLoanBalance.update(CheckLoanBalance.java:40)
     at org.ecmc.nib.batch.session.payprocess.RouteToMethods$RouteMeQueryHandler.processStep(RouteToMethods.java:240)
     at org.ecmc.nib.batch.session.payprocess.RouteToMethods$RouteMeQueryHandler.processRow(RouteToMethods.java:111)
     at org.springframework.jdbc.core.JdbcTemplate$RowCallbackHandlerResultSetExtractor.extractData(JdbcTemplate.java:939)
     at org.springframework.jdbc.core.JdbcTemplate$1QueryStatementCallback.doInStatement(JdbcTemplate.java:256)
     at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:204)
     at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:266)
     at org.springframework.jdbc.core.JdbcTemplate.query(JdbcTemplate.java:270)
     at org.ecmc.nib.batch.session.payprocess.RouteToMethods.routeMe(RouteToMethods.java:62)
     at org.ecmc.nib.batch.session.RouterFacadeBean.route(RouterFacadeBean.java:35)
     at org.ecmc.nib.batch.session.RouterFacade_s27p4a_ELOImpl.route(RouterFacade_s27p4a_ELOImpl.java:46)
     at org.ecmc.nib.batch.session.PaymentProcessFacadeBean.processPayments(PaymentProcessFacadeBean.java:38)
     at org.ecmc.nib.batch.session.PaymentProcessFacade_blomzu_EOImpl.processPayments(PaymentProcessFacade_blomzu_EOImpl.java:46)
     at org.ecmc.nib.batch.session.PaymentProcessFacade_blomzu_EOImpl_WLSkel.invoke(Unknown Source)
     at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
     at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
     at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
     at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
     at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
     at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
     at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)

Problem during migrating from weblogic to oracle9iAS, .......urgent

Hi all
I am migrating my application from weblogic 7.0 to oracle9iAS Release2 Version 9.0.2.
My problem is:
In my application, after an entity bean creates a row in the table, if there is any SQL update or insert in the same transaction for the same table to which the entity bean created the row, Oracle9iAS could not proceed with the transaction(it is locking indefinitely the stored procedure which is either updating or inserting).
After analysing the problem,i found that this is working in Weblogic because of the following parameter in the weblogic-ejb-jar.xml.
<delay-updates-until-end-of-tx>false</delay-updates-until-end-of-tx>
The function of the above parameter in Weblogic is:
Setting delay-updates-until-end-of-tx to false does not cause database updates to be "committed" to the database after each method invoke; they are only sent to the database. Updates are committed or rolled back in the database only at the conclusion of the transaction.
My question is Is there any such parameter or its equivalent in oracle9iAS or is there any way to get out of this problem. This is very urgent for me......plz help me out.
Thanks in advance,
Siva Kishor

Hi,
The tag (delay-updates-until-commit) you have suggested was not compatiable with oracle9iAS 9.0.2, It is giving "Counld not recognize "delay-updates-until-commit" in orion-ejb-jar.xml during deployment of the jar.
So we have migrated our application to oracle9iAS 9.0.3. Now we are not getting any such error during deployment but while using the application to insert/update getting Null PointerException.
This problem may be related with some migrating issues of Oracle App server(9.0.3).
But at the same time this can be related with EJB's coding also since this new version
of Oracle App server is compatible with EJB 2.0, our application has been developed using EJB1.1 Spec.
This is the stack trace, during accessing EntityBean.
java.lang.NullPointerException
at com.evermind.server.ejb.EJBUtils.cloneOneObjectInstance(EJBUtils.java
:416)
at com.evermind.server.ejb.EJBUtils.cloneHashMap(EJBUtils.java:523)
at com.evermind.server.ejb.EJBUtils.cloneObject(EJBUtils.java:375)
at IIMST_PARTY_VERSIONEB_EntityBeanWrapper387.getAll(IIMST_PARTY_VERSION
EB_EntityBeanWrapper387.java:543)
at iims.PARTY.BPPTYPARTYBean.SAVEPARTYINDVDTL(BPPTYPARTYBean.java:589)
at BPPTYPARTY_StatelessSessionBeanWrapper409.SAVEPARTYINDVDTL(BPPTYPARTY
_StatelessSessionBeanWrapper409.java:811)
at iims.PARTY.TCPTYBean.TRANSACTIONCONTROL(TCPTYBean.java:939)
at TCPTY_StatelessSessionBeanWrapper423.TRANSACTIONCONTROL(TCPTY_Statele
ssSessionBeanWrapper423.java:133)
at _party._PCPTY__PROCESS__1.processBody(_PCPTY__PROCESS__1.java:2005)
at _party._PCPTY__PROCESS__1._jspService(_PCPTY__PROCESS__1.java:3897)
at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:5
6)
at oracle.jsp.runtimev2.JspPageTable.compileAndServe(JspPageTable.java:5
37)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:272)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:465)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:379)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterC
hain.java:65)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:283)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletReque
stDispatcher.java:560)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(Ser
vletRequestDispatcher.java:306)
at com.evermind.server.http.ServletRequestDispatcher.forward(ServletRequ
estDispatcher.java:209)
at _party._PCPTY__PROCESS.processBody(_PCPTY__PROCESS.java:4473)
at _party._PCPTY__PROCESS._jspService(_PCPTY__PROCESS.java:4557)
at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:5
6)
at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:317)
at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:465)
at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:379)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterC
hain.java:65)
at oracle.security.jazn.oc4j.JAZNFilter.doFilter(JAZNFilter.java:283)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletReque
stDispatcher.java:560)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(Ser
vletRequestDispatcher.java:306)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpReques
tHandler.java:767)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java
:148)
at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java
:72)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExec
utor.java:803)
at java.lang.Thread.run(Thread.java:479)
Regards
kishor

Migrating from Weblogic 9.2 to 10.3.2 getting Error

While Migrating from Weblogic 9.2 to 10.3, I am getting the following error. Please help me to solve this issue.
<openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal user error> org.apache.openjpa.util.MetaDataException: Errors encountered while resolving metadata. See nested exceptions for details.
at org.apache.openjpa.meta.MetaDataRepository.resolve(MetaDataRepository.java:563)
at org.apache.openjpa.meta.MetaDataRepository.getMetaData(MetaDataRepository.java:308)
at org.apache.openjpa.enhance.PCEnhancer.<init>(PCEnhancer.java:248)
at org.apache.openjpa.enhance.PCEnhancer.<init>(PCEnhancer.java:219)
at org.apache.openjpa.enhance.PCClassFileTransformer.transform0(PCClassFileTransformer.java:139)
Truncated. see log file for complete stacktrace
Caused By: java.lang.NullPointerException
at org.apache.openjpa.meta.ClassMetaData.validateAppIdClass(ClassMetaData.java:1874)
at org.apache.openjpa.meta.ClassMetaData.validateIdentity(ClassMetaData.java:1832)
at org.apache.openjpa.meta.ClassMetaData.validateMeta(ClassMetaData.java:1749)
at org.apache.openjpa.meta.ClassMetaData.resolve(ClassMetaData.java:1622)
at org.apache.openjpa.meta.MetaDataRepository.processBuffer(MetaDataRepository.java:717)
Truncated. see log file for complete stacktrace
Dec 7, 2010 4:17:14 PM weblogic.utils.classloaders.ClassPreProcessor$ClassPreProcessorSupport preProcess
WARNING: Error pre-processing class com.bac.fvo.model.exposure.RiskRatingExposure with weblogic.deployment.PersistenceUnitInfoImpl$ClassPreProcessorImpl@1074a5f'
<openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal user error> org.apache.openjpa.util.MetaDataException: Errors encountered while resolving metadata. See nested exceptions for details.
at org.apache.openjpa.meta.MetaDataRepository.resolve(MetaDataRepository.java:563)
at org.apache.openjpa.meta.MetaDataRepository.getMetaData(MetaDataRepository.java:308)
at org.apache.openjpa.enhance.PCEnhancer.<init>(PCEnhancer.java:248)
at org.apache.openjpa.enhance.PCEnhancer.<init>(PCEnhancer.java:219)
at org.apache.openjpa.enhance.PCClassFileTransformer.transform0(PCClassFileTransformer.java:139)
at org.apache.openjpa.enhance.PCClassFileTransformer.transform(PCClassFileTransformer.java:120)
at org.apache.openjpa.persistence.PersistenceProviderImpl$ClassTransformerImpl.transform(PersistenceProviderImpl.java:210)
at weblogic.deployment.PersistenceUnitInfoImpl$ClassPreProcessorImpl.preProcess(PersistenceUnitInfoImpl.java:547)
at weblogic.utils.classloaders.ClassPreProcessor$ClassPreProcessorSupport.preProcess(ClassPreProcessor.java:102)
at weblogic.utils.classloaders.GenericClassLoader.doPreProcess(GenericClassLoader.java:357)
at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:338)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:301)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:269)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:56)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:177)
at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:37)
at org.hibernate.util.ReflectHelper.classForName(ReflectHelper.java:107)
at org.hibernate.ejb.Ejb3Configuration.classForName(Ejb3Configuration.java:1008)
at org.hibernate.ejb.Ejb3Configuration.addNamedAnnotatedClasses(Ejb3Configuration.java:1080)
at org.hibernate.ejb.Ejb3Configuration.addClassesToSessionFactory(Ejb3Configuration.java:871)
at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:758)
at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:425)
at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:131)
at org.springframework.orm.jpa.LocalContainerEntityManagerFactoryBean.createNativeEntityManagerFactory(LocalContainerEntityManagerFactoryBean.java:227)
at org.springframework.orm.jpa.AbstractEntityManagerFactoryBean.afterPropertiesSet(AbstractEntityManagerFactoryBean.java:281)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1333)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1299)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:463)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:404)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:375)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:263)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:170)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:260)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:184)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:163)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeansOfType(DefaultListableBeanFactory.java:309)
at org.springframework.beans.factory.BeanFactoryUtils.beansOfTypeIncludingAncestors(BeanFactoryUtils.java:270)
at org.springframework.dao.support.PersistenceExceptionTranslationInterceptor.detectPersistenceExceptionTranslators(PersistenceExceptionTranslationInterceptor.java:122)
at org.springframework.dao.support.PersistenceExceptionTranslationInterceptor.<init>(PersistenceExceptionTranslationInterceptor.java:78)
at org.springframework.dao.annotation.PersistenceExceptionTranslationAdvisor.<init>(PersistenceExceptionTranslationAdvisor.java:70)
at org.springframework.dao.annotation.PersistenceExceptionTranslationPostProcessor.setBeanFactory(PersistenceExceptionTranslationPostProcessor.java:97)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1290)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:463)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:404)
at java.security.AccessController.doPrivileged(Native Method)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:375)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:263)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:170)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:260)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:184)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:163)
at org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:881)
at org.springframework.context.support.AbstractApplicationContext.registerBeanPostProcessors(AbstractApplicationContext.java:597)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:366)
at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:254)
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:198)
at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45)
at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:481)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:181)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1801)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3045)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1397)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:460)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:247)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:27)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:1267)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:83)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:409)
at weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:39)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:51)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:196)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:30)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:233)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:169)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:123)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:173)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:89)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: java.lang.NullPointerException
at org.apache.openjpa.meta.ClassMetaData.validateAppIdClass(ClassMetaData.java:1874)
at org.apache.openjpa.meta.ClassMetaData.validateIdentity(ClassMetaData.java:1832)
at org.apache.openjpa.meta.ClassMetaData.validateMeta(ClassMetaData.java:1749)
at org.apache.openjpa.meta.ClassMetaData.resolve(ClassMetaData.java:1622)
at org.apache.openjpa.meta.MetaDataRepository.processBuffer(MetaDataRepository.java:717)
at org.apache.openjpa.meta.MetaDataRepository.resolveMeta(MetaDataRepository.java:616)
at org.apache.openjpa.meta.MetaDataRepository.resolve(MetaDataRepository.java:541)
... 95 more
Thanks in Advance
Sheejo Rapheal

We have war application and we have antlr in preclasspath. have weblogic.xml entries as suggested. still it's going to OpenJPA.
WARNING: Error pre-processing class com.bac.fvo.model.pricing.PricingVerificationPK with weblogic.de
ployment.PersistenceUnitInfoImpl$ClassPreProcessorImpl@3d8b1e3'
<openjpa-1.1.1-SNAPSHOT-r422266:891341 fatal user error> org.apache.openjpa.util.MetaDataException:
Type "class com.bac.fvo.model.pricing.PricingVerificationPK" with application identity and no superc
lass does not declare an id class. This type is not eligible for builtin identity, so it must decla
re an id class.
at org.apache.openjpa.meta.ClassMetaData.validateAppIdClass(ClassMetaData.java:1858)
at org.apache.openjpa.meta.ClassMetaData.validateIdentity(ClassMetaData.java:1834)
at org.apache.openjpa.meta.ClassMetaData.validateMeta(ClassMetaData.java:1751)
at org.apache.openjpa.meta.ClassMetaData.resolve(ClassMetaData.java:1624)
at org.apache.openjpa.meta.MetaDataRepository.processBuffer(MetaDataRepository.java:717)
at org.apache.openjpa.meta.MetaDataRepository.resolveMeta(MetaDataRepository.java:616)
at org.apache.openjpa.meta.MetaDataRepository.resolve(MetaDataRepository.java:542)
at org.apache.openjpa.meta.MetaDataRepository.getMetaData(MetaDataRepository.java:308)
at org.apache.openjpa.enhance.PCEnhancer.<init>(PCEnhancer.java:248)
at org.apache.openjpa.enhance.PCEnhancer.<init>(PCEnhancer.java:220)
at org.apache.openjpa.enhance.PCClassFileTransformer.transform0(PCClassFileTransformer.java:
139)
at org.apache.openjpa.enhance.PCClassFileTransformer.transform(PCClassFileTransformer.java:1
20)
at org.apache.openjpa.persistence.PersistenceProviderImpl$ClassTransformerImpl.transform(Per
sistenceProviderImpl.java:210)
at weblogic.deployment.PersistenceUnitInfoImpl$ClassPreProcessorImpl.preProcess(PersistenceU
nitInfoImpl.java:620)
at weblogic.utils.classloaders.ClassPreProcessor$ClassPreProcessorSupport.preProcess(ClassPr
eProcessor.java:102)
at weblogic.utils.classloaders.GenericClassLoader.doPreProcess(GenericClassLoader.java:341)
at weblogic.utils.classloaders.GenericClassLoader.defineClass(GenericClassLoader.java:322)
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:285
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:253)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:
56)
at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:
42)
at org.hibernate.util.ReflectHelper.classForName(ReflectHelper.java:107)
at org.hibernate.ejb.Ejb3Configuration.classForName(Ejb3Configuration.java:1008)
at org.hibernate.ejb.Ejb3Configuration.addNamedAnnotatedClasses(Ejb3Configuration.java:1080)
at org.hibernate.ejb.Ejb3Configuration.addClassesToSessionFactory(Ejb3Configuration.java:871
at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:761)
at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:425)
at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersi
stence.java:132)
ApplicationContext.xml is
     
     <context:annotation-config/>
     
     <bean class="org.springframework.orm.jpa.support.PersistenceAnnotationBeanPostProcessor"/>
     
     <bean class="org.springframework.dao.annotation.PersistenceExceptionTranslationPostProcessor"/>
          
     
     <tx:annotation-driven transaction-manager="transactionManager"/>

Error while deploying ear file generated from weblogic to ocj4

Hi All,
I have an .ear file which has been generated from weblogic server.I tried to deploy it on ocj4 aby created a new project in eclipse and deploying it on ocj4.
When I try to run my project it gives me an error:
2008-12-15 19:13:54.811 NOTIFICATION J2EE JSP-0008 Unable to dispatch JSP Page : Exception:oracle.classloader.util.AnnotatedLinkageError: duplicate class definition: javax/xml/rpc/Service
     Invalid class: javax.xml.rpc.Service
     Loader: Test.web.TSOptyQGateWeb:0.0.0
     Code-Source: /C:/OC4J_10.1.3.4/j2ee/home/applications/Test/TSOptyQGateWeb/WEB-INF/lib/jaxrpc.jar
     Configuration: WEB-INF/lib/ directory in C:\OC4J_10.1.3.4\j2ee\home\applications\Test\TSOptyQGateWeb\WEB-INF\lib
     Dependent class: oracle.jsp.runtimev2.JspPageInstFacade$DeclaredAction
     Loader: oc4j:10.1.3
     Code-Source: /C:/OC4J_10.1.3.4/j2ee/home/lib/ojsp.jar
     Configuration: <code-source> in META-INF/boot.xml in C:\OC4J_10.1.3.4\j2ee\home\oc4j.jar
     The original class instance was defined in the shared-library oracle.ws.jaxrpc:1.1, and oc4j:10.1.3 does import that loader. This may be a search-order problem.
Can anyone help??

Hi,
I checked the log-files, but there are no helpful informations, but:
07/04/23 12:08:04 - Start updating EAR file...
07/04/23 12:08:04 - start-up mode is lazy
07/04/23 12:08:20 - com.sap.engine.deploy.manager.DeployManagerException: com.sap.engine.services.deploy.container.DeploymentException: Cannot update archive file Docsndownloads.war
                     com.sap.engine.services.deploy.ear.exceptions.BaseIOException: Error during replacement of substitution values. Reason:
                      java.io.IOException: Stream closed
and
Apr 23, 2007 12:08:20... Error: Aborted: development component 'Dokusunddownloads'/'sap.com'/'localhost'/'2007.04.23.12.07.47'/'0':
Caught exception during application deployment from SAP J2EE Engine's deploy API:
com.sap.engine.deploy.manager.DeployManagerException: com.sap.engine.services.deploy.container.DeploymentException: Cannot update archive file Docsndownloads.war
com.sap.engine.services.deploy.ear.exceptions.BaseIOException: Error during replacement of substitution values. Reason:
java.io.IOException: Stream closed
thanks,
Lu

Upgrading from Weblogic 6.1sp5/TopLink 3.6.3 to Weblogic 8.1/TopLink 9.0.4

Hi.
We are doing the migration from Weblogic 6.1sp5/TopLink 3.6.3 to Weblogic 8.1 & TopLink 9.0.4
We have been reading available documentation and started the migration. We have not had any problems with package ranaming issues and XML DOCTYPES changes.
As we do have a lot of ammedmed querys, we do prefer to use a java class as our proyect mapping descriptor rather than a huge XML.
We are currently porting all our querys to the new system.
As we are doing a lot of changes we are also updating our EJB 1.1 entity beans to EJB 2.0 (maybe in the future we will deploy our EJBs with local interfaces too).
The main problem we are facing right now is with all the querys we had in our toplink-cmp-<bean>.xml files. Even if most of the finders are "REDIRECT" querys that had to be ammendmed we have a good number of "EXPRESSION"s on them.
As far as we are able to see we should move them to the TopLink Project java file in the querys section. The question is: is it possible to declare them in the ejb-jar.xml file into the <ejb-ql> tag (we have seen that the TopLinkImplemented string appears on the <ejb-ql> telling the container who should handle the query, so if Weblogic can be "tricked" to do that "ejb-ql" it may be possible to do the same with a TopLink expression isn't it?.
Another issue we don't have clear is if now all the querys must be either ejb-ql (compliant with the EJB 2.0 standard) or named querys (either TopLink expressions or SQL querys) defined in the TopLink Project java or XML files. What happened with the redirect querys
I would like to point just another issue we have "solved" but we are not really satisfied with how we solved it.
We are using timestamp locking with our entity beans. The shouldBindAllParameters is set to true too and we have the logging activated so we have been able to track down the problem.
The problem seems to be something like this.
You create a new entity bean and TopLink issues a sentence like this against the DB (Oracle 8.1.7 I must say we have also configured the login session to use the Oracle8PlatformSupport)
INSERT INTO FOO(OID,OCA) VALUES (?, ?)
bind => [1, 2004-04-26 13:16:45.251]
As far as we know Oracle 8.1.7 doesn't store the milliseconds (we are using DATE type in Oracle tables) so the ".251" value is stored as "0"
Then we try to delete the entity bean and TopLink sends this sentence to the database:
DELETE FROM FOO WHERE ((OID = ? AND OCA = ?))
bind => [1, 2004-04-26 13:16:45.251]
Then, a TOPLINK-5003 (the object has been modified or deleted since last read) is raised and the transaction is rolled back.
We tried without binding and it works perfect (it seems that the timestamp is treated as YYYY-MM-DD SSSSS in the "to_date" function issued)
As we would like to keep with binding all parameters in order to optimize our database accesses we have changed the default jdbc driver (sun.jdbc...) that is showed when reading the proper property of the login sesion with the oracle.jdbc.driver.OracleDriver. This latest driver seems to solve the problem with the reminders of the timestamps but this brings us a doubt.
If we have configured two datasources in our Weblogic's config.xml file (one for transactional operations, beeing that one also an XA driver as we need to coordinate RDBMS operations with a JMS service, and the other one being a "standar" oracle.jdbc.driver.OracleDriver) why is that the driver used as default by the login method is that "weird" sun.jdbc... driver? Shouldn't TopLink use one (the XA driver I hopefully) of the drivers defined in Weblogic's datasource?
1. Is the issue we are seeing with the timestamp a known bug/problem?
2. Is there a better way to solve it than changing the driver (we are affraid of the "new" issues changing it could raise)
I have seen that with TopLink 3.6.3 and the "default" driver used in the login (it is the same by default on both TopLink 3.6.3 and TopLink 9.0.4) the binded timestamp are "truncated" to the second resolution and it works without any problem.
Thanks in advance.
Ignacio

Not sure on all of the issues, but can provide some information on some of them.
Re-directors:
Support was added for re-director to core queries, so now your named queries can make use of re-director if they require advanced dynamic execution. So all re-director queries can become named queries.
Timestamp locking:
In general we would always suggest numeric version locking if you have the choice. I'm not clear on what you are saying about the driver having an effect on the problem, however in general Oracle 8 does not support milliseconds, if you use timestamp locking with local timestamps they will have milliseconds and the database values will not match the ones in memory.
To resolve this you can,
- Use server timestamps TimestampLockingPolicy.useServerTime()
- Clear the timestamp's milli/nano second value through an aboutToInsert event.
- Extend Oracle8Platform.convertObject to clear the timestamp's milli/nano second value.
- If you can use Oracle 9 or 10 there is now a TIMESTAMP type that does support milliseconds.
If a different driver seems to be solving this, it is most likely the database ignores the milliseconds in the comparison, but the driver you are using sends the millisecond to the database incorrectly when binding.

PL/SQL procedure is 10x slower when running from weblogic

Hi everyone,
we've developed a PL/SQL procedure performing reporting - the original solution was written in Java but due to performance problems we've decided to switch this particular piece to PL/SQL. Everything works fine as long as we execute the procedure from SQL Developer - the batch processing 20000 items finishes in about 80 seconds, which is a serious improvement compared to the previous solution.
But once we call the very same procedure (on exactly the same data) from weblogic, the performance seriously drops - instead of 80 seconds it suddenly runs for about 23 minutes, which is 10x slower. And we don't know why this happens :-(
We've profiled the procedure (in both environments) using DBMS_PROFILER, and we've found that if the procedure is executed from Weblogic, one of the SQL statements runs noticeably slower and consumes about 800 seconds (90% of the total run time) instead of 0.9 second (2% of the total run time), but we're not sure why - in both cases this query is executed 32742-times, giving 24ms vs. 0.03ms in average.
The SQL is
SELECT personId INTO v_personId FROM (
        SELECT personId FROM PersonRelations
        WHERE extPersonId LIKE v_person_prefix || '%'
) WHERE rownum = 1;Basically it returns an ID of the person according to some external ID (or the prefix of the ID). I do understand why this query might be a performance problem (LIKE operator etc.), but I don't understand why this runs quite fast when executed from SQL Developer and 10x slower when executed from Weblogic (exactly the same data, etc.).
Ve're using Oracle 10gR2 with Weblogic 10, running on a separate machine - there are no other intensive tasks, so there's nothing that could interfere with the oracle process. According to the 'top' command, the wait time is below 0.5%, so there should be no serious I/O problems. We've even checked JDBC connection pool settings in Weblogic, but I doubt this issue is related to JDBC (and everything looks fine anyway). The statistics are fresh and the results are quite consistent.
Edited by: user6510516 on 17.7.2009 13:46

The setup is quite simple - the database is running on a dedicated database server (development only). Generally there are no 'intensive' tasks running on this machine, especially not when the procedure I'm talking about was executed. The application server (weblogic 10) is running on different machine so it does not interfere with the database (in this case it was my own workstation).
No, the procedure is not called 20000x - we have a table with batch of records we need to process, with a given flag (say processed=0). The procedure reads them using a cursor and processes the records one-by-one. By 'processing' I mean computing some sums, updating other table, etc. and finally switching the record to processed=1. I.e. the procedure looks like this:
CREATE PROCEDURE process_records IS
    v_record records_to_process%ROWTYPE;
BEGIN
     OPEN records_to_process;
     LOOP
          FETCH records_to_process INTO v_record;
          EXIT WHEN records_to_process%NOTFOUND;
          -- process the record (update table A, insert a record into B, delete from C, query table D ....)
          -- and finally mark the row as 'processed=1'
     END LOOP;
     CLOSE records_to_process;
END process_records;The procedure is actually part of a package and the cursor 'records_to_process' is defined in the body. One of the queries executed in the procedure is the SELECT mentioned above (the one that jumps from 2% to 90%).
So the only thing we actually do in Weblogic is
CallableStatement cstmt = connection.prepareCall("{call ProcessPkg.process_records}");
cstmt.execute();and that's it - there is only one call to the JDBC, so the network overhead shouldn't be a problem.
There are 20000 rows we use for testing - we just update them to 'processed=0' (and clear some of the other tables). So actually each run uses exactly the same data, same code paths and produces the very same results. Yet when executed from SQL developer it takes 80 seconds and when executed from Weblogic it takes 800 seconds :-(
The only difference I've just noticed is that when using SQL Developer, we're using PL/SQL notation, i.e. "BEGIN ProcessPkg.process_records; END;" instead of "{call }" but I guess that's irrelevant. And yet another difference - weblogic uses JDBC from 10gR2, while the SQL Developer is bundled with JDBC from 11g.

No output at all from weblogic.Admin HELP | GETSTATE | VERSION on linux

Hi, somehow I am getting zero output from weblogic.Admin command, is it redirected somewhere?
#>java -cp $WH/server/lib/weblogic.jar weblogic.Admin -adminurl $AURL -username weblogic -password $WPWD VERSION
#>java -cp $WH/server/lib/weblogic.jar weblogic.Admin -adminurl $AURL -username weblogic -password $WPWD GETSTATE
#>
#>java -cp $WH/server/lib/weblogic.jar weblogic.Admin -username weblogic -password $WPWD HELP
#>
Thanks.

Hi,
You need to Run the SetDomainEnv.sh/cmd from the Domain_Home/bin and then you can execute the below Commands and they will execute succesfully
Eg:From Windows Environment Same applies in Linux Environmet as well
C:\Oracle\Middleware\wlserver_10.3\server\lib>java -cp weblogic.jar weblogic.Admin -adminurl t3://localhost:7001 -username weblogic -password weblogic1 VERSION
WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638
C:\Oracle\Middleware\wlserver_10.3\server\lib>java -cp weblogic.jar weblogic.Admin -adminurl t3://localhost:7001 -username weblogic -password weblogic1 GETSTATE
Current state of "AdminServer" : RUNNING
C:\Oracle\Middleware\wlserver_10.3\server\lib>java -cp weblogic.jar weblogic.Admin -adminurl t3://localhost:7001 -username weblogic -password weblogic1 HELP
Usage: java [<SSL trust options>] weblogic.Admin
        [ [-url | -adminurl] [<protocol>://]<listen-address>:<port>]
        -username <username> [-password <password>]
        <COMMAND> <ARGUMENTS>
Hope it helps

How can I get all the settings from weblogic.properties ?

Hi, and excuse me for my poor english.....
I have a T3Client and I want to obtain all the settings from weblogic
properties...
With the sentence getT3Services().config().getProperty("......"), I can
obtain the property, but my problem is that at runtime, I don`t know
established names....
I want to obtain something as the AdminProps servlet, but with a non-web
client.....
Can anybody help me ?

Hi, and excuse me for my poor english.....
I have a T3Client and I want to obtain all the settings from weblogic
properties...
With the sentence getT3Services().config().getProperty("......"), I can
obtain the property, but my problem is that at runtime, I don`t know
established names....
I want to obtain something as the AdminProps servlet, but with a non-web
client.....
Can anybody help me ?

How can i get all the users from weblogic server?

how can i get all the users from weblogic server?
i have configurated a LDAP server using iPlanet and
in weblogic server console i see those users from LDAP
server. but how can i get all the users in my program
from weblogic server instead of LDAP server?
BTW,how to configure a RDBMSAuthenticator and what should i do
in Oracle? which tables should i create? and how are their architectures?
Thanks
Daniel

BTW, i use weblogic platform 8.1
"Daniel" <[email protected]> Ð´ÈëÓÊ¼þ
news:[email protected]..
how can i get all the users from weblogic server?
i have configurated a LDAP server using iPlanet and
in weblogic server console i see those users from LDAP
server. but how can i get all the users in my program
from weblogic server instead of LDAP server?
BTW,how to configure a RDBMSAuthenticator and what should i do
in Oracle? which tables should i create? and how are their architectures?
Thanks
Daniel

Error while trying to pick message from weblogic queue

Hi,
We are getting the following error while trying to connect to pick up a message from weblogic queue.
We are suing oracle soa suite 10.1.3.1 and weblogic 8.1
the bad part is that, this error is not documented anywhere and couldn't get much help on this.
Would appreciate any suggestions / pointers on this.
Let me know if any further information is required.
invoke failed
org.collaxa.thirdparty.apache.wsif.WSIFException: file:/E:/product/10.1.3.1/OracleAS_4/bpel/domains/default/tmp/.bpel_OTOCBPELProcess_1.0_78fcf080ec2bd7495aebfb5373e76116.tmp/readmsg.wsdl [ Consume_Message_ptt::Consume_Message(opaque) ] - WSIF JCA Execute of operation 'Consume_Message' failed due to: ERRJMS_IX_WRONG_SPEC.
Outbound interaction invoked with incorrect InteractionSpec.
; nested exception is:
ORABPEL-12115
ERRJMS_IX_WRONG_SPEC.
Outbound interaction invoked with incorrect InteractionSpec.
---------------------------------------------------

Hi!
I am facing a similar issue, does someone have an idea ?
<remoteFault xmlns="http://schemas.oracle.com/bpel/extension"><part name="code"><code>null</code>
</part><part name="detail"><detail>null</detail>
</part><part name="summary"><summary>file:/opt/oracle/product/10.1.3.1/OracleAS_1/bpel/domains/default/tmp/.bpel_TestReceiveMessage_BPEL_1.0_e00fd88d454889b871183d0d92dc9f7d.tmp/plReceiveMessage.wsdl [ Consume_Message_ptt::Consume_Message(TestPushMessage_BPELProcessRequest) ] - WSIF JCA Execute of operation 'Consume_Message' failed due to: ERRJMS_IX_WRONG_SPEC.
Outbound interaction invoked with incorrect InteractionSpec.
; nested exception is:
ORABPEL-12115
ERRJMS_IX_WRONG_SPEC.
Outbound interaction invoked with incorrect InteractionSpec.
Please examine the log file to determine the problem.
</summary>
</part></remoteFault>
Thanks,
romain.

Error connecting to websphere MQ from weblogic 10.3.0 :EndPointFinder

1)     We are in process of connection from weblogic 10.3.0 to websphere MQ series . We are trying connecting to the response queues using MQclient binding . I created .binding file using following configuration
DEFINE QCF(BBNMSRMSConnectionFactory2) QMGR(ESBMBJU2) CHAN(ESBMBJU2_SSL) HOST(bos69872.bst.bls.com) PORT(1414) TEMPMODEL(WEBLOGIC.MODEL.QUEUE) TRAN(CLIENT)
DEFINE QCF(BBNMSRMSConnectionFactory2) QMGR(ESBMBJU2) CHAN(ESBMBJU2_SSL) HOST(bos69874.bst.bls.com) PORT(1415) TEMPMODEL(WEBLOGIC.MODEL.QUEUE) TRAN(CLIENT)
DEFINE Q(BBNMSSERESPONSEQUEUE1) QUEUE(FUSIONQL.BBNMSE.BBNMSTORMS.1_0.D.JU.RSP) QMGR(ESBMBJU1) TARGCLIENT(MQ)
DEFINE Q(BBNMSSERESPONSEQUEUE2) QUEUE(FUSIONQL.BBNMSE.BBNMSTORMS.1_0.D.JU.RSP) QMGR(ESBMBJU2) TARGCLIENT(MQ)
DEFINE QCF(BBNMSRMSCF1) QMGR(ESBMBJU1) CHAN(ESBMBJU1_SSL) HOST(bos69872.bst.bls.com) PORT(1414) TEMPMODEL(WEBLOGIC.MODEL.QUEUE) TRAN(CLIENT)
ALTER QCF(BBNMSRMSConnectionFactory1) CHAN(ESBMBJU1_SSL) SSLCIPHERSUITE(SSL_RSA_WITH_NULL_MD5)
ALTER QCF(BBNMSRMSConnectionFactory2) CHAN(ESBMBJU2_SSL) SSLCIPHERSUITE(SSL_RSA_WITH_NULL_MD5)
2)     The I created the foreign JMS-server as such :
<foreign-server name="ForeignRmsServer-1">
<default-targeting-enabled>true</default-targeting-enabled>
<foreign-destination name="RmsFusionBusRequestQueue1">
<local-jndi-name>RmsResponseQueue1</local-jndi-name>
<remote-jndi-name>BBNMSSERESPONSEQUEUE1</remote-jndi-name>
</foreign-destination>
<foreign-connection-factory name="RmsFusionBusFactory1">
<local-jndi-name>RmsFusionBusfactory1</local-jndi-name>
<remote-jndi-name>BBNMSRMSConnectionFactory1</remote-jndi-name>
<username>m66300d</username>
<password-encrypted xsi:nil="true"/>
</foreign-connection-factory>
<initial-context-factory>com.sun.jndi.fscontext.RefFSContextFactory</initial-context-factory>
<connection-url>file:/opt/mqm/java/bin/mqjndi</connection-url>
</foreign-server>
3)     Subsequently I use the JNDI names configured in foreign server(above) in weblogic-ejb-jar.xml .
<weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/10.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<weblogic-enterprise-bean>
<ejb-name>RMSRespMDB</ejb-name>
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>10</max-beans-in-free-pool>
<initial-beans-in-free-pool>5</initial-beans-in-free-pool>
</pool>
<destination-jndi-name>BBNMSSERESPONSEQUEUE1</destination-jndi-name>
<initial-context-factory>com.sun.jndi.fscontext.RefFSContextFactory</initial-context-factory>
<provider-url>file:/opt/mqm/java/bin/mqjndi</provider-url>
<connection-factory-jndi-name>BBNMSRMSConnectionFactory1</connection-factory-jndi-name>
</message-driven-descriptor>
<transaction-descriptor>
<trans-timeout-seconds>300</trans-timeout-seconds>
</transaction-descriptor>
<enable-call-by-reference>true</enable-call-by-reference>
<jndi-name>jms.RMSRespMDB</jndi-name>
<dispatch-policy>JbbosServicesServerXQ</dispatch-policy>
</weblogic-enterprise-bean>
<weblogic-compatibility>
<entity-always-uses-transaction>true</entity-always-uses-transaction>
</weblogic-compatibility>
</weblogic-ejb-jar>
4)     Now when my MDB comes up its giving following error
Mar 8, 2011 10:13:16 AM EST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application
'RMSRespMDB'.
weblogic.application.ModuleException: Exception activating module: EJBModule(RMSRespMDB)
Unable to deploy EJB: RMSRespMDB from RMSRespMDB.jar:
unable to find EndPointFinder for file:/opt/mqm/java/bin/mqjndi
at weblogic.ejb.container.deployer.EJBModule.activate(EJBModule.java:493)
at weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:107)
at weblogic.application.internal.flow.DeploymentCallbackFlow$2.next(DeploymentCallbackFlow.java:411)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:74)
Truncated. see log file for complete stacktrace
java.lang.AssertionError: unable to find EndPointFinder for file:/opt/mqm/java/bin/mqjndi
at weblogic.rmi.spi.RMIRuntime.getEndPointFinder(RMIRuntime.java:61)
at weblogic.rmi.spi.RMIRuntime.findOrCreateEndPoint(RMIRuntime.java:42)
at weblogic.rmi.extensions.server.RemoteDomainSecurityHelper.isRemoteDomain(RemoteDomainSecurityHelper.java:379)
at weblogic.jms.common.ServerCrossDomainSecurityUtil.isRemoteDomain(ServerCrossDomainSecurityUtil.java:319)
at weblogic.jms.common.ServerCrossDomainSecurityUtil.getRemoteSubject(ServerCrossDomainSecurityUtil.java:116)
Truncated. see log file for complete stacktrace
>
My binding file is correctly placed on the following location file:/opt/mqm/java/bin/mqjndi with appropriate permissions
Some info :
Our weblogic version is 10.3.0
I tracked this exception (unable to find EndPointFinder) to bug id 8168598
Can anyone please suggest what can be issue potentially
Thanks in advance

hi,
Even i want to connect webspere MQ 7 with weblogic 10.3, can u suggest me some document where i can follow step by step?
I have too tried using some binding file,but it is not reading the same.

NullPointerException from weblogic.i18ntools.l10ngen

Similar Messages

Maybe you are looking for