This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 85487 - Classes altered by profiler make connection to Oracle DB fail
Summary: Classes altered by profiler make connection to Oracle DB fail
Status: RESOLVED INVALID
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: All Linux
: P3 blocker (vote)
Assignee: issues@profiler
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-21 21:48 UTC by denka_b
Modified: 2007-08-13 16:50 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description denka_b 2006-09-21 21:48:49 UTC 
Had this issue with Profiler 6.0 M2 and same is with M3. When I try to profile
my server app that uses Spring, Hibernate and connects to Oracle Db using JDBC,
this obscure exception is thrown:

Message:   No more data to read from socket
SQLState:  null
ErrorCode: 17410
java.sql.SQLException: No more data to read from socket
        at
oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
        at
oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
        at
oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:208)
        at oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1118)
        at oracle.jdbc.driver.T4CMAREngine.unmarshalSB1(T4CMAREngine.java:1070)
        at oracle.jdbc.driver.T4C8TTIdty.receive(T4C8TTIdty.java:441)
        at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:337)
        at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:427)
        at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:165)
        at
oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)
        at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:806)
        at java.sql.DriverManager.getConnection(DriverManager.java:528)
        at java.sql.DriverManager.getConnection(DriverManager.java:140)

Profiler is launched in "Analyze Memory Usage" profile with default settings
(record obj creations only, track every 10 object allocs, do not record stack
traces).
Comment 1 Tomas Hurka 2006-09-22 12:23:37 UTC 
This is really strange. I am not sure how this can be caused by profiler. Is it 100% reproducible? Which 
version of JDK are you using?
Comment 2 denka_b 2006-09-22 17:23:20 UTC 
I've a suspicion that timing lag introduced by instrun=mentation is responsible
for this... This happens 100% of the time. 

java version "1.5.0_06"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_06-b05)
Java HotSpot(TM) Server VM (build 1.5.0_06-b05, mixed mode)
Comment 3 Tomas Hurka 2006-09-22 20:15:46 UTC 
Can you please try 1.5.0_08 if it makes any difference. Thanks.
Comment 4 Alexander Kouznetsov 2007-08-13 16:50:20 UTC 
Closing due to no response on INCOMPLETE status. Please reopen if necessary.