Problems with navigation when deploy application on WebLogic 10.3

Hi! I have problems with navigation when I deploy my application on Weblogic server 10.3. In my application I have two pages. One page where I can see the records. In this page I have button Create with action to secound jspx page. When I press this button then the first form (where I could see all records) is empty - the create operation worked, but navigation to second page not. Navigation rules is in adf task flow. In default server all works correct. Where is the problem?
Maybe when I deploy my application I need specialy deploy adf task flow or somewhere write something? If so, then can you explain me where? Any suggestions what to do.
Best regards!

I have in log:
2009.26.3 20:12:52 oracle.adfinternal.controller.faces.lifecycle.JSFLifecycleImp
l setLifecycleContextBuilder
WARNING: ADFc: Replacing the ADF Page Lifecycle implementation with 'oracle.adfi
nternal.controller.application.model.JSFDataBindingLifecycleContextBuilder'.
2009.26.3 20:12:52 oracle.adfinternal.controller.util.model.AdfmInterface initia
lize
INFO: ADFc: BindingContext is present, using ADFm APIs for DataControlFrames.
2009.26.3 20:12:52 oracle.adfinternal.controller.metadata.provider.MdsMetadataRe
sourceProvider <init>
INFO: ADFc: Controller caching of MDS metadata resources ENABLED.
2009.26.3 20:12:52 oracle.adf.controller.internal.metadata.MetadataService$Boots
trap add
INFO: ADFc: Loading bootstrap metadata from '/WEB-INF/adfc-config.xml'.
2009.26.3 20:12:54 oracle.adf.share.security.providers.jps.CSFCredentialStore fe
tchCredential
WARNING: Unable to locate the credential for key AUGI in D:\bea\user_projects\do
mains\base_domain\config\oracle.
2009.26.3 20:12:54 oracle.adf.share.jndi.ReferenceStoreHelper throwPartialResult
Exception
WARNING: Incomplete connection information
Edited by: Debuger on Mar 26, 2009 11:18 AM

Similar Messages

Java.lang.ClassNotFoundException when deploy application on Weblogic 10.3

Hi all, when I deploy an application on Weblogic 10.3 the following error occurs
the following detail is shown on the summary screen when I deploy the application via control
An error occurred during activation of changes, please see the log for details.
weblogic.application.ModuleException:
com.excellence.exoa.sso.SsoSessionListener
The deployment has been successfully installed
the following detail is shown on the log
Could not load user defined listener: com.excellence.exoa.sso.SsoSessionListener
java.lang.ClassNotFoundException: com.excellence.exoa.sso.SsoSessionListener
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:283)
at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:256)
at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:54)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:176)
at weblogic.utils.classloaders.ChangeAwareClassLoader.loadClass(ChangeAwareClassLoader.java:35)
at weblogic.servlet.internal.EventsManager.registerEventListeners(EventsManager.java:117)
at weblogic.servlet.internal.EventsManager.registerPreparePhaseListeners(EventsManager.java:65)
at weblogic.servlet.internal.WebAppServletContext.initContextListeners(WebAppServletContext.java:1765)
at weblogic.servlet.internal.WebAppServletContext.prepare(WebAppServletContext.java:1126)
at weblogic.servlet.internal.HttpServer.doPostContextInit(HttpServer.java:449)
at weblogic.servlet.internal.HttpServer.loadWebApp(HttpServer.java:424)
at weblogic.servlet.internal.WebAppModule.registerWebApp(WebAppModule.java:910)
at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:364)
at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:58)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:42)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:155)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:60)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723)
at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190)
at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45)
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)
the following listener is configured in the web.xml
<listener>
<listener-class>com.excellence.exoa.sso.SsoSessionListener</listener-class>
</listener>
and the SsoSessionListener class is packaged in the mainframe.jar. there are two mainframe.jar in this ear, the first which include SsoSessionListener in the souce directory and the other mainfrain.jar which extend the SsoSessionListener is in the ./extend/mainframe.jar
How can I fix this error ? any suggestion?
Thanks
Jayson
Edited by: Jayson on Feb 12, 2009 3:37 AM
Edited by: Jayson on Feb 12, 2009 3:54 AM

