My problem in using weblogic Datasource and proxy user

Hello
I create a DataSource in Weblogic that connect to the database by a proxy user and I have a client application that use this DataSource and create a proxy session , I've written my client application (it's a stand alone client application) code below :
public static void main(String [] args) {
OracleConnection conn=null;
javax.sql.DataSource ds=null;
Hashtable env = new Hashtable();
env.put( Context.INITIAL_CONTEXT_FACTORY, "weblogic.jndi.WLInitialContextFactory" );
env.put(Context.PROVIDER_URL, "t3://127.0.0.1:7001");
try{
Context context=new InitialContext( env );
ds=(javax.sql.DataSource) context.lookup ("OracleConnection2");
conn=(OracleConnection) ds.getConnection();
java.util.Properties prop = new java.util.Properties();
prop.put(OracleConnection.PROXY_USER_NAME, "web_user1");
prop.put(OracleConnection.PROXY_USER_PASSWORD,"web_user1");
conn.openProxySession(OracleConnection.PROXYTYPE_USER_NAME, prop);
if (conn.isClosed()){
System.out.println("Connection closed");
return;
testJDBC(conn,true);
for(int k=0;k<10;k++){
testJDBC(conn,false);
conn.close(OracleConnection.PROXY_SESSION);
conn.close();
}catch(Exception ex){
ex.printStackTrace();
It works but my problem is that in line "prop.put(OracleConnection.PROXY_USER_PASSWORD,"web_user1")" or line "prop.put(OracleConnection.PROXY_USER_NAME, "web_user1");"
Let me to mention a scenario :
*1- I type a wrong username or password in my client application and I run the client application it shows me this error : invalid username/password*
*this error is acceptable*
*2- then I correct the wrong username or password immediately and run the application again , it shows me this error (at line conn.openProxySession(OracleConnection.PROXYTYPE_USER_NAME, prop)) :*
java.sql.SQLException: Closed Connection
     at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
     at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
     at weblogic.jdbc.rmi.internal.ConnectionImpl_weblogic_jdbc_wrapper_JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection_1032_WLStub.openProxySession(Unknown Source)
     at weblogic.jdbc.rmi.SerialConnection_weblogic_jdbc_rmi_internal_ConnectionImpl_weblogic_jdbc_wrapper_JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection_1032_WLStub.openProxySession(Unknown Source)
     at oracle.HRFacadeClient.main(HRFacadeClient.java:38)
*3- I run the application again (by correct username and password) but this time it shows me this error :*
java.sql.SQLException: Unsupported feature
     at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
     at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:223)
     at weblogic.jdbc.rmi.internal.ConnectionImpl_weblogic_jdbc_wrapper_JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection_1032_WLStub.openProxySession(Unknown Source)
     at weblogic.jdbc.rmi.SerialConnection_weblogic_jdbc_rmi_internal_ConnectionImpl_weblogic_jdbc_wrapper_JTAConnection_weblogic_jdbc_wrapper_XAConnection_oracle_jdbc_driver_LogicalConnection_1032_WLStub.openProxySession(Unknown Source)
     at oracle.HRFacadeClient.main(HRFacadeClient.java:38)
*4 - if I repeat running the application for multi times every time it shows me the previous error*
*5- I wait about one minute the problem solved and my application can create proxy session *
the result is that if I wanna create proxy session by wrong username or password and I get "Invalid username/password" error message , then after correcting username or password I have to wait about one minute and then run the application again_
Do you know how I can overcome this problem ?
Thank you

Hi Jamshid,
There is same problem observed few days back with us, and we have used the below code, and it got solved. Actually there is a problem observed while using proxy connections on weblogic.
if(conn instanceof weblogic.jdbc.extensions.WLConnection){
     weblogic.jdbc.extensions.WLConnection cn=(weblogic.jdbc.extensions.WLConnection)conn;
     cn.clearStatementCache();
http://rocksolutions.wordpress.com/2010/06/04/connection-pool-issue-on-weblogic/
Hope this helps.
Thanks

Similar Messages

  • Problem in starting weblogic server as proxy

    I am using weblogic server as Proxy to forward the requests to weblogic cluster.
    When i bring up the proxy, it works fine, but when i try to access the application deployed in cluster through Proxy, the proxy server crashes with the follwoing error.
    I am Pasting my complete logs below.
    Setting JVM memory params for server IRISProxy
    Using server IRISProxy-specfic java memory arguments: -Xms32m -Xmx200m -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=80 -XX:MaxPermSize=128m -XX:+DisableExplicitGC -XX:NewRatio=4
    WLS Production Mode=true
    ./startWebLogic.sh[68]: B: not found.
    maxfiles=8192
    CLASSPATH=/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/CR211812_81sp4.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/CR235145_81sp4.jar:/home/weblogic/bea_wli/weblogic81/common/lib/CR224719_81sp2.jar:/home/weblogic/bea_wli/weblogic81/common/lib/CR137449_81sp2.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic_knex_patch.jar:/home/weblogic/bea_wli/weblogic81/common/lib/log4j.jar:/home/weblogic/bea_wli/weblogic81/server/lib/debugging.jar:/home/weblogic/bea_wli/weblogic81/server/lib/knex.jar:/home/weblogic/bea_wli/weblogic81/javelin/lib/javelin.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wlw-lang.jar:/home/weblogic/bea_wli/jdk141_05/lib/tools.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic_sp.jar:/home/weblogic/bea_wli/weblogic81/server/lib/weblogic.jar:/home/weblogic/bea_wli/weblogic81/server/lib/ojdbc14.jar:/home/weblogic/bea_wli/weblogic81/server/lib/ant/ant.jar:/home/weblogic/bea_wli/jdk141_05/jre/lib/rt.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/agent_tools_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-Admin:/opt/jes/policy_agent/IdentityServer/j2ee_agents/locale:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_agent_sdk_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_agent_filter_2_1.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_sdk.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_services.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_sso_provider.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_logging.jar:/opt/jes/policy_agent/IdentityServer/j2ee_agents/lib/am_wl70_agent_2_1.jar:::::/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/SecurityClient-v1.0.7.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/Log4JInitServlet.jar:/home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/util/log4j_IRIS-1.2.4.jar:::/home/weblogic/bea_wli/weblogic81/server/lib/webserviceclient.jar:/home/weblogic/bea_wli/weblogic81/server/lib/webserviceclient+ssl.jar:/home/weblogic/bea_wli/weblogic81/server/lib/xbean.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wlxbean.jar:/home/weblogic/bea_wli/weblogic81/server/lib/xqrl.jar:/home/weblogic/bea_wli/weblogic81/server/lib/netui/netui-compiler.jar:/home/weblogic/bea_wli/weblogic81/server/lib/wli.jar:/home/weblogic/bea_wli/weblogic81/server/lib/fop.jar:/home/weblogic/bea_wli/weblogic81/integration/adapters/sample/lib/sample-eis.jar:
    PATH=/home/weblogic/bea_wli/weblogic81/server/bin:/home/weblogic/bea_wli/weblogic81/server/bin:/home/weblogic/bea_wli/jdk141_05/jre/bin:/home/weblogic/bea_wli/jdk141_05/bin:/usr/sbin:/usr/bin:/usr/ccs/bin:/usr/contrib/bin:/usr/local/bin:/opt/hparray/bin:/opt/nettladm/bin:/opt/upgrade/bin:/opt/fcms/bin:/opt/pd/bin:/usr/bin/X11:/usr/contrib/bin/X11:/opt/resmon/bin:/opt/perf/bin:/opt/prm/bin:/opt/mx/bin:/opt/gnome/bin:/opt/wbem/bin:/opt/wbem/sbin:/opt/ignite/bin:/opt/graphics/common/bin:/usr/sbin/diag/contrib:/opt/sec_mgmt/spc/bin:/opt/networker/bin:/opt/sec_mgmt/bastille/bin:/opt/hpnpl//bin:/opt/mozilla:/opt/OV/bin/OpC:/opt/OV/bin:/sbin:/home/root:/util:/home/weblogic/bea_wli/jdk141_05/jre/bin:/usr/local/bin:/usr/local/sbin:.
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http://hostname:port/console *
    starting weblogic with Java version:
    java version "1.4.1.05"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1.05-030910-01:23)
    Java HotSpot(TM) Server VM (build 1.4.1 1.4.1.05-030910-02:49-PA_RISC2.0 PA2.0, mixed mode)
    Starting WLS with line:
    /home/weblogic/bea_wli/jdk141_05/bin/java -server -Xms32m -Xmx200m -XX:SurvivorRatio=4 -XX:TargetSurvivorRatio=80 -XX:MaxPermSize=128m -XX:+DisableExplicitGC -XX:NewRatio=4 -Dweblogic.security.SSL.trustedCAKeyStore=/home/weblogic/bea_wli/weblogic81/server/lib/cacerts -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dapp.config.dir=/home/weblogic/upload/appsvcdomain/IRIS/config -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain-IRIS/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dapp.config.dir=/home/weblogic/upload/appsvcdomain/IRIS/config -da -Dplatform.home=/home/weblogic/bea_wli/weblogic81 -Dwls.home=/home/weblogic/bea_wli/weblogic81/server -Dwli.home=/home/weblogic/bea_wli/weblogic81/integration -Dlog4j.configuration=file:/home/weblogic/bea_wli/weblogic81/common/lib/workshopLogCfg.xml -Dweblogic.management.discover=false -Dweblogic.management.server=t3://170.63.142.14:8100 -Dweblogic.security.SSL.ignoreHostnameVerify=false -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=true -Dweblogic.security.SSL.trustedCAKeyStore=/home/weblogic/bea_wli/weblogic81/server/lib/cacerts -Dcom.iplanet.coreservices.configpath=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain/ums -Djava.util.logging.config.file=/opt/jes/policy_agent/IdentityServer/j2ee_agents/config/_home_weblogic_bea_wli_user_projects_domains_AppSvcDomain/AMAgent.properties -DLOG_COMPATMODE=Off -Dmax_conn_pool=10 -Dmin_conn_pool=1 -Damconfig=AMAgent -Dweblogic.Name=IRISProxy -Dweblogic.ProductionModeEnabled=true -Djava.security.policy=/home/weblogic/bea_wli/weblogic81/server/lib/weblogic.policy weblogic.Server
    Bad level value for property: com.iplanet.services.debug.level
    Bad level value for property: com.sun.identity.agents.logging.level
    Bad level value for property: com.sun.am.policy.amFilter.audit.level
    <Mar 15, 2006 3:40:33 PM EST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.4.1 1.4.1.05-030910-02:49-PA_RISC2.0 PA2.0 from Hewlett-Packard Company>
    <Mar 15, 2006 3:40:34 PM EST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://170.63.142.14:8100 to check if there exists a running admin server at this URL.>
    <Mar 15, 2006 3:40:34 PM EST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
    <Mar 15, 2006 3:40:35 PM EST> <Warning> <Configuration Management> <BEA-150033> <The managed server should not be started in development mode.>
    <Mar 15, 2006 3:40:35 PM EST> <Info> <Management> <BEA-141107> <Version: WebLogic Temporary Patch for CR211812 01/23/2005 22:15:39
    WebLogic Temporary Patch for CR235145 08/16/2005 11:44:59
    WebLogic Temporary Patch for CR224719 04/29/2005 16:40:35
    WebLogic Temporary Patch for CR137449 02/24/2004 10:48:06
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic Integration 8.1 SP2 Thu Dec 11 22:07:14 PST 2003 148883>
    <Mar 15, 2006 3:40:35 PM EST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://170.63.142.14:8100 to retrieve the initial configuration.>
    <Mar 15, 2006 3:40:46 PM EST> <Notice> <Log Management> <BEA-170019> <The server log file /home/weblogic/bea_wli/user_projects/domains/AppSvcDomain/IRISProxy/IRISProxy.log is opened. All server side log events will be written to this file.>
    <Mar 15, 2006 3:41:29 PM EST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Mar 15, 2006 3:41:29 PM EST> <Notice> <WebLogicServer> <BEA-000328> <Starting WebLogic Managed Server "IRISProxy" for domain "AppSvcDomain">
    <Mar 15, 2006 3:41:57 PM EST> <Warning> <HTTP> <BEA-101299> <The servlet-mapping for servlet-name "HttpClusterServlet" will override the default mapping for *.jsp. This can lead to a show code vulnerability.>
    <Mar 15, 2006 3:42:06 PM EST> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias irisqa from the jks keystore file /home/weblogic/bea_wli/weblogic81/server/lib/trustIdentityKeys/iris_qa.jks.>
    <Mar 15, 2006 3:42:06 PM EST> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias irisqa from the jks keystore file /home/weblogic/bea_wli/weblogic81/server/lib/trustIdentityKeys/iris_qa.jks.>
    <Mar 15, 2006 3:42:08 PM EST> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /home/weblogic/bea_wli/jdk141_05/jre/lib/security/cacerts.>
    <Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "IRISProxy" for domain "AppSvcDomain" running in Production Mode>
    <Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
    <Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 7001, ip address 170.63.142.29>
    <Mar 15, 2006 3:42:09 PM EST> <Notice> <WebLogicServer> <BEA-000355> <Thread "SSLListenThread.Default" listening on port 443, ip address 170.63.142.29>
    <Mar 15, 2006 5:02:26 PM EST> <Emergency> <WebLogicServer> <BEA-000209> <ListenThread.run() failed: java.lang.NoSuchMethodError: com.certicom.tls.interfaceimpl.TLSSystem.createServer(Ljavax/net/ssl/SSLSocket;Ljava/io/InputStream;Ljava/io/OutputStream;Ljava/io/Serializable;)Lcom/certicom/tls/TLSConnection;
    java.lang.NoSuchMethodError: com.certicom.tls.interfaceimpl.TLSSystem.createServer(Ljavax/net/ssl/SSLSocket;Ljava/io/InputStream;Ljava/io/OutputStream;Ljava/io/Serializable;)Lcom/certicom/tls/TLSConnection;
         at javax.net.ssl.impl.SSLSocketImpl.resetConnection(Unknown Source)
         at javax.net.ssl.impl.SSLServerSocketImpl.accept(Unknown Source)
         at weblogic.t3.srvr.ListenThread.accept(ListenThread.java:739)
         at weblogic.t3.srvr.ListenThread.run(ListenThread.java:292)
    >
    <Mar 15, 2006 5:02:26 PM EST> <Emergency> <WebLogicServer> <BEA-000210> <The WebLogic Server is no longer listening for connections.>
    <Mar 15, 2006 5:02:26 PM EST> <Alert> <WebLogicServer> <BEA-000218> <Server shutdown has been requested by <WLS Kernel>>
    <Mar 15, 2006 5:02:26 PM EST> <Notice> <WebLogicServer> <BEA-000353> <Thread "ListenThread.Default" stopped listening on port 7001, ip address 170.63.142.29>
    <Mar 15, 2006 5:02:26 PM EST> <Notice> <WebLogicServer> <BEA-000353> <Thread "SSLListenThread.Default" stopped listening on port 443, ip address 170.63.142.29>
    <Mar 15, 2006 5:02:26 PM EST> <Alert> <WebLogicServer> <BEA-000219> <The shutdown sequence has been initiated.>
    Can someone help me in solving this problem
    Thanks
    Kris

    I solved this problem by commenting the 8.1 SP4 patches i applied in 8.1 SP2
    WebLogic Temporary Patch for CR211812
    WebLogic Temporary Patch for CR235145
    Once i commented the above patches in the CLASSPATH.
    The issue is resolved.

  • Problem in using Weblogic 5.1

    hello friends,
    I have a Problem in Using Weblogic 5.1
    I am using weblogic 5.1 Enterprise on Linux 2.2.16 SuSE (7.0) with
    Dual Celeron 550MHz and 1GB RAM. The server runs our web application
    which uses the servelt, JSP and XSQL technology. The problem is
    that often i receive ASSERTION FAILURES where after the jsp's stop
    displaying content. Is this a Weblogic administration problem or
    the underlying OS problem. Kindly advice.
    Thankx in Advance
    Yajneesh sabharwal

    Is this an issue with the "T-engine" or the "J-engine"? Are you using a
    ubbconfig file or weblogic.properties file? Can you post the stack trace?
    This may be an known issue and simply require you to install the latest
    service pack for WLS 5.1 (aka. J-engine)...
    Mary Ann Slavin wrote:
    Accordning to the Software Product Information (SPI) for WLE 5.1 it is
    available on the following Linux versions so this could be a problem
    with the version you are running.
    "BEA WebLogic Enterprise 5.1 software for Red Hat Linux 6.2 and Reliant
    Unix 5.45 is available separately. "
    MAS
    yajneesh Sabharwal wrote:
    hello friends,
    I have a Problem in Using Weblogic 5.1
    I am using weblogic 5.1 Enterprise on Linux 2.2.16 SuSE (7.0) with
    Dual Celeron 550MHz and 1GB RAM. The server runs our web application
    which uses the servelt, JSP and XSQL technology. The problem is
    that often i receive ASSERTION FAILURES where after the jsp's stop
    displaying content. Is this a Weblogic administration problem or
    the underlying OS problem. Kindly advice.
    Thankx in Advance
    Yajneesh sabharwal

  • Error Connecting to Database using Weblogic Datasource

    Hi,
    I am trying to connect to oracle database from my program using weblogic DataSource. I am using JDK1.3.1.08 , weblogic 7.
    I am using the following code to get Connection object.
    contextFactory ="weblogic.jndi.WLInitialContextFactory";
    providerURL="t3://192.168.0.29:7001";
    dataSource ="temp_ds";
    if(contextFactory!=null)
    properties.put(Context.INITIAL_CONTEXT_FACTORY,contextFactory);
    if(providerURL !=null)
    properties.put(Context.PROVIDER_URL, providerURL);
    initCtx = new InitialContext(properties);
    DataSource ds= (javax.sql.DataSource) initCtx.lookup(dataSource);
    Connection con = ds.getConnection();
    con.setAutoCommit(false);
    I am getting the following error while running the program. Can any body help?
    javax.naming.CommunicationException. Root exception is weblogic.socket.Unrecove
    rableConnectException: [JDK 1.3 or higher required]
    at java.lang.Throwable.fillInStackTrace(Native Method)
    at java.lang.Throwable.fillInStackTrace(Compiled Code)
    at java.lang.Throwable.<init>(Compiled Code)
    at java.lang.Exception.<init>(Compiled Code)
    at java.io.IOException.<init>(IOException.java:47)
    at java.net.SocketException.<init>(SocketException.java:36)
    at java.net.ConnectException.<init>(ConnectException.java:34)
    at weblogic.socket.UnrecoverableConnectException.<init>(UnrecoverableCon
    nectException.java:19)
    at weblogic.rjvm.RJVMManager.checkVersion(RJVMManager.java:451)
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java
    :201)
    at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:191)
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:203)
    at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:169)
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:262)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(Compi
    led Code)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLIni
    tialContextFactoryDelegate.java:221)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialCont
    extFactory.java:149)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:671)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:242)
    at javax.naming.InitialContext.init(InitialContext.java:218)
    at javax.naming.InitialContext.<init>(InitialContext.java:194)
    at WeblogicTest.getConnection(WeblogicTest.java:40)
    at WeblogicTest.<init>(WeblogicTest.java:23)
    at WeblogicTest.main(WeblogicTest.java:18)
    at WeblogicTest.printTableData(Compiled Code)
    at WeblogicTest.<init>(WeblogicTest.java:24)
    at WeblogicTest.main(WeblogicTest.java:18)
    Regards
    Kumar

    I am not sure if this is the reason, but going thru the stack trace ...
    javax.naming.CommunicationException. Root exception is weblogic.socket.Unrecove
    rableConnectException: [JDK 1.3 or higher required]Make sure you have JDK 1.3 or higher installed.
    Cheers
    Sekar

  • I used this command and my user account is hidden sudo mv /Users/ed /Users/.ernestotaricone .

    i used this command and my user account is hidden and my account name ED
    sudo mv /Users/ed /Users/.ernestotaricone
    Please help me retrieve this Ed account back. Will there be any luck?
    When i checked the size of Users account the same gigabyte space is there but cannot see my user account ED

    This is the report the system gave me: CFPreferences: user home directory at file://localhost/Users/ernestotaricone/ is unavailable. User domains will be volatile.
    What of if i create another account say User account say good, can i transfer it back there?
    Seth

  • Problem using Weblogic 6 and Weblogic 8.1 thin clients from same applicatio

    We are developing a application where we require to communicate with 2 different ?Webogic Servers? running different versions.
    First server is ?Weblogic 6.1 SP7? and the other is ?Weblogic 8.1?. We use Weblogic thin client jars to connect to these servers. Protocol used to connect to ?Weblogic 8.1? is t3 and for ?Weblogic 6.1 SP7? its t3s. But the obvious problem is that both thin client can not be used simultaneously in the same class-path. Whichever jar file appears first in the class-path, classes will be loaded from that jar. This is causing breakage in our application. If we put ?Weblogic 6.1 SP7? thin client jar first in the path, our application throws exception while connecting to ?Weblogic 8.1? and if we put ?Weblogic 8.1? jar first the path, ?Weblogic 6.1 SP7? won?t connect. Is there a workaround to handle this problem. We have admin level access to Weblogic 8.1 which mean we can change the configuration here if required but we have only user level access to ?Weblogic 6.1 SP7? and can?t do any modification in server config.
    Exceptions:
    Case 1: ?Weblogic 6.1 SP7? thin client jar first in class-path.
    Result : connects successfully with ?Weblogic 6.1 SP7?.
         throws following exception while connecting to ?Weblogic 8.1?.
    weblogic.common.internal.VersioningError: Incompatible packages in CLASSPATH: (BEA Systems, WebLogic Server 6.1 SP7 08/30/2004 22:36:21 #428658 , 6.1.7.0) not compatible with (BEA Systems, WebLogic Server 8.1 SP3 Thu Jun 10 14:16:50 PDT 2004 396756 , 8.1.3.0)
         at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:118)
         at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
         at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
         at weblogic.kernel.Kernel.initialize(Kernel.java:138)
         at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:117)
         at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
         at java.lang.Class.newInstance0(Class.java:308)
         at java.lang.Class.newInstance(Class.java:261)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
         at javax.naming.InitialContext.init(InitialContext.java:219)
         at javax.naming.InitialContext.<init>(InitialContext.java:195)
         at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
         at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
         at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
    java.lang.InternalError: error initializing kernel
         at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:120)
         at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
         at java.lang.Class.newInstance0(Class.java:308)
         at java.lang.Class.newInstance(Class.java:261)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
         at javax.naming.InitialContext.init(InitialContext.java:219)
         at javax.naming.InitialContext.<init>(InitialContext.java:195)
         at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
         at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
         at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
    Case 2: ?Weblogic 8.1? thin client jar first in class-path.
    Result : connects successfully with ?Weblogic 8.1?.
         throws following exception while connecting to ?Weblogic 6.1 SP7?.
    avax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 203  completed: No]
    at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
    at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)
    at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)TRWLClientBinder.InitialContext NamingException try#: 0 attempt: -1 threadID: 31505976 message: javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 203  completed: No]
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
    at javax.naming.InitialContext.init(InitialContext.java:219)
    at javax.naming.InitialContext.<init>(InitialContext.java:195)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
    at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
    Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
    at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
    at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
    at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
    at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
    at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
    at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
    at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
    at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
    at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
    ... 16 more
    Couldn't connect to any host
    Cause: {1}
    javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 203  completed: No]
    at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
    at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)01/12|15:35:54.279|TRClientBinder.jndiBind TRConnectException, try#: 0 attempt: -1 Message: Couldn't connect to any host
    Cause: {1}
    at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
    at javax.naming.InitialContext.init(InitialContext.java:219)
    at javax.naming.InitialContext.<init>(InitialContext.java:195)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
    at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
    Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
    at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
    at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
    at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
    at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
    at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
    at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
    at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
    at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
    at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
    ... 16 more

    uday naik <> writes:
    The thin-client isn't supported on 6.1, I'm not sure what you are doing.
    andy
    We are developing a application where we require to communicate with 2 different ?Webogic Servers? running different versions.
    First server is ?Weblogic 6.1 SP7? and the other is ?Weblogic 8.1?. We use Weblogic thin client jars to connect to these servers. Protocol used to connect to ?Weblogic 8.1? is t3 and for ?Weblogic 6.1 SP7? its t3s. But the obvious problem is that both thin client can not be used simultaneously in the same class-path. Whichever jar file appears first in the class-path, classes will be loaded from that jar. This is causing breakage in our application. If we put ?Weblogic 6.1 SP7? thin client jar first in the path, our application throws exception while connecting to ?Weblogic 8.1? and if we put ?Weblogic 8.1? jar first the path, ?Weblogic 6.1 SP7? won?t connect. Is there a workaround to handle this problem. We have admin level access to Weblogic 8.1 which mean we can change the configuration here if required but we have only user level access to ?Weblogic 6.1 SP7? and can?t do any modification in server config.
    Exceptions:
    Case 1: ?Weblogic 6.1 SP7? thin client jar first in class-path.
    Result : connects successfully with ?Weblogic 6.1 SP7?.
         throws following exception while connecting to ?Weblogic 8.1?.
    weblogic.common.internal.VersioningError: Incompatible packages in CLASSPATH: (BEA Systems, WebLogic Server 6.1 SP7 08/30/2004 22:36:21 #428658 , 6.1.7.0) not compatible with (BEA Systems, WebLogic Server 8.1 SP3 Thu Jun 10 14:16:50 PDT 2004 396756 , 8.1.3.0)
         at weblogic.common.internal.VersionInfo.verifyPackages(VersionInfo.java:118)
         at weblogic.common.internal.VersionInfo.<init>(VersionInfo.java:60)
         at weblogic.common.internal.VersionInfo.initialize(VersionInfo.java:79)
         at weblogic.kernel.Kernel.initialize(Kernel.java:138)
         at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:117)
         at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
         at java.lang.Class.newInstance0(Class.java:308)
         at java.lang.Class.newInstance(Class.java:261)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
         at javax.naming.InitialContext.init(InitialContext.java:219)
         at javax.naming.InitialContext.<init>(InitialContext.java:195)
         at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
         at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
         at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
    java.lang.InternalError: error initializing kernel
         at weblogic.kernel.Kernel.ensureInitialized(Kernel.java:120)
         at weblogic.jndi.WLInitialContextFactoryDelegate.<init>(WLInitialContextFactoryDelegate.java:168)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
         at java.lang.Class.newInstance0(Class.java:308)
         at java.lang.Class.newInstance(Class.java:261)
         at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:147)
         at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
         at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
         at javax.naming.InitialContext.init(InitialContext.java:219)
         at javax.naming.InitialContext.<init>(InitialContext.java:195)
         at com.tpt.thresher.common.concurrent.DistributedProcessExceptionListener.connect(DistributedProcessExceptionListener.java:202)
         at com.tpt.thresher.common.concurrent.DistributedProcess.<init>(DistributedProcess.java:166)
         at com.tpt.thresher.common.concurrent.DistributedProcess.main(DistributedProcess.java:254)
    Case 2: ?Weblogic 8.1? thin client jar first in class-path.
    Result : connects successfully with ?Weblogic 8.1?.
         throws following exception while connecting to ?Weblogic 6.1 SP7?.
    avax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 203  completed: No]
    at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
    at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)
    at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)TRWLClientBinder.InitialContext NamingException try#: 0 attempt: -1 threadID: 31505976 message: javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 203  completed: No]
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
    at javax.naming.InitialContext.init(InitialContext.java:219)
    at javax.naming.InitialContext.<init>(InitialContext.java:195)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
    at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
    Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
    at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
    at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
    at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
    at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
    at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
    at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
    at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
    at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
    at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
    ... 16 more
    Couldn't connect to any host
    Cause: {1}
    javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE:   vmcid: SUN  minor code: 203  completed: No]
    at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:81)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:504)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:467)
    at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:97)01/12|15:35:54.279|TRClientBinder.jndiBind TRConnectException, try#: 0 attempt: -1 Message: Couldn't connect to any host
    Cause: {1}
    at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:42)
    at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
    at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)
    at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)
    at javax.naming.InitialContext.init(InitialContext.java:219)
    at javax.naming.InitialContext.<init>(InitialContext.java:195)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.getInitialContext(TRWLClientBinder.java:715)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:920)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientBinder.jndiBind(TRWLClientBinder.java:849)
    at com.cpex.trade.comm.TROrm.wl.TRWLClientMessenger.initBinding(TRWLClientMessenger.java:548)
    at com.cpex.trade.domain.TRSession.<init>(TRSession.java:237)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.<init>(ICEXChangeFeedController.java:113)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedController.getController(ICEXChangeFeedController.java:63)
    at com.oldlane.cxlfeeds.ICE.controller.ICEXChangeFeedProcessController.main(ICEXChangeFeedProcessController.java:150)
    Caused by: org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: No
    at com.sun.corba.se.internal.iiop.IIOPConnection.writeLock(IIOPConnection.java:562)
    at com.sun.corba.se.internal.iiop.BufferManagerWriteGrow.sendMessage(BufferManagerWriteGrow.java:55)
    at com.sun.corba.se.internal.iiop.IIOPOutputStream.finishSendingMessage(IIOPOutputStream.java:159)
    at com.sun.corba.se.internal.iiop.IIOPOutputStream.invoke(IIOPOutputStream.java:117)
    at com.sun.corba.se.internal.iiop.ClientRequestImpl.invoke(ClientRequestImpl.java:76)
    at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:235)
    at com.sun.corba.se.internal.corba.ClientDelegate.invoke(ClientDelegate.java:282)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolve(InitialNamingClient.java:1117)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolveUsingBootstrapProtocol(InitialNamingClient.java:788)
    at com.sun.corba.se.internal.corba.InitialNamingClient.cachedInitialReferences(InitialNamingClient.java:1186)
    at com.sun.corba.se.internal.corba.InitialNamingClient.resolve_initial_references(InitialNamingClient.java:1079)
    at com.sun.corba.se.internal.corba.ORB.resolve_initial_references(ORB.java:2436)
    at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:490)
    ... 16 more

  • Problem when using weblogic.jspc from an IDE

    I am trying to call JSPC from an IDE (as part of an Eclipse Builder). To optimize performance I want to avoid to spwan a new process. So I am trying to call weblogic.jspc's main method directly from the IDE. Everything works fine for simple simple pages.
              But when the page refers to a tag library with a tag providing a TagExtraInfo class, weblogic.jspc complains about the class not extending the TagExtraInfo base class although it does:
              Errors encountered while compiling 'D:\vrp-localdeploy\applications\wot\WOT' :
              Translation of /rentalcar/tiles/i18n/CarCapacityView.jsp failed: (line 17): Error in using tag library uri='/tags/i18n' prefix='i18n': For tag 'bundle', extra info class 'org.apache.taglibs.i18n.BundleTEI' does not extend javax.servlet.jsp.tagext.TagExtraInfo
              I could not figure out what exactly causes the problem. Using exactly the same settings workes just fine.
              Any suggestions?

    The full stack trace reads as follows:
              <p>
              Errors encountered while compiling 'D:\vrp-localdeploy\applications\wot\WOT' :
              <p>
              Translation of /common/include/i18n/definitions.inc failed: (line 17): Error in using tag library uri='/tags/i18n' prefix='i18n': For tag 'bundle', extra info class 'org.apache.taglibs.i18n.BundleTEI' does not extend javax.servlet.jsp.tagext.TagExtraInfo
              <br>
                   at weblogic.jspc.runJspc(jspc.java:559)
                   at weblogic.jspc.runBodyInternal(jspc.java:410)
                   at weblogic.jspc.runBody(jspc.java:319)
                   at weblogic.utils.compiler.Tool.run(Tool.java:146)
                   at weblogic.utils.compiler.Tool.run(Tool.java:103)
                   at weblogic.jspc.main(jspc.java:708)
                   at tui.vrp.tools.presentation.builder.PresentationBuilder.compileJSP(PresentationBuilder.java:1173)
                   at tui.vrp.tools.presentation.builder.PresentationBuilder.checkResource(PresentationBuilder.java:718)
                   at tui.vrp.tools.presentation.builder.PresentationBuilder$PresentationDeltaVisitor.visit(PresentationBuilder.java:102)
                   at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:68)
                   at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
                   at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
                   at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
                   at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
                   at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
                   at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:77)
                   at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:49)
                   at tui.vrp.tools.presentation.builder.PresentationBuilder.incrementalBuild(PresentationBuilder.java:1268)
                   at tui.vrp.tools.presentation.builder.PresentationBuilder.build(PresentationBuilder.java:677)
                   at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:593)
                   at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1044)
                   at org.eclipse.core.runtime.Platform.run(Platform.java:783)
                   at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:168)
                   at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:202)
                   at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:231)
                   at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1044)
                   at org.eclipse.core.runtime.Platform.run(Platform.java:783)
                   at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:234)
                   at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:253)
                   at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:282)
                   at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:139)
                   at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:200)
                   at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
              <p>
              Unfortunately it doesn't really give any real reason - it is a general piece of code in jspc to report problems.
              <p>
              But I dug a lot bit deeper into the code and realized that the original problem is a ClassCastException in line 1290 of class StandardTagLib, which reads as follows:
              <p>
                   tagextrainfo = (TagExtraInfo)Beans.instantiate(classloader, s3);
              <p>
              This looks quite obvious that the class named by s3 simply is no extension of TagExtraInfo, but unfortunately the only class with that name being referenced by the class path does extend this class. I wondered what the problem might be and came up with the following answer:
              <p>
              The class of the bean instantiated by Beans.instantiate extends a class with the name "javax.servlet.jsp.tagext.TagExtraInfo" which is cast to another class with exactly <b>the same name, but a different class loader</b>. Since neither of the class loaders is parent of the other one, both classes are not considered being the same class although they have the same name. Sounds weird, but exactly this is the problem!
              <p>
              Where does it come from and why it works fine when the tool is executed in a separate thread or on the console?
              <p>
              From my understanding the problem is caused in line 395 of the class weblogic.jspc:
              <p>
                   GenericClassLoader genericclassloader = new GenericClassLoader(classpathclassfinder);
              <p>
              This line of code creates a class loader not knowing a parent class loader by which the class weblogic.jspc was loaded. All classes weblogic.jspc is using or calling will be loader by either the same or a parent class loader - this is important to understand. Since TagExtraInfo is directly referenced by StandardTagLib one instance of the class object (the object of type class) will be generated and linked when the class StandardTagLib is instantiated for the first time by the class loader which loaded weblogic.jspc (or by its parent). This is consequence which can not be avoided.
              <p>
              But now look at line 1290 of class StandardTagLib: It explicitly requests the class to be loaded by the GenericClassLoader instantiated in line 395 of the class weblogic.jspc. This class loader, off course, is not aware of the same class just being loaded by another class loader since it has no knowledge of it. It simply creates a fresh copy of the class object, which only differs in the reference to the class loader which created this class object.
              <p>
              Actually, I figured that the following line of code replacing the upper one, would resolve the problem:
              <p>
              GenericClassLoader genericclassloader = new GenericClassLoader(classpathclassfinder, this.getClass().getClassLoader());
              <p>
              Doing this, the GenericClassLoader would know its logical parent by reference and would implicitly - thanks to the implementation of java.lang.ClassLoader - try to find the class using its parent first, would find a valid class, and hence use the same instance of the class object instantiated by the parent class loader. The problem would be solved.
              <p>
              It works fine in the console or under a running application server, because they will always have the weblogic jar in their system class path. ClassLoaders not having a parent are implied to have the system class loader as their parent - the piece of code does work in this case.
              <p>
              Under Eclipse this is no option, off course. We would restrain us to exactly this version of the APIs used by the weblogic version in the system class path.
              <p>
              I was trying to patch this myself by extending weblogic.jspc by my own class to pass on a proper class loader knowing its parent, and I was sort of successful: The problem disappeared. But I can't gain exactly what I am looking for, because the method runJspc with four parameters (around line 447) of weblogic.jspc is private to the class and its public brother always passes true to this method as the fourth parameter - causing jspc to recompile all JSPs instead of just the requested ones.
              <p>
              Everything refers to WL81SP3.
              <p>
              That's were I got stuck currently. I have read some postings about this problem in the internet - some dating far back into the history. So, I have the impression that there have been some folks around with the same problem. I think the patch I suggested does not any harm and I could simply use jspc in my builder without any problems.
              <p>
              Regards,
              <p>
              Elmar Schwarz

  • OraclePersistManager.updateBlobs() errors in using WebLogic DataSource

    CONFIGURATION
    Ap server: WebLogic 8.1
    Oracle database: 10g
    Oracle JDBC Driver: ojdbc14.jar, ojdbc14_g.jar, classes12.jar
    DESCRIPTION
    We have developed an application- V3- on top of ADF, and currently, we wanna deployed V3 from OC4J to WebLogic, and we used weblogic data source to access oracle database. The following Exception occurred in deployment to Weblogic.
    java.lang.ClassCastException: weblogic.jdbc.wrapper.Blob_oracle_sql_BLOB
         at oracle.jbo.pcoll.OraclePersistManager.updateBlobs(JI[Loracle.jbo.pcoll.PCollKeyInfo;[BILoracle.jdbc.OracleCallableStatement;)V(OraclePersistManager.java:1682)
         at oracle.jbo.pcoll.OraclePersistManager.insert(JJI[Loracle.jbo.pcoll.PCollKeyInfo;[B)V(OraclePersistManager.java:1832)
         at oracle.jbo.pcoll.PCollNode.passivateElem(Loracle.jbo.pcoll.PCollPersistable;Loracle.jbo.pcoll.PCollNode;Loracle.jbo.pcoll.PCollection;J)Z(PCollNode.java:561)
         at oracle.jbo.pcoll.PCollNode.passivate()Z(PCollNode.java:684)
         at oracle.jbo.pcoll.PCollNode.passivateBranch()Z(PCollNode.java:643)
         at oracle.jbo.pcoll.PCollection.passivate()J(PCollection.java:461)
         at oracle.jbo.server.DBSerializer.passivateRootAM(I[BI)I(DBSerializer.java:294)
         at oracle.jbo.server.DBSerializer.passivateRootAM([B)I(DBSerializer.java:267)
         at oracle.jbo.server.ApplicationModuleImpl.passivateStateInternal(I[BI)I(ApplicationModuleImpl.java:5123)
         at oracle.jbo.server.ApplicationModuleImpl.passivateState(I[BI)I(ApplicationModuleImpl.java:5011)
         at oracle.jbo.server.ApplicationModuleImpl.doPoolMessage(Loracle.jbo.ApplicationPoolSvcMsgContext;)Loracle.jbo.ApplicationPoolSvcMsgContext;(ApplicationModuleImpl.java:7741)
         at oracle.jbo.common.ampool.ApplicationPoolImpl.sendPoolMessage(Loracle.jbo.ApplicationPoolSvcMsgContext;Loracle.jbo.common.ampool.SessionCookie;Loracle.jbo.common.ampool.ApplicationPoolImpl$SessionCookieInfo;Loracle.jbo.ApplicationModule;Loracle.jbo.common.ampool.ApplicationPoolImpl$ApplicationModuleInfo;)V(ApplicationPoolImpl.java:3923)
         at oracle.jbo.common.ampool.ApplicationPoolImpl.doManagedCheckin(Loracle.jbo.common.ampool.SessionCookie;Z)V(ApplicationPoolImpl.java:2161)
         at oracle.jbo.common.ampool.ApplicationPoolImpl.releaseApplicationModule(Loracle.jbo.common.ampool.SessionCookie;I)V(ApplicationPoolImpl.java:1261)
         at oracle.jbo.common.ampool.SessionCookieImpl.releaseApplicationModule(IJ)V(SessionCookieImpl.java:717)
         at oracle.jbo.common.ampool.SessionCookieImpl.releaseApplicationModule(ZZJ)V(SessionCookieImpl.java:629)
         at oracle.jbo.common.ampool.SessionCookieImpl.releaseApplicationModule(ZZ)V(SessionCookieImpl.java:611)
         at oracle.cabo.data.jbo.servlet.RootAppModuleRegistryImpl$ReleaseRootAppModule.unbindValue()V(Unknown Source)
         at oracle.cabo.share.util.BindableNamespaceMap.unbindAll()V(Unknown Source)
         at oracle.cabo.servlet.BaseBajaContext.dispose()V(Unknown Source)
         at oracle.cabo.servlet.PageBrokerHandler.handleRequest(Loracle.cabo.servlet.BajaContext;)Loracle.cabo.servlet.Page;(Unknown Source)
         at oracle.cabo.servlet.UIXServlet.doGet(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(Unknown Source)
         at javax.servlet.http.HttpServlet.service(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(HttpServlet.java:853)
         at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run()Ljava.lang.Object;(ServletStubImpl.java:996)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;Lweblogic.servlet.internal.FilterChainImpl;)V(ServletStubImpl.java:419)
         at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(ServletStubImpl.java:315)
         at weblogc.servlet.internal.WebAppServletContext$ServletInvocationAction.run()Ljava.lang.Object;(WebAppServletContext.java:6452)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Lweblogic.security.subject.AbstractSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Obect;(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(Lweblogic.security.acl.internal.AuthenticatedSubject;Lweblogic.security.acl.internal.AuthenticatedSubject;Ljava.security.PrivilegedAction;)Ljava.lang.Object;(SecurityManager.java:118)
         at weblogic.servlet.internal.WebAppServletContext.invokeServlet(Lweblogic.servlet.internal.ServletRequestImpl;Lweblogic.servlet.internal.ServletResponseImpl;)V(WebAppServletContext.java:3661)
         at weblogic.servlet.internal.ServletRequestImpl.execute(Lweblogic.kernel.ExecuteThread;)V(ServletRequestImpl.java:2630)
    After decompiling class file of OraclePersistManager, it is because the following statement, which wanted to Cast returned object to Oracle.sql.BLOB.
    BLOB blob = (BLOB)oraclecallablestatement.getObject(j++);
    After searching the internet, the following url says it should be casted to weblogic.jdbc.vendor.oracle.OracleThinBlob.
    http://e-docs.bea.com/wls/docs81/jdbc/thirdparty.html#1043777
    oracle.jbo.pcoll.OraclePersistManager is the foundation class in ADF, of which code can NOT be revised. So, what should we do to resolve such error?? Please help to get it resolved ASAP, Thx for ur time...
    cheers
    Adam

    Hi. The problem is that in several places in Oracle JDBC extensions,
    they have methods that claim they take generic JDBC objects, such
    as java.sql.Blob, but they actually assume that the object is an
    Oracle driver object, and do such casts internally. WebLogic always
    generates a wrapper around JDBC objects so we can control transactions
    and prevent unintended multithreaded use of pooled connections.
    In this case, the only quick solution is to judiciously use our
    getVendorConnection() call and generate/obtain the actual Oracle
    blob object to pass to the OraclePersistenceManager. Do note though
    that this will initially mean that the pool connection will be closed and
    replaced at the end of the current invoke, to protect the pool. This is
    reconfigurable, but please read our docs.
    Joe Weinstein at BEA Systems

  • Exception while using weblogic datasource in ADF-BC app

    Hi,
    I want to use the weblogic datasource[JNDI name] as the datasource for my ADF BC application.
    I am following the "Configuring Your Application Module Database Connection" in the link
    http://download.oracle.com/docs/cd/E14571_01/web.1111/b31974/bcservices.htm#CHDJDBJB.
    I have done the following steps.
    1.Started weblogic server and configured a datasource[ex:testbcDS]
    2.In JDeveloper,navigated to 'Configuration' panel,edited the '**ModuleLocal' and changed the connection type to 'JDBC DataSource'.
    and Datasource Name to 'java:comp/env/jdbc/testbcDS'.
    3.In JDeveloper,wrote a stand alone Java client with the following snippet.
    public static void main(String[] args) {
    try {           
    String amDef = "oracle.communications.platform.bcapp.poc.app.AppModule";
    String config = "AppModuleLocal";
    ApplicationModule am = Configuration.createRootApplicationModule(amDef, config);
    ViewObject rscGroupVo = am.findViewObject("IfwRscGroupView1");
    rscGroupVo.executeQuery();
    4.On execution of this the following exception is being displayed in the console
    oracle.jbo.DMLException: JBO-27200: JNDI failure. Unable to lookup Data Source at context jdbc/testbcDS
    at oracle.jbo.server.DBTransactionImpl.lookupDataSource(DBTransactionImpl.java:1418)
    at oracle.jbo.server.DBTransactionImpl2.connectToDataSource(DBTransactionImpl2.java:309)
    Please let me know if I have followed correct steps and let me know the missing/wrongs steps I have done.
    The same works fine when the connection type is 'JDBC URL'.
    Please suggest.
    Thanks,
    Praveen

    Hi,
    After your suggestion I created weblogic data source with name as 'jdbc/testbcDS'
    and JNDI Name as 'jdbc/testbcDS'.
    Still I get the same error.
    oracle.jbo.DMLException: JBO-27200: JNDI failure. Unable to lookup Data Source at context jdbc/testbcDS
    at oracle.jbo.server.DBTransactionImpl.lookupDataSource(DBTransactionImpl.java:1418)
    Thanks,
    Praveen

  • Problems with using Captivate 7 behind Proxy

    Since I've upgraded to Adobe Captivate 7, I have issues while using Captivate. The program start takes very long and during working the program window sometimes freezes and then I have to wait about 15 Seconds before Captivate allows continuing my work, sometimes Captivate crashes completely. These issues are gone, when I'm disabling my network connection. I'm using Captivate inside a corporate network and behind firewall and proxy.
    I tested it also with a direct internet connection, no problems. So I'm missing some adresses which are filtered by the proxy. Does a list with necessary connections for Adobe Captivate 7 exist?

    It is well known that Captivate authors should ONLY work on project files that are stored and accessed from the computer's own hard drive.  If you are pulling down project files from your network LAN or saving back up to the LAN using Captivate then you will have these issues.  The use of virtual My Documents folders and roaming user profiles can also play havoc with Captivate's stability.
    You need to set up working folders on your C drive for your Captivate projects.  You'll need one for your Captivate Project Cache, one for your Captivate Publish folder, one for your Video Demo Recording Working Folder, and one for your Layouts and Themes.  All should be on your own hard drive, not the LAN or (if your IT dept uses virtualization or roaming user profiles) in your My Documents folder.
    Once your folders are created you can set these as the Default Locations in Preferences > General Settings > Default Locations and Preferences > Recording > Video Demo etc.
    Since it appears as if you have been working over the network up to this point, you may also find that you need to kill your Preferences folder as well after setting up the local default locations.  Otherwise Captivate will continue to look for the network addresses.

  • Can anyone help me what is the use of business and proxy service in osb?

    Hi,
    I am new in Osb what is the use of business service and proxy service in osb.
    I know little bit proxy service is used for actual message flow. I saw some project proxy service invoking the (using service callout,routing and publish) service,but the wsdl of the services of the proxy and business service is same.
    Please can anyone explain the flow while executing through soapUI?(that means it will hit 1st business services or proxy service)
    I have this project structure
    business service
    1.reference.biz----> this is the wsdl of ex:reference.wsdl
    2.external.biz----> this is the wsdl of ex:external.wsdl
    proxy service
    1.referece.proxy--->this is the wsdl of ex:reference.wsdl(in this proxy we are routing to reference.biz proxy service both contains same wsdls why?)
    xqueries of request and response.
    Best Regards,
    Raju.
    Edited by: 996674 on Apr 2, 2013 10:53 PM

    Hi Raju,
    Proxy Service - It is the starting point of you OSB application which deal with receiving messages, inducing logic in it like transformation, if-else, replace, java call outs,etc. You can put in your program logic here and then invoke a business service to route it to your Database or to any other queue as per your requirement.
    Business Service - It is generally used for routing purposes, like inserting the input in your Database or sending it to a different queue or BPEL process, etc..
    Cheers,
    Rit

  • Problem while using camera connetor and Sony DSC-M1

    Dear all
    My digital Camera Sony DSC-M1 is able to take pictures and take video into mpeg4 format .
    this is the revirew of this camera
    http://www.steves-digicams.com/2004_reviews/m1.html
    However, I got a problem while using this camera with iPod +Camera connector.
    When I plug this camera into camera connector , ipod will transfer all photo from the camera , but do nothing with the video.
    I guess that problem is the video file is not inside the "/DCIM" folder
    All video file ( *.mp4 ) are all in the folder named " /MP_ROOT/101MNV01/ "
    Can anyone help me how to make this sync from camera to ipod automatically both photo and video ?
    This problem also bother me while I am using iPhoto to transfer the file when I was home .
    pls , help me , thanks a lot

    Hi there, I'm having exactly the same problem. Have you found out how to do it?

  • Problem when using WEB.SHOW_DOCUMENT and passing in lexical parameter

    Hi,
    I got a blank page with error "An error has occured while trying to use this document" when I tried to use web.show_document and passing a lexical parameter to 10g report on 10gAS. The URL in the web.show_document is:
    http://<srvname>:<portnum>/reports/rwservlet?server=repserver90&report=myrpt.rdf&destype=Cache&desformat=pdf&userid=<usr>/<pw>@<db>&where_clause=where%20product_type%20in%20('REPORT')
    If I change the desformat to htmlcss, it is fine to display the report. But doesn't work with desformat=pdf. The pdf file has been generated in the cache. Why can't it display on the screen.
    Also I tried to use double quote the value for where_clause. The pdf report showed up. But it ignored the where clause.
    Experts please help.
    Ying

    I use lexical parameters and they work fine, but I use a parameter list. The code is contained in a form that is called by all forms that wish to run a report. This way you only need the logic for printing in a single form. If you want the form, email me at [email protected]

  • Quickviewer and Proxy user

    When a user with Proxy Access to a certain mailbox opens a forwarded (as attachment) message in this mailbox by using the Quickview Attachment Window and next tries to open the enclosed attachment the Groupwise Client gives a "c081" error, Missing BLOB file on add/modify. This only happens when the user with Proxy Access en the 'certain mailbox' exist on different PostOffices.
    When the same message is opened by the same Proxy user, but now from the Mailbox folder (and not via the Quickview) the forwarded message and attachment can be opened without any problem.
    Our Groupwise Agents and Clients are GW7sp3HotPatch4.
    Can anybody out there reproduce this at their Groupwise environment? Or even better, does someone have an idea about the cause and/or solution?
    Thanks in advance.

    keersen,
    It appears that in the past few days you have not received a response to your
    posting. That concerns us, and has triggered this automated reply.
    Has your problem been resolved? If not, you might try one of the following options:
    - Visit http://support.novell.com and search the knowledgebase and/or check all
    the other self support options and support programs available.
    - You could also try posting your message again. Make sure it is posted in the
    correct newsgroup. (http://forums.novell.com)
    Be sure to read the forum FAQ about what to expect in the way of responses:
    http://forums.novell.com/faq.php
    If this is a reply to a duplicate posting, please ignore and accept our apologies
    and rest assured we will issue a stern reprimand to our posting bot.
    Good luck!
    Your Novell Product Support Forums Team
    http://support.novell.com/forums/

  • [solved] Problem setting up a dedicated ssh proxy user

    I created a user which should only be able to create a ssh SOCKS tunel, with no shell access:
    username: proxy
    User ID: 1000 (or should it be 500?)
    shell: /bin/cat
    password: xxx
    group: users
    The problem is that when I try to ssh to it by
    ssh proxy@ip -vvv
    or set up a tunnel
    ssh proxy@ip -D 9999 -vvv
    I get asked for the password and when I give it, I get:
    debug2: we did not send a packet, disable method
    debug3: authmethod_lookup password
    debug3: remaining preferred: ,password
    debug3: authmethod_is_enabled password
    debug1: Next authentication method: password
    proxy@ip's password:
    debug3: packet_send2: adding 64 (len 58 padlen 6 extra_pad 64)
    debug2: we sent a password packet, wait for reply
    debug1: Authentications that can continue: publickey,password
    Permission denied, please try again.
    I am positive the password given is correct.
    Last edited by Lockheed (2014-06-20 10:05:15)

    Add /bin/cat to /etc/shells

Maybe you are looking for

  • HELP PLEASE !!! Can't get Linksys router to work.

    Okay, I am a new owner of an Alu-imac 2.4 ghz !!!!!! Installed Leopard last night and wanted to get my internet set up and --. IT DIDN'T WORK !!!!!!!! The Diagnostic thing wouldn't recognize my internet. (Info for you): 1) I have an Linksys wireless

  • Dump on execution of RFC HRXSS_PER_READ_P0006_US in ECC

    Hi I am just trying to execute one of FM that is used in case of country specific self service application. But I get following dump in the  backend. Strangely standard wd java also calls this FM without any dump. I also did check though extenal debu

  • Adobe Connect Desktop - just doesn't download recordings any more...

    Hi all, Has anyone had issues since the upgrade of this? I have made the recordings downloadable in all places thru the adobce connect admin area, but when using the desktop client evcewn though i am able to search for the file i am not however able

  • How application module helps for performance improve

    Hi Everyone, I have a sample web-application in which I am connecting with single AM instance (AM for database view object), retrieving some information and then close the connection. I am doing this as, // making AM instance <application module inst

  • Clearing up the subject of SkyDrive Pro once and for all

    Ok. So after reading many web pages, I get the point that 'SkyDrive Pro' is completely different to the consumer version of SkyDrive, and that the 'SkyDrive Pro' designation is really a fancy word for 'My Sites' within Sharepoint. I also understand t