Skip to Main Content

New to Java

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

NetBeans: Adding Elements in a list Box

Zulfi KhanJul 4 2016 — edited Jul 10 2016

Hi,

I am using NetBeans 8.1. I have created a list using swing component. I have a text box (variable name :TF) & 3 buttons. button1 is variable corresponding to the add button. I want to write its handler. I dont know what is the method of list box which can add elements in the list box.

When I press the add button, the data in text field should store in the list box. My variables are:

private javax.swing.JButton button1;

    private javax.swing.JButton button2;

    private javax.swing.JButton button3;

    private javax.swing.JLabel jLabel1;

    private javax.swing.JPanel jPanel1;

    private javax.swing.JScrollBar jScrollBar1;

    private javax.swing.JScrollPane jScrollPane1;

    private javax.swing.JTextField jTF;

    private javax.swing.JList<String> list;

I cant find the addElement ( ) method to add the string from the textbox into the list.

private void button1ActionPerformed(java.awt.event.ActionEvent evt) {                                       

        // TODO add your handling code here:

        String str=jTF.getText();

        list.???

    }    

Some body please guide me about the method to addElement in list box.

Zulfi.

This post has been answered by Zulfi Khan on Jul 10 2016
Jump to Answer

Comments

John Thorton

580988 wrote:

Hi All,

I have a stored procedure which is running forever. The particular stored procedure reads a file and performs validation and inserts into some transaction table.

There are many stored procedures that are called within the main procedure. There might be locks or blocks or some query is taking long time to execute

How do i find out which query in which procedure is taking long time to execute? But sometimes the same procedures completes successfully within few seconds inserting

all the records (10000 recs).

Thanks

Gautam S

Consider to issue SQL below just prior to starting the rogue procedure.

ALTER SESSION SET SQL_TRACE=TRUE;  -- ensure the USER has necessary privilege to successfully run this SQL statement

process resultant trace file using TKPROF

ms

I just ran the main procedure now and it ran successfully within few seconds. I don't know why it was not running earlier 1 hour ago. Can someone throw some light on this?

Thanks

Gautam

John Thorton

580988 wrote:

I just ran the main procedure now and it ran successfully within few seconds. I don't know why it was not running earlier 1 hour ago. Can someone throw some light on this?

Thanks

Gautam

Something changed, but we don't know what you have.

Does any of the SQL in your mystery procedure use bind variables?

ms

No, none of the SQL use bind variables. My procedure calls the innermost procedure which is a PRAGMA AUTONOMOUS procedure.

FYI : The innermost procedure has a FOR UPDATE in a select clause. I have issued proper COMMIT/ROLLBACK also in that procedure. Does it have something to do with that? Also, the total record count i am processing is 10000.

Thanks

Gautam

ms

@John Thorton

However the records are processed successfully and inserted into relevant tables. Only the session keeps hanging in SQL Developer.

Let me know if you need anything else. If the session keeps hanging probably the application would also keep hanging in Production.

Can you someone kindly help on this.

Thanks

Gautam

ms

Hi all,

It's solved. The hanging was due to the excessive dbms_output messages being populated for each of the 10000 records.

Cookiemonster76

580988 wrote:

No, none of the SQL use bind variables.

Are you using dynamic SQL? Because unless you are, all your SQL will definitely be using bind variables. PL/SQL sorts that out automatically.

BEDE

The most simple thing is to use a log table and log there when the code gets to some place using a store procedure with pragma autonomous_transaction.

Or, you may see what shows in the sys.gv_$open_cursor and sys.gv_$sql for that session of yours, like below:

select sq.*

from sys.gv_$open_cursor oc

join sys.gv_$sql sq on oc.sql_id=sq.sql_id and oc.inst_id=sq.inst_id

where oc.sid=&sid and oc.inst_id=&inst_id

and sq.users_executing>0

;

If it's quite difficult to know which your session is, you may mark that session using the facilities of package dbms_application_info.

BEDE

If you suspect there may be some session blocking:

Select * from sys.gv_$session_blockers

;

And see what you get.

1 - 9
Locked Post
New comments cannot be posted to this locked post.

Post Details

Locked on Aug 7 2016
Added on Jul 4 2016
4 comments
3,673 views