I have in log:
2009.26.3 20:12:52 oracle.adfinternal.controller.faces.lifecycle.JSFLifecycleImp
l setLifecycleContextBuilder
WARNING: ADFc: Replacing the ADF Page Lifecycle implementation with 'oracle.adfi
nternal.controller.application.model.JSFDataBindingLifecycleContextBuilder'.
2009.26.3 20:12:52 oracle.adfinternal.controller.util.model.AdfmInterface initia
lize
INFO: ADFc: BindingContext is present, using ADFm APIs for DataControlFrames.
2009.26.3 20:12:52 oracle.adfinternal.controller.metadata.provider.MdsMetadataRe
sourceProvider <init>
INFO: ADFc: Controller caching of MDS metadata resources ENABLED.
2009.26.3 20:12:52 oracle.adf.controller.internal.metadata.MetadataService$Boots
trap add
INFO: ADFc: Loading bootstrap metadata from '/WEB-INF/adfc-config.xml'.
2009.26.3 20:12:54 oracle.adf.share.security.providers.jps.CSFCredentialStore fe
tchCredential
WARNING: Unable to locate the credential for key AUGI in D:\bea\user_projects\do
mains\base_domain\config\oracle.
2009.26.3 20:12:54 oracle.adf.share.jndi.ReferenceStoreHelper throwPartialResult
Exception
WARNING: Incomplete connection information
Edited by: Debuger on Mar 26, 2009 11:18 AM

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

Error when deploying application in weblogic 10.0

weblogic.application.ModuleException: [HTTP:101216]Servlet: "cds-service" failed to preload on startup in Web application: "/cds-wsclient".
          org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'hdr2PersistenceManager' defined in class path resource [gov/va/med/cds/config/hdr2PersistenceContext.xml]: Cannot resolve reference to bean 'hdr2SessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'hdr2SessionFactory' defined in class path resource [gov/va/med/cds/config/hdr2PersistenceContext.xml]: Invocation of init method failed; nested exception is org.hibernate.HibernateException: Errors in named queries: VitalSignObservationEvent.patient.date, VitalSignObservationEvent.patient, IntoleranceCondition.patient.date, IntoleranceCondition.patient
          Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'hdr2SessionFactory' defined in class path resource [gov/va/med/cds/config/hdr2PersistenceContext.xml]: Invocation of init method failed; nested exception is org.hibernate.HibernateException: Errors in named queries: VitalSignObservationEvent.patient.date, VitalSignObservationEvent.patient, IntoleranceCondition.patient.date, IntoleranceCondition.patient
          Caused by: org.hibernate.HibernateException: Errors in named queries: VitalSignObservationEvent.patient.date, VitalSignObservationEvent.patient, IntoleranceCondition.patient.date, IntoleranceCondition.patient
               at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:339)
               at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1176)
               at org.springframework.orm.hibernate3.LocalSessionFactoryBean.newSessionFactory(LocalSessionFactoryBean.java:805)
               at org.springframework.orm.hibernate3.LocalSessionFactoryBean.buildSessionFactory(LocalSessionFactoryBean.java:745)
               at org.springframework.orm.hibernate3.AbstractSessionFactoryBean.afterPropertiesSet(AbstractSessionFactoryBean.java:134)
               at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1202)
               at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1172)
               at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:428)
               at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:251)
               at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:156)
               at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:248)
               at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160)
               at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:261)
               at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:109)
               at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1100)
               at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:862)
               at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:424)
               at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:251)
               at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:156)
               at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:248)
               at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:160)
               at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:287)
               at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:352)
               at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:330)
               at org.springframework.web.servlet.FrameworkServlet.initWebApplicationContext(FrameworkServlet.java:266)
               at org.springframework.web.servlet.FrameworkServlet.initServletBean(FrameworkServlet.java:236)
               at org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.java:126)
               at javax.servlet.GenericServlet.init(GenericServlet.java:241)
               at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:282)
               at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
               at weblogic.security.service.SecurityManager.runAs(Unknown Source)
               at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:63)
               at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
               at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
               at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:504)
               at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1830)
               at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1807)
               at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1727)
               at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2890)
               at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:948)
               at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:353)
               at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
               at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
               at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
               at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
               at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
               at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
               at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
               at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
               at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
               at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
               at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
               at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
               at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
               at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
               at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
               at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
               at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
               at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
               at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:816)
               at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
               at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:434)
               at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
               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:464)
               at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
               at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)
               at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:950)
               at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:353)
               at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
               at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
               at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
               at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
               at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
               at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
               at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
               at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
               at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
               at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
               at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
               at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
               at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
               at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
               at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
               at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
               at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
               at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
               at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:816)
               at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1223)
               at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:434)
               at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
               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:464)
               at weblogic.work.ExecuteThread.execute(ExecuteThread.java:200)
               at weblogic.work.ExecuteThread.run(ExecuteThread.java:172)

