WebLogic test RMI

Hi,
I'm trying to test a call RMI in WebLogic 10.3.6 but an error is generated...
String serviceAddress = "rmi://localhost:7001/BeanRemoteService";
Naming.lookup(serviceAddress);
java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
     java.io.EOFException
     at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:286)
     at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:184)
     at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:322)
     at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)
     at java.rmi.Naming.lookup(Naming.java:84)
Caused by: java.io.EOFException
     at java.io.DataInputStream.readByte(DataInputStream.java:250)
     at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:228)
     ... 7 more
javax.naming.ServiceUnavailableException: error during JRMP connection establishment; nested exception is:
     java.io.EOFException
I have a wlfullclient lib in the classpath...
Can anybody help me?

If Naming.lookup() works, then you muist be binding the server using Naming.bind(). To lookup under the JNDI tree, you must bind the using JNDI, too.
jay allen wrote:
This test case uses the example classes in weblogic/examples/rmi/hello:
The rmi.hello classes are deployed on WL and the following code can connect
from a remote node and get a reference to the remote object.
try {
Hello_WLStub obj = ( Hello_WLStub )
Naming.lookup("t3://192.32.239.58:7511/HelloServer");
catch (Throwable t){
t.printStackTrace();
The following code, using WLInitialContext however, throws a
javax.naming.NameNotFoundException
Hashtable env = new Hashtable(5);
env.put(Context.INITIAL_CONTEXT_FACTORY,"weblogic.jndi.WLInitialContextFacto
ry");
env.put(Context.PROVIDER_URL,"t3://192.32.239.58:7511");
Context ctx = new InitialContext(env);
Hello_WLStub obj = ( Hello_WLStub )ctx.lookup("HelloServer");
here's the exception
javax.naming.NameNotFoundException: 'HelloServer'; remaining name
'HelloServer'
at
weblogic.rmi.extensions.AbstractRequest.sendReceive(AbstractRequest.java:76)
at
weblogic.jndi.toolkit.BasicWLContext_WLStub.lookup(BasicWLContext_WLStub.jav
a:246)
at
weblogic.jndi.toolkit.WLContextStub.lookup(WLContextStub.java:545)
at javax.naming.InitialContext.lookup(InitialContext.java:349)
at client2.main(client2.java:61)
Note, there hasn't been any security set up for weblogic.rmi or
weblogic.jndi, or the HelloImpl class. That is, 'everyone' has access.
Thanks,
Jay

Similar Messages

  • Weblogic.jdbc20.rmi.SerialConnection fail to prepareCall()

    Hi, I have a stateless session bean calling an oracle8i stored procedure. The java.sql.Connection is obtained via weblogic DataSource (non-transactional). and this line is failing:CallableStatement cstmt = conn.prepareCall(qstr);Start of the stack is this:java.sql.SQLException: java.lang.NullPointerException: at weblogic.jdbc20.rmi.SerialConnection.prepareCall(SerialConnection.java:44)I tested printing conn.toString() and it gave me "weblogic.jdbc20.rmi.SerialConnection@43074758", but any other method on this Connection object will fail.Yet, same program runs just fine in servlet. Any idea why? How does weblogic.jdbc20.rmi.SerialConnection come to into play? What is it?Any help is appreciated!Alan

    Potluri wrote:
    >
    WLS 6.1 on Win 2000 and trying to connect Oracle database on remote Unix machine.Let me know if you're at the latest service pack level. This feels like a bug that
    has been fixed...
    Joe
    >
    Joseph Weinstein <[email protected]> wrote:
    Potluri wrote:
    Hi ,
    I am using CallableStatement to update the database. When i tried tocreate the
    callable statement it is throwing the following exception. can anysuggest some
    solution for this....
    java.sql.SQLException: java.lang.NullPointerException
    at weblogic.jdbc.rmi.SerialConnection.prepareCall(SerialConnection.java:
    106)
    PotluriWhat version of the server are you running?
    B.E.A. is now hiring! (12/14/01) If interested send a resume to [email protected]
    DIRECTOR OF PRODUCT PLANS AND STRATEGY San Francisco, CA
    E-SALES BUSINESS DEVELOPMENT REPRESENTATIVE Dallas, TX
    SOFTWARE ENGINEER (DBA) Liberty Corner, NJ
    SENIOR WEB DEVELOPER San Jose, CA
    SOFTWARE ENGINEER (ALL LEVELS), CARY, NORTH CAROLINA San Jose, CA
    SR. PRODUCT MANAGER Bellevue, WA
    SR. WEB DESIGNER San Jose, CA
    Channel Marketing Manager - EMEA Region London, GBR
    DIRECTOR OF MARKETING STRATEGY, APPLICATION SERVERS San Jose, CA
    SENIOR SOFTWARE ENGINEER (PLATFORM) San Jose, CA
    E-COMMERCE INTEGRATION ARCHITECT San Jose, CA
    QUALITY ASSURANCE ENGINEER Redmond, WA
    Services Development Manager (Business Development Manager - Services) Paris, FRA; Munich, DEU
    SENIOR SOFTWARE ENGINEER (PLATFORM) Redmond, WA
    E-Marketing Programs Specialist EMEA London, GBR
    BUSINESS DEVELOPMENT DIRECTOR - E COMMERCE INTEGRATION San Jose, CA
    MANAGER, E-SALES Plano, TX

  • NullPointerException in weblogic.jdbc.rmi.SerialConnection.createStatement()

    Hello,
    we are running WLS 6.1 SP2. The following code sometimes (rather rarely) throws
    a NullPointerException:
    Connection dbConnection = DBUtil.getDBConnection();//here we get the Connection
    stmt = dbConnection.createStatement(ResultSet.TYPE_FORWARD_ONLY, ResultSet.CONCUR_UPDATABLE);//it's
    where NPE happens
    The error report says:
    java.sql.SQLException:
    java.lang.NullPointerException at
    weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
    So, I think, this is something in WebLogic's code... Is this a known issue (I
    couldn't find a similar report in the newsgroup)? Is there a workaround?
    regards,
    Vitaly

    Vitaly Sourikov wrote:
    "Vitaly Sourikov" <[email protected]> wrote:
    The patches that we use with SP2 are
    CR061106_61sp2.jar
    CR072612_61sp2.jar
    CR077919_61sp2.jar
    As far as we know, those fixes (or some of them) were not introduced in SP4. Are
    there new versions of the patches for SP4?I have found that all these bugs are fixed in sp4, so no patches are needed if you
    upgrade to 6.1sp4.
    Joe
    >
    >
    regards,
    Vitaly
    Hi Joseph,
    Thank you for the reply. Unfortunately, we cannot move to SP3 or SP4
    - they have
    conflicts with other patches from WebLogic we use. This error happens
    rather rarely.
    In most of cases this very stuff works. But it would be intresing to
    have this
    patch for diagnostics, in case of future failures. Would you send it
    to me, please?
    Thank you in advance,
    Vitaly
    Joseph Weinstein <[email protected]> wrote:
    Vitaly Sourikov wrote:
    Hello,
    we are running WLS 6.1 SP2. The following code sometimes (rather rarely)throws
    a NullPointerException:
    Connection dbConnection = DBUtil.getDBConnection();//here we get theConnection
    stmt = dbConnection.createStatement(ResultSet.TYPE_FORWARD_ONLY, ResultSet.CONCUR_UPDATABLE);//it's
    where NPE happens
    The error report says:
    java.sql.SQLException:
    java.lang.NullPointerException at
    weblogic.jdbc.rmi.SerialConnection.createStatement(SerialConnection.java:396)
    So, I think, this is something in WebLogic's code... Is this a knownissue (I
    couldn't find a similar report in the newsgroup)? Is there a workaround?Hi. The NPE is probably happening in the actual DBMS driver. What is
    happening
    is that the rmi driver is having to catch any non-SQLException, andthrow
    a SQLException
    with the message of the original exception. Unfortunately, the fullstacktrace
    of the
    original NPE is lost. If you want, I can send you a small diagnostic
    patch, which will
    just make the rmi object retain the whole original stacktrace in the
    exception it throws,
    and that will help lead to the real problem.
    This may well be a bug that was fixed in sp3 or 4. Is it possible
    for you to upgrade to
    the latest stuff?
    Joe
    regards,
    Vitaly

  • ClassCastException: weblogic.jdbc.rmi.SerialResultSet

    HI,
    I am using WebLogic 6.0 SP2 connection pooling to get CLOB data from Oracle database.
    It is working fine to get the connection and get non-CLOB data like string, but
    when I retrieve the CLOB column in my program such as, theClob = ((oracle.jdbc.OracleResultSet)
    rs).getCLOB(1),
    Weblogic throws ClassCastException: weblogic.jdbc.rmi.SerialResultSet, does anybody
    experience the same problem ? How can I get around this problem ?
    Thanks
    John

    Hi,
    I've got the same error. The only diference is that I read BLOBs out of the table
    ((oracle.jdbc.OracleResultSet)rset).getBLOB(1) from oracle.jdbc.OracleResultSet).
    Best regards,
    Kai
    "John Chen" <[email protected]> wrote:
    >
    HI,
    I am using WebLogic 6.0 SP2 connection pooling to get CLOB data from
    Oracle database.
    It is working fine to get the connection and get non-CLOB data like string,
    but
    when I retrieve the CLOB column in my program such as, theClob = ((oracle.jdbc.OracleResultSet)
    rs).getCLOB(1),
    Weblogic throws ClassCastException: weblogic.jdbc.rmi.SerialResultSet,
    does anybody
    experience the same problem ? How can I get around this problem ?
    Thanks
    John

  • Weblogic Test Browser

    Weblogic Test Browser is not able to handle miltiple windows. When javascript is used to open a new window, the test browser passes the control to the default browser of the machine but the session object is lost.
    Can we expect support for Multiple browser windows in the future version?
    BTW am running WebLogic Server 8.1 SP4.
    Krish

    Hi manjunath,
    I had the same error on a similar config (win2k, ie 5). We tried several
    other configuration (with newer browsers) and didn't have the same
    experience.
    I'm almost sure that the problem is the browser, which is too old and
    doesn't support some featrue used by the webapp. If you can do it I
    suggest to upgrade to a newer version.
    BR,
    don
    manjunath wrote:
    Hi all
    whenever i run any portal sample through Workshop Test Browser ,i get following
    error.
    a dialogue window "Internet Explorer script error" with following texts
    An error has occured in the script on this page
    Do you want to continue running scripts on this page ?
    I am running Win2K professional, weblogic platform 8.1.1.0 and IE 5.0
    But this problem does not appear in WinXP & IE6.0
    ANy idea what is missing ?
    thx
    manjunath

  • WebLogic Test Client,  throws java.lang.NoSuchMethodException

    In weblogic server 10.3, the  WebLogic Test Client,  throws java.lang.NoSuchMethodException for “any” soap fault message from the web  service.
    In Detail:
    Our web services uses JAX-WS spec and are deployed in WebLogic server 10.3.The web service ear file is generated using standard ant utility. We are using “WebLogic Test Client” available through WebLogic server administration console .The issue is, for “any” soap fault message from the web service, the test client generates “java.lang.NoSuchMethodException:” . The key point is we are creating this class. We are not using our own client. WebLogic Test Client 's service response section has the following stack trace.
    S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
    <S:Body>
    <S:Fault xmlns:ns4="http://www.w3.org/2003/05/soap-envelope">
    <faultcode>S:Server</faultcode>
    <faultstring>java.lang.NoSuchMethodException: our.custom.package.name.jaxws.IllegalStateWSFaultExceptionBean.setErrorCode(java.lang.String)</faultstring>
    <detail>
    <ns2:exception xmlns:ns2="http://jax-ws.dev.java.net/" class="com.sun.xml.ws.encoding.soap.SerializationException" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false">
    <message>java.lang.NoSuchMethodException: our.custom.package.name.jaxws.IllegalStateWSFaultExceptionBean.setErrorCode(java.lang.String)</message>
    <ns2:stackTrace>
    <ns2:frame class="com.sun.xml.ws.fault.SOAPFaultBuilder" file="SOAPFaultBuilder.java" line="328" method="createDetailFromUserDefinedException" />
    <ns2:frame class="com.sun.xml.ws.fault.SOAPFaultBuilder" file="SOAPFaultBuilder.java" line="306" method="getFaultDetail" />
    <ns2:frame class="com.sun.xml.ws.fault.SOAPFaultBuilder" file="SOAPFaultBuilder.java" line="170" method="createSOAPFaultMessage" />
    <ns2:frame class="com.sun.xml.ws.server.sei.EndpointMethodHandler" file="EndpointMethodHandler.java" line="265" method="invoke" />
    <ns2:frame class="com.sun.xml.ws.server.sei.SEIInvokerTube" file="SEIInvokerTube.java" line="93" method="processRequest" />
    <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="598" method="__doRun" />
    <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="557" method="_doRun" />
    <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="542" method="doRun" />
    <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="439" method="runSync" />
    <ns2:frame class="com.sun.xml.ws.server.WSEndpointImpl$2" file="WSEndpointImpl.java" line="243" method="process" />
    <ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit" file="HttpAdapter.java" line="444" method="handle" />
    <ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter" file="HttpAdapter.java" line="244" method="handle" />
    <ns2:frame class="com.sun.xml.ws.transport.http.servlet.ServletAdapter" file="ServletAdapter.java" line="134" method="handle" />
    <ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke" file="HttpServletAdapter.java" line="272" method="run" />
    <ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter" file="HttpServletAdapter.java" line="185" method="post" />
    <ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="180" method="doPost" />
    <ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="727" method="service" />
    <ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="64" method="service" />
    <ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="820" method="service" />
    <ns2:frame class="weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction" file="StubSecurityHelper.java" line="227" method="run" />
    <ns2:frame class="weblogic.servlet.internal.StubSecurityHelper" file="StubSecurityHelper.java" line="125" method="invokeServlet" />
    <ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="292" method="execute" />
    <ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="175" method="execute" />
    <ns2:frame class="weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction" file="WebAppServletContext.java" line="3498" method="run" />
    <ns2:frame class="weblogic.security.acl.internal.AuthenticatedSubject" file="AuthenticatedSubject.java" line="321" method="doAs" />
    <ns2:frame class="weblogic.security.service.SecurityManager" line="unknown" method="runAs" />
    <ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2180" method="securedExecute" />
    <ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2086" method="execute" />
    <ns2:frame class="weblogic.servlet.internal.ServletRequestImpl" file="ServletRequestImpl.java" line="1406" method="run" />
    <ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="201" method="execute" />
    <ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="173" method="run" />
    </ns2:stackTrace>
    <ns2:cause class="java.lang.NoSuchMethodException" note="To disable this feature, set com.sun.xml.ws.fault.SOAPFaultBuilder.disableCaptureStackTrace system property to false">
    <message>our.custom.package.name.jaxws.IllegalStateWSFaultExceptionBean.setErrorCode(java.lang.String)</message>
    <ns2:stackTrace>
    <ns2:frame class="java.lang.Class" file="Class.java" line="1605" method="getMethod" />
    <ns2:frame class="com.sun.xml.ws.fault.SOAPFaultBuilder" file="SOAPFaultBuilder.java" line="323" method="createDetailFromUserDefinedException" />
    <ns2:frame class="com.sun.xml.ws.fault.SOAPFaultBuilder" file="SOAPFaultBuilder.java" line="306" method="getFaultDetail" />
    <ns2:frame class="com.sun.xml.ws.fault.SOAPFaultBuilder" file="SOAPFaultBuilder.java" line="170" method="createSOAPFaultMessage" />
    <ns2:frame class="com.sun.xml.ws.server.sei.EndpointMethodHandler" file="EndpointMethodHandler.java" line="265" method="invoke" />
    <ns2:frame class="com.sun.xml.ws.server.sei.SEIInvokerTube" file="SEIInvokerTube.java" line="93" method="processRequest" />
    <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="598" method="__doRun" />
    <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="557" method="_doRun" />
    <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="542" method="doRun" />
    <ns2:frame class="com.sun.xml.ws.api.pipe.Fiber" file="Fiber.java" line="439" method="runSync" />
    <ns2:frame class="com.sun.xml.ws.server.WSEndpointImpl$2" file="WSEndpointImpl.java" line="243" method="process" />
    <ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit" file="HttpAdapter.java" line="444" method="handle" />
    <ns2:frame class="com.sun.xml.ws.transport.http.HttpAdapter" file="HttpAdapter.java" line="244" method="handle" />
    <ns2:frame class="com.sun.xml.ws.transport.http.servlet.ServletAdapter" file="ServletAdapter.java" line="134" method="handle" />
    <ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke" file="HttpServletAdapter.java" line="272" method="run" />
    <ns2:frame class="weblogic.wsee.jaxws.HttpServletAdapter" file="HttpServletAdapter.java" line="185" method="post" />
    <ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="180" method="doPost" />
    <ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="727" method="service" />
    <ns2:frame class="weblogic.wsee.jaxws.JAXWSServlet" file="JAXWSServlet.java" line="64" method="service" />
    <ns2:frame class="javax.servlet.http.HttpServlet" file="HttpServlet.java" line="820" method="service" />
    <ns2:frame class="weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction" file="StubSecurityHelper.java" line="227" method="run" />
    <ns2:frame class="weblogic.servlet.internal.StubSecurityHelper" file="StubSecurityHelper.java" line="125" method="invokeServlet" />
    <ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="292" method="execute" />
    <ns2:frame class="weblogic.servlet.internal.ServletStubImpl" file="ServletStubImpl.java" line="175" method="execute" />
    <ns2:frame class="weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction" file="WebAppServletContext.java" line="3498" method="run" />
    <ns2:frame class="weblogic.security.acl.internal.AuthenticatedSubject" file="AuthenticatedSubject.java" line="321" method="doAs" />
    <ns2:frame class="weblogic.security.service.SecurityManager" line="unknown" method="runAs" />
    <ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2180" method="securedExecute" />
    <ns2:frame class="weblogic.servlet.internal.WebAppServletContext" file="WebAppServletContext.java" line="2086" method="execute" />
    <ns2:frame class="weblogic.servlet.internal.ServletRequestImpl" file="ServletRequestImpl.java" line="1406" method="run" />
    <ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="201" method="execute" />
    <ns2:frame class="weblogic.work.ExecuteThread" file="ExecuteThread.java" line="173" method="run" />
    </ns2:stackTrace>
    </ns2:cause>
    </ns2:exception>
    </detail>
    </S:Fault>
    </S:Body>
    </S:Envelope>

    Thanks for your assistance. Here is the log from weblogic. You may find "xxx" and "yyy" terms. these are given to our specific project oriented names. If you need any further info please let me know. Again a brief about the issue. when the service returns a fault soap message, the server trying to set the error code in a class generated by it's own where the method is not avilable. this happens for all fault soap message. In case of right response from the service no issues. all are working fine.
    Note: Max 3000 characters are allowed to post. so truncating initial stack trace.
    Thanks, ganesh.
    <xxx JDBC connection is xxx.jdbc.driver.LogicalConnection@2e0bd8e
    Bound datums[Lxxx.sql.STRUCT;@1b2d059
    xxx JDBC connection is xxx.jdbc.driver.LogicalConnection@1aa0f36
    xxx JDBC connection is xxx.jdbc.driver.LogicalConnection@191d9ba
    Bound datums[Lxxx.sql.STRUCT;@1dc70ec
    xxx JDBC connection is xxx.jdbc.driver.LogicalConnection@1def11c
    xxx JDBC connection is xxx.jdbc.driver.LogicalConnection@2683f76
    Bound datums[Lxxx.sql.STRUCT;@197400e
    Caused by: our.package.name.integration.services.exception.IllegalStateWSFaultException: Service Provider API did not return any object back.
    at xxx.xxx.yyy.integration.services.xxxservice.xxxService.findxxxxxx(xxxService.java:576)
    at sun.xxxlect.GeneratedMethodAccessor763.invoke(Unknown Source)
    at sun.xxxlect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.xxxlect.Method.invoke(Method.java:597)
    at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingxxxlection(AopUtils.java:281)
    at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.invokeJoinpoint(xxxlectiveMethodInvocation.java:187)
    at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:154)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
    at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
    at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:15)
    at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
    at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:30)
    at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
    at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
    at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
    at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
    at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
    at $Proxy188.findxxxxxx(Unknown Source)
    at xxx.xxx.yyy.integration.services.xxxservice.xxxService_n3bi9u_WSOImpl.__WL_findxxxxxx_WS(xxxService_n3bi9u_WSOImpl.java:75)
    at sun.xxxlect.GeneratedMethodAccessor762.invoke(Unknown Source)
    at sun.xxxlect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.xxxlect.Method.invoke(Method.java:597)
    at weblogic.wsee.server.ejb.WsEjb.invoke(WsEjb.java:50)
    at weblogic.wsee.jaxws.WLSEjbInstanceResolver$WLSEjbInvoker.invoke(WLSEjbInstanceResolver.java:187)
    ... 30 more
    Caused by: java.lang.IllegalStateException: Service Provider API did not return any object back.
    at our.package.name.soa.enabler.service.provider.engine.ServiceInvoker.invoke(ServiceInvoker.java:156)
    at xxx.xxx.yyy.integration.services.xxxservice.xxxService.findxxxxxx(xxxService.java:545)
    ... 56 more
    Nov 21, 2008 9:38:27 AM com.sun.xml.ws.server.sei.EndpointMethodHandler invoke
    INFO: Service Provider API did not return any object back.
    our.package.name.integration.services.exception.IllegalStateWSFaultException: Service Provider API did not return any object back.
    at xxx.xxx.yyy.integration.services.xxxservice.xxxService.findxxxxxx(xxxService.java:576)
    at sun.xxxlect.GeneratedMethodAccessor763.invoke(Unknown Source)
    at sun.xxxlect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.xxxlect.Method.invoke(Method.java:597)
    at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingxxxlection(AopUtils.java:281)
    at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.invokeJoinpoint(xxxlectiveMethodInvocation.java:187)
    at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:154)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
    at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
    at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:15)
    at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
    at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:30)
    at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
    at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
    at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:126)
    at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:114)
    at com.bea.core.repackaged.springframework.aop.framework.xxxlectiveMethodInvocation.proceed(xxxlectiveMethodInvocation.java:176)
    at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210)
    at $Proxy188.findxxxxxx(Unknown Source)
    at xxx.xxx.yyy.integration.services.xxxservice.xxxService_n3bi9u_WSOImpl.__WL_findxxxxxx_WS(xxxService_n3bi9u_WSOImpl.java:75)
    at sun.xxxlect.GeneratedMethodAccessor762.invoke(Unknown Source)
    at sun.xxxlect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.xxxlect.Method.invoke(Method.java:597)
    at weblogic.wsee.server.ejb.WsEjb.invoke(WsEjb.java:50)
    at weblogic.wsee.jaxws.WLSEjbInstanceResolver$WLSEjbInvoker.invoke(WLSEjbInstanceResolver.java:187)
    at weblogic.wsee.jaxws.WLSInstanceResolver$WLSInvoker.invoke(WLSInstanceResolver.java:71)
    at com.sun.xml.ws.server.InvokerTube$2.invoke(InvokerTube.java:146)
    at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:257)
    at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:93)
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:598)
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:557)
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:542)
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:439)
    at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)
    at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)
    at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
    at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:134)
    at weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:272)
    at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:185)
    at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:180)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at weblogic.wsee.jaxws.JAXWSServlet.service(JAXWSServlet.java:64)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: java.lang.IllegalStateException: Service Provider API did not return any object back.
    at our.package.name.soa.enabler.service.provider.engine.ServiceInvoker.invoke(ServiceInvoker.java:156)
    at xxx.xxx.yyy.integration.services.xxxservice.xxxService.findxxxxxx(xxxService.java:545)
    ... 56 more
    com.sun.xml.ws.encoding.soap.SerializationException: java.lang.NoSuchMethodException: xxx.xxx.yyy.integration.services.xxxservice.jaxws.IllegalStateWSFaultExceptionBean.setErrorCode(java.lang.String)
    at com.sun.xml.ws.fault.SOAPFaultBuilder.createDetailFromUserDefinedException(SOAPFaultBuilder.java:328)
    at com.sun.xml.ws.fault.SOAPFaultBuilder.getFaultDetail(SOAPFaultBuilder.java:306)
    at com.sun.xml.ws.fault.SOAPFaultBuilder.createSOAPFaultMessage(SOAPFaultBuilder.java:170)
    at com.sun.xml.ws.server.sei.EndpointMethodHandler.invoke(EndpointMethodHandler.java:265)
    at com.sun.xml.ws.server.sei.SEIInvokerTube.processRequest(SEIInvokerTube.java:93)
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:598)
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:557)
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:542)
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:439)
    at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243)
    at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:444)
    at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244)
    at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:134)
    at weblogic.wsee.jaxws.HttpServletAdapter$AuthorizedInvoke.run(HttpServletAdapter.java:272)
    at weblogic.wsee.jaxws.HttpServletAdapter.post(HttpServletAdapter.java:185)
    at weblogic.wsee.jaxws.JAXWSServlet.doPost(JAXWSServlet.java:180)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
    at weblogic.wsee.jaxws.JAXWSServlet.service(JAXWSServlet.java:64)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
    at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
    at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:175)
    at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3498)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(Unknown Source)
    at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
    at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
    at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Caused by: java.lang.NoSuchMethodException: xxx.xxx.yyy.integration.services.xxxservice.jaxws.IllegalStateWSFaultExceptionBean.setErrorCode(java.lang.String)
    at java.lang.Class.getMethod(Class.java:1605)
    at com.sun.xml.ws.fault.SOAPFaultBuilder.createDetailFromUserDefinedException(SOAPFaultBuilder.java:323)
    ... 30 more

  • Can weblogic test client be used in weblogic 8.1 version

    Can anyone confirm whether we can use weblogic test client in weblogic server 8.1 version

    We figured out that Oracle SQL Flavor can be used with WebLogic, but only with DB connections created from JDBC URL, not work with DB connections from WebLogic connection pool.

  • Crystal Reports in Java with BEA Weblogic (test drive)

    Hello,<br/>
    <br/>
    The question is: What is wrong with Crystal Reports or BEA Weblogic, when they are working together? And how can it be repaired?<br/>
    <br/>
    I have a project working with reports. Tried to implement it for crystal reports and found an interesting problem. Crystal Reports didn't work with BEA Weblogic as well as with other servers. 1-2 years ago we just took Tomcat and worked with it. Right now we are interested in working with BEA.<br/>
    <br/>
    Everything works, but much slower than other servers. The best explanation is just a my tries in the end of the post. I hope some clever man helps me to option Weblogic or at least explains what is wrong.<br/>
    <br/>
    Test results are:<br/>
    <br/>
    - Apache Software Foundation - Tomcat 6.0:<br/>
    ~3 sec for clientDoc.open(reportName, OpenReportOptions._openAsReadOnly);<br/>
    ~1 sec for crystalReportPageViewer.processHttpRequest(request, response, application, null); <br/>
    <br/>
    - OC4J - Oracle Containers for J2EE 10g (10.1.3.3.0):<br/>
    ~4 sec for clientDoc.open(reportName, OpenReportOptions._openAsReadOnly);<br/>
    ~1 sec for crystalReportPageViewer.processHttpRequest(request, response, application, null); <br/>
    <br/>
    - Jetty 7.0.0.pre5:<br/>
    ~2 sec for clientDoc.open(reportName, OpenReportOptions._openAsReadOnly);<br/>
    ~0 sec for crystalReportPageViewer.processHttpRequest(request, response, application, null); <br/>
    <br/>
    - BEA Weblogic 9.2:<br/>
    <b>~30 sec</b> for clientDoc.open(reportName, OpenReportOptions._openAsReadOnly);<br/>
    <b>~8 sec</b> for crystalReportPageViewer.processHttpRequest(request, response, application, null); <br/>
    <br/>
    simple_cr_webapp.war (30 MB) can be downloaded [here|http://rapidshare.com/files/221096566/simple_cr_webapp.war.html] or [here|http://math.ut.ee/~a30858/simple_cr_webapp.war]:<br/>
    crystalreportviewers //all viewers for 2.0
    WEB-INF
      classes
        CRConfig.xml //see WAR - without key, only sets timeout and report location
      lib //all libraries for Eclipse plugin's web-app + j2ee.jar
      web.xml //see WAR - generated by Eclipse plugin
    sample.jsp //see WAR - generated by Eclipse plugin
    sample.rpt //"Consolidated Balance Sheet.rpt" from Eclipse plugin's web-app samples
    <br/>
    P.S. It is also suites if someone gives a simple project with CR, that works well. I really need to get solution for this problem, so any advises are expected.<br/>

    I also tried for different java vendors on BEA Weblogic 9.2.
    Results for Jrockit are above: 30 sec and 8 sec
    Results for Sun are worse than JRockit: 50 sec and 10 sec
    JRockit:
    java version "1.5.0_04"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
    BEA JRockit(R) (build R26.0.0-189_CR269406-59389-1.5.0_04-20060322-1120-win-ia32, )
    JAVA Memory arguments: -Xms500m -Xmx1000m
    Sun:
    java version "1.5.0_04"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
    Java HotSpot(TM) Client VM (build 1.5.0_04-b05, mixed mode)
    JAVA Memory arguments: -Xms256m -Xmx512m -XX:CompileThreshold=8000 -XX:PermSize=256m -XX:MaxPermSize=256m

  • WebLogic Test & Development server

    We are about to start a web service and have been considering a number of enviroments
    including .net, lotus and BEA. We have decided on BEA because of its market share,
    openness and scalability. Our .net trained programmers think it is S____ Hot.
    However as I am paying the licence fees I am a little confused about one element
    (involves more money)
    Our development time to our first production service is only 12 weeks
    My question is Do we need to purchase the Test & Development Licence and subsequent
    support fees with such a short lead time to first production.
    Can we not do every thing we would need to develop and test with a full Server
    liscence.

    "Joel Nylund" <[email protected]> wrote in message
    news:3cee46b8$[email protected]..
    I have the same question if anyone from weblogic is out there? It lookslike
    I can just copy the files from the ldap directory over.
    Does the embeded server support regular ldap protocol from other clients.Yes. You can use either the listen port or the SSL listen port. You can set
    the
    credentials for the Admin server in the Embedded LDAP tab off the security
    tab off the domain (they are generated on the first boot). The admin
    principal
    is cn=Admin
    Can I browse the ldap entries from other tools?Yes.
    Can I add additional attributes to entries for users?
    That would not be supported as adding new attributes may cause problems
    at upgrade times if we change the schema.
    thanks
    Joel
    "Andy Kim" <[email protected]> wrote in message
    news:[email protected]..
    I am using the embedded LDAP server to store users, groups and roles. I
    have a development server and nowI want to import the security settingsfrom
    the development server to the test servers. Both servers are running
    WebLogic 7. How do I export users, groups and roles from the
    development
    server and import to the test server.
    Thanks,
    Andy

  • ClassCastException: weblogic.jdbc.rmi.SerialPreparedStatement

    I am attempting to retrieve CLOBs and XMLTypes in a servelet from a 9i release
    2 database. Using sampe code from oracle, I am getting ClassCastException when
    I attempt to cast ...
    oracle.jdbc.OraclePreparedStatement stmt =
    (oracle.jdbc.OraclePreparedStatement) conn.prepareStatement( sql );
    The connection pool sets up fine, no errors. I am getting the connection in the
    servlet through the JNDI lookup ... (see code)
    From the config.xml, the jdbc setup ...
    <JDBCConnectionPool DriverName="oracle.jdbc.driver.OracleDriver"
    InitialCapacity="3" MaxCapacity="10" Name="9iR2Pool"
    Properties="user=kr;password=*****;dll=ocijdbc9;protocol=oci8"
    Targets="myserver" URL="jdbc:oracle:oci8:@ora9i"/>
    Has anyone done this before? Is there another way? Does bea have 9i release
    2 jdbc drivers?
    [huh.java]

    Hi Rick,
    JDBC objects obtained via a connection pool
    can not be cast to anything oracle.jdbc.*.
    In order to use oracle-specific functions of
    prepared statements you need to use oracle
    extensions provided by weblogic. Documentation
    and examples can be found here:
    http://e-docs.bea.com/wls/docs61/jdbc/thirdparty.html#1043705
    Regards,
    Slava Imeshev
    "Rick Bradshaw" <[email protected]> wrote in message
    news:3d6cfa2c$[email protected]..
    >
    I am attempting to retrieve CLOBs and XMLTypes in a servelet from a 9irelease
    2 database. Using sampe code from oracle, I am getting ClassCastExceptionwhen
    I attempt to cast ...
    oracle.jdbc.OraclePreparedStatement stmt =
    (oracle.jdbc.OraclePreparedStatement) conn.prepareStatement( sql );
    The connection pool sets up fine, no errors. I am getting the connectionin the
    servlet through the JNDI lookup ... (see code)
    From the config.xml, the jdbc setup ...
    <JDBCConnectionPool DriverName="oracle.jdbc.driver.OracleDriver"
    InitialCapacity="3" MaxCapacity="10" Name="9iR2Pool"
    Properties="user=kr;password=*****;dll=ocijdbc9;protocol=oci8"
    Targets="myserver" URL="jdbc:oracle:oci8:@ora9i"/>
    Has anyone done this before? Is there another way? Does bea have 9irelease
    2 jdbc drivers?

  • My connector wants XA, Weblogic gives RMI

    Hello,
              First, yes I know Cloudscape may not be the best database for production and
              XA, but anyway, I have to use it, and it supports XA.
              Now my question :
              I'm using WLS 6.1 SP1.
              I defined a Cloudscape XA pool which seems to initialize well (the server
              logs shows initial connections creations for the XA pool successfully). For
              this pool, the driver classname I use is COM.cloudscape.core.XADataSource.
              Over this pool I defined a Tx Data Source which some JNDI name, let's say
              "MyXADataSource".
              This works well and I can get and use connections from this "MyXADataSource"
              datasource while I use it as a javax.sql.DataSource (from a BMP for
              example).
              However this DataSource is not XA. I mean that it does not implement
              javax.sql.XADataSource (the concrete class is actually
              weblogic.jdbc.common.internal.RmiDataSource). This is a problem for example
              when a connector (let's say the BlackBoxXA sample connector) tries to use
              this datasource as an XA datasource, leading to a ClassCastException.
              So why the concrete weblogic.jdbc.common.internal.RmiDataSource class is not
              an XA class ? Did I configure something wrong or forget something ?
              Thanks for your help.
              Jérôme.
              Jérôme.
              

    Hello,
              First, yes I know Cloudscape may not be the best database for production and
              XA, but anyway, I have to use it, and it supports XA.
              Now my question :
              I'm using WLS 6.1 SP1.
              I defined a Cloudscape XA pool which seems to initialize well (the server
              logs shows initial connections creations for the XA pool successfully). For
              this pool, the driver classname I use is COM.cloudscape.core.XADataSource.
              Over this pool I defined a Tx Data Source which some JNDI name, let's say
              "MyXADataSource".
              This works well and I can get and use connections from this "MyXADataSource"
              datasource while I use it as a javax.sql.DataSource (from a BMP for
              example).
              However this DataSource is not XA. I mean that it does not implement
              javax.sql.XADataSource (the concrete class is actually
              weblogic.jdbc.common.internal.RmiDataSource). This is a problem for example
              when a connector (let's say the BlackBoxXA sample connector) tries to use
              this datasource as an XA datasource, leading to a ClassCastException.
              So why the concrete weblogic.jdbc.common.internal.RmiDataSource class is not
              an XA class ? Did I configure something wrong or forget something ?
              Thanks for your help.
              Jérôme.
              Jérôme.
              

  • DataSource is XA but Weblogic gives RMI

    Hello,
              First, yes I know Cloudscape may not be the best database for production and
              XA, but anyway, I have to use it, and it supports XA.
              Now my question :
              I'm using WLS 6.1 SP1.
              I defined a Cloudscape XA pool which seems to initialize well (the server
              logs shows initial connections creations for the XA pool successfully). For
              this pool, the driver classname I use is COM.cloudscape.core.XADataSource.
              Over this pool I defined a Tx Data Source which some JNDI name, let's say
              "MyXADataSource".
              This works well and I can get and use connections from this "MyXADataSource"
              datasource while I use it as a javax.sql.DataSource (from a BMP for
              example).
              However this DataSource is not XA. I mean that it does not implement
              javax.sql.XADataSource (the concrete class is actually
              weblogic.jdbc.common.internal.RmiDataSource). This is a problem for example
              when a connector (let's say the BlackBoxXA sample connector) tries to use
              this datasource as an XA datasource, leading to a ClassCastException.
              So why the concrete weblogic.jdbc.common.internal.RmiDataSource class is not
              an XA class ? Did I configure something wrong or forget something ?
              Thanks for your help.
              Jérôme.
              

    Thanks Priscilla,
              But, so, why the BlackBoxXA connector tries to cast the datasource it
              lookups to XADataSource ?
              Jérôme.
              "Priscilla Fung" <[email protected]> a écrit dans le message de news:
              [email protected]...
              > Hi,
              >
              > The javax.sql.XADataSource, XAConnection interfaces are for container uses
              > only, and are not exposed to applications. Applications should only see
              and
              > use javax.sql.DataSource and java.sql.Connection etc. Refer to the JDBC
              2.0
              > Standard Extension spec or JDBC 3.0 spec for more info.
              >
              > Regards,
              > Priscilla
              >
              > Jérôme Beau <[email protected]> wrote in message
              > news:[email protected]...
              > > Hello,
              > >
              > > First, yes I know Cloudscape may not be the best database for production
              > and
              > > XA, but anyway, I have to use it, and it supports XA.
              > >
              > > Now my question :
              > >
              > > I'm using WLS 6.1 SP1.
              > >
              > > I defined a Cloudscape XA pool which seems to initialize well (the
              server
              > > logs shows initial connections creations for the XA pool successfully).
              > For
              > > this pool, the driver classname I use is
              COM.cloudscape.core.XADataSource.
              > >
              > > Over this pool I defined a Tx Data Source which some JNDI name, let's
              say
              > > "MyXADataSource".
              > >
              > > This works well and I can get and use connections from this
              > "MyXADataSource"
              > > datasource while I use it as a javax.sql.DataSource (from a BMP for
              > > example).
              > >
              > > However this DataSource is not XA. I mean that it does not implement
              > > javax.sql.XADataSource (the concrete class is actually
              > > weblogic.jdbc.common.internal.RmiDataSource). This is a problem for
              > example
              > > when a connector (let's say the BlackBoxXA sample connector) tries to
              use
              > > this datasource as an XA datasource, leading to a ClassCastException.
              > >
              > > So why the concrete weblogic.jdbc.common.internal.RmiDataSource class is
              > not
              > > an XA class ? Did I configure something wrong or forget something ?
              > >
              > > Thanks for your help.
              > >
              > > Jérôme.
              > >
              > >
              >
              >
              

  • Just deployed to external weblogic test server with oid

    I am getting errors for the beans that have to do with progress bars. It says these objects are not serializable.
    When I try to implement serializable I still get that error. What do I need to do?
    I have 3 progress bars in view scope.
    SEVERE: ADFc: Scope object serialization failed (object not serializable), scope='viewScope[page.jsf]', objectKey='progressBarSampleBean',
    Edited by: veena pandit on May 2, 2012 3:39 PM

    SEVERE: ADFc: Scope object serialization failed (object not serializable), scope='viewScope[page.jsf]', objectKey='progressBarSampleBean',

  • Java.lang.ClassCastException: weblogic.jdbc20.rmi.SerialResultSet

    You can try this as a work around :
    // CLOB clob = ((OracleResultSet) rs).getCLOB (2); this causes the exception
    // this is the work around (assuming thin drivers)
    java.sql.Clob clobFromDB = (java.sql.Clob) rs.getObject("MYCLOBCOL");
    int len = (int) clobFromDB.length();
    String str = clobFromDB.getSubString (Long.parseLong("1"), len );

    hi, all.
    I also encounter this problem.but I can't see your message body on this subject. can you help me to resolve this problem? Please send to me by email. Thanks!

  • Why JDEVADF11.1.1.3 can not test web service in IE for  Integrated WebLogic

    Hi,
    Testing a web service deployed to Integrated WebLogic Server.
    1.When you deploy the web service to Integrated WebLogic Server, examine the contents of the log window. Find http://IP_address:port/Project1-context-root/MyWebService1
    2.Copy the URL and paste it into browser. The browser shows a simple page which lists the operations available on the service.
    3.Enter a parameter, and click Enter. The result from the web service is displayed.
    My question:
    Why only display Web Services Endpoint and Information . Can not have Enter a parameter and operations available on the service.
    HttP analyzer test web service is OK.
    Thanks

    Hi,
    That is because you are looking at the endpoint information.
    If you want to test the service in a browser, then you can use the Weblogic Test Client.
    When your Integrated WLS is running, point the browser to the following url: http://localhost:7101/wls_utc/
    Thanks,
    Vishal

Maybe you are looking for

  • Multibyte character (Chinese, Korean....) support problem

    I used OLE DB(C++) and JDBC(Java) in Oracle 8i server with no problem. I worked very well. but using ADO.NET(C#), there are the critical problem in selecting and inserting multibyte character (Chinese,Korean.. so on) Oracle 8i Server charset : US7ASC

  • Matrix with CFL and RecordSet with DoQuery

    Hello Experts,                         How to use Matrix with CFL and RecordSet with DoQuery

  • Mavericks - clean install with filevault and Time machine restore

    Hi All, I will update my MacBook pro mid 2011 with the new Mavericks OS. I've activated Filevault on my HDD due to corporate security rules. I want to make a clean install of the new OS. I plan the following action: 1 - Make a full backup with Time m

  • Bootcamp quits unexpectedly when opened.

    Hi. My Mac Mini quits Bootcamp every time I open it. I dont know if updating my OS will help. Here are the details: Process:         Boot Camp Assistant [1712] Path:            /Applications/Utilities/Boot Camp Assistant.app/Contents/MacOS/Boot Camp

  • Force quit

    I am getting too many Force Quit/SBOD responses for too long. Why? What can I do to fix it? I have been through trash cache, repair permissions, verify disk and trash Safari cache. Can I avoid reinstall system?