Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 14 Oracle Analytics Lounge
- 208 Oracle Analytics News
- 41 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 76 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
startWebLogic.sh job is stuck in obiee12c
Hi,
I have moved completed the following step as per link
https://docs.oracle.com/middleware/1221/biee/BIESC/privileges.htm#CJAFBFID
ORACLE_HOME/bi/plugins/security/bi-sql-group-provider.jar
You must copy the file to the following location:
ORACLE_HOME/wlserver/server/lib/mbeantypes
After this step i have stopped the script stopWebLogic.sh , but when i start the script startWebLogic.sh its gets stuck
<May 12, 2017, 6:09:55,695 PM UTC> <Notice> <WebLogicServer> <BEA-000360> <The server started in RUNNING mode.>
<May 12, 2017, 6:09:55,702 PM UTC> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING.>
After load: Instance: obips1
OBIPS -> OBIPS.obips1 tcp(s)://unknownhost.example.com:9507(9507)/ - System Component
Instance: obijh1
OBIJH -> OBIJH.obijh1 tcp(s)://unknownhost.example.com:9510(9510)/ - System Component
Instance: obiccs1
OBICCS_MONITOR -> OBICCS_MONITOR.obiccs1 tcp(s)://unknownhost.example.com:9509(9509)/ - System Component
OBICCS -> OBICCS.obiccs1 tcp(s)://unknownhost.example.com:9508(9508)/ - System Component
Instance: obisch1
OBISCH_SCRIPT -> OBISCH_SCRIPT.obisch1 tcp(s)://unknownhost.example.com:9513(9513)/ - System Component
OBISCH -> OBISCH.obisch1 tcp(s)://unknownhost.example.com:9511(9511)/ - System Component
OBISCH_MONITOR -> OBISCH_MONITOR.obisch1 tcp(s)://unknownhost.example.com:9512(9512)/ - System Component
Instance: obis1
OBIS -> OBIS.obis1 tcp(s)://unknownhost.example.com:9514(9514)/ - System Component
OBIS_MONITOR -> OBIS_MONITOR.obis1 tcp(s)://unknownhost.example.com:9515(9515)/ - System Component
skinMapping
Or
<May 12, 2017, 7:08:28,867 PM UTC> <Warning> <JMX> <BEA-149535> <JMX Resiliency Activity Server=bi_server1 :
Received a CONNECT EVENT
>
<May 12, 2017, 7:08:28,868 PM UTC> <Warning> <JMX> <BEA-149535> <JMX Resiliency Activity Server=bi_server1 : Starting JMX connection. forceReconnect value: false>
<May 12, 2017, 7:08:28,907 PM UTC> <Warning> <JMX> <BEA-149535> <JMX Resiliency Activity Server=bi_server1 : Registering call backs for server>
<May 12, 2017, 7:08:28,907 PM UTC> <Warning> <JMX> <BEA-149535> <JMX Resiliency Activity Server=bi_server1 : Initializing callbacks>
<May 12, 2017, 7:08:28,908 PM UTC> <Warning> <JMX> <BEA-149535> <JMX Resiliency Activity Server=bi_server1 : Added MBeanServerConnection in DomainRuntimeServiceMBean >
<May 12, 2017, 7:08:31,905 PM UTC> <Warning> <JMX> <BEA-149535> <JMX Resiliency Activity Server=bi_server1 : Callback is done>
<May 12, 2017, 7:08:31,905 PM UTC> <Warning> <JMX> <BEA-149506> <Established JMX Connectivity with bi_server1 at the JMX Service URL of service:jmx:t3://10.14.155.25:9502/jndi/weblogic.management.mbeanservers.runtime.>
<May 12, 2017, 7:08:31,908 PM UTC> <Warning> <JMX> <BEA-149535> <JMX Resiliency Activity Server=bi_server1 : Server is reachable, after a single attempt. Will return from the retry.>
I tried this on 2 different servers First one is from one host & second is from another host.
Both are Oracle Business Intelligence 12.2.1.2.0
Please let me know if there is anything iam missing?
Answers
-
Sorry but what are you asking?
startWeblogic get stuck but you get the RUNNING state? So it's running?
0 -
the linux terminal wont return it displaying the same lines which i pasted in the correspondance for more than an hour.
Iam not sure why its not returning the prompt, i thought it got stuck at that point.
Is there any way i can check if weblogic started successfully?
0 -
Hi -
Is there any way i can check if weblogic started successfully?
Yes, when it shows that is is in 'RUNNING' mode. it is as simple as that. That is the state that indicates that Weblogic Server (admin or managed) has successfully started. Also you can go to your WebLogic Console. Should be something like {server_name}:7001/console.
What is confusing you is that script is running in foreground mode - basically, it is printing all of the output to the screen. Once it reaches the RUNNING point, it is finished. Beyond that, you'll begin to see "logging" messages as any activity happens with the application. This is probably not the best way to start it. Unless, you have a VNC session available, you could run it in there and just leave it (again, probably not the recomended approach). If you were to hit CTRL + C at that prompt, it will immediately kill Weblogic and return you to the command prompt.
Take a look at this discussion:
There are many, many more discussions, notes about this. The good news is that the script is working .
Regards,
Charles
0 -
If you like something official, refer to this: https://docs.oracle.com/middleware/12212/wls/START/overview.htm#START117
0 -
There are few blogs on Linux random number entropy issue. We had suffered that. Check if you are hitting it.
How to Diagnose a Linux Entropy Issue on WebLogic Server Instances (Doc ID 1574979.1)
Thanks
Arijit
0 -
Honestly I have the feeling you are trying to make things complicated when they can be easy ....
Why are you starting components one by one by hand?
Use the start.sh script provided: it does everything and will run all the pieces in the background, so you keep your session once the script succeed. In the same way you have stop.sh stopping everything.
These 2 scripts are great because to take care of all the pieces: node manager, admin server, managed server, services, everything started in the right sequence.
0 -
thanks all for the inputs going fwd i will run start / stop scripts instead of individual ones.
0 -
Use the start.sh script provided: it does everything and will run all the pieces in the background, so you keep your session once the script succeed. In the same way you have stop.sh stopping everything.These 2 scripts are great because to take care of all the pieces: node manager, admin server, managed server, services, everything started in the right sequence.
Good tip! They don't have this in 11g. Much easier ...
0