I was trying to deploy a Hibernate based application on WL 10.0 . I was getting this exception.
          your help would be greatly appreciated.

Error when deploy application on weblogic's console(weblogic 10 on AIX)

?:|
After successfully start weblogic,I access console and select "Deployment".While I click "Finish" after choose the application named "ls_app", an error appears as follow.
- Messages
The deployment has not been installed.
java.lang.NullPointerException
The log information from weblogic is as follow::-(
Failures were detected while initiating distribute task for application 'ls_app'. Error is: ''
WARN [PageFlowRequestProcessor] Struts module is configured to use com.bea.console.internal.ConsolePageFlowRequestProcessor as the request processor, but the <controller> element does not contain a <set-property> for "controllerClass".
Page Flow actions in this module may not be handled correctly.
Please help on this issue.Thanks!!:-)

I have in log:
2009.26.3 20:12:52 oracle.adfinternal.controller.faces.lifecycle.JSFLifecycleImp
l setLifecycleContextBuilder
WARNING: ADFc: Replacing the ADF Page Lifecycle implementation with 'oracle.adfi
nternal.controller.application.model.JSFDataBindingLifecycleContextBuilder'.
2009.26.3 20:12:52 oracle.adfinternal.controller.util.model.AdfmInterface initia
lize
INFO: ADFc: BindingContext is present, using ADFm APIs for DataControlFrames.
2009.26.3 20:12:52 oracle.adfinternal.controller.metadata.provider.MdsMetadataRe
sourceProvider <init>
INFO: ADFc: Controller caching of MDS metadata resources ENABLED.
2009.26.3 20:12:52 oracle.adf.controller.internal.metadata.MetadataService$Boots
trap add
INFO: ADFc: Loading bootstrap metadata from '/WEB-INF/adfc-config.xml'.
2009.26.3 20:12:54 oracle.adf.share.security.providers.jps.CSFCredentialStore fe
tchCredential
WARNING: Unable to locate the credential for key AUGI in D:\bea\user_projects\do
mains\base_domain\config\oracle.
2009.26.3 20:12:54 oracle.adf.share.jndi.ReferenceStoreHelper throwPartialResult
Exception
WARNING: Incomplete connection information
Edited by: Debuger on Mar 26, 2009 11:18 AM

When I open Firefox the following alert appears: "Could not initialize the application's security component. The most likely cause is problems with files in your application's profile directory." There is a solution in the forum but only for Windows based

When I open the application the following alert appears: "Could not initialize the application's security component. The most likely cause is problems with files in your application's profile directory." There is a solution on the support site but only for Windows-based Firefox, and I'm a Mac user. I have plenty of room on my hard disk.
== This happened ==
Every time Firefox opened
== Two days ago, for no apparent reason.

In Mac OS X v10.7, the $HOME/Library folder is a hidden folder.
Open Finder and use one of these:
* Go > Go To Folder (Shift-Command-G) and in the dialog type: ~/Library
* Open the "Go" menu and hold down the Option key to make the Library appear
You can also use this command in a Terminal window to remove the hidden flag.
* Mac HD > Applications > Utilities > Terminal
* chflags nohidden ~/Library

Problem while Deploying application in weblogic admin console

