Connecting managed server to cluster's administration server
Hello,
I have a problem when trying to connect managed server to cluster's
administration server.
When starting the managed server I get a security exception:
[javax.naming.AuthenticationException [Root exception is
java.lang.SecurityException: Administrators must log in over admin port with
admin protocol.]]
weblogic.management.configuration.ConfigurationException: admin URL:
t3://192.168.14.15:7001 - with nested exception:
[javax.naming.AuthenticationException [Root exception is
java.lang.SecurityException: Administrators must log in over admin port with
admin protocol.]]
at
weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:893)
at weblogic.management.Admin.start(Admin.java:303)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
I get the same result when testing the connection setup with
java weblogic.Admin -url 192.168.14.15:7001 -username system -password xyz
CONNECT 1
Background for this problem:
I'm trying to evaluate WLS6.0 clustering for my RMI services. I have two
machines setup with my test domain (DEdomain) and one cluster (DECluster)
within it.
In administration server (machine A) I defined two servers to be run in
machine A and machine B:
DEserver2 in machine B (to be started as managed server) and DEserver3
in machine A
I'm going to bind a same service into these above servers of my DECluster.
In machine B's startManagedWeblogic.sh I have:
java -ms64m -mx64m -classpath
$CLASSPATH -Dweblogic.Domain=DEdomain -Dweblogic.Name=$SERVER_NAME -Dweblogi
c.management.server=$ADMIN_URL -Djava.security.policy==$WL_HOME/lib/weblogic
.policy -Dweblogic.management.username=system -Dweblogic.management.password
=$WLS_PW weblogic.Server
In machine A I have administration server DEserver1 listening port 7001.
And for the domain and cluster building I followed all relevant e-docs
manual pages. It's still somewhat blurry what kind of preparations I have to
make in managed server side to join the domain; for example do I have to
have identical domain directory structure within machine B and do I have to
configure something with admin console or is everything handled by
connecting to the administation server and reading the domain's config.xml
from machine A.
I'm sure I have missed some fundamental idea for building clustered services
and would greatly appreciate if someone had any good tips or ideas.
Best regards,
Harri
Hi Kumar,
and thank you. That fixed my problem
Best regards,
Harri
"Kumar Allamraju" <[email protected]> wrote in message
news:[email protected]...
It appears you had set the administration port & listen port on the admin
server.
Logging onto admin server via admin port is broken currently. I wouldsuggest
you to set only listen port
and see how that goes.
Kumar
"Harri Töhönen" wrote:
Hello,
I have a problem when trying to connect managed server to cluster's
administration server.
When starting the managed server I get a security exception:
[javax.naming.AuthenticationException [Root exception is
java.lang.SecurityException: Administrators must log in over admin portwith> > admin protocol.]
weblogic.management.configuration.ConfigurationException: admin URL:
t3://192.168.14.15:7001 - with nested exception:
[javax.naming.AuthenticationException [Root exception is
java.lang.SecurityException: Administrators must log in over admin portwith> > admin protocol.]
at
weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:893)
at weblogic.management.Admin.start(Admin.java:303)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
I get the same result when testing the connection setup with
java weblogic.Admin -url 192.168.14.15:7001 -username system -password
xyz
CONNECT 1
Background for this problem:
I'm trying to evaluate WLS6.0 clustering for my RMI services. I have two
machines setup with my test domain (DEdomain) and one cluster(DECluster)
within it.
In administration server (machine A) I defined two servers to be run in
machine A and machine B:
DEserver2 in machine B (to be started as managed server) andDEserver3
in machine A
I'm going to bind a same service into these above servers of myDECluster.
>>
In machine B's startManagedWeblogic.sh I have:
java -ms64m -mx64m -classpath
$CLASSPATH -Dweblogic.Domain=DEdomain -Dweblogic.Name=$SERVER_NAME -Dweblogi
>>
c.management.server=$ADMIN_URL -Djava.security.policy==$WL_HOME/lib/weblogic
>>
.policy -Dweblogic.management.username=system -Dweblogic.management.password
=$WLS_PW weblogic.Server
In machine A I have administration server DEserver1 listening port 7001.
And for the domain and cluster building I followed all relevant e-docs
manual pages. It's still somewhat blurry what kind of preparations Ihave to
make in managed server side to join the domain; for example do I have to
have identical domain directory structure within machine B and do I haveto
configure something with admin console or is everything handled by
connecting to the administation server and reading the domain'sconfig.xml
from machine A.
I'm sure I have missed some fundamental idea for building clusteredservices
and would greatly appreciate if someone had any good tips or ideas.
Best regards,
Harri
Similar Messages
-
Web Proxy Server 3.6 with Administration Server using SSL connection
In your manual: Administrator�s Guide Sun� ONE Web Proxy Server Version 3.6 SP3 for UNIX you wrote:
You should also make the administrative connection a mandatory SSL connection
Instead of using http://servername:port_number
I need to use:
https://servername:port_number
How can I do that?
Thanx
Gian MarioHI
To enable https for the admin,
Create a certifcate for the proxy admin
Next, From 'Admin Preferences', click on 'Encryption on/off'
From the 'Encryption on/off'; screen that appears, click on the 'on' radio button. Select the certficate from the alias list and click on OK to enable encryption for the cerficate you have installed for your admin server.
Now restart you admin server.
You wil now be able to connect to your admin using https
Thanks
Nagendra HK -
Hi,
When I Adding a server from the server list to the cluster , and
click 'apply' , the weblogic server will be halted. Why could it
happen and How can I solve this problem?
Furthermore,I try to shutdown the server by using the command script
- java weblogic.Admin -url http://localhost:port SHUTDOWN -username
username -password password ( e.g. java weblogic.Admin -url http://999.99.99.99:7001
SHUTDOWN -username system -password weblogic ), there is an error
message "Exception in thread 'main' java.land.NoclassDefFoundError:
weblogic/Admin" . Why?
Chris
Your CLASSPATH must include $WL_HOME/classes to startup as:
java weblogic.Admin t3://localhost:<port> SHUTDOWN <USERNAME> <PASSWORD>
Note here protocol is t3. Brian
"Joe E. Schwarz" <[email protected]> wrote:
>
>Chris,
>You gave probably forgotten to set your CLASSPATH to,
>for example
>on NT, C:\bea\wlserver6.0\lib\weblogic.jar.
>Joe
>
>"Chris" <[email protected]> wrote:
>>
>>Hi,
>>When I Adding a server from the server list to the cluster
>>, and
>>click 'apply' , the weblogic server will be halted. Why
>>could it
>>happen and How can I solve this problem?
>>Furthermore,I try to shutdown the server by using the
>>command script
>>- java weblogic.Admin -url http://localhost:port SHUTDOWN
>>-username
>>username -password password ( e.g. java weblogic.Admin
>>-url http://999.99.99.99:7001
>>SHUTDOWN -username system -password weblogic ), there
>>is an error
>>message "Exception in thread 'main' java.land.NoclassDefFoundError:
>>weblogic/Admin" . Why?
>>
>>
>>Chris
>
-
Problem with Connection Manager. Can't change connection string / Server name
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin-top:0cm;margin-right:0cm;margin-bottom:10.0pt;margin-left:0cm;line-height:115%;font-size:11.0pt;font-family:'Calibri','sans-serif';}
.MsoChpDefault
{font-size:10.0pt;}
.MsoPapDefault
{line-height:115%;}
@page Section1
{size:612.0pt 792.0pt;margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.Section1
{page:Section1;}
Hi,
I have copied a number of SSID packages from a live server to my test server and am trying to get them up and running but I have a problem with the connection. The only thing that is different is the server name. I decided to keep the same connection in the connection manager as it is referenced in a dtsConfig file. I changed the dtsConfig file to reference the new servername [Data Source= new test server name]. I also check my paths and they are pointing to the correct config locations etc.
I found this post which was similar to my problem but I still get problems with the connection
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1319961&SiteID=1
I updated the connection by changing the server name in the actual connection. I did this from the data flow tab in the Connection Managers sections (MS Visual Studio). Right clicked - Edit - changed the name of the server name to my test server and selected the database. Test connection was fine, and saved this.
Once I saved this, the connection string changed to my current test server in the properties of the connection. However when I run the package I get the following error:
Error: 0xC0202009 at ReportsImport, Connection manager "myconnectionstring": SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Login timeout expired".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.".
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Named Pipes Provider: Could not open a connection to SQL Server [53]. ".
Error: 0xC020801C at Myprocess import from file, BuyAtReportsImport [79]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "myconnectionstring" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
Error: 0xC0047017 at Myprocess import from file, DTS.Pipeline: component "ReportsImport" (79) failed validation and returned error code 0xC020801C.
Error: 0xC004700C at Myprocess import from file, DTS.Pipeline: One or more component failed validation.
Error: 0xC0024107 at Myprocess import from file: There were errors during task validation.
So even if I change the existing connection properties and save and Build my package again, my connection properties (connectionstring, servername etc) all revert back to its original data source when I re-open the package. Simply it does not seem to be saving the connection properties i put in.
What am I doing wrong or how can I change the existing connection manager to look at the new server. The database is the same and I have full admin privilege on the server.
I don't want to recreate my packages as there are alot and they are not simple.
After changing the connection properties, saving and reloading I get a connection error. But this is because it is not retaining the new connection manger setting i entered.
Incidentally - I created a new SSID to perform a simple connection and write to the the server and it was OK so there is no problem with actually seeing the my test server.
Thanks in advanceYes, the package is in visual studio and I have executed it. There are no errors but in the output i have the error message about my connection. My dtsConfig file is added to the project in the 'Package Configuration Organizer' and path and files are correct. This is the output error:
Error: 0xC020801C at xx import from file, xxReportsImport [79]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "myconnectionname" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
I will try and run it using dtexec.exe. if I have two config files do i use
dtsexec.exe /f <packagename> /conf <configfile> /conf <secondconfigfile> -
Administration Server in Domains
I have a domain with one Administration Server and some Managed Servers and I want
to controll the state of each Managed Server (running or not) from outside.
Is it possible to manage each Managed Server also if the Administration Server
is not active?
Or in this case is it necessary to controll directly each Managed Server state?Hi Deepak,
Unfortunately the server logs do not show any problems, errors or exceptions. The server just hangs and stops responding! It does not seem to crash though, it just hangs... When I point a browser to the URL served by the server, the browser doesn't tell "connection refused"; rather it shows a white screen as though it is waiting for reply but never gets it. Logs do not show any activity on the server side (neither access.log nor server log).
I understand this is a subtle situation where you need more details to figure out what's going on. Please ask me more specific questions and I will gladly provide you with answers.
Maybe there are more files I need to look in, or maybe there are some system/JVM settings you are interested in.
Sincerely,
Sergei Batiuk. -
Prepositioning files on a Server 2008 Cluster
I recently replaced a Server 2003 cluster with a server 2008 cluster. After the migration my prepostioning stopped functioning. The virtual servers are named the same and all the credentials, etc are the same. If I go into one of the preposition definitions and click browse I get a could not access cifs://<servername>. If I point to any of the other servers I am able to browse. Doesn't matter if they are server 2003 or 2008. The clustered servers are domain controllers. The version is 4.1.1c
Could you elaborate on this,as I am having the same issues? Our prepositioning works on the 2003 boxes but not the new 2008 ones.
Where abouts did you turn off the server signing .My serevr team say they have done this,but i would like to check myself.Is there anything else you changed? I can browse the files and select them fine,its just that once the schedule has started,no files get copied.
thanks,
Nick -
NET8 CONNECTION MANAGER 설치와 설정방법
제품 : SQL*NET
작성날짜 : 2003-01-15
NET8 CONNECTION MANAGER 설치와 설정방법
=======================================
Purpose
Oracle Connection Manager(v3.0.x)의 설치와 설정 방법을
알아 보고 시작시켜 봅니다.
V3.0.x은 Oracle8 Enterprise Edition에 같이 들어 있으며
Oracle8의 일부는 아닙니다.
1. 설치 방법
2. 설정 방법
3. 시작 하기 (Windows NT)
Explanation
1. 설치 방법
다음 세가지의 실행 파일이 설치 됩니다.
CMGW, CMADMIN, CMCTL (Unix 와 VMS)
CMGW80, CMADM80, CMCTL80(desktop Oracle8에서)
CMGW, CMADMIN, CMCTL(desktop Oracle8i에서)
CMGW/CMGW80
이 것은 Connection Manager의 hub와 같은 역할을 하는
gateway process입니다.
CMGW의 기능은 다음과 같습니다.
- CMADMIN를 등록합니다.
- SQL*Net 2.x와 NET 8.x에서 오는 접속 요청에 대해 대기합니다.
기본적으로 1610 port를 사용합니다.
- NET 8.x listeners에 접속 요청을 발생 시킵니다.
- client와 server사이의 data를 전달합니다.
- CMCTL/CMCTL80에 의해 발생되는 요청에 응답합니다.
CMADMIN/CMADM80
Connection Manager의 모든 관리적인 문제들을 처리하는 multi-threaded
process입니다.
SQL*Net 2.x 와 NET 8.x clients들을 위해
Oracle Names Server에 있는 주소정보를 유지하는 기능을 합니다.
- CMGW/CMGW80 등록 작업을 합니다.
- local Oracle Names Server를 찾습니다.
- 하나이상의 db instance를 서비스하는 모든 listener들을 관리합니다.
- CMGW/CMGW80 와 listener에 대한 주소 정보를 등록합니다.
- 네트워크와 Names Server의 수정된 정보를 감시합니다.
- CMCTL/CMCTL80의 요청에 응답합니다.
CMGW, CMADMIN/CMGW80, 와 CMADM80 의 서로간의 정보전달은 IPC를 통해
이루어 집니다.
CMAN은 주기적으로 Names Server의 바뀐 정보를 cache에 반영합니다.
CMCTL/CMCTL80
CMADM/CMADM80 와 CMGW/CMGW80 를 관리하는 일을 합니다.
현재 제공되는 명령은 start, stop, status, 그리고 version 입니다.
CMCTL START [CMAN | CM | ADM]
이 명령은 Connection Manager 또는 그 구성요소를 시작 시킵니다.
- 인자가 없는 경우 또는 CMAN을 준 경우는 gateway 와
administration process를 시작시킵니다.
- CM 을 주면 gateway process 만 시작됩니다.
- ADM 을 주면 administration process 만 시작됩니다.
CMCTL STOP [CM]
Connection Manager process들을 중지 시킵니다.
- 인자가 없는 경우 또는 CM 을 준 경우 gateway 와
administration process 모두를 중지시킵니다.
gateway process가 중단될 경우 administration process는 자동으로
중단됩니다.
현재 진행중인 접속이 있는 경우 CMAN 는 중지될 수 없습니다.
CMCTL STATUS [CMAN | CM | ADM]
이 명령은 Connection Manager의 요소들의 상태를 보여줍니다.
- 인자가 없거나 CMAN이나 CM일 경우 gateway process의 상태를 보여 줍니다.
- ADM은 administration process의 상태를 보여 줍니다.
CMCTL VERSION
이 명령은 control utility의 버젼을 보여 줍니다.
CMGW/CMGW80 와 CMADM/CMADM80의 버젼은 status명령으로 볼 수 있습니다.
2. 설정 방법
client들은 tnsnames.ora 이나 Oracle Names Server 가 필요합니다.
Connection Manager는 cman.ora 가 필요하며 server는 init.ora에 MTS설정이
필요합니다.
client설정
tnsnames.ora파일의 예 입니다.
EXAMPLE=
(DESCRIPTION=
(ADDRESS=
(PROTOCOL=TCP)
(HOST=SERVER.US.ORACLE.COM)
(PORT=1521)
(CONNECT_DATA=
(SID=ORCL)
하나의 protocol로 Connection Manager를 사용하는 tnsnames.ora파일 예입니다.
EXAMPLE_CMAN=
(DESCRIPTION=
(ADDRESS_LIST=
(ADDRESS=
(PROTOCOL=TCP)
(HOST=CMAN.US.ORACLE.COM)
(PORT=1610)
(ADDRESS=
(PROTOCOL=TCP)
(HOST=SERVER.US.ORACLE.COM)
(PORT=1521)
(CONNECT_DATA=
(SID=ORCL)
(SOURCE_ROUTE=YES)
ADDRESS_LIST가 path입니다.
첫번째 주소가 CMAN에 접속하는 정보이고, 두번째 주소가 서버에
접속할때 CMAN에 의해 사용되는 주소입니다.
필요하다면 ADDRESS_LIST 안에 여러개의 CMAN 의 주소를 설정할
수 있습니다. CMAN은 기본적으로 라우터처럼 동작합니다.
접속 요청을 다음 hop으로 지정합니다.
여러개의 protocol로 Connection Manager를 사용하는
tnsnames.ora파일 예입니다.
EXAMPLE_CMAN=
(DESCRIPTION=
(ADDRESS_LIST=
(ADDRESS=
(PROTOCOL=SPX)
(SERVICE=CMAN)
(ADDRESS=
(PROTOCOL=TCP)
(HOST=SERVER.US.ORACLE.COM)
(PORT=1521)
(CONNECT_DATA=
(SID=ORCL)
(SOURCE_ROUTE=YES)
위의 예에서 CMAN에 접속하기 위해서 client는 SPX를 사용하고
server에 접속하기 위해서 CMAN은 TCP/IP를 사용하게 됩니다.
Oracle7에서 소개된 Oracle Multi-Protocol Interchange (MPI)과
같은 기능을 합니다.
만일 서버까지 가는데 한개 이상의 router가 있는 경우
SQL*Net 2.3에서 소개된 DESCRIPTION_LIST를 사용할 수 있습니다.
다음은 DESCRIPTION_LIST를 사용한 tnsnames.ora 파일의 예 입니다.
EXAMPLE_ROUTES=
(DESCRIPTION_LIST=
(DESCRIPTION=
(ADDRESS_LIST=
(ADDRESS=
(PROTOCOL=TCP)
(HOST=CMAN1.US.ORACLE.COM)
(PORT=1610)
(ADDRESS=
(PROTOCOL=TCP)
(HOST=SERVER.US.ORACLE.COM)
(PORT=1521)
(CONNECT_DATA=
(SID=ORCL)
(SOURCE_ROUTE=YES)
(DESCRIPTION=
(ADDRESS_LIST=
(ADDRESS=
(PROTOCOL=TCP)
(HOST=CMAN2.US.ORACLE.COM)
(PORT=1610)
(ADDRESS=
(PROTOCOL=TCP)
(HOST=SERVER.US.ORACLE.COM)
(PORT=1521)
(CONNECT_DATA=
(SID=ORCL)
(SOURCE_ROUTE=YES)
만일 Oracle Names Server를 사용하면 Connection Manager는 자동으로
CMAN을 위한 주소를 Names Server에 있는 기존의 주소에 추가하게 됩니다.
SQLNET.ORA파일에 다음과 같은 parater를 설정할 수 있습니다.
USE_CMAN = [TRUE | FALSE]
- TRUE 라고 설정하면 CMAN이 무작위로 뽑은 간접적인 경로를 이용해
client를 접속시킵니다. ( 적어도 하나의 CMAN address가 있는
address list)
- TRUE 그리고 description에 간접 경로가 없는 경우에는 무작위로 뽑은
경로가 사용됩니다.
- FALSE 이거나 설정이 안된 경우 무작위로 뽑힌 경로가 사용됩니다.
Connection Manager 설정
CMAN 은 한개의 파일(CMAN.ORA)로 설정된다.
CMAN.ORA 파일은 다음 세개의 부분으로 구성된다.
1) CMAN - Connection Manager를 위한 listening주소를 포함한다.
2) CMAN_PROFILE - CMAN 설정 parameter들을 포함한다.
3) CMAN_RULES - 접속 요청에 대한 필터링에 관련된 규칙을 포함한다.
CMAN=
(ADDRESS_LIST=
(ADDRESS=
(PROTOCOL=SPX)
(SERVICE=CMAN)
(ADDRESS=
(PROTOCOL=TCP)
(HOST=CMAN.US.ORACLE.COM)
(PORT=1610)
이 CMAN의 예에서는 SPX 와 TCP/IP 두개의 주소에서 listening하고 있습니다.
CMAN 은 CMAN이 실행되는 장비에서 oracle이 지원하는 모든 protocol에 대해
listen할 수 있습니다.
CMAN_PROFILE=
(PARAMETER_LIST=
(MAXIMUM_RELAYS=64)
(LOG_LEVEL=0)
(TRACING=YES)
(RELAY_STATISTICS=YES)
(SHOW_TNS_INFO=NO)
(USE_ASYNC_CALL=YES)
(AUTHENTICATION_LEVEL=0)
각 parameter들에 대한 정의 :
MAXIMUM_RELAYS = n
- 허용되는 최대 동시 접속수
- 기본값 8
- 최대값 1024
LOG_LEVEL = n
- CMAN에 의해 수행되는 logging의 level설정
- 기본값 0 ( logging이 안됨 )
- 0에서부터 4까지의 값을 설정할 수 있음
TRACING = [YES | NO]
- YES로 설정하면 CMAN은 파일에 tracing을 한다.
- 기본값 NO
주의: trace파일을 읽기위새허는 Oracle Trace를 사용하면 됩니다.
RELAY_STATISTICS = [YES | NO]
- YES는 I/O활동에 대한 통계정보를 저장하게 합니다.
예를 들어 :
- IN bytes 수
- OUT bytes 수
- IN packets 수
- OUT packets 수
- 기본값 NO
SHOW_TNS_INFO = [YES | NO]
- Yes로 설정하면 log 파일에 TNS events를 포함하게 합니다.
- 기본값 NO
USE_ASYNC_CALL = [YES | NO]
- YES로 설정하면 CMAN 접속을 실행하고 받아들이고 대답하는 과정에서
모든 비동기적인 기능을 사용할 수 있게 합니다.
- 기본값 NO
주의: CMAN은 out-of-band breaks를 지원합니다.
CMAN은 그것을 서버로 전달합니다.
AUTHENTICATION_LEVEL = [0 | 1]
- 1로 설정하게 되면 CMAN은 Secure Network Services를 사용하지 않은
접속 요청은 거절하게 됩니다
Secure Network Services은 Advanced Networking Option의 일부입니다.
- 기본값은 0 입니다.
즉 Secure Network Services가 필요없다는 뜻입니다.
CMAN_RULES=
(RULE_LIST=
(RULE=
(SRC = shost)
(DST = dhost)
(SRV = services)
(ACT = accept | reject)
CMAN_RULES에 정의된 parameter들:
- shost 는 client에서 session을 요청한 source hostname 이거나
IP address입니다.
- dhost 는 서버쪽의 hostname 이거나 IP address 입니다.
- services 는 SID 이름입니다.
- ACT: 위 세개의 parameter들의 값을 근거로한 들어오는 접속요청에
대한 승인이나 거절입니다.
주의: wild-card는 'x'입니다. IP address (d.d.d.d)인 경우에
각 'd'는 wild-card character인 'x'로 교체될 수 있습니다.
RULE_LIST내에 여러 RULE들이 정의될 수 있습니다.
여러 rule들 중에 처음에 맞는 rule이 그 요청에 적용됩니다.
CMAN_RULES이 존재하는 경우 Connection Manager는 규칙에 허용되지 않은
것들은 모두 허락되지 않게 합니다.
만일 CMAN_RULES이 정의되지 않았다면 모든것이 허용됩니다.
Connection Manager의 제한
만일 connection path에 사용된 Connection Manager가 한개 이상이라면 (1개
이상의 hop이라면), tnsnames.ora를 직접 설정해야 하며 Oracle Names Server
를 사용할 수 없습니다.
TCP/IP network에서만 Connection Manager는 접근 통제(CMAN_RULES)를 할 수
있습니다.
Oracle Multi-Protocol Interchange (MPI) 과의 호환성
client와 server사이에 단 하나의 MPI만 있다면, MPI를
Connection Manager로 교체하십시요.
client와 server사이에 여러개의 MPI가 있다면,
tnsnames.ora를 수정해서 MPI들을 Connection Manager들로
교체하십시요.
SQL*Net V2.x client와의 호환성
Connection Manager를 SQL*Net 2.x clients과 Oracle 8사이의
중심이나 접속 필터로 사용하기 위해서는 다음과 같은 일을
해야 합니다.
1) Connection Manager를 설치하고 설정합니다..
2) SQL*Net v2.x client들을 Connection Manager를 MPI처럼 사용
하도록 설정 합니다.
Server 설정
===========
NET8의 새로운 기능을 이용하기 위해서는 Connection Manager를 설정
해야 하며 서버를 Multi-Threaded Server (MTS)로 설정해야 합니다.
MTS parameter들은 각 instance의 INIT.ORA파일에 설정합니다.
NET8 MTS를 위한 parameter들은 SQL*Net 2과 다르지 않습니다.
다음 Connection Pooling 과 Multiplexing 기능을 사용할때
MTS_DISPATCHERS parameter의 경우만 제외하면 말입니다.
MTS_DISPATCHERS parameter:
MTS_DISPATCHERS ="(PROTOCOL=TCP)(POOL=NO)(MULT=ON)"
이 예에서 TCP/IP를 위해 dispatcher들을 설정하고 Connection Pooling
기능을 사용하지 못하게 하고, Multiplexing를 가능하게 합니다.
만일 Connection Pooling 과 Multiplexing 를 사용하지 않을 거라면
SQL*Net 2.x용으로 정의된 MTS parameter들을 사용하실 수 있습니다.
좀더 자세한 내용은 MTS관련 문서를 참조 하시기 바랍니다.
Connection Manager를 사용하는 경우, INIT.ORA에 새로운 parameter를
설정해야 합니다. Connection Manager는 한개 이상의 physical connection
을 만들기 때문에 instance의 dispatcher가 허용할 client sessions의 최대값을
알아야 합니다. SESSIONS라는 parameter가 이 값을 설정합니다.
이 값은 'LSNRCTL SERVICES' 명령으로 볼 수 있습니다.
3. 시작 하기 (Windows NT)
Oracle Names server 환경에서 :
- command line utility 사용하기
1. 작업 표시줄에서 시작->실행
열기: x:\CMCTL80.exe (8i에서는 CMCTL.exe)
OK<click>
2. CMCTL> start CMAN <enter>
- Windows NT 제어판 사용하기
1. 제어판>SERVICES <double click>
2. 다음을 찾아 시작 시킵니다.
(주의: 순서대로 시작시켜야 합니다.)
OracleCMAdminService80 <click start>
OracleCMANService80 <click start>
NON-Oracle Names server 환경에서 :
- command line utility 사용하기
1. 작업 표시줄에서 시작->실행
열기: x:\CMCTL80.exe (8i에서는 CMCTL.exe)
OK<click>
2. CMCTL> start CM <enter>
- Windows NT 제어판 사용하기
1. 제어판>SERVICES <double click>
2. 다음을 찾아 시작 시킵니다.
(주의: 순서대로 시작시켜야 합니다.)
OracleCMANService80 <click start>
Reference Ducumment
---------------------Hi
You must install the Connection Manager, available on the Oracle8 distribution media, onto the Web server host. You can find the installation instructions in the Net8 Administrator's Guide.
On the Web server host, create a CMAN.ORA file in the [ORACLE_HOME]/NET8/ADMIN directory. The options you can declare in a CMAN.ORA file include firewall and connection pooling support
Here is an example of a very simple CMAN.ORA file. Replace <web-server-host> with the name of your Web server host. The fourth line in the file indicates that the connection manager is listening on port 1610. You must use this port number in your connect string for JDBC.
cman = (ADDRESS_LIST =
(ADDRESS = (PROTOCOL=TCP)
(HOST=<web-server-host>)
(PORT=1610)))
cman_profile = (parameter_list =
(MAXIMUM_RELAYS=512)
(LOG_LEVEL=1)
(TRACING=YES)
(RELAY_STATISTICS=YES)
(SHOW_TNS_INFO=YES)
(USE_ASYNC_CALL=YES)
(AUTHENTICATION_LEVEL=0)
Ariel G. -
Hello,
I get the following error message everytime I try to add a node to an existing cluster "Failed to connect to the service manager".
I'm running Windows Server 2008 R2,
Any ideas?Hi saeedawadx,
Please run the cluster validation and post the error or warning information, in normal scenario the “Failed to connect to the service manager” issue often caused by the firewall
or AV soft block the others node connect, please try to disable the firewall and AV soft then try again.
The following related article will give more helpful tips,
The case of the server who couldn’t join a cluster – operation returned because the timeout period expired
http://blogs.technet.com/b/roplatforms/archive/2010/04/28/the-case-of-the-server-who-couldn-t-join-a-cluster-operation-returned-because-the-timeout-period-expired.aspx
Trouble Connecting to Cluster Nodes? Check WMI!
http://blogs.msdn.com/b/clustering/archive/2010/11/23/10095621.aspx
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected] -
Problem starting managed server in cluster (The name of the managed server is same as admin server)
We have the following setup.
CLLUSTER1 and CLUSTER2 are the servers to be in the cluster. CLUSTER3 is the cluster
administrator. We start CLUSTER3 as a self-managed server and then try and start
CLUSTER1 and CLUSTER3 as a managed server pointing at CLUSTER3. When we start
1 and 2 we get the following:
D:\bea\wlserver6.1\config\CLUSTER1>startmanagedweblogic CLUSTER3 http://10.0.1.1
03:7001
D:\bea\wlserver6.1>set PATH=.\bin;C:\WINNT\System32;d:\jdk1.3.1\bin
D:\bea\wlserver6.1>set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
D:\bea\wlserver6.1>echo off
* To start WebLogic Server, use the password *
* assigned to the system user. The system *
* username and password must also be used to *
* access the WebLogic Server console from a web *
* browser. *
D:\bea\wlserver6.1>"d:\bea\jdk131\bin\java" -hotspot -ms64m -mx64m -classpath
;.\lib\weblogic_sp.jar;.\lib\weblogic.jar" -Dweblogic.Domain=CLUSTER1 -Dbea.home
="d:\bea" -Dweblogic.management.password= -Dweblogic.ProductionModeEnabled=true
-Dweblogic.Name="CLUSTER3" -Dweblogic.management.server="http://10.0.1.103:7001"
"-Djava.security.policy==d:\bea\wlserver6.1/lib/weblogic.policy" weblogic.Serve
r
<20/11/2001 12:05:10> <Info> <Security> <Getting boot password from user.>
Enter password to boot WebLogic server:
Starting WebLogic Server ....
Connecting to http://10.0.1.103:7001...
The WebLogic Server did not start up properly.
Exception raised: weblogic.management.configuration.ConfigurationException: The
name of the managed server is same as admin server. The managed server will not
be allowed to start up.
weblogic.management.configuration.ConfigurationException: The name of the manage
d server is same as admin server. The managed server will not be allowed to star
t up.
at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:998)
at weblogic.management.Admin.initialize(Admin.java:320)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
D:\bea\wlserver6.1>goto finish
D:\bea\wlserver6.1>cd config\CLUSTER1
D:\bea\wlserver6.1\config\CLUSTER1>ENDLOCAL
D:\bea\wlserver6.1\config\CLUSTER1>
Many thanks in advance,
Alex Burton
http://www.e-plus.com.au/
Don't start the admin server as managed. Removing
-Dweblogic.management.server...
from the command line should help.
Alex Burton wrote:
> We have the following setup.
> CLLUSTER1 and CLUSTER2 are the servers to be in the cluster. CLUSTER3 is the cluster
> administrator. We start CLUSTER3 as a self-managed server and then try and start
> CLUSTER1 and CLUSTER3 as a managed server pointing at CLUSTER3. When we start
> 1 and 2 we get the following:
>
> D:\bea\wlserver6.1\config\CLUSTER1>startmanagedweblogic CLUSTER3 http://10.0.1.1
> 03:7001
>
> D:\bea\wlserver6.1>set PATH=.\bin;C:\WINNT\System32;d:\jdk1.3.1\bin
>
> D:\bea\wlserver6.1>set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
>
> D:\bea\wlserver6.1>echo off
>
> ***************************************************
> * To start WebLogic Server, use the password *
> * assigned to the system user. The system *
> * username and password must also be used to *
> * access the WebLogic Server console from a web *
> * browser. *
> ***************************************************
>
> D:\bea\wlserver6.1>"d:\bea\jdk131\bin\java" -hotspot -ms64m -mx64m -classpath
> ".
> ;.\lib\weblogic_sp.jar;.\lib\weblogic.jar" -Dweblogic.Domain=CLUSTER1 -Dbea.home
> ="d:\bea" -Dweblogic.management.password= -Dweblogic.ProductionModeEnabled=true
> -Dweblogic.Name="CLUSTER3" -Dweblogic.management.server="http://10.0.1.103:7001"
> "-Djava.security.policy==d:\bea\wlserver6.1/lib/weblogic.policy" weblogic.Serve
> r
> <20/11/2001 12:05:10> <Info> <Security> <Getting boot password from user.>
> Enter password to boot WebLogic server:
> Starting WebLogic Server ....
> Connecting to http://10.0.1.103:7001...
> ***************************************************************************
> The WebLogic Server did not start up properly.
> Exception raised: weblogic.management.configuration.ConfigurationException: The
> name of the managed server is same as admin server. The managed server will not
> be allowed to start up.
> weblogic.management.configuration.ConfigurationException: The name of the manage
> d server is same as admin server. The managed server will not be allowed to star
> t up.
> at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:998)
> at weblogic.management.Admin.initialize(Admin.java:320)
> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
> at weblogic.Server.main(Server.java:35)
> Reason: Fatal initialization exception
> ***************************************************************************
>
> D:\bea\wlserver6.1>goto finish
>
> D:\bea\wlserver6.1>cd config\CLUSTER1
>
> D:\bea\wlserver6.1\config\CLUSTER1>ENDLOCAL
>
> D:\bea\wlserver6.1\config\CLUSTER1>
>
> Many thanks in advance,
> Alex Burton
> http://www.e-plus.com.au/
-
EAS server error: Could not connect to administration Server
Hi,
I have installed Hyperion suite in Windows server 2008 R2. It was working fine but now when i tried to login in to the EAS console, I am getting the following error:
"Server Error: Could not connect to administration server".
I tried accessing the same through the web URL and I found "404 error - file or directory not found".
I verified all my services are up and running fine. I am able to connect to the essbase sever through Excel as well as planning.
The log retireved from the HyS9eas-sysout.log file is below:
<Sep 11, 2013 7:06:56 AM JST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Sep 11, 2013 7:06:57 AM JST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Sep 11, 2013 7:06:58 AM JST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Oracle JRockit(R) Version R28.0.2-11-135406-1.6.0_20-20100624-2119-windows-x86_64 from Oracle Corporation>
<Sep 11, 2013 7:07:04 AM JST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.4.0 Fri Dec 17 20:47:33 PST 2010 1384255 >
<Sep 11, 2013 7:07:15 AM JST> <Emergency> <Management> <BEA-141151> <The admin server could not be reached at http://localhost:7001.>
<Sep 11, 2013 7:07:15 AM JST> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.>
<Sep 11, 2013 7:07:15 AM JST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Sep 11, 2013 7:07:15 AM JST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Sep 11, 2013 7:07:16 AM JST> <Notice> <LoggingService> <BEA-320400> <The log file E:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EssbaseAdminServices0\logs\EssbaseAdminServices0.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>
<Sep 11, 2013 7:07:16 AM JST> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to E:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EssbaseAdminServices0\logs\EssbaseAdminServices0.log00410. Log messages will continue to be logged in E:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EssbaseAdminServices0\logs\EssbaseAdminServices0.log.>
<Sep 11, 2013 7:07:16 AM JST> <Notice> <Log Management> <BEA-170019> <The server log file E:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EssbaseAdminServices0\logs\EssbaseAdminServices0.log is opened. All server side log events will be written to this file.>
<Sep 11, 2013 7:07:48 AM JST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Sep 11, 2013 7:07:56 AM JST> <Warning> <JTA> <BEA-110503> <The migrator(the AdminServer for manual JTA migration policy, or the Singleton Master for automatic JTA migration policy) is not available. Will skip JTA TRS failback because isStrictOwnershipCheck is [false]. This may lead to potencial TLOG corruption if TRS of EssbaseAdminServices0 has been migrated to backup server and the backup server is accessing the TLOG of EssbaseAdminServices0. More safety can be achieved by setting isStrictOwnershipCheck to [true].>
<Sep 11, 2013 7:08:35 AM JST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
<Sep 11, 2013 7:08:35 AM JST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
Calling getConnection()
return weblogic.management.jmx.mbeanserver.WLSMBeanServer@9830ac
Calling getDomainConfiguration()
Calling getConnection()
return weblogic.management.jmx.mbeanserver.WLSMBeanServer@9830ac
Calling getRuntimeService()
Calling getConnection()
return weblogic.management.jmx.mbeanserver.WLSMBeanServer@9830ac
return com.bea:Name=RuntimeService,Type=weblogic.management.mbeanservers.runtime.RuntimeServiceMBean
return com.bea:Name=EPMSystem,Type=Domain
Calling getConnection()
return weblogic.management.jmx.mbeanserver.WLSMBeanServer@9830ac
Domain location is 'E:\Oracle\Middleware\user_projects\domains\EPMSystem'
Calling getRuntimeService()
return com.bea:Name=RuntimeService,Type=weblogic.management.mbeanservers.runtime.RuntimeServiceMBean
Calling getConnection()
return weblogic.management.jmx.mbeanserver.WLSMBeanServer@9830ac
Calling getConnection()
return weblogic.management.jmx.mbeanserver.WLSMBeanServer@9830ac
Calling getConnection()
return weblogic.management.jmx.mbeanserver.WLSMBeanServer@9830ac
Calling getConnection()
return weblogic.management.jmx.mbeanserver.WLSMBeanServer@9830ac
Checking E:\Oracle\Middleware\user_projects\domains\EPMSystem\servers\EssbaseAdminServices0\registry_update.xml file
EPM_ORACLE_HOME: E:\Oracle\Middleware\EPMSystem11R1
Template for EAS#11.1.2.0: E:\Oracle\Middleware\EPMSystem11R1\common\templates\applications\epm_eas_11.1.2.1.jar
Dependencies for E:\Oracle\Middleware\EPMSystem11R1\common\templates\applications\epm_eas_11.1.2.1.jar: [Oracle EPM Common, Oracle EPM Calcmgr, Oracle EPM Planning libraries, Oracle EPM EAS libraries, Oracle EPM Misc libraries, Oracle EPM Xerces libraries]
BPMUI shared webapp not referenced from EAS#11.1.2.0
Application name: EAS#11.1.2.0
Application source: eas.ear
Server name: EssbaseAdminServices0
Server port: 10080
Server SSL port: 10083
Application context: eas
Registry product type: ESSBASE_PRODUCT
Registry physical web application type: ADMIN_SERVICES_WEB_APP
weblogic.Name property is 'EssbaseAdminServices0', seems to be WebLogic mode
registry.isRegistryDatabaseCreated()true
Registry was initialized sucessfully
Executing pre custom update for EAS#11.1.2.0
EPM_ORACLE_INSTANCE: E:\Oracle\Middleware\user_projects\epmsystem1
<Sep 11, 2013 7:09:06 AM JST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'EAS [Version=11.1.2.0]' due to error java.lang.NullPointerException.
java.lang.NullPointerException
at java.io.File.<init>(File.java:222)
at com.hyperion.hit.tool.deploy.update.util.RegistryHelper.createPhysicalWebApp(RegistryHelper.java:168)
at com.hyperion.hit.tool.deploy.update.RegistryUpdater.update(RegistryUpdater.java:36)
at com.hyperion.hit.tool.deploy.update.RegistryUpdateListener.preStart(RegistryUpdateListener.java:91)
at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
Truncated. see log file for complete stacktrace
Caused By: java.lang.NullPointerException
at java.io.File.<init>(File.java:222)
at com.hyperion.hit.tool.deploy.update.util.RegistryHelper.createPhysicalWebApp(RegistryHelper.java:168)
at com.hyperion.hit.tool.deploy.update.RegistryUpdater.update(RegistryUpdater.java:36)
at com.hyperion.hit.tool.deploy.update.RegistryUpdateListener.preStart(RegistryUpdateListener.java:91)
at weblogic.application.internal.flow.BaseLifecycleFlow$PreStartAction.run(BaseLifecycleFlow.java:282)
Truncated. see log file for complete stacktrace
>
<Sep 11, 2013 7:09:06 AM JST> <Emergency> <Deployer> <BEA-149259> <Server 'EssbaseAdminServices0' in cluster 'EssbaseAdminServices' is being brought up in administration state due to failed deployments.>
<Sep 11, 2013 7:09:17 AM JST> <Notice> <Cluster> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
<Sep 11, 2013 7:09:17 AM JST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of EssbaseAdminServices.>
<Sep 11, 2013 7:09:22 AM JST> <Warning> <Log Management> <BEA-170011> <The LogBroadcaster on this server failed to broadcast log messages to the admin server. The Admin server may not be running. Message broadcasts to the admin server will be disabled.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090171> <Loading the identity certificate and private key stored under the alias DemoIdentity from the jks keystore file E:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoIdentity.jks.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file E:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file E:\Oracle\Middleware\jrockit_160_20\jre\lib\security\cacerts.>
<Sep 11, 2013 7:09:48 AM JST> <Alert> <Security> <BEA-090152> <Demo trusted CA certificate is being used in production mode: [
Version: V3
Subject: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
Key: Sun RSA public key, 512 bits
modulus: 9550192877869244258838480703390456015046425375252278279190673063544122510925482179963329236052146047356415957587628011282484772458983977898996276815440753
public exponent: 65537
Validity: [From: Fri Mar 22 05:12:27 JST 2002,
To: Wed Mar 23 05:12:27 JST 2022]
Issuer: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
SerialNumber: [ 33f10648 fcde0deb 4199921f d64537f4]
Certificate Extensions: 1
[1]: ObjectId: 2.5.29.15 Criticality=true
KeyUsage [
Key_CertSign
Algorithm: [MD5withRSA]
Signature:
0000: 9D 26 4C 29 C8 91 C3 A7 06 C3 24 6F AE B4 F8 82 .&L)......$o....
0010: 80 4D AA CB 7C 79 46 84 81 C4 66 95 F4 1E D8 C4 .M...yF...f.....
0020: E9 B7 D9 7C E2 23 33 A4 B7 21 E0 AA 54 2B 4A FF .....#3..!..T+J.
0030: CB 21 20 88 81 21 DB AC 90 54 D8 7D 79 63 23 3C .! ..!...T..yc#<
] The system is vulnerable to security attacks, since it trusts certificates signed by the demo trusted CA.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "Default[6]" is now listening on 127.0.0.1:10080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[6]" is now listening on 127.0.0.1:10083 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "Default[7]" is now listening on 0:0:0:0:0:0:0:1:10080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[7]" is now listening on 0:0:0:0:0:0:0:1:10083 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on fe80:0:0:0:0:5efe:a0e:daee:10080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 10.14.126.11:10080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[5]" is now listening on fe80:0:0:0:0:5efe:a0e:224b:10083 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[3]" is now listening on fe80:0:0:0:0:5efe:a0e:daee:10083 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[1]" is now listening on 10.14.126.11:10083 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "Default[5]" is now listening on fe80:0:0:0:0:5efe:a0e:224b:10080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on 10.14.34.75:10080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[4]" is now listening on fe80:0:0:0:0:5efe:a0e:7e0b:10083 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure" is now listening on 10.14.218.238:10083 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 10.14.218.238:10080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[2]" is now listening on 10.14.34.75:10083 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <Server> <BEA-002613> <Channel "Default[4]" is now listening on fe80:0:0:0:0:5efe:a0e:7e0b:10080 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Sep 11, 2013 7:09:48 AM JST> <Notice> <WebLogicServer> <BEA-000358> <Started WebLogic Independent Managed Server "EssbaseAdminServices0" for domain "EPMSystem" running in Production Mode>
<Sep 11, 2013 7:09:48 AM JST> <Warning> <JMX> <BEA-149510> <Unable to establish JMX Connectivity with the Adminstration Server AdminServer at <JMXServiceURL:null>.>
<Sep 11, 2013 7:09:48 AM JST> <Warning> <Server> <BEA-002611> <Hostname "SJ015040", maps to multiple IP addresses: 10.14.126.11, 10.14.34.75, 10.14.218.238, 0:0:0:0:0:0:0:1>
<Sep 11, 2013 7:09:53 AM JST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Sep 11, 2013 7:09:53 AM JST> <Notice> <WebLogicServer> <BEA-000360> <Server started in ADMIN mode>
HyS9eas-syserr.log is empty and I dont find anyother details from the other log files.
Kindly help me out in solving this issue.
Thanks in advance.
Regards,
Balaji PHi John,
Sorry for replying late.
I ran the EPM diagnostic and found EAS & APS application are failed. So as you mentioned, i tried re-deployment through EPM configurator.
But Re-configuration fails with error "An unexpected error occurred and the application will have to shut down" .
When i looked in to the Config tool.log,I got the following messages.
[2013-09-17T18:17:04.635+09:00] [EPMCFG] [TRACE] [EPMCFG-01001] [oracle.EPMCFG] [tid: 17] [ecid: 0000K4fDMY^0zkgpxC^AyW1IE1pJ000003,0:325] [SRC_CLASS: com.hyperion.hit.tool.deploy.utils.UIPortUtil] trace: Parsing server FinancialReporting0 on port 8200 from registry
[2013-09-17T18:17:04.827+09:00] [EPMINS] [ERROR] [EPMINS-00001] [oracle.EPMINS] [tid: 17] [ecid: 0000K4fDMY^0zkgpxC^AyW1IE1pJ000003,0:325] [SRC_CLASS: com.hyperion.hit.wizard.Wizard] trace: Unexpected error:[[
java.lang.NullPointerException
at com.hyperion.hit.tool.deploy.utils.UIPortUtil.<init>(UIPortUtil.java:83)
at com.hyperion.hit.tool.deploy.utils.UIPortUtil.getInstance(UIPortUtil.java:53)
at com.hyperion.config.wizard.DeploymentField.getAppServerDeploymentData(DeploymentField.java:235)
at com.hyperion.config.wizard.DeploymentField.<init>(DeploymentField.java:56)
at com.hyperion.config.wizard.impl.DeploymentForm.<init>(DeploymentForm.java:57)
at com.hyperion.config.wizard.impl.DeploymentState.initializeBeforeShowOnNext(DeploymentState.java:56)
at com.hyperion.hit.wizard.Wizard$NextClass.run(Wizard.java:522)
at java.lang.Thread.run(Thread.java:619)
Since it is similare to the Oracle konwledge base article - (Doc ID 1570293.1), I tried adding the shared service domain to the Windows host file. But i am still recieveing the same error message as above.
Appreciates your help.
Thanks & Regards,
Balaji P -
Problem connecting weblogic server to cluster
Hi,
I am very new to WL/JMS/JNDI/EJB etc. I downloaded WL6.0, and tried to make a cluster. I started a server on one machine as Administrative server, and created a cluster. Now, I started another server on a different machine, as a managed server by adding the following parameter at startup
-Dweblogic.admin.host=http://admin-ipaddr:7001....,
I get the following error
Starting WebLogic Server ....
<Thu Oct 19 14:37:37 PDT 2000> <Error> <Configuration Management> <Error connecting to admin server to bootstrap via URL: http://admin-ipaddr:7001/Bootstrap, user: system
weblogic.management.configuration.ConfigurationException: Connection error: java.lang.SecurityException: Authentication for user system
denied in realm weblogic
at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:752)
at weblogic.management.Admin.initialize(Admin.java:275)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:345)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
at weblogic.Server.main(Server.java:32)
>
<Thu Oct 19 14:37:37 PDT 2000> <Emergency> <Server> <Unable to initialize the server: Fatal initialization exception
Throwable: weblogic.management.configuration.ConfigurationException: connecting to http://admin-ipaddr:7001/Bootstrap - with nested exception:
[weblogic.management.configuration.ConfigurationException: Connection error: java.lang.SecurityException: Authentication for user system denied in realm weblogic]
weblogic.management.configuration.ConfigurationException: connecting to http://admin-ipaddr:7001/Bootstrap - with nested exception:
[weblogic.management.configuration.ConfigurationException: Connection error: java.lang.SecurityException: Authentication for user syste
m denied in realm weblogic]
at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:803)
at weblogic.management.Admin.initialize(Admin.java:275)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:345)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
at weblogic.Server.main(Server.java:32)
>
I understand that all managed servers are supposed to use the same config file as the Admin server.
Also, I am not clear about the domain parameter.... what should I pass for -Dweblogic.Domain=mydomain (this is what is there in the batch file that comes). Should I change this parameter for Managed servers, which points to Admin domain? If so, how do I do that?
I am struck up on this. I'd greatly appreciate it some body could help me out.
thanks a lot,
Anil.
-Dweblogic.admin.host=admin-ipaddr:7001, you shouldn't specify protocol. Also please use beta newsgroup for 6.0 related questions.
anil wrote:
> Hi,
> I am very new to WL/JMS/JNDI/EJB etc. I downloaded WL6.0, and tried to make a cluster. I started a server on one machine as Administrative server, and created a cluster. Now, I started another server on a different machine, as a managed server by adding the following parameter at startup
> -Dweblogic.admin.host=http://admin-ipaddr:7001....,
>
> I get the following error
> Starting WebLogic Server ....
> <Thu Oct 19 14:37:37 PDT 2000> <Error> <Configuration Management> <Error connecting to admin server to bootstrap via URL: http://admin-ipaddr:7001/Bootstrap, user: system
> weblogic.management.configuration.ConfigurationException: Connection error: java.lang.SecurityException: Authentication for user system
> denied in realm weblogic
> at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:752)
> at weblogic.management.Admin.initialize(Admin.java:275)
> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:345)
> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
> at weblogic.Server.main(Server.java:32)
> >
> <Thu Oct 19 14:37:37 PDT 2000> <Emergency> <Server> <Unable to initialize the server: Fatal initialization exception
> Throwable: weblogic.management.configuration.ConfigurationException: connecting to http://admin-ipaddr:7001/Bootstrap - with nested exception:
> [weblogic.management.configuration.ConfigurationException: Connection error: java.lang.SecurityException: Authentication for user system denied in realm weblogic]
> weblogic.management.configuration.ConfigurationException: connecting to http://admin-ipaddr:7001/Bootstrap - with nested exception:
> [weblogic.management.configuration.ConfigurationException: Connection error: java.lang.SecurityException: Authentication for user syste
> m denied in realm weblogic]
> at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:803)
> at weblogic.management.Admin.initialize(Admin.java:275)
> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:345)
> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
> at weblogic.Server.main(Server.java:32)
> >
> ***************************************************************************
> I understand that all managed servers are supposed to use the same config file as the Admin server.
>
> Also, I am not clear about the domain parameter.... what should I pass for -Dweblogic.Domain=mydomain (this is what is there in the batch file that comes). Should I change this parameter for Managed servers, which points to Admin domain? If so, how do I do that?
>
> I am struck up on this. I'd greatly appreciate it some body could help me out.
>
> thanks a lot,
> Anil.
-
Could not connect to Administration server Essbase in EAS console 11.1.2.2
Hi All,
I successfully installed and configured Essbase 11.1.2.2 version. When I tried to connect with administration server in eas console it throwing me error as,
Could not connect to Administration server Essbase.
Kindly guide me.
Thanks and Regards
SaiHi John,
Thanks for your response. These are the following message I found in HyS9eas-sysout.log and HyS9eas-syserr.log.
HyS9eas-sysout.log:
<May 11, 2012 8:43:26 PM IST> <Error> <HTTP> <BEA-101216> <Servlet: "InitServlet" failed to preload on startup in Web application: "WebAnalysis".
com.hyperion.atf.services.ServiceManager$ServiceRecursiveInitException: Could not start critical service: "assignable.admin", all services are being rolled back.
at com.hyperion.atf.services.ServiceManager.setServiceContainer(ServiceManager.java:591)
at com.hyperion.atf.services.ServiceManager.getService(ServiceManager.java:309)
at com.hyperion.atf.services.ServiceManager.getService(ServiceManager.java:341)
at com.hyperion.atf.security.assignables.AssignableManager.getAssignableAdmin(AssignableManager.java:28)
at com.hyperion.atf.security.assignables.AssignableManager.getDefaultHomeDirLocation(AssignableManager.java:77)
Truncated. see log file for complete stacktrace
>
<May 11, 2012 8:43:27 PM IST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'WEBANALYSIS [Version=11.1.2.0]'.
weblogic.application.ModuleException: [HTTP:101216]Servlet: "InitServlet" failed to preload on startup in Web application: "WebAnalysis".
com.hyperion.atf.services.ServiceManager$ServiceRecursiveInitException: Could not start critical service: "assignable.admin", all services are being rolled back.
at com.hyperion.atf.services.ServiceManager.setServiceContainer(ServiceManager.java:591)
at com.hyperion.atf.services.ServiceManager.getService(ServiceManager.java:309)
at com.hyperion.atf.services.ServiceManager.getService(ServiceManager.java:341)
at com.hyperion.atf.security.assignables.AssignableManager.getAssignableAdmin(AssignableManager.java:28)
at com.hyperion.atf.security.assignables.AssignableManager.getDefaultHomeDirLocation(AssignableManager.java:77)
at com.hyperion.analyzer.servlet.HYAInitServlet.checkUserDir(Unknown Source)
at com.hyperion.analyzer.servlet.HYAInitServlet.init(Unknown Source)
at javax.servlet.GenericServlet.init(GenericServlet.java:241)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:283)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
at weblogic.servlet.internal.StubSecurityHelper.createServlet(StubSecurityHelper.java:64)
at weblogic.servlet.internal.StubLifecycleHelper.createOneInstance(StubLifecycleHelper.java:58)
at weblogic.servlet.internal.StubLifecycleHelper.<init>(StubLifecycleHelper.java:48)
at weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:539)
at weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:1981)
at weblogic.servlet.internal.WebAppServletContext.loadServletsOnStartup(WebAppServletContext.java:1955)
at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1874)
at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:3155)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1518)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:487)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
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:201)
at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:249)
at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:427)
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:28)
at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:672)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:59)
at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:161)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:79)
at weblogic.deploy.internal.targetserver.BasicDeployment.activate(BasicDeployment.java:184)
at weblogic.deploy.internal.targetserver.BasicDeployment.activateFromServerLifecycle(BasicDeployment.java:361)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doActivate(DeploymentAdapter.java:52)
at weblogic.management.deploy.internal.DeploymentAdapter.activate(DeploymentAdapter.java:200)
at weblogic.management.deploy.internal.AppTransition$2.transitionApp(AppTransition.java:31)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:261)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:220)
at weblogic.management.deploy.internal.ConfiguredDeployments.activate(ConfiguredDeployments.java:170)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:124)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:181)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:97)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1520)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:484)
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)
Truncated. see log file for complete stacktrace
Caused By: com.hyperion.atf.services.ServiceManager$ServiceRecursiveInitException: Could not start critical service: "assignable.admin", all services are being rolled back.
at com.hyperion.atf.services.ServiceManager.setServiceContainer(ServiceManager.java:591)
at com.hyperion.atf.services.ServiceManager.getService(ServiceManager.java:309)
at com.hyperion.atf.services.ServiceManager.getService(ServiceManager.java:341)
at com.hyperion.atf.security.assignables.AssignableManager.getAssignableAdmin(AssignableManager.java:28)
at com.hyperion.atf.security.assignables.AssignableManager.getDefaultHomeDirLocation(AssignableManager.java:77)
Truncated. see log file for complete stacktrace
>
<May 11, 2012 8:43:39 PM IST> <Notice> <Cluster> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
<May 11, 2012 8:43:39 PM IST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of EPMServer.>
<May 11, 2012 8:43:42 PM IST> <Warning> <Log Management> <BEA-170011> <The LogBroadcaster on this server failed to broadcast log messages to the admin server. The Admin server may not be running. Message broadcasts to the admin server will be disabled.>
<May 11, 2012 8:44:11 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<May 11, 2012 8:44:12 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<May 11, 2012 8:44:21 PM IST> <Notice> <Cluster> <BEA-000162> <Starting "async" replication service with remote cluster address "null">
<May 11, 2012 8:44:24 PM IST> <Notice> <Security> <BEA-090171> <Loading the identity certificate and private key stored under the alias DemoIdentity from the jks keystore file C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoIdentity.jks.>
<May 11, 2012 8:44:29 PM IST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks.>
<May 11, 2012 8:44:29 PM IST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\Oracle\Middleware\jrockit_160_29\jre\lib\security\cacerts.>
<May 11, 2012 8:44:29 PM IST> <Alert> <Security> <BEA-090152> <Demo trusted CA certificate is being used in production mode: [
Version: V3
Subject: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4
Key: Sun RSA public key, 512 bits
modulus: 9550192877869244258838480703390456015046425375252278279190673063544122510925482179963329236052146047356415957587628011282484772458983977898996276815440753
public exponent: 65537
Validity: [From: Fri Mar 22 01:42:27 IST 2002,
To: Wed Mar 23 01:42:27 IST 2022]
Issuer: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
SerialNumber: [ 33f10648 fcde0deb 4199921f d64537f4]
Certificate Extensions: 1
[1]: ObjectId: 2.5.29.15 Criticality=true
KeyUsage [
Key_CertSign
Algorithm: [MD5withRSA]
Signature:
0000: 9D 26 4C 29 C8 91 C3 A7 06 C3 24 6F AE B4 F8 82 .&L)......$o....
0010: 80 4D AA CB 7C 79 46 84 81 C4 66 95 F4 1E D8 C4 .M...yF...f.....
0020: E9 B7 D9 7C E2 23 33 A4 B7 21 E0 AA 54 2B 4A FF .....#3..!..T+J.
0030: CB 21 20 88 81 21 DB AC 90 54 D8 7D 79 63 23 3C .! ..!...T..yc#<
] The system is vulnerable to security attacks, since it trusts certificates signed by the demo trusted CA.>
<May 11, 2012 8:44:29 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=Entrust Root Certification Authority - G2,OU=(c) 2009 Entrust\, Inc. - for authorized use only,OU=See www.entrust.net/legal-terms,O=Entrust\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<May 11, 2012 8:44:29 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<May 11, 2012 8:44:29 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<May 11, 2012 8:44:29 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<May 11, 2012 8:44:29 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<May 11, 2012 8:44:29 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<May 11, 2012 8:44:29 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<May 11, 2012 8:44:29 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<May 11, 2012 8:44:29 PM IST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<May 11, 2012 8:44:29 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 127.0.0.1:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<May 11, 2012 8:44:29 PM IST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 172.16.2.14:9000 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<May 11, 2012 8:44:29 PM IST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure" is now listening on 172.16.2.14:9443 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<May 11, 2012 8:44:29 PM IST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[1]" is now listening on 127.0.0.1:9443 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<May 11, 2012 8:44:29 PM IST> <Notice> <WebLogicServer> <BEA-000358> <Started WebLogic Independent Managed Server "EPMServer0" for domain "EPMSystem" running in Production Mode>
<May 11, 2012 8:44:29 PM IST> <Warning> <JMX> <BEA-149510> <Unable to establish JMX Connectivity with the Adminstration Server AdminServer at <JMXServiceURL:null>.>
<May 11, 2012 8:44:37 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<May 11, 2012 8:44:38 PM IST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
HyS9eas-syserr.log:
Creating rebind thread to RMI -
EAS Error: Could not connect to Administration Server
Hi Genius,
I have installed and configured Hyperion (11.1.2.1) Essbase & Planning successfully on windows server 2008 64 bit. For that I installed Oracle 10g Standard Edition as supported RDBMS. Due to RAM consumption I planned to install the Oracle Express Edition instead of Standard Edition. For that I export the tablespace which contains metadata of Hyperion products from existing database(SE) to current database(XE). After that I reconfigured all the Hyperion Products.
Once re-configuration completed, I tried to log-in to the Administration Server via EAS Console by providing server name as localhost and username as Admin. Then EAS console throwing error as "Could not connect to Administration server".
To solve this issue I tried following steps,
1> Remove the Cwallet.sso and create a new Cwallet.sso by using orapki bat file.
2> Backup the original ESSBASE.SEC file and rename the ESSBASE.BAK file to ESSBASE.SEC then I started the Essbase Administration service.
3> I re-installed and re-configured the EAS console.
After following these steps I am not able to overcome this issue.
For your kind information,
1> I can able to login to the Essbase through ESSCMD.
2> I can able to view the list of essbase applications through Smart View.
Kindly guide me how to overcome this issue.
Best Regards
SCHi John,
Thanks for your response. I observed the EAS logs clearly and came to know that there were no errors in Hypeas-syserr.log.
The warnings listed below are mentioned in Hypeas-sysout.log,
Dec 11, 2013 6:18:46 AM PST> <Info> <Configuration Management> <BEA-150018> <This server is being started in managed server independence mode in the absence of the admin server.><Dec 11, 2013 6:20:56 AM PST> <Notice> <Cluster> <BEA-000197> <Listening for announcements from cluster using unicast cluster messaging>
<Dec 11, 2013 6:20:56 AM PST> <Notice> <Cluster> <BEA-000133> <Waiting to synchronize with other running members of EssbaseAdminServices.>
<Dec 11, 2013 6:21:01 AM PST> <Warning> <Log Management> <BEA-170011> <The LogBroadcaster on this server failed to broadcast log messages to the admin server. The Admin server may not be running. Message broadcasts to the admin server will be disabled.>
<Dec 11, 2013 6:21:26 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Dec 11, 2013 6:21:26 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
<Dec 11, 2013 6:21:50 AM PST> <Notice> <Cluster> <BEA-000162> <Starting "async" replication service with remote cluster address "null">
<Dec 11, 2013 6:21:50 AM PST> <Notice> <Security> <BEA-090171> <Loading the identity certificate and private key stored under the alias DemoIdentity from the jks keystore file C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoIdentity.jks.>
<Dec 11, 2013 6:21:50 AM PST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks.>
<Dec 11, 2013 6:21:51 AM PST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C:\Oracle\Middleware\jrockit_160_20\jre\lib\security\cacerts.>
<Dec 11, 2013 6:21:51 AM PST> <Alert> <Security> <BEA-090152> <Demo trusted CA certificate is being used in production mode: [
Version: V3
Subject: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
Signature Algorithm: MD5withRSA, OID = 1.2.840.113549.1.1.4 Key: Sun RSA public key, 512 bits
modulus: 9550192877869244258838480703390456015046425375252278279190673063544122510925482179963329236052146047356415957587628011282484772458983977898996276815440753
public exponent: 65537
Validity: [From: Thu Mar 21 12:12:27 PST 2002,
To: Tue Mar 22 13:12:27 PDT 2022]
Issuer: CN=CACERT, OU=FOR TESTING ONLY, O=MyOrganization, L=MyTown, ST=MyState, C=US
SerialNumber: [ 33f10648 fcde0deb 4199921f d64537f4] Certificate Extensions: 1
[1]: ObjectId: 2.5.29.15 Criticality=true
KeyUsage [
Key_CertSign
Algorithm: [MD5withRSA]
Signature:
0000: 9D 26 4C 29 C8 91 C3 A7 06 C3 24 6F AE B4 F8 82 .&L)......$o....
0010: 80 4D AA CB 7C 79 46 84 81 C4 66 95 F4 1E D8 C4 .M...yF...f.....
0020: E9 B7 D9 7C E2 23 33 A4 B7 21 E0 AA 54 2B 4A FF .....#3..!..T+J.
0030: CB 21 20 88 81 21 DB AC 90 54 D8 7D 79 63 23 3C .! ..!...T..yc#< ] The system is vulnerable to security attacks, since it trusts certificates signed by the demo trusted CA.>
<Dec 11, 2013 6:21:51 AM PST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=thawte Primary Root CA - G3,OU=(c) 2008 thawte\, Inc. - For authorized use only,OU=Certification Services Division,O=thawte\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Dec 11, 2013 6:21:51 AM PST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Dec 11, 2013 6:21:51 AM PST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Dec 11, 2013 6:21:51 AM PST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Dec 11, 2013 6:21:51 AM PST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Dec 11, 2013 6:21:51 AM PST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=VeriSign Universal Root Certification Authority,OU=(c) 2008 VeriSign\, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign\, Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Dec 11, 2013 6:21:51 AM PST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Dec 11, 2013 6:21:51 AM PST> <Notice> <Security> <BEA-090898> <Ignoring the trusted CA certificate "CN=GeoTrust Primary Certification Authority - G3,OU=(c) 2008 GeoTrust Inc. - For authorized use only,O=GeoTrust Inc.,C=US". The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<Dec 11, 2013 6:21:51 AM PST> <Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on fe80:0:0:0:0:5efe:ac10:538:10180 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 11, 2013 6:21:51 AM PST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[3]" is now listening on 127.0.0.1:10083 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Dec 11, 2013 6:21:51 AM PST> <Notice> <Server> <BEA-002613> <Channel "Default[2]" is now listening on fe80:0:0:0:40e8:3a49:3d4b:1fd1:10180 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 11, 2013 6:21:51 AM PST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure" is now listening on 172.16.5.56:10083 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Dec 11, 2013 6:21:51 AM PST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[4]" is now listening on 0:0:0:0:0:0:0:1:10083 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Dec 11, 2013 6:21:51 AM PST> <Notice> <Server> <BEA-002613> <Channel "Default[4]" is now listening on 0:0:0:0:0:0:0:1:10180 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 11, 2013 6:21:51 AM PST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[2]" is now listening on fe80:0:0:0:40e8:3a49:3d4b:1fd1:10083 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Dec 11, 2013 6:21:51 AM PST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 172.16.5.56:10180 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 11, 2013 6:21:51 AM PST> <Notice> <Server> <BEA-002613> <Channel "Default[3]" is now listening on 127.0.0.1:10180 for protocols iiop, t3, CLUSTER-BROADCAST, ldap, snmp, http.>
<Dec 11, 2013 6:21:51 AM PST> <Notice> <Server> <BEA-002613> <Channel "DefaultSecure[1]" is now listening on fe80:0:0:0:0:5efe:ac10:538:10083 for protocols iiops, t3s, CLUSTER-BROADCAST-SECURE, ldaps, https.>
<Dec 11, 2013 6:21:51 AM PST> <Notice> <WebLogicServer> <BEA-000358> <Started WebLogic Independent Managed Server "EssbaseAdminServices1" for domain "EPMSystem" running in Production Mode>
<Dec 11, 2013 6:21:51 AM PST> <Warning> <JMX> <BEA-149510> <Unable to establish JMX Connectivity with the Adminstration Server AdminServer at <JMXServiceURL:null>.>
<Dec 11, 2013 6:21:56 AM PST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
<Dec 11, 2013 6:21:56 AM PST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
Best Regards
SC -
BEA-149505 -The administration server was unable to establish JMX Connect.
hello
Getting the following error, trying to access the weblogic admin server ( Linux x86-64 RHL50) after a fresh install.
BEA-149505 The administration server was unable to establish JMX Connectivity with the managedServer at the JMX Service URL of <none > URL in the AdminServer LogiI
1. what steps and configuration files do I need to access to add the url
I will like to add that the node manager and the cluster screen were NOT configured during the configuration, since this is NOT an OIM configuration
2. if you have any tips please let me know
r.faisal
thank for your feedback. I added this in my startup script, but I was NOT able to get the web access to work and when I shot it down, there was an error.
Here is the startup script, Please show me when to place the scripts
#!/bin/sh
# WARNING: This file is created by the Configuration Wizard.
# Any changes to this script may be lost when adding extensions to this configuration.
# --- Start Functions ---
stopAll()
# We separate the stop commands into a function so we are able to use the trap command in Unix (calling a function) to stop these services
if [ "X${ALREADY_STOPPED}" != "X" ] ; then
exit
fi
# STOP DERBY (only if we started it)
if [ "${DERBY_FLAG}" = "true" ] ; then
echo "Stopping Derby server..."
${WL_HOME}/common/derby/bin/stopNetworkServer.sh >"${DOMAIN_HOME}/derbyShutdown.log" 2>&1
echo "Derby server stopped."
fi
ALREADY_STOPPED="true"
# --- End Functions ---
# This script is used to start WebLogic Server for this domain.
# To create your own start script for your domain, you can initialize the
# environment by calling @USERDOMAINHOME/setDomainEnv.
# setDomainEnv initializes or calls commEnv to initialize the following variables:
# BEA_HOME - The BEA home directory of your WebLogic installation.
# JAVA_HOME - Location of the version of Java used to start WebLogic
# Server.
# JAVA_VENDOR - Vendor of the JVM (i.e. BEA, HP, IBM, Sun, etc.)
# PATH - JDK and WebLogic directories are added to system path.
# WEBLOGIC_CLASSPATH
# - Classpath needed to start WebLogic Server.
# PATCH_CLASSPATH - Classpath used for patches
# PATCH_LIBPATH - Library path used for patches
# PATCH_PATH - Path used for patches
# WEBLOGIC_EXTENSION_DIRS - Extension dirs for WebLogic classpath patch
"/erasdevapp/weblogic/user_projects/domains/base_domain/bin/startWebLogic
umask 037
# Call setDomainEnv here.
DOMAIN_HOME="/erasdevapp/weblogic/user_projects/domains/base_domain"
. ${DOMAIN_HOME}/bin/setDomainEnv.sh $*
SAVE_JAVA_OPTIONS="${JAVA_OPTIONS}"
SAVE_CLASSPATH="${CLASSPATH}"
# Start Derby
DERBY_DEBUG_LEVEL="0"
if [ "${DERBY_FLAG}" = "true" ] ; then
${WL_HOME}/common/derby/bin/startNetworkServer.sh >"${DOMAIN_HOME}/derby.log" 2>&1
fi
JAVA_OPTIONS="${SAVE_JAVA_OPTIONS}"
SAVE_JAVA_OPTIONS=""
CLASSPATH="${SAVE_CLASSPATH}"
SAVE_CLASSPATH=""
trap 'stopAll' 1 2 3 15
if [ "${PRODUCTION_MODE}" = "true" ] ; then
WLS_DISPLAY_MODE="Production"
WLS_DISPLAY_MODE="Production"
else
WLS_DISPLAY_MODE="Development"
fi
if [ "${WLS_USER}" != "" ] ; then
JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.management.username=${WLS_USER}"
fi
if [ "${WLS_PW}" != "" ] ; then
JAVA_OPTIONS="${JAVA_OPTIONS} -Dweblogic.management.password=${WLS_PW}"
fi
if [ "${MEDREC_WEBLOGIC_CLASSPATH}" != "" ] ; then
if [ "${CLASSPATH}" != "" ] ; then
CLASSPATH="${CLASSPATH}${CLASSPATHSEP}${MEDREC_WEBLOGIC_CLASSPATH}"
else
CLASSPATH="${MEDREC_WEBLOGIC_CLASSPATH}"
fi
fi
echo "."
echo "."
echo "JAVA Memory arguments: ${MEM_ARGS}"
echo "."
echo "WLS Start Mode=${WLS_DISPLAY_MODE}"
echo "."
echo "CLASSPATH=${CLASSPATH}"
echo "."
echo "PATH=${PATH}"
echo "."
echo "***************************************************"
echo "* To start WebLogic Server, use a username and *"
echo "* password assigned to an admin-level user. For *"
echo "* server administration, use the WebLogic Server *"
echo "* console at http://hostname:port/console *"
echo "***************************************************"
# CLASS CACHING
if [ "${CLASS_CACHE}" = "true" ] ; then
echo "Class caching enabled..."
JAVA_OPTIONS="${JAVA_OPTIONS} -Dlaunch.main.class=${SERVER_CLASS} -Dlaunch.class.path="${CLASSPATH}" -Dlaunch.complete=weblogic.store.internal.LockManagerImpl -cp ${WL_HOME}/server/lib/pcl2.jar"
export JAVA_OPTIONS
SERVER_CLASS="com.oracle.classloader.launch.Launcher"
fi
# START WEBLOGIC
echo "starting weblogic with Java version:"
${JAVA_HOME}/bin/java ${JAVA_VM} -version
if [ "${WLS_REDIRECT_LOG}" = "" ] ; then
echo "Starting WLS with line:"
echo "${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} -Dweblogic.Name=${SERVER_NAME} -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${JAVA_OPTIONS} ${PROXY_SETTINGS} ${SERVER_CLASS}"
${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} -Dweblogic.Name=${SERVER_NAME} -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${JAVA_OPTIONS} ${PROXY_SETTINGS} ${SERVER_CLASS}
else
echo "Redirecting output from WLS window to ${WLS_REDIRECT_LOG}"
${JAVA_HOME}/bin/java ${JAVA_VM} ${MEM_ARGS} -Dweblogic.Name=${SERVER_NAME} -Djava.security.policy=${WL_HOME}/server/lib/weblogic.policy ${JAVA_OPTIONS} ${PROXY_SETTINGS} ${SERVER_CLASS} >"${WLS_REDIRECT_LOG}" 2>&1
fi
stopAll
popd
# Exit this script only if we have been told to exit.
if [ "${doExitFlag}" = "true" ] ; then
exit
fi -
Cookie bug using Administrative Server as part of the Cluster
All using Weblogic 6.0:
Administrative Server running on Windows 2000 Professional
Managed Server running on Windows 2000 Server
Both machines running in the same cluster.
Requests being proxied by the Windows 2000 Professional machine running IIS
Ok, now that you know our test environment, here's a little about our bug.
If we begin an http session with requests being fulfilled by the
administrative server (through the proxy), and shut down and bring the
managed server back up, everything is fine. (No big surprise.)
However, if requests are being fulfilled by the managed server and the
administrator goes down and then comes back up, we get a
"ReplicationManager: object 722399223287670702 not found" error, where the
number seems to refer to value stored in the cookie after the last OR
symbol as shown below.
When the session is created, the cookie contains the following value:
session id =
OnIXh5A6DxUWgBrA2qCLIDN0Co1dewmjdV1ze1isn9Wur2CHl2k2|60563422118895
84610/-1062731365/7001/7002|4648941459387506517/-1062731381/7001/7002|722399
223287670702
When the administrative server goes down, the cookie contains the following
value:
session id =
OnIXh5A6DxUWgBrA2qCLIDN0Co1dewmjdV1ze1isn9Wur2CHl2k2|60563422118895
84610/-1062731365/7001/7002|NONE|722399223287670702
When the administrative server comes back up, the cookie contains the
following value:
session id =
OnIXh5A6DxUWgBrA2qCLIDN0Co1dewmjdV1ze1isn9Wur2CHl2k2|60563422118895
84610/-1062731365/7001/7002|4563245475623454445/-1062731381/7001/7002|722399
223287670702
Its pretty obvious how the cookie id breaks down, information before the
first OR is client info specific to each client, between the first and
second OR is information regarding the first server from the cluster to
fulfill the requests. The info between the second and third is the
identification of the backup server containing the replicated version of the
session. And the last bit of information seems to be an ID referring to the
session object as stored in memory. As you can see, the value that the error
is referring to never changes. SO WHY DOES THE OBJECT GET LOST?
This is a big problem for us, as our resources are limited (as I assume
everyone else's is). Is this just a bug? If so, is there a service pack
already available? If its not a bug, it should be as resolving the bug
allows the administrative server to be part of the cluster saving everyone
the money for an extra machine and (here's the killer) the money for an
extra weblogic license to run on a administrative server separate from the
cluster (in which case it works fine, just costs a whole lot more).
Well, I hope this is clear enough. If not please ask whatever you need to
know. We are looking for any information anyone can provide.
Thank you,
Chad Griffith
Software Engineer
VisionTEK Inc.
[email protected]
To answer your question, fail over works fine, i.e. if a session is
maintained on the managed server, we can shut it down and the session is
transferred to the administrative sever.
The only problem we are having is when the session is on the MANAGED server,
and the ADMIN server goes down and back up WITHOUT any session transfer.
As for shutting down an admin server, you can bring it back up while managed
servers are running by using the -Dweblogic.management.discover=TRUE
setting.
I hope this clarifies everything.
Thanks again,
Chad
"Sioux France" <[email protected]> wrote in message
news:[email protected]...
> Is this an admin server problem though? Can you try the opposite? i.e. IS
it
> possible to connect to the Managed server for your http requests (through
> the proxy)? If so, then shut down and bring back the managed server. I'd
> expect that to go wrong in the same way? Likewise if you shutdown and
bring
> back the admin server in that configuration you would not have a problem?
> "Chad Griffith" <[email protected]> wrote in message
> news:[email protected]...
> > All using Weblogic 6.0:
> > Administrative Server running on Windows 2000 Professional
> > Managed Server running on Windows 2000 Server
> > Both machines running in the same cluster.
> > Requests being proxied by the Windows 2000 Professional machine running
> IIS
> >
> > Ok, now that you know our test environment, here's a little about our
bug.
> > If we begin an http session with requests being fulfilled by the
> > administrative server (through the proxy), and shut down and bring the
> > managed server back up, everything is fine. (No big surprise.)
> >
> > However, if requests are being fulfilled by the managed server and the
> > administrator goes down and then comes back up, we get a
> > "ReplicationManager: object 722399223287670702 not found" error, where
the
> > number seems to refer to value stored in the cookie after the last OR
> > symbol as shown below.
> >
> > When the session is created, the cookie contains the following value:
> > session id =
> > OnIXh5A6DxUWgBrA2qCLIDN0Co1dewmjdV1ze1isn9Wur2CHl2k2|60563422118895
> >
>
84610/-1062731365/7001/7002|4648941459387506517/-1062731381/7001/7002|722399
> > 223287670702
> >
> > When the administrative server goes down, the cookie contains the
> following
> > value:
> > session id =
> > OnIXh5A6DxUWgBrA2qCLIDN0Co1dewmjdV1ze1isn9Wur2CHl2k2|60563422118895
> > 84610/-1062731365/7001/7002|NONE|722399223287670702
> >
> > When the administrative server comes back up, the cookie contains the
> > following value:
> > session id =
> > OnIXh5A6DxUWgBrA2qCLIDN0Co1dewmjdV1ze1isn9Wur2CHl2k2|60563422118895
> >
>
84610/-1062731365/7001/7002|4563245475623454445/-1062731381/7001/7002|722399
> > 223287670702
> >
> > Its pretty obvious how the cookie id breaks down, information before the
> > first OR is client info specific to each client, between the first and
> > second OR is information regarding the first server from the cluster to
> > fulfill the requests. The info between the second and third is the
> > identification of the backup server containing the replicated version of
> the
> > session. And the last bit of information seems to be an ID referring to
> the
> > session object as stored in memory. As you can see, the value that the
> error
> > is referring to never changes. SO WHY DOES THE OBJECT GET LOST?
> >
> > This is a big problem for us, as our resources are limited (as I assume
> > everyone else's is). Is this just a bug? If so, is there a service pack
> > already available? If its not a bug, it should be as resolving the bug
> > allows the administrative server to be part of the cluster saving
everyone
> > the money for an extra machine and (here's the killer) the money for an
> > extra weblogic license to run on a administrative server separate from
the
> > cluster (in which case it works fine, just costs a whole lot more).
> >
> > Well, I hope this is clear enough. If not please ask whatever you need
to
> > know. We are looking for any information anyone can provide.
> >
> > Thank you,
> > Chad Griffith
> > Software Engineer
> > VisionTEK Inc.
> > [email protected]
> >
> >
>
>
Maybe you are looking for
-
Help: Connecting JDeveloper 9.0.2 with Oracle9i Lite
Hello, everyone on OTN! I have installed Oracle 9i Lite and then JDeveloper 9 on WinXP Pro machine. When I was trying to create a new connection using Oracle Lite JDBC 4.0 driver and testing the connection I've got the following message : "Unable to
-
Primo 81 hdmi out.. how to get it working
Hey, I picked up a primo 81 for my wife and we are trying to get it to output to the tv via the hdmi out... Any idea's? The pdf mentions nothing about it.
-
Hi guys! I'm planning to import a file with about 400k records with data loader (insert function). I do this operation with web services and I took about 7 hours. With web services I import about 20k records per time. Someone know if i use dataloader
-
Windows File viewer in JavaFX?
Is there any built in JAVAFX which is similar to the file viewer in windows? Edited by: 901246 on Dec 8, 2011 2:14 AM Edited by: 901246 on Dec 8, 2011 2:15 AM
-
How to Remove Backup files in Rescue & Recovery on local drive
I need more space on my hard drive and for a year have been backing up to an expansion drive. However, I kept the base and one backup on the local drive. I attempted to delete the base backup, since it was listed in "view all backups" on the "loca