Oracle VM Manager Error
Hello.
I have some problems with Oracle VM Manager.
Oracle VM Manager
Version: 3.0.1.1361
Build: 20110818_1361
When I try to delete/create Virtual Machine I get such error:
"ADF_FACES-60097:For more information, please see the server's error log for an entry beginning with: ADF_FACES-60096:Server Exception during PPR, #2"
From log file:
[2011-10-27T00:17:32.596+03:00] [AdminServer] [ERROR] [] [oracle.adfinternal.view.faces.config.rich.RegistrationConfigurator] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: admin] [ecid: ed6a9604e327fec3:212e54d:133421229c7:-8000-0000000000000064,0] [APP: ovm_console] ADF_FACES-60096:Server Exception during PPR, #2[[
javax.servlet.ServletException: java.lang.NullPointerException
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:277)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:205)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:106)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:60)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:446)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:271)
at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:177)
at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.oracle.ovm.mgr.faces.servlet.SessionExpiryCheckFilter.doFilter(SessionExpiryCheckFilter.java:77)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.security.jps.ee.http.JpsAbsFilter$1.run(JpsAbsFilter.java:111)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
at oracle.security.jps.ee.util.JpsPlatformUtil.runJaasMode(JpsPlatformUtil.java:413)
at oracle.security.jps.ee.http.JpsAbsFilter.runJaasMode(JpsAbsFilter.java:94)
at oracle.security.jps.ee.http.JpsAbsFilter.doFilter(JpsAbsFilter.java:161)
at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:71)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.servlet.DMSServletFilter.doFilter(DMSServletFilter.java:136)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
Please help me to solve this problem.
Thanks!
893391 wrote:
Oracle VM Manager
Version: 3.0.1.1361Can you upgrade to Oracle VM Manager and Server 3.0.2? Part of the upgrade process clears out orphaned objects, which may resolve this issue.
Similar Messages
-
Oracle Performance Manager error VTM-0002
Hi,
when i am trying to display charts using Oracle Performance Manager it's throwing errors like
VTM-0002: Error displaying chart CPU Breakdown
ODG-05185: Error: message decode:
VP_START_COLLECT_REQ: vppcallbb failed
can any one help?i feel it's a configuration problem not a oracle bug. and who wants pin those oracle guys ; )
any guess from you ppl ?
I am using Oracle 9.0.1.0.1 in windows, connecting to the server from remote system. -
Hi all,
Inorder to test SSL, i created a certificate request in OWM.Then i got a trial certificate from verisign for this request.What should i do now ? I tried to import that certificate in Oracle Wallet manager but getting this error.
"Trusted Certificate Installation Failed.
Input was not a valid certificate".
Please guide me
Srinibelw is the note
PURPOSE
To list the steps needed to configure Oracle HTTP Server (OHS) to use the Secure
Sockets Layer (SSL) when installed with Oracle9i Application Server (9iAS)
Release 2 (9.0.2). The below instructions show, step by step, instructions for
obtaining a trial certificate from a Certificate Authority, such as Verisign or
Thawte. Please refer to the Oracle 9iAS Documentation for further details.
SCOPE AND APPLICATION
Oracle9i Application Server (9iAS) Release 2 (9.0.2 and above)
Configuring SSL with Oracle HTTP Server in 9iAS Release 2
There are two major steps needed to configure SSL in 9iAS:
I. Create an Oracle Wallet which contains an SSL Certificate
II. Configure httpd.conf directives to enable SSL with OHS
NOTE:
Only standard server certificates are supported. These are sometimes referred
to as "40-bit Certificates", but will allow 128-bit encryption provided the
browser supports 128-bit encryption. 9iAS Release 2 does not support Global
Server Certificates, called "128-bit Certificates", that allow 56-bit export
browsers to step up to 128-bit.
STEP I: Configuring Oracle Wallet Manager (OWM)
1. Start Oracle Wallet Manager from the 9iAS $ORACLE_HOME.
Note: If you wish to use AutoLogin features you must start OWM as the user
who owns the httpd parent process.
To start Oracle Wallet Manager:
On Windows: select Start > Programs > Oracle - ORACLE_HOME >
Integrated Management Tools > Wallet Manager
On UNIX: enter owm at the command line.
2. Create an Oracle Wallet which contains an SSL Certificate:
- Select Wallet -> New
- Enter a password for the wallet e.g Welcome1
- Create a Certificate Request.
- Enter the details for the request. For example:
Common Name: <hostname.domainname>
Organizational Unit: Support
Organization: Oracle
Location: Reading
State: Berkshire
Country: United Kingdom
Key Size: 1024bits
* Common Name has to match the hostname.domainname that the webserver is
known as. This is the Servername parameter in the httpd.conf file, and
is the hostname.domainname that users will enter in the browser URL.
- Click OK.
- Click 'Certificate:[Requested]' and select from the Menu 'Operations' and
'Export Certificate Request'
- Save to a file e.g server.csr
- Open the file in a text editor and copy the contents of the certificate
signing request, to be pasted in a Certificate Authority (Verisign) form.
An example is shown below:
-----BEGIN NEW CERTIFICATE REQUEST-----
MIIBtzCCASACAQAwdzELMAkGA1UEBhMCR0IxEjAQBgNVBAgTCWJlcmtzaGlyZTEQMA4GA1UEBxMH
cmVhZGluZzEPMA0GA1UEChQGb3JhY2xlMRAwDgYDVQQLFAdzdXBwb3J0MR8wHQYDVQQDFBZ1a2Ro
MTkzNC51ay5vcmFjbGUuY29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCYkFMb9x4ehsG3
yQ2ub319GxPW+/TC3NSIYRLzEa49EziqBUr08R3Ssn9+6nolVjj1eb3rzwCfjiOSzsp1lSa/B9Vo
63pwP6xLbCgF8J86YfcZvavgLzY0Yc1fPfRxpZkb/jjt+F1zkaI6Lilm5YU3bRNYMb36TAWxUYL1
m6wZOwIDAQABoAAwDQYJKoZIhvcNAQEEBQADgYEACKXTmPHaSe3Lx3onnKJk/qI8SzpKyQC/B29v
JGg1+7Lb7gl052Y9WKxbKHzOQOYr8yYxMXNBCUwW6kBAFoxTWSpIxIQOpJXcsu1RlHKaLfAnw053
LiwpRB6do7MBrVgMRiv3AyTkJkgRzSxABWAgNpBPbhH+L6PZj5tSjOPErKA=
-----END NEW CERTIFICATE REQUEST-----
3. Request a Certificate from a Certificate Authority:
- Load a web browser and go a Certificate Authority website of your choice.
The examples below are from www.thawte.com:
- Click on 'request your free trial'.
- Fill in the necessary name and address details etc. and 'Submit'.
- Paste in the certificate request into the box under the
'Certificate Signing Request' Section.
- Select "Test X509v3 SSL Cert" and hit "Generate Test Certificate"
- Once submitted the Trial Certificate will appear on screen similar to below:
-----BEGIN CERTIFICATE-----
MIICnDCCAgWgAwIBAgIDD9m+MA0GCSqGSIb3DQEBBAUAMIGHMQswCQYDVQQGEwJa
QTEiMCAGA1UECBMZRk9SIFRFU1RJTkcgUFVSUE9TRVMgT05MWTEdMBsGA1UEChMU
VGhhd3RlIENlcnRpZmljYXRpb24xFzAVBgNVBAsTDlRFU1QgVEVTVCBURVNUMRww
GgYDVQQDExNUaGF3dGUgVGVzdCBDQSBSb290MB4XDTAxMTAyNDE0MDIxOVoXDTAx
MTExNDE0MDIxOVowdzELMAkGA1UEBhMCR0IxEjAQBgNVBAgTCUJlcmtzaGlyZTEQ
MA4GA1UEBxMHUmVhZGluZzEPMA0GA1UEChQGT3JhY2xlMRAwDgYDVQQLFAdTdXBw
b3J0MR8wHQYDVQQDFBZ1a3AxNTkxOC51ay5vcmFjbGUuY29tMIGfMA0GCSqGSIb3
DQEBAQUAA4GNADCBiQKBgQDiQbg8KHjQ8hazvFe+OFhQa6ka+i5oShUty1MhlH+/
/xXP+j82h4VlyPG6IGKeQdXLhnKXgLuxTZ8/VDtLZyucmpIB95o2A3Betjp7UdIm
C572rKrQTA+1mCt/KLWcNE+fQuCmhloaERh3jsWTng0TKsDpJeAJdW2F4tCy/E/E
MwIDAQABoyUwIzATBgNVHSUEDDAKBggrBgEFBQcDATAMBgNVHRMBAf8EAjAAMA0G
CSqGSIb3DQEBBAUAA4GBACffzyC3qvAlvNWc6mBPMjFu6XWUGZBuNawFCz8qGw5/
ce3rWFNI4zOjc1OncoJg7FjDJgAWqiJFHgdV4gwQm/8lTJX6wD1FhMtrJDXf29ei
1DAe8kBOBWiFMio8Qjp24TdxoI6/53/32ydl91CPtTKAix3SaC2bBS5lG73AbKRr
-----END CERTIFICATE-----
- Copy the certificate to a file called server.crt
- Get the Trusted CA Root certificate by accessing:
https://www.thawte.com/roots/index.html
- Copy the certificate that appears on the screen to a file called
servertest.crt
- Ftp or move the files to a directory on your server
- In Wallet Manager select Operations -> Import User Certificate.
- It will then ask you if you want to Paste the certificate or load
from a file. Choose 'Select a file that contains a certificate'.
- Select the file server.crt and hit OK.
- At this point, the Wallet Manager may complain that the Trusted CA Root
Certificate does not exist in the wallet. It will ask if you want to
import it now. Select Yes. See Below
- Select 'Select a file that contains a certificate' and select the
servertest.crt file.
- If this completes successfully you should see Certificate:[Ready] and the
Thawte Test CA Root will appear in the list of trusted certificates.
- If you desire Oracle HTTP Server to AutoLogin to the Wallet, then select
AutoLogin. (Wallet Manager must have been started as the owner of the
httpd parent process for this to work).
- From the menu, File -> Save
Save the Wallet in a directory where the 9iAS user has permission to access
* If you generated your test certificate via www.verisign.com there is an additional
step required if OWM is not accepting the Trusted CA Root Certificate. The step is
as follows:
In OWM, at the point of message "User certificate import has failed because the
CA certificate does not exist". You are expected to import the CA certificate.
For Verisign, that would be the 'Test CA Root' for the Trial version. Verisign's
email has instructions on how to download the Test CA Root. One problem with the
Test CA Root is that it is saved as DER encoding, but OWM expects BASE64 encoding.
Please do following, using Internet Explorer 5.X as example.
1. Following Verisign instructions and install Test CA Root
certification into IE.
2. Export 'Test CA Root' from IE in BASE64 format
Tools -> Internet Options -> Contents -> Certificates
-> Trusted Root Certificate Authorities
Select CA issued by Versign with following Description in 'Issued to' column
"For Versign authorized testing only ....."
Export -> Next -> select Base-64 encoded X.509(.cer)
The file saved must me accessible to OWM
3. When prompted to load 'CA certificate ', provide the Base64 encoded file.
Then, continue where you left off when OWM did not accept your Trusted CA
Root Certificate.
STEP II: Configuring Oracle HTTP Server (OHS)
Please review the default directives in the httpd.conf file that relate to SSL by
opening the file in a text editor and search on "SSL". If you have not already
done so, please make a back up of this file. Do NOT hand edit this file without reading
the precautions in the 9iAS Documentation. You should use the Enterprise Manager (EM)
Website to modify this file. For SSL to work, the SSL 'listen' port must match the
"VirtualHost _default_" directive within the file. All other SSL parameters are
set to the default, and you can modify at a later time, depending on your needs.
## SSL Support
Listen 80
Listen 443
#443 is the SSL port number.
##Further down in file:
<VirtualHost default:443>
For the purposes of a basic SSL configuration, you should only need to
change the following directives:
SSLWallet
SSLWalletPassword
- Change the SSLWallet directive to the path where you saved your wallet, i.e:
SSLWallet file:/tmp/wallets
- If you get an error, ADMN-906025 with exception 806212, when starting OHS
after modifying httpd.conf, it is because you need to supply this password.
You may also see errors such as the following:
Error Failed to restart HTTP Server.
Timeout has been reached. Timeout has been reached.
If you did not select AutoLogin, then you need to change the SSLWalletPassword
to your clear text Wallet password by adding the following into your httpd.conf
SSLWalletPassword <yourPassword>
- If you wish to encrypt the SSLWalletPassword refer to the following:
[NOTE:184677.1]
How to Use IASOBF to Encrpyt a Wallet Password Within 9iAS Release 2
- Save the configuration, and restart Oracle HTTP Server
- Test a URL to Oracle HTTP Server in SSL mode:
https://<hostname.domainname>:<port> -
Oracle Enterprise Manager Error(s)
I recently installed Oracle 11g on my computer and am playing around with it and have come across two errors that i see are pretty common but i cant wrap my head around whats going on.
Scenario 1:
I start up my computer, no services are running (OracleDBConsoleorcl, OracleTNSListener & OracleServiceORCL) are all not on.
I go into control panel->Services and turn on OracleDBConsoleorcl so i can log into enterprise manager.
When I enter enterprise manager I see that i can start up the listener or database instance.
I start up the listener (no problems) but when i try to turn on the instance I then get the error
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor
When i go back to the control panel and services and start up OracleServiceORCL then everything works as expected.
Why am i not able to start up the oracle instance via the enterprise manager?
Thanks....rodneyc8063 wrote:
I recently installed Oracle 11g on my computer and am playing around with it and have come across two errors that i see are pretty common but i cant wrap my head around whats going on.
Scenario 1:
I start up my computer, no services are running (OracleDBConsoleorcl, OracleTNSListener & OracleServiceORCL) are all not on.
I go into control panel->Services and turn on OracleDBConsoleorcl so i can log into enterprise manager.
When I enter enterprise manager I see that i can start up the listener or database instance.
I start up the listener (no problems) but when i try to turn on the instance I then get the error
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor
When i go back to the control panel and services and start up OracleServiceORCL then everything works as expected.
Why am i not able to start up the oracle instance via the enterprise manager?
Thanks....
>I recently installed Oracle 11g on my computer and am playing around with it and have come across two errors that i see are pretty common but i cant wrap my head around whats going on.
Scenario 1:
I start up my computer, no services are running (OracleDBConsoleorcl, OracleTNSListener & OracleServiceORCL) are all not on.
I go into control panel->Services and turn on OracleDBConsoleorcl so i can log into enterprise manager.
When I enter enterprise manager I see that i can start up the listener or database instance.
I start up the listener (no problems) but when i try to turn on the instance I then get the error
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor
When i go back to the control panel and services and start up OracleServiceORCL then everything works as expected.
Why am i not able to start up the oracle instance via the enterprise manager?
Thanks....
EM can only connect to the DB via SQL*Net.
When the DB is down the listener does not know anything about the DB.
When EM tries to connect to the DB the listener reports it does not know how to complete the connection request -
Oracle Server Management Error!!!
Hi all,
Can anyone faced this b4?
I'm getting an error while logging into Oracle management server!!
the OMS service has started..
i've craeted a repository with user OEM and Pwd. XXXXXX
but when i try to logging into EMS..it gives incorrect login credential..
even though i've entered exact user name & pwd
my machine name is IRDBACK with domain XXX.XXX.com
when it gives me login screen
i put this info
Administrator: OEM
Password :xxxxx
Management Server: IRDBACK.XXX.XXX.com
is it ok?
Thanx in Advance...Hi all,
Can anyone faced this b4?
I'm getting an error while logging into Oracle management server!!
the OMS service has started..
i've craeted a repository with user OEM and Pwd. XXXXXX
but when i try to logging into EMS..it gives incorrect login credential..
even though i've entered exact user name & pwd
my machine name is IRDBACK with domain XXX.XXX.com
when it gives me login screen
i put this info
Administrator: OEM
Password :xxxxx
Management Server: IRDBACK.XXX.XXX.com
is it ok?
Thanx in Advance... -
Aloha!
I have just created a database instance on oracle 11g R2. When i tried to create a connection to that said instance on net manager from a certain client machine
i'm prompted with this error:
ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
but on the server itself i can access the instance through SQLplus as sysdba.
Thanks in advance for the help.
Regards,
HadesORA-12514: TNS:listener does not currently know of service requested in connect descriptor
Cause: The listener received a request to establish a connection to a database or other service. The connect descriptor received by the listener specified a service name for a service (usually a database service) that either has not yet dynamically registered with the listener or has not been statically configured for the listener. This may be a temporary condition such as after the listener has started, but before the database instance has registered with the listener.
Action:
- Wait a moment and try to connect a second time.
- Check which services are currently known by the listener by executing: lsnrctl services <listener name>
- Check that the SERVICE_NAME parameter in the connect descriptor of the net service name used specifies a service known by the listener.
- If an easy connect naming connect identifier was used, check that the service name specified is a service known by the listener.
- Check for an event in the listener.log file. -
*********Oracle Learning Management Error Help**********
Hi code was deployed to PROD environment last night and now I am seeing the following OLM error when I try to enroll a learner in a course
User-Defined Exception in Package ota_delegate_booking_swi Procedure create_delegate_booking
Does anyone know what this error means or know where i can look to find the problem?I had the same problem. Il run the api OTA_DELEGATE_BOOKING_API. you can catch your error.
In my case it was sommething like this
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "APPS_AOL93.OTA_LRNR_ENROLL_UNENROLL_WF", line 334
ORA-01654: unable to extend index AOL93.WF_ITEM_ATTRIBUTE_VALUES_PK by 64
in tablespace FINIDX
ORA-06512: at "APPS_AOL93.OTA_DELEGATE_BOOKING_API", line 866
ORA-06512: at line 16
A tablespace problem. If this, contact your DBA. -
Error in Librarie oracle.adf.management
Hi all,
I installed JDeveloper version 11.1.1.5.0 along with the correct WebCenter extensions (http://www.oracle.com/ocom/groups/public/@otn/documents/webcontent/156082.xml).
Everytime i open the JDeveloper i got the following error on extesions tabs:
oracle.adf.management
-> Error: libraries in namespace http://xmlns.oracle.com/jdeveloper/1013/jdev-libraries is not a recognized hook.
When i try to run a simple project i got a java.lang.nullpointerException on ADF
-> at oracle.adf.model.binding.DCBindingContainerReference.getDef(DCBindingContainerReference.java:111)
Can those errors be related? How do i resolve this?
Regards,
João LoureiroI have the same problem during compile project this err occur.
I think that those err depend each other because when i log in in my app NullPointer Excep raise. -
Error when upgrading Oracle Identity Manager 9.1.0.1 to OIM 9.1.0.2
Hello friends,
I upgraded Oracle Identity Manager 9.1.0.1 to Oracle Identity Manager 9.1.0.2,after the running the command to apply the patch:
OIM_HOME/xellerate/setup/patch_weblogic.cmd/sh WEBLOGIC_ADMIN_PASSWORD OIM_DB_USER_PASSWORD
I get the error:
[wldeploy] [BasicOperation.execute():445] : Initiating deploy operation for app, Xellerate, on targets:
[wldeploy] [BasicOperation.execute():447] : AdminServer
[wldeploy] Task 2 initiated: [Deployer:149026]deploy application Xellerate on AdminServer.
[wldeploy] dumping Exception stack
[wldeploy] Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
[wldeploy] Target state: deploy failed on Server AdminServer
[wldeploy]
[wldeploy]
[wldeploy] There are 2 nested errors:
[wldeploy]
[wldeploy] weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
[wldeploy] and
[wldeploy]
[wldeploy] weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
[wldeploy] Target Assignments:
[wldeploy] + Xellerate AdminServer
[wldeploy] weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
[wldeploy] Target state: deploy failed on Server AdminServer
[wldeploy]
[wldeploy]
[wldeploy] There are 2 nested errors:
[wldeploy]
[wldeploy] weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
[wldeploy] and
[wldeploy]
[wldeploy] weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
[wldeploy] [ServerConnectionImpl.close():332] : Closing DM connection
[wldeploy] [ServerConnectionImpl.close():352] : Unregistered all listeners
[wldeploy] [ServerConnectionImpl.closeJMX():372] : Closed JMX connection
[wldeploy] [ServerConnectionImpl.closeJMX():384] : Closed Runtime JMX connection
[wldeploy] [ServerConnectionImpl.closeJMX():396] : Closed Edit JMX connection
[ant] Exiting C:\oracle\xellerate\setup\weblogic-setup.xml.
BUILD FAILED
C:\oracle\xellerate\Setup\setup.xml:448: The following error occurred while executing this line:
C:\oracle\xellerate\setup\weblogic-setup.xml:310: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
Target state: deploy failed on Server AdminServer
There are 2 nested errors:
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
and
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
Caused by: C:\oracle\xellerate\setup\weblogic-setup.xml:310: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
Target state: deploy failed on Server AdminServer
There are 2 nested errors:
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
and
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
Caused by: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
Target state: deploy failed on Server AdminServer
There are 2 nested errors:
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
and
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
Caused by: weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
Target state: deploy failed on Server AdminServer
There are 2 nested errors:
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
and
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
--- Nested Exception ---
C:\oracle\xellerate\setup\weblogic-setup.xml:310: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
Target state: deploy failed on Server AdminServer
There are 2 nested errors:
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
and
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
Caused by: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
Target state: deploy failed on Server AdminServer
There are 2 nested errors:
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
and
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
Caused by: weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
Target state: deploy failed on Server AdminServer
There are 2 nested errors:
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
and
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
--- Nested Exception ---
weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
Target state: deploy failed on Server AdminServer
There are 2 nested errors:
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
and
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
Caused by: weblogic.deploy.api.tools.deployer.DeployerException: Task 2 failed: [Deployer:149026]deploy application Xellerate on AdminServer.
Target state: deploy failed on Server AdminServer
There are 2 nested errors:
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the remote interface either does not exist in the bean class, or it is not a public method. Each method in the remote interface must have a corresponding public method in the bean class.
and
weblogic.ejb.container.compliance.ComplianceException: In EJB tcGroupOperations, method getMemberGroups(long,int,int,java.lang.String,boolean) defined in the local interface either does not exist in the bean class, or it is not a public method. Each method in the local interface must have a corresponding public method in the bean class.
Total time: 4 minutes 35 seconds
How do I deal with this question?
Thanks.This error generally occur if your server is up and you are running patch for upgrade, and its very common error.
follow the troubleshoot step and get it done.
page 36
Troubleshooting the Application of the Patch on Oracle WebLogic Server
http://docs.oracle.com/cd/E14899_01/doc.9102/e14764.pdf -
Error while creating data source using Oracle Enterprise Manager 10g
Hi,
I have deployed my web application developed on OC4J 9.0.4 stand alone (Win2K) to an integrated OC4J version(Solaris) using Oracle Enterprise Manager 10g.
However, I get an error when I try to create a data source.
The data source I want to create would have the following parameters (as seen in data-sources.xml on the stand alone version):
<data-source
class="com.evermind.sql.DriverManagerDataSource"
name="TestDS"
location="jdbc/OracleCoreDS"
xa-location="jdbc/xa/OracleXADS"
ejb-location="jdbc/TestDS"
connection-driver="oracle.jdbc.driver.OracleDriver"
url="jdbc:oracle:thin:@hostName:1521:test"
username="user"
password="password"
min-connections="5"
max-connections="20"
inactivity-timeout="30"
/>
When I entered the above data on the Enterprise Manager Data Sources page, I got the following error:
quote:
Error saving Data Source Properties. - Entity et="system";ei="0",et="application";ei="48",et="data-sources";ei="167":child:data-sourcechild key:location:jdbc/OracleCoreDS; class:com.evermind.sql.DriverManagerDataSource; already exists in the repository. Resolution: Please check the code base.
unquote:
Could somebody tell me what I'm doing wrong ?
I tried to manually edit the data-sources.xml file but the data source didn't show up on the Enterprise Manager.
I'm using a new OC4J instance (on the Solaris machine) for my applications. Is the data source error related to this?
Any help will be greatly appreciated.
Thanks,
ShyamThanks for your reply , Steve.
I noticed that there is a default datasouce on the EM with the following parameters:
<data-source
class="com.evermind.sql.DriverManagerDataSource"
name="OracleDS"
location="jdbc/OracleCoreDS"
xa-location="jdbc/xa/OracleXADS"
ejb-location="jdbc/OracleDS"
connection-driver="oracle.jdbc.driver.OracleDriver"
username="scott"
password="->pwForScott"
url="jdbc:oracle:thin:@localhost:1521:oracle"
inactivity-timeout="30"
/>
The location and xa-location attributes that I use for my "test" data source are the same as the default one. So, could this be the issue?
What should be the values for location and xa-location attributes from my "test" data source?
Any help will be greatly appreciated.
Thanks,
Shyam -
Error while installing Oracle identity Management Suite 11.1.1.2.0.
Hi,
I am installing Oracle Identity Federation in that i am getting following issue while configuring the tools in Oracle Identity Management Suite 11.1.1.2.0.
"Error Starting Managed Server wls_oif1.
Cause:
An internal error has occured : Managed Server didn't start in RUNNING mode"
Can anyone please help me to solve this issue.
-SriHi,
The pre-req is that it should be minimum 2GB RAM.
Also please try starting the server manually and stop the server and then Retry in the install wizard.
Thanks,
Mahendra. -
Error while installing OFM 11g - Oracle Identity management suite 11g
Hi,
I am getting following error while installing Oracle Identity management suite 11g (Oracle Internet Directory & Oracle Virtual Directory) on Red Hat Linux 5.0.
"Error in invoking target 'client_sharedlib' of makefile '/apps/idm/Oracle/OracleHome/Oracle_Home/rdbms/lib/ins_rdbms.mk"
the same error is repeating for others also i.e. 'all', 'install" etc.
Can you advice me how to overcome this?
Regards
ChintaHi Chinta,
Pl. check for all gcc and glibc OS packages compatibility with your your OS. This will solve your problem.
Also check that you are not installing a 32 bit IM software on a 64 bit machine or viceversa.
regards,
Sailesh -
Error while installing oracle identity manager
Im using windows installer. I get error below when installing Oracle Identity Manager, any idea to solve this?
Following Error occured during schema creation connected
ERROR loading database script C:\oracle identity manager\OIM9.0.1.1\installServer\Xellerate/db/oracle/xell.sql!
Please contact your DBA! ORA-06550: line 1,
column 7: PLS-00905: object KOD.PIN_OBJ is invalid ORA-06550: line 1,
column 7: PL/SQL: Statement ignored [12/13/06 11:36 AM]
------------------------------------------------------------------------------Hi,
I got the same error:
Following Error occurred during schema creation connectedError loading database scriptD:\appl\OIM_902_RC\OIM_902_RC\installServer\Xellerate/db/oracle/xell.sqlPlease contact your DBA!ORA-06550: line 1, column 7: PLS-00905: object VIM_ADMIN.PIN_OBJ is invalid ORA-06550: line 1, column 7: PL/SQL: Statement ignored [12/8/06 5:57 PM]
But I could fix it by dropping the schema and recreate it by only executing the prepare_xl_db.sh script as dba user on database server:
1. Copy the scripts prepare_xl_db.sh and xell_db_prepare.sql from the distribution CD/Directory to a directory on the machine hosting the database where there is (as the account user performing this task) write permission.
2. Run the prepare_xl_db.sh script by entering the following command:
./prepare_xl_db.sh
3. Provide information appropriate for the database and host machine when the script prompts for the following items:
• The location of the Oracle home (ORACLE_HOME)
• The name of the database (ORACLE_SID)
• The name of the Oracle Identity Manager database user to be created
• The password for the Oracle Identity Manager database user
• The name of the tablespace to be created for storing Oracle Identity Manager data
• The directory in which to store the data file for the Oracle Identity Manager tablespace
• The name of the data file ( no need to append the .dbf extension)
• The name of the temporary tablespace
4. Check the prepare_xell_db.lst log file located in the directory where the xell_db_prepare script was run from to see execution status and additional information. -
Error when installing Oracle Identity Manager 9.1.0.1
Hello friends,
I installed Oracle Identity Manager 9.1.0.2 Oracle Weblogic Server on a cluster, at the time of treaties authenticated in the web console of Oracle Identity Manager, I get the following message:
A system error was encountered.
View the full log here
http://pastebin.com/ucN1LHP4
BUILD FAILED
/opt/oim/xellerate/setup/setup.xml:447: The following error occurred while executing this line:
/opt/oim/xellerate/setup/weblogic-setup.xml:318: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 3 failed: [Deployer:149026]deploy application Nexaweb on oimCluster.
Target state: deploy failed on Cluster oimCluster
javax.servlet.ServletException: [HTTP:101249][ServletContext@59809215[app:Nexaweb module:/Nexaweb path:/Nexaweb spec-version:null]]: Servlet class com.nexaweb.loader.ClientLoaderServlet for servlet ClientClassServlet could not be loaded because the requested class was not found in the classpath .
java.lang.ClassNotFoundException: com.nexaweb.loader.ClientLoaderServlet.
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:551)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
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:52)
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:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:508)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:418)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
at org.apache.tools.ant.Project.executeTarget(Project.java:1306)
at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
at org.apache.tools.ant.Main.runBuild(Main.java:758)
at org.apache.tools.ant.Main.startAnt(Main.java:217)
at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
Caused by: /opt/oim/xellerate/setup/weblogic-setup.xml:318: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 3 failed: [Deployer:149026]deploy application Nexaweb on oimCluster.
Target state: deploy failed on Cluster oimCluster
javax.servlet.ServletException: [HTTP:101249][ServletContext@59809215[app:Nexaweb module:/Nexaweb path:/Nexaweb spec-version:null]]: Servlet class com.nexaweb.loader.ClientLoaderServlet for servlet ClientClassServlet could not be loaded because the requested class was not found in the classpath .
java.lang.ClassNotFoundException: com.nexaweb.loader.ClientLoaderServlet.
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:551)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
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:52)
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:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.java:357)
at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
at sun.reflect.GeneratedMethodAccessor167.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
at org.apache.tools.ant.Task.perform(Task.java:348)
at org.apache.tools.ant.Target.execute(Target.java:357)
at org.apache.tools.ant.Target.performTasks(Target.java:385)
at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1337)
at org.apache.tools.ant.helper.SingleCheckExecutor.executeTargets(SingleCheckExecutor.java:38)
at org.apache.tools.ant.Project.executeTargets(Project.java:1189)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:416)
... 16 more
Caused by: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Task 3 failed: [Deployer:149026]deploy application Nexaweb on oimCluster.
Target state: deploy failed on Cluster oimCluster
javax.servlet.ServletException: [HTTP:101249][ServletContext@59809215[app:Nexaweb module:/Nexaweb path:/Nexaweb spec-version:null]]: Servlet class com.nexaweb.loader.ClientLoaderServlet for servlet ClientClassServlet could not be loaded because the requested class was not found in the classpath .
java.lang.ClassNotFoundException: com.nexaweb.loader.ClientLoaderServlet.
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:551)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
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:52)
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:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
at weblogic.Deployer.run(Deployer.java:72)
at weblogic.Deployer.mainWithExceptions(Deployer.java:62)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy.java:419)
at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.java:349)
... 28 more
Caused by: weblogic.deploy.api.tools.deployer.DeployerException: Task 3 failed: [Deployer:149026]deploy application Nexaweb on oimCluster.
Target state: deploy failed on Cluster oimCluster
javax.servlet.ServletException: [HTTP:101249][ServletContext@59809215[app:Nexaweb module:/Nexaweb path:/Nexaweb spec-version:null]]: Servlet class com.nexaweb.loader.ClientLoaderServlet for servlet ClientClassServlet could not be loaded because the requested class was not found in the classpath .
java.lang.ClassNotFoundException: com.nexaweb.loader.ClientLoaderServlet.
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:551)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1985)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1959)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1878)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3153)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1508)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:482)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
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:52)
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:636)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:205)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:58)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:569)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:323)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:844)
at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1253)
at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:440)
at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:163)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
at weblogic.deploy.api.tools.deployer.Jsr88Operation.report(Jsr88Operation.java:542)
at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:140)
at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
at weblogic.utils.compiler.Tool.run(Tool.java:158)
at weblogic.utils.compiler.Tool.run(Tool.java:115)
at weblogic.Deployer.run(Deployer.java:70)
... 35 more
As I can solve this problem, not to reinstall everything again
thanksNot sure if I understand your issue correctly. Your deployment failed during the installation and you have started the servers and trying to login?
When installing OIM in a clustered WLS domain, the docs specify various cluster configurations needed to be completed in the WLS Admin Console before running the OIM installer. These steps DO NOT include starting up of the first managed server. In fact, if you start up the managed server then you may very well run into deployment issues after the OIM application is built. Instead, when installing OIM, the installer detects that not all nodes are on-line and so will queue the deployment for later. Deployment then takes place in later steps when you are instructed to restart the app server and start managed nodes.
Thus was your managed server running when you were doing the installation? That has caused the issue. I would suggest to dump this domain (save the .xldatabasekey) if you don't wanna to dump the database part and start the installation again BUT don't start the managed server while doing the installation.
HTH,
BB -
Error on installing Oracle Identity Manager 9.1.0.1 in WebLogic Server 11g
Hello friends.
Can you help solve this case:
I installed Oracle 9.1.0.1 on Oracle Identity Manager Weblogic Server 11g, completing the installation with the following errors: attach the log so I can guide the solution.
link of the complete log
http://textbin.com/1c824
Part of the log**************************************
With the Partitioning, OLAP, Data Mining and Real Application Testing options".>
####<Sep 30, 2011 4:23:04 PM PET> <Info> <JDBC> <idm9> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1317417784538> <BEA-001517> <Connection Pool "xlXADS" using Driver: "Oracle JDBC driver", Version: "11.2.0.2.0".>
####<Sep 30, 2011 4:23:18 PM PET> <Info> <Common> <idm9> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1317417798143> <BEA-000628> <Created "30" resources for pool "xlXADS", out of which "30" are available and "0" are unavailable.>
####<Sep 30, 2011 4:23:18 PM PET> <Info> <JDBC> <idm9> <AdminServer> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1317417798147> <BEA-001124> <Created Connection Pool named xlXADS.>
####<Sep 30, 2011 4:23:24 PM PET> <Error> <Store> <idm9> <AdminServer> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1317417804279> <BEA-280061> <The persistent store "AdminServer_OIM_JDBCSTORE" could not be deployed: weblogic.store.PersistentStoreException: Can't find JDBC DataSource jdbc/xlDS: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
weblogic.store.PersistentStoreException: Can't find JDBC DataSource jdbc/xlDS: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:107)
at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:186)
at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:164)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:59)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:240)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:102)
at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:186)
at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:164)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:59)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:187)
at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:491)
at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:137)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<Sep 30, 2011 4:23:24 PM PET> <Warning> <Management> <idm9> <AdminServer> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1317417804321> <BEA-141197> <The deployment of AdminServer_OIM_JDBCSTORE failed.
weblogic.management.DeploymentException:
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:62)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
at javax.naming.InitialContext.lookup(InitialContext.java:392)
at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:102)
at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:186)
at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:164)
at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:59)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:187)
at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:491)
at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:137)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<Sep 30, 2011 4:23:24 PM PET> <Error> <JMS> <idm9> <AdminServer> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1317417804381> <BEA-040123> <Failed to start JMS Server "AdminServer_OIM_JMSSERVER" due to weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist.
weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist
at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:313)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:200)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:240)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
####<Sep 30, 2011 4:23:24 PM PET> <Warning> <Management> <idm9> <AdminServer> <[ACTIVE] ExecuteThread: '23' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1317417804385> <BEA-141197> <The deployment of AdminServer_OIM_JMSSERVER failed.
weblogic.management.DeploymentException: Internalrror activating the JMS Server AdminServer_OIM_JMSSERVER: weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:215)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:239)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
Caused By: weblogic.management.DeploymentException: The persistent store "AdminServer_OIM_JDBCSTORE" does not exist
at weblogic.jms.deployer.BEAdminHandler.findPersistentStore(BEAdminHandler.java:313)
at weblogic.jms.deployer.BEAdminHandler.activate(BEAdminHandler.java:200)
at weblogic.management.utils.GenericManagedService.activateDeployment(GenericManagedService.java:240)
at weblogic.management.utils.GenericServiceManager.activateDeployment(GenericServiceManager.java:131)
at weblogic.management.internal.DeploymentHandlerHome.invokeHandlers(DeploymentHandlerHome.java:632)
at weblogic.management.internal.DeploymentHandlerHome.access$400(DeploymentHandlerHome.java:67)
at weblogic.management.internal.DeploymentHandlerHome$1.activateUpdate(DeploymentHandlerHome.java:188)
at weblogic.descriptor.internal.DescriptorImpl$Update.activate(DescriptorImpl.java:492)
at weblogic.descriptor.internal.DescriptorImpl.activateUpdate(DescriptorImpl.java:230)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService$1.run(RuntimeAccessDeploymentReceiverService.java:362)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.management.provider.internal.RuntimeAccessDeploymentReceiverService.commit(RuntimeAccessDeploymentReceiverService.java:357)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.commit(DeploymentReceiverCallbackDeliverer.java:64)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.callDeploymentReceivers(AwaitingCommit.java:241)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.handleCommit(AwaitingCommit.java:139)
at weblogic.deploy.service.internal.statemachines.targetserver.AwaitingCommit.receivedCommit(AwaitingCommit.java:44)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver.receiveRequestCommitMsg(CommonMessageReceiver.java:517)
at weblogic.deploy.service.internal.transport.CommonMessageReceiver$3.run(CommonMessageReceiver.java:799)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
ThanksHi Kevin,
Make your suggestion, delete the domain and reinstall Oracle Identity Manager, the result was the same error, this happens when I start the xlStartServer.sh
Exception in thread "QuartzWorkerThread-2" java.lang.OutOfMemoryError: PermGen space
at java.lang.reflect.Proxy.defineClass0(Native Method)
at java.lang.reflect.Proxy.getProxyClass(Proxy.java:504)
at java.lang.reflect.Proxy.newProxyInstance(Proxy.java:581)
at com.thortech.xl.dataaccess.tcDataBaseClient.bindToInstance(Unknown Source)
at com.thortech.xl.dataaccess.tcDataBaseClient.<init>(Unknown Source)
at com.thortech.xl.server.tcDataBaseClient.<init>(Unknown Source)
at com.thortech.xl.client.dataobj.tcDataBaseClient.<init>(Unknown Source)
at com.thortech.xl.scheduler.core.quartz.QuartzWrapper$TaskExecutionAction.run(Unknown Source)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.security.Security.runAs(Security.java:41)
at Thor.API.Security.LoginHandler.weblogicLoginSession.runAs(Unknown Source)
at com.thortech.xl.scheduler.core.quartz.QuartzWrapper.execute(Unknown Source)
at org.quartz.core.JobRunShell.run(JobRunShell.java:178)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:477)
CJava HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
^CJava HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
Exception in thread "QuartzScheduler_NON_CLUSTERED_MisfireHandler" java.lang.OutOfMemoryError: PermGen space
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
java.lang.OutOfMemoryError: PermGen space
^CJava HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
Exception in thread "[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'" java.lang.OutOfMemoryError: PermGen space
java.lang.OutOfMemoryError: PermGen space
Java HotSpot(TM) 64-Bit Server VM warning: Exception java.lang.OutOfMemoryError occurred dispatching signal SIGINT to handler- the VM may need to be forcibly terminated
Thanks
Edited by: JLK on Oct 2, 2011 11:35 PM
Edited by: JLK on Oct 2, 2011 11:37 PM
Maybe you are looking for
-
DELETING INBOX MAIL MESSAGE PROBLEM
I am getting a dialogue pop up box that tells me that the message hat I am trying to move to the trash can't be copied to "messages" because an item with the same name already exists. I completely emptied my trash and that didn't help. Needlwaa to sa
-
Security issue in Crystal Report 2008 for SAP B1
Hi Friends, I want to hide the Query which is used in my report from the end user,I don't want they can see and edit the report after exporting from sap b1. Please help.....its urgent Thanks. Andy
-
G4, 400Mhz, OS X, (10.4.6) Disk insertion not readable messsage.
I've installed an internal secondary hard drive, 120GB, Barracuda 7200 RPM to my G4 which contains a 10GB hard drive as master drive. I'm trying to install a second hard drive as a slave but I keep getting a Disk insertion not readable message. The c
-
Every time I save a document it freezes the app. Why?
Every time I save a document in Pages it freezes the app and I have to "force quit" to exit the app. Why?
-
I have a JSP within an application that I want the user to enter the weblogic system username/password before display (this page allows for application configuration for the system admin). I want to setup an ACL on this JSP, please offer help (I'm ne