Hi all,
Recently i got an issue while deploying application through weblogic admin console,
I have logged in the weblogic console and clicked on the deployment option, i got the page of install the application, then i have click the install option, i was getting the page of blank white screen. checking the log file of the admin server i cannot find any error. The admin server was running state was ok. before many times i have done deploying application in the same weblogic admin console.
My weblogic 10.3 was running in windows 2008 r2
Kindly need a help to resolve this problem ASAP.
Regards,
Rakhi

Hi sir,
thanks for ur reply.. but while troubleshooting on this issue i am facing another problem,
The weblogic server is running on windows os box, i have stop the weblogic admin server from the windows services and again started the weblogic admin server, the server was running in proper state and i have open the console and try the same thing clicking on the deployment and install options but the same issue i faced. getting the white blank screen, while trying to refresh the page i cannot get the weblogic console waiting for long time also. again after restarting the server i can get the weblogic console.
Then i have tried in another way, i removed the window services and started the weblogic server from command prompt,after starting the server i have opened the admin console and click on the deployment and install option, it is working fine. i tried the same for many times its working fine. but while starting from windows services the problem i was facing same as blank white screen,
Kindly give me a perfect resolution on this issue. because i was so confused on this part.
Regards,
Rakhi..

Having a problem with dates when I send my numbers doc to excel. dates are all out and that they have to cut and paste individual entries onto their spreadsheet. Any idea how I can prevent this

having a problem with dates when I send my numbers doc to excel. dates are all out and that they have to cut and paste individual entries onto their spreadsheet. Any idea how I can prevent this.
I'm using Lion on an MBP and Numbers is the latest version

May you give more details about what is wrong with your dates ?
M…oSoft products aren't allowed on my machines but I use LibreOffice which is a clone of Office.
When I export from Numbers to Excel and open the result with LibreOffice, the dates are correctly treated.
To be precise, dates after 01/01/1904 are correctly treated. dates before 01/01/1904 are exported as strings but, as it's flagged during the export process, it's not surprising.
Yvan KOENIG (VALLAURIS, France) mardi 3 janvier 2012
iMac 21”5, i7, 2.8 GHz, 12 Gbytes, 1 Tbytes, mac OS X 10.6.8 and 10.7.2
My iDisk is : http://public.me.com/koenigyvan
Please : Search for questions similar to your own before submitting them to the community
For iWork's applications dedicated to iOS, go to :
https://discussions.apple.com/community/app_store/iwork_for_ios

Problem with navigation and masthead by changing languages with Anonymous

Hi All,
i have a problem with navigation and masthead by changin the language when accessing as anonymous user.
Ive created two additional users anon_de (with language german )and anon_en (for english).
I've created also two links in the in masthead:
/irj/portal/anonymous?guest_user=anon_en and /irj/portal/anonymous?guest_user=anon_de
When i choose "de" for the first time it works fine, but when i choose "en" again the language in the content are is changing to english again, but not in navigation and masthead. When i click again on link for "en" the languge is set to english. Strange thing is that when i click on "de" instead the portal content change to german but masthead and navigation are in english now, as it should be before....
It seems that masthead and navigation have always prevoius language selected.
Do you know, what could be the reason of that strange behavior?
Thanks for help
Karol

Hi Detlev,
you are right. the user is not "updated" fast enough... the strange thing is, that it works by the first time i change the language...
well.. i can implement that workaround as you suposed, but it would be a really workaround as the same page will be requestes second time, causing requests number to be double..
Thanks for help
ps. i forgot to mark this message as question to give points.. if you tell me how i can change that ill reward your answer..

I suddenly have this error message on FireFoxthis message pops up: "Could not initialize the application's security component. The most likely cause is problems with files in your application's profile directory. Please check that this directory has no re

I suddenly encounter this error message from Fire Fox.
Could not initialize the application's security component. The most likely cause is problems with files in your application's profile directory. Please check that this directory has no read/write restrictions and your hard disk is not full or close to full. It is recommended that you exit the application and fix the problem. If you continue to use this session, you might see incorrect application behaviour when accessing security features.
I uninstalled the browser and download a new version but it does not resolve the issue.
I know my hard disc has ample space. I do NOT know where to find the Profile directory to fix the read restriction box.
== This happened ==
Every time Firefox opened
== After something about security add-on of Norton pop up by itself. ==
== User Agent ==
Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; MSN Optimized;US)

