WLST startserver issues in WLS 12.1

Trying to upgrade to WLS 12.1 (and WebSPhere 8.x)
We create a Domain through WLSt. Save it, start it and then deploy our app. All though WLST.
Part 1), creating the domain worked. While starting the server, it complained about "JAX-WS 2.2 API is required, but an older version was found in the JDK.". That was resolved when I added java.endorsed.dirs. Now, I have the domain created and then WLSt tries to start it using
startServer('AdminServer','MyDomain','t3://localhost:7001', 'weblogic', 'weblogic1',
'c:/release/v78/weblogic/config/MyDomain',
serverLog='c:/release/v78/weblogic/config/logs/wlstStartServer.log', timeout=360000,
systemProperties='weblogic.alternateTypesDirectory=c:/release/v78/weblogic/config/lib/jmx,com.sun.xml.namespace.QName.useCompatibleSerialVersionUID=1.0,java.endorsed.dirs=C:/bea/java6_29_64bit/jre/lib/endorsed;c:/bea/wls12/wlserver_12.1/endorsed;c:/release/v78/weblogic/config/vendor/jaxws22/jaxws-ri/lib',
jvmArgs='-Xms256m -Xmx1024m -XX:MaxPermSize=128m')
and the above always results in the following. Interestingly, if I simply used the MyDomain/startWebLogic.cmd, the server starts.
*+.WLST-WLS-1326381258658: <Jan 12, 2012 10:14:26 AM EST> <Error> <HTTP> <BEA-101064> <[WebAppModule(bea_wls_internal:bea_wls_internal.war)] Error parsing descriptor in Web appplication "C:\release\v78\Webworks\weblogic\config\MyDomain\serves\AdminServer\tmp\.internal\bea_wls_internal.war"+*
WLST-WLS-1326381258658: java.lang.StringIndexOutOfBoundsException: String indexout of range: 0*
WLST-WLS-1326381258658:         at java.lang.String.charAt(String.java:686)*
WLST-WLS-1326381258658:         at weblogic.servlet.internal.WebAppReader2.getText(WebAppReader2.java:190)*
WLST-WLS-1326381258658:         at weblogic.application.descriptor.BasicMunger2._onDTD(BasicMunger2.java:471)*
WLST-WLS-1326381258658:         at weblogic.application.descriptor.BasicMunger2.next(BasicMunger2.java:433)*

unable to start a domain through WLST startServer

Similar Messages

Performance issue on WLS Plugins

I also have some performance issue on wls plugins. tried to load test to
weblogic directly with 1000 concurrent connection, it's fine on Weblogic
server. when try to use SunOne Web Server 6.0 + wls plugins, it becomes slow
through web server, if configure wls plugins with Weblogic Cluster , even
worse, very slow response. look like this plugins can not support so much of
load . it's a bottleneck.

Duplicate post:
Performance issue on AFPO
Performance issue on AFPO

WLST : We face this issue on WLS 8.1, 9.2, 10.3

Hi All,
Unless I have a copy of the boot.properties file in the domain root directory I cannot get weblogic.WLST to "utilize" the boot.properties. I thought there was a java option I should be able to set to "point" WLST to the boot.properties in the servers/instance/security directory?
we need to be able to check state of instances programmatically - we cannot use the admin console to do this. We prefer to use weblogic.Admin to do this because we can run the weblogic.Admin GETSTATE command against each individual instance (which I have not been able to do with weblogic.WLST - you have to run the weblogic.WLST state command only via the admin instance which if the admin instance is down you won't be able to tell the state of the other instances in the domain.
I'm hoping that if we can find a way to "tell" webogic.WLST where the boot.properties file is located.
Putting a copy of the boot.properties file in the domain root works fine - but I don't have to do this based on the documentation provided by Oracle.
Any help is appreciated.

Hi,
It is better to create the "userConfig" file abd pass it to the WLST connect() function...
How to create user Config file:
BEA_HOME :- /usr/bea10mp1
WL_HOME :- BEA_HOME/wlserver_10.0
STEP-1) Go to WL_HOME/server/bin and set the environment by executing "setWLSEnv.sh".
STEP-2) Then execute below command which generate "*userconfig*" and "*userkey*" files in the directory you had execute this command
java weblogic.Admin -adminurl t3://adminserverl:port -username <adminusername> -password <adminpassword> -userconfigfile userconfig -userkeyfile userkey -STOREUSERCONFIG
This command prompts for "Y" or "N", select "Y", then creates two files "userconfig" and "userkey"
STEP-3) Validate above keys are correct, execute below command
java weblogic.Admin -adminurl t3://adminserverl:port -userconfigfile userconfig -userkeyfile userkey -GETSTATE
Above command should display "RUNNING".
STEP-4) Now you can use the following link of connect() in your WLSt script...
connect(userConfigFile='/usr/someLocation/userconfig',userKeyFile='/usr/someLocation/userkey',url='t3://localhost:7001')
Why we need to create userConfig ...please see below...
http://download-llnw.oracle.com/docs/cd/E12840_01/wls/docs103/config_scripting/reference.html#wp1049091
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)
Edited by: Jay SenSharma on Feb 24, 2010 10:26 AM

