Problems connecting weblogic 10.3 to mssql2005

Hello,
my job is to migrate an existing application from weblogic 6.5 to weblogic 10.3.
My Problem is the connection to MS SQL-Server 2005.
(My other problem is to be unexperienced in java and weblogic ;-) )
public void connect(String user, String passwd, String server, String database)
throws LetServerException {
log.getLog().debug("DBManager try to connect user:" + user + " server:" + server + " db:" + database);
if(dbConnection != null)
disconnect();
dbUser = user;
try {
java.util.Properties props = new java.util.Properties();
props.put("user", user);
props.put("password", passwd);
props.put("server", server);
//props.put("db", database); //weblogic 6.5
props.put("DatabaseName", database);          //weblogic 10.3
props.put("appname", "myapp");
try {
props.put("hostname", InetAddress.getByName(InetAddress.getLocalHost().getHostAddress()).getHostName());
} catch (Exception ex) {
// nothing
     //cc Class.forName("weblogic.jdbc.mssqlserver4.Driver"); // weblogic 6.5
//cc dbConnection = DriverManager.getConnection("jdbc:weblogic:mssqlserver4", props); // weblogic 6.5
     Class.forName("weblogic.jdbc.sqlserver.SQLServerDriver"); //weblogic 10.3
dbConnection = DriverManager.getConnection("jdbc:bea:sqlserver", props); //weblogic 10.3
pStatements = new StatementCache (dbConnection);
catch(Exception dbe) {
handleDBException(dbe);
After replacing the weblogic-jdbc-driver i get the runtime-exception:
"java.lang.StringIndexOutOfBoundsException: String index out of range: 0"
I think, that there is something wrong or missing with the parameters, but i can not find.
I hope, that there is anyone who can help me.
Thanks in advance
Christian

No.
I tried it to make some tests with the driver, but then i get:
"java.sql.SQLException: [BEA][SQLServer JDBC Driver]This driver is locked for use with embedded applications."

Similar Messages

  • Problem connecting weblogic 5.1 to AS400 DB2 version

    Hi All,
    I am having problem connecting from a weblogic server 5.1 version on win2000 machine to AS400 DB2 version using iToolbox jdbc driver "com.ibm.as400.access.AS400JDBCDriver".The following is the weblogic connectionpool :
    weblogic.jdbc.connectionPool.DBPool=\
    url=jdbc:as400://3.3.111.111/MySchema,\
    driver=com.ibm.as400.access.AS400JDBCDriver,\
    loginDelaySecs=10,\
    initialCapacity=1,\
    maxCapacity=10,\
    capacityIncrement=1,\
    allowShrinking=true,\
    shrinkPeriodMins=15,\
    refreshTestMinutes=10,\
    props=user=xxx;password=xxx
    weblogic.allow.reserve.weblogic.jdbc.connectionPool.DBPool=\
    everyone
    I am getting the following exception:
    Fri Jan 28 05:38:16 EST 2005:<E> <JDBC Pool> Failed to create connection pool "DBPool"
    weblogic.common.ResourceException: weblogic.common.ResourceException:
    Could not create pool connection. The DBMS driver exception was:
    java.lang.IllegalMonitorStateException: current thread not owner
         at com.ibm.as400.access.PortMapper.getServerSocket(PortMapper.java:150)
         at com.ibm.as400.access.AS400ImplRemote.signonConnect(AS400ImplRemote.java:1831)
         at com.ibm.as400.access.AS400ImplRemote.signon(AS400ImplRemote.java, Compiled Code)
         at com.ibm.as400.access.AS400.sendSignonRequest(AS400.java:2581)
         at com.ibm.as400.access.AS400.promptSignon(AS400.java, Compiled Code)
         at com.ibm.as400.access.AS400.signon(AS400.java:3375)
         at com.ibm.as400.access.AS400.connectService(AS400.java:821)
         at com.ibm.as400.access.AS400JDBCConnection.setProperties(AS400JDBCConnection.java:2764)
         at com.ibm.as400.access.AS400JDBCDriver.prepareConnection(AS400JDBCDriver.java:1040)
         at com.ibm.as400.access.AS400JDBCDriver.initializeConnection(AS400JDBCDriver.java, Compiled Code)
         at com.ibm.as400.access.AS400JDBCDriver.connect(AS400JDBCDriver.java:355)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:146)
         at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:108)
         at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java, Compiled Code)
         at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java, Compiled Code)
         at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:330)
         at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java, Compiled Code)
         at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:255)
         at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11)
         at java.lang.reflect.Method.invoke(Native Method)
         at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219)
         at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java, Compiled Code)
         at weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)
    Can anyone let me know is there any problem with connection pool configuration or do i have to make any configuration changes on DB2.Why is it throwing current thread not a owner.
    Pl help.

    Hi Joe,
    Can i use jdk1.3.1 version with weblogic 5.1 version to get rid of this problem or will this change in jvm will effect my existing production applications?
    -thanks
    bharani
    Hi Joe,
    Yes the same code put into jsp scriplet is also
    throwing the error
    "java.lang.IllegalMonitorStateException: current
    thread not owner".It would be really wonderfull if
    you can get some info on the stacktrace.The version
    of jdk we are using is jdk1.2.2, is the problem
    anyway related with the jdk version as the standalone
    program i have tested ran on jdk1.3.1 and jdk1.4
    versions.
    Thanking you in advance,
    -bharani
    bharani noudu wrote:
    Hi Joe,
    Thanks for the quick reply.As per your suggestion
    i
    am able to run a simple 15 line
    standalone program with jdk versions of jdk1.3.1and jdk1.4.1 and jt400.jar in the
    classpath, but i am not able to use the sameconfiguration details in the connection
    pool created in weblogic or the same code pasted
    in
    JSP.Both are throwing the exception
    that "current thread is not a owner".Is thisanything related with the web container
    implementation of weblogic 5.1 or the jdk
    version
    of weblogic 5.1 ?
    Can you please help.I am pasting the code i usedbelow for your reference.
    Hi. If you can put this code in a JSP it throwsthe
    "current thread" exception?
    Even if there's no pool?
    I would contact IBM or post to their newsgroups to
    explain the stacktrace.
    The Driver.connect() call just takes a URL and
    properties (user and password).
    There's nothing a user could do to cause such a
    problem.
    java.lang.IllegalMonitorStateException: current
    thread not owner
    at
    com.ibm.as400.access.PortMapper.getServerSocket(PortMa
    pper.java:150)
    at
    com.ibm.as400.access.AS400ImplRemote.signonConnect(AS4
    00ImplRemote.java:1831)
    at
    com.ibm.as400.access.AS400ImplRemote.signon(AS400ImplR
    emote.java, Compiled Code)
    at
    com.ibm.as400.access.AS400.sendSignonRequest(AS400.jav
    a:2581)
    at
    com.ibm.as400.access.AS400.promptSignon(AS400.java,
    Compiled Code)
    atcom.ibm.as400.access.AS400.signon(AS400.java:3375)
    at
    com.ibm.as400.access.AS400.connectService(AS400.java:8
    21)
    at
    com.ibm.as400.access.AS400JDBCConnection.setProperties
    (AS400JDBCConnection.java:2764)
    at
    com.ibm.as400.access.AS400JDBCDriver.prepareConnection
    (AS400JDBCDriver.java:1040)
    at
    com.ibm.as400.access.AS400JDBCDriver.initializeConnect
    ion(AS400JDBCDriver.java, Compiled Code)
    at
    com.ibm.as400.access.AS400JDBCDriver.connect(AS400JDBC
    Driver.java:355)
    import java.sql.Connection;
    import java.sql.DriverManager;
    import java.sql.ResultSet;
    import java.sql.SQLException;
    import java.sql.Statement;
    public class TestDb2 {
         public static void main(String[] args) {
         Connection connection = null;
         try{               
         DriverManager.registerDriver(newcom.ibm.as400.access.AS400JDBCDriver());          
              connection = DriverManager.getConnection
    ("jdbc:as400://1.11.111.1/MySchema","test","test");
              System.out.println("step 1");          
              Statement st = connection.createStatement();          
              System.out.println("step 2");
              ResultSet rs = st.executeQuery("SELECT * FROMMYDB.EMPLOYEE_V");
              while(rs.next()){
                   System.out.println("empid "+rs.getString(1));
              }catch(Exception e){
                   System.out.println("step 3"+e);
                   e.printStackTrace();
              finally{
                   if(connection!=null){
                        try {
                             connection.close();
                        } catch (SQLException e1) {
         e1.printStackTrace();
    Thanking you in advance,
    -bharani
    Hi. That's a very odd internal IBM driver error.
    It's
    mesage is not helpful, and can't be due to
    anything
    you or WebLogic did. Can you get that driver wowork
    on it's own, using it's own example programs? If
    you can get a simple 15-line program to succeed
    making
    a connection, then we can get WebLogic to do the
    same.
    Show me that program and I'll show you the pool
    definition.
    Joe
    bharani noudu wrote:
    Hi All,
    I am having problem connecting from a weblogicserver 5.1 version on win2000 machine to AS400
    DB2
    version using iToolbox jdbc driver
    "com.ibm.as400.access.AS400JDBCDriver".Thefollowing
    is the weblogic connectionpool :
    weblogic.jdbc.connectionPool.DBPool=\
    url=jdbc:as400://3.3.111.111/MySchema,\
    driver=com.ibm.as400.access.AS400JDBCDriver,\
    loginDelaySecs=10,\
    initialCapacity=1,\
    maxCapacity=10,\
    capacityIncrement=1,\
    allowShrinking=true,\
    shrinkPeriodMins=15,\
    refreshTestMinutes=10,\
    props=user=xxx;password=xxx
    weblogic.allow.reserve.weblogic.jdbc.connectionPool.
    DB
    Pool=\
    everyone
    I am getting the following exception:
    Fri Jan 28 05:38:16 EST 2005:<E> <JDBC Pool>
    Failed
    to create connection pool "DBPool"
    weblogic.common.ResourceException:weblogic.common.ResourceException:
    Could not create pool connection. The DBMS
    driver
    exception was:
    java.lang.IllegalMonitorStateException: currentthread not owner
         at
    com.ibm.as400.access.PortMapper.getServerSocket(Port
    Ma
    pper.java:150)
         at
    com.ibm.as400.access.AS400ImplRemote.signonConnect(A
    S4
    00ImplRemote.java:1831)
         at
    com.ibm.as400.access.AS400ImplRemote.signon(AS400Imp
    lR
    emote.java, Compiled Code)
         at
    com.ibm.as400.access.AS400.sendSignonRequest(AS400.j
    av
    a:2581)
         at
    com.ibm.as400.access.AS400.promptSignon(AS400.java,
    Compiled Code)
         at
    com.ibm.as400.access.AS400.signon(AS400.java:3375)
         at
    com.ibm.as400.access.AS400.connectService(AS400.java
    :8
    21)
         at
    com.ibm.as400.access.AS400JDBCConnection.setProperti
    es
    (AS400JDBCConnection.java:2764)
         at
    com.ibm.as400.access.AS400JDBCDriver.prepareConnecti
    on
    (AS400JDBCDriver.java:1040)
         at
    com.ibm.as400.access.AS400JDBCDriver.initializeConne
    ct
    ion(AS400JDBCDriver.java, Compiled Code)
         at
    com.ibm.as400.access.AS400JDBCDriver.connect(AS400JD
    BC
    Driver.java:355)
         at
    weblogic.jdbc.common.internal.ConnectionEnvFactory.m
    ak
    eConnection(ConnectionEnvFactory.java:146)
         at
    weblogic.jdbc.common.internal.ConnectionEnvFactory.c
    re
    ateResource(ConnectionEnvFactory.java:108)
         at
    weblogic.common.internal.ResourceAllocator.makeResou
    rc
    es(ResourceAllocator.java, Compiled Code)
         at
    weblogic.common.internal.ResourceAllocator.<init>(Re
    so
    urceAllocator.java, Compiled Code)
         at
    weblogic.jdbc.common.internal.ConnectionPool.startup
    (C
    onnectionPool.java:330)
         at
    weblogic.jdbc.common.internal.JdbcInfo.initPools(Jdb
    cI
    nfo.java, Compiled Code)
         at
    weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcI
    nf
    o.java:255)
         at
    weblogic.jdbc.common.internal.JdbcStartup.main(JdbcS
    ta
    rtup.java:11)
         at java.lang.reflect.Method.invoke(Native
    Method)
         at
    weblogic.t3.srvr.StartupThread.runMain(StartupThread
    .j
    ava:219)
         at
    weblogic.t3.srvr.StartupThread.doWork(StartupThread.
    ja
    va, Compiled Code)
         at
    weblogic.t3.srvr.PropertyExecuteThread.run(PropertyE
    xe
    cuteThread.java:62)
    Can anyone let me know is there any problem
    with
    connection pool configuration or do i have tomake
    any configuration changes on DB2.Why is itthrowing
    current thread not a owner.
    Pl help.

  • Problem connecting weblogic server to cluster

              Hi,
              I am very new to WL/JMS/JNDI/EJB etc. I downloaded WL6.0, and tried to make a cluster. I started a server on one machine as Administrative server, and created a cluster. Now, I started another server on a different machine, as a managed server by adding the following parameter at startup
              -Dweblogic.admin.host=http://admin-ipaddr:7001....,
              I get the following error
              Starting WebLogic Server ....
              <Thu Oct 19 14:37:37 PDT 2000> <Error> <Configuration Management> <Error connecting to admin server to bootstrap via URL: http://admin-ipaddr:7001/Bootstrap, user: system
              weblogic.management.configuration.ConfigurationException: Connection error: java.lang.SecurityException: Authentication for user system
              denied in realm weblogic
              at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:752)
              at weblogic.management.Admin.initialize(Admin.java:275)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:345)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
              at weblogic.Server.main(Server.java:32)
              >
              <Thu Oct 19 14:37:37 PDT 2000> <Emergency> <Server> <Unable to initialize the server: Fatal initialization exception
              Throwable: weblogic.management.configuration.ConfigurationException: connecting to http://admin-ipaddr:7001/Bootstrap - with nested exception:
              [weblogic.management.configuration.ConfigurationException: Connection error: java.lang.SecurityException: Authentication for user system denied in realm weblogic]
              weblogic.management.configuration.ConfigurationException: connecting to http://admin-ipaddr:7001/Bootstrap - with nested exception:
              [weblogic.management.configuration.ConfigurationException: Connection error: java.lang.SecurityException: Authentication for user syste
              m denied in realm weblogic]
              at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:803)
              at weblogic.management.Admin.initialize(Admin.java:275)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:345)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
              at weblogic.Server.main(Server.java:32)
              >
              I understand that all managed servers are supposed to use the same config file as the Admin server.
              Also, I am not clear about the domain parameter.... what should I pass for -Dweblogic.Domain=mydomain (this is what is there in the batch file that comes). Should I change this parameter for Managed servers, which points to Admin domain? If so, how do I do that?
              I am struck up on this. I'd greatly appreciate it some body could help me out.
              thanks a lot,
              Anil.
              

    -Dweblogic.admin.host=admin-ipaddr:7001, you shouldn't specify protocol. Also please use beta newsgroup for 6.0 related questions.
              anil wrote:
              > Hi,
              > I am very new to WL/JMS/JNDI/EJB etc. I downloaded WL6.0, and tried to make a cluster. I started a server on one machine as Administrative server, and created a cluster. Now, I started another server on a different machine, as a managed server by adding the following parameter at startup
              > -Dweblogic.admin.host=http://admin-ipaddr:7001....,
              >
              > I get the following error
              > Starting WebLogic Server ....
              > <Thu Oct 19 14:37:37 PDT 2000> <Error> <Configuration Management> <Error connecting to admin server to bootstrap via URL: http://admin-ipaddr:7001/Bootstrap, user: system
              > weblogic.management.configuration.ConfigurationException: Connection error: java.lang.SecurityException: Authentication for user system
              > denied in realm weblogic
              > at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:752)
              > at weblogic.management.Admin.initialize(Admin.java:275)
              > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:345)
              > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
              > at weblogic.Server.main(Server.java:32)
              > >
              > <Thu Oct 19 14:37:37 PDT 2000> <Emergency> <Server> <Unable to initialize the server: Fatal initialization exception
              > Throwable: weblogic.management.configuration.ConfigurationException: connecting to http://admin-ipaddr:7001/Bootstrap - with nested exception:
              > [weblogic.management.configuration.ConfigurationException: Connection error: java.lang.SecurityException: Authentication for user system denied in realm weblogic]
              > weblogic.management.configuration.ConfigurationException: connecting to http://admin-ipaddr:7001/Bootstrap - with nested exception:
              > [weblogic.management.configuration.ConfigurationException: Connection error: java.lang.SecurityException: Authentication for user syste
              > m denied in realm weblogic]
              > at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:803)
              > at weblogic.management.Admin.initialize(Admin.java:275)
              > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:345)
              > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:160)
              > at weblogic.Server.main(Server.java:32)
              > >
              > ***************************************************************************
              > I understand that all managed servers are supposed to use the same config file as the Admin server.
              >
              > Also, I am not clear about the domain parameter.... what should I pass for -Dweblogic.Domain=mydomain (this is what is there in the batch file that comes). Should I change this parameter for Managed servers, which points to Admin domain? If so, how do I do that?
              >
              > I am struck up on this. I'd greatly appreciate it some body could help me out.
              >
              > thanks a lot,
              > Anil.
              

  • Problem connecting weblogic OSB with IBM websphere via foreign JMS

    Hi All,
    I am trying to setup Foreign JMS. My configuration doesn’t work.
    Could you please let me know if I am missing anything .
    All my configuration details are done as specified in this link http://www.oracle.com/technology/products/integration/service-bus/docs/osb-websphere-whitepaper.pdf
    Here is what I did.
    In OSB sbconsole
    OSB business Service ENDPoint URL jms://webspherehost:9082/sampleQueuemanager/sampleQueue
    In websphere
    Created a queue connection factory and a queue from the webspehere administrator console.
    Modified JSMAdmin.config to enable the following…/Java/bin/JMSAdmin.config.
    INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
    PROVIDER_URL=file:/C:/JNDI-Directory
    Ran JSMAdmin.bat to bind the JNDI
    def qcf(sampleQueuemanager) qmanager(QMGR) HOSTNAME(webspherehost) PORT(1327) TRANSPORT(CLIENT)
    def Q(sampleQueue) queue(sampleQueue) qmanager(QMGR) PERSISTENCE(PERS)
    InitCtx> dis ctx
    JMSADM4089 InitCtx
    .bindings java.io.File
    bck_.bindings java.io.File
    a sampleQueuemanager com.ibm.mq.jms.MQQueueConnectionFactory
    a sampleQueue com.ibm.mq.jms.MQQueue
    4 Object(s)
    0 Context(s)
    4 Binding(s), 2 Administered
    In weblogic admin console
    Created foreign JMS, destination and connection factory as mentioned in the following link.
    http://download.oracle.com/docs/cd/E12840_01/wls/docs103/ConsoleHelp/taskhelp/jms_modules/foreign_servers/CreateForeignConnectionFactories.html
    When I execute business service from OSB sbconsole, this is what I get.
    +The invocation resulted in an error: [JMSPool:169803]JNDI lookup of the JMS connection factory sampleQueuemanager failed: javax.naming.CommunicationException [Root exception is weblogic.socket.UnrecoverableConnectException: [Login failed for an unknown reason: HTTP/1.1 400 Bad Request]].+
    Thanks
    siva

    Little confusing. Are we not supposed to use osb host name and port along with foreign connection factory created in weblogic for OSB BS?.
    You said: jms://webspherehost:9082/sampleQueuemanager/sampleQueue
    We have to jms://osbhost:port/ForeignQueueManagerInWeblogic/ForeignQueueInWeblogic
    Manoj

  • Problems with weblogic clustering in 6.1 sp3

    We have spent a lot of time trying to get our application deployed to
              a cluster using weblogic 6.1 sp3 and we consistently receive a failure
              when we attempt to start the managed server. This was not a problem
              with weblogic sp1--we got our application to deploy to the cluster
              successfully; although there was another weblogic bug there with
              clients accessing EJB clusters--we won't go into that here...
              We have tried this on both a Windows 2000 machine and an HP machine
              running weblogic sp3. The same error occurs on both platforms.
              The error in deploying our application to the cluster against weblogic
              sp3 looks to have to do with our custom security realm. Inside our
              custom realm we make use of a configurable providerUrl which we set to
              the cluster address/port. The custom realm makes a call where it
              passes in the providerUrl to:
                   weblogic.management.Helper.getMBeanHome(..., providerUrl,...)
              When we have our providerUrl set to the cluster address/port--e.g.,
                   t3://clustermember1:7001
              and attempt to start the managed server we get the error:
              Starting WebLogic Server ....
              Connecting to http://adminserver:7117...
              The WebLogic Server did not start up properly.
              Exception raised:
              weblogic.management.configuration.ConfigurationException:
              clustermember1 not found
                   at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1084)
                   at weblogic.management.Admin.initialize(Admin.java:340)
                   at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
                   at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
                   at weblogic.Server.main(Server.java:35)
              Reason: Fatal initialization exception
              When we have our providerUrl set to the admin server address--e.g.,
                   t3://adminserver:7117
              everything starts up fine.
              Does anyone know why this would work on sp1 and not sp3 of weblogic
              6.1?
              We verified that all passwords are correct and everything else we
              could determine--any ideas would be helpful.
              We don't want the providerUrl to point at our admin server, we want it
              to point at the cluster address/port.
              When we get the managed server error, we received this error on the
              AdminServer:
              2002-08-15 16:52:23,019 ERROR [ExecuteThread: '11' for queue:
              'default'] (com.msa.gabriel.share.security.wlrealm.GabrielRealm) -
              Caught naming exception null; throwing RuntimeException.
              javax.naming.CommunicationException. Root exception is
              java.net.ConnectException: t3://tomtate.msais.com:7119: Destination
              unreachable; nested exception is:
                   java.net.ConnectException: Connection refused; No available router to
              destination
                   at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
                   at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
                   at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:307)
                   at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:211)
                   at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:149)
                   at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:665)
                   at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
                   at javax.naming.InitialContext.init(InitialContext.java:222)
                   at javax.naming.InitialContext.<init>(InitialContext.java:198)
                   at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getNamingContext(GabrielRealm.java:416)
                   at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getConnection(GabrielRealm.java:347)
                   at com.msa.gabriel.share.security.wlrealm.GabrielRealm.access$000(GabrielRealm.java:51)
                   at com.msa.gabriel.share.security.wlrealm.GabrielRealm$2.run(GabrielRealm.java:225)
                   at weblogic.security.acl.Security.doAsPrivileged(Security.java:489)
                   at com.msa.gabriel.share.security.wlrealm.GabrielRealm.myDoAsPrivileged(GabrielRealm.java:578)
                   at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.java:221)
                   at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
                   at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
                   at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
                   at weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.java:356)
                   at weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(ServletSecurityManager.java:205)
                   at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2518)
                   at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2260)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              <Aug 15, 2002 4:52:23 PM EDT> <Error> <HTTP>
              <[WebAppServletContext(8091823,wl_management_internal2,/wl_management_internal2)]
              Servlet failed with Exception
              java.lang.RuntimeException
                   at com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.java:260)
                   at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
                   at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
                   at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
                   at weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.java:356)
                   at weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(ServletSecurityManager.java:205)
                   at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2518)
                   at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2260)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              Thanks for any help.
              Rich
              

    Bottom line:
              In our custom realm we were not handling user guest correctly. Even if you
              have guest user disabled, Weblogic seems to have hard-coded guest to
              send messages to the cluster every-so-often. Not sure there--couldn't get
              an answer out of bea as to exactly why we see guest still being used...
              It seems that with sp3, the user guest interaction started happening earlier
              than it did with sp1, consequently making our realm code fail when trying to
              retrieve the guest user like someone we knew about in our system.
              Hence, our getUser and authUserPassword methods now return null for both
              users guest and system, making the secondary realm (file realm) be used to
              authenticate and resolve guest & system. BEA helped get our code fixed;
              however, we still don't have a lot of depth in understanding Weblogic
              server's use of guest...
              Apparently, in 7.x the guest & system user behavior and configuration is
              different also... We'll see when we start digging into that migration.
              Rich
              [email protected] (Rich Koch) wrote in message news:<[email protected]>...
              > Thanks for the responses--we're working with weblogic support now. We
              > think that the custom realm that we have [the developer that wrote it
              > left the company] is the problem.
              >
              > The original developer was told by someone to check:
              > weblogic.security.acl.internal.ClusterRealm.THE_ONE != null
              >
              > In order to determine if the JNDI was available/ready for the whole
              > cluster.
              >
              > It seems that the meaning/setting of THE_ONE changed with this respect
              > from
              > sp1 to sp3--i.e., this is no longer a valid test to tell us if the
              > JNDI is
              > ready for the cluster.
              >
              > We believe this was used because the 'system' user has to be
              > authenticated before the custom realm is up. Originally, before this
              > check was in place, an exception was received when authenticating
              > 'system'. This appears to be a weblogic limitation/issue. Support
              > has told us that this is different in weblogic 7.0. Unfortunately, we
              > can't upgrade from 6.1 yet.
              >
              > We'll post the solution when this gets figured out.
              >
              > Rak
              >
              > "Sabha" <[email protected]> wrote in message news:<[email protected]>...
              > > There was a security restriction enforced from sp2/sp3 onwards in terms of
              > > looking up mbeans from admin server.
              > >
              > > This might cause things to fail if you are attempting to lookup Mbeans with
              > > guest priviliges from admin server. Also, can you try doing the following:
              > >
              > > Run " java weblogic.Admin -url adminServer -username system -password
              > > .... -GET -pretty -type Server" and check whether the named clustermember1
              > > is available in the list or not.
              > >
              > > Also you seem to be getting some security exception - can you check that.
              > >
              > > t3://tomtate.msais.com:7119: Destination
              > > unreachable; nested exception is:
              > >
              > > --- Try running weblogic.Admin PING on this one and see whether you are
              > > able to reach this server upon the error message.
              > >
              > > --Sabha
              > >
              > > "Rich Koch" <[email protected]> wrote in message
              > > news:[email protected]...
              > > > We have spent a lot of time trying to get our application deployed to
              > > > a cluster using weblogic 6.1 sp3 and we consistently receive a failure
              > > > when we attempt to start the managed server. This was not a problem
              > > > with weblogic sp1--we got our application to deploy to the cluster
              > > > successfully; although there was another weblogic bug there with
              > > > clients accessing EJB clusters--we won't go into that here...
              > > >
              > > > We have tried this on both a Windows 2000 machine and an HP machine
              > > > running weblogic sp3. The same error occurs on both platforms.
              > > >
              > > > The error in deploying our application to the cluster against weblogic
              > > > sp3 looks to have to do with our custom security realm. Inside our
              > > > custom realm we make use of a configurable providerUrl which we set to
              > > > the cluster address/port. The custom realm makes a call where it
              > > > passes in the providerUrl to:
              > > > weblogic.management.Helper.getMBeanHome(..., providerUrl,...)
              > > >
              > > > When we have our providerUrl set to the cluster address/port--e.g.,
              > > > t3://clustermember1:7001
              > > >
              > > > and attempt to start the managed server we get the error:
              > > >
              > > > Starting WebLogic Server ....
              > > > Connecting to http://adminserver:7117...
              > > >
              > ***************************************************************************
              > > > The WebLogic Server did not start up properly.
              > > > Exception raised:
              > > > weblogic.management.configuration.ConfigurationException:
              > > > clustermember1 not found
              > > > at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1084)
              > > > at weblogic.management.Admin.initialize(Admin.java:340)
              > > > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
              > > > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:206)
              > > > at weblogic.Server.main(Server.java:35)
              > > > Reason: Fatal initialization exception
              > > >
              > ***************************************************************************
              > > >
              > > > When we have our providerUrl set to the admin server address--e.g.,
              > > > t3://adminserver:7117
              > > >
              > > > everything starts up fine.
              > > >
              > > > Does anyone know why this would work on sp1 and not sp3 of weblogic
              > > > 6.1?
              > > > We verified that all passwords are correct and everything else we
              > > > could determine--any ideas would be helpful.
              > > >
              > > > We don't want the providerUrl to point at our admin server, we want it
              > > > to point at the cluster address/port.
              > > >
              > > > When we get the managed server error, we received this error on the
              > > > AdminServer:
              > > >
              > > > 2002-08-15 16:52:23,019 ERROR [ExecuteThread: '11' for queue:
              > > > 'default'] (com.msa.gabriel.share.security.wlrealm.GabrielRealm) -
              > > > Caught naming exception null; throwing RuntimeException.
              > > > javax.naming.CommunicationException. Root exception is
              > > > java.net.ConnectException: t3://tomtate.msais.com:7119: Destination
              > > > unreachable; nested exception is:
              > > > java.net.ConnectException: Connection refused; No available router to
              > > > destination
              > > > at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:155)
              > > > at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:207)
              > > > at
              > > weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
              > > textFactoryDelegate.java:307)
              > > > at
              > > weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
              > > textFactoryDelegate.java:211)
              > > > at
              > > weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFact
              > > ory.java:149)
              > > > at
              > javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:665)
              > > > at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:246)
              > > > at javax.naming.InitialContext.init(InitialContext.java:222)
              > > > at javax.naming.InitialContext.<init>(InitialContext.java:198)
              > > > at
              > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getNamingContext(Gabriel
              > > Realm.java:416)
              > > > at
              > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getConnection(GabrielRea
              > > lm.java:347)
              > > > at
              > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.access$000(GabrielRealm.
              > > java:51)
              > > > at
              > > com.msa.gabriel.share.security.wlrealm.GabrielRealm$2.run(GabrielRealm.java:
              > > 225)
              > > > at weblogic.security.acl.Security.doAsPrivileged(Security.java:489)
              > > > at
              > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.myDoAsPrivileged(Gabriel
              > > Realm.java:578)
              > > > at
              > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.jav
              > > a:221)
              > > > at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
              > > > at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
              > > > at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
              > > > at
              > > weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.j
              > > ava:356)
              > > > at
              > > weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Servle
              > > tSecurityManager.java:205)
              > > > at
              > > weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
              > > ntext.java:2518)
              > > > at
              > weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
              > > :2260)
              > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > > > <Aug 15, 2002 4:52:23 PM EDT> <Error> <HTTP>
              > > >
              > > <[WebAppServletContext(8091823,wl_management_internal2,/wl_management_intern
              > > al2)]
              > > > Servlet failed with Exception
              > > > java.lang.RuntimeException
              > > > at
              > > com.msa.gabriel.share.security.wlrealm.GabrielRealm.getUser(GabrielRealm.jav
              > > a:260)
              > > > at weblogic.security.acl.CachingRealm.getUserEntry(CachingRealm.java:832)
              > > > at weblogic.security.acl.CachingRealm.getUser(CachingRealm.java:696)
              > > > at weblogic.security.acl.Security.getCurrentUser(Security.java:250)
              > > > at
              > > weblogic.servlet.security.internal.SecurityModule.auditPerm(SecurityModule.j
              > > ava:356)
              > > > at
              > > weblogic.servlet.security.internal.ServletSecurityManager.checkAccess(Servle
              > > tSecurityManager.java:205)
              > > > at
              > > weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletCo
              > > ntext.java:2518)
              > > > at
              > weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java
              > > :2260)
              > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > > >
              > > >
              > > > Thanks for any help.
              > > >
              > > > Rich
              

  • Help Connecting Weblogic to Oracle.

    Hello,
    We are encountering some error to connect weblogic at start up to
    oracle 8i on a Solaris box. I have attached an error log file for the
    same. The Error is something to do with ORA-24327.
    The Fact is I am able to connect to oracle from NT Weblogic server,
    NT SQL, SVRMGRL . But when I try to connect to oracle from Solaris
    WebLogic I get this Error.
    Thanks in advance for the help.
    [weblogic.log]

    According to our jdbc engineer:
    ORA-24327 ("need explicit attach before authenticating a user")
    First, this is not one of our error codes. Its one of OCI's many ways of telling you it
    could not connect for some unknown reason. Unfortunately, this generally doesn't help
    solve the problem. Currently, I'm aware of
    two things that might cause this problem:
    1. Oracle client DLL/SO is not compatable with Oracle server or Oracle client
    installation. The former is a limitation of oracle that we can't do anything about.
    The latter often implies an installation problem or conflict with some other installed
    software. For example, some Oracle applications will install the OCI DLL in your path
    (most
    often in the windows system directory), thinking that its being helpful.
    Unfortunately, if your ORACLE_HOME is pointing to a different version of oracle, this
    will screw you. So if you get this error, one thing to check whether you have an old
    version of OCI (OCI.DLL and/or OCIW32.dll) somewhere in your path.
    2. More recently, I've learned that this error can also occur if your tnsnames.ora
    does not have a reference to the service you are trying to access.
    Hope this helps
    --Kumar
    Sheshadri Yagati wrote:
    Hello,
    We are encountering some error to connect weblogic at start up to
    oracle 8i on a Solaris box. I have attached an error log file for the
    same. The Error is something to do with ORA-24327.
    The Fact is I am able to connect to oracle from NT Weblogic server,
    NT SQL, SVRMGRL . But when I try to connect to oracle from Solaris
    WebLogic I get this Error.
    Thanks in advance for the help.
    Name: weblogic.log
    weblogic.log Type: Text Document (application/x-unknown-content-type-txtfile)
    Encoding: base64

  • Problem using WebLogic Scripting Tool

    Hi,
    I'm new to weblogic. I tried to deploy WAR file to weblogic(installed on my PC) using WLST. I got the following error message.
    Problem invoking WLST - Traceback (innermost last):
    [exec] File "C:\TutorialHome\CDB\buildfiles\localhost.py", line 7, in ?
    [exec] File "<iostream>", line 354, in activate
    [exec] WLSTException: 'Error occured while performing activate : Error while Activating changes. Use dumpStack() to view the full stacktrace'
    [exec] <Apr 21, 2009 1:24:43 PM EDT> <Warning> *<JNDI> <BEA-050001> <WLContext.close() was called in a different thread than the one in which it was created.>*
    Here is my hostlocal.py:
    connect('weblogic','weblogic','t3://localhost:7001')
    stopApplication('cdb')
    edit()
    startEdit()
    progress=redeploy('cdb')
    save()
    activate()
    startApplication('cdb')
    disconnect()
    exit()
    So How can I solve the problem of "<BEA-050001> <WLContext.close() was called in a different thread than the one in which it was created.>"?
    Thanks in advance.
    Sarah

    Check the blend modes for the brush tool in the tool options bar.
    Also if your painting on a blank layer check the blend modes in the layers panel.
    Either way try the Normal mode.
    MTSTUNER

  • How to connect weblogic 8.1 to IBM MQ Series from remote machines?

    Hi,
              I am trying to connect WebLogic 8.1 to IBM MQ Series 6.0 both are running in a seperate machines.Can we do using JNDI services? Can anyone help me to fix this issue?

    I'm cutting/pasting my notes on the topic, including MQ specific notes. Start with the Integrating Remote JMS Providers FAQ (link below). You can also search this newsgroup for answers.
              Tom
              JMS Integration of Foreign Vendors with BEA WebLogic Server
              The following notes are derived mostly from "http://dev2dev.bea.com/technologies/jms/index.jsp".
              For additional questions, a good forum for WebLogic questions in general is "newsgroups.bea.com". These can be mined for information by using Google's newsgroup search function.
              JMS Integration Overview
              - For integration with "non-Java" and/or "non-JMS" platforms, see "Non-Java Integration Options" below.
              - For a foreign JMS vendor to participate in a WL transaction it must support XA. Specifically, it must support the javax.jms.XA* interfaces.
              - In WL versions 6.0 and up it is possible to make synchronous calls to foreign JMS vendors participate in a WL transaction as long as the foreign vendor supports XA.
              - WL 6.0 and 6.1 MDBs can be driven by foreign vendors non-transactionally. They can be driven transactionally by a select few foreign vendors (MQ is not part of the select few)
              - WL 7.0 and later, MDBs can be driven by foreign vendors transactionally and non-transationally.
              - WL 6.1 and later WL provides a messaging bridge feature. Messaging bridges forward messages between any two JMS destinations, including foreign destinations, and can transfer messages transactionally or non-transactionally.
              - WL 8.1 JMS provides additional features that simplify transactional and JNDI integration of foreign vendors. See http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features and http://e-docs.bea.com/wls/docs81/faq/interop.html
              Integration with 8.1 Details
              To start, first read the "Integrating Remote JMS Providers FAQ" (released in Dec 2004) at:
              http://e-docs.bea.com/wls/docs81/faq/interop.html
              A good overview of 8.1 JMS interop capability is the presentation "Integrating Foreign JMS Providers with BEA WebLogic Server" here:
              http://www.bea.com/content/files/eworld/presentations/Wed_03_05_03/Application_Servers/1097-Foreign_JMS_Providers_WLS.pdf
              This document refers to helpful new 8.1 features, which simplify integration. These include:
              http://edocs.bea.com/wls/docs81/ConsoleHelp/jms_config.html#accessing_foreign_providers
              http://edocs.bea.com/wls/docs81/jms/j2ee_components.html#1033768
              And are also summarized here (under interoperability):
              http://edocs.bea.com/wls/docs81/jms/intro.html#jms_features
              Also read the MDB documentation, which extensively covers integrating foreign vendors:
              http://edocs.bea.com/wls/docs81/ejb/message_beans.html
              The 8.1 features are likely sufficient for most 8.1 integration needs, but you may want to refer to the "Using Foreign JMS Providers With WLS" white-paper mentioned below, which is 7.0 specific but contains specific examples of configuring non-WebLogic JMS vendors. See also notes on "MQ" below.
              Integration with 6.1 and 7.0 Details
              Read the "Using Foreign JMS Providers With WLS" white-paper:
              http://dev2dev.bea.com/products/wlserver/whitepapers/jmsproviders.jsp
              Note that this white-paper does not take into account 8.1 features.
              For 7.0 read the extensive 8.1 MDB documentation, which largely also applies to 7.0:
              http://edocs.bea.com/wls/docs81/ejb/message_beans.html
              Non-Java Integration Options
              - WL JMS has a JNI based C client which is available for Windows and some UNIX platforms. This C client supports 7.0 and up, and will be officially packaged with WLS in 9.0 (virtually unchanged). The C API is currently only supported through the jms newsgroup. See "JMS C API", here:
              http://dev2dev.bea.com/technologies/jms/index.jsp
              - WL supports direct Windows COM access through its "JCOM" feature. This doesn't include the JMS API, but one can invoke EJBs which in turn invoke JMS. See
              http://e-docs.bea.com/wls/docs61/jcom.html
              http://e-docs.bea.com/wls/docs70/jcom/
              http://e-docs.bea.com/wls/docs81/jcom/
              - Similar to JCOM, but more advanced and supported on more platforms, WL supports access via the standard IIOP protocol. You can use the BEA Tuxedo C client for this purpose (no license fee). This doesn't include the JMS API, but one can invoke EJBs which in turn invoke JMS. See
              http://e-docs.bea.com/wls/docs81/rmi_iiop/
              http://e-docs.bea.com/wls/docs70/rmi_iiop/
              http://e-docs.bea.com/wls/docs61/rmi_iiop/
              Unlike most other approaches, the IIOP client approach also allows the client to begin and commit user (JTA) transactions (not configured).
              - If you already have a BEA Tuxedo license, one option is communicate through BEA Tuxedo (which has various APIs on Windows) and configure a WebLogic Server to respond to these requests via the WTC bridge. Search for "WTC" in the BEA docs. Unlike most other approaches, the Tuxedo API approach also allows the client to begin and commit user (JTA) transactions.
              - Another approach is to interop via web-service standards. Or even to simply to invoke a servlet on the WL server using a basic HTTP call from the client. These operation in turn can invoke the JMS API. There is a white-paper on "Interoperability Study of BEA WebLogic Workshop 8.1 and Microsoft .NET 1.1 Web Services", that demonstrates web-services here:
              http://ftpna2.bea.com/pub/downloads/WebLogic-DotNet-Interop.pdf
              - Yet another approach is to use a third party product that is designed to wrap any JMS vendor. There are even open source versions. In no particular order, here are some examples: Open3 WinJMS, CodeMesh, Active JMS, SpiritSoft
              - Finally, there are .NET/C/C++ integration libraries that are not specific to JMS, some examples are JNBridge, Jace, and CodeMesh.
              Notes on MQ Remote Capable XA Clients
              Until recently, IBM MQ JMS clients could not work transactionally unless they were running on the same host as their MQ server. This is a limitation unique to MQ that was relaxed with the introduction of IBM's new "WebSphere MQ Extended Transactional Client". See:
              http://publibfp.boulder.ibm.com/epubs/pdf/csqzar00.pdf
              The product is new, and for some reason, configuration of this client seems to be tricky, even when WebLogic is not involved at all. Oddly, the main sticking point seems to be simply making sure that class paths refer to the required IBM jars:
              - Required on WLS where MQ objects are bound into JNDI:
              com.ibm.mq.jar, com.ibm.mqjms.jar
              - Required only if MQ objects are bound into JNDI on a different server:
              com.ibm.mq.jar
              If there are problems when using this client, first get it to work using a pure IBM client without any BEA classes involved. Once that is working, search the WL JMS newsgroup for answers and/or contact BEA customer support.
              Notes on Oracle AQ Integration
              If problems are encountered integrating Oracle's built-in queuing (Oracle AQ) JMS client, there is publicly available wrapper code that can aid integrating AQ directly into MDBs, JMS, or the messaging bridge. The solution is titled "Startup class to bind AQ/Referenceable objects to WLS JNDI", is not supported by BEA, and is posted to:
              http://dev2dev.bea.com/codelibrary/code/startupclass.jsp (older version)
              http://xa-compliant-oracleaq.projects.dev2dev.bea.com (newer version)
              Caveats:
              It may be that the solution doesn't directly support concurrent consumers. Perhaps Oracle requires that concurrent consumers each have a unique JMS connection? As a work-around, parallel message processing can be achieved indirectly by forwarding AQ messages into a WL JMS destination - which do support concurrent processing.
              Up-to-date versions of Oracle may be required. For more information, google search the weblogic.developer.interest.jms newsgroup for "Oracle" and "AQ".
              MDB Thread Pool Notes
              WL7.0SP? and WL8.1 and later support the "dispatch-policy" field to specify which thread pool an MDB uses to run its instances. In most cases this field should be configured to help address potential performance issues and/or dead-locks:
              http://edocs.bea.com/wls/docs81/ejb/DDreference-ejb-jar.html#dispatch-policy
              (Note that "dispatch-policy" is ignored for non-transactional foreign vendors; in this case, the MDB "onMessage" callback runs in the foreign vendor's thread.)
              MDB Concurrency Notes
              Queue MDBs driven by foreign providers can run multiple instances concurrently. Topic MDBs driven by foreign providers are limited to one instance (not sure, but transactional foreign driven topic MDBs may not have this limitation). The size of the thread pool that the MDB runs in and the "max-beans-in-free-pool" descriptor limit how many instances run concurrently.
              Design Guide-Lines and Performance Tuning Notes
              The "WebLogic JMS Performance Guide" white-paper contains detailed design, performance, and tuning information for Clustering, Messaging Bridge, JMS, and MDBs.
              http://dev2dev.bea.com/products/wlserver/whitepapers/WL_JMS_Perform_GD.jsp

  • Portal Drive - Connection Problems (a problem connecting user) 2

    Hello Experts,
    I installed the latest Portal-Drive from
    [SWDC|https://websmp230.sap-ag.de/sap/bc/bsp/spn/download_basket/download.htm?objid=012002523100000835972009D]
    and followed step-by-step explanations from
    [http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/2541]
    So I created a new-service and filled fields as follows:
    Service Name: PW1
    Server URL: http://r3ebwpdb.ekostahl.agn:50000/irj/go/km/docs/documents/Hilfe
    Username: TLI399958 (That is my SAP-User)
    Server-Url (...) looks like:
    Server: r3ebwpdb.ekostahl.agn
    Port: 50000
    Server directory: irj\go\km\docs\documents\Hilfe
    Unfortunatley the connection does not work --- message:
    r3ebwpdb.ekostahl.agn is currently experiencing a problem connecting user. Please try again later.
    I read in other threats, that the URL should work in a Browser-window - unfunatley I receive the following message:
         Portal-Laufzeitfehler
    Ausnahme bei der Verarbeitung des Requests; senden Sie die ID der Ausnahme an Ihren Portaladministrator
    Ausnahme-ID 01:08_03/03/11_0039_8263550
    Weitere Details zu dieser Ausnahme finden Sie in der entsprechenden Protokolldatei
    My log-files "pw1.log" shows:
    SAP NetWeaver Portal Drive 4.5 (build 7651) on WinVista
    Service: WebDAV:
    r3ebwpdb.ekostahl.agn:50000\irj\go\km\docs\documents\Hilfe
    Sharing Level: 2
    Secure connection: No
    13:12:29 2011/03/03 Failed to connect
      Error 0000003A.
    13:12:30 2011/03/03 dirlist timeout=300, flags=4
    I checked also:
    1.
    [SAP-Help|http://help.sap.com/saphelp_nw04s/helpdata/en/42/c99b91341a6bade10000000a1553f6/frameset.htm]
    2.
    Tried several things with PROXY on Portal-Drive-App.
    3.
    Tried several things with Tab Advanced / User authentification  on Portal-Drive-App.
    Systemlandscape:
    OS: UNIX
    Portal: EP 7.00 SP20
    Thanks for your help...
    Regards,
    Thomas

    Hello Mikhail,
    I tried to logon again, because my last try was at 03.03.2011.
    I got the following-log-files:
    1. pw1.log
    2. PW1.http.0.log
    3. PW1.http.1.log
    4. PW1.http.2.log
    5. PW1.http.log
    Content of 1
    SAP NetWeaver Portal Drive 4.5 (build 7651) on WinVista
    Service: WebDAV:\\r3ebwpdb.ekostahl.agn:50000\irj\go\km\docs\documents\Hilfe
    Sharing Level: 2
    Secure connection: No
    16:12:12 2011/03/24 Failed to connect
      Error 0000003A.
    16:12:14 2011/03/24 dirlist timeout=300, flags=4

  • Portal Drive - Connection Problems (a problem connecting user)

    Hello Experts,
    I installed the latest Portal-Drive from
    [SWDC|https://websmp230.sap-ag.de/sap/bc/bsp/spn/download_basket/download.htm?objid=012002523100000835972009D]
    and followed step-by-step explanations from
    [http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/2541]
    So I created a new-service and filled fields as follows:
    Service Name: PW1
    Server URL: http://r3ebwpdb.ekostahl.agn:50000/irj/go/km/docs/documents/Hilfe
    Username: TLI399958 (That is my SAP-User)
    Server-Url (...) looks like:
    Server: r3ebwpdb.ekostahl.agn
    Port: 50000
    Server directory: irj\go\km\docs\documents\Hilfe
    Unfortunatley the connection does not work --- message:
    r3ebwpdb.ekostahl.agn is currently experiencing a problem connecting user. Please try again later.
    I read in other threats, that the URL should work in a Browser-window - unfunatley I receive the following message:
         Portal-Laufzeitfehler
    Ausnahme bei der Verarbeitung des Requests; senden Sie die ID der Ausnahme an Ihren Portaladministrator
    Ausnahme-ID 01:08_03/03/11_0039_8263550
    Weitere Details zu dieser Ausnahme finden Sie in der entsprechenden Protokolldatei
    My log-files "pw1.log" shows:
    SAP NetWeaver Portal Drive 4.5 (build 7651) on WinVista
    Service: WebDAV:
    r3ebwpdb.ekostahl.agn:50000\irj\go\km\docs\documents\Hilfe
    Sharing Level: 2
    Secure connection: No
    13:12:29 2011/03/03 Failed to connect
      Error 0000003A.
    13:12:30 2011/03/03 dirlist timeout=300, flags=4
    I checked also:
    1.
    [SAP-Help|http://help.sap.com/saphelp_nw04s/helpdata/en/42/c99b91341a6bade10000000a1553f6/frameset.htm]
    2.
    Tried several things with PROXY on Portal-Drive-App.
    3.
    Tried several things with Tab Advanced / User authentification  on Portal-Drive-App.
    Systemlandscape:
    OS: UNIX
    Portal: EP 7.00 SP20
    Thanks for your help...
    Regards,
    Thomas

    Hello Mikhail,
    I tried to logon again, because my last try was at 03.03.2011.
    I got the following-log-files:
    1. pw1.log
    2. PW1.http.0.log
    3. PW1.http.1.log
    4. PW1.http.2.log
    5. PW1.http.log
    Content of 1
    SAP NetWeaver Portal Drive 4.5 (build 7651) on WinVista
    Service: WebDAV:\\r3ebwpdb.ekostahl.agn:50000\irj\go\km\docs\documents\Hilfe
    Sharing Level: 2
    Secure connection: No
    16:12:12 2011/03/24 Failed to connect
      Error 0000003A.
    16:12:14 2011/03/24 dirlist timeout=300, flags=4

  • I'm trying to set up my Ipod, but when I go to sign in with an apple ID it says 'Could not sign in: there was a problem connecting to the server'.

    I just bought a 3rd generation ipod touch. It was professionally refurbished. I'm trying to set it up, and everything seems to be working fine, until we get to the wifi. I live on campus and our wifi is username and password protected. I signed in and everything seemed to work fine, and in the top left hand corner I have all the bars for wifi. However, when I go to sign in with an apple ID it says 'Could no sign in: there was a problem connecting to the server'. I've tried turning it on and off again, tried signing on to our wifi again, but it all isn't working. What can I do?

    I also encountered the same problem. Try using a different email address or try signing in later.

  • I am having problems connecting to home wifi.  It was working, but now all I get is a blank white screen.  I re-booted with no success.

    I am having problems connecting to home wifi.  It was working, but now all I get is a blank white screen.  I re-booted with no success.

    Hi, blank white screen where exactly?
    Make a New Location, Using network locations in Mac OS X ...
    http://support.apple.com/kb/HT2712
    10.5, 10.6, 10.7 & 10.8…
    System Preferences>Network, top of window>Locations>Edit Locations, little plus icon, give it a name.
    10.5.x/10.6.x/10.7.x/10.8.x instructions...
    System Preferences>Network, click on the little gear at the bottom next to the + & - icons, (unlock lock first if locked), choose Set Service Order.
    The interface that connects to the Internet should be dragged to the top of the list.
    If using Wifi/Airport...
    Instead of joining your Network from the list, click the WiFi icon at the top, and click join other network. Fill in everything as needed.
    For 10.5/10.6/10.7/10.8, System Preferences>Network, unlock the lock if need be, highlight the Interface you use to connect to Internet, click on the advanced button, click on the DNS tab, click on the little plus icon, then add these numbers...
    208.67.222.222
    208.67.220.220
    (There may be better or faster DNS numbers in your area, but these should be a good test).
    Click OK.

  • Problems connecting multiple macs to an Airport Extreme network.

    I think this problem is similar to a previous post, but is individual in some ways.
    I have 2 Airport Extreme basestations covering a large flat connected by Ethernet extending a single network. I did try to extend the network wirelessly, but this was plagued with problems where the network would work for 10 mins, then drop out as I think the basestations are slightly too far apart.
    Connected to the network are a number of machines:
    Wirelessly we have 3x iPhones, 1x G4 Cube, 1x iMac (current model), 2x MacBook Pro (previous model) & 1x PC.
    Wired via a hub is an Apple TV, PS3, Nintendo Wii, Denon Home Cinema Amp, PS2
    For aprox 6 months I have had major problems connecting all the wireless machines at the same time. I have played around with the security as per previous posts with varying degrees of success.
    I seem to have the most problems with the iMac. The iMac will not join the network when there is any form of wireless security. Every time I try to set up a password it hangs when trying to join and I finally get the "There was a error joining xxxx network".
    After more playing around I managed to get all the machines working by having no security on the network and locking the network down by MAC addresses.
    Since last Thursday I now have a new problem. The iMac joins and stays on the network perfectly, but the second my second MacBook Pro is switched on and joins the network, the internet connection on the iMac drops out. In addition, as we use the iMac as a media server, all other machines connected to the iMac for either file sharing or iTunes sharing then get the error "the remote machine is failing to respond. Please check firewall settings if there are any". What is strange is that the iMac remains on the network, full signal, independent IP address and the second the MacBook Pro is switched off, works perfectly again.
    I have tried wiping both the iMac & the MacBook Pro and re-installing their operating systems, but this only solves the problem for aprox 24 hours then all of a sudden the issue re-appears.
    Can anyone out there help?

    Let's double-check the AirPort Express Base Station's (AX) settings ...
    Perform a "factory default" reset of the AX
    o (ref: http://docs.info.apple.com/article.html?artnum=108044)
    Either connect to the AX's wireless network or connect directly, using an Ethernet cable, to the Ethernet port of the AX, and then using the AirPort Utility in "Manual Setup" mode, check the following settings:
    AirPort > Base Station
    o Base Station Name: <rename or leave default>
    o Base Station Password: <enter desired password>
    o Verify Password: <re-enter desired password>
    o Remember this password in my keychain: (optional)
    o Set time automatically: (unchecked)
    AirPort > Wireless
    o Wireless Mode: Join a wireless network
    o Network Name: <existing AEBSn's wireless network>
    o Wireless Security: <select the encryption type of the existing wireless network>
    o Wireless Password: <enter the existing wireless network password>
    o Verify Password: <re-enter the existing wireless network password>
    Music
    o Enable AirTunes (checked)
    o iTunes Speaker Name: <enter desired speaker name>
    o iTunes Speaker Password: (optional)
    o Verify Password: (optional)
    o Click Update to write the new settings to the AX
    In iTunes:
    iTunes > Preferences... > Advanced > General
    o Look for remote speakers connected with AirTunes (checked)

  • TS3048 My early 2009 Mac Pro does not connect via bluetooth to my sound bar or bluetooth mini speakers. Both my wireless keyboard and mouse have no problems connecting. What do I need to do to connect to external bluetooth devices?

    My early 2009 Mac Pro does not connect via bluetooth to my sound bar or bluetooth mini speakers. Both my wireless keyboard and mouse have no problems connecting. What do I need to do to connect to external bluetooth devices?

    I would always have a wired keyboard and mouse on hand (need not be expensive ... any cheap wired devices will work).  "Emergency recovery" procedures can activate features in random order, so the opportunity to select a recovery partition may pass before the wireless devices are recognized.
    That will let you select the "turn on Bluetooth" icon.

  • Problem connecting MacBook to a Sharp video projector

    One of the great things I like about Macs is the easy way they (usually) connect to a video projector. Unlike a lot of my friends who run PCs with Windows I never had any problems whatsoever connecting my MacBook to a projector at the university and start my presentations.
    Until today that is.
    I tried to connect my MacBook with Apple's mini-DVI to VGA adapter to a Sharp ("Notevision") video projector and although the MacBook had the projector (even with its correct name "PG-M20X" and available resolution settings) listed under "Displays" immediately, I couldn't get the projector to show any more than "no signal" whatever input source I chose...
    What did I do wrong? Or is it the projector that is somehow "incompatible"?! Please help!
    MacBook Mac OS X (10.4.9) Core Duo 2GHz, July 2006
    MacBook   Mac OS X (10.4.9)   Core Duo 2GHz, July 2006

    Maybe this could help as well:
    After we tried several things with the MacBook (reboot, "detect displays" etc.), we successfully connected a Powerbook (15", FireWire 800, late 2003) to the projector, using Apple's DVI-VGA Adapter.
    So that did work out fine, but the MacBook didn't work on the projector. The cable that came with the projector was a VGA--DVI-A cable: there were only a few pins on the DVI-end of it going into the DVI-Connector on the projector. Could it have something to do with that? But why didn't the Powerbook have any problems connecting to the projector then?
    MacBook Mac OS X (10.4.9) Core Duo 2GHz, July 2006

Maybe you are looking for

  • Capturing from my HDR FX7

    Thank you Tom I just already solve my problem trashing Adolfo

  • IWeb not publishing edited "top" and "bottom" page backgrounds

    I have edited the page background for the "Layered Paper" theme to fit an 800px space (up from 700px). The backgrounds display correctly in iWeb, but in Safari, only the middle image is the correct 800px format. The top and bottom both display the ol

  • I do not want firefox to block any websites

    Firefox give me the message "This Connection is Untrusted You have asked Firefox to connect securely to mofb.hexify.biz, but we can't confirm that your connection is secure. Normally, when you try to connect securely, sites will present trusted ident

  • How do I move files onto a G4 with OSX 10.3.9?

    Brethren, I just gave my G4 Quicksilver to my fiancee and she is having trouble moving her laptop files onto it. She has a bunch of MP3's (songs you'd puke if you had to listen to) and jpegs (billions of them) but no streamlined way of moving the dat

  • Another wrong amount sainsburys gift card

    I too have been sent a £50 gift card instead of the stated £125 for taking their infinity offer, used the online chat procedure 3 times,every time they have forwarded the transcript to the gift card dept yet 12 days later,still no response.Tried phon