Essbase Cluster - Lease manager is no connecting to the DB

Hi All,
This is a tough one for the Gurus :)
We are deploying a EPM 11.1.2.1, all windows except for the Essbase.
The Essbase is a cluster solution running on RHEL 5.3 with a shared repository for the ARBORPATH using OCFS2 as a filesystem. I am also using an Oracle RAC 11G as a DataBase.
I am using opmnctl to start the Essbase, but the StartEssbase.sh ends up with the same errors.
Now I've deploy this sort of solution many many times and never encourtered this error before:
leasemanager.log:
[ESSBASE0] [LM-39] [NOTIFICATION] [16][] [ecid:1347916530705,0] [tid:-13298064] Lease Database Connection Information:
[ESSBASE0] [LM-41] [NOTIFICATION] [16][] [ecid:1347916530705,0] [tid:-13298064] Odbc Driver [DataDirect 6.0 Oracle Wire Protocol]
[ESSBASE0] [LM-40] [NOTIFICATION] [16][] [ecid:1347916530705,0] [tid:-13298064] Host [ora-grid1] and port [1521]
[ESSBASE0] [LM-42] [NOTIFICATION] [16][] [ecid:1347916530705,0] [tid:-13298064] Service Name [prodepm]
[ESSBASE0] [LM-44] [NOTIFICATION] [16][] [ecid:1347916530705,0] [tid:-13298064] User [HSS]
[ESSBASE0] [LM-9] [NOTIFICATION] [16][] [ecid:1347916530705,0] [tid:1090230592] Attempt to connect to database failed with error [[DataDirect][ODBC Oracle Wire Protocol driver][Oracle]TNS-12516: TNS:listener could not find available handler with matching protocol stack].
[ESSBASE0] [LM-9] [ERROR] [32][] [ecid:1347916530705,0] [tid:1090230592] Attempt to connect to database failed with error [[DataDirect][ODBC Oracle Wire Protocol driver][Oracle]TNS-12505: TNS:listener could not resolve SID given in connect descriptor].
[ESSBASE0] [LM-9] [NOTIFICATION] [16][] [ecid:1347916530705,0] [tid:1090230592] Attempt to connect to database failed with error [[DataDirect][ODBC Oracle Wire Protocol driver][Oracle]TNS-12516: TNS:listener could not find available handler with matching protocol stack].
[ESSBASE0] [LM-9] [ERROR] [32][] [ecid:1347916530705,0] [tid:1090230592] Attempt to connect to database failed with error [[DataDirect][ODBC Oracle Wire Protocol driver][Oracle]TNS-12505: TNS:listener could not resolve SID given in connect descriptor].
[ESSBASE0] [LM-9] [NOTIFICATION] [16][] [ecid:1347916530705,0] [tid:1090230592] Attempt to connect to database failed with error [[DataDirect][ODBC Oracle Wire Protocol driver][Oracle]TNS-12516: TNS:listener could not find available handler with matching protocol stack].
[ESSBASE0] [LM-9] [ERROR] [32][] [ecid:1347916530705,0] [tid:1090230592] Attempt to connect to database failed with error [[DataDirect][ODBC Oracle Wire Protocol driver][Oracle]TNS-12505: TNS:listener could not resolve SID given in connect descriptor].
[ESSBASE0] [LM-9] [NOTIFICATION] [16][] [ecid:1347916530705,0] [tid:1090230592] Attempt to connect to database failed with error [[DataDirect][ODBC Oracle Wire Protocol driver][Oracle]TNS-12516: TNS:listener could not find available handler with matching protocol stack].
[ESSBASE0] [LM-9] [ERROR] [32][] [ecid:1347916530705,0] [tid:1090230592] Attempt to connect to database failed with error [[DataDirect][ODBC Oracle Wire Protocol driver][Oracle]TNS-12505: TNS:listener could not resolve SID given in connect descriptor].
[ESSBASE0] [LM-9] [NOTIFICATION] [16][] [ecid:1347916530705,0] [tid:1090230592] Attempt to connect to database failed with error [[DataDirect][ODBC Oracle Wire Protocol driver][Oracle]TNS-12516: TNS:listener could not find available handler with matching protocol stack].
[ESSBASE0] [LM-9] [ERROR] [32][] [ecid:1347916530705,0] [tid:1090230592] Attempt to connect to database failed with error [[DataDirect][ODBC Oracle Wire Protocol driver][Oracle]TNS-12505: TNS:listener could not resolve SID given in connect descriptor].
[ESSBASE0] [LM-9] [NOTIFICATION] [16][] [ecid:1347916530705,0] [tid:1090230592] Attempt to connect to database failed with error [[DataDirect][ODBC Oracle Wire Protocol driver][Oracle]TNS-12516: TNS:listener could not find available handler with matching protocol stack].
[ESSBASE0] [LM-9] [ERROR] [32][] [ecid:1347916530705,0] [tid:1090230592] Attempt to connect to database failed with error [[DataDirect][ODBC Oracle Wire Protocol driver][Oracle]TNS-12505: TNS:listener could not resolve SID given in connect descriptor].
[ESSBASE0] [LM-1] [ERROR] [32][] [ecid:1347916530705,0] [tid:1090230592] Failed to acquire the lease after [6] consecutive attempts.
[ESSBASE0] [LM-16] [NOTIFICATION] [16][] [ecid:1347916530705,0] [tid:1090230592] Lease is being surrendered. [ESSBASE0] [LM-11] [NOTIFICATION] [16][] [ecid:1347916530705,0] [tid:1090230592] Preparing to shutdown abort.
[ESSBASE0] [LM-12] [ERROR] [32][] [ecid:1347916530705,0] [tid:1090230592] Terminating the process.
It is obviously not connecting to the Database to know wich node is the Active-One, but the reason why is still a mistery.
Now the DB connection info is ok, I tested manually and it works like a charm
This are the rest of my logs...just in case:
Essbase.log:
[Mon Sep 17 22:15:28 2012]Local/ESSBASE0///47588224341616/Info(1051283)
Retrieving License Information Please Wait...
[Mon Sep 17 22:15:28 2012]Local/ESSBASE0///47588224341616/Info(1051286)
License information retrieved.
[Mon Sep 17 22:15:28 2012]Local/ESSBASE0///47588224341616/Info(1051216)
JVM Started Successfully !
[Mon Sep 17 22:15:30 2012]Local/ESSBASE0///47588224341616/Info(1051199)
Single Sign-On Initialization Succeeded !
[Mon Sep 17 22:15:30 2012]Local/ESSBASE0///47588224341616/Info(1051232)
Using English_UnitedStates.Latin1@Binary as the Essbase Locale
[Mon Sep 17 22:15:30 2012]Local/ESSBASE0///47588224341616/Info(1056797)
Incremental security backup started by SYSTEM. The file created is [u01/EssbaseServer/essbaseserver1/bin/essbasets_1347916530.bak]
Essbase_ODL.log
[2012-09-17T22:15:28.35-21:15] [ESSBASE0] [AGENT-1283] [NOTIFICATION] [16][] [ecid:1347916528494,0] [tid:-13298064] Retrieving License Information Please Wait...
[2012-09-17T22:15:28.35-21:15] [ESSBASE0] [AGENT-1286] [NOTIFICATION] [16][] [ecid:1347916528494,0] [tid:-13298064] License information retrieved.
[2012-09-17T22:15:28.109-21:15] [ESSBASE0] [AGENT-1216] [NOTIFICATION] [16][] [ecid:1347916528494,0] [tid:-13298064] JVM Started Successfully !
[2012-09-17T22:15:30.468-21:15] [ESSBASE0] [AGENT-1199] [NOTIFICATION] [16][] [ecid:1347916528494,0] [tid:-13298064] Single Sign-On Initialization Succeeded !
[2012-09-17T22:15:30.468-21:15] [ESSBASE0] [NET-17] [ERROR] [16][] [ecid:1347916528494,0] [tid:-13298064] Host Name Not Available
[2012-09-17T22:15:30.513-21:15] [ESSBASE0] [AGENT-1232] [NOTIFICATION] [16][] [ecid:1347916528494,0] [tid:-13298064]
Using English_UnitedStates.Latin1@Binary as the Essbase Locale
[2012-09-17T22:15:30.513-21:15] [ESSBASE0] [NET-17] [ERROR] [16][] [ecid:1347916528494,0] [tid:-13298064] Host Name Not Available
[2012-09-17T22:15:30.782-21:15] [ESSBASE0] [AGENT-6797] [NOTIFICATION] [16][] [ecid:1347916528494,0] [tid:-13298064] Incremental security backup started by SYSTEM. The file created is [u01/EssbaseServer/essbaseserver1/bin/essbasets_1347916530.bak]
I have a SEV1 open with Oracle Support and is escalated to Development
Any help is wellcome...
Thank you all!