SSL certificate issue with WLS 10.3

Hi All,
I am facing this issue with my WLS cluster.
<21-Apr-2010 10:42:00 o'clock BST> <Warning> <Security> <BEA-090482> <BAD_CERTIF
ICATE alert was received from system.core.com - 10.15.135.30.
Check the peer to determine why it rejected the certificate chain (trusted CA co
nfiguration, hostname verification). SSL debug tracing may be required to determ
ine the exact reason the certificate was rejected.>
<21-Apr-2010 10:42:00> <Warning> <Uncaught exception in server handler: javax.ne
t.ssl.SSLKeyException: [Security:090482]BAD_CERTIFICATE alert was received from
system.core.com - 10.15.135.30. Check the peer to determine wh
y it rejected the certificate chain (trusted CA configuration, hostname verifica
tion). SSL debug tracing may be required to determine the exact reason the certi
ficate was rejected.>
Please suggest. I have also tried the below settings.
Node Manager:
-Dweblogic.nodemanager.sslHostNameVerificationEnabled=false
Admin Server:
-Dweblogic.security.SSL.ignoreHostnameVerification=true
Many thanks in advance.

Hi Sandip,
I am facing this issue right after when I have configured the listen address to my system IP in Machine(NodeManager), earlier it was "localhost".
Also I have tried to generate the certificates e.g.
C:\bea\wlserver_10.3\server\bin>java utils.CertGen -cn system.core.com -keyfilepass DemoIdentityPassPhr
ase -certfile mycertificate -keyfile .keystore
Generating a certificate with common name system.core.com and key strength 1024
issued by CA with certificate from C:\bea\WLSERV~1.3\server\lib\CertGenCA.der file and key from C:\bea\WLSERV~1.3\server
\lib\CertGenCAKey.der file
C:\bea\wlserver_10.3\server\bin>java utils.ImportPrivateKey -keystore DemoIdentity.jks -storepass DemoIdentityKeyStorePa
ssPhrase -keyfile .keystore.pem -keyfilepass DemoIdentityPassPhrase -certfile mycertificate.pem -alias demoidentity
No password was specified for the key entry
Key file password will be used
Imported private key .keystore.pem and certificate mycertificate.pem
into a new keystore DemoIdentity.jks of type jks under alias demoidentity
Tried the above but not wokring. Please advise.
Edited by: R Vashi on 21-Apr-2010 03:38

VARRAY mapping issues using WLS spk2 connection pools

We have an ongoing issue with VARRAY's and WLS Connection pools. The connection
pool of WebLogic does not support certain data structures of Oracle such as VARRAY.
To create array/struct object in java application, we have to register these
objects through array/struct descriptor methods. These methods require Oracle.sql.Connection
as a parameter. There is no way to get Oracle.sql.Connection from Weblogic Server
Connection Pool because the Oracle.sql.Connection is not serializable.
So, what is the recommended solution for a situation in which the application
tends to need to use VARRAYs and can we instead pass tables?
Any recommendations?

More information on this issue.
I'm using the method DriverManager.getConnection(URL) to get a connection to
the database, passing in the name of the connection pool. This method is
throwing the following SecurityException:
java.lang.SecurityException: User "john" does not have Permission
"reserve"
based on ACL "weblogic.jdbc.connectionPool.ICOM_DEV2_A".
When running under the LDAP realm:
-calls to getConnection() from within a jsp fail
-calls to getConnection() from within a Session Bean or Entity Bean work
-calls to getConnection() from a non-EJB class fail if it is called directly
from the jsp
-calls to getConnection() from a non-EJB class work if it is called from a
Session Bean
When running under the RDBMS realm, all calls to getConnection() work,
whether they are a jsp, non-EJB class or a Session Bean.
Is there some security context that is only present inside the EJB
container?

WLST startServer() fails

Hi,
I am trying to use the wlst command startServer() to start the admin server of a domain I just created in some earlier wlst steps. The domain is created as expected; however, when I try to start it I get an error telling me that the username and password found in the boot.properties file is invalid. Here is the exception...
weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid;The username and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
Does anyone have any idea why this is happening? Any suggestions as to how I get around it?
Thanks

apparently, a java bug (even in Java7u13) which is expected to be fixed in later releases.
for the time being, use -Dfile.separator=\/

Using Weblogic 9.1 WLST to connect to WLS 8.1.5 Server

Hello:
I have 2 questions:
Question 1: BEA documentation says WLST is support in version 8.*. However, I can't find weblogic.WLST class in v8.1 weblogic.jar. So do I need to get additional jars?
Question 2: I can launch weblogic.WLST in Weblogic v9.1 and it works fine to connect to other v9.1 servers. However, when connecting to v8.1 servers, it complains MBean Server is not initially property and it can't find weblogic.management.MBeanServer in InitialContext. Does that mean I need to do some configuration change on v8.1 server in order to accept WLST commands?
Thanks in advance!
Jenny Chen

Yes, you will need to download WLST for 8.1 from https://codesamples.projects.dev2dev.bea.com/servlets/Scarab?id=S13 and follow the directions to install in your environment.
No, connecting to WLS 8.1 servers from a 9.x WLST is not supported.
HTH,
-satya
BEA Blog:
http://dev2dev.bea.com/blog/sghattu/
Get Involved in CodeShare:
https://wls-console-extensions.projects.dev2dev.bea.com/
https://wlnav.projects.dev2dev.bea.com/
https://eclipse-wlst.projects.dev2dev.bea.com/
https://wlst.projects.dev2dev.bea.com/

We are having issues with WLS 5.1   pdf   SSL

We are running IE 5.0 and above browser with our application and the server is Weblogic 5.1 We are having issues with a generated pdf being sent down from the server using the response outputStream in an SSL connection. We tried setting the content type before getting the outputstream. IE comes back with a dialog for download. When we select either of the options IE comes back with "Unable to download <url> from <server>. We are using WLS 5.1 service pack 6. Any help will be greatly appreciated


          I tried this option, but did not help. We have two weblogic servers on different
          machines. One works fine in downloading pdf file over https, but not the other.
          The error we are getting after selecting it to save it to a file:
          IE cannot download xx.pdf from www.xxx.com
          From the link, when we say "save target as", we get different error as:
          This file could not be written to cache.
          Someone suggested to pass "pragma: public" or "pragama: no-cache" in the header.
          But we are just simply serving it as a file, neither from servlet nor from jsp.
          So I suspect it something to do with our weblogic proxy or security configuration.
          Any ideas/help is much appreciated.
          Thanks
          Jayashree Raghavan <[email protected]> wrote:
          >If you ever have a similar problem it might help to check in browser
          >settings.
          >In IE goto tools/internet options/
          >Goto advanced Tab
          >go down to Security.
          >Uncheck the "donot save encrypted pages to disk".
          >This will make downloading a pdf work in ssl.
          >
          >
          >Jayashree Raghavan wrote:
          >
          >> We resolved this problem thanks to Maxim, by commenting out the code
          >that sends to the browser not to cache these pdf files. response.setHeader("Pragma",
          >"no-cache");
          >

How to get some good docs for general troubleshooting issues of WLS 8.1?

Hi,
In my company we just have started WLS, m working as WLS admin.
How can i get some good docs for general issues as I m facing a lot problem in this early stage.
If ther is any link, or community which can help me?
I have tried on google n got some basic info.
I think ther r some useful info is available on the site " http://eudownload.bea.com/" but m not able to open it.....is this url is changed?

Troubleshoot Cluster :-
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/cluster/trouble.html
Troubleshoot JMS :-
http://download-llnw.oracle.com/docs/cd/E13222_01/wls/docs92/jms_admin/troubleshoot.html
Troubleshoot SAF :-
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/saf_admin/troubleshoot.html
Troubleshoot JDBC:-
http://download-llnw.oracle.com/docs/cd/E13222_01/wls/docs81/jdbc/troubleshooting.html
Troubleshoot JTA:-
http://download.oracle.com/docs/cd/E11035_01/wls100/jta/trbtrx.html
Its more or less same for all versions. You can refer to specific version docs. Hope this helps.

SAAJ issue on WLS

Hello,
I have deployed OPA determination server (10.1.0.27 from Edelivery) on my WLS 10.3.1. and I get this issue in the server log when calling the list-rulebases-request
<10.6.2010 9:30:04 CEST> <Error> <HTTP> <BEA-101017> <[weblogic.servlet.internal.WebAppServletContext@1e80719 - appName: 'determinations-server', name: 'determinations-server.war', context-path: '/determinations-server', spec-version: '2.5', request: weblogic.servlet.internal.ServletRequestImpl@15a8121[
POST /determinations-server/soap HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: text/xml;charset=UTF-8
SOAPAction: "http://oracle.com/determinations/server/10.0/server/types/ListRulebases"
User-Agent: Jakarta Commons-HttpClient/3.1
Content-Length: 260
]] Root cause of ServletException.
java.lang.UnsupportedOperationException: This class does not support SAAJ 1.1
     at weblogic.webservice.core.soap.SOAPMessageImpl.getSOAPBody(SOAPMessageImpl.java:634)
     at com.oracle.determinations.server.servlet.SOAPAction.doAction(SOAPAction.java:324)
     at com.oracle.determinations.server.servlet.DeterminationsServerServlet.doPost(DeterminationsServerServlet.java:227)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
     Truncated. see log file for complete stacktrace
Any idea?
Thank you, Ladislav.

Hi Ladislav,
If you look at the section "Deploying Oracle Determinations Server to a Java Application Server" in the Oracle Policy Automation Installation Guide ("Oracle Policy Automation Installation Guide.pdf") you will see that Oracle Determinations Server requires the application server to support SAAJ 1.1, and includes the following guidance:
There is a specific procedure for enabling SAAJ 1.1 support for Oracle Weblogic. This is outlined in the Section Deploying Oracle Determinations Server for Java on Oracle WebLogic Server belowTherefore please read the section "Deploying Oracle Determinations Server for Java on Oracle WebLogic Server" for instructions on how to enable SAAJ 1.1 on Oracle WebLogic Server.

WLST Deployment Issue

Hi All,
I am doing one deployment using WLST deploy command passing appName,path and targets as arguments :-
deploy(appName='someName',path='Somepath/some.war' , targets='AdminServer')
I am executing this command like
/some_path/bea/wls92mp2/weblogic92/server/bin/setWLSEnv.sh from some directory
and then starting WLST and running this command
Command is working fine but it is creating a directory structure from the path where i am giving the command
PATH_FROM_WHERE_COMMAND_IS_EXECUTED/config/deployments/some.war/
some.war is the empty directory with same name of war file which i deployed.
I am bit new to wlst and can somebody help to tell its impact and how to get rid of it....thanks...

Hi,
I would suggest you to go through the below link which has the step by step way to use a WLST and the WLST script would deploy your application. It would surely help you.
Topic:Recursive Deployment Using WLST
http://middlewaremagic.com/weblogic/?p=303
Regards,
Ravish Mody
http://middlewaremagic.com/weblogic
Come, Join Us and Experience The Magic…

SSO using Kerberos issue in WLS 8.1 SP4

In the documentation, it is stated to if the host is myhost.bea.com the use must be named myhost. Is this the onl way, or may I have a user name different from my host name? Any help is greatly appreciated.
Erik

I've configured wls8.1 SP4 in a Windows 2000 Domain. The name of the user hasn't to be the same as the host. If you change it, you have to change jass login file and keytab too.

Start node manager using WLST

I am trying to start node manager using WLST with following command
wls:/offline> nmConnect('weblogic','weblogic123','localhost','5556','FirstDomain','C:\Oracle\Middleware\user_projects\domains\FirstDomain','plain')but getting below exception
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 123, in nmConnect
File "<iostream>", line 618, in raiseWLSTException
WLSTException: Error occured while performing nmConnect : Cannot connect to Node
Manager. : Connection refused: connect. Could not connect to NodeManager. Check
that it is running at localhost:5,556.
Use dumpStack() to view the full stacktrace
wls:/offline>
I am using weblogic 11g.
Can anybody let me know how to fix this issue.

You can use something like this:
beahome = '/home/oracle/soasuite';
pathseparator = '/';
adminusername = 'weblogic';
adminpassword = 'magic11g';
domainname = 'base_domain';
domainlocation = beahome + pathseparator + 'user_projects' + pathseparator + 'domains' + pathseparator + domainname;
nodemanagerhomelocation = beahome + pathseparator + 'wlserver_10.3' + pathseparator + 'common' + pathseparator + 'nodemanager';
print 'START NODE MANAGER';
startNodeManager(verbose='true', NodeManagerHome=nodemanagerhomelocation, ListenPort='5556', ListenAddress='localhost');
print 'CONNECT TO NODE MANAGER';
nmConnect(adminusername, adminpassword, 'localhost', '5556', domainname, domainlocation, 'ssl');
print 'START ADMIN SERVER';
nmStart('AdminServer');
nmServerStatus('AdminServer');More information can be found here: http://middlewaremagic.com/weblogic/?p=6040
in particular the "Starting the SOA environment" section

Wlst connect error in AIX 64 bit 10.3.3

What is the following?
I create a server using scripted WLST and call a
startServer('AdminServer','MyDomain'.....)
connect('weblogic','weblogic1','t3://xxxx:7019')
server is started. But connect fails with the following. The WLST script is OS unaware and works on Windows/HP/Solaris. The problem is only on AIX/64 bit/10.3.3. I can go to the MyDomain that I created and start the server using startWebLogic.sh. If I invoke weblogic.WLST from command line and I still get the following
=======================
AdminServer> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1282604457094> <BEA-080003> <RuntimeExceptio
n thrown by rmi server: weblogic.management.remote.iiop.IIOPServerImpl.newClient
(Ljava.lang.Object;)
java.lang.NullPointerException.
java.lang.NullPointerException
at org.apache.harmony.security.Util.equalsIgnoreCase(Util.java:46)
at org.apache.harmony.security.fortress.PolicyUtils.getPolicyURLs(PolicyUtils.java:429)
at org.apache.harmony.security.fortress.DefaultPolicy$1.run(DefaultPolicy.java:307)
at org.apache.harmony.security.fortress.DefaultPolicy$1.run(DefaultPolicy.java:300)
at java.security.AccessController.doPrivileged(AccessController.java:202)
at org.apache.harmony.security.fortress.DefaultPolicy.refreshImpl(DefaultPolicy.java:300)
at org.apache.harmony.security.fortress.DefaultPolicy.<init>(DefaultPolicy.java:202)
at org.apache.harmony.security.fortress.DefaultPolicy.<init>(DefaultPolicy.java:195)
at org.apache.harmony.security.fortress.DefaultPolicy.<init>(DefaultPolicy.java:182)
at java.security.Policy.getDefaultProvider(Policy.java:485)
at java.security.Policy.getAccessiblePolicy(Policy.java:524)
at java.security.ProtectionDomain.implies(ProtectionDomain.java:159)
at java.security.AccessController.checkPermission(AccessController.java:98)
at com.sun.jmx.remote.security.SubjectDelegator.checkRemoveCallerContext(SubjectDelegator.java:135)
at javax.management.remote.rmi.RMIConnectionImpl.<init>(RMIConnectionImpl.java:128)
at weblogic.management.remote.iiop.IIOPServerImpl.makeClient(IIOPServerImpl.java:69)
at javax.management.remote.rmi.RMIServerImpl.doNewClient(RMIServerImpl.java:243)
at javax.management.remote.rmi.RMIServerImpl.newClient(RMIServerImpl.java:192)
at weblogic.management.remote.iiop.IIOPServerImpl_WLSkel.invoke(UnknownSource)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Edited by: user9975126 on Aug 25, 2010 5:55 AM

This does not make any difference. I sourced setWLSEnv.sh. Manually started my server (and not through WLST startServer command)
And tried a
connect('weblogic','xxxxxxxxx','t3://xxxxxx:7019')
Server Console
=========
<Aug 24, 2010 7:18:16 AM EDT> <Warning> <RMI> <BEA-080003> <RuntimeException thr
own by rmi server: weblogic.management.remote.iiop.IIOPServerImpl.newClient(Ljava.lang.Object;)
java.lang.NullPointerException.
java.lang.NullPointerException
at org.apache.harmony.security.Util.equalsIgnoreCase(Util.java:46)
at org.apache.harmony.security.fortress.PolicyUtils.getPolicyURLs(PolicyUtils.java:429)
at org.apache.harmony.security.fortress.DefaultPolicy$1.run(DefaultPolicy.java:307)
at org.apache.harmony.security.fortress.DefaultPolicy$1.run(DefaultPolicy.java:300)
at java.security.AccessController.doPrivileged(AccessController.java:202)
Truncated. see log file for complete stacktrace>
WLST side
=======
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
wls:/offline> connect('weblogic','weblogic1','t3://xxxx01:7019')
Connecting to t3://xxxx01:7019 with userid weblogic ...
WLST detected that the RuntimeMBeanServer is not enabled. This
might happen if the RuntimeMBeanServer is disabled via the JMXMBean.
Please ensure that this MBeanServer is enabled. Online WLST cannot
function without this MBeanServer.
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 22, in connect
File "<iostream>", line 646, in raiseWLSTException
WLSTException: Error occured while performing connect : "Cannot connect to WLST.
Use dumpStack() to view the full stacktrace
========================
dumpStack()
wls:/xxxDomain/config> dumpStack()
This Exception occurred at Tue Aug 24 07:18:16 EDT 2010.
java.lang.NullPointerException
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
at weblogic.management.remote.iiop.IIOPServerImpl_1033_WLStub.newClient(Unknown Source)
at weblogic.management.remote.common.RMIServerWrapper.newClient(ClientProviderBase.java:339)
at javax.management.remote.rmi.RMIConnector.getConnection(RMIConnector.java:2339)
at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:291)
at weblogic.management.remote.common.WLSRMIConnector.doConnect(WLSRMIConnector.java:150)
at weblogic.management.remote.common.WLSRMIConnector.access$100(WLSRMIConnector.java:27)
at weblogic.management.remote.common.WLSRMIConnector$2.run(WLSRMIConnector.java:138)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.security.Security.runAs(Security.java:61)
at weblogic.management.remote.common.WLSRMIConnector.connect(WLSRMIConnector.java:136)
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:260)
at weblogic.management.scripting.WLSTHelper.lookupMBeanServerConnection(WLSTHelper.java:678)
at weblogic.management.scripting.WLSTHelper.initRuntimeServerConnection(WLSTHelper.java:398)
at weblogic.management.scripting.WLSTHelper.initConnections(WLSTHelper.java:315)
at weblogic.management.scripting.WLSTHelper.connect(WLSTHelper.java:203)
at weblogic.management.scripting.WLScriptContext.connect(WLScriptContext.java:61)
at weblogic.management.scripting.utils.WLSTUtil.initializeOnlineWLST(WLSTUtil.java:147)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:600)
at org.python.core.PyReflectedFunction.__call__(Unknown Source)
at org.python.core.PyMethod.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.core.PyObject.invoke(Unknown Source)
at org.python.pycode._pyx4.connect$1(<iostream>:16)
at org.python.pycode._pyx4.call_function(<iostream>)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyFunction.__call__(Unknown Source)
at org.python.pycode._pyx16.f$0(<console>:1)
at org.python.pycode._pyx16.call_function(<console>)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyCode.call(Unknown Source)
at org.python.core.Py.runCode(Unknown Source)
at org.python.core.Py.exec(Unknown Source)
at org.python.util.PythonInterpreter.exec(Unknown Source)
at org.python.util.InteractiveInterpreter.runcode(Unknown Source)
at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
at weblogic.management.scripting.WLST.main(WLST.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:600)
at weblogic.WLST.main(WLST.java:29)
Caused by: java.lang.NullPointerException
at org.apache.harmony.security.Util.equalsIgnoreCase(Util.java:46)
at org.apache.harmony.security.fortress.PolicyUtils.getPolicyURLs(PolicyUtils.java:429)
at org.apache.harmony.security.fortress.DefaultPolicy$1.run(DefaultPolicy.java:307)
at org.apache.harmony.security.fortress.DefaultPolicy$1.run(DefaultPolicy.java:300)
at java.security.AccessController.doPrivileged(AccessController.java:202)
at org.apache.harmony.security.fortress.DefaultPolicy.refreshImpl(DefaultPolicy.java:300)
at org.apache.harmony.security.fortress.DefaultPolicy.<init>(DefaultPolicy.java:202)
at org.apache.harmony.security.fortress.DefaultPolicy.<init>(DefaultPolicy.java:195)
at org.apache.harmony.security.fortress.DefaultPolicy.<init>(DefaultPolicy.java:182)
at java.security.Policy.getDefaultProvider(Policy.java:485)
at java.security.Policy.getAccessiblePolicy(Policy.java:524)
at java.security.ProtectionDomain.implies(ProtectionDomain.java:159)
at java.security.AccessController.checkPermission(AccessController.java:98)
at com.sun.jmx.remote.security.SubjectDelegator.checkRemoveCallerContext(SubjectDelegator.java:135)
at javax.management.remote.rmi.RMIConnectionImpl.<init>(RMIConnectionImpl.java:128)
at weblogic.management.remote.iiop.IIOPServerImpl.makeClient(IIOPServerImpl.java:69)
at javax.management.remote.rmi.RMIServerImpl.doNewClient(RMIServerImpl.j
at javax.management.remote.rmi.RMIServerImpl.newClient(RMIServerImpl.java:192)
at weblogic.management.remote.iiop.IIOPServerImpl_WLSkel.invoke(UnknownSource)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
java.lang.NullPointerException
wls:/xxxDomain/config>
Edited by: user9975126 on Aug 24, 2010 4:54 AM

Error removing data from MDS using WLST

I'm new at MDS so i want to remove some data which I inserted in the wrong structure....sounds quite easy. After some looking around I should be able to do this using a deployment plan and WLST. I chose the last one as I am not realy familiar yet with deployment plans. I connect with my server and started WLST did the following:
wls:/offline> connect ('weblogic', 'mypassword' , 't3://localhost:8001')
Connecting to t3://localhost:8001 with userid weblogic ...
Successfully connected to managed Server 'soa_server1' that belongs to domain 'MY_DOMAIN'.
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
wls:/MY_DOMAIN/serverConfig> deleteMetadata(application='soa-infra', server='soa-server1', docs='/apps/deploy/*')The outcome was:
Location changed to custom tree. This is a writable tree with No root.
For more help, use help(custom)
and after a while it closed the WLST connection. Can anyone tell me how I can remove data from my repository or what is going wrong here?
Thanks in advance

Hi,
I think you were getting this error because you had your server name incorrect : soa-server1 instead of soa_server1. Also it might be possible that soa-infra is installed on the different server.
Regards,
Neeraj Sehgal

WLST startserver issues in WLS 12.1

Similar Messages

Maybe you are looking for