This link shows things to check - https://support.mozilla.com/kb/Could+not+initialize+the+browser+security+component

New WIN7 System, FFox gives error "Could not initialize the application's security component. The most likely cause is problems with files in your application's profile directory" - will not go to any site.

New Windows 7 computer. After installing Firefox, every time I bring it up I get the following message:
"Could not initialize the application's security component. The most likely cause is problems with files in your application's profile directory. Please check that this directory has no read/write restrictions and your hard disk is not full or close to full. It is recommended that you exit the application and fix the problem. If you continue to use this session, you might see incorrect application behaviour when accessing security features."
Then Firefox comes up, but will not function at all - can enter url address, but will not respond to ANY clicks, so can not go to any site.

This link shows how to fix this - https://support.mozilla.com/kb/Could+not+initialize+the+browser+security+component

This message [Ubuntu repositories or Mozilla download: " There is no Profile folder Could not initialize the application's security component. The most likely cause is problems with files in your application's profile directory....

Ubuntu 11.04: I have been getting this message whenever I install Firefox from the repositories and downloading the tar file. I cannot use Firefox! " There is no Profile folder Could not initialize the application's security component. The most likely cause is problems with files in your application's profile directory. Please check that this directory has no read/write restrictions and your hard disk is not full or close to full. It is recommended that you exit the application and fix the problem. If you continue to use this session, you might see incorrect application behaviour when accessing security features."Firefox does not respond to any addresses or a google search. Indeed it responds to nothing. There is no Profile folder!

Uninstalling Firefox on Linux
* http://kb.mozillazine.org/Uninstalling_Firefox#On_Linux
* http://kb.mozillazine.org/Installation_directory#Linux
* Removing user profile data - http://kb.mozillazine.org/Uninstalling_Firefox#Removing_user_profile_data
After all is done, Restart your system.
Installing Firefox on Linux
* https://support.mozilla.com/en-US/kb/Installing%20Firefox%20on%20Linux
Check and tell if its working.

BUG: Entering a "version" when deploying to a WebLogic server doesn't work

By default when deploying to a weblogic server the "Version" is set to v2.0. If you change that to something like v2.1 when the application is deployed, the deployment logs still show the Version=2.0. What needs to be done to get the Version in deployment to accept the changes on the deployment form?

Sorry, I wasn't clear. This is a Portal application deployed using MDS. So it doesn't have the file referenced in that blog post. The Version field I'm referring to is on the form that pops up to set the MDS repository. For reasons unknown it will always come up v2.0 even during the first deployment. Regardless of what I change it to the Version always equals 2.0 in the deployment logs.

URGENT : Problems with exporting a translated application

Hi ! I have a problem with exporting a translated application. Effectively, I exported both applications (The normal and the translated version). I want now to apply the translation XLIFF. I want to know if it is possible to apply my old XLIFF file. The problem is that I can't select the same ID for my application.
I really have problems!
Anyone can help me ?

When I import the translated version, the translation works a little bit. Effectively, all my reports appear but there is no item that appears.

I have a problem with itunes when I sync the saved music and want to sync my iphone 5 ios 7.0.6 no longer passes the music thing is that just stays on "waiting for sync" and not worry please help are more than 400 songs that do not want to hear who are wi

I have a problem with itunes when I sync the saved music and want to sync my iphone 5 ios 7.0.6 no longer passes the music thing is that just stays on "waiting for sync" and not worry please help are more than 400 songs that do not want to hear who are wi

Plawexki wrote:
... do you know if the contacts, photos, messages etc will be wiped?
Yes... Everything will be Wiped and Replaced with what is currently on Your Mac.
SYNCING with iTunes
See here > http://support.apple.com/kb/HT1386
From Here > http://www.apple.com/support/iphone/syncing/
You may find this information of interest...
Have a read here...
https://discussions.apple.com/message/18409815?ac_cid=ha
And See Here...
How to Use Multiple iDevices with One Computer

Problems with navigation when deploy application on WebLogic 10.3

Similar Messages

Maybe you are looking for