Hi All,
Problem solved...
The problem as you know was a connection issue to the Oracle DB from the OPMN, this one tries to connect to the DB (lese manager) to establish who is the active node and since the connection wasn’t happening, all nodes kill themselves as a default action.
After a long troubleshooting with TCP/IP and SQL.net traces we realize that the requests from OPMN existed but the response from the DB was not coming back and the reason why is how the Data Direct driver works. All EPM apps use a JDBC driver, this one is a little bit smarter and once you connect it to the SCAN-VIP it resolves everything automatically, even though we were using an alias for the SCAN-VIP (named oracle-grid). Data Direct drivers is not that smart and need to be connected to the actual SCAN name configured in the Oracle RAC, so while the request was going OK using the alias name (oracle-grid) the response was not, because it needs to have the same name as the SCAN (scan.hostname.com).
Once changed the alias name to the SCAN connection were happening and Essbase started in fail-over mode.
Thank you all for your suggestions!
Cheers,
Pablo.-

Similar Messages

  • Distribution manager failed to connect to the distribution point

    After upgrading my distribution point to windows server 2012 standard I can't distribute content to my distribution point.
    I see the following error.
    source: SMS Server
    Component: SMS_DISTRIBUTION_MANAGER
    message id 2391
    Distribution Manager failed to connect to the distribution point Check your network and firewall settings.
    The firewall is not enabled. 
    wbemtest is able to connect to the remote server that has the distribution point role installed.
    The network access account is working.
    How do I fix this?

    but why does it most of the time work? I did inplace upgrade at least 6 times from 2008 R2 to 2012 R2 and every DP except one works fine.
    I'm not completely sure, but I think, my faulty one, that I'm trying to get working, was working correctly after the inplace upgrade. But as I said, that is only a theory, I'm just curious if that's possible.
    I have the same issue as described above.
    The IT guys from LukOIL

  • My CreativeCloud manager won't connect to the internet. As a result it can't verify my serial number for Adobe Acrobat XI.

    I followed the trouble-shooting steps for this issue, to no avail (Sign in, activation, or connection errors | CS5.5 and later, Acrobat DC). The back story is that I was an independent contractor working for a company and had my own CreativeCloud account. I've since been hired and my boss has opted to purchase a license for Acrobat instead of a CC subscription. He bought the license a few months back, right around the time I cancelled my subscription. But now, the machine I have been using this whole time (PC, Windows 7) is saying I need to renew my subscription when I attempt to run Acrobat. When I click the links, 'Subscription Manager' or 'Have a different Adobe ID?', I get a spinning wheel that eventually times out and tells me 'Please connect to the internet and retry'. At one point I uninstalled the program and reinstalled it, at which point it asked me for a serial number, which I have. I entered the number and as it was trying to verify, it timed out and gave me the same 'Renew your subscription' message.
    Any help would be greatly appreciated. This has been very frustrating.

    Hello - Is the issue still pending

  • Restricting Management to HTTPS Connections on the WRVS4400N

    Where in the web management console is the toggle to restrict management sessions to HTTPS on the WRVS4400N?
    I have found this option on the WRT54G under Mangement 'Server Access' but I can not locate the setting on the WRVS4400N. I assume it must be present as it seems quite silly to drop that security setting an a more complex device with an IDS etc. built in.

    HTTPS is enabled in that location and Remote Management is Disabled because I do not want anyone to be able to manage the unit remotely.
    I want to forbid ANY management (including local) though HTTP. This is a network security requirement.

  • App-Manager does not connect to Firefox OS Simulator on Windows 7

    OS: Windows 7
    Firefox: 28
    Firefox OS 1.2 Simulator 6.0pre8.20140112
    When I start the Simulator it opens fine and I can see a Firefox OS Desktop
    But the App Manager does not connect. The console at the right bottom just says:
    ...connecting to localhost:56455 (the port varies)
    ...connection timeout. Possible causes: didn't click on 'accept' (prompt).
    ...disconnecting
    ...disconnected
    I disabled my firewall, restarted firefox and even the system - did not help
    there is a similiar bug - but I am not sure if we are talking about the same:
    https://support.mozilla.org/en-US/questions/988385
    Thank you

    well - I already knew these links and I can`t find anything helpful there
    anyway, I tried the (unstable) Simulator for 1.3 instead of 1.2
    this one works fine

  • How to find whether any disk arry is connected in the system

    Hi Guys,
    Please help me regarding Disk Array.
    1) What command(s) should I use to check whether any disk array is connected in the server or not.
    2) Please share the method for,
    For single server system (A single sun server is connected with exernal disk array).
    For Cluster server system (Two servers are connected as a sun cluster and Disk array is connected to the cluster as resource).
    3) If the disk array is from SUN or from other vendor, how can i know that?
    4) How to find how many disks are available in the Disk array?
    Thanks

    Wow... I got a reply from nik !!!
    Thanks for your reply..
    *1) I have a confussion that format command only report the local disks not external disks(Disk array). Is that correct?*
    2) We have a cluster server V890+V890 + Disk-Array(Sun StorageTek). The format output is below.
    *(5,6,7 & 8 are disk array?)*
    root# format
    Searching for disks...done
    AVAILABLE DISK SELECTIONS:
    0. c1t0d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
    /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01924a4e1,0
    1. c1t1d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
    /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01a467d91,0
    2. c1t2d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
    /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e019dd3151,0
    3. c1t3d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
    /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01a467321,0
    4. c1t4d0 <SUN146G cyl 14087 alt 2 hd 24 sec 848>
    /pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w500000e01922a001,0
    5. c2t600A0B8000482D560000031B482A46BCd0 <SUN-CSM200_R-0619 cyl 51838 alt 2 hd 512 sec 64>
    /scsi_vhci/ssd@g600a0b8000482d560000031b482a46bc
    6. c2t600A0B8000482D5600000318482A46A6d0 <SUN-CSM200_R-0619 cyl 51838 alt 2 hd 512 sec 64>
    /scsi_vhci/ssd@g600a0b8000482d5600000318482a46a6
    7. c2t600A0B8000482DBC00000659482B59D3d0 <SUN-CSM200_R-0619 cyl 51838 alt 2 hd 512 sec 64>
    /scsi_vhci/ssd@g600a0b8000482dbc00000659482b59d3
    8. c2t600A0B8000482E200000049E482B599Ad0 <SUN-CSM200_R-0619 cyl 51838 alt 2 hd 512 sec 64>
    /scsi_vhci/ssd@g600a0b8000482e200000049e482b599a
    (End 0f output)
    *3) For cfgadm output is given below*
    root# cfgadm -al
    Ap_Id Type Receptacle Occupant Condition
    PCI0 unknown empty unconfigured unknown
    PCI1 unknown empty unconfigured unknown
    PCI2 unknown empty unconfigured unknown
    PCI3 unknown empty unconfigured unknown
    PCI4 scsi/hp connected configured ok
    PCI5 pci-pci/hp connected configured ok
    PCI6 pci-pci/hp connected configured ok
    PCI7 fibre/hp connected configured ok
    PCI8 fibre/hp connected configured ok
    c0 scsi-bus connected configured unknown
    c0::dsk/c0t0d0 CD-ROM connected configured unknown
    c1 fc-private connected configured unknown
    c1::500000e01922a001 disk connected configured unknown
    c1::500000e01924a4e1 disk connected configured unknown
    c1::500000e019dd3151 disk connected configured unknown
    c1::500000e01a467321 disk connected configured unknown
    c1::500000e01a467d91 disk connected configured unknown
    c1::508002000065adb9 ESI connected configured unknown
    c3 scsi-bus connected configured unknown
    c3::rmt/0 tape connected configured unknown
    c4 scsi-bus connected unconfigured unknown
    c5 scsi-bus connected unconfigured unknown
    c6 scsi-bus connected configured unknown
    c6::rmt/1 tape connected configured unknown
    c7 scsi-bus connected unconfigured unknown
    c8 scsi-bus connected unconfigured unknown
    c9 fc-private connected configured unknown
    c9::200600a0b8482dab disk connected configured unknown
    c10 fc-private connected configured unknown
    c10::200500a0b8482dbd disk connected configured unknown
    c11 fc-private connected configured unknown
    c11::200700a0b8482dab disk connected configured unknown
    c12 fc-private connected configured unknown
    c12::200400a0b8482dbd disk connected configured unknown
    usb0/1 unknown empty unconfigured ok
    usb0/2 unknown empty unconfigured ok
    usb0/3 unknown empty unconfigured ok
    usb0/4 unknown empty unconfigured ok
    *4) root# cfgadm -al -o show_FCP_dev*
    Ap_Id Type Receptacle Occupant Condition
    c1 fc-private connected configured unknown
    c1::500000e01922a001,0 disk connected configured unknown
    c1::500000e01924a4e1,0 disk connected configured unknown
    c1::500000e019dd3151,0 disk connected configured unknown
    c1::500000e01a467321,0 disk connected configured unknown
    c1::500000e01a467d91,0 disk connected configured unknown
    c1::508002000065adb9 ESI connected configured unknown
    c9 fc-private connected configured unknown
    c9::200600a0b8482dab,0 disk connected configured unknown
    c9::200600a0b8482dab,1 disk connected configured unknown
    c9::200600a0b8482dab,31 disk connected configured unknown
    c10 fc-private connected configured unknown
    c10::200500a0b8482dbd,0 disk connected configured unknown
    c10::200500a0b8482dbd,1 disk connected configured unknown
    c10::200500a0b8482dbd,31 disk connected configured unknown
    c11 fc-private connected configured unknown
    c11::200700a0b8482dab,0 disk connected configured unknown
    c11::200700a0b8482dab,1 disk connected configured unknown
    c11::200700a0b8482dab,31 disk connected configured unknown
    c12 fc-private connected configured unknown
    c12::200400a0b8482dbd,0 disk connected configured unknown
    c12::200400a0b8482dbd,1 disk connected configured unknown
    c12::200400a0b8482dbd,31 disk connected configured unknown
    Which part of output is indicating diskarry.. Please help me to understand....
    FYI
    root@# more /etc/vfstab
    #device device mount FS fsck mount mount
    #to mount to fsck point type pass at boot options
    #/dev/dsk/c1d0s2 /dev/rdsk/c1d0s2 /usr ufs 1 yes -
    fd - /dev/fd fd - no -
    /proc - /proc proc - no -
    /dev/md/dsk/d103 - - swap - no -
    /dev/md/dsk/d100 /dev/md/rdsk/d100 / ufs 1 no nologging
    /dev/md/dsk/d115 /dev/md/rdsk/d115 /global/.devices/node@1 ufs 2 no global
    swap - /tmp tmpfs - yes -
    /dev/vx/dsk/ossdg/exporthome /dev/vx/rdsk/ossdg/exporthome /export/home ufs 2 no logging
    /devices - /devices devfs - no -
    ctfs - /system/contract ctfs - no -
    objfs - /system/object objfs - no -
    sharefs - /etc/dfs/sharetab sharefs - no -

  • "Failed to connect to the service manager" when I try to add nodes to a cluster on Windows Server 2008 R2

    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]

  • Weblogic managed servers connecting to the servers in different cluster

              Hi All,
              We have a weired problem going on for a while. We have a cluster configuration
              with an admin server and two managed servers. We have the similar configuration
              in DEV, TEST and PROD. The problem is that the managed server members in DEV cluster
              are making connections to managed servers which are member of PROD cluster for
              session replication. The same way TEST servers are trying to connect to PROD and
              DEV.
              Has anyone seen this kind of problem before. BEA seems to be cluless so far.
              Thanks in adavnce for your input.
              Udit
              

              Venkat,
              Thats a good suggestion but these things are too obvious to ignore. We have different
              multicast address in DEV and PROD and also hosts are on different sub net. I do
              not know if cluster name will make any differene though.
              Thanks for your input anyway,
              Udit
              "venkat" <[email protected]> wrote:
              >
              >Udit,
              > You can check the sub net, multicast address and the cluster name.
              >If the dev
              >and prod servers are in the same sub net with same multicast address,
              >then change
              >the multicast and try.
              >
              >Venkat
              >"venkat" <[email protected]> wrote:
              >>
              >>Udit,
              >>
              >>
              >>"Udit Singh" <[email protected]> wrote:
              >>>
              >>>Kumar,
              >>>Thanks for the reply.
              >>>The situation is that managed server in DEV try to replicate the session
              >>>to a
              >>>managed server in PROD and TEST and vice versa.
              >>>Let us say our dev managed servers are running on abc01 and abc02 and
              >>>prod managed
              >>>servers are running on xyz01 and xyz02. All the managed servers are
              >>running
              >>>on
              >>>port 7005.
              >>>If I do the netstat on abc01 or abc02 I could the see established connections
              >>>between abc01/02 and xyz01/02.
              >>>Why is that happening? We are running 6.1SP2.
              >>>
              >>>Udit
              >>>
              >>>Kumar Allamraju <[email protected]> wrote:
              >>>>We do not restrict intercluster communication as of 61 SP3.
              >>>>Once we get the IP from the cookie, we can safely make a
              >>>>connection to the other clustered node. We were not checking
              >>>>if the server is part of the same cluster or not. This is
              >>>>already fixed in 7.x and 61 SP4(not yet released) If you are
              >>>>on 61 Sp2 or SP3 then you should contact support and
              >>>>reference CR # CR089798 to get a one off patch.
              >>>>
              >>>>Regardless, are you traversing from DEV to PROD cluster and
              >>>>vice-versa. If not then this problem shouldn't happen unless
              >>>>plugin is routing the request to wrong cluster.
              >>>>
              >>>>--
              >>>>Kumar
              >>>>
              >>>>Udit Singh wrote:
              >>>>> Hi All,
              >>>>> We have a weired problem going on for a while. We have a cluster
              >>configuration
              >>>>> with an admin server and two managed servers. We have the similar
              >>>configuration
              >>>>> in DEV, TEST and PROD. The problem is that the managed server members
              >>>>in DEV cluster
              >>>>> are making connections to managed servers which are member of PROD
              >>>>cluster for
              >>>>> session replication. The same way TEST servers are trying to connect
              >>>>to PROD and
              >>>>> DEV.
              >>>>> Has anyone seen this kind of problem before. BEA seems to be cluless
              >>>>so far.
              >>>>>
              >>>>> Thanks in adavnce for your input.
              >>>>> Udit
              >>>>
              >>>
              >>
              >
              

  • Starting cluster fails, managed servers can't seem to connect to admin serv

    I have been trying to run the WebLogic JPA example from,
    http://wiki.eclipse.org/EclipseLink/Examples/JPA/CacheCoordination
    but not having much luck on three different Linux machines,
    The first issue I found was if you did not set the memory options just right, the JVM would just hang,
    I am now using,
                   <jvmarg value="-XX:PermSize=512m"/>
                   <jvmarg value="-XX:MaxPermSize=960m"/>
    with JDK 1.7_17, not sure if there are better options...
    The 3 servers are started using (each with different port, all server run on the same machine, as with the admin server),
    <java classname="weblogic.Server"
    fork="true"
    failonerror="true">
    <jvmarg value="-server"/>
    <!--jvmarg value="-Xms512m"/>
    <jvmarg value="-Xmx960m"/-->
                   <jvmarg value="-XX:PermSize=512m"/>
                   <jvmarg value="-XX:MaxPermSize=960m"/>
    <env key="PATH" value="${env.JAVA_HOME}/bin:${env.PATH}"/>
                   <sysproperty key="java.security.egd" value="file:///dev/./urandom"/>
    <sysproperty key="weblogic.Name" value="server1"/>
    <sysproperty key="bea.home" value="${JEE_HOME}"/>
    <sysproperty key="weblogic.management.server" value="${JEE_HOST}:7001"/>
    <sysproperty key="weblogic.management.username" value="${JEE_USER}"/>
    <sysproperty key="weblogic.management.password" value="${JEE_PASSWORD}"/>
    <sysproperty key="java.security.police" value='"${JEE_SERVER}/lib/weblogic.policy"'/>
    <sysproperty key="weblogic.RootDirectory" value="${JEE_DOMAIN}"/>
    <sysproperty key="weblogic.Stdout" value="server1.log"/>
    <sysproperty key="weblogic.Stderr" value="server1.err"/>
    <classpath>
    <fileset dir="${JEE_SERVER}/lib" includes="weblogic.jar,weblogic_sp.jar"/>
    <pathelement location="${env.JAVA_HOME}/lib/tools.jar"/>
    </classpath>
    </java>
    I found that the start-up would sometimes fail on some of the machines unless I used,
                   <sysproperty key="java.security.egd" value="file:///dev/./urandom"/>
    But on once machine this does not help either,
    I also tried using unicast, but still does not start,
    the admin server starts, then the managed servers start and seem to try to connect to the admin server and just never do, never get past STARTING (to STARTED in the log).
    Another have any other ideas?

    How are you starting the managed servers. try running the command
    from /MW_HOME/user_projects/domains/bifoundation_domain/bin
    nohup sh ./startManagedWebLogic.sh bi_server1 http://localhost:7001> start_bi_server1.log &
    and see how it goes. make sure you have set the boot.properties files under security folder so that it wont get failed looking for username and password.
    hope it helps

  • The lease timeout between avaiability group and the Windows Server Failover Cluster has expired

    Hi,
    I am having some issues where I get a lease timeout from time to time.  I have a Windows 2012 Failover Cluster with 2 nodes and 2 SQL 2012 Always-on Availability Groups.  Both nodes
    are a physical machines and each node is the primary for an AG. 
    From what I understand if
    the HealhCheckTimeout
    is exceeded without the signal exchange the lease is declared 'expired' and the SQL Server resource dll reports that the SQL Server availability group no longer 'looks alive' to the Windows cluster manager.  Here are the properties I have setup
    which are the default settings:
    LeaseTimeout - 20000
    HealthCheckTimeout - 30000
    VerboseLoging - 0>
    FailureConditionLevel – 3
    Here are the events that occur in the Application Event Viewer:
    Event ID 19407:
    The lease between availability group 'AG_NAME' and the Windows Server Failover Cluster has expired. A connectivity issue occurred between the instance of SQL Server and the Windows Server Failover
    Cluster. To determine whether the availability group is failing over correctly, check the corresponding availability group resource in the Windows Server Failover Cluster.
    Event ID 35285:
    The recovery LSN (120881:37533:1) was identified for the database with ID 32. This is an informational message only. No user action is required.
    SQl server logs are too long to post in this box but I can send them if you request.
    The AG is setup to failover automatically but it did not failover.  I am trying to figure out why the lease timed out.  Thanks.

    From what I've been able to find out, this is due to an issue with the procedure sp_server_diagnostics.  It sounds like the cluster is expecting this procedure to regularly log good status "Clean" in the log files, but the procedure is designed not
    to flood the logs with "Clean" messages, so only reports changes, and does not make an entry when the last status was "Clean" and the current status is "Clean".  The result is that the cluster looks to be unresponsive.  However, once it initiates
    the failover, the primary machine responds, since it was never really down, and the failover operation stops.   
    The end result is that there really never is a failover, but the database becomes unavailable for  a few minutes while this is resolved.
    I'm going to try setting the cluster's failure condition level to 2 (instead of 3) and see if that prevents the down time.
    blogs.msdn.com/b/sql_pfe_blog/archive/2013/04/08/sql-2012-alwayson-availability-groups-automatic-failover-doesn-t-occur-or-does-it-a-look-at-the-logs.aspx

  • Ent. Manager is not able to connect to the database instance. ORA-12541

    Hi
    I have installed and configured Oracle 10.2.0.1 on a Microsoft Cluster with Windows 2003 Server.
    Database instance and listener are running OK on both cluster nodes.
    On one of the nodes (pwmssrv1) I configured Enterprise Manager to monitor and control the database.
    At the beginning it worked fine, but after making a reboot on this server the Enterprise Manager cannot see the database instance and listener anymore.
    I already recreated/reinstalled EM and the problem persists.
    When I try to access the Oracle EM I get the errors (it do not show the login page):
    Database Instance
    (it shows the red down arrow)
    Host pwmssrv1
    Port 1521
    SID WMS10
    Oracle Home C:\oracle\product\10.2.0\db_1
    Listener
    (it shows the red down arrow)
    Status Down
    Host pwmssrv1
    Port 1521
    Name FSLEFA_BOCWMS_ORA
    Oracle Home C:\oracle\product\10.2.0\db_1
    Location C:\oracle\product\10.2.0\db_1\network\admin
    Details TNS-12541: TNS:no listener
    Agent Connection to Instance
    (it shows the red down arrow)
    Status Failed
    Details ORA-12541: TNS:no listener (DBD ERROR: OCIServerAttach)
    If I do the "emctl status dbconsole" it shows:
    Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0
    Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
    http://pwmssrv1.BOCWMS.COM:1158/em/console/aboutApplication
    Oracle Enterprise Manager 10g is running.
    Logs are generated in directory C:\oracle\product\10.2.0\db_1/pwmssrv1.BOCWMS.CO
    M_wms10/sysman/log
    I also look into the logs and it shows a few errors (emoms.log):
    2010-02-22 17:09:49,000 [HttpRequestHandler-9300338] ERROR conn.ConnectionService verifyRepositoryEx.433 - Invalid Connection Pool. ERROR = Io exception: The Network Adapter could not establish the connection
    2010-02-22 17:09:56,000 [HttpRequestHandler-22569956] WARN jdbc.ConnectionCache _getConnection.303 - Got a fatal exeption when getting a connection; Error code = 17002; Cleaning up cache and retrying
    2010-02-22 17:09:56,000 [HttpRequestHandler-22569956] WARN jdbc.ConnectionCache _getConnection.306 - Io exception: The Network Adapter could not establish the connection
    java.sql.SQLException: Io exception: The Network Adapter could not establish the connection
    2010-02-22 17:09:57,000 [HttpRequestHandler-22569956] ERROR conn.ConnectionService verifyRepositoryEx.433 - Invalid Connection Pool. ERROR = Io exception: The Network Adapter could not establish the connection
    2010-02-22 17:09:57,000 [EMUI_17_09_57_/console/aboutApplication] ERROR em.console doGet.311 - java.lang.IllegalStateException: Response has already been committed
    java.lang.IllegalStateException: Response has already been committed
    Can someone help me on this problem.
    Thanks in advance.
    Jose

    You need to do some troubleshooting to find exact issue...
    Here are some metalink notes,
    How to Verify Agent Connectivity to 'OMS and Repository' Target using emrepresp.pl [ID 472292.1]
    --Database Status Shows Down Getting Error "Failed to Connect to Database Instance: ORA-12541: TNS:no listener " [ID 402227.1]
    --Error While Configuring the Database from the Grid Control Console [ID 750621.1]
    Hope this helps,
    http://www.oracleracexpert.com/
    Oracle RAC Load balancing and failover
    http://www.oracleracexpert.com/2010/01/oracle-rac-load-balancing-and-failover.html
    Download Oracle Grid Control and ASMLib and Install
    http://www.oracleracexpert.com/2009/08/download-oracle-grid-control-and-asmlib.html

  • Creating a new Essbase Cluster on the same Solaris server

    Hi All,
    I have two servers:
    Server1: Foundation services, APS, EAS
    Server2: Essbase Server, Essbase Studio Server on epminstance_1
    Due to business requirements I need to "rename" the Essbase cluster from "EssbaseCluster-1" to something else.. I know this is not possible and from the below document I understand that I need to create a new instance on Server2 and configure Essbase and Essbase Studio on it.
    "How to Rename Essbase Cluster (Doc ID 1434439.1)"
    Goal: In EPM System Release 11.1.2.x, is it possible to rename the Essbase instance and cluster names after they are configured?
    Solution: No, it is not possible to rename the Essbase cluster or instance names after the initial configuration. If you need to change the instance and cluster names, create new instance and cluster. Export the applications from the old cluster and import them into the new cluster.
    My doubt lies with configuring the 2nd Essbase server as I am not clear how a single environment with two Essbase standalone instances on the same physical Solaris server, with each belonging to their own cluster will behave. I know that they are independent clusters and the concept of active/passive and active/active clusters are for Essbase instances part of the same cluster.
    I plan to create a new epminstance_2 instance on Server2 and configure the 2nd Essbase server as follows: give it a *new* cluster name and not assign it to the existing Essbase cluster and deploy it in standalone mode.
    1. Now I plan to use the 1st instance only as a backup option.. In an event where for some reason the new instance were to fail I would start up the services on the older essbase instance. Is this possible without any additional configuration or changes to OPMN?
    2. Alternatively, say we want to remove the older instance. Kindly suggest ways in which I can safely "remove" the older cluster (other than uninstalling). Also when users log in using SmartView, they would see the older and new cluster.. Is there anyways I can get rid of the older cluster without having to uninstall everthing on Server2 and start fresh?
    Thanks!

    Thanks John!
    I have a doubt which I hope you can throw some light now..
    I created a new instance and configured Essbase Server and Studio server on it. So now I have two EPM instances on the same physical server both having Essbase server and Essbase studio server - both Essbase servers belong to different Essbase clusters. Now from the EPM docs I do not find any mention that we can or cannot have multiple instances of Essbase Studio on the same server. Kindly correct me if I am wrong..
    In the deployment report I see two identical entries for the Essbase Studio server in the older epminstance but I do not see Essbase Studio of the 2nd Instance.
    epmsystem_1 (Server2)
                    Essbase Studio Server - 9080
    epmsystem_1 (Server2)
                    Essbase Studio Server - 9080
    After I start up the 2nd Essbase Studio server I tried connecting to it from Essbase Studio Console and got the error "Read permission denied to object folder:\'system'."
    Similarly when I run start_BPMS_bpms1_CommandLineClient.sh and issue the reinit command I get the same error.
    So I stopped the 2nd Essbase Studio server on epmsystem_2 and started up the first Essbase Studio server on epmsystem_1. I was able to connect to it fine from Essbase Studio console and reinit worked too.. I ran a drill through report which worked fine.
    -> So is it that we can have only one instance of Essbase Studio on a single server?
    Also say I want to use the Essbase Studio on the 2nd instance.. Could I re-configure just Essbase server on epmsystem_1 and re-configure Essbase server and Essbase studio server on epmsystem_2 ?
    Thanks,
    Kent

  • Network Manager fails to connect with Huawei E3276 modem after upgrade

    Hi,
    I have Huawei E3276 (lsusb: Huawei Technologies Co., Ltd. E398 LTE/UMTS/GSM Modem/Networkcard).
    I wasn't updating the system for a long time (since KDE 4.14.3), but after upgrade Network Manager can't connect anymore.
    I also tried on the fresh install on different machine (KDE + Plasma 5.3), but I get the same error...
    Error: failed to connect modem: Only IPv4 is supported by this modem.
    I realize that this problem has nothing to do with KDE, but with new version of NM + MM, systemd, dhcpcd or dhclient?
    Why now Network Manager don't use ppp like before upgrade (different connection type "cdc-wdm0")?
    I would be grateful for any advice.
    After upgrade (KDE 4.14.3 -> 15.04 apps/5.2 plasma):
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: starting connection 'Orange'
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) started...
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> NetworkManager state is now CONNECTING
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: prepare -> need-auth (reason 'none') [40 60 0]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) complete.
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) started...
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) complete.
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect started...
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (4/8): Wait to get fully enabled
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (5/8): Register
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (6/8): Bearer
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Simple connect state (7/8): Connect
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    may 07 17:18:58 AsusN56VZ ModemManager[358]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> registered)
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): modem state changed, 'connecting' --> 'registered' (reason: user-requested)
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <warn> (cdc-wdm0) failed to connect modem: Only IPv4 is supported by this modem
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: prepare -> failed (reason '(null)') [40 120 1]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> NetworkManager state is now DISCONNECTED
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> Disabling autoconnect for connection 'Orange'.
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <warn> (cdc-wdm0): Activation: failed for connection 'Orange'
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): device state change: failed -> disconnected (reason 'none') [120 30 0]
    may 07 17:18:58 AsusN56VZ NetworkManager[239]: <info> (cdc-wdm0): deactivating device (reason 'none') [0]
    Before upgrade (KDE 4.14)
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) starting connection 'Orange'
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> NetworkManager state is now CONNECTING
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) scheduled...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) started...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) complete.
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect started...
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (4/8): Wait to get fully enabled
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (5/8): Register
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (6/8): Bearer
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (7/8): Connect
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1) modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <warn> (ttyUSB0): port attributes not fully set
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
    mar 23 19:31:33 AsusN56VZ ModemManager[267]: <info> Simple connect state (8/8): All done
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1) modem state changed, 'connecting' --> 'connected' (reason: user-requested)
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <warn> (ttyUSB0): failed to look up interface index
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) scheduled...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) starting...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1): device state change: prepare -> config (reason 'none') [40 50 0]
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) successful.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) scheduled.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) complete.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) started...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> (ttyUSB1): device state change: config -> ip-config (reason 'none') [50 70 0]
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> using modem-specified IP timeout: 20 seconds
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> starting PPP connection
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> pppd started with pid 780
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) complete.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) started...
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    mar 23 19:31:33 AsusN56VZ pppd[780]: Plugin /usr/lib/pppd/2.4.6/nm-pppd-plugin.so loaded.
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: Plugin /usr/lib/pppd/2.4.6/nm-pppd-plugin.so loaded.
    mar 23 19:31:33 AsusN56VZ kernel: PPP generic driver version 2.4.2
    mar 23 19:31:33 AsusN56VZ pppd[780]: pppd 2.4.6 started by root, uid 0
    mar 23 19:31:33 AsusN56VZ pppd[780]: Using interface ppp0
    mar 23 19:31:33 AsusN56VZ pppd[780]: Connect: ppp0 <--> /dev/ttyUSB0
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: Using interface ppp0
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: Connect: ppp0 <--> /dev/ttyUSB0
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: <warn> /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring...
    mar 23 19:31:33 AsusN56VZ pppd[780]: CHAP authentication succeeded: Welcome!!
    mar 23 19:31:33 AsusN56VZ pppd[780]: CHAP authentication succeeded
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: CHAP authentication succeeded: Welcome!!
    mar 23 19:31:33 AsusN56VZ NetworkManager[268]: CHAP authentication succeeded
    mar 23 19:31:33 AsusN56VZ kernel: PPP BSD Compression module registered
    mar 23 19:31:33 AsusN56VZ kernel: PPP Deflate Compression module registered
    mar 23 19:31:35 AsusN56VZ ModemManager[267]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: access technology changed (umts -> hspa-plus)
    mar 23 19:31:35 AsusN56VZ NetworkManager[268]: <info> PPP manager(IP Config Get) reply received.
    mar 23 19:31:35 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    mar 23 19:31:35 AsusN56VZ NetworkManager[268]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Commit) started...
    Linux Mint 17.1 KDE (works the same like Arch before update)
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) starting connection 'Orange Standard access - with image compression'
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> NetworkManager state is now CONNECTING
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) scheduled...
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) started...
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 1 of 5 (Device Prepare) complete.
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Simple connect started...
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Simple connect state (3/8): Enable
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
    May 7 20:06:33 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'disabled' --> 'enabling' (reason: user-requested)
    May 7 20:06:33 mint17-vm ModemManager[781]: <warn> (ttyUSB1): port attributes not fully set
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering)
    May 7 20:06:33 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
    May 7 20:06:34 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: signal quality updated (80)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (4/8): Wait to get fully enabled
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (5/8): Register
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (6/8): Bearer
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'enabling' --> 'registered' (reason: user-requested)
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> WWAN now enabled by management service
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (7/8): Connect
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: signal quality updated (77)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: access technology changed (unknown -> lte)
    May 7 20:06:35 mint17-vm ModemManager[781]: <warn> (ttyUSB0): port attributes not fully set
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
    May 7 20:06:35 mint17-vm ModemManager[781]: <info> Simple connect state (8/8): All done
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1) modem state changed, 'connecting' --> 'connected' (reason: user-requested)
    May 7 20:06:35 mint17-vm NetworkManager[835]: <warn> (ttyUSB0): failed to look up interface index
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) scheduled...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) starting...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: prepare -> config (reason 'none') [40 50 0]
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) successful.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) scheduled.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 2 of 5 (Device Configure) complete.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) started...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: config -> ip-config (reason 'none') [50 70 0]
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> using modem-specified IP timeout: 20 seconds
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> starting PPP connection
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> pppd started with pid 2468
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 3 of 5 (IP Configure Start) complete.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) started...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) complete.
    May 7 20:06:35 mint17-vm pppd[2468]: Plugin /usr/lib/i386-linux-gnu/pppd/2.4.5/nm-pppd-plugin.so loaded.
    May 7 20:06:35 mint17-vm pppd[2468]: pppd 2.4.5 started by root, uid 0
    May 7 20:06:35 mint17-vm pppd[2468]: Using interface ppp0
    May 7 20:06:35 mint17-vm pppd[2468]: Connect: ppp0 <--> /dev/ttyUSB0
    May 7 20:06:35 mint17-vm NetworkManager[835]: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
    May 7 20:06:35 mint17-vm NetworkManager[835]: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <warn> /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring...
    May 7 20:06:35 mint17-vm pppd[2468]: CHAP authentication succeeded: Welcome!!
    May 7 20:06:35 mint17-vm pppd[2468]: CHAP authentication succeeded
    May 7 20:06:35 mint17-vm kernel: [ 82.363825] PPP BSD Compression module registered
    May 7 20:06:35 mint17-vm kernel: [ 82.368188] PPP Deflate Compression module registered
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> PPP manager(IP Config Get) reply received.
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    May 7 20:06:35 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Commit) started...
    May 7 20:06:36 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
    May 7 20:06:36 mint17-vm NetworkManager[835]: <info> Activation (ttyUSB1) Stage 5 of 5 (IPv4 Commit) complete.
    May 7 20:06:36 mint17-vm NetworkManager[835]: <info> (ttyUSB1): device state change: secondaries -> activated (reason 'none') [90 100 0]
    May 7 20:06:36 mint17-vm NetworkManager[835]: <info> NetworkManager state is now CONNECTED_GLOBAL
    Last edited by Shocker (2015-05-07 19:18:43)

    This week, after update, modem works again.
    However, there's a new bug in the kernel, which was not there before:
    kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
    but the modem works and connects to the network.
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> Auto-activating connection 'Orange'.
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: starting connection 'Orange'
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) scheduled...
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) started...
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> NetworkManager state is now CONNECTING
    may 24 09:32:44 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 1 of 5 (Device Prepare) complete.
    may 24 09:32:44 AsusN56VZ ModemManager[338]: <info> Simple connect started...
    may 24 09:32:44 AsusN56VZ ModemManager[338]: <info> Simple connect state (1/8): Unlock check
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Simple connect state (2/8): Wait to get fully initialized
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (locked -> initializing)
    may 24 09:32:47 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2: unknown notification 3 received: index 2 len 4
    may 24 09:32:47 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2: unknown notification 3 received: index 2 len 4
    may 24 09:32:47 AsusN56VZ ModemManager[338]: Invalid mobile equipment error code: 50
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (initializing -> disabled)
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Simple connect state (3/8): Enable
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (disabled -> enabling)
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <warn> (ttyUSB1): port attributes not fully set
    may 24 09:32:47 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'locked' --> 'disabled' (reason: unknown)
    may 24 09:32:47 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'disabled' --> 'enabling' (reason: user preference)
    may 24 09:32:47 AsusN56VZ NetworkManager[342]: <warn> (cdc-wdm0) failed to enable modem: GDBus.Error:org.freedesktop.ModemManager1.Error.Core.InProgress: Cannot enable modem: already being enabled
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (unknown -> registering)
    may 24 09:32:47 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: 3GPP Registration state changed (registering -> home)
    may 24 09:32:48 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2: unknown notification 3 received: index 2 len 4
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (enabling -> registered)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (4/8): Wait to get fully enabled
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (5/8): Register
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (6/8): Bearer
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'enabling' --> 'registered' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (7/8): Connect
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> registered)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'connecting' --> 'registered' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect started...
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (4/8): Wait to get fully enabled
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (5/8): Register
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (6/8): Bearer
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (7/8): Connect
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (registered -> connecting)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'registered' --> 'connecting' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Modem /org/freedesktop/ModemManager1/Modem/0: state changed (connecting -> connected)
    may 24 09:33:08 AsusN56VZ ModemManager[338]: <info> Simple connect state (8/8): All done
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): modem state changed, 'connecting' --> 'connected' (reason: user-requested)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) scheduled...
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) starting...
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: prepare -> config (reason 'none') [40 50 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) successful.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 2 of 5 (Device Configure) complete.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 3 of 5 (IP Configure Start) scheduled.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 3 of 5 (IP Configure Start) started...
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: config -> ip-config (reason 'none') [50 70 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> Activation (wwp0s20u2i2) Beginning DHCPv4 transaction (timeout in 15 seconds)
    may 24 09:33:08 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
    may 24 09:33:08 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
    may 24 09:33:08 AsusN56VZ kernel: huawei_cdc_ncm 3-2:1.2 wwp0s20u2i2: kevent 12 may have been dropped
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> dhclient started with pid 3624
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): IPv6 configuration disabled
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 3 of 5 (IP Configure Start) complete.
    may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPDISCOVER on wwp0s20u2i2 to 255.255.255.255 port 67 interval 7
    may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPREQUEST on wwp0s20u2i2 to 255.255.255.255 port 67
    may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPOFFER from 10.X.X.X
    may 24 09:33:08 AsusN56VZ dhclient[3624]: DHCPACK from 10.X.X.X
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> address 10.X.X.X
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> plen 30 (255.255.255.252)
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> gateway 10.X.X.X
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> server identifier 10.X.X.X
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> lease time 518400
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> nameserver '194.X.X.X'
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> nameserver '194.X.X.X'
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (wwp0s20u2i2): DHCPv4 state changed unknown -> bound
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 5 of 5 (IPv4 Configure Commit) scheduled...
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 5 of 5 (IPv4 Commit) started...
    may 24 09:33:08 AsusN56VZ avahi-daemon[1326]: Joining mDNS multicast group on interface wwp0s20u2i2.IPv4 with address 10.X.X.X.
    may 24 09:33:08 AsusN56VZ avahi-daemon[1326]: New relevant interface wwp0s20u2i2.IPv4 for mDNS.
    may 24 09:33:08 AsusN56VZ avahi-daemon[1326]: Registering new address record for 10.X.X.X on wwp0s20u2i2.IPv4.
    may 24 09:33:08 AsusN56VZ dhclient[3624]: bound to 10.X.X.X -- renewal in 252436 seconds.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: Stage 5 of 5 (IPv4 Commit) complete.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): device state change: secondaries -> activated (reason 'none') [90 100 0]
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> NetworkManager state is now CONNECTED_LOCAL
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> NetworkManager state is now CONNECTED_GLOBAL
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> Policy set 'Orange' (wwp0s20u2i2) as default for IPv4 routing and DNS.
    may 24 09:33:08 AsusN56VZ NetworkManager[342]: <info> Writing DNS information to /usr/bin/resolvconf
    may 24 09:33:09 AsusN56VZ NetworkManager[342]: <info> (cdc-wdm0): Activation: successful, device activated.

  • Essbase Cluster COPYAPP very slow

    Hello,
    I set the Essbase cluster version 11.1.2, and when I trying to copyapp using esscmd it very slow compare to preveouse version none weblogic v11
    on version 11 copy application 1.2GB take 3 min
    on new version 11.1.2 copy application takes more then 10 min
    what could be wrong that I set, or area that I can take look
    thank you,

    Hi Prateek ,
    First and best way to see what is happening with this particular node would be to set the following trace sections with full verbose tracing :
    folders*,requestaudit,systemdatabase,socketrequest
    With these tracing sections set access from DIS 2nd node and wait till the final results come .
    Once either the folders show up or operation times out navigate to View server output and refresh the section , capture the logs to see if there is any particular section that creates this bottleneck .
    Also check how good is the connection from DIS to the second node host machine ? That also might create a specific issue like this .
    Thanks,
    Srinath

  • WebLogic Cluster 2 Managed Servers

    Hi all,
    Description: 2 virtual machines configured in cluster:
    ManagedServer1: 172.31.10.76 on port 7780 (here is also AdminServer on port 7001)
    ManagedServer2: 172.31.10.77 on port 7780
    Everything seems to be working. I was able to deploy a war file which could tell me the ip address of the server. Everything seems to be all right. However I have some questions:
    On a third machine I have Oracle 11g and I want to deploy application through the AdminServer to both of my ManagedServers but to use the db of the third server 172.31.10.78. Well I managed to do this however I can not log in through the login page of my web application. I get the following error:
    <Aug 30, 2011 11:13:13 AM PDT> <Error> <HTTP> <BEA-101020> <[ServletContext@1072316483[app:manager module:manager.war path:/manager spec-version:2.5]] Servlet failed with Exception
    org.springframework.transaction.CannotCreateTransactionException: Could not open JPA EntityManager for transaction; nested exception is javax.persistence.PersistenceException: Exception [EclipseLink-28013] (Eclipse Persistence Services - 2.0.2.v20100323-r6872): org.eclipse.persistence.exceptions.EntityManagerSetupException
    Exception Description: Attempted to deploy PersistenceUnit [ApplicationEntityManager] while being in the wrong state [DeployFailed]. Close all factories for this PersistenceUnit.
    at org.springframework.orm.jpa.JpaTransactionManager.doBegin(JpaTransactionManager.java:375)
    at org.springframework.transaction.support.AbstractPlatformTransactionManager.getTransaction(AbstractPlatformTransactionManager.java:374)
    at org.springframework.transaction.interceptor.TransactionAspectSupport.createTransactionIfNecessary(TransactionAspectSupport.java:263)
    at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:101)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    Truncated. see log file for complete stacktrace
    Caused By: javax.persistence.PersistenceException: Exception [EclipseLink-28013] (Eclipse Persistence Services - 2.0.2.v20100323-r6872): org.eclipse.persistence.exceptions.EntityManagerSetupException
    Exception Description: Attempted to deploy PersistenceUnit [ApplicationEntityManager] while being in the wrong state [DeployFailed]. Close all factories for this PersistenceUnit.
    at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:307)
    at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.getServerSession(EntityManagerFactoryImpl.java:151)
    at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:207)
    at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:195)
    at org.springframework.orm.jpa.JpaTransactionManager.createEntityManagerForTransaction(JpaTransactionManager.java:392)
    Truncated. see log file for complete stacktrace
    Caused By: Exception [EclipseLink-28013] (Eclipse Persistence Services - 2.0.2.v20100323-r6872): org.eclipse.persistence.exceptions.EntityManagerSetupException
    Exception Description: Attempted to deploy PersistenceUnit [ApplicationEntityManager] while being in the wrong state [DeployFailed]. Close all factories for this PersistenceUnit.
    at org.eclipse.persistence.exceptions.EntityManagerSetupException.cannotDeployWithoutPredeploy(EntityManagerSetupException.java:170)
    at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.deploy(EntityManagerSetupImpl.java:307)
    at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.getServerSession(EntityManagerFactoryImpl.java:151)
    at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManagerImpl(EntityManagerFactoryImpl.java:207)
    at org.eclipse.persistence.internal.jpa.EntityManagerFactoryImpl.createEntityManager(EntityManagerFactoryImpl.java:195)
    Truncated. see log file for complete stacktrace
    I have also setup a DataSources with the appropriet settings - from tests I see I am able to connect to the db however I can not log in so I think there is something with the db. I`m not sure if I have Cluster with 2 Managed Servers which option I need to use DataSources or MultiData Sources. I may be wrong I do not know I`m new to clusters and weblogic but I`m very happy that after 2 days I was able to do all this :).
    Any help is much appreciated.
    Thank you.

    Do you have any rewrites configured in Apache?
    This (Middleware Snippets: Session Management Using WebLogic 12c) includes some examples to configure the WebLogic plug-in.
    LoadModule weblogic_module modules/mod_wl.so
    <IfModule weblogic_module>
      ConnectTimeoutSecs 10
      ConnectRetrySecs 2
      DebugConfigInfo ON
      WLSocketTimeoutSecs 2
      WLIOTimeoutSecs 300
      Idempotent ON
      FileCaching ON
      KeepAliveSecs 20
      KeepAliveEnabled ON
      DynamicServerList ON
      WLProxySSL OFF
    </IfModule>
    <Location /SessionTest>
      SetHandler weblogic-handler
      WebLogicCluster <%= @WEBLOGIC_CLUSTER_ADDRESS %>
    </Location>
    <Location /SpringHibernate>
      SetHandler weblogic-handler
      WebLogicCluster <%= @WEBLOGIC_CLUSTER_ADDRESS %>
    </Location>

Maybe you are looking for

  • Acrobat X & XI add-in Word 2010 32-bit cause macro error messages

    When I enable Acrobat COM add-in in Word 2010 32-bit, when I close Word and re-open Word, I receive the following This dialog screen pops up three consecutive times after I click on "OK" three consecutive instances. The add-in works great in Outlook

  • HP 110-210 Doesn't Want to Turn On!

    Hello internet, My first post on here so bare with me but I'll try my best to be as detaield as possible. I've had my HP 110-210 Desktop for about 2 years now, and I've had no issues with it up until this past week. I was using the system doing regul

  • Sticky Hide and Show

    Hi! Referring to this packaged app from OTN: http://www.oracle.com/technology/products/database/application_express/packaged_apps/packaged_apps.html#STICKY How can I view the apex_show_hide_region.js source? Thx! Marc

  • Why does iPhone/Ipad still sync email after changing Exchange\Windows Server AD password !?

    Has anyone noticed this issue before? A user changes their office network password but it takes anywhere from 2 days to more than a week before the iPhone notices and prompts the user to enter their new password. But not only that, users can still ac

  • Just cant connect wireless wrt54g2

    i just cant get the wireless to work. and when i try the software we get the following....