Cisco PI 2.0 Configuration Archive fails Nexus 5000
Hi,
we recently upgraded Cisco PI from 1.3 to 2.0 and i thought this problem would be solved but it did not. I have added two Nexus 5548 switches that i can monitor and configure through Cisco Prime but im not able to read the running och startup config to the Configuration Archive. When i run the job i get the following error:
"fig from device: java.net.SocketTimeoutException: Read timed out"
Current NXOS: 5.2(1)N1(2a)
Before i proceed troubleshooting i just would like an answer if it should be possible to archive configs from Nexus to Cisco Prime Infrastructure?
Cheers! // Mattias Andersson
Thanks for the quick reply! Well, i did some more troubleshooting and i noticed that through Ethanalyzer and inspected the telnet packets that Prime tries to set the terminal lenght and width before it shows the running-config but it fails as it is in the default role of priv-0, and therefore gets % Permission denied. So, it times out after 2,5 min.
I added these two lines and worked like a charm!
role name priv-0
rule 12 permit command terminal length *
rule 11 permit command terminal width *
Similar Messages
-
Cisco Prime Infrastructure Scheduled Configuration Archive not executing
We have a deployment of Cisco Prime Infrastrcuture 1.3 (1.3.0.20).
Configuration Archive is a feature that collects and archives the device configurations i.e. cisco switches.
You have an option to schedule this to run, say daily, weekly etc. Once scheduled you can see it in the "Jobs Dashboard" and with the "next start time" of what you configured. I have a situation whereby the time it is suppose to start - it doesnt - howevere flags the job as a "success". Not newe device configurations are archived and the "next start time" remain the same. Its almost like it is failing to execute, but some other process under the hood thinks that it was been executed correctly?
Any ideas or experience that could help here would be appreciated!Some extra info that has just come to my attention. At one point we were running (we're actually still running) CiscoWorks with LMS3.2 and Cisco NCS 1.x. I merged these two things together into Cisco Prime Infrastructure (upgraded the licensing to get 450 lifecycle licenses to cover the APs + all of the devices coming from LMS3.2). I followed all of the documented procedures to upgrade the NCS appliance to Prime Infrastructure. But when I type "show application" from the CLI of the NCS appliance (now the Prime Infrastructure appliance) I see this:
HQ-NCS1/admin# show application
NCS Cisco Prime Network Control System
Is that normal? Maybe this is my problem. Should this output list "Cisco Prime Infrastructure" instead of (or in addtion to) Cisco Prime Network Control System? When I login to the GUI it shows "Cisco Prime Infrastructure" and the GUI has changed considerably (menus are different) so I'm assuming that the application upgrades I launched from the CLI to go to Prime Infrastructure worked fine. -
Default Configuration Lines on Nexus 5000
What is the purpose of these default configuration lines? What do they mean? I can't find an explanation of them anywhere. I believe some are written to the config when FCoE is enabled....
I would like to know exactly what they are doing.
I DO have an idea but I would like to have each line explained, one at a time, so that I can understand how Cisco implements PFC and ETS and how they identify system classes, etc....
class-map type qos class-fcoe
class-map type queuing class-fcoe
match qos-group 1
class-map type queuing class-all-flood
match qos-group 2
class-map type queuing class-ip-multicast
match qos-group 2
class-map type network-qos class-fcoe
match qos-group 1
class-map type network-qos class-all-flood
match qos-group 2
class-map type network-qos class-ip-multicast
match qos-group 2
system qos
service-policy type qos input fcoe-default-in-policy
service-policy type queuing input fcoe-default-in-policy
service-policy type queuing output fcoe-default-out-policy
service-policy type network-qos fcoe-default-nq-policyWhat is the purpose of these default configuration lines? What do they mean? I can't find an explanation of them anywhere. I believe some are written to the config when FCoE is enabled....
I would like to know exactly what they are doing.
I DO have an idea but I would like to have each line explained, one at a time, so that I can understand how Cisco implements PFC and ETS and how they identify system classes, etc....
class-map type qos class-fcoe
class-map type queuing class-fcoe
match qos-group 1
class-map type queuing class-all-flood
match qos-group 2
class-map type queuing class-ip-multicast
match qos-group 2
class-map type network-qos class-fcoe
match qos-group 1
class-map type network-qos class-all-flood
match qos-group 2
class-map type network-qos class-ip-multicast
match qos-group 2
system qos
service-policy type qos input fcoe-default-in-policy
service-policy type queuing input fcoe-default-in-policy
service-policy type queuing output fcoe-default-out-policy
service-policy type network-qos fcoe-default-nq-policy -
VPC on Nexus 5000 with Catalyst 6500 (no VSS)
Hi, I'm pretty new on the Nexus and UCS world so I have some many questions I hope you can help on getting some answers.
The diagram below is the configuration we are looking to deploy, that way because we do not have VSS on the 6500 switches so we can not create only one Etherchannel to the 6500s.
Our blades inserted on the UCS chassis have INTEL dual port cards, so they do not support full failover.
Questions I have are.
- Is this my best deployment choice?
- vPC highly depend on the management interface on the Nexus 5000 for the keep alive peer monitoring, so what is going to happen if the vPC brakes due to:
- one of the 6500 goes down
- STP?
- What is going to happend with the Etherchannels on the remaining 6500?
- the Management interface goes down for any other reason
- which one is going to be the primary NEXUS?
Below is the list of devices involved and the configuration for the Nexus 5000 and 65000.
Any help is appreciated.
Devices
· 2 Cisco Catalyst with two WS-SUP720-3B each (no VSS)
· 2 Cisco Nexus 5010
· 2 Cisco UCS 6120xp
· 2 UCS Chassis
- 4 Cisco B200-M1 blades (2 each chassis)
- Dual 10Gb Intel card (1 per blade)
vPC Configuration on Nexus 5000
TACSWN01
TACSWN02
feature vpc
vpc domain 5
reload restore
reload restore delay 300
Peer-keepalive destination 10.11.3.10
role priority 10
!--- Enables vPC, define vPC domain and peer for keep alive
int ethernet 1/9-10
channel-group 50 mode active
!--- Put Interfaces on Po50
int port-channel 50
switchport mode trunk
spanning-tree port type network
vpc peer-link
!--- Po50 configured as Peer-Link for vPC
inter ethernet 1/17-18
description UCS6120-A
switchport mode trunk
channel-group 51 mode active
!--- Associates interfaces to Po51 connected to UCS6120xp-A
int port-channel 51
swithport mode trunk
vpc 51
spannig-tree port type edge trunk
!--- Associates vPC 51 to Po51
inter ethernet 1/19-20
description UCS6120-B
switchport mode trunk
channel-group 52 mode active
!--- Associates interfaces to Po51 connected to UCS6120xp-B
int port-channel 52
swithport mode trunk
vpc 52
spannig-tree port type edge trunk
!--- Associates vPC 52 to Po52
!----- CONFIGURATION for Connection to Catalyst 6506
Int ethernet 1/1-3
description Cat6506-01
switchport mode trunk
channel-group 61 mode active
!--- Associate interfaces to Po61 connected to Cat6506-01
Int port-channel 61
switchport mode trunk
vpc 61
!--- Associates vPC 61 to Po61
Int ethernet 1/4-6
description Cat6506-02
switchport mode trunk
channel-group 62 mode active
!--- Associate interfaces to Po62 connected to Cat6506-02
Int port-channel 62
switchport mode trunk
vpc 62
!--- Associates vPC 62 to Po62
feature vpc
vpc domain 5
reload restore
reload restore delay 300
Peer-keepalive destination 10.11.3.9
role priority 20
!--- Enables vPC, define vPC domain and peer for keep alive
int ethernet 1/9-10
channel-group 50 mode active
!--- Put Interfaces on Po50
int port-channel 50
switchport mode trunk
spanning-tree port type network
vpc peer-link
!--- Po50 configured as Peer-Link for vPC
inter ethernet 1/17-18
description UCS6120-A
switchport mode trunk
channel-group 51 mode active
!--- Associates interfaces to Po51 connected to UCS6120xp-A
int port-channel 51
swithport mode trunk
vpc 51
spannig-tree port type edge trunk
!--- Associates vPC 51 to Po51
inter ethernet 1/19-20
description UCS6120-B
switchport mode trunk
channel-group 52 mode active
!--- Associates interfaces to Po51 connected to UCS6120xp-B
int port-channel 52
swithport mode trunk
vpc 52
spannig-tree port type edge trunk
!--- Associates vPC 52 to Po52
!----- CONFIGURATION for Connection to Catalyst 6506
Int ethernet 1/1-3
description Cat6506-01
switchport mode trunk
channel-group 61 mode active
!--- Associate interfaces to Po61 connected to Cat6506-01
Int port-channel 61
switchport mode trunk
vpc 61
!--- Associates vPC 61 to Po61
Int ethernet 1/4-6
description Cat6506-02
switchport mode trunk
channel-group 62 mode active
!--- Associate interfaces to Po62 connected to Cat6506-02
Int port-channel 62
switchport mode trunk
vpc 62
!--- Associates vPC 62 to Po62
vPC Verification
show vpc consistency-parameters
!--- show compatibility parameters
Show feature
!--- Use it to verify that vpc and lacp features are enabled.
show vpc brief
!--- Displays information about vPC Domain
Etherchannel configuration on TAC 6500s
TACSWC01
TACSWC02
interface range GigabitEthernet2/38 - 43
description TACSWN01 (Po61 vPC61)
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
no ip address
channel-group 61 mode active
interface range GigabitEthernet2/38 - 43
description TACSWN02 (Po62 vPC62)
switchport
switchport trunk encapsulation dot1q
switchport mode trunk
no ip address
channel-group 62 mode activeihernandez81,
Between the c1-r1 & c1-r2 there are no L2 links, ditto with d6-s1 & d6-s2. We did have a routed link just to allow orphan traffic.
All the c1r1 & c1-r2 HSRP communications ( we use GLBP as well ) go from c1-r1 to c1-r2 via the hosp-n5k-s1 & hosp-n5k-s2. Port channels 203 & 204 carry the exact same vlans.
The same is the case on the d6-s1 & d6-s2 sides except we converted them to a VSS cluster so we only have po203 with 4 *10 Gb links going to the 5Ks ( 2 from each VSS member to each 5K).
As you can tell what we were doing was extending VM vlans between 2 data centers prior to arrivals of 7010s and UCS chassis - which worked quite well.
If you got on any 5K you would see 2 port channels - 203 & 204 - going to each 6500, again when one pair went to VSS po204 went away.
I know, I know they are not the same things .... but if you view the 5Ks like a 3750 stack .... how would you hook up a 3750 stack from 2 6500s and if you did why would you run an L2 link between the 6500s ?
For us using 4 10G ports between 6509s took ports that were too expensive - we had 6704s - so use the 5Ks.
Our blocking link was on one of the links between site1 & site2. If we did not have wan connectivty there would have been no blocking or loops.
Caution .... if you go with 7Ks beware of the inability to do L2/L3 via VPCs.
better ?
one of the nice things about working with some of this stuff is as long as you maintain l2 connectivity if you are migrating things they tend to work, unless they really break -
SAN Port-Channel between Nexus 5000 and Brocade 5100
I have a Nexus 5000 running in NPV mode connected to a Brocade 5100 FC switch using two FC ports on a native FC module in the Nexus 5000. I would like to configure these two physical links as one logical link using a SAN Port-Channel/ISL-Trunk. An ISL trunking license is already installed on the Brocade 5100. The Nexus 5000 is running NX-OS 4.2(1), the Brocade 5100 Fabric OS 6.20. Does anybody know if this is a supported configuration? If so, how can this be configured on the Nexus 5000 and the Brocade 5100? Thank you in advance for any comments.
Best regards,
FlorianI tried that and I could see the status light on the ports come on but it still showed not connected.
I configured another switch (a 3560) with the same config and the same layout with the fiber and I got the connection up on it. I just cant seem to get it on the 4506, would it be something with the supervisor? Could it be wanting to use the 10gb port instead of the 1gb ports? -
LMS 3.2: RME failed archive with Nexus 5010
Hi,
LMS 3.2, RME 4.3.1, dev packages updated, Windows.
We would like to archive the configuration of the Nexus 5010 switches. Due to authentication with Radius based on tokens we're not able to use telnet/SSH and therefore we only can use SNMP WRite in combination with TFTP. But, this is not working at all. Other systems like 3750 works fine. Is there a difference between Catalysts IOS and nexus NXOS?
I searched the forum and found this:
https://supportforums.cisco.com/message/663481#663481
upgrade to LMS 2.6, archive config not working anymore
We ship and start a TFTP server by default on Windows. You must have an SNMP read-write community string configured on your devices, and entered in DCR for TFTP config fetches to work. Additionally, udp/69 must be open between device and server.
The easiest way to troubleshoot this kind of problem is to start a sniffer trace on the LMS server (using Device Center > Packet Capture). Filter on all traffic to one of the failing devices. Then, run a Sync Archive job for that same device. When it fails, the sniffer trace will indicate what the problem is
Regards
Ad OlsthoornHi Lavramov,
Yes I'm quite sure, I installed the required packages acoording to the Nexus.RME431.v2-2.readme.pdf manual. the manual tell me to install the following (see also attachement).
To install the Cisco Nexus Series Package, you must install the following dependent packages:
- SharedDcmaSS.RME431.v2-2.zip
- SharedInventoryMDS.RME431.v1-5-1.zip
- SharedSwimMDS9000.RME431.v1-6-1.zip
- SharedNetshowSS.RME431.v1-1.zip
regards
Ad -
I've got a handful of devices in Cisco Prime Infrastructure 2.0 which show up in the "Archive Failed Devices" view. The "Failure Reason" is some variation of "Fetch VLAN configuration - Command failed" sometimes including "TELNET: Failed to establish TELNET connection to x.x.x.x". What does this mean? How do I overcome this? In all cases, the device is configured to use SSH and has valid SSH credentials. In all cases, I can SSH from the command line of the NCS appliance to the devices listed in the "Archive Failed Devices" view.
Hi
I was able to fix the "Fetch VLAN configuration - Command failed" by allowing tftp from the device to PI server in firewall. See if this can help. -
PI2.1 : Cannot make Configuration Archive : Fetch Runing/Start Fail
Hello,
I cannot make a configuration archive with PI2.1.
I'm using PI2.1 to control WLC.
When I run Configuration archive, it says Fetch Running: "Unkown error", Fetch Startup "Unknown Error", Fetch VLAN "Unknown Error".
What should be the reason?
I can enter in the WLC, configure it from PI, but cannot make "Archive Config"
Please help.
Regards,Please check the following:
SWIM and Configuration Archives support for Devices during Cisco Prime Infrastructure releases—Table 4 outlines the devices that the software image management and configuration archives support during the various Prime Infrastructure releases.
Table 4 SWIM and Configuration Archives support for Devices during Prime Infrastructure Releases
Devices
Prime Infrastructure Releases
Cisco 4400 Wireless LAN Controller1
1.2, 1.3, 1.4, 2.0, and 2.1
Cisco 5500 Series Wireless LAN Controllers
1.2, 1.3, 1.4, 2.0, and 2.1
Cisco WiSM1 Controller
1.2, 1.3, 1.4, 2.0, and 2.1
Cisco 2106 Wireless LAN Controller1
1.2, 1.3, 1.4, 2.0, and 2.1
Cisco 2504 Wireless LAN Controller
1.2, 1.3, 1.4, 2.0, and 2.1
Cisco 2800 and 3800 Series Integrated Services Routers
1.2, 1.3, 1.4, 2.0, and 2.1
Cisco Flex 7500 Series Wireless LAN Controller
1.2, 1.3, 1.4, 2.0, and 2.1
Cisco 8500 Wireless LAN Controller1
1.4, 2.0, and 2.1
Cisco Virtual Wireless LAN Controller1
1.4, 2.0, and 2.1
Cisco WiSM2 Controller
Not supported
1.Prime Infrastructure 1.4 does not support SWIM in Cisco 2106/4400/8500/WiSM2/Virtual WLC.
Hope that helps. -
Cisco Prime Configuration Archive on Interface Flap
Hey All,
We've been using Cisco Prime 2.1 for a bit now and I have a question about the configuration archive based on change events. Will Cisco Prime go and attempt to perform a config backup based on an interface flap? Looking at the audit logs it appears that it does that (see attachment). Is this a default behavior and does anyone see any benefit to this? It seems like if an interface is flapping it will continuously log into the device to see if the configuration has changed.
BrianHi Brian,
I don't think configuration achieve can be triggered due to interface flap ,however if there is any change in the configuration yes PI can do the config Archive
Go to Administration > System Settings > Configuration Archive
Archive Configuration on receiving configuration change events? Check box this option
Thanks-
Afroz
***Ratings Encourages Contributors ***** -
Cisco Prime Infrastructure release 2.1 configuration archiving on CISCO WiSM2
Hi all,
Just wondering Cisco Prime Infrastructure release 2-1 support configuration archiving on CISCO WiSM2?
CISCO release 2.0 mentioned that it doesn't support configuration archiving for WiSM2 but release 2.1 doesn't mention anything on it.
Please assist.No, it is not supported even for PI 2.1
-
Prime Infrastructure 2.1 - Fetch VLAN Configuration - command failed
Hi,
i am installing the system on a customer's site.
i've noticed that most of the devices configured on the PI have resulted in error in the Configuration Archive with this error:
Fetch VLAN Configuration - command failed.
i checked that the tftp service on the PI is enabled.
i tried manually executing from a device: copy flash:vlan.dat tftp://PI_IP and couldnt manage to do so.
i also tried manually to do it to another tftp server and it worked.
i dont see any FW drops.
does anyone have any idea how to troubleshoot this?
thanks in advance!As to get the VLAN information, the file in Cisco devices Flash : Vlan.dat is fetced, and if PI fails to do so, it gives this error. As it is a file in flash, PI needs to send it over to Server itself using TFTP.
If TFPT is somehow not working between Server and devices, it may throw this error.
Is it happening with all the devices or some perticular platform?
If with all the device, you need to check if there is any Firewall blocking TFTP access to devices.
Also, you can check if TFTP service on CPI is working properly by command ncs status.
If service is affected, try to restart service - service tftp restart Or you can restart the PI Machine itself.
-Thanks
Vinod
**Encourage Contributors. RATE Them.** -
BPM for Weblogic configuration is failed
1, I install BPM for Weblogic.
2, I create a domain for weblogic using config tool and start it.
3, I create a new directory.
However, the configuration is failed.
The BPM for weblogic is installed in XP and the window of selecting JDK is not pop out.
The log is as follows:
For more help, use help(edit) Starting an edit session ... Started edit session, please be sure to save and activate your
changes once you are done. creating mbean of type JMSServer ... creating mbean of type JMSSystemResource ... creating mbean of type SubDeployment ... creating mbean of type Queue ... creating mbean of type Topic ... creating mbean of type ConnectionFactory ... creating mbean of type ConnectionFactory ... creating mbean of type JDBCSystemResource ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type JDBCSystemResource ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... setting attributes for mbean type JMSServer setting attributes for mbean type JMSSystemResource setting attributes for mbean type SubDeployment setting attributes for mbean type Queue setting attributes for mbean type Topic setting attributes for mbean type JMSConnectionFactory setting attributes for mbean type JMSConnectionFactory setting attributes for mbean type JDBCSystemResource setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCConnectionPoolParams setting attributes for mbean type JDBCDriverParams setting attributes for mbean type JDBCDataSource setting attributes for mbean type JDBCDataSource setting attributes for mbean type JDBCXAParams setting attributes for mbean type JDBCDataSourceParams setting attributes for mbean type JDBCConnectionPoolParams setting attributes for mbean type JDBCDriverParams setting attributes for mbean type JDBCDataSourceParams setting attributes for mbean type JDBCSystemResource setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty Saving all your changes ... Saved all your changes successfully. Your edit session is not stopped, you can continue your edits. Activating all your changes, this may take a while ...
The edit lock associated with this edit session is released
once the activation is completed. Activation completed Creating a user ... Created user successfully Deploying application from E:\OraBPMwlHome20090715WebLogic\j2ee\weblogic\deployer\wlj2eedeployer.ear to targets examplesServer (upload=true) ... <Jul 15, 2009 12:11:44 PM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, wlj2eedeployer archive: E:\OraBPMwlHome20090715WebLogic\j2ee\weblogic\deployer\wlj2eedeployer.ear, to examplesServer .> .Completed the deployment of Application with status completed Current Status of your Deployment: Deployment command type: deploy Deployment State : completed Deployment Message : no message Deploying application from E:\OraBPMwlHome20090715WebLogic\ears\engine\01-eng-bpmengine3.ear to targets examplesServer (upload=true) ... <Jul 15, 2009 12:11:54 PM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 01-eng-bpmengine3 archive: E:\OraBPMwlHome20090715WebLogic\ears\engine\01-eng-bpmengine3.ear, to examplesServer .> Failed to deploy the application with status failed Current Status of your Deployment: Deployment command type: deploy Deployment State : failed Deployment Message : java.lang.OutOfMemoryError: Java heap space No stack trace available. This Exception occurred at Wed Jul 15 12:12:17 CST 2009. weblogic.management.scripting.ScriptException: Error occured while performing deploy : Deployment Failed. at weblogic.management.scripting.ExceptionHandler.handleException(ExceptionHandler.java:48) at weblogic.management.scripting.WLSTUtils.throwWLSTException(WLSTUtils.java:185) at weblogic.management.scripting.JSR88DeployHandler.deploy(JSR88DeployHandler.java:536) at weblogic.management.scripting.WLScriptContext.deploy(WLScriptContext.java:429) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160) at org.python.core.PyMethod.__call__(PyMethod.java:96) at org.python.core.PyObject.__call__(PyObject.java:248) at org.python.core.PyObject.invoke(PyObject.java:2016) at org.python.pycode._pyx17.deploy$8(<iostream>:223) at org.python.pycode._pyx17.call_function(<iostream>) at org.python.core.PyTableCode.call(PyTableCode.java:208) at org.python.core.PyTableCode.call(PyTableCode.java:404) at org.python.core.PyFunction.__call__(PyFunction.java:184) at org.python.pycode._pyx16.deploy_Applications$61(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py:623) at org.python.pycode._pyx16.call_function(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py) at org.python.core.PyTableCode.call(PyTableCode.java:208) at org.python.core.PyTableCode.call(PyTableCode.java:256) at org.python.core.PyFunction.__call__(PyFunction.java:169) at org.python.pycode._pyx16.f$0(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py:738) at org.python.pycode._pyx16.call_function(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py) at org.python.core.PyTableCode.call(PyTableCode.java:208) at org.python.core.PyCode.call(PyCode.java:14) at org.python.core.Py.runCode(Py.java:1135) at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:167) at weblogic.management.scripting.WLST.main(WLST.java:129) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at weblogic.WLST.main(WLST.java:29)
Exiting WebLogic Scripting Tool.
<Jul 15, 2009 12:12:17 PM CST> <Warning> <JNDI> <BEA-050001> <WLContext.close() was called in a different thread than the one in which it was created.> QuestionConfirm Action
Do you want to cancel this wizard?Hi,
Thanks for your reply. I change the file and reconfigure the BPM for weblogic. However, it is still failed in 70-72%.
-------------------log message-------------------------------
TO_MSG PATH=/root/bea/wlserver_10.3/server/bin:/root/bea/modules/org.apache.ant_1.6.5/bin:/root/bea/jrockit_160_05/jre/bin:/root/bea/jrockit_160_05/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/root/bin
TO_MSG
TO_MSG Your environment has been set.
TO_MSG
TO_MSG CLASSPATH=/root/bea/patch_wlw1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/bea/patch_wls1030/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/bea/patch_cie660/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/bea/jrockit_160_05/lib/tools.jar:/root/bea/wlserver_10.3/server/lib/weblogic_sp.jar:/root/bea/wlserver_10.3/server/lib/weblogic.jar:/root/bea/modules/features/weblogic.server.modules_10.3.0.0.jar:/root/bea/wlserver_10.3/server/lib/webservices.jar:/root/bea/modules/org.apache.ant_1.6.5/lib/ant-all.jar:/root/bea/modules/net.sf.antcontrib_1.0.0.0_1-0b2/lib/ant-contrib.jar:/root/OraBPMwlHome/lib/fuego.boot.jar:/root/OraBPMwlHome/bin/./:/root/OraBPMwlHome/bin/./lax.jar::/root/bea/wlserver_10.3/common/eval/pointbase/lib/pbembedded57.jar:/root/bea/wlserver_10.3/common/eval/pointbase/lib/pbtools57.jar:/root/bea/wlserver_10.3/common/eval/pointbase/lib/pbclient57.jar
TO_MSG
TO_MSG Initializing WebLogic Scripting Tool (WLST) ...
TO_MSG
TO_MSG Welcome to WebLogic Server Administration Scripting Shell
TO_MSG
TO_MSG Type help() for help on available commands
TO_MSG
TO_MSG Starting server BPMServer
TO_MSG Please see the server log files for startup messages available at /root/weblogic3/bpm
TO_MSG Starting weblogic server ...
TO_MSG WLST-WLS-1249792014056: [WARN ] -XX:MaxPermSize=256m is not a valid VM option. Ignoring
TO_MSG .WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ26￥ﾈﾆ58ﾧﾒ CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.0-50_o-100423-1.6.0_05-20080626-2104-linux-ia32 from BEA Systems, Inc.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ00ﾧﾒ CST> <Info> <Management> <BEA-140013> </root/weblogic3/bpm/config/config.xml not found>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ00ﾧﾒ CST> <Info> <Management> <BEA-141254> <Generating new domain directory in /root/weblogic3/bpm>
TO_MSG .....WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ12ﾧﾒ CST> <Info> <Management> <BEA-141255> <Domain generation completed in 12,326 milliseconds.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ13ﾧﾒ CST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3 Fri Jul 25 16:30:05 EDT 2008 1137967 >
TO_MSG .WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ15ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ15ﾧﾒ CST> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ16ﾧﾒ CST> <Notice> <Log Management> <BEA-170019> <The server log file /root/weblogic3/bpm/servers/BPMServer/logs/BPMServer.log is opened. All server side log events will be written to this file.>
TO_MSG ...WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ24ﾧﾒ CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
TO_MSG ....WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ34ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ34ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ34ﾧﾒ CST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
TO_MSG .WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ35ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ35ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RESUMING>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ35ﾧﾒ CST> <Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ35ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000331> <Started WebLogic Admin Server "BPMServer" for domain "bpm" running in Development Mode>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ36ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to RUNNING>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ36ﾧﾒ CST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
TO_MSG Server started successfully.
TO_MSG Started Server. Trying to connect to the server ...
TO_MSG Connecting to t3://localhost.localdomain:7001 with userid weblogic ...
TO_MSG Successfully connected to Admin Server 'BPMServer' that belongs to domain 'bpm'.
TO_MSG
TO_MSG Warning: An insecure protocol was used to connect to the
TO_MSG server. To ensure on-the-wire security, the SSL port or
TO_MSG Admin port should be used instead.
TO_MSG
TO_MSG Location changed to edit tree. This is a writable tree with
TO_MSG DomainMBean as the root. To make changes you will need to start
TO_MSG an edit session via startEdit().
TO_MSG
TO_MSG For more help, use help(edit)
TO_MSG
TO_MSG Starting an edit session ...
TO_MSG Started edit session, please be sure to save and activate your
TO_MSG changes once you are done.
TO_MSG creating mbean of type JMSServer ...
TO_MSG creating mbean of type JMSSystemResource ...
TO_MSG creating mbean of type SubDeployment ...
TO_MSG creating mbean of type Queue ...
TO_MSG creating mbean of type Topic ...
TO_MSG creating mbean of type ConnectionFactory ...
TO_MSG creating mbean of type ConnectionFactory ...
TO_MSG creating mbean of type Server ...
TO_MSG creating mbean of type JDBCSystemResource ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type JDBCSystemResource ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Property ...
TO_MSG creating mbean of type Realm ...
TO_MSG creating mbean of type RoleMapper ...
TO_MSG creating mbean of type CredentialMapper ...
TO_MSG creating mbean of type CertPathProvider ...
TO_MSG creating mbean of type Authorizer ...
TO_MSG creating mbean of type Adjudicator ...
TO_MSG creating mbean of type AuthenticationProvider ...
TO_MSG creating mbean of type AuthenticationProvider ...
TO_MSG setting attributes for mbean type JMSServer
TO_MSG setting attributes for mbean type JMSSystemResource
TO_MSG setting attributes for mbean type SubDeployment
TO_MSG setting attributes for mbean type Queue
TO_MSG setting attributes for mbean type Topic
TO_MSG setting attributes for mbean type JMSConnectionFactory
TO_MSG setting attributes for mbean type JMSConnectionFactory
TO_MSG setting attributes for mbean type Server
TO_MSG setting attributes for mbean type JDBCSystemResource
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCConnectionPoolParams
TO_MSG setting attributes for mbean type JDBCDriverParams
TO_MSG setting attributes for mbean type JDBCDataSource
TO_MSG setting attributes for mbean type DefaultIdentityAsserter
TO_MSG setting attributes for mbean type SecurityConfiguration
TO_MSG setting attributes for mbean type SecurityParams
TO_MSG setting attributes for mbean type EmbeddedLDAP
TO_MSG setting attributes for mbean type SecurityParams
TO_MSG setting attributes for mbean type Domain
TO_MSG setting attributes for mbean type JDBCDataSource
TO_MSG setting attributes for mbean type JDBCXAParams
TO_MSG setting attributes for mbean type JDBCDataSourceParams
TO_MSG setting attributes for mbean type JDBCConnectionPoolParams
TO_MSG setting attributes for mbean type JDBCDriverParams
TO_MSG setting attributes for mbean type JDBCDataSourceParams
TO_MSG setting attributes for mbean type JDBCSystemResource
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG setting attributes for mbean type JDBCProperty
TO_MSG Saving all your changes ...
TO_MSG Saved all your changes successfully.
TO_MSG Your edit session is not stopped, you can continue your edits.
TO_MSG Activating all your changes, this may take a while ...
TO_MSG The edit lock associated with this edit session is released
TO_MSG once the activation is completed.
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53ﾧﾒ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute InternalAppsDeployOnDemandEnabled on weblogic.management.configuration.DomainMBeanImpl@fffe8220([bpm]) has been changed. This may require redeploying or rebooting configured entities>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53ﾧﾒ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53ﾧﾒ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute RotateLogOnStartup on weblogic.management.configuration.LogMBeanImpl@1759a12([bpm]/Log[bpm]) has been changed. This may require redeploying or rebooting configured entities>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53ﾧﾒ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53ﾧﾒ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute ListenAddress on weblogic.management.configuration.ServerMBeanImpl@2ddd7637([bpm]/Servers[BPMServer]) has been changed. This may require redeploying or rebooting configured entities>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53ﾧﾒ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53ﾧﾒ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute RotateLogOnStartup on weblogic.management.configuration.LogMBeanImpl@2df105fa([bpm]/Servers[BPMServer]/Log[BPMServer]) has been changed. This may require redeploying or rebooting configured entities>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53ﾧﾒ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53ﾧﾒ CST> <Warning> <Management> <BEA-141239> <The non-dynamic attribute RotateLogOnStartup on weblogic.management.configuration.WebServerLogMBeanImpl@2df106e5([bpm]/Servers[BPMServer]/WebServer[BPMServer]/WebServerLog[BPMServer]) has been changed. This may require redeploying or rebooting configured entities>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ27￥ﾈﾆ53ﾧﾒ CST> <Warning> <Management> <BEA-141238> <A non-dynamic change has been made which affects the server BPMServer. This server must be rebooted in order to consume this change.>
TO_MSG
TO_MSG The following non-dynamic attribute(s) have been changed on MBeans
TO_MSG that require server re-start:
TO_MSG MBean Changed : com.bea:Name=BPMServer,Type=Log,Server=BPMServer
TO_MSG Attributes changed : RotateLogOnStartup
TO_MSG
TO_MSG MBean Changed : com.bea:Name=BPMServer,Type=Server
TO_MSG Attributes changed : ListenAddress
TO_MSG
TO_MSG MBean Changed : com.bea:Name=bpm,Type=Log
TO_MSG Attributes changed : RotateLogOnStartup
TO_MSG
TO_MSG MBean Changed : com.bea:Name=bpm,Type=Domain
TO_MSG Attributes changed : InternalAppsDeployOnDemandEnabled, ProductionModeEnabled
TO_MSG
TO_MSG MBean Changed : com.bea:Name=BPMServer,Type=WebServerLog,Server=BPMServer,WebServer=BPMServer
TO_MSG Attributes changed : RotateLogOnStartup
TO_MSG
TO_MSG Activation completed
TO_MSG Creating a user ...
TO_MSG
TO_MSG Created user successfully
TO_MSG Deploying application from /root/OraBPMwlHome/j2ee/weblogic/deployer/wlj2eedeployer.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ28￥ﾈﾆ01ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, wlj2eedeployer [archive: /root/OraBPMwlHome/j2ee/weblogic/deployer/wlj2eedeployer.ear], to BPMServer .>
TO_MSG .Completed the deployment of Application with status completed
TO_MSG Current Status of your Deployment:
TO_MSG Deployment command type: deploy
TO_MSG Deployment State : completed
TO_MSG Deployment Message : no message
TO_MSG Deploying application from /root/OraBPMwlHome/ears/engine/01-eng-bpmengine.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ28￥ﾈﾆ08ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 01-eng-bpmengine [archive: /root/OraBPMwlHome/ears/engine/01-eng-bpmengine.ear], to BPMServer .>
TO_MSG .................Completed the deployment of Application with status completed
TO_MSG Current Status of your Deployment:
TO_MSG Deployment command type: deploy
TO_MSG Deployment State : completed
TO_MSG Deployment Message : no message
TO_MSG Deploying application from /root/OraBPMwlHome/ears/webapps/webapps_expanded/08-workspace-XAFDIDS.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ29￥ﾈﾆ48ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 08-workspace-XAFDIDS.ear [archive: /root/OraBPMwlHome/ears/webapps/webapps_expanded/08-workspace-XAFDIDS.ear], to BPMServer .>
TO_MSG .Completed the deployment of Application with status completed
TO_MSG Current Status of your Deployment:
TO_MSG Deployment command type: deploy
TO_MSG Deployment State : completed
TO_MSG Deployment Message : no message
TO_MSG Deploying application from /root/OraBPMwlHome/ears/webapps/webapps_expanded/09-feeds-XAFDIDS.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ30￥ﾈﾆ45ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 09-feeds-XAFDIDS.ear [archive: /root/OraBPMwlHome/ears/webapps/webapps_expanded/09-feeds-XAFDIDS.ear], to BPMServer .>
TO_MSG .Completed the deployment of Application with status completed
TO_MSG Current Status of your Deployment:
TO_MSG Deployment command type: deploy
TO_MSG Deployment State : completed
TO_MSG Deployment Message : no message
TO_MSG Deploying application from /root/OraBPMwlHome/ears/webapps/webapps_expanded/06-workspaceadmin-XAFDIDS.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ31￥ﾈﾆ00ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 06-workspaceadmin-XAFDIDS.ear [archive: /root/OraBPMwlHome/ears/webapps/webapps_expanded/06-workspaceadmin-XAFDIDS.ear], to BPMServer .>
TO_MSG .Completed the deployment of Application with status completed
TO_MSG Current Status of your Deployment:
TO_MSG Deployment command type: deploy
TO_MSG Deployment State : completed
TO_MSG Deployment Message : no message
TO_MSG Deploying application from /root/OraBPMwlHome/ears/webapps/07-papiws-wls103-XAFDIDS.ear to targets BPMServer (upload=true) ...
TO_MSG <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ31￥ﾈﾆ31ﾧﾒ CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 07-papiws-wls103-XAFDIDS.ear [archive: /root/OraBPMwlHome/ears/webapps/07-papiws-wls103-XAFDIDS.ear], to BPMServer .>
TO_MSG ..WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ31￥ﾈﾆ48ﾧﾒ CST> <Error> <HTTP> <BEA-101220> <Error occurred while setting document root for "weblogic.servlet.internal.WebAppServletContext@30302d0 - appName: '07-papiws-wls103-XAFDIDS.ear', name: 'papiws', context-path: '/papiws', spec-version: '2.5'" to "/root/weblogic3/bpm/servers/BPMServer/tmp/_WL_user/07-papiws-wls103-XAFDIDS.ear/f0r1c0/papiws.war".>
TO_MSG WLST-WLS-1249792014056: <2009-8-9 ￤ﾸﾋ￥ﾍﾈ12￦ﾗﾶ31￥ﾈﾆ48ﾧﾒ CST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1249792304208' for task '5'. Error is: 'weblogic.application.ModuleException: Failed to load webapp: 'papiws''
TO_MSG WLST-WLS-1249792014056: weblogic.application.ModuleException: Failed to load webapp: 'papiws'
TO_MSG WLST-WLS-1249792014056: at weblogic.servlet.internal.WebAppModule.prepare(WebAppModule.java:387)
TO_MSG WLST-WLS-1249792014056: at weblogic.application.internal.flow.ScopedModuleDriver.prepare(ScopedModuleDriver.java:176)
TO_MSG WLST-WLS-1249792014056: at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93)
TO_MSG WLST-WLS-1249792014056: at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:387)
TO_MSG WLST-WLS-1249792014056: at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:37)
TO_MSG WLST-WLS-1249792014056: Truncated. see log file for complete stacktrace
TO_MSG WLST-WLS-1249792014056: java.io.IOException: Error opening file
TO_MSG WLST-WLS-1249792014056: at java.util.zip.ZipFile.open(Native Method)
TO_MSG WLST-WLS-1249792014056: at java.util.zip.ZipFile.<init>(ZipFile.java:117)
TO_MSG WLST-WLS-1249792014056: at java.util.zip.ZipFile.<init>(ZipFile.java:133)
TO_MSG WLST-WLS-1249792014056: at weblogic.utils.classloaders.ZipClassFinder.<init>(ZipClassFinder.java:23)
TO_MSG WLST-WLS-1249792014056: at weblogic.application.io.ArchivedWar$WebInfClassesFinder.<init>(ArchivedWar.java:290)
TO_MSG WLST-WLS-1249792014056: Truncated. see log file for complete stacktrace
TO_MSG WLST-WLS-1249792014056: >
TO_MSG WLST-WLS-1249792014056: java.io.FileNotFoundException: /root/weblogic3/bpm/config/config.xml (Too many open files)
TO_MSG WLST-WLS-1249792014056: at java.io.FileOutputStream.open(Native Method)
TO_MSG WLST-WLS-1249792014056: at java.io.FileOutputStream.<init>(FileOutputStream.java:179)
TO_MSG WLST-WLS-1249792014056: at java.io.FileOutputStream.<init>(FileOutputStream.java:131)
TO_MSG WLST-WLS-1249792014056: at weblogic.utils.FileUtils.writeToFile(FileUtils.java:115)
TO_MSG WLST-WLS-1249792014056: at weblogic.utils.Fil -
Configuration is failed - BPM for Weblogic 10.3.1
1, I install BPM for Weblogic.
2, I create a domain for weblogic using config tool and start it.
3, I create a new directory.
However, the configuration is failed.
The BPM for weblogic is installed in XP and the window of selecting JDK is not pop out.
The log is as follows:
For more help, use help(edit) Starting an edit session ... Started edit session, please be sure to save and activate your
changes once you are done. creating mbean of type JMSServer ... creating mbean of type JMSSystemResource ... creating mbean of type SubDeployment ... creating mbean of type Queue ... creating mbean of type Topic ... creating mbean of type ConnectionFactory ... creating mbean of type ConnectionFactory ... creating mbean of type JDBCSystemResource ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type JDBCSystemResource ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... creating mbean of type Property ... setting attributes for mbean type JMSServer setting attributes for mbean type JMSSystemResource setting attributes for mbean type SubDeployment setting attributes for mbean type Queue setting attributes for mbean type Topic setting attributes for mbean type JMSConnectionFactory setting attributes for mbean type JMSConnectionFactory setting attributes for mbean type JDBCSystemResource setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCConnectionPoolParams setting attributes for mbean type JDBCDriverParams setting attributes for mbean type JDBCDataSource setting attributes for mbean type JDBCDataSource setting attributes for mbean type JDBCXAParams setting attributes for mbean type JDBCDataSourceParams setting attributes for mbean type JDBCConnectionPoolParams setting attributes for mbean type JDBCDriverParams setting attributes for mbean type JDBCDataSourceParams setting attributes for mbean type JDBCSystemResource setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty setting attributes for mbean type JDBCProperty Saving all your changes ... Saved all your changes successfully. Your edit session is not stopped, you can continue your edits. Activating all your changes, this may take a while ...
The edit lock associated with this edit session is released
once the activation is completed. Activation completed Creating a user ... Created user successfully Deploying application from E:\OraBPMwlHome20090715WebLogic\j2ee\weblogic\deployer\wlj2eedeployer.ear to targets examplesServer (upload=true) ... <Jul 15, 2009 12:11:44 PM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, wlj2eedeployer [archive: E:\OraBPMwlHome20090715WebLogic\j2ee\weblogic\deployer\wlj2eedeployer.ear], to examplesServer .> .Completed the deployment of Application with status completed Current Status of your Deployment: Deployment command type: deploy Deployment State : completed Deployment Message : no message Deploying application from E:\OraBPMwlHome20090715WebLogic\ears\engine\01-eng-bpmengine3.ear to targets examplesServer (upload=true) ... <Jul 15, 2009 12:11:54 PM CST> <Info> <J2EE Deployment SPI> <BEA-260121> <Initiating deploy operation for application, 01-eng-bpmengine3 [archive: E:\OraBPMwlHome20090715WebLogic\ears\engine\01-eng-bpmengine3.ear], to examplesServer .> Failed to deploy the application with status failed Current Status of your Deployment: Deployment command type: deploy Deployment State : failed Deployment Message : java.lang.OutOfMemoryError: Java heap space No stack trace available. This Exception occurred at Wed Jul 15 12:12:17 CST 2009. weblogic.management.scripting.ScriptException: Error occured while performing deploy : Deployment Failed. at weblogic.management.scripting.ExceptionHandler.handleException(ExceptionHandler.java:48) at weblogic.management.scripting.WLSTUtils.throwWLSTException(WLSTUtils.java:185) at weblogic.management.scripting.JSR88DeployHandler.deploy(JSR88DeployHandler.java:536) at weblogic.management.scripting.WLScriptContext.deploy(WLScriptContext.java:429) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.python.core.PyReflectedFunction.__call__(PyReflectedFunction.java:160) at org.python.core.PyMethod.__call__(PyMethod.java:96) at org.python.core.PyObject.__call__(PyObject.java:248) at org.python.core.PyObject.invoke(PyObject.java:2016) at org.python.pycode._pyx17.deploy$8(<iostream>:223) at org.python.pycode._pyx17.call_function(<iostream>) at org.python.core.PyTableCode.call(PyTableCode.java:208) at org.python.core.PyTableCode.call(PyTableCode.java:404) at org.python.core.PyFunction.__call__(PyFunction.java:184) at org.python.pycode._pyx16.deploy_Applications$61(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py:623) at org.python.pycode._pyx16.call_function(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py) at org.python.core.PyTableCode.call(PyTableCode.java:208) at org.python.core.PyTableCode.call(PyTableCode.java:256) at org.python.core.PyFunction.__call__(PyFunction.java:169) at org.python.pycode._pyx16.f$0(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py:738) at org.python.pycode._pyx16.call_function(C:\Documents and Settings\Administrator\.configWizard\tmp\config.py) at org.python.core.PyTableCode.call(PyTableCode.java:208) at org.python.core.PyCode.call(PyCode.java:14) at org.python.core.Py.runCode(Py.java:1135) at org.python.util.PythonInterpreter.execfile(PythonInterpreter.java:167) at weblogic.management.scripting.WLST.main(WLST.java:129) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at weblogic.WLST.main(WLST.java:29)
Exiting WebLogic Scripting Tool.
<Jul 15, 2009 12:12:17 PM CST> <Warning> <JNDI> <BEA-050001> <WLContext.close() was called in a different thread than the one in which it was created.> QuestionConfirm Action
Do you want to cancel this wizard?Hi Ye,
I noticed this afternoon that Oracle's refering to Oracle WebLogic 10.3.1 as "Oracle WebLogic 11g".
Know this comes as no surprise to you, but when I tried to install Oracle BPM 10gR3 Enterprise on WebLogic 11g (WebLogic 10.3.1) this afternoon it failed. A friend pointed out to me that Oracle WebLogic 11g does not support the DataDirect JDBC driver. Since Oracle BPM Enterprise 10gR3 uses this driver to connect to both its Engine database and Directory Service databases, he's thinking this might be the cause of our problem.
It would be worth verifying this with Support. Here's what I think they'll point you to. The Oracle BPM 10gR3 release notes(http://download.oracle.com/docs/cd/E13154_01/bpm/docs65/relnotes/release_notes_OracleBPM10gR3.htm#N65589) indicate that the only WebLogic application servers supported are Oracle WebLogic 10.3 (10gR3), Oracle WebLogic 10.0 MP1.
Again, talk to Support, but I don't think there's a workaround. The only thing I think you can do is to uninstall WebLogic 10.3.1 and then install WebLogic 10.3 if you want to install Oracle BPM 10gR3 Enterprise on it.
Dan -
LMS 3.2 - RME 4.3.1 Sync archive fails
Hi,
Sync archive fails for some of my devices.
This is the message :
*** Device Details for .... ***
Protocol ==> Unknown / Not Applicable
Selected Protocols with order ==> Telnet,TFTP,SSH,RCP,HTTPS
Execution Result:
CM00139 Could not archive config Cause: Action: Verify that device is managed and credentials are correct. Increase timeout value, if required.
Check device credential is OK (Telnet + SNMP V2)
This device is Cisco Systems WS-C6009.Cisco Catalyst Operating System Software, Version 7.4(3). (sysObjectID : enterprises.9.5.39)
I have modified the "Maximum time to wait for Job Results per device (seconds):" to 240.
What could be wrong?
Thanks in advanceResolution Summary:Checked the dcmaService.log and found the following recurring statements.
com.cisco.nm.xms.xdi.pkgs.LibCommon.common.CommonUtility,getMinSupportedVersion,406,Descr = 12.2(50)SE
[ Tue Oct 26 15:58:45 CDT 2010 ],DEBUG,[main],com.cisco.nm.xms.xdi.pkgs.LibCommon.common.CommonUtility,getMinSupportedVersion,405,suppSysId = .1.3.6.1.4.1.9.1.927
[ Tue Oct 26 15:58:45 CDT 2010
Checked that the device IOS was well above the version specified in the logs, so thought may be an issue with the device packages.
Checked the mdf version was 1.25 which came as default when we install LMS 3.2, so upgraded the mdf version to 1.45.
Still the issue didn't got solved, so upgraded the RME device packages and now the archive job was successful.
Message was edited by: Dheeraj Gera -
PI 2.0 configuration archive problems
Hi,
I've got 2 problems with archiving device configurations in Prime Infrastructure 2.0.
1. Configuration archive job status is Completed and Last run status is Success
Looking at Configuration archive results, I see this:
Fetch Running: Success
Fetch Startup: Success
Fetch VLAN: Unsupported operation
Fetch Modules: N/A
Archive: Success
It's a Cisco 7200 router.
Looking at its Configuration archive, I can see just the running config. Startup config is missing.
2. Configuration archive job status is Completed and Last run status is Partial-Success
Looking at Configuration archive results, I see this:
Fetch Running: Success
Fetch Startup: Success
Fetch VLAN: Unsupported operation
Fetch Modules: N/A
Archive: Error in archiving for device '3663756'
It's a Cisco 6500 FWSM.
Looking at its Configuration archive, I can't see anything, it says 'No data available'. Both running and startup configs are missing.
Do you have some ideas what is wrong here, why can't I see the configurations?I've found the reason why this is happening. In the case when startup and running configs are identical (disregarding lines like 'last configuration change', 'ntp clock-period',...), Prime doesn't show startup config under Configuration Archive, it
just shows the running config.
Maybe you are looking for
-
Best Camera for Graphic Design
I am a Web Designer and Graphic designer in American Samoa. I am looking at cameras for when local clients want me to do work. What is the best one to get. I want a professional grade, not some $49 special from Wal-Mart.
-
HT2693 how can i save my pages document as a PDF file or jpeg now?
Hi... How can i save my pages document as a PDF file or Jpeg file now that the share is NA.
-
Upgarading my 8520 curve software to os5 or 6
Is it possible to upgrade the software of my Blackberry Curve 8520 software to one of the latest OS's? Where can I download the software and how do I install it? I live in South Africa
-
AppStore: cannot view account info because off password loop
I got a login looping problem in appstore when I try to view/Update my account info from my iPad. I tried to login 20 times without any luck :-(( I dont have any problem if I use: https://appleid.apple.com/cgi-bin/WebObjects/MyAppleId.woa/
-
I'm having trouble connecting a new time capsule, I get "an unexpected error occurred.Try again" I'm trying to connect wirelessly, and have reset the capsule.