Problem using WebLogic Scripting Tool
Hi,
I'm new to weblogic. I tried to deploy WAR file to weblogic(installed on my PC) using WLST. I got the following error message.
Problem invoking WLST - Traceback (innermost last):
[exec] File "C:\TutorialHome\CDB\buildfiles\localhost.py", line 7, in ?
[exec] File "<iostream>", line 354, in activate
[exec] WLSTException: 'Error occured while performing activate : Error while Activating changes. Use dumpStack() to view the full stacktrace'
[exec] <Apr 21, 2009 1:24:43 PM EDT> <Warning> *<JNDI> <BEA-050001> <WLContext.close() was called in a different thread than the one in which it was created.>*
Here is my hostlocal.py:
connect('weblogic','weblogic','t3://localhost:7001')
stopApplication('cdb')
edit()
startEdit()
progress=redeploy('cdb')
save()
activate()
startApplication('cdb')
disconnect()
exit()
So How can I solve the problem of "<BEA-050001> <WLContext.close() was called in a different thread than the one in which it was created.>"?
Thanks in advance.
Sarah
Check the blend modes for the brush tool in the tool options bar.
Also if your painting on a blank layer check the blend modes in the layers panel.
Either way try the Normal mode.
MTSTUNER
Similar Messages
-
Anyone tried the new Weblogic Scripting Tool (WLST)?
Has anyone tried using the new WebLogic Scripting Tool (WLST) that was recently
posted on the dev2dev WebLogic Utilities site: http://dev2dev.bea.com/resourcelibrary/utilitiestools/adminmgmt.jsp
It looks to be a handy tool that is built upon jython and enables you to easily
navigate, inspect and manipulate the WebLogic MBean tree on a running server.
It also has a nice scripting tool which allows you to convert a config.xml file
into a script that can be run to recreate a domain or specific resources within
the domain. This is exactly something I have been looking for because we occasionally
recreate domains or subsets of a domain for testing and POC purposes.
The utility is fairly well documented and works well for the most part. The only
issue I have run into so far is that is does not seem to understand JMS Distributed
Destinations. When I try to convert a config.xml that contains a DD to a script
it throws a null pointer exception. I have not tried a cluster yet.
I noticed the utility was authored by someone at BEA. Is there potential that
BEA will support this in the future if it catches on? Has anyone had experience
with WLST or jython that would cause you to reccomend (or not) using it?
Thanks.Darryl,
Thanks for the valuable feedback. My comments are inline.
Darryl Stoflet wrote:
As a fairly long time wlshell user who recently started testing wlst there are
few features I have found lacking in wlst.
1. For monitoring purposes I am frequently using the -g and -r options to wlshell's
get command for graphing and repeating respectivelyI haven't looked at -g and -r options in wlshell, but will do so.
Although there is no graphical monitoring of attributes in wlst, but
there is certainly some monitoring capability (which will be enhanced
further in the coming version). Please take a look at the
monitorAttribute() function.
wls:/(offline)> help('monitorAttribute')
Description:
Monitors the specified attribute every by polling every interval.
Syntax:
monitorAttribute(attributeName, interval, monitorFile)
attributeName = Name of the attribue that you would like to monitor.
interval = Time (in seconds) to wait before the next fetch
monitorFile=[optional] File path where the monitored data will be
written to.
Example:
wls:/mydomain/runtime/ServerRuntimes/myserver/ExecuteQueueRuntimes/weblogic.kernel.Default>
monitorAttribute("ServicedRequestTotalCount",10)
Press Return to quit monitoring
Monitoring started for attribute ServicedRequestTotalCount
wls:/(offline)>
>
2. wlshell 2.0 adds the option when connecting to the admin server to also connect
to all managed servers in that domain. This is a nice feature for monitoring because
you then have access to all the runtime mbeans in each managed serverYes, this indeed seems to be a very nice feature. We will consider this
for our next release.
>
3. There is not a good way to pass cmd line options(variables) to wlst. In wlshell
I can send cmd line options via -v. I have tried something similar with wlst using
-loadProperties but this is a little laborious because I do not necessarily want
to create a properties file when a passing in only one or two variables. Also
I find loadProperties lacking somewhat (see 4 below)ok, I just realised that there is indeed a bug in wlst where the command
line arguments are not being honored. In Jython one can access the
command line arguments from the sys.argv variable. For example,
java weblogic.WLST -i foo.py var1 var2 var3
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to Weblogic Server Administration Scripting Shell
Type help() for help on available commands
wls:/offline> print sys.argv
['foo.py', 'var1', 'var2', 'var3']
wls:/offline>
But this isn't working properly, please keep using the loadProperties
untill this has been fixed.
>
4) loadProperties treats all created variables as strings. While this is understandable
from the perspective that getProperty returns a string, it would be nice if wlst
was smart enough that when a property is numbers only its an int, otherwise a
string etc.
wlshell does this logic/conversion for you which really simplifies calling methods
that expect the particular datatype. To get around this problem you can create a script file say,
variables.py which would look like,
# variables that will be used
theInterpreter.set('var1',10)
theInterpreter.set('var2','i am a string')
java weblogic.WLST variables.py
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to Weblogic Server Administration Scripting Shell
Type help() for help on available commands
wls:/(offline)> print var1
10
wls:/(offline)> print var2
'i am a string'
>
5. I'd like to be able to send cmd output etc to a file while running within wlst.
In wlshell its a simple as adding >> filename to the end of the command. In wlst it is not as simple as doing >>, it is more than that. You can
choose any output stream to direct your output to. In your case you can
create a FileOutputStream and route the output to this stream for any
particular command.
Example,
# create a file output stream say fos
from java.io import FileOutputStream
fos = FileOutputStream("output.txt")
# save the default output stream to a variable to
# switch it back
sys.stdout=fos
# Now all output for any function will go to output.txt
ls()
cd('foo')
# after done with your functions switch it back
sys.stdout=origOutput
This is the right Jython way to do it. This works for all output streams
, very useful when you embed an interpreter in a servlet and would like
to display the output via a PrintStream etc.
>
>
All in all wlst is a nice tool. Personally if the above features were added it
would be much easier to transistion to wlst for good.
Also I really like the wlst offline tool. Its nice to be able to do the whole
create and configure domain process with one tool. Will this be supported. Yes indeed. We are working on merging both the tools into one.
I do
not want to rely on it too much if it will not work in future weblogic versions.It will be supported in future release of weblogic.
Thanks,
-satya
>
Thanks,
Darryl
"Steve Hess" <[email protected]> wrote:
Hello,
I am the BEA Product Manager behind WLST.
WLST, as it appears today on dev2dev, is an early release version of
a tool that
BEA does intend to support as part of our next major release. We decided
to issue
early versions of the tool because of the demand for a supported scripting
solution,
and to generate feedback from our user community. I encourage you to
work with
WLST, and assure you that this tool represents our current direction
in management
scripting.
Also note, this newsgroup can be used to issue questions, concerns and
feedback
about WLST. The engineering and PM team will monitor this group and
respond to
your questions as quickly as we can. While we will not be able to respond
to
every feature request, we really value your suggestions, and will endeavor
to
improve the tool in ways that meet your real-world needs.
Cheers,
Steve Hess
Director, WLS PM
"George Lupanoff" <[email protected]> wrote:
Has anyone tried using the new WebLogic Scripting Tool (WLST) that was
recently
posted on the dev2dev WebLogic Utilities site: http://dev2dev.bea.com/resourcelibrary/utilitiestools/adminmgmt.jsp
It looks to be a handy tool that is built upon jython and enables you
to easily
navigate, inspect and manipulate the WebLogic MBean tree on a running
server.
It also has a nice scripting tool which allows you to convert a config.xml
file
into a script that can be run to recreate a domain or specific resources
within
the domain. This is exactly something I have been looking for because
we occasionally
recreate domains or subsets of a domain for testing and POC purposes.
The utility is fairly well documented and works well for the most part.
The only
issue I have run into so far is that is does not seem to understandJMS
Distributed
Destinations. When I try to convert a config.xml that contains a DDto
a script
it throws a null pointer exception. I have not tried a cluster yet.
I noticed the utility was authored by someone at BEA. Is there potential
that
BEA will support this in the future if it catches on? Has anyone had
experience
with WLST or jython that would cause you to reccomend (or not) using
it?
Thanks. -
How to create a server through WLST ( Weblogic Scripting Tool ) ?
How to create a server through WLST ( Weblogic Scripting Tool ) ?
Thanks in advance...
SanjayHi Murugesh,
Thanks a lot for you reply..
I was able to create a server using create(). Is it possible to clone a server ?
When i create a server following tags is added to config.xml
<server>
<name>testServer_lab1</name>
<listen-port>43000</listen-port>
</server>
And if i do a clone through admin console, following is added to config.xml
<server>
<name>testServer2_lab1</name>
<machine xsi:nil="true"></machine>
<listen-port>7001</listen-port>
<cluster xsi:nil="true"></cluster>
<listen-address></listen-address>
<graceful-shutdown-timeout>120</graceful-shutdown-timeout>
</server>
If incase, cloning is not possible through WLST, can i add following
<machine xsi:nil="true"></machine>
<listen-port>7001</listen-port>
<cluster xsi:nil="true"></cluster>
<listen-address></listen-address>
<graceful-shutdown-timeout>120</graceful-shutdown-timeout>
under <server> tag which is created through WLST ?
I am using 9.2 version.
Regards
Sanjay -
Unable to capture the adf table column sort icons using open script tool
Hi All,
I am new to OATS and I am trying to create script for testing ADF application using open script tool. I face issues in recording two events.
1. I am unable to record the event of clicking adf table column sort icons that exist on the column header. I tried to use the capture tool, but that couldn't help me.
2. The second issue is I am unable to capture the panel header text. The component can be identified but I was not able to identify the supporting attribute for the header text.Hi keerthi,
1. I have pasted the code for the first issue
web
.button(
122,
"/web:window[@index='0' or @title='Manage Network Targets - Oracle Communications Order and Service Management - Order and Service Management']/web:document[@index='0' or @name='1824fhkchs_6']/web:form[@id='pt1:_UISform1' or @name='pt1:_UISform1' or @index='0']/web:button[@id='pt1:MA:0:n1:1:pt1:qryId1::search' or @value='Search' or @index='3']")
.click();
adf
.table(
"/web:window[@index='0' or @title='Manage Network Targets - Oracle Communications Order and Service Management - Order and Service Management']/web:document[@index='0' or @name='1c9nk1ryzv_6']/web:ADFTable[@absoluteLocator='pt1:MA:n1:pt1:pnlcltn:resId1']")
.columnSort("Ascending", "Name" );
} -
Urgent - How to Run a FM using CATT script tool,
Hi All,
How to Run a FM using CATT script tool,
Thanks in advance,
KSRchoose type as "Function module test" (if you are in release less than 6.4 abap) after entering into t.code SCAT.
Pl. refer to this documentation for creating function module test cases
<a href="http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCCATTOL/CACATTOL.pdf">http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCCATTOL/CACATTOL.pdf</a>
reward if it helps
Krishna -
How to use weblogic.DDconverter Tool to upgrade Deployment Descriptors.
Hi,
I want to know how to use weblogic.DDconverter Tool to upgrade Deployment Descriptors using EAR of previous verisons(JDK and weblogic).
Regards,
NeerajLooks like the protocol is not correct (Unable to connect to 'http://localhost:7001': Destination unreachable)
Could you try the t3 protocol, for example,
java weblogic.Deployer -adminurl t3://localhost:7001 -username weblogic -password welcome1 -listapps -
Weblogic 8.1 and Eclipse using Weblogic Server Tools
I am working on a project that has been developed with Weblogic 8.1 without integration into an IDE (Eclipse, etc.) We are trying to convert the source tree to a form usable within Eclipse using Weblogic Server Tools. We want to make deployment on developer workstations quicker and easier and provide for server side debugging. There is not much documentation on how to do this that I have been able to find. I have just finished reading the details of the split directory strucuture in the Weblogic documentation and understand that Server Tools uses the split directory concept. My question is basically how we create the project in Eclipse (with Server Tools plug-ins) initially. Is anyone out there still using Weblogic 8.1 and Eclipse 3.3 (Europa) using Weblogic Server Tools that can help?
There isn't much in a way of documentation that's explicit to WebLogic Server Tools, but a lot of Workshop 10.2 documentation applies. Basically, you will want to create Dynamic Web Projects to house your code. On the first page of Dynamic Web Project wizard, you will get a chance to define and target a server (WLS 8.1 in your case). That will configure your project classpath for WLS 8.1 and get everything else squared away.
Note that there is only very basic support for 8.1. In particular, the split-directory concept is not supported, but deployment is taken care of for you behind the scenes, so the details shouldn't matter that much. -
Problem using weblogic.jspc with wls6.1
I've got this error using weblogic.jspc on jsp that works fine with the compiler
of 5.1, is this a bug?
java.lang.NullPointerException
at weblogic.management.Admin.getServer(Admin.java:1252)
at weblogic.servlet.internal.dd.ServletEntityResolver.initServerMBean(ServletEntityResolver.java:69)
at weblogic.servlet.internal.dd.ServletEntityResolver.resolveEntity(ServletEntityResolver.java:94)
at weblogic.apache.xerces.readers.DefaultEntityHandler.startReadingFromExternalEntity(DefaultEntityHandler.java:749)
at weblogic.apache.xerces.readers.DefaultEntityHandler.startReadingFromExternalSubset(DefaultEntityHandler.java:566)
at weblogic.apache.xerces.framework.XMLDTDScanner.scanDoctypeDecl(XMLDTDScanner.java:1139)
at weblogic.apache.xerces.framework.XMLDocumentScanner.scanDoctypeDecl(XMLDocumentScanner.java:2215)
at weblogic.apache.xerces.framework.XMLDocumentScanner.access$0(Compiled
Code)
at weblogic.apache.xerces.framework.XMLDocumentScanner$PrologDispatcher.dispatch(Compiled
Code)
at weblogic.apache.xerces.framework.XMLDocumentScanner.parseSome(Compiled
Code)
at weblogic.apache.xerces.framework.XMLParser.parse(XMLParser.java:967)
at weblogic.apache.xerces.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:175)
at weblogic.servlet.internal.dd.DescriptorLoader.parse(DescriptorLoader.java:311)
at weblogic.servlet.internal.dd.DescriptorLoader.initializeWebXml(DescriptorLoader.java:327)
at weblogic.servlet.internal.dd.DescriptorLoader.initialize(DescriptorLoader.java:242)
at weblogic.servlet.internal.dd.DescriptorLoader.<init>(DescriptorLoader.java:176)
at weblogic.servlet.internal.dd.DescriptorLoader.loadDescriptor(DescriptorLoader.java:396)
at weblogic.jspc.runBodyInternal(Compiled Code)
at weblogic.jspc.runBody(jspc.java:169)
at weblogic.utils.compiler.Tool.run(Tool.java:79)
at weblogic.jspc.main(Compiled Code)
--------------- nested within: ------------------
weblogic.utils.AssertionError: ***** ASSERTION FAILED ***** - with nested exception:
[java.lang.NullPointerException]
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Error.<init>(Error.java:50)
at weblogic.utils.NestedError.<init>(NestedError.java:24)
Please post your full description. I can't see what you're replying to (must
be too old).
Alex
"Gregory Chazalon" <[email protected]> wrote in message
news:3c7383a8$[email protected]..
> I've got te same problem (NullPointerException at the same line code in
the same class). The most disturbing is that the weblogic.jspc works fine
with wl6.1 SP2 but fails with wl6.1 SP1.
>
> Do you have a solution ? Can I download a CRXXXX.jar that fixes it ?
>
> I will appreciate any help.
>
-
Problem using Weblogic 6 and Weblogic 8.1 thin clients from same applicatio
We are developing a application where we require to communicate with 2 different ?Webogic Servers? running different versions.
First server is ?Weblogic 6.1 SP7? and the other is ?Weblogic 8.1?. We use Weblogic thin client jars to connect to these servers. Protocol used to connect to ?Weblogic 8.1? is t3 and for ?Weblogic 6.1 SP7? its t3s. But the obvious problem is that both thin client can not be used simultaneously in the same class-path. Whichever jar file appears first in the class-path, classes will be loaded from that jar. This is causing breakage in our application. If we put ?Weblogic 6.1 SP7? thin client jar first in the path, our application throws exception while connecting to ?Weblogic 8.1? and if we put ?Weblogic 8.1? jar first the path, ?Weblogic 6.1 SP7? won?t connect. Is there a workaround to handle this problem. We have admin level access to Weblogic 8.1 which mean we can change the configuration here if required but we have only user level access to ?Weblogic 6.1 SP7? and can?t do any modification in server config.
Exceptions:
Case 1: ?Weblogic 6.1 SP7? thin client jar first in class-path.
Result : connects successfully with ?Weblogic 6.1 SP7?.
throws following exception while connecting to ?Weblogic 8.1?.
weblogic.common.internal.VersioningError: Incompatible packages in CLASSPATH: (BEA Systems, WebLogic Server 6.1 SP7 08/30/2004 22:36:21 #428658 , 6.1.7.0) not compatible with (BEA Systems, WebLogic Server 8.1 SP3 Thu Jun 10 14:16:50 PDT 2004 396756 , 8.1.3.0)
at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:118)
at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
at weblogic.kernel.Kernel.initialize(Kernel.java:138)
at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:117)
at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:308)
at java.lang.Class.newInstance(Class.java:261)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
java.lang.InternalError: error initializing kernel
at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:120)
at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:308)
at java.lang.Class.newInstance(Class.java:261)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
Case 2: ?Weblogic 8.1? thin client jar first in class-path.
Result : connects successfully with ?Weblogic 8.1?.
throws following exception while connecting to ?Weblogic 6.1 SP7?.
avax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)TRWLClientBinder.InitialContext NamingException try#: 0 attempt: -1 threadID: 31505976 message: javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
... 16 more
Couldn't connect to any host
Cause: {1}
javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)01/12|15:35:54.279|TRClientBinder.jndiBind TRConnectException, try#: 0 attempt: -1 Message: Couldn't connect to any host
Cause: {1}
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
... 16 moreuday naik <> writes:
The thin-client isn't supported on 6.1, I'm not sure what you are doing.
andy
We are developing a application where we require to communicate with 2 different ?Webogic Servers? running different versions.
First server is ?Weblogic 6.1 SP7? and the other is ?Weblogic 8.1?. We use Weblogic thin client jars to connect to these servers. Protocol used to connect to ?Weblogic 8.1? is t3 and for ?Weblogic 6.1 SP7? its t3s. But the obvious problem is that both thin client can not be used simultaneously in the same class-path. Whichever jar file appears first in the class-path, classes will be loaded from that jar. This is causing breakage in our application. If we put ?Weblogic 6.1 SP7? thin client jar first in the path, our application throws exception while connecting to ?Weblogic 8.1? and if we put ?Weblogic 8.1? jar first the path, ?Weblogic 6.1 SP7? won?t connect. Is there a workaround to handle this problem. We have admin level access to Weblogic 8.1 which mean we can change the configuration here if required but we have only user level access to ?Weblogic 6.1 SP7? and can?t do any modification in server config.
Exceptions:
Case 1: ?Weblogic 6.1 SP7? thin client jar first in class-path.
Result : connects successfully with ?Weblogic 6.1 SP7?.
throws following exception while connecting to ?Weblogic 8.1?.
weblogic.common.internal.VersioningError: Incompatible packages in CLASSPATH: (BEA Systems, WebLogic Server 6.1 SP7 08/30/2004 22:36:21 #428658 , 6.1.7.0) not compatible with (BEA Systems, WebLogic Server 8.1 SP3 Thu Jun 10 14:16:50 PDT 2004 396756 , 8.1.3.0)
at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:118)
at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
at weblogic.kernel.Kernel.initialize(Kernel.java:138)
at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:117)
at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:308)
at java.lang.Class.newInstance(Class.java:261)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
java.lang.InternalError: error initializing kernel
at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:120)
at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
at java.lang.Class.newInstance0(Class.java:308)
at java.lang.Class.newInstance(Class.java:261)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
Case 2: ?Weblogic 8.1? thin client jar first in class-path.
Result : connects successfully with ?Weblogic 8.1?.
throws following exception while connecting to ?Weblogic 6.1 SP7?.
avax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)TRWLClientBinder.InitialContext NamingException try#: 0 attempt: -1 threadID: 31505976 message: javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
... 16 more
Couldn't connect to any host
Cause: {1}
javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)01/12|15:35:54.279|TRClientBinder.jndiBind TRConnectException, try#: 0 attempt: -1 Message: Couldn't connect to any host
Cause: {1}
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
at javax.naming.InitialContext.init(InitialContext.java:219)
at javax.naming.InitialContext.<init>(InitialContext.java:195)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
... 16 more -
Problem using PSE9 Brush Tool!
I am experiencing a problem using the PSE9 Brush Tool. The color does produced by the brush not match the color of the sample picked by the Eyedropper Tool, Painting near the area where the sample was picked-up results in a much darker color.
Check the blend modes for the brush tool in the tool options bar.
Also if your painting on a blank layer check the blend modes in the layers panel.
Either way try the Normal mode.
MTSTUNER -
I am already paying a subscription for Adobe Acrobat XI Pro Now it want me to buy when using the edit tool or even the tool to insert pages Never had that problem before??????????????
Acrobat Reader can't edit PDF files. Use Adobe Acrobat Pro DC.
-
Z68a-GD65 (G3) Problems Using USB Bootable Tool 1.25g
I am having problems using the USB Bootable Tool 1.25g with the P77, P80, and P82 BIOS's. I have tried both modes 1 and 2. Both modes copy over everything successfully. When booting using the bootable USB drive, after copying the BIOS file via mode 1, the tool flashes a screen very quickly, then says BIOS updated successfully. This is not true, however, because nothing has been updated. I see something rapidly go 1-2-3-4-5, but the progress indicator I was familiar with with the old version of the USB Bootable tool does not show up, where the BIOS file was being copied block by block and took some time.
Mode 2 doesn't work either. I get the message "ROMFILE ROMID is not compatible with existing BIOS". This happened with all three BIOS's, using mode 2. I have tried the "Fix my USB Key" option, and have tried clearing the CMOS as described in the instructions on the forum. As a test, I used the M-Flash in the BIOS and was able to flash to P80. P80 is giving me problems with an Intel Management Mode HECI error which disappears when I start the PC, as well as me being unable to raise the base clock speed--even though it shows as raised in the BIOS and it saves the setting. I am now stuck with P80. Now I cannot flash to any other BIOS using the M-Flash utility, as it doesn't find the BIOS file I manually copied over to the drive. The USB bootable tool will not work.I did use mode 1, although since I was having trouble, I used mode 2 also, after reading troubleshooting instructions for the USB BIOS tool. The archives I used were all ones I downloaded from the Beta BIOS thread I posted above.
The problems I was having with P80 were actually because I unknowingly was using the N20 BIOS because somehow my BIOS reverted to that. I have no idea how that happened, aside from that possibly being the failsafe BIOS as part of the dual bios system. Above, I meant to say that I flashed the BIOS through Windows when I had success with the P80 BIOS. The M-Flash utility does not read the BIOS files which are available on this forum. -
Problem using Radial Gradient tool in Creative Suite CS4.
I have pasted on a separate layer a circular photo of a couple's head and shoulders onto a woodland photo, and want to make the sides of it gradiently transparent using the Radial Gradient tool. The problem I have is that it makes all of the photo gradiently transparent.
If I use the Linear Gradient tool it works fine, but only on one part and I can't add it to other parts of the photo.
Am I using the right tool for the job, and if I am, where am I going wrong?
Any help would be much appreciated. Thanks.here I send 2 versions, one is the hand done one as I mentioned, before, re mask then use black brush, the second is the circle feather edge again as mentioned but I left in the layers to give you an idea too
the first allows you more freedom to kill background as I notice the top is flat, I assume that's the edge if the original photo -
Problems using the bone tool, CS4?
Okay so I have spent countless hours trying to figure this out. I want to use the bone tool to make a leg animation. First I create a new symbol called Leg. I double click the Leg in the library which opens it in leg window. Then I grab the circle tool in the tool bar and make the thigh. Then I make another circle for the leg. Now the problem is when I click the bone tool to connect them, it won't let me connect the thigh with the leg! Can somebody tell me why this is happening? (This is all done on one layer).
However when I click the circle tool and then click object drawing tool in the bottom of the tool bar I then can connect both the thigh and the leg with the bone tool. Problem is when I use this feature if I want to move the shapes to revise it a little they wont seperate. The thigh is stuck to the leg.
Some please please help me.. this is making me angry!
I want to be able to draw a leg with a couple shapes and be able to connect the bone tool to one shape to the other. Thanks RossiFollowing article covers how to add bones to Symbols:
http://help.adobe.com/en_US/flash/cs/using/WS14DAFDB4-B9AD-4080-A29F-022128CCFD39.html -
Weblogic Scripting Tool help required
Hi,
Can anyone please help me in creating a new WLS domain which is exactly same as an another existing WLS domain, by using WLST scripts? Suppose I have my own domain, which is having a admin server, and two managed servers, and some resourse configuraions(JDBC, JMS, etc) and application deployments, then I want to create the same domain configuration on another machine, by just running a WLST script. Is it possible? If yes, how should I create a WLST script for doing that?? Please answer to my query at the earliest.
Thanks in advance,
SeshuHello Kalluri,
Have you tried configToScript? You can run configToScript on a config.xml to create a wlst script and a properties file. You can change the server names, domain name etc in the properties file and run the script on a different machine to create the same configuration. The script might need a little tweaking depending on any errors or any encrypted passwords.
Thanks,
-satya
Maybe you are looking for
-
HT1212 i still cant unlock my ipad
i forgot my passcode, and can't unlock my ipad
-
Doing queries in view objects that do not include primary keys of entities
Is it possible to create a view object based on an entity that doesn't include the primary key from that entity object. For instance I want to do something like "select distinct (attrib1) from sometable" and obviously attrib1 is not the primary key f
-
Error when opening Database.
Hii, IM facing error when trying to open the database, My apps:11.5.10.2 my Database:10.2.0.4 i have successfully run adcfgclone dbTechStack on Database Tier, but when i try to open the database im getting the following error, Errors in file f:\dev\d
-
If I send files via Adobe Send, the recipient gets an email from "John Smith via Adobe Send." I want it to read as being from my company, not me personally, as in "Acme Services via Adobe Send." How do I make that change?
-
Add speed on a mac book pro 10.6.8
add more speed to a mac book pro version 10.6.8