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/
Similar Messages
-
One of our customers starts to encounter this error message recently.
We checked our log files. It seems that the error happens when
to obtain a jdbc connection. Have anyone seen similar problems
and knows how to fix it? thanks in advance.
We are using weblogic server 6.1sp2, and weblogic sql type 4 driver.
The functions that invoke the jdbc calls are stateless session bean
methods with their transaction attributes marked as Required.
There is no nested calls of these methods.
A partial stack trace we obtained is as following:
java.sql.SQLException: No JDBC connection can be made
because the transaction state is
Marked Rollback
at weblogic.jdbc.jts.Connection.getOrCreateConnection(Connection.java:586)
at weblogic.jdbc.jts.Connection.prepareStatement(Connection.java:115)
at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:135)
at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:76)
lixinJoseph Weinstein <[email protected]> wrote:
>
>
YuanHui Liu wrote:
Joe,
We got the exact same error message. The error came after we got theJDBC connection,
and trying to create statement off it.
It occurs intermitently when we are running another standalone JAVAapp to do
some end of day work, which results in the DB Server being very busy(90+%CPU
usage) for about 5 minutes. We see a surge of requests to the WLSJDBC Connection
pool. This would sometimes result in all our subsequent DB requeststo fail and
lead to a crash.
We are using WLS6.0SP1. I do not think there's a 30 seconds wait leadingto a
connection timeout that caused this(rather it is the end effect).
Can you give us a more detailed explanation? Is there a miscommunicationbetween
our DB(Sybase12) and WLS?Hi. It looks to you like it's after you get the connection, but really
it's when the server is
gettng the pool connection. For performance/synchronization reasons we
do a clever
delay: When your code asks for a pool connection we quickly give you
the pool wrapper,
but we delay actually reserving the real underlying DBMS connection until
your first
real need for a connection, at your first JDBC call, such as createStatement()
etc.
It is while waiting for a pool connection long enough for the transaction
coordinator
to have timed you out before you ever get a chance. It's nothing to do
with the
DBMS or even JDBC, I believe. I think the weblogic server either has
too few execute-threads
and/or too few CPU cycles to do the work load.
Okay, so there's a lazy initialization of the connection.
From reading our log I believe our failur is immediate rather
than waiting for 30+ seconds(the default setting) from the DB,
the timeout occurred later as a result. At the time either because the DB Server
is very busy.
Since we are running WLS6.0 we have only one connection pool,
we have defined a max of 150 threads in the pool. While this
is happening the DB Server is being pinned by an overnight job,
but the WLS Server is not busy at all. The DB and WLS resides
on different physical boxes.
We also have a thread dump from the WLS console when we rebooted the server, it
showed that we are hanging on to the thread & jdbc
connections after these exceptions has occurred instead of releasing them, note
"16083"(~4.5 hours) seconds has passed:
142 116222 Retry rollback request for tx: 'transaction=(IdHash=2963855,Name =
[EJB UserManagerBeanImpl.signalICUserServletHeartBeat()],Xid=30643:8f3838f3709bf53d,Status=Rolling
Back. [Reason = Unknown],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since
begin=16083,seconds left=10,ServerResourceInfo[weblogic.jdbc.jts.Connection]=(state=started,assigned=server),SCInfo[server]=(state=active),properties=({weblogic.jdbc=t3://159.55.158.25:8005,
weblogic.transaction.name=[EJB UserManagerBeanImpl.signalICUserServletHeartBeat()]}))'
Scheduled Trigger
So I would argue this problem actually chewed up resources on the WLS server.
-Yuanhui Liu
>>
>>
Thanks.
-YuanHui Liu
Joseph Weinstein <[email protected]> wrote:
lixin wrote:
One of our customers starts to encounter this error message recently.
We checked our log files. It seems that the error happens when
to obtain a jdbc connection. Have anyone seen similar problems
and knows how to fix it? thanks in advance.
We are using weblogic server 6.1sp2, and weblogic sql type 4 driver.
The functions that invoke the jdbc calls are stateless session bean
methods with their transaction attributes marked as Required.
There is no nested calls of these methods.
A partial stack trace we obtained is as following:
java.sql.SQLException: No JDBC connection can be made
because the transaction state is
Marked Rollback
at weblogic.jdbc.jts.Connection.getOrCreateConnection(Connection.java:586)Hi. This sounds like a JVM thread starvation issue, and/or a server
load
issue. What is
happening is that the transaction is started, and times out beforethe
SSB even gets to
the first JDBC work. I would first verify that the customer is using
the very latest JVM
available for the machine.
Joe Weinstein
at weblogic.jdbc.jts.Connection.prepareStatement(Connection.java:115)
at weblogic.jdbc.rmi.internal.ConnectionImpl.prepareStatement(ConnectionImpl.java:135)
at weblogic.jdbc.rmi.SerialConnection.prepareStatement(SerialConnection.java:76)
lixin -
How to prepend or append classpath using weblogic.Admin or WLST
When I call weblogic.Admin or WLST, is there any way to append or prepend to the existing classpath?
Currently I am calling weblogic.Admin with the following argument:
set -mbean base_domain:Name=base-server,Server=base-server,Type=ServerStart -property ClassPath "C:\test\test.jar"
But this overwrite the Server classpath with the new entry.
I want to keep the existing entries as it is and add the new one. Is it possible with Weblogic 8.1 or Weblogic 9.1fyi
A tricky SQL statement issue was fixed in the example application
at http://www.consideringred.com/files/oracle/2011/SQLAuthenticatorApp-v0.03.zip
So, it allows for the setup of a SQLAuthenticator (see README.txt for details), but in short : run Ant target "wlst.create-domain" (possibly preceded by Ant target "delete.domain-dir"), Ant target "create.wls-start-stop-bat-files", run wls-start.bat, setup tables TS_USER, TS_GROUP and TS_GROUPMEMBER, Ant target "wlst.create-datasource", Ant target "wlst.create-authentication-provider", run wls-stop.bat, run wls-start.bat, Ant target "wlst.create-user", Ant target "wlst.create-group.sqla-groupname", Ant target "wlst.add-user-member-to-group", deploy SQLAuthenticatorApp (using JDeveloper or otherwise), try http://localhost:7001/sqlauthenticatorweb , try to authenticate using tsusertwo/welcome1
Several Ant targets calling OPSS MBeans API were added (e.g. "wlst.opss.printmembersforallapplicationroles"), to review adding a SQLAuthenticator group as member to an application role, resulting in the forum thread "OPSS : addMembersToApplicationRole : The search for role failed"
at OPSS : addMembersToApplicationRole : The search for role failed
So, suggestions to resolve that grant application role issue are welcome in that forum thread.
regards
Jan -
Cannot use MAFLogon(iOS native apps) to connect to SMP 3.0 SP05 Server
Hi experts,
I have a problem when i try to use MAFLogon to logon/register on my SMP server ( im using iOS native Application). I fill some values, and waiting for login, but it doesnot work.
This is my config at MAFLogon UI Screen.
This is my application on SMP Server
This is my .plist config on MAFLogonManagerNG1.
When i run https://<ip_server>:443 in the Safari browser of iOS simulator, i cannot connect because of credential
>> you may have to import the certificate, i believe. Have a look at this.http://scn.sap.com/docs/DOC-50247
2.
As you say, i'm using Integration GW, when i try to ping the backend without "Internal" check, it works. When i check "Internal" and ping again, it still works.
>> Ideally, that option should be checked if endpoint URL is from IGW.
Should i replace https port 443 = 8083 ? Because the backend use https:<ip>:8083/...
>> 8083 port is admin port and used for accessing admin cockpit and gateway cockpit (plus all odata services listen on same port iff exposed via IGW) . 8083 is nothing to do with registration.
I suggest you to try with 8080 first. In that case you have to set secured channel off from login screen.
Regards,
JK -
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 -
With out using Weblogic libraries to maintain the same functionality
Hi,
Please tell the solution of my problem.Here application developed in Weblogic,now we are migrating that applicationin jboss.Here one java servlet program is there which is using Weblogic libraries to get the connection pool .
How can change the code without using Weblogic libraries to maintain the same funtionality. Is there any alternate method to get the connection pools in Jboss.
Here I am attaching the code ,please go througth the code and provide me the correct solution.
package gsk.servlets;
import java.io.*;
import java.sql.Connection;
import java.sql.Statement;
import java.sql.ResultSet;
import javax.naming.Context;
import javax.naming.NamingException;
import javax.management.*;
import javax.management.InstanceNotFoundException;
import javax.management.InvalidAttributeValueException;
import javax.management.Notification;
import javax.servlet.*;
import javax.servlet.http.*;
//Below lines are commnented by Anupama on 29-09-05 to avoid using Weblogic libraries.
//import weblogic.jndi.Environment;
//import weblogic.management.MBeanHome;
//import weblogic.management.MBeanCreationException;
//import weblogic.management.*;
//import weblogic.management.runtime.*;
//import weblogic.management.configuration.*;
//import weblogic.management.RemoteNotificationListener;
//import weblogic.management.logging.WebLogicLogNotification;
//import javax.management.Notification.*;
//below lines are added by Anupama T on 29-09-05 to run the same functionality without using Weblogic libraries
import org.jboss.management.*;
import org.jboss.jdbc.*;
import org.jboss.naming.*;
import org.jboss.management.j2ee.MBean;
import javax.management.AttributeChangeNotification;
import javax.management.JMException;
import javax.management.MalformedObjectNameException;
import javax.management.MBeanServer;
import javax.management.NotificationListener;
import javax.management.ObjectName;
import org.jboss.logging.Logger;
import org.jboss.system.ServiceMBean;
import gsk.adip.portal.GKMProperties;
import gsk.adip.dbconnectionservice.DatabaseConnector;
* @author jjc18400
* The ConnectionsManager class acts as a Servlet that listens and
* responds to events that are thrown by WebLogic MBeans. In particular,
* it listens for failures in WebLogic connection pools, and attempts to
* restore these pools.
public class ConnectionsManager extends HttpServlet implements NotificationListener {
private static Context ctx;
private static MBean managedHome;
private static MBean adminHome;
private static String SERVER_NAME;
private static String DOMAIN_NAME;
private static MBeanServer myServer;
private JDBCConnectionPoolRuntimeMBean connectionPoolMBean;
private JDBCConnectionPoolMBean jdbcConnPoolMBean;
private JDBCConnectionPoolMBean myPool;
private static ResultSet rset = null;
public void init(ServletConfig config) throws ServletException {
super.init(config);
System.out.println("Initializing the ConnectionsManager servlet.");
SERVER_NAME = GKMProperties.getProperty("GKM_SERVER_NAME");
DOMAIN_NAME = GKMProperties.getProperty("DOMAIN_NAME");
findMBeans();
testConnectionPool("GENNETConnectionPool");
try {
//findConnPool("GENNETConnectionPool").addNotificationListener(this, null, null);
RemoteMBeanServer rmbs = adminHome.getMBeanServer();
WebLogicObjectName oname =
new WebLogicObjectName("TheLogBroadcaster", "LogBroadcasterRuntime", DOMAIN_NAME, SERVER_NAME);
rmbs.addNotificationListener(oname, this, null, null);
catch (IllegalArgumentException e) {}
catch (MalformedObjectNameException e) {}
catch (InstanceNotFoundException e) {}
public void handleNotification(Notification notification, Object obj) {
WebLogicLogNotification wln = (WebLogicLogNotification)notification;
System.out.println("\nWebLogicLogNotification");
System.out.println(" type = " + wln.getType());
System.out.println(" message id = " + wln.getMessageId());
System.out.println(" server name = " + wln.getServername());
System.out.println(" timestamp = " + wln.getTimeStamp());
System.out.println(" message = " + wln.getMessage() + "\n");
private void testConnectionPool(String poolName) {
JDBCConnectionPoolMBean aPool = findConnPool(poolName);
JDBCConnectionPoolRuntimeMBean aRuntimeMBean = findRuntimeMBean(poolName);
/*while(aRuntimeMBean.getPoolState()) {
try {
Thread.sleep(6000);
System.out.println("Thread is sleeping.");
catch (InterruptedException ie) {
retargetConnPool(aPool);
private JDBCConnectionPoolRuntimeMBean findRuntimeMBean(String aPoolName) {
JDBCConnectionPoolRuntimeMBean aRuntimeMBean = null;
if (managedHome != null) {
try {
aRuntimeMBean = (JDBCConnectionPoolRuntimeMBean)managedHome.
getRuntimeMBean(aPoolName, "JDBCConnectionPoolRuntime");
catch (InstanceNotFoundException e) {
System.out.println("Unable to find the JDBCConnectionPoolRuntimeMBean: " + e);
aRuntimeMBean = null;
return aRuntimeMBean;
private JDBCConnectionPoolMBean findConnPool(String poolName) {
if (adminHome != null) {
try {
myPool = (JDBCConnectionPoolMBean)adminHome.getMBean(poolName, JDBCConnectionPoolMBean.class);
catch (InstanceNotFoundException e) {
System.out.println("Unable to find the JDBCConnectionPoolMBean: " + e);
myPool = null;
return myPool;
private void retargetConnPool(JDBCConnectionPoolMBean aPool) {
//System.out.println("The connection pool: " + aPool.toString() + " is not responding.\nAttempting to retarget the pool...");
try {
System.out.println("Attempting to remove " + myServer.toString() + " from the connection pool target list.");
aPool.removeTarget(myServer);
System.out.println("Removal successful: " + aPool.getTargets().toString());
aPool.addTarget(myServer);
System.out.println("Addition successful: " + aPool.getTargets().toString());
catch (InvalidAttributeValueException e) {
System.out.println(e.toString());
catch (DistributedManagementException e) {
System.out.println(e.toString());
public void doPost(HttpServletRequest req, HttpServletResponse resp)
throws ServletException, IOException {
String poolName = (String)req.getParameter("poolName");
String dataSource = (String)req.getParameter("dataSource");
//System.out.println("req.getAttribute(poolName) is: " + poolName);
//System.out.println("req.getAttribute(dataSource) is: " + dataSource);
String message = runTestQuery(dataSource);
getConnectionPoolMBean(poolName);
resp.setContentType("text/html");
PrintWriter out = resp.getWriter();
out.println("<html>");
out.println(" <head><title>The ConnectionsManager Responds:</title></head>");
out.println(" <body>");
out.println(" <h1>" + message + "</h1>");
out.println(" </body>");
out.println("</html>");
public void destroy() {
System.out.println("Destroying the ConnectionsManager servlet.");
public String getServletInfo() {
return "This servlet monitors and corrects errors in WebLogic connection pools.";
/**private void runTests() {
while (false) {
rset = testConnection();
if (rset == null) {
resetConnectionPool();
try {
wait();
catch (InterruptedException e) {}
private String runTestQuery(String dataSource) {
String statusMessage = "";
Connection conn = null;
Statement stmt = null;
ResultSet rset = null;
//String aPoolName = "GENNETConnectionPool";
String aSql = "select * from dual where 1 = 1";
try {
conn = DatabaseConnector.getDatabaseConnection(dataSource);
System.out.println("Established database connection.");
if (conn != null) {
conn.setAutoCommit(false);
stmt = conn.createStatement();
rset = stmt.executeQuery(aSql);
statusMessage = "The connection \'" + dataSource + "\' is OK.";
catch (Exception e) {
try {
conn.rollback();
catch (Exception e1) {}
e.printStackTrace();
statusMessage = "The connection \'" + dataSource + "\' has failed.\n" + e.toString();
finally {
try {
if (stmt != null) stmt.close();
if (conn != null) conn.close();
catch (Exception e) {
e.printStackTrace();
return statusMessage;
public void resetConnectionPool() {
private void findConnPoolRuntimeMBean(String poolName) {
try {
connectionPoolMBean = (JDBCConnectionPoolRuntimeMBean)managedHome.getRuntimeMBean(poolName, "JDBCConnectionPoolRuntime");
catch (InstanceNotFoundException e) {
System.out.println("Unable to find the JDBCConnectionPoolRuntimeMBean: " + e);
private void findMBeans() {
Environment env = new Environment();
try {
ctx = env.getInitialContext();
managedHome = (MBeanHome)ctx.lookup(MBeanHome.JNDI_NAME + "." + SERVER_NAME);
System.out.println(MBeanHome.JNDI_NAME + "." + SERVER_NAME + " -- managedHome found successfully.");
adminHome = (MBeanHome)ctx.lookup(MBeanHome.ADMIN_JNDI_NAME);
System.out.println(MBeanHome.ADMIN_JNDI_NAME + " -- adminHome found successfully.");
myServer = (ServerMBean)adminHome.getMBean(SERVER_NAME, ServerMBean.class );
System.out.println(MBeanHome.ADMIN_JNDI_NAME + " -- " + SERVER_NAME + " instance found successfully.");
ctx.close();
catch (NamingException e) {
System.out.println("Naming Exception: " + e);
managedHome = null;
adminHome = null;
catch (InstanceNotFoundException e) {
System.out.println("Unable to find the JDBCConnectionPoolMBean: " + e);
public String displayHomeName() {
getConnectionPoolMBean("GENNETConnectionPool");
if (managedHome != null) {
return new String("MBeanHome found successfully.");
else return new String("MBeanHome not found.\nSee WL Console for error.");
private void getConnectionPoolMBean(String poolName) {
String thisPoolName = poolName;
connectionPoolMBean = null;
if (managedHome != null) {
try {
connectionPoolMBean =
(JDBCConnectionPoolRuntimeMBean)managedHome.getRuntimeMBean(thisPoolName, "JDBCConnectionPoolRuntime");
if (connectionPoolMBean != null) {
System.out.println("JDBCConnectionPoolRuntime found successfully.");
System.out.println("connectionPoolMBean.toString() is: " + connectionPoolMBean.toString());
System.out.println("connectionPoolMBean.getFailuresToReconnectCount() is: " + connectionPoolMBean.getFailuresToReconnectCount());
System.out.println("connectionPoolMBean.getPoolState() is: " + connectionPoolMBean.getPoolState());
catch (InstanceNotFoundException e) {
System.out.println("Unable to find the JDBCConnectionPoolRuntimeMBean: " + e);
connectionPoolMBean = null;
// Obtain MBeanHome for the administration server.
/*JDBCConnectionPoolMBean mbean = (JDBCConnectionPoolMBean)home.
getConfigurationMBean(poolName, "JDBCConnectionPoolConfig");
mbean.setConnLeakProfilingEnabled(true);
mbean.setSqlStmtParamLoggingEnabled(true);
mbean.setSqlStmtMaxParamLength(maxLen);*/
/*try {
mypool = (JDBCConnectionPoolMBean)mbh.getMBean( "mypool",
JDBCConnectionPoolMBean.class );
catch( javax.management.InstanceNotFoundException e ) {
mypool = (JDBCConnectionPoolMBean) mbh.createAdminMBean( "mypool",
"JDBCConnectionPool", "mydomain" );
mypool.addTarget( myserver );
mypool.setDriverName( "org.gjt.mm.mysql.Driver" );*/
if (adminHome != null) {
try {
myPool = (JDBCConnectionPoolMBean)adminHome.getMBean(poolName, JDBCConnectionPoolMBean.class);
catch (InstanceNotFoundException e) {
System.out.println("Unable to find the JDBCConnectionPoolMBean: " + e);
if (myPool != null) {
//System.out.println("myPool.getMaxCapacity() is: " + myPool.getMaxCapacity());
try {
myPool.setMaxCapacity(10);
System.out.println("Before: myPool.getMaxCapacity() is: " + myPool.getMaxCapacity());
myPool.setMaxCapacity(100);
System.out.println("After: myPool.getMaxCapacity() is: " + myPool.getMaxCapacity());
catch (InvalidAttributeValueException e) {
System.out.println("Max Capacity is an invalid value.");
//System.out.println("myPool.getMaxCapacity() is: " + myPool.getMaxCapacity());
}Hy, i've got the same problem as you. Did you find out a solution.
If so, please contact me. Thanks a lot.
Lorenzo -
WLST : Error connecting to a remote Weblogic server instance from OEPE 3.7
Attempting a to run a weblogic script connecting to a remote weblogic server instance (10.3.5), which is generating the following exception in OEPE 3.7.2 -
username = 'weblogic'
password = 'weblogic6'
url='t3://xxx.xxx.com:7001'
connect(username,password,url)
Connecting to t3://xxx.xxx.com:7001 with userid weblogic ...
This Exception occurred at Fri Feb 01 13:20:54 MST 2013.
Error occured while performing connect : Error connecting to the server : Failed to generate class for weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl_1035_WLStub
Use dumpStack() to view the full stacktrace :
java.lang.AssertionError: Failed to generate class for weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl_1035_WLStubconnect
Problem invoking WLST - Traceback (innermost last):
File "C:\Users\hughese\workspace\12c_wlst\wlst\heapsize.py", line 13, in ?
File "<iostream>", line 22, in connect
File "<iostream>", line 648, in raiseWLSTException
WLSTException: Error occured while performing connect : Error connecting to the server : Failed to generate class for weblogic.management.mbeanservers.compatibility.internal.MBeanHomeImpl_1035_WLStub
Use dumpStack() to view the full stacktrace
Connecting to the local weblogic server instance (t3://localhost:7001) works okay.
From the command prompt (wlst.cmd) I'm able to connect to the remote weblogic server instance -
wls:/offline> connect('weblogic','xxxxx','t3:xxx.xxx.com:7001') ;
Connecting to t3://xxx.xxx.com:7001 with userid weblogic ...
Successfully connected to Admin Server 'AdminServer' that belongs to domain 'IDMDomain'.
I've compared the CLASSPATHs between OEPE and the command prompt.
Any assistance would be greatly appreciated.
Edited by: 950635 on Feb 1, 2013 7:47 PMHi,
1)To get mysql JDBC driver to work on my Linux system, i had to add the classpath for the driver to the .bashrc:
CLASSPATH=./:home/<user>/java/mm.mysql-2.0.6/:home/<user>/java
Note that I execute the java program as the user <user> (and .bashrc is the config. file of this <user>...). Perhaps you must do this as well for the Oracle driver on your client machine. I don't know if your client machine is UNIX/LINUX or WINDOWS. It should only be clear that the CLASSPATH is set in the config. file of the user under which the java program runs and that this user has the permission to access the files.
There are no differences between accessing the database locally than accessing it by a network connection. The only thing that matters are that the connection parameters are right and that the network works properly.
2) are you sure that the table tname (case sensitivity?) exits?
Marc -
Java.io.IOException when to use WLST to connect admin server
Hello experts,
I am following this article to use wlst to connect to admin server from remote, but failed with below error.
Oracle WebLogic Server 12c: Configuring and Using Node Manager
>java weblogic.WLST
wls:/offline> connect('superadmin', 'agile9', 't3://myadminserver.company.com:7001')
Connecting to t3://myadminserver.company.com:7001 with userid superadmin ...
The CompatabilityMBeanServer is not initialized properly.
This might happen if the CompatabilityMBeanServer is
disabled via the JMXMBean.
To view the root cause exception use dumpStack()
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 648, in raiseWLSTException
WLSTException: Error occured while performing connect : "Cannot connect to WLST."
Use dumpStack() to view the full stacktrace
wls:/offline> dumpStack()
This Exception occurred at Tue Jul 22 20:45:53 PDT 2014.
java.io.IOException
java.io.IOException
wls:/offline>
I checked CompatabilityMBeanServer is already enabled in Admin Console
Does anybody has any idea how to resolve?
My Environment:
weblogic 12.1.1.0
OS: REL 6.0
Java: 1.7.0_21
Thanks
JieHi,
Thanks for the reply. There was some problem with the input parameters to the automated activity. That error is resolved now.
I try to view the output of the automated activity, i.e, response of the web service call. I do an output mapping from the automated activity to a data object. But once I start the process and the automated activity executes, I could not see the output data in the context data in 'Operation Management --> Manage Processes'. The data object doesn't have any value.
The default trace doesn't have any error. I doubt if the web service is called at all!
Any suggestions?
Thank you. -
I'm currently writing a script that starts managed servers through WLST and I want it to avoid having the user enter their username and password similar to how startManagedWebLogic.sh does when a boot.properties file exists in the security directory of the server.
Currently, the way my script is set up is that it starts up WLST and enters the connect command, where it requests the username and password. The admin server URL is pulled from a config file used for the script.
Does anyone know how to supply the boot.properties file into WLST to have it automatically use the values in there? I do not want to have to save the values in plain text, nor do I want to have to create a new file to store them if it isn't necessary. I've read this thread weblogic.system.BootIdentityFile not working with WLST and tried copying boot.properties to domain home but didn't have any luck and still had to enter username and password. I have also tried looking into how startManagedWebLogic.sh pulls the values from the boot.properties but was unable to clearly identify how this is done. Any help would be much appreciated.
Thanks,
BrianExamples are presented here: Middleware Snippets: Starting and Stopping a Java EE Environment when using WebLogic
The examples use the Node Manager and Admin Server to start the managed server. To start the AdminServer nmStart is used. Note that boot.properties (in ${DOMAIN_HOME}/servers/${ADMIN_SERVER_NAME}/security) must exist in order to start a server with nmStart.
Next you can use, for example, the ServerLifeCycleRuntimeMBean to start the managed server (in this case the Node Manager and the Admin Server will make sure a boot.properties and startup.properties are propagated to the right directory ${DOMAIN_HOME}/servers/${SERVER_NAME}/data/nodemanager.
When the Admin Server is not available you can also use nmStart for the managed server. In this case you have to create boot.properties and startup.properties yourself by using nmGenBootStartupProps and copy them to the ${DOMAIN_HOME}/servers/${SERVER_NAME}/data/nodemanager directory. -
PROBLEM DESCRIPTION :
When I try to read a clob from Oracle, I receive "ORA-03120: two-task
conversion routine: integer overflow" Error.
This error occurs only for CLOB Type and only if I try to connect to
Oracle using WebLogic JDriver/Oracle POOL.
IMPORTANT NOTE: I can read CLOB or any other data using direct JDBC
connection to ORacle with out any problem.
Below Please find the JAVA CODE for Both Working and NON Working .
Created a Connection Pool as:
Name: MyJDBCConnectionPool
URL : jdbc:weblogic:oracle
DIRVER:weblogic.jdbc.oci.Driver
NON WORKING JAVA CODE (USES WEBLOGIC JDBC CONNECTION POOL TO ORACLE):
Driver myDriver =
(Driver)Class.forName("weblogic.jdbc.pool.Driver").newInstance();
Connection mconn =
myDriver.connect("jdbc:weblogic:pool:MyJDBCConnectionPool",null);
mconn.setAutoCommit (false);
CallableStatement cs = mconn.prepareCall("{call
P_XMLTEST2(?)}"); //This returns a CLOB
cs.registerOutParameter(1,java.sql.Types.CLOB);
cs.execute();
Clob clob = null;
clob = cs.getClob(1);
String data =new String();
data = clob.getSubString(1, (int)clob.length());
System.out.println(data); //print the data
data = null;
clob=null;
cs.close();
WORKING JAVA CODE (USES DIRECT THIN JDBC CONNECTION TO ORACLE):
Driver myDriver =
(Driver)Class.forName("oracle.jdbc.driver.OracleDriver").newInstance();
Connection mconn =
myDriver.connect("jdbc:oracle:thin:@server:1521:DB",null);
mconn.setAutoCommit (false);
CallableStatement cs = mconn.prepareCall("{call
P_XMLTEST2(?)}"); //This returns a CLOB
cs.registerOutParameter(1,java.sql.Types.CLOB);
cs.execute();
Clob clob = null;
clob = cs.getClob(1);
String data =new String();
data = clob.getSubString(1, (int)clob.length());
System.out.println(data); //print the data
data = null;
clob=null;
cs.close();
ERROR MESSAGE:
ORA-03120: two-task conversion routine: integer overflow
I appreciate your help on this problem.PROBLEM DESCRIPTION :
When I try to read a clob from Oracle, I receive "ORA-03120: two-task
conversion routine: integer overflow" Error.
This error occurs only for CLOB Type and only if I try to connect to
Oracle using WebLogic JDriver/Oracle POOL.
IMPORTANT NOTE: I can read CLOB or any other data using direct JDBC
connection to ORacle with out any problem.
Below Please find the JAVA CODE for Both Working and NON Working .
Created a Connection Pool as:
Name: MyJDBCConnectionPool
URL : jdbc:weblogic:oracle
DIRVER:weblogic.jdbc.oci.Driver
NON WORKING JAVA CODE (USES WEBLOGIC JDBC CONNECTION POOL TO ORACLE):
Driver myDriver =
(Driver)Class.forName("weblogic.jdbc.pool.Driver").newInstance();
Connection mconn =
myDriver.connect("jdbc:weblogic:pool:MyJDBCConnectionPool",null);
mconn.setAutoCommit (false);
CallableStatement cs = mconn.prepareCall("{call
P_XMLTEST2(?)}"); //This returns a CLOB
cs.registerOutParameter(1,java.sql.Types.CLOB);
cs.execute();
Clob clob = null;
clob = cs.getClob(1);
String data =new String();
data = clob.getSubString(1, (int)clob.length());
System.out.println(data); //print the data
data = null;
clob=null;
cs.close();
WORKING JAVA CODE (USES DIRECT THIN JDBC CONNECTION TO ORACLE):
Driver myDriver =
(Driver)Class.forName("oracle.jdbc.driver.OracleDriver").newInstance();
Connection mconn =
myDriver.connect("jdbc:oracle:thin:@server:1521:DB",null);
mconn.setAutoCommit (false);
CallableStatement cs = mconn.prepareCall("{call
P_XMLTEST2(?)}"); //This returns a CLOB
cs.registerOutParameter(1,java.sql.Types.CLOB);
cs.execute();
Clob clob = null;
clob = cs.getClob(1);
String data =new String();
data = clob.getSubString(1, (int)clob.length());
System.out.println(data); //print the data
data = null;
clob=null;
cs.close();
ERROR MESSAGE:
ORA-03120: two-task conversion routine: integer overflow
I appreciate your help on this problem. -
Error Connecting to Database using Weblogic Datasource
Hi,
I am trying to connect to oracle database from my program using weblogic DataSource. I am using JDK1.3.1.08 , weblogic 7.
I am using the following code to get Connection object.
contextFactory ="weblogic.jndi.WLInitialContextFactory";
providerURL="t3://192.168.0.29:7001";
dataSource ="temp_ds";
if(contextFactory!=null)
properties.put(Context.INITIAL_CONTEXT_FACTORY,contextFactory);
if(providerURL !=null)
properties.put(Context.PROVIDER_URL, providerURL);
initCtx = new InitialContext(properties);
DataSource ds= (javax.sql.DataSource) initCtx.lookup(dataSource);
Connection con = ds.getConnection();
con.setAutoCommit(false);
I am getting the following error while running the program. Can any body help?
javax.naming.CommunicationException. Root exception is weblogic.socket.Unrecove
rableConnectException: [JDK 1.3 or higher required]
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Compiled Code)
at java.io.IOException.<init>(IOException.java:47)
at java.net.SocketException.<init>(SocketException.java:36)
at java.net.ConnectException.<init>(ConnectException.java:34)
at weblogic.socket.UnrecoverableConnectException.<init>(UnrecoverableCon
nectException.java:19)
at weblogic.rjvm.RJVMManager.checkVersion(RJVMManager.java:451)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java
:201)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:191)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:203)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:169)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:262)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(Compi
led Code)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
tialContextFactoryDelegate.java:221)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialCont
extFactory.java:149)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:671)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:242)
at javax.naming.InitialContext.init(InitialContext.java:218)
at javax.naming.InitialContext.<init>(InitialContext.java:194)
at WeblogicTest.getConnection(WeblogicTest.java:40)
at WeblogicTest.<init>(WeblogicTest.java:23)
at WeblogicTest.main(WeblogicTest.java:18)
at WeblogicTest.printTableData(Compiled Code)
at WeblogicTest.<init>(WeblogicTest.java:24)
at WeblogicTest.main(WeblogicTest.java:18)
Regards
KumarI am not sure if this is the reason, but going thru the stack trace ...
javax.naming.CommunicationException. Root exception is weblogic.socket.Unrecove
rableConnectException: [JDK 1.3 or higher required]Make sure you have JDK 1.3 or higher installed.
Cheers
Sekar -
How to connect Oracle 7.x database using weblogic 11g
Hi,
For one of my requirement, I need to connect to a Oracle 7.x database using weblogic 11g Application server.
Any idea?Tried as per the suggestion from the link :
http://jvzoggel.wordpress.com/2011/07/26/weblogic-ojdbc-driver/
It worked. -
Problem modifying the connection details in a Report when using Weblogic 12
Hi
I have a j2ee application that uses the Java Reporting Component (JRC). At runtime, the code programmatically changes the connection type and schema name of a crystal report before running it. The connection that was used when designing the report is replaced with new JNDI parameters pointing to a Weblogic/Oracle datasource.
The application works perfectly when using Weblogic 11, but the same code and report fails when deployed to Weblogic 12.
I used Version 12.2.207.916 of the JRC, and updating to the most current version I could find (12.2.217) did not solve the problem.
The code snippet below shows how the connection and schema name is replaced for each of the tables in the report (not all the code is shown here)...
PropertyBag propertyBag = new PropertyBag();
propertyBag.put("Database DLL", "crdb_jdbc.dll");
propertyBag.put("JNDI Datasource Name", jndiName);
propertyBag.put("Initial Context", "");
while (tableList.hasNext()) {
ITable table = tableList.next();
ITable tableNew = (ITable) table.clone(true);
IConnectionInfo connectionInfo = table.getConnectionInfo();
connectionInfo.setAttributes(propertyBag);
connectionInfo.setKind(ConnectionInfoKind.SQL);
tableNew.setQualifiedName(newQualifier + "." + table.getName());
tableNew.setConnectionInfo(connectionInfo);
dbController.setTableLocation(table, tableNew);
The setTableLocation() function throws the following exception ...
2014-05-13 16:46:27,173 ERROR [[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] JRCCommunicationAdapter detected an exception: Unexpected database connector error
at com.crystaldecisions.reports.queryengine.Table.u7(SourceFile:2409)
at com.crystaldecisions.reports.dataengine.datafoundation.AddDatabaseTableCommand.new(SourceFile:529)
at com.crystaldecisions.reports.common.CommandManager.a(SourceFile:71)
at com.crystaldecisions.reports.common.Document.a(SourceFile:203)
at com.businessobjects.reports.sdk.requesthandler.f.a(SourceFile:175)
at com.businessobjects.reports.sdk.requesthandler.DatabaseRequestHandler.byte(SourceFile:1079)
at com.businessobjects.reports.sdk.JRCCommunicationAdapter.do(SourceFile:1167)
at com.businessobjects.reports.sdk.JRCCommunicationAdapter.if(SourceFile:661)
at com.businessobjects.reports.sdk.JRCCommunicationAdapter.a(SourceFile:167)
at com.businessobjects.reports.sdk.JRCCommunicationAdapter$2.a(SourceFile:529)
at com.businessobjects.reports.sdk.JRCCommunicationAdapter$2.call(SourceFile:527)
at com.crystaldecisions.reports.common.ThreadGuard.syncExecute(SourceFile:102)
at com.businessobjects.reports.sdk.JRCCommunicationAdapter.for(SourceFile:525)
at com.businessobjects.reports.sdk.JRCCommunicationAdapter.int(SourceFile:424)
at com.businessobjects.reports.sdk.JRCCommunicationAdapter.request(SourceFile:352)
at com.businessobjects.sdk.erom.jrc.a.a(SourceFile:54)
at com.businessobjects.sdk.erom.jrc.a.execute(SourceFile:67)
at com.crystaldecisions.proxy.remoteagent.RemoteAgent$a.execute(SourceFile:716)
at com.crystaldecisions.proxy.remoteagent.CommunicationChannel.a(SourceFile:125)
at com.crystaldecisions.proxy.remoteagent.RemoteAgent.a(SourceFile:537)
at com.crystaldecisions.sdk.occa.report.application.ds.a(SourceFile:186)
at com.crystaldecisions.sdk.occa.report.application.an.a(SourceFile:108)
at com.crystaldecisions.sdk.occa.report.application.b0.if(SourceFile:148)
at com.crystaldecisions.sdk.occa.report.application.b0.b(SourceFile:95)
at com.crystaldecisions.sdk.occa.report.application.bb.int(SourceFile:96)
at com.crystaldecisions.proxy.remoteagent.UndoUnitBase.performDo(SourceFile:151)
at com.crystaldecisions.proxy.remoteagent.UndoUnitBase.a(SourceFile:106)
at com.crystaldecisions.sdk.occa.report.application.DatabaseController.a(SourceFile:2159)
at com.crystaldecisions.sdk.occa.report.application.DatabaseController.a(SourceFile:543)
at com.crystaldecisions.sdk.occa.report.application.DatabaseController.a(SourceFile:3898)
at com.crystaldecisions.sdk.occa.report.application.DatabaseController.setTableLocation(SourceFile:2906)
at com.systest.reporting.engine.crystal.CrystalReportEngine.replaceConnection(CrystalReportEngine.java:523)
at com.systest.reporting.engine.crystal.CrystalReportEngine.changeDataSource(CrystalReportEngine.java:449)
at com.systest.CrystalReportPane.setReportDataSourceDetails(CrystalReportPane.java:170)
at com.systest.CrystalReportPane.commandLoad(CrystalReportPane.java:136)
at com.systest.ReportRunner.CrystalReport.Load(CrystalReport.java:401)
at com.systest.ReportRunner.SaveReportToFile(ReportRunner.java:1385)
Any idea what I can do to fix this ?
Thanks in advance!Last reference in any documentation re. version of supported weblogic is 10.3.x. And it may very well be that things worked in weblogic 11, but as versions go by the differences get bigger and eventually the app stops working.
I'll ping the Program Manager for definitive info and future support. Once I have the info, I'll update this Discussion.
- Ludek
Senior Support Engineer AGS Product Support, Global Support Center Canada
Follow us on Twitter -
Connect SQL2000 using weblogic 6.1
Hi,
I am a new to java.
Does anyone can tell me how to connect sql2000 using weblogic 6.1 ?
WilsonThanks !!
"Slava Imeshev" <[email protected]> wrote in message
news:[email protected]..
Hi Wilson,
You need to take path containing spaces into quotes i.e
"C:\Program Files\Microsoft SQL Server 2000 Driver for
JDBC\lib\msbase.jar";
Slava
"Wilson" <[email protected]> wrote in message
news:[email protected]..
I want to setup a connection pool using ms JDBC driver and what i done
are
I have set the class path in startWebLogic.cmd
set CLASSPATH=C:\Program Files\Microsoft SQL Server 2000 Driver for
JDBC\lib\msbase.jar;
C:\Program Files\Microsoft SQL Server 2000 Driver for
JDBC\lib\mssqlserver.jar;
C:\Program Files\Microsoft SQL Server 2000 Driver for
JDBC\lib\msutil.jar;
.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
and
<JDBCConnectionPool
Name="MyJDBC Connection Pool"
Targets="jdbctest"
URL="jdbc:microsoft:sqlserver://sqlsvr01:1433"
DriverName="com.microsoft.jdbc.sqlserver.SQLServerDriver"
InitialCapacity="1"
MaxCapacity="1"
CapacityIncrement="1"
Password=""
Properties="user=sa;server=qa75"
/>
but I get these error :
<2002/12/10 ??10?17?31?> <Error> <JDBC> <Cannot startup connection pool"My
JDBC Connection Pool" Cannot load driver class:
com.microsoft.jdbc.sqlserver.SQL
ServerDriver>
Thanks in advance.
Wilson
"Joseph Weinstein" <[email protected]> wrote in message
news:[email protected]..
Wilson wrote:
Hi,
I am a new to java.
Does anyone can tell me how to connect sql2000 using weblogic 6.1 ?
WilsonFrom what sort of code you you want to connect? Do read our onlinedocumentation
on connection pools. You can tell our pool system what JDBC driver youwant to use,
and the arguments it needs, and then we'll make a pool of connections
for
you. You should
start out with the simple JDBC driver examples.
Joe -
ClassCastException while asting ResultSet to OracleResultSet. Using weblogic connection pool
Hi,
I am using weblogic server 5.1 and connection pools for accessing Oracle database.
We wanted to use BLOB in oracle and I coded the java class to insert data into BLOB
field.
When I code a sample calss without using weblogic pool, I do not have any problem.
But when I use the weblogic connection pool, I get classcastException as described
below:
I am using
"insert into shipmentCorrection (" + insfields + ") VALUES (?,?,?,?,?,?,?,?,?,?,?,?,?,empty_blob())"
to insert a dummy record with empty_blob and then getting the BLOB locater by the
following code:
java.sql.ResultSet rset = stmt.executeQuery ("SELECT zipped_pdf FROM shipmentCorrection
WHERE shipment_id ='"+ ShipmentId + "' and correction_num ="+ CorrectionNum +" and
Bl_Type = '"+ blType +"'" );
rset.next();
BLOB blob = ((OracleResultSet)rset).getBLOB(1);
java.io.OutputStream outstream = blob.getBinaryOutputStream();
IN the above line of code where I cast the ResultSet to OracleResultSet, I get the
classcastException as follows:
I donno how to solve this problem. Could any one please help me on this ?
java.lang.ClassCastException: weblogic.jdbc.pool.ResultSet
at fmweb.SQL.PdfDataSQL.insertPdfData(PdfDataSQL.java:347)
at fmweb.framework.ShipmentManagerImpl.insertPdfData(ShipmentManagerImpl
.java:2471)
at fmweb.framework.ShipmentManager_WLSkel.invoke(ShipmentManager_WLSkel.
java:1316)
at weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerOb
jectAdapter.java:347)
at weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicReques
tHandler.java:69)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
.java:15)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
Thanks,
Muralidaran ChakravarthyWhen using weblogic pool drivers it is not possible to cast to an Oracle
JDBC driver, (or any other driver )
pool driver hides the driver you have configured.
"Muralidaran Chakravarthy" <[email protected]> wrote in message
news:3ce16855$[email protected]..
>
Hi,
I am using weblogic server 5.1 and connection pools for accessing Oracledatabase.
We wanted to use BLOB in oracle and I coded the java class to insert datainto BLOB
field.
When I code a sample calss without using weblogic pool, I do not have anyproblem.
But when I use the weblogic connection pool, I get classcastException asdescribed
below:
I am using
"insert into shipmentCorrection (" + insfields + ") VALUES(?,?,?,?,?,?,?,?,?,?,?,?,?,empty_blob())"
>
to insert a dummy record with empty_blob and then getting the BLOB locaterby the
following code:
java.sql.ResultSet rset = stmt.executeQuery ("SELECT zipped_pdf FROMshipmentCorrection
WHERE shipment_id ='"+ ShipmentId + "' and correction_num ="+CorrectionNum +" and
Bl_Type = '"+ blType +"'" );
rset.next();
BLOB blob = ((OracleResultSet)rset).getBLOB(1);
java.io.OutputStream outstream = blob.getBinaryOutputStream();
IN the above line of code where I cast the ResultSet to OracleResultSet, Iget the
classcastException as follows:
I donno how to solve this problem. Could any one please help me on this ?
java.lang.ClassCastException: weblogic.jdbc.pool.ResultSet
at fmweb.SQL.PdfDataSQL.insertPdfData(PdfDataSQL.java:347)
atfmweb.framework.ShipmentManagerImpl.insertPdfData(ShipmentManagerImpl
java:2471)
atfmweb.framework.ShipmentManager_WLSkel.invoke(ShipmentManager_WLSkel.
java:1316)
atweblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerOb
jectAdapter.java:347)
atweblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicReques
tHandler.java:69)
atweblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
java:15)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:135)
Thanks,
Muralidaran Chakravarthy
Maybe you are looking for
-
I have been using thunderbird for some years - in last month when I have been trying to send some emails I have a problem with some of them in that part of the email address has changed when I insert it ino the address bar and has inverted commas aro
-
Front Row Issue When iTunes is Running
On my Mac Mini (which is our media centre), I've noticed some strange behaviour. Namely, if I leave iTunes running and then start Front Row, after a while (up to 24 hours sometimes), Front Row can no longer see the iTunes library. With iTunes shutdow
-
I can certainly appreciate all the recommendations here for which graphics cards to use with my G5 and a 30" monitor, but as I sit here staring at pixels the size of my thumb, the one thing constantly ignored is the fact none of these cards are actua
-
Query with an integer managed property
Hello everyone, A (I hope) simple question. How to do search with a managed property of type Integer (or non-text type in general)? Here is what I am doing and fail to make function so far. Create a column of type Number with a Document Library; name
-
Revision: 11479 Author: [email protected] Date: 2009-11-05 13:47:44 -0800 (Thu, 05 Nov 2009) Log Message: Tweak the Spark project settings so that builder shows MX+spark setting in the build path. QE notes: None Doc notes: None Bugs: None Revie