SQL Server JDBC problem of JClient deploy in java web start

I have a test of JClient, it use SQL Server JDBC ,and I download the Microsoft SQL Server 2000 Driver for JDBC from microsoft(msbase.jar, mssqlserver.jar, msutil.jar), add the driver in jdevelop libraries, I can right click the java file to run this application in application navigator , I want run it in java web start and deploy in oc4j, and setup application follow the document of
http://www.oracle.com/technology/products/jdev/collateral/papers/10g/adfjclientbcwebstart.pdf
,but application catch the exception of com.microsoft.jdbc.sqlserver.SQLServerDriver ClassNotFoundException, how to load SQL Server JDBC in embedded oc4j server or standalone oc4j server
Thaks for helping me!

How to load SQL Server JDBC to OC4J server

Similar Messages

Problem with CORBA application deployed using Java Web Start 1_6_0.

Java Web Start fans and experts:
We have been using Java Web Start to deploy the client side of a CORBA-based application since the inception of Java Web Start ... including Java Web Start 1.0 right up through the present.
With Java Web Start 1_6_0, we see evidence that Web Start is "tinkering with" the IOR that CORBA uses to communicate. In all previous versions of Java Web Start, independent of the JRE which the application uses, the stringified IOR have been the same size regardless of whether the application is deployed locally or via Java Web Start. With Java Web Start 1_6_0, the stringified IOR is much longer than the "real" IOR (again, regardless of the JRE used by the application itself). To me this smells like a bug in Java Web Start 1_6_0. Has anyone else observed this behavior?
Here are some specifics .... I've run the same client application with various JREs both with and without Java Web Start as the deployment mechanism. The application was compiled and runs against servers that are running JDK 1_5_0_09.
Here is the summary of my results from a Linux box running various JREs, various versions of Java Web Start, and also running as a non-JWS deployed application. I've listed the length of the stringified IOR in each case.
JRE 1.5.0 non-JWS client: stringified IOR length = 344
JRE 1.6.0 non-JWS client: stringified IOR length = 344 ... this, I think, excludes the JRE as the cause of these problems.
Java WS 1.5.0, JRE 1.5.0 JWS client: stringified IOR length = 344
Java WS 1.5.0, JRE 1.6.0 JWS client: stringified IOR length = 344
Java WS 1.6.0, JRE 1.6.0 JWS client: stringified IOR length = 1568
Java WS 1.6.0, JRE 1.5.0 JWS cleint: stringified IOR length = 1568
In all cases, the stringified IOR length is determined by the service receiving the message and is always running JRE 1_5_9_09 and is
always the same 344 characters in length UNLESS it was deployed
using Java Web Start 1_6_0, in which case it in nearly 5 times as big!
To me, it sure looks as if there is a problem with Java Web Start 1_6_0 to be adding so much to the stringified IOR. Note: it's hard to tell how different the underlying IOR is in the JWS 1_6_0 case because, unlike most other ORBs, the Sun ORB doesn't have a tool to extract the IOR into a human readable structure. However, I can think of no good reason why the identical application deployed using Java Web Start 1_6_0 should have a stringified IOR length that is different than that of the same application deployed in non-JWS form or should differ from the behavior seen in all previous releases of Java Web Start.
Any clues or suggestions? Has anyone else observed this behavior?
Thanks,
John

Hi.
I got a different problem. My Corba application works in JRE 1.6, but doesn't works in JRE 1.5.X. I got an unexpected error and my console shows:
getSubjectX500Principal NoSuchMethodError: java.lang NoSuchMethodError
#### Java Web Start Error:
#### null
Can you help me?

A RCP Application using javafx deployed by java web start,in jre8u25 run have problem.

a RCP Application using javafx deployed by java web start,in jre8u20 can use jre7run the applicat,but in jre8u25 use jre7run application have problem.
in jre8u20 use jre7 run the application can run success.
but in jre8u20 the control print:
java.lang.UnsupportedClassVersionError: com/sun/javafx/runtime/VersionInfo : Unsupported major.minor version 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(Unknown Source)
at java.security.SecureClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.access$100(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at com.sun.deploy.config.JfxRuntime.runtimeForPath(Unknown Source)
at com.sun.deploy.config.JREInfo.<init>(Unknown Source)
at com.sun.deploy.config.JREInfo.setInstalledJREList(Unknown Source)
at com.sun.deploy.config.ClientConfig.storeInstalledJREs(Unknown Source)
at com.sun.javaws.Main.launchApp(Unknown Source)
at com.sun.javaws.Main.continueInSecureThread(Unknown Source)
at com.sun.javaws.Main.access$000(Unknown Source)
at com.sun.javaws.Main$1.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
the reason (i think) is that the application will use javafx's com.sum.javafx.runtime.VersionInfo,i use e(fx)clipse load the javafx runtime.in jre8u20,the web start use jre7's class.in jre8u25,the web start use jre8's class.
so i use jre7 run the application get this result.
how could i solve this problem?

Hi,
I have created client stubs for a webservice using axis wsdl2java tool. When I try calling these stubbed methods from JUnit tests, they are working fine but when I try to execute the jar (it is a swing) I get the following exception:
Exception in thread "main" java.lang.NoClassDefFoundError: javax/xml/rpc/Service
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(Unknown Source)
at java.security.SecureClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.defineClass(Unknown Source)
at java.net.URLClassLoader.access$100(Unknown Source)
at java.net.URLClassLoader$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClass(Unknown Source)
at java.lang.ClassLoader.loadClassInternal(Unknown Source)
at com.Gudds.SeCURE.MainUI.<init>(MainUI.java:76)
at com.Gudds.SeCURE.Main.Start(Main.java:62)
at org.owasp.webscarab.WebScarab.main(WebScarab.java:34)
I have put the jaxrpc.jar in the classpath and I suppose this jar has the java.xml.rpc.service class but I donot understand why it fails while executing the jar but works fine from the eclipse IDe. Plase help me.
Regrdas,
Kundan

Call report from java with deployment of java web start

I need call report from java,the call function is:execURL ( String pURL )
pURL is a url link to call report from report services .
such as :http://10.20.1.43:8888/reports/rwservlet?destype=cache&desformat=PDF&report=test.rdf&user=scott/tiger@cims
public static void execURL ( String pURL )
String tempstr = new String();
int posIdx = 0;
if ( (System.getProperty("os.name").equals("Windows NT"))||
(System.getProperty("os.name").equals("Windows 2000")) )
posIdx = pURL.indexOf("&");
while ( posIdx > 0 )
tempstr = pURL.substring(0,posIdx)+"^"+pURL.substring(posIdx);
pURL = tempstr;
posIdx = pURL.indexOf("&",posIdx+2);
try
Runtime.getRuntime().exec("cmd /c start "+pURL);
catch (Exception e1) {System.out.println(e1.getMessage()); }
else
try
Runtime.getRuntime().exec("start "+pURL);
catch (Exception e2)
System.out.println(e2.getMessage());
It's run with no problem with deployment of simple jar.
But when i call report with deployment of java web start,it can not.
I think it's java secuity problem,so i add
Permission java.io.FilePermission "c://winnt//system32//cmd.exe", "execute";
in java.policy file in client(windows 20000).However ,it can not too.
Who can help me,Thanks in Advance!

David,
In your code, 'cmd' is invoked as Runtime.getRuntime().exec("cmd /c start "+pURL);
but in your policy file you specify
Permission java.io.FilePermission "c://winnt//system32//cmd.exe", "execute";
Before creating a new process, the security manager checks for FilePermission(cmd,"execute")
if cmd is an absolute path, otherwise it calls checkPermission with
FilePermission("<<ALL FILES>>","execute"). Try specifying
FilePermission("<<ALL FILES>>","execute") in your policy file.
But, I believe using exec, may not be the right solution as it may not work on
other platforms. Also you will have to expect the client m/c to relax security
permission.
Did you consider using java.net.HttpUrlConnection class instead to access the report
service URL?
HTH,
Sathish.

SQL Server JDBC Problem - Exception vs. Empty ResultSet

I just uploaded and installed the latest pre-release build (123667). Win2K
platform.
There is something very wrong with the MS SQL Server JDBC behavior now.
If you Select * from a table which exists but is empty, the code raises an
exception like:
weblogic.jdbc.mssqlserver4.TdsException: Statement.executeQuery - No result
sets
were produced by 'SELECT recordHandle, record, recordState FROM JMSStore'
This is a big change. Normally JDBC returns an empty ResultSet. Cloudscape
still works fine, I havent test any other drivers yet.
This is also affecting EJB deployment -- Many beans in the examples provided
with the product fail to deploy with an error because of this JDBC exception
change. (Yes I'm sure the required tables are in my SQL*Server database,
I've been running the beta for a month now).
Help!

Sorry. My fault i sent you the WLS51 stuff. heres the driver again. Let me
know if any prblem with this one.
sree
"Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote in message
news:[email protected]...
If I put your mssqlserver4v70.jar file first in the classpath in the
startWebLogic script, it doesn't boot:
C:\bea\wlserver6.1>"C:\bea\jdk131\bin\java" -hotspot -ms64m -mx64m -classpat
h .;
.\lib\mssqlserver4v70.jar;.\lib\weblogic_sp.jar;.\lib\weblogic.jar -Dweblogi
c.Do
main=ejbbook -Dweblogic.Name=myserver "-Dbea.home=C:\bea"
"-Djava.security.polic
y==C:\bea\wlserver6.1/lib/weblogic.policy" -Dweblogic.management.password=we
blog
ic weblogic.Server
Starting WebLogic Server ....
The WebLogic Server did not start up properly.
Exception raised: java.lang.NoSuchMethodError
java.lang.NoSuchMethodError
at
weblogic.management.internal.ConfigurationMBeanImpl.<clinit>(Configur
ationMBeanImpl.java:80)
at weblogic.management.Admin.initialize(Admin.java:214)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:354)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:197)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
>
Putting it at the end doesn't work, of course.. Still uses jDriver classes
in weblogic.jar.
Did you package too many things in this .jar file? It is a lot biggerthan
4v65.jar and I see some "common" and "boot" classes in it..
-Greg
"Sree Bodapati" <[email protected]> wrote in message
news:[email protected]...
Yep QA found this problem and the fix will go into the GA. I am
attaching
a
new driver for you , please let me know if you see any problem with this
driver.
regards
sree
"Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote in message
news:[email protected]...
Problem goes away if I take the old version of the jDriver for SQL
Server
from the original beta 61 install and place it in the classpath in
front
of
the new weblogic.jar before booting.. Empty tables return empty
results
sets again, EJBs deploy, etc.
Please tell me QA found this problem and it is not going to be in theGA
release..
-Greg
"Greg Nyberg" <greg.nyberg.at.objectpartners.com> wrote in message
news:[email protected]...
I just uploaded and installed the latest pre-release build (123667).Win2K
platform.
There is something very wrong with the MS SQL Server JDBC behavior
now.
If you Select * from a table which exists but is empty, the coderaises
an
exception like:
weblogic.jdbc.mssqlserver4.TdsException: Statement.executeQuery - Noresult
sets
were produced by 'SELECT recordHandle, record, recordState FROM
JMSStore'
This is a big change. Normally JDBC returns an empty ResultSet.Cloudscape
still works fine, I havent test any other drivers yet.
This is also affecting EJB deployment -- Many beans in the examplesprovided
with the product fail to deploy with an error because of this JDBCexception
change. (Yes I'm sure the required tables are in my SQL*Server
database,
I've been running the beta for a month now).
Help!
[mssqlserver4v70.jar]

Problem while distribute software via Java Web Start

Hi,
I use JWS to distribute my software to the clients. I use apache 2.2 as webserver.
My Problem:
When i put a update a jar on the webserver, the clients have to start JWS twice to get the new file.
First i thought it is a problem with the webserver. So i have restarted the apache after i�ve put the new jar. ... without success.
Are there any settings in JWS which take affect?
Any ideas?
Tom

The default behavior is to timeout if checking for an update takes too much time.
You can add the jnlp element:
<update check="always"/>
and updates will always happen on the forst launch (when client is using Java Web Start 1.6.0 or later, update element will be ignored by earlier versions)
see: http://java.sun.com/javase/6/docs/technotes/guides/javaws/developersguide/syntax.html#security
/Andy

SQL Server/JDBC Problems...

I know this topic has been posted before, and believe me I've read all of it and followed instructions at least 5 times over. But I just can't get rid of :
Got an exception!
[Microsoft][SQLServer 2000 Driver for JDBC]Error establishing socket.
On my SQL server side:
1) My Client Network Utility and Server Network Utility both have TCP enabled and default port set to 1433
2) I've set authentication to "SQL Server and Windows" instead of just "windows".
3) For now I'm using my 'sa' account as startup which is set to "SQL Server and Windows" authentication.
4) I've disabled and then enabled TCP a bunch of times, that doesn't seem to help.
5) My SQL Server log says:
2005-02-22 10:12:12.86 server SQL server listening on Shared Memory, Named Pipes.
It should say something about TCP according to the MS SQL help, but I've had no luck with that.
I've even tried NMAP on my computer to check for open TCP ports, and 1433 doesn't show up. My guess is the problem is with SQL Server 2000 (I'm using Java 1.5.0_01 for now). Is there some kind of trick (ritual? animal sacrifice?) needed to get SQL Server to start listening on TCP? God knows I''ve tried everything short of kicking the **** out of my purchased boxed set. Please...any help in the matter would be GREATLY appreciated. Thanks

I had the same problem on my windows XP laptop.
For windows XP you need SQL Server 2000 service pack 3.
Of course you may not be using windows XP but the service pack will not hurt.

JClient/BC4J using Java web start deploy error

I have created the JClient/BC4J Applications,when I run local.html within JDeveploper,there is an error,which message is
that Can't find the resource http://localhost:8988/sqlj/lib/runtime12.jar.How can I sovle it?
Env:Windows2000,Oracle8i,JDeveloper9.03
Thanks for your help!

Hello,
JDev 9.0.3 preview release includes support for signing the bc4j jar files and
your project jar files. When you run the JClient WebStart wizard, Ant build
scripts are generated. One of the Ant build target 'signs' the jar file.
You can download the JDev 9.0.3 preview release from
http://otn.oracle.com/software/products/jdev/content.html
HTH,
Sathish.

J2EE SDK & SQL Server JDBC Driver

I am trying to use SQL Server JDBC Driver with J2EE SDK.
Following with the instruction of Deployment tool's help, I configured both the SQL Server JDBC and JDBC-ODBC Bridge. My classpath has include SQL Server JDBC Driver's lib, and my java program can connect to SQL Server 2000 correctly. but deployment tool always told me "no suitable driver" with SQL Server JDBC Driver when I want to generate SQLs. With JDBC-ODBC bridge, it's OK.
Why? I just want to know that if there is anywhere else that I can configure the class lib. I think it's because J2EE can't find the classes of SQL Server JDBC, but I don't know how to do.

step 1:download the sql driver and unzip it
step 2:copy the .jar file to $j2ee_home%/lib/system
step 3:modif userconfig.bat file ,add the .jar files
to j2ee_classpath
step 4:modify you resource.properpties files,add
yourself
JNDI name.
because i am a chinese,have poor english,if can't
trouble,send e-mail to me,i can replay to u with the
config files.I do as your steps,but it still cannot work. for bookstore1(j2ee tutorial example), it give out such exception:
javax.servlet.UnavailableException: Couldn't get database.
at BookStoreServlet.init(BookStoreServlet.java:28)
what 's the problem?
please give me some advice.

More problems with Java Web Start

In my quest for running a simple JClient as a Java Web Start, I encountered another roadblock.
The JClient program runs fine when run on its own, but it fails when it runs from Java Web Start, and the stack trace says that the Application Module failed to get an instance because it couldn't find the following class (complete stack trace at bottom): javax/servlet/http/HttpSessionContext
(Now, isn't that a deprecated class?) I feel like I'm plagued with all kind of errors lately. Anyone knows what am I doing wrong?
Thanks,
GVdP
[Stack trace]
oracle.jbo.JboException: JBO-29000: Unexpected exception caught: oracle.jbo.common.ampool.ApplicationPoolException, msg=JBO-30003: The application pool (FI_Module9iASLocal) failed to checkout an application module due to the following exception:
     at oracle.jbo.client.Configuration.createRootApplicationModuleFromConfig(Configuration.java:1144)
     at oracle.jbo.uicli.mom.JUMetaObjectManager.createApplicationObject(JUMetaObjectManager.java:386)
     at JApp.Main_Form.main(Main_Form.java:377)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sun.javaws.Launcher.executeApplication(Unknown Source)
     at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
     at com.sun.javaws.Launcher.continueLaunch(Unknown Source)
     at com.sun.javaws.Launcher.handleApplicationDesc(Unknown Source)
     at com.sun.javaws.Launcher.handleLaunchFile(Unknown Source)
     at com.sun.javaws.Launcher.run(Unknown Source)
     at java.lang.Thread.run(Thread.java:536)
## Detail 0 ##
JBO-30003: The application pool (FI_Module9iASLocal) failed to checkout an application module due to the following exception:
oracle.jbo.JboException: JBO-25222: Unable to create application module.
     at oracle.jbo.common.ampool.DefaultConnectionStrategy.createApplicationModule(DefaultConnectionStrategy.java:151)
     at oracle.jbo.common.ampool.DefaultConnectionStrategy.createApplicationModule(DefaultConnectionStrategy.java:76)
     at oracle.jbo.common.ampool.ApplicationPoolImpl.instantiateResource(ApplicationPoolImpl.java:1767)
     at oracle.jbo.pool.ResourcePool.createResource(ResourcePool.java:315)
     at oracle.jbo.common.ampool.ApplicationPoolImpl.doCheckout(ApplicationPoolImpl.java:1394)
     at oracle.jbo.common.ampool.ApplicationPoolImpl.useApplicationModule(ApplicationPoolImpl.java:2062)
     at oracle.jbo.common.ampool.SessionCookieImpl.useApplicationModule(SessionCookieImpl.java:398)
     at oracle.jbo.common.ampool.SessionCookieImpl.useApplicationModule(SessionCookieImpl.java:369)
     at oracle.jbo.common.ampool.SessionCookieImpl.useApplicationModule(SessionCookieImpl.java:364)
     at oracle.jbo.client.Configuration.createRootApplicationModuleFromConfig(Configuration.java:1135)
     at oracle.jbo.uicli.mom.JUMetaObjectManager.createApplicationObject(JUMetaObjectManager.java:386)
     at JApp.Main_Form.main(Main_Form.java:377)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sun.javaws.Launcher.executeApplication(Unknown Source)
     at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
     at com.sun.javaws.Launcher.continueLaunch(Unknown Source)
     at com.sun.javaws.Launcher.handleApplicationDesc(Unknown Source)
     at com.sun.javaws.Launcher.handleLaunchFile(Unknown Source)
     at com.sun.javaws.Launcher.run(Unknown Source)
     at java.lang.Thread.run(Thread.java:536)
## Detail 0 ##
javax.naming.NamingException: Lookup error: java.lang.NoClassDefFoundError: javax/servlet/http/HttpSessionContext; nested exception is:
     java.lang.NoClassDefFoundError: javax/servlet/http/HttpSessionContext
     at com.evermind.server.rmi.RMIContext.lookup(RMIContext.java:134)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at oracle.jbo.client.remote.ejb.ias.AmHomeImpl.remoteLookup(AmHomeImpl.java:99)
     at oracle.jbo.client.remote.ejb.ias.AmHomeImpl.getRemoteApplicationModuleHome(AmHomeImpl.java:40)
     at oracle.jbo.client.remote.ejb.AbstractApplicationModuleHomeImpl.lookupUsingPlatformContext(AbstractApplicationModuleHomeImpl.java:141)
     at oracle.jbo.client.ejb.ApplicationModuleHomeImpl.<init>(ApplicationModuleHomeImpl.java:62)
     at oracle.jbo.client.remote.ejb.AbstractApplicationModuleHomeImpl.<init>(AbstractApplicationModuleHomeImpl.java:37)
     at oracle.jbo.client.remote.ejb.ias.AmHomeImpl.<init>(AmHomeImpl.java:33)
     at oracle.jbo.client.remote.ejb.ias.InitialContextImpl.createJboHome(InitialContextImpl.java:28)
     at oracle.jbo.common.JboInitialContext.lookup(JboInitialContext.java:81)
     at javax.naming.InitialContext.lookup(InitialContext.java:347)
     at oracle.jbo.common.ampool.DefaultConnectionStrategy.createApplicationModule(DefaultConnectionStrategy.java:132)
     at oracle.jbo.common.ampool.DefaultConnectionStrategy.createApplicationModule(DefaultConnectionStrategy.java:76)
     at oracle.jbo.common.ampool.ApplicationPoolImpl.instantiateResource(ApplicationPoolImpl.java:1767)
     at oracle.jbo.pool.ResourcePool.createResource(ResourcePool.java:315)
     at oracle.jbo.common.ampool.ApplicationPoolImpl.doCheckout(ApplicationPoolImpl.java:1394)
     at oracle.jbo.common.ampool.ApplicationPoolImpl.useApplicationModule(ApplicationPoolImpl.java:2062)
     at oracle.jbo.common.ampool.SessionCookieImpl.useApplicationModule(SessionCookieImpl.java:398)
     at oracle.jbo.common.ampool.SessionCookieImpl.useApplicationModule(SessionCookieImpl.java:369)
     at oracle.jbo.common.ampool.SessionCookieImpl.useApplicationModule(SessionCookieImpl.java:364)
     at oracle.jbo.client.Configuration.createRootApplicationModuleFromConfig(Configuration.java:1135)
     at oracle.jbo.uicli.mom.JUMetaObjectManager.createApplicationObject(JUMetaObjectManager.java:386)
     at JApp.Main_Form.main(Main_Form.java:377)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sun.javaws.Launcher.executeApplication(Unknown Source)
     at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
     at com.sun.javaws.Launcher.continueLaunch(Unknown Source)
     at com.sun.javaws.Launcher.handleApplicationDesc(Unknown Source)
     at com.sun.javaws.Launcher.handleLaunchFile(Unknown Source)
     at com.sun.javaws.Launcher.run(Unknown Source)
     at java.lang.Thread.run(Thread.java:536)

Please add servlet.jar to your classpath

Deploying no java applications using Java Web Start

Hi,
I am new to java web start. Is it possible to distribute non java applications using java web start. I have an APP which can run on a desktop in standalone mode. The app has jusy HTML and Java script files. Is it possible to package this app and deploying using java web start? I am assuming If it is possible, I can make updates to the packaged app in the web servers and the updates will be downloaded next time the app is used provided configurations are correct?
thx

The app has jusy HTML and Java script files. Is it possible
to package this app and deploying using java web start? Not really. Resources for JWS need to be zipped,
while this HTML/JS app. will (I guess) not work from
inside the depths of a Jar (or Zip) archive.
Note that you can organise for those files to be
downloaded and expanded onto a known place
on the user's disk, by using an 'installer' element,
but..
...I am assuming If it is possible, I can make updates to the
packaged app in the web servers and the updates ..installers are only called once, and do not 'update'.

Microsoft SQL Server JDBC driver and WLS JMS problem?

          Greetings,
          I'm using the Microsoft SQL Server JDBC driver with WLS with JMS
          persisted to SQL Server, during WLS startup the JMS attempts to
          read the JMSStore and JMSState tables in the db, if they are
          already present (say, from a previous run) the driver kicks out:
          java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet can
          not re-read row data for column 1.
          If the tables are not present, then WLS creates them and
          everything proceeds fine. Now, its not a good thing to attempt
          to reread row data for a ResultSet, especially for portability. Why is WLS JMS
          doing this? is there some config I can use to adjust JMS startup behavior for
          persisted JMS stores?
          Jay Houghton
          Centiv
          [email protected]
          long exception trace follows:
          <Oct 1, 2002 8:29:11 AM EDT> <Info> <JMS> <User connection factory "BroadcastTopicFactory"
          is started.>
          <Oct 1, 2002 8:29:18 AM EDT> <Info> <JMS> <JMSServer "EnergizerJMSServer", Opening
          JDBC store tables "JMSStore
          " and "JMSState" using connection pool "JMSConnectionPool".>
          <Oct 1, 2002 8:29:20 AM EDT> <Alert> <JMS> <JMSServer "EnergizerJMSServer", store
          failed to open, java.io.IOEx
          ception: JMS JDBC store, connection pool = <JMSConnectionPool>, prefix = <null>:
          recover
          java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet can
          not re-read row data for colum
          n 1.
          at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
          at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
          at weblogic.jdbc.pool.ResultSet.getLong(ResultSet.java:304)
          at weblogic.jms.store.JDBCIOStream.doRecover(JDBCIOStream.java:618)
          at weblogic.jms.store.JDBCIOStream.recover(JDBCIOStream.java:728)
          at weblogic.jms.store.JMSStore.recover(JMSStore.java:112)
          at weblogic.jms.backend.BEStore.open(BEStore.java:179)
          at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:330)
          at weblogic.jms.JMSService.createBackEnd(JMSService.java:923)
          at weblogic.jms.JMSService.addJMSServer(JMSService.java:1277)
          at weblogic.jms.JMSService.addDeployment(JMSService.java:1174)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
          at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
          at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:23
          3)
          at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
          at $Proxy40.updateDeployments(Unknown Source)
          at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub
          .java:2734)
          at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:362
          at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:154)
          at java.lang.reflect.Method.invoke(Native Method)
          at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
          at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
          at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
          at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
          at $Proxy57.start(Unknown Source)
          at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean
          _CachingStub.java:480)
          at weblogic.management.Admin.startApplicationManager(Admin.java:1151)
          at weblogic.management.Admin.finish(Admin.java:571)
          at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:508)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
          at weblogic.Server.main(Server.java:35)


          Tom,
          thanks for the info, I'll bring this to support.
          I did try the weblogic jDriver for SQL Server and it works fine, so i think it
          must be the way JMS is interacting with the MS driver.
          here are my components:
          WLS 6.1sp1
          Microsoft® SQL Server™ 2000 Driver for JDBC™ is a (Type 4 JDBC) which provides
          partial JDBC 2 support (no blobs, clobs, etc)
          MS SQL Server 2000 (sp2?)
          thanks!
          Jay Houghton
          [email protected]
          Tom Barnes <[email protected]> wrote:
          >Hi Jay,
          >
          >This is not a known issue at BEA as far as I know, perhaps it is the
          >result
          >of a new driver/database combination. Try using a different driver,
          >or a different
          >version of the current driver. Meanwhile, use a file store (just as
          >reliable but faster) and log a case with customer support, including
          >information on your version, service-pack, and what driver you are using.
          >
          >Tom, BEA
          >
          >Jay Houghton wrote:
          >
          >> Greetings,
          >>
          >> I'm using the Microsoft SQL Server JDBC driver with WLS with JMS
          >> persisted to SQL Server, during WLS startup the JMS attempts to
          >> read the JMSStore and JMSState tables in the db, if they are
          >> already present (say, from a previous run) the driver kicks out:
          >>
          >> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet
          >can
          >> not re-read row data for column 1.
          >>
          >> If the tables are not present, then WLS creates them and
          >> everything proceeds fine. Now, its not a good thing to attempt
          >> to reread row data for a ResultSet, especially for portability. Why
          >is WLS JMS
          >> doing this? is there some config I can use to adjust JMS startup behavior
          >for
          >> persisted JMS stores?
          >>
          >> Jay Houghton
          >> Centiv
          >> [email protected]
          >>
          >> long exception trace follows:
          >>
          >> <Oct 1, 2002 8:29:11 AM EDT> <Info> <JMS> <User connection factory
          >"BroadcastTopicFactory"
          >> is started.>
          >> <Oct 1, 2002 8:29:18 AM EDT> <Info> <JMS> <JMSServer "EnergizerJMSServer",
          >Opening
          >> JDBC store tables "JMSStore
          >> " and "JMSState" using connection pool "JMSConnectionPool".>
          >> <Oct 1, 2002 8:29:20 AM EDT> <Alert> <JMS> <JMSServer "EnergizerJMSServer",
          >store
          >> failed to open, java.io.IOEx
          >> ception: JMS JDBC store, connection pool = <JMSConnectionPool>, prefix
          >= <null>:
          >> recover
          >> java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for JDBC]ResultSet
          >can
          >> not re-read row data for colum
          >> n 1.
          >> at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
          >> at com.microsoft.jdbc.base.BaseResultSet.getLong(Unknown Source)
          >> at weblogic.jdbc.pool.ResultSet.getLong(ResultSet.java:304)
          >> at weblogic.jms.store.JDBCIOStream.doRecover(JDBCIOStream.java:618)
          >> at weblogic.jms.store.JDBCIOStream.recover(JDBCIOStream.java:728)
          >> at weblogic.jms.store.JMSStore.recover(JMSStore.java:112)
          >> at weblogic.jms.backend.BEStore.open(BEStore.java:179)
          >> at weblogic.jms.backend.BackEnd.initialize(BackEnd.java:330)
          >> at weblogic.jms.JMSService.createBackEnd(JMSService.java:923)
          >> at weblogic.jms.JMSService.addJMSServer(JMSService.java:1277)
          >> at weblogic.jms.JMSService.addDeployment(JMSService.java:1174)
          >> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployment(DeploymentTarget.java:329)
          >> at weblogic.management.mbeans.custom.DeploymentTarget.addDeployments(DeploymentTarget.java:279)
          >> at weblogic.management.mbeans.custom.DeploymentTarget.updateServerDeployments(DeploymentTarget.java:23
          >> 3)
          >> at weblogic.management.mbeans.custom.DeploymentTarget.updateDeployments(DeploymentTarget.java:193)
          >> at java.lang.reflect.Method.invoke(Native Method)
          >> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
          >> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
          >> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
          >> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          >> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          >> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
          >> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
          >> at $Proxy40.updateDeployments(Unknown Source)
          >> at weblogic.management.configuration.ServerMBean_CachingStub.updateDeployments(ServerMBean_CachingStub
          >> java:2734)
          >> at weblogic.management.mbeans.custom.ApplicationManager.startConfigManager(ApplicationManager.java:362
          >> )
          >> at weblogic.management.mbeans.custom.ApplicationManager.start(ApplicationManager.java:154)
          >> at java.lang.reflect.Method.invoke(Native Method)
          >> at weblogic.management.internal.DynamicMBeanImpl.invokeLocally(DynamicMBeanImpl.java:608)
          >> at weblogic.management.internal.DynamicMBeanImpl.invoke(DynamicMBeanImpl.java:592)
          >> at weblogic.management.internal.ConfigurationMBeanImpl.invoke(ConfigurationMBeanImpl.java:352)
          >> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1555)
          >> at com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
          >> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:449)
          >> at weblogic.management.internal.MBeanProxy.invoke(MBeanProxy.java:190)
          >> at $Proxy57.start(Unknown Source)
          >> at weblogic.management.configuration.ApplicationManagerMBean_CachingStub.start(ApplicationManagerMBean
          >> _CachingStub.java:480)
          >> at weblogic.management.Admin.startApplicationManager(Admin.java:1151)
          >> at weblogic.management.Admin.finish(Admin.java:571)
          >> at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:508)
          >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
          >> at weblogic.Server.main(Server.java:35)
          >

MS SQL Server JDBC 2.0 datasource creation issue using Visual Admin

Hi,
I need to create an MS SQL Server JDBC 2.0 DataSource using the Visual Admin (running on NetWeaver 2004 SP19). I'm using the Microsoft SQL Server 2005 JDBC driver. Have no problem creating a Version 1.x (no XA support) DataSource.
The issue is that when I try to create a Version 2.0 (with XA support) datasource I get the following exception: java.sql.SQLException: Invalid DataSource reference
This is the setup I used:
JDBC Version "2.0 (with XA support)
JDBC 2.0 Compliant:
object factory: com.microsoft.sqlserver.jdbc.SQLServerDataSourceObjectFactory
datasource type: XADataSource
xads class name: com.microsoft.sqlserver.jdbc.SQLServerXADataSource
On the additional tab:
databaseName=fldev_jj
portNumber=1433
serverName=dbsrv61
user=fldev_jj
password=******
Even added the url, but that made no difference. Chose Vendor SQL,
and have initial connections set to 1. This url worked when used
with a version 1.x datasource.
What can I try to do to resolve this?
Full exception:
java.rmi.RemoteException: com.sap.engine.services.dbpool.exceptions.BaseRemoteException: Error during start of application "factorylogic.com/FactoryLogicBusinessDS". [id = StartupError]
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:608)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
     at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
     at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
     at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
     at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
     at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
     at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
     at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.rmi.RemoteException: Error occurred while starting application in whole cluster and wait.; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 4557350:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "FactoryLogicDS".
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1843)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
     at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
     at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
     at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
     at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
     at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
     at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
     at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.dbpool.exceptions.BaseInstantiationException: Cannot create instance XAManagedConnectionFactoryImpl.
     at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:131)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1760)
     ... 42 more
Caused by: java.sql.SQLException: Invalid DataSource reference.
     at com.microsoft.sqlserver.jdbc.SQLServerDataSourceObjectFactory.getObjectInstance(Unknown Source)
     at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:129)
     ... 43 more
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:663)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
     ... 31 more
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 4557350:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "FactoryLogicDS".
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1843)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:606)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:285)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.createDataSource(DataSourceManagerImpl.java:342)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
     at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
     at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
     at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
     at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
     at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
     at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
     at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.dbpool.exceptions.BaseInstantiationException: Cannot create instance XAManagedConnectionFactoryImpl.
     at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:131)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1760)
     ... 42 more
Caused by: java.sql.SQLException: Invalid DataSource reference.
     at com.microsoft.sqlserver.jdbc.SQLServerDataSourceObjectFactory.getObjectInstance(Unknown Source)
     at com.sap.engine.services.dbpool.spi.XAManagedConnectionFactoryImpl.<init>(XAManagedConnectionFactoryImpl.java:129)
     ... 43 more
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.sleepClientThread(ParallelAdapter.java:270)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:127)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4707)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
     ... 33 more
     at com.sap.engine.services.dbpool.exceptions.BaseRemoteException.writeReplace(BaseRemoteException.java:178)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at java.io.ObjectStreamClass.invokeWriteReplace(ObjectStreamClass.java:896)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1016)
     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1337)
     at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)
     at javax.management.MBeanException.writeObject(MBeanException.java:126)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1301)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1252)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1337)
     at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367)
     at com.sap.exception.BaseExceptionInfo.writeObject(BaseExceptionInfo.java:964)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:809)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1301)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1252)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
     at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1337)
     at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1309)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1252)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
     at com.sap.engine.services.jmx.ResponseMessage.writeBody(ResponseMessage.java:177)
     at com.sap.engine.services.jmx.Message.writeMsg(Message.java:257)
     at com.sap.engine.services.jmx.Message.getMsg(Message.java:453)
     at com.sap.engine.services.jmx.Message.writeExternal(Message.java:505)
     at java.io.ObjectOutputStream.writeExternalData(ObjectOutputStream.java:1272)
     at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1250)
     at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1057)
     at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:66)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Leaving the object factory empty is absolutely part of the solution.
I can now start the data source and it can get a connection.
The remaining problem is that the moment I try to do anything with xa (inside of netweaver, using the datasource) I get an xa error... Found a way around that by changing the datasource type from "XADataSource" to a "ConnectionPoolDatasource".
The problem with that is that I'm no longer sure it uses XA transactions...
Will do more testing...
Very helpful reply Yuri!
Thanks

MS SQL Server jdbc Driver installation on XI

Hi,
I am running XI 3 on sp11 patch 1.
We need to install the MS SQL Server jdbc driver on the XI box to connect to a SQL Server 2000 SP3 Database server.
We tried installing the driver from the MS downloads website:
http://www.microsoft.com/downloads/details.aspx?familyid=07287b11-0502-461a-b138-2aa54bfdc03a&displaylang=en
But this is giving us problems while installation as SDM does not like the format.
Can someone please tell us how do we install this driver?
Thanks
Ashish

Hi Ashish,
i assume that u already have the drivers (msbase.jar,mssqlserver.jar,msutil.jar). All u have to do is deploy them.
The procedure is:
1.Add all jars to the archive <b>aii_af_jmsproviderlib.sda</b>, modify the <b>provider.xml</b> file and WinZip the .sda file again.
     a)Copy the file: aii_af_jmsproviderlib.sda from    the path ..\usr\sap\SID\DVEBMGS00\SDM\root\origin\sap.com\com.sap.aii.af.jmsproviderlib\SAP AG\3.0.20040112154003.0000. to any other drive on the server.
     b)Unzip it. After Unzipping the archive there are 2 folders created under the provided directory
     \META-INF
     \server
     c)     Edit the file provider.xml
        Add the vendor specific jar file names to the provider.xml file in between the tags <jars> </jars> and Save it.
         For you it will be
         <jars>
         <jar-name>msbase.jar</jar-name>
         <jar-name>mssqlserver.jar</jar-name>
         <jar-name>msutil.jar</jar-name>
         </jars>
      d)Copy the specific driver files to the same dirctory where u have unzipped the .sda
      e)Now ZIP the following files/folders from the drive/dirctory.
       Vendor driver files
       META-INF folder
       Server folder
       The name of the zip file should be the same i.e   aii_af_jmsproviderlib.sda
2.Deploy the archive aii_af_jmsproviderlib.sda on to the J2ee Engine using SDM tool.
This will solve ur problem.
Regards
Sunita

Update of MySQL and SQL Server JDBC Driver does not work in 1.2.1

Hi,
always after the update process is started i got the MySQL and SQL Server JDBC driver
update notification.
But all the time after i install the update i got the notification again but no errormessage
that the update was maybe not successful ???
Frank

Ok
then my subject was false
i always try to update the extensions and now i can see that they are updated on the filesystem but the IDE does not recognize them as updated
....\sqldeveloper\sqldeveloper\extensions\oracle.sqldeveloper.thirdparty.drivers.mysql
is available and new after the update process
and under
...\sqldeveloper\sqldeveloper\tmp\update\oracle.sqldeveloper.thirdparty.drivers.mysql.5239.zip
the downloaded zip file is also available.
In the update window the message is that the extension with version 5206 is available
Maybe that is the problem cause the downloaded files are version 11.1.1.5239
if you look at the bundle.xml file inside the META-INF directory
Frank

SQL Server JDBC problem of JClient deploy in java web start

Similar Messages

Maybe you are looking for