JDBC Type 3 driver problem with WLS 6.1 SP4

We have Oracle 8.1.7.4 client running on WebLogic 6.1 SP4 on Solaris 2.6 connecting to Oracle OPS 8.1.7 running on Solaris 2.6. We are getting core dumps while running stress testing using Load Runner for 100 concurrent users. The performance is very good for a while in the beginning of the test and all of a sudden we see requests for connections queueing up on the WLS and the server crashes. Please send us details of any previous instances any one faced similar problem and the fix applied will be very helpful.
Regards,
Raj

The Member Feedback forum is for suggestions and feedback for OTN Developer Services. This forum is not monitored by Oracle support or product teams and so Oracle product and technology related questions cannot be answered. We recommend that you post this thread to the SQLJ/JDBC forum.
The URL is: http://forums.oracle.com/forums/forum.jsp?forum=99
Thanks, OTN Team

Similar Messages

  • Oracle XA driver problem with WLS 7.0.1.0, Oracle 9.0.1

    We are using simplified chinese, after swith to bea jdriver, it messed up
    all the encoding. So we cannot display Chinese character correctly.
    We are using WLS 7.0.1.0, Oracle 9.0.1 on both Windows and Solaris 8
    environment, BEA supplied JDK 1.3.1_03.
    We have many diffrent problems with oracle drivers:
    1. We want to use XA driver to support distributed transaction, However:
    * bea jdriver xa messes up with encoding
    * when using oracle 901 driver, everything works fince except webservices.
    Workshop application access the ejb, then the workshp application sets
    isolation level, but oracle driver does not support it and gives error. Is
    there a way to turn off isolation level in workshop? I tried manually edit
    weblogic-ejb-jar.xml, however,workshop cannot redeploy it after that.
    2. When not using XA, oracle thin driver works fine. But we lost XA
    capability.
    Any work around?

    I did try to change the value in this config file as well, but did not help.
    In fact, the installation default setting is with
    '<transaction-isolation-level>' commented out.
    And when I use bea oracle jdriver, it somehow messed up with database
    character set encoding, so our Chinese characters could not be retrieved
    correctly. And I try to set the encoding of jdriver to 'GBK', it did not
    work.
    "Anurag Pareek" <[email protected]> дÈëÏûÏ¢ÐÂÎÅ
    :[email protected]..
    Hello Ma,
    The transaction isolation level value for EJBs backing the JWS files is
    specified in the <transaction-isolation-level> tag in the
    WEB-INF/weblogic-jws-config.xml file of a Workshop project. You can
    manipulate this value to serve your purpose.
    Please do let me know how it goes.
    Regards,
    Anurag
    Workshop Support
    "Ma Jie" <[email protected]> wrote in message
    news:[email protected]..
    We are using simplified chinese, after swith to bea jdriver, it messed
    up
    all the encoding. So we cannot display Chinese character correctly.
    We are using WLS 7.0.1.0, Oracle 9.0.1 on both Windows and Solaris 8
    environment, BEA supplied JDK 1.3.1_03.
    We have many diffrent problems with oracle drivers:
    1. We want to use XA driver to support distributed transaction, However:
    * bea jdriver xa messes up with encoding
    * when using oracle 901 driver, everything works fince exceptwebservices.
    Workshop application access the ejb, then the workshp application sets
    isolation level, but oracle driver does not support it and gives error.Is
    there a way to turn off isolation level in workshop? I tried manuallyedit
    weblogic-ejb-jar.xml, however,workshop cannot redeploy it after that.
    2. When not using XA, oracle thin driver works fine. But we lost XA
    capability.
    Any work around?

  • Hard drive problem with HP Pavillion dv7-4180us

    Hard drive problem with my HP Pavillion dv7-4180us. Using Windows 7.
    Boots up sometimes and very slow.
    Appreciate any help.

    Have you booted into the BIOS or Diagnostics Tool to run the Hard Drive Test?

  • General install and deployment problem with WLS clustering on two boxes

    Hi,
    I've come across a general installation problem with WLS with a cluster spanning two different physical machines and two Managed Servers, one Managed Server per physical machine.
    The problem is, starting from scratch, you install WLS on both physical machines. You can then use the config wizard to create the domain, cluster and managed servers, but this is a manual typing in process.
    So we've now got a WLST Script which we run with "java weblogic.WLST domaincreate.py domain.properties". This is good as it creates the domain, cluster, managed servers and JMS modules.
    Now the trouble is, it doesn't do anything to the 2nd physical machine which will be running only the 2nd Managed Server.
    One dirty way to get around this in order to start the 2nd managed server was to copy the domain directory to the 2nd server, but I'm sure this is bad practice and what you can actually do is improve the WLST script to actually, but the same as the config wizard and dump the nessary information to the 2nd physical machine in order so you don't need to copy the domain directory across so that it will startup straight after running the WLST.
    Any help appriecated.
    Surfbum.

    Hi I think I've found the answer. You can build a managed server template using the pack command.
    http://e-docs.bea.com/common/docs90/pack/tasks.html

  • Apache-soap Problem with WLS 5.1sp9

    I have problem with WLS 5.1sp9.
    My environment is the following :
    jaf-1.0.1
    javamail-1.2
    soap-2.2
    xerces-1.4.4
    and I want to call EJB.
    So, I write some EJB and deploy it.
    And rpcrouter work!!
    Success to deploy the Service.
    But I run into problem with calling this ejb.
    This error is the following.
    SOAP-ENV:Server.BadTargetObjectURI
    Unable to resolve target object: BC2_BoardSync
    please, help me.
    here's my example..
    ps.
    sorry for my poor English..T_T
    [ws5.10.zip]
    [vb.zip]

    I have problem with WLS 5.1sp9.
    My environment is the following :
    jaf-1.0.1
    javamail-1.2
    soap-2.2
    xerces-1.4.4
    and I want to call EJB.
    So, I write some EJB and deploy it.
    And rpcrouter work!!
    Success to deploy the Service.
    But I run into problem with calling this ejb.
    This error is the following.
    SOAP-ENV:Server.BadTargetObjectURI
    Unable to resolve target object: BC2_BoardSync
    please, help me.
    here's my example..
    ps.
    sorry for my poor English..T_T
    [ws5.10.zip]
    [vb.zip]

  • MOVED: Driver problems with Windows Professional XP 64bit Edition

    This topic has been moved to Operating Systems.
    Driver problems with Windows Professional XP 64bit Edition

    Well, after looking around the forum here I found an answer that works! I wish I could remember who to give credit too though. I installed the latest Vista drivers and I got static all the time. I tried another members suggestion of disabling the X-Fi device in the Device manager every time I log off and then enable the X-Fi the next time I log in. I have great sound as long as I do that. Also, for connecting to a home system I am using the DTS-60, $00 on this website, but it works well if you havea DTS decoder. I am using the X-Fi extreme Music edition. Good Luck, hopefully another driver is on the way.

  • Oracle 8.1.5 JDBC driver problem with LONGVARCHAR

    Hi, I'm having problem with 8.1.5 release on Solaris with the
    JDBC type 4 driver (thin). If I create the following table
    create table test1 (col1 NUMBER, col2 LONG);
    Using JDBC driver to insert into the second column any string
    longer than 4000 characters causing run time exception. The type2
    driver works fine, but type2 is slow.
    String sql = "insert into test1 (col1, col2) values (1099,?)";
    PreparedStatement stmt ;
    stmt = conn.prepareStatement(sql);
    // create a string with very long value , bigger than 4096
    stmt.setString(1,string);
    stmt.executeUpdate();
    runtime exception:
    java.sql.SQLException: Data size bigger than max size for this
    type
    at java.lang.Throwable.<init>(Compiled Code)
    at java.lang.Exception.<init>(Compiled Code)
    at java.sql.SQLException.<init>(Compiled Code)
    at oracle.jdbc.dbaccess.DBError.check_error(Compiled
    Code)
    at oracle.jdbc.ttc7.TTCItem.setArrayData(Compiled Code)
    at
    oracle.jdbc.driver.OraclePreparedStatement.setItem(Compiled Code)
    at
    oracle.jdbc.driver.OraclePreparedStatement.setString(Compiled
    Code)
    at testi.main(Compiled Code)
    Any help is appreciated.
    Thanks
    Steve
    null

    Post the full stacktrace here
    Also you might want to post jdbc related questions to weblogic.developer.
    interest.jdbc
    Kumar
    DreamNEON wrote:
    Hello,
    the NSAPI integration works, also the JSP files.
    But I have still problems with the Jdriver for my Oracle 8.1.5.
    I get the message :
    Failed to invoke startup class
    weblogic.jdbc.common.internal.JdbcStartup=weblogic.jdbc.common.internal.JdbcStartup
    when the WebLogic Server is started.
    Any ideas or hints about that?
    Thanks in advance
    Armin

  • ConnectionPool problems with WLS 7.0 and Oracle 9.2

    Hi,
    We are using WLS 7.0 SP4, and Oracle 9 and the Oracle thin driver type 4. In our
    application on the productive system (and only there) we constantly encounter
    a whole set of SQLExceptions which have all in common that the Connection from
    the pool is not valid any more when the application tries to use it.
    Typical, recurring error messages are:
    - Exhausted ResultSet
    - Connection has already been closed
    - Closed Statement
    - Transaction is no longer active - status committing
    - NullPointerException at
    weblogic.jdbc.pool.Connection.prepareStatement()
    There are no special Statements which create these errors. They are spread at
    random across practically every query the application creates, and the same queries
    sometimes succeed and sometimes fail.
    I double and triple checked that all Connections, Statements and ResultSets are
    closed immediately after use. As an example, I attached a code snippet and a resulting
    StackTrace which.
    The problem also seems to occur only with an (unknown) minimum of concurrent usern,
    since in the approval tests on an almost identical test system these errors never
    occurred.
    I also followed the advice from Oracle and installed the latest Oracle JDBC driver
    (Oracle 10g) - to no avail.
    What else can I do?
    Another question: Is it correct that my Oracle JDBC driver is in the application
    classpath (via a reference in the Manifest file of the application jar), not in
    the system classpath? There has never been a problem with that, but in a Newsgroup
    answer from Nov 10, 2003 (subject: "ResultSet closes prematurely"), Joe Weinstein
    suggested to "get it listed at the
    front of the -classpath argument that the startWebLogic script creates for the
    java line that starts the server".
    I hesitate to do so, since the driver is in a standard WebApp- directory, WEB-INF/lib.
    Is it possible and safe to add a jar located there to the system classpath? If
    it is possible, why is it necessary?
    Best regards,
    Andreas Zehrt
    [CodeSnippetsAndStackTraceForConnectionPoolProblem.txt]

    Andreas Zehrt wrote:
    Hi Joe,
    Your hint that there is a threading problem was right:
    On further investigation of the code I found out that the class that passes the
    Connection to the DAO not only stores it as a member at some point (which is not
    a good idea anyway) but is also a singleton - then, of course, it's no surprise
    that the Connection gets invalid in a incalculable way when concurrent threads
    share it.
    The singleton instantiation was not so obvious because the way of instantiation
    is controlled by a configuration parameter that can be overridden at different
    levels.
    I changed it and the productive logfiles indicate that the SQLExceptions related
    to that class have disappeared.I am happy to have helped.
    So, thanks a lot for the advice.
    But I am still wondering why this code has worked for so long a time with WLS
    5.1 and Oracle 8 (the system has been productive for over 2 years). Even in the
    approval tests with WLS 7.0 and Oracle 9, we did not run into problems, although
    it was multi-user environment.Mo idea.
    I still believe that there is a difference between WLS 5.1 and 7.0 in the way
    it treats pooled Oracle JDBC Connections. I wished both Oracle and Bea could be
    a little more explicit about those changes and possible version incompatabilities
    beyond the general advice "use the latest thin driver".Though I can think of no change to our pooling which would have had any material
    effect in this case, I will certainly do what I can to see that our documentation
    is explicit about changes.
    Joe
    Best regards, Andreas
    Joe Weinstein <[email protected]> wrote:
    Hi Andreas.
    Andreas Zehrt wrote:
    Hi,
    We are using WLS 7.0 SP4, and Oracle 9 and the Oracle thin driver type4. In our
    application on the productive system (and only there) we constantlyencounter
    a whole set of SQLExceptions which have all in common that the Connectionfrom
    the pool is not valid any more when the application tries to use it.
    Typical, recurring error messages are:
    - Exhausted ResultSetThat is typically if the statement that created it is either re-executed
    or closed.
    - Connection has already been closedAs described. If you give a stacktrace, we could make a debug patch which
    would show
    where it was originally closed.
    - Closed Statementsame as above.
    - Transaction is no longer active - status committingThat implies your code is obtaining a connection from a transactional
    datasource,
    and then later trying to use it after the transaction which it was associated
    with,
    is finished.
    - NullPointerException at
    weblogic.jdbc.pool.Connection.prepareStatement()Maybe any of the above.
    There are no special Statements which create these errors. They arespread at
    random across practically every query the application creates, andthe same queries
    sometimes succeed and sometimes fail.
    I double and triple checked that all Connections, Statements and ResultSetsare
    closed immediately after use. As an example, I attached a code snippetand a resulting
    StackTrace which.
    The problem also seems to occur only with an (unknown) minimum of concurrentusern,
    since in the approval tests on an almost identical test system theseerrors never
    occurred.
    I also followed the advice from Oracle and installed the latest OracleJDBC driver
    (Oracle 10g) - to no avail.
    What else can I do?
    Another question: Is it correct that my Oracle JDBC driver is in theapplication
    classpath (via a reference in the Manifest file of the applicationjar), not in
    the system classpath? There has never been a problem with that, butin a Newsgroup
    answer from Nov 10, 2003 (subject: "ResultSet closes prematurely"),Joe Weinstein
    suggested to "get it listed at the
    front of the -classpath argument that the startWebLogic script createsfor the
    java line that starts the server".
    I hesitate to do so, since the driver is in a standard WebApp- directory,WEB-INF/lib.
    Is it possible and safe to add a jar located there to the system classpath?If
    it is possible, why is it necessary?I was only concerned to ensure we know which driver we are working with.
    We also ship
    an oracle thin driver, which becomes obsolete soon...
    I am concerned that your code creates pool connections to be used later.
    The problems
    can arise if more than one thread ever gets the same connection, or if
    the connection
    is used in the same thread, spanning transactions. It does also seem
    that there may
    be a threading issue, because if two threads each call the code to create
    a connection,
    and two connections are made, but one over-writes the other, the two
    threads can
    end up using the same connection, and closing it. The over-written one
    never gets closed,
    resulting in that leak message you got...
    Joe
    The Connection parameter is opened by a business component class, ComaServiceProviderClassicImpl.It is propagated through
    several classes in the business layer, but not used, until the DAOtakes it to make the query.
    So, the Connection is closed where it was opened, not in the DAO class.
    public class ConcernDAOImpl extends BaseDAO {
         public Collection getConcernsForIncidents(Connection conn, Collectionincidents)
    throws DataAccessException, ConstraintException, ComaParseException{>
    sqlMessage.append(")");
    String sqlStmt = sqlMessage.toString();
    PreparedStatement pstmt = null;
    ResultSet rs = null;
    try {
    pstmt = conn.prepareStatement(sqlStmt);
    rs = pstmt.executeQuery();
    while (rs != null && rs.next()) {
    final Concern concern =
    new Concern(DAOUtil.getComaOID(rs, ComaDBNames.KDANR));
    concern.setIncidentOID(DAOUtil.getComaOID(rs, ComaDBNames.KDAVGENR));
    return concerns;
    } catch (SQLException sqle) {
    // Wrapps real SQL exception
    String[] message = new String[]{sqle.getMessage(), sqlStmt};
    throw new DataAccessException(ExpCode.S_ORACLE_SQL, message,
    sqle);
    } finally {
    closeAll(rs, pstmt);
    _logger.exitDebug(method);
    Here, the Connection is acquired and finally closed
    public class ComaServiceProviderClassicImpl {
         public void updateComplaint(
    final Request updateRequest,
    final ResponseSingleElement response,
    final Principal principal)
    throws SystemException {
    try {
    logger.info("updateComplaint", "store incident");
    // store the incident in the database
    incidentManager.storeIncident(getConnection(), updateIncident);
    // reload the incident from Cache and / or the databaseto get the ContactReferences.
    Incident returnIncident = incidentManager.loadIncident(//IncidentManager passes the Connection to the DAO
    getConnection(), updateIncident.getOID());
    } catch (RemoteException rex) {
    // remote exceptions
    rollbackIfNecessary();
    CoreUtils.unwrapRemoteException(rex, logger);
    } catch (SystemException e) {
    // all other exceptions --> rollback if necessary and rethrow
    rollbackIfNecessary();
    throw e;
    } finally {
    removeConnection();
    logger.exitDebug("updateComplaint");
    This is the resulting StackTrace:
    sql exception: [Closed Statement: next] - sql statement: [select *
         at de.deutschepost.ubbrief.coma.persistence.dao.ConcernDAOImpl.getConcernsForIncidents(ConcernDAOImpl.java:363)
         at de.deutschepost.ubbrief.coma.persistence.dao.CachingConcernDAOImpl.getConcernsForIncidents(CachingConcernDAOImpl.java:129)
         at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadConcernStructuresIntoIncidents(IncidentManagerImpl.java:1067)
         at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadStructureForIncident(IncidentManagerImpl.java:320)
         at de.deutschepost.ubbrief.coma.persistence.incidentmanager.IncidentManagerImpl.loadIncidents(IncidentManagerImpl.java:264)
         at de.deutschepost.ubbrief.coma.persistence.taskmanager.TaskManagerImpl.selectTasksForUser(TaskManagerImpl.java:299)
         at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Impl.getTaskList(ComaServiceProviderZ2Impl.java:113)
         at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Bean_1dhrj7_EOImpl.getTaskList(ComaServiceProviderZ2Bean_1dhrj7_EOImpl.java:154)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList.runServiceMethod(CMPGetTaskList.java:64)
         at de.deutschepost.ubbrief.coma.sbbx.sp.BasicMethodProvider.execute(BasicMethodProvider.java:145)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl.execute(CMPGetTaskList_9b9mv5_EOImpl.java:46)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLSkel.invoke(UnknownSource)
         at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:159)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:263)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:230)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLStub.execute(UnknownSource)
         at de.deutschepost.ubbrief.backbone.jazz.impl.core.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:115)
         at de.deutschepost.ubbrief.backbone.common.impl.core.rpc.server.ServerKernelImpl.handleTransportMessage(ServerKernelImpl.java:270)
         at de.deutschepost.ubbrief.backbone.common.impl.core.messaging.MessageTransport.handleMessage(MessageTransport.java:454)
         at de.deutschepost.ubbrief.backbone.common.impl.core.KernelFacade.handleMessage(KernelFacade.java:209)
         at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean.messageArrived(BackboneBean.java:637)
         at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean_ina9d7_ELOImpl.messageArrived(BackboneBean_ina9d7_ELOImpl.java:105)
         at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.LocalQueueReceiveBean.deliverMessage(LocalQueueReceiveBean.java:43)
         at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.AbstractMessageReceiveBean.onMessage(AbstractMessageReceiveBean.java:127)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:377)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:311)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:286)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2351)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2267)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
    ####<May 26, 2004 12:18:43 PM CEST> <Warning> <JDBC> <S0048016> <REMA20Z><Finalizer> <kernel identity> <> <001074> <A JDBC pool connection leak
    was detected. A Connection leak occurs when a connection obtained from
    the pool was not closed explicitly by calling close() and then was disposed
    by the garbage collector and returned to the connection pool. The following
    stack trace at create shows where the leaked connection was created.
    Stack trace at connection create:
         at weblogic.jdbc.pool.Connection.<init>(Connection.java:66)
         at weblogic.jdbc.pool.Driver.allocateConnection(Driver.java:294)
         at weblogic.jdbc.pool.Driver.connect(Driver.java:210)
         at weblogic.jdbc.jts.Driver.getNonTxConnection(Driver.java:373)
         at weblogic.jdbc.jts.Driver.connect(Driver.java:129)
         at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:287)
         at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnectionFromPool(ComaComponentImpl.java:163)
         at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnectionInternal(ComaComponentImpl.java:135)
         at de.deutschepost.ubbrief.coma.core.ComaComponentImpl.getConnection(ComaComponentImpl.java:99)
         at de.deutschepost.ubbrief.coma.persistence.customermanager.CurryCustomerManagerImpl.findCustomers(CurryCustomerManagerImpl.java:73)
         at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2BaseImpl.resolveCustomerInstances(ComaServiceProviderZ2BaseImpl.java:808)
         at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Impl.getTaskList(ComaServiceProviderZ2Impl.java:213)
         at de.deutschepost.ubbrief.coma.service.z2.ComaServiceProviderZ2Bean_1dhrj7_EOImpl.getTaskList(ComaServiceProviderZ2Bean_1dhrj7_EOImpl.java:154)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList.runServiceMethod(CMPGetTaskList.java:64)
         at de.deutschepost.ubbrief.coma.sbbx.sp.BasicMethodProvider.execute(BasicMethodProvider.java:145)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl.execute(CMPGetTaskList_9b9mv5_EOImpl.java:46)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLSkel.invoke(UnknownSource)
         at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:159)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:263)
         at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:230)
         at de.deutschepost.ubbrief.coma.sbba.z2.CMPGetTaskList_9b9mv5_EOImpl_WLStub.execute(UnknownSource)
         at de.deutschepost.ubbrief.backbone.jazz.impl.core.RequestHandlerImpl.handleRequest(RequestHandlerImpl.java:115)
         at de.deutschepost.ubbrief.backbone.common.impl.core.rpc.server.ServerKernelImpl.handleTransportMessage(ServerKernelImpl.java:270)
         at de.deutschepost.ubbrief.backbone.common.impl.core.messaging.MessageTransport.handleMessage(MessageTransport.java:454)
         at de.deutschepost.ubbrief.backbone.common.impl.core.KernelFacade.handleMessage(KernelFacade.java:209)
         at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean.messageArrived(BackboneBean.java:637)
         at de.deutschepost.ubbrief.backbone.jazz.impl.backbone.BackboneBean_ina9d7_ELOImpl.messageArrived(BackboneBean_ina9d7_ELOImpl.java:105)
         at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.LocalQueueReceiveBean.deliverMessage(LocalQueueReceiveBean.java:43)
         at de.deutschepost.ubbrief.backbone.jazz.impl.transport.receive.AbstractMessageReceiveBean.onMessage(AbstractMessageReceiveBean.java:127)
         at weblogic.ejb20.internal.MDListener.execute(MDListener.java:377)
         at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:311)
         at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:286)
         at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2351)
         at weblogic.jms.client.JMSSession.execute(JMSSession.java:2267)
         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)

  • Having hard drive problems with 2011 macbook pro

    Hey all,
    I am having some hard drive issues with a 2011 Macbook Pro running OS X Mavericks.
    How it happened: I was browsing the web when suddenly I got the spinny-wheel-of-death.  The spinny wheel of death stuck around for much longer than usual, and eventually my computer wouldn't even respond to mouse input (the mouse wouldn't move).  Nothing worked, so I did a hard reset of my computer.  When I rebooted the machine, it took me into "Recovery Disk Mode".
    Here are the diagnostics that I've done: In "Recovery Disk Mode", I have the option to use the Disk Utility, which I have done.  My main volume, called "Macintosh HD" is grayed out - and not mountable.  When I run "first aid" on it, it is not able to verify the disk because of an "Invalid B-tree node size".  It then tells me to repair the disk.  I have tried repairing the disk, but it fails - and that is not entirely unexpected because all of the forum posts that I have read up until now say that Disk Utility cannot repair this specific type of error.
    3rd party software I have tried: Based on the forum posts that I have read, Disk Warrior is especially capable at fixing this kind of error, so I went to my local computer shop, purchased the software, and booted into it.  Disk Warrior did not recognize my drive, and did not even show it in the list of available options.
    Other things I have tried: I purchased a Seagate external drive, and I tried to use Disk Utility to copy the contents from my MBP's hard drive over to the external drive, but when I do so, "Disk Utility" tells me that "Recovery partition restores can only be done on GPT partition maps."  I have also had it give me another error message where it says it "cannot verify source - error 254". 
    Additionally, I have seen around the internet that many people try using "fsck" to fix this issue, but I haven't been able to find a good explanation of the proper steps when using "fsck", nor how to specify to the "fsck" program that I want it to fix my "Macintosh HD" volume.  I've opened up the terminal, and gone into the "/dev/" folder, but I don't know which item in that folder, or any other folder, would properly lead down the path to my "Macintosh HD" volume.  Also, the man pages seem to be of little help here.
    One option I would like to try, but I have not been able to, is to try putting my MBP into Target Disk Mode, and see if my desktop machine (a Dell) can see it.  The problem here is that my Dell only has USB ports - no Firewire, and obviously no Thunderbolt ports.  I would need to find a way to plug my MBP into my Dell while it is in Target Disk Mode, but from what I can tell, that's impossible if I don't have a Firewire or Thunderbolt port on my Dell.
    So, now having explained everything I have tried, can y'all give me any advice on how I can recover my drive without completely repartitioning it?  Although most of my important data and files are located on cloud services, there are definitely some files on the drive that I don't have backed up, and I would like to recover the drive without losing those files.  What suggestions can you give me?  Thanks!

    Yes, BUT...
    ... there are many problems that are really easy to eliminate by replacing the Hard drive, including ones that have nothing to do with actual Drive Hardware failure. These include corrupted install of Mac OS X, its EFI partition, clobbered partition tables, or the appearance of Bad Blocks in a critical area.
    Any of these problems can sometimes be eliminated by re-initializing the entire drive and writing Zeroes, and re-installing from scratch. The trouble is, this process takes hours to complete, and is not guaranteed to be successful -- you may still need a new drive after all that effort.
    I learned from my Plumber that consumers have no appetite for solutions that might work, and detest return visits for any related problems whatsoever. You or your friend may have had your drive replaced, not because it actually failed, but because the situation was troublesome, and the provider thought you would not tolerate anything less than a crisp, complete fix on the first attempt. And based on the cost of technician time, it may have even been cheaper that way.

  • Sqljdbc4 driver problem with the latest version of java (java6 update9)

    Hi all, sorry for my ingles.Need help with a problem, I have to connect to sql server 2008 from Java, I had install the Java SE Development Kit 6u22, and when the upgrade to the 6u29, the driver stopped working, they let the following example:
    public static Connection getConnection(String db_connect_string,String jdbcDriver)
    Connection conn = null;
    try {
    Class.forName(jdbcDriver);
    conn = DriverManager.getConnection(db_connect_string); //when you run this line, does nothing mores, nor throws errors
    } catch (Exception e) {
    System.out.println("Error de conexion." + e.getMessage());
    return conn;
    uninstall update29, and install that before and had returned to work. Still do not know how to solve this problem with the latest version of java. Any ideas?.
    Thanks.

    You are not the only one.
    MS SQL JDBC does not work with 1.6.0_29?

  • JDBC Connection Driver Problem for Oracle in a J2EE servlet/class

    Hi,
    I am having a big problem with setting up a JDBC connection with my oracle database, I have been trying to fix it for about 6 hours now with no joy, I have read that many threads about JDBC, class paths etc.. that i dont know which way is up any more!!
    Here is the issue:
    (Please bare in mind that I am new to this when posting replies)
    I have a Web Application set up as a project in the netbeans IDE. I have a servlet which creates a new object call dbaseFunc which is a public class I have wrote and within this class is a function called getAppConfigCon(). The code for this function is below:
    public Connection getAppConfigCon()
    Connection con = null;
    try
    Class.forName("oracle.jdbc.driver.OracleDriver");
    con = DriverManager.getConnection("jdbc:oracle:thin:@localhost:1521:xe","cavdev", "password");
    catch (SQLException e)
    e.printStackTrace();
    catch (ClassNotFoundException e)
    e.printStackTrace(System.out);
    return con;
    The database is Oracle XE and is installed on the same machine I am developing on, the database is up and I can connect to it via the netbeans IDE database interface after telling it where the driver is (C:\oracle\product\10.2.0\client_1\jdbc\lib\ojdbc14.zip). Obviously this is just IDE functionality and allows you to browse the database objects from netbeans however I now need to know how to tell the jre where the drivers are, right??
    Well like I said multiple forums led me down the classpath route and I have a system environment variable called CLASSPATH set up with the oracle jdbc driver specified as its value, when i run the set command from the command line ( I am running Windows XP Pro) I can see the class path entry in the output as follows:
    CLASSPATH=C:\oracle\product\10.2.0\client_1\jdbc\lib\ojdbc14.zip
    When I try to run my web app it doesnt assign the connection object with a value, i.e. when i was debugging my con object was null after calling the method mentioned above. After some time debugging i found a ClassNotFoundException was being thrown when the following command was executed:
    Class.forName("oracle.jdbc.driver.OracleDriver");
    Which I understand is because their is a problem with the class path but what is the problem??? The IDE likes the driver so why doesnt the jre.
    I am runnin jdk and jre 1.5, an Oracle XE Database using the netbeans environment.
    Some one please help me, I have spent far to much time on this rather than actually working on my project!!!!
    Thanks
    Keith

    Well After 10.5 hrs I actually sorted this myself, the two problems that were throwing me were this:
    1. Netbeans does not stop the tomcat server when it finishes running the app, you either have to stop the server from the menu or exit netbeans, until the server restarts it will not pick up on any driver files you add to common/lib
    2. You are very right Kiros tomcat does not do .zip files!!!!~~~###
    In order to sort this I had to add the oracle driver as a package to my project using the netbeans ide Project > Libraries > New Jar file, this allowed me to access the oracle classes. Then I had to set the server up to deal with the drivers as well, this meant adding the .jar file (not the latest .zip as it wont work) to the bundled tomcat common lib directory and restart the server via the ide (using the start/stop bat files in the tomcat conf directory doesnt work for some reason when its bundled with netbeans!)
    Thanks for the help guys but in the end it took 10 hrs a lot of reading and 2 bottles of lucozade to keep the brain goin.
    Keith

  • Samsung hard drive problems with mid 2009 Macbook Pro

    Arghh, this is driving me mad. 
    I'd like to know if anyone has installed a Samsung HM641JI SATA II hard drive into a mid 2009 Macbook Pro (mine is a 2.8Ghz) and, if so, how they managed it. The drive is 640GB. These are the steps I've taken:
    1. Swap out the stock drive for the Samsung
    2. Boot from a USB drive which contains a mirror of my system
    3. When the system identified the new disk, I formatted it with 2 partitions (GUID table, HFS journaled)
    4. Reboot
    5. System is very slow. Boots from USB but can't use keyboard to login
    6. Switch off and try again
    7. Remove Samsung drive
    8. Reboot from USB (works perfectly)
    9. Downgrade firmware to 1.6
    10. Replace samsung drive and try again
    11. System boots from USB
    12. Verify that drive is running at 1.5Ghz
    13. Disk utility and system profiler both crash
    14. Disk unmounts by itself and other random weirdness
    15. Remove Samsung drive
    I've read endless reports about the firmware in this model of Macbook Pro and its issues with SATA II but struggling to find anything current and specific. Two questions:
    a. Is there anythign I can do to get this drive to play nicely?
    b. What drive should I get if the answer to a is no?
    As a bit of background.. my system began playing up last week with lots of spinning beach balls resulting in forced switch offs. Booting from a mirror on a USB drive works perfectly so I concluded that the drive was on its way out. A drive test utility confirmed this. I'm now wondering if it really was the drive or the cable or the logic board.
    Any advice appreciated.
    Cheers
    //A

    I'm coming around to the idea that this might be a problem with the SATA cable rather than the drive.
    I currently have the stock drive (Hitachi) back in the macbook. It mounted for a while and was then ejected when I tried writing data to it. System profiler reports that "There was an error while scanning for Serial-ATA devices."
    I was able to mount the same drive in a USB enclosure this afternoon without any problems. Right now, I seem to be having issues with both the Samsung drive and the Hitachi drive - I wasn't suspicious of thr latter because I thought it was failing.
    I found one or two accounts of other people having similar problems that were resolved with a new sata cable.
    How does a cable fail? Could this be my problem?
    Cheers
    //A

  • Scanner driver Problem with - Windows 8.1 and HP AIO L7680

    Hi folk,
    i have a problem with my HP AIO L7680.
    I have made an upgrade to Windows 8.1 x64
    I install the actual driver version 14.8.0.
    The printer runs but the scanner makes trouble.
    When i will start a scan process i will get an error message and the scan process will be canceled.
    I will get this error message with photoshop, HP Solution Center and any other scanner software.
    The HP Print and Scan Doctor says i should contact the support.
    Here i am any idea?
    By the way i disabled my Antivirus Software during the installation.
    Thanks a lot.
    greetings
    Markus
    This question was solved.
    View Solution.

    Hi Markus,
    I understand that you are having an issue with scanning after upgrading to Windows 8.1. I will try my best to help you resolve this issue. I just need a little more information. What operating system are you running on your computer? Are you connecting wireless or with a USB cable? What is the error message that you are getting?
    I am including this document for A 'No Scan Options' or 'Scan settings are not set' Message Displays on the All-in-One there are trouble shooting steps for Windows 8 that will work for Windows 8.1.
    I hope this helps, let me know.
    Thank you,
    I worked on behalf of HP.

  • [SOLVED!] On USB drives, problems with non-English chars and HAL

    Hello,
    I am having a problem with non-English caracters (áãàçéẽê...) on files stored on my USB drive.
    On Windows they're created with the correct name. But on Linux the files have the non-English characteres replaced by '?' and are not accessible.
    If I manuallly mount the drives using 'mount -o iocharset=utf8 /dev/sdb1 /media/usbdisk' the characters are OK, so I think I just need to get HAL to pass the correct parameters to mount. However I don't know how to do that, and haven't found any good solution.
    I tried to build a custom kernel setting the default charset as UTF-8 and it didn't work.
    Any ideas? I'm using x86-64, HAL 0.5.13-3 and my locale is pt-BR.UTF-8.
    Thanks!
    EDIT: Actually, this is not a HAL problem, but a problem with 'exo'. For the solution, I edited /etc/xdg/xfce4/mount.rc and added iocharset=utf8 to the [vfat] category.
    Last edited by Renan Birck (2009-11-28 20:54:23)

    I don't use Thunar presently, but I looked in the Thunar Volume Manager doc and I didn't find anything to change the mount options of removable drives. I am not quite sure if it's possible or not. Maybe someone using it can tell for sure.
    But if it is not possible to change the mount options, a possible solution is to disable the Thunar Volume Manager plugin and to use something else more configurable to manage the automount function.
    Personally I use the halevt package from AUR which uses configuration files in the xml format.
    It's not so easy to use but is highly configurable.
    But there exists other tools also.
    I can help you with halevt if you choose that way...

  • Print driver problem with OS 10.4.6

    I recently installed 10.4.6 and ever since have been unable to print via a network on a Lexmark Optra T614 (duplex). All was working fine until the upgrade to 10.4.6. I have downloaded a driver from Lexmark's website and successfully installed it to my system via the wizard - message was "you have successfully installed . . . ". However cannot find it to install through the Print Centre. I am running it through a router shared with a PC (Windows 2000). No problems at the Pc end. As I said prior to purchasing 10.4.6 all was working fine. I have tried to set up to print through the local network via the PC - without success. At one point (not sure what I did) actually got the Mac talking to the printer. The lights were activated and it made a few attempts but then cancelled out. I then tried something else and it didn't work, so now I am back to where I was when I started. Can you help with this one Greg? regards Ian

    Hi Greg, Still no answer to my printing problem.
    The Optra T driver is probably right.
    I trashed the drivers and did a fresh download and reinsatlled. It is an Optra T driver.
    Since you can't print using generic postscript, I don't think you
    have a driver problem. If the printer supports LPD or
    IPP, you probably need to enter a device queue name
    in Printer Setup. (No queue name for HP Jetdirect
    protocol) L1, P1, LPT1, and print are common queue names
    I have set up so that Printer Name is 192.168.0.200. This automatically selected Lexmark Optra T. Also the queue name appeared as 192_168_0200-1. Host name was blank and Driver Version 10.4 and PPD File Version is 10.4.3.3.0. I tried to print the Print box showed Preparing . . then Processing Page 1 and dissapeared in the normal manner. I opened the Printer Monitor (in the dock) and it showed the job in the queue as it should and the Status showed: printing. The blue bar scrolls and the message Connected to 192.168.0.200 comes up. The printer shows no sign of receiving the file. I have done this numerous times. I have also keyed in the computer name in the location and still no go - just the same outcome. The computer name is ian-brownlees-computer.local.
    Look in the printer manual or google for it.
    Unfortunately I don't have a manual but have been trying to locate one.
    Any further clues??

Maybe you